Skip to content

Conversation

@dynco-nym
Copy link
Contributor

@dynco-nym dynco-nym commented Jun 27, 2025

This change is Reviewable

@vercel
Copy link

vercel bot commented Jun 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nym-explorer-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 11, 2025 9:59am
nym-next-explorer ❌ Failed (Inspect) Jul 11, 2025 9:59am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
docs-nextra ⬜️ Ignored (Inspect) Visit Preview Jul 11, 2025 9:59am

export ENVIRONMENT=${ENVIRONMENT:-"mainnet"}

probe_git_ref="nym-vpn-core-v1.10.0"
probe_git_ref="nym-vpn-core-v1.4.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

downgrade?

.inspect(|_| {
let elapsed = now_utc() - started_at;
info!(
"📊 ☑️ Packet stats successfully committed to DB (took {}s)",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: use humantime::format_duration which is more readable, especially for smaller values. I think it will be better than say 0.1234567s : )

tokio::spawn(async move {
scraper.start().await;
});
let scraper = node_scraper::PacketScraper::new(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the nittest of nits, but can you rename this guy? at first glance, before finishing my morning coffee, I got quite confused by having two things defined as scraper

let results_clone = Arc::clone(&results);

task_set.spawn(async move {
match scrape_packet_stats(&node).await {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we add some sort of timeout here in case task gets stuck trying to scrape particular node?

} else {
success_count += 1;
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can't we set the TASK_ID_COUNTER to 0 explicitly here instead (since our join_Set is empty) and also then not make it static? (because at that point it would be fully local to this scope)

@jstuczyn
Copy link
Contributor

jstuczyn commented Jul 1, 2025

you'd probably also want to rebase against develop to deal with 1.88 clippy (and potentially add extra fixes specific to your branch)

@jstuczyn jstuczyn force-pushed the feature/batch_sqlx_writes branch from 42c03e0 to c62ab3a Compare July 11, 2025 09:41
@jstuczyn jstuczyn merged commit 35bbf5f into develop Jul 11, 2025
8 of 13 checks passed
@jstuczyn jstuczyn deleted the feature/batch_sqlx_writes branch July 11, 2025 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants