pip25

This behavior still looks very much like a bug to me compared to what's described in the JDBC API. If the `getTables` method receives a catalog name it cannot support...

Good point, I was so preoccupied with not wanting to make even bigger breaking changes that I forgot that this already is one. XD Edited the PR and the commit...

@davecramer As mentioned in #2947, while the driver can only return data for the catalog the connection refers to, this is not enforced in the metadata API at all. Instead,...

Perhaps not everything is retrieved at once, but the runtime and especially the converted application code is still downloaded in huge chunks, a whole multi-megabyte JAR at a time, potentially...

We experienced the same problem, and I can confirm that the issue is due to an older Node version. The 1.1.1 version of gulp-order ran fine on Node 5.7, 1.2.0...

I think it might have been an accidental oversight on our part (but the codebase is old, so it's hard to say). We upgraded our dependencies to the latest Node...

@brainlulz I simply changed the Node/NPM version (this was a Maven build that automatically installs the required Node and NPM versions into the workspace), ran the build again and it...

Here's a screenshot using a slightly modified StackBlitz example from the official site that illustrates the issue: 

I've already created a bug (#128), but I added a screenshot to it just now to illustrate the problem.

If anyone runs into this issue, I'd suggest ignoring the bot's above ramblings. A quick look at the source code shows that the __async_add_nodes_to_index_ function is a near copy-paste of...