Daniel Xu
Daniel Xu
Dang, unfortunate. So the ambiguity is only when the second arg is a keyed map, eg `@foo[$bar]` b/c deleting a scalar map doesn't make sense eg (`@foo`). Can we warn...
Ah, right. So `@foo[$bar]` resolves to a value (and not a map), so they get a good error.
The first arg would have had to be a keyed map for it to have been a multi-delete. New delete API requires first arg to be unkeyed map. So I...
Argh, right. Unless it's a scalar map. In which case a second argument was not valid anyways. So we're still ok there I think
My personal thought it that given bpftrace is a tracing tool (and not necessarily an error injection one even though we do have some of that already), we should not...
I'm considering an offline symbol resolution approach. If we store base addr and exe path, we should be able to resolve symbols even after the process exits. However, it'll only...
> So, delete(@map, 1) would always display a warning on failure to delete while $res = delete(@map, 1) and if (delete(@map, 1)) { ... } would move the warning to...
Closing due to inactivity
You are probably not setting `PROMETHEUS_MULTIPROC_DIR` before importing `prometheus_client`. Note that even a transitive import of `prometheus_client` from some downstream dependency can trigger this issue.
Hi, thanks for the report! Do you mind building from source and trying again on your machine? Or trying the appimage: https://github.com/bpftrace/bpftrace/blob/master/INSTALL.md#appimage-install I can't reproduce this on msater on my...