Tim Wojtulewicz

> One change I'd suggest is do the scope lookup only if the ID isn't scoped to begin with. The lookup has to happen regardless because it needs the deprecation...

Interestingly, the same test failure occurs if I make this change to the test script, even without the changes in this PR: ``` diff --git a/testing/btest/scripts/policy/misc/capture-loss.zeek b/testing/btest/scripts/policy/misc/capture-loss.zeek index d51576a5b..a6ce0e571 100644...

This is probably going to miss 4.1 since we're in RC1 already. Moving it to 4.2.

What's the status on this PR? It's been a couple of months since the last comment.

I'm not seeing this anymore on `master` with script above so it's possible that the fixes for #2332 fixed it: tim@coregeek2 build% zeek ~/Desktop/2331.zeek && sleep 1 && zeek ~/Desktop/2331.zeek...

I marked this as a good first issue. For some guidance, you can generate the coverage information locally by building with `--enable-coverage` and then running `make coverage` in the btest...

I like this idea so I put it into the 5.1 milestone.

I honestly can't say. We try to keep to roughly a 4 month cadence on releases but things have a tendency to slip over time. As for the API changes,...

If you want to take a stab at it, we'll happily review PRs. 😃 Otherwise it'd probably end up being a maintainer (likely me, since I have the most experience...

@rsmmr @Neverlord Have enough of the changes landed in Broker now to revisit this?