Nicholas Roberts
Nicholas Roberts
(Please excuse the PR re-lodge) As far as I can tell, the Options type is incapable of using params, so I've elected not to pass opt to astOptions (or astTableRef...
So I've been testing out serialising a query to the AST representation, it looks like there's a slight bug when _referencing_ params (serializing them is fine). So this works: `query().params({param1:...
So Actix added SSL a while back (marginal benefit really), and recently HTTP/2; I've confirmed that both work behind nginx (or whichever other reverse proxy you care to use), though...
Partly a follow-on from [#320](https://github.com/pola-rs/polars/issues/320). Currently IpcWriter uses the output of schema.to_arrow() (which in turn relies on DataType::to_arrow()). This is fine for unambiguous types, but not so great for those...
It would be nice to get this to work with cmake - more for the event insertion and nicer loading mechanism than the auto-recompile (given that even the linking step...
NB: Starting this a little earlier for design feedback on the object-store-wasm crate itself (primarily around ehttp vs reqwest). The usage is very straightforward (given all the plumbing is present...
Derived from the refactor branch, at the moment I've extended the file struct a bit for easy toggling between the two backing readers.
The interface for writing to streams so far is: ```typescript const table = wasm.readParquet(buf); const outputStream = wasm.writeParquetStream(table); // sink the contents somewhere useful, like to a server that supports...
TLDR: HEAD requests are the correct way to check content-length, but object stores (and overly restrictive policies) don't play nice. The problem: 1. Determine the content length of the target...
It would be worthwhile adding to the docs for firebase-messaging a warning about the timing of firebase.initializeApp - pretty much, if it's called *after* firebase-messaging fires its ready callback, nothing...