anthony sottile

> Unfortunately pytest parametrization won't work for unittest-based tests... i don't even know y. it's because the unittest support via pytest is testgen which is incompatible with the parametrize testgen

just my 2c, this should maybe be off-by-default as it's difficult-to-impossible to know if the inner lambda / function is used in a deferred manner there's a bunch of examples...

this example appears to trigger an unrelated false positive as well: ```python def get_group_backfill_attributes(caches, group, events): return { k: v for k, v in reduce( lambda data, event: merge_mappings( [data,...

@bruno-garcia can you link the run for this? I'm not sure I completely understand all the moving parts here and would like to see where the trace is coming from

hmmm -- if you create the release manually should you then check the registry box in the publish issue so it skips the (already done) one?

the `publish` diff makes a link [against `null...`](https://github.com/getsentry/publish/issues/1315#issue-1343583859) when using the placeholder `0.0.0` tag as well

perhaps as a bandaid can #824 be considered?

@kotewar can that be configured down to say ~3 minutes? an hour is pretty bad still

@kotewar is there a reason this was done as an environment variable rather than a job input (`with`)? it's a little awkward to feed environment variables into `uses:` unless I'm...

afaict (or maybe the schema I'm using isn't up to date) `env` isn't supported on `uses` actions in `composite` actions (?) so it makes this a tiny bit tricky