lmeyerov
lmeyerov
loaders.gl/core is `"3.0.9^"`, which in theory should allow the current `"3.4.x"` , but the `yarn.lock` looks like `3.0.9` instead of more recent: https://github.com/keplergl/kepler.gl/blob/5bae745b6a2fe60a9aba96f2539c979626cc80c5/yarn.lock#L1565 Not sure if a rebuild or some...
3yr ago `loadOptions: {xyz: {workerUrl: ...}}` should have worked, e.g., https://github.com/visgl/loaders.gl/issues/999 .. EDIT: Maybe not - the issue reported the workaround helped, but did not confirm`workerUrl` worked . Workaround may...
We were able to update just the `loader.gl/*` dependencies and that was enough for `{arrow: {CDA: null}}` to do the trick It still seems like, by default, an unusual thing...
i'm unclear what problem this solves? rgcn for link prediction that handles both node+edge attrs and node+edge classes? or for ER, how would this line up with a real dataset...
awesome -- * CI seems to fail? * Are there tests we can port in? * FEP would need to be able to call w/out passing in column names, can...
@aucahuasi on that note... CHANGELOG :)
https://github.com/graphistry/pygraphistry/pull/548 is landing, may help w/ CI fails
LGTM! Want to try going through the release flow in the develop.md?
https://github.com/graphistry/pygraphistry/pull/548 is landing, should solve CI fail where are we on this?