Bill Mark
Bill Mark
I just checked these issues against the most recent version of v8 (3.17.16.2). Issue 1 from above (JSON.stringify dying on proxies) is fixed. Issue 3 from above (Arrays returning "object...
More details: I also checked against the slightly more recent "bleeding_edge" version of v8, "3.18.0 (candidate)", and it still has the issue that calling Object.prototype.toString on a proxied array returns...
There are a bunch of confusing comments in the Flax documentation and code regarding what to do for type annotations on PyTrees. For example: https://flax.readthedocs.io/en/latest/flax.struct.html says "Note: Inherit from PyTreeNode...
@jakevdp. I realize I didn't directly reply to your question: > Beyond the recommendation to use Any for arrays and pytrees, and the caveat that type-checking is fundamentally broken as...
As I said in the original bug, "In particular, it's not clear what the parameters to the callback need to be.".. That is, what are the args passed to the...
An additional clarification. The code looks essentially like the following: ``` errs, returns = jax.pmap(jax.experimental.checkify(step_fn, ..), ...)(state, batch, rng) print(errs). # shows all four errors (one error from each device)...
It is not blocking my work any more, but I think it is critical to address this issue for other users, either by a code change or a documentation change....
I respectfully disagree. The current behavior is terrible, and just caused me to waste an enormous amount of time. When trying to track down a NaN with checkify's "float" check,...