lmeyerov

Moving docs to 2.41

Hi @jacob-parnell-rozetta we recently started using https://aws-sdk-pandas.readthedocs.io/en/stable/tutorials/033%20-%20Amazon%20Neptune.html for some other Neptune work, which gets you a dataframe that you can drop into regular pygraphistry calls + @DataBoyTX who is more...

Is there any update on the right patterns to cancel chains? This is an architectural need at multiple levels: * When langchain is managing an LLM stream, or running a...

We should support multiple spark versions, sounds like impacts potentially these: * Spark availability sniffing: https://github.com/graphistry/pygraphistry/blob/2506b798ec723e906c1c5279f613fe0c37bdbad2/graphistry/PlotterBase.py#L80 * Dispatch: https://github.com/graphistry/pygraphistry/blob/2506b798ec723e906c1c5279f613fe0c37bdbad2/graphistry/PlotterBase.py#L1682 * Arrow coercion: https://github.com/graphistry/pygraphistry/blob/2506b798ec723e906c1c5279f613fe0c37bdbad2/graphistry/PlotterBase.py#L1901

I'll do some quick research Agreed, can be a fun one for @mj3cheun

OK confirmed, looking like a straightforward streamgl-viz backend fix

Some examples we see: 1. Data ingestion: We get some annoying formats like excel files and more niche ones that we do dask jobs to turn into dataframes, and then...

Thanks. I was starting to get to that conclusion as the current happy path based on the slack conv. Doing some reworking here to be closer to that, I'm guessing...

Interim update: blazingsql context creation is getting wedged when combining `dask-worker --resources CPU=1` and `dask-cuda-worker --resources GPU=1` (despite the happy case of single node / single gpu / sequential test)....

@ibgreen @igorDykhta Any ideas? This breaks most F500 & gov scenarios that we see