When we have 2 queries that have a falsy queryKey and each has an initialData set then the second one ignores the initialData set and takes the data of the first query as it's data.
I reproduce the issue here
CodeSandBox example

Describe the bug

It looks like this assignment to bc.size is dead (bc is a local variable which does not escape, and the field is not read anywhere).

To Reproduce

I found this issue using static analysis, so I cannot provide reproduction steps. I think this pr

Right now query in the nodejs api is just a string. we should support gql-parsed strings too, so that if they are exported elsewhere, it can be used directly.

import gql from 'graphql-tag';

export const GRAPHQL_QUERY=gql`
  query {
    something {
      anotherthing
    }
  }
`;

I'm not sure how feasible this may be, but the old logparser program from Microsoft supported queries like

Select * from test.csv

And it would read from test.csv, without needing any config files.

URL: http://pumpkindb.org/doc/master

Upon initial load, all documentation pages are scrolled down just a tiny bit, but it makes a bad initial impression (feels messy). Has something to do with the gitbook theme we're using, I suppose. When pages are changed by clicking on menu items, there is no such issue because subsequent navigation is done over AJAX.

![screenshot 2017-04-22 15 2

I recently checked the alerts of our cluster and some of them would never fire,
as the value we wanted to be alerted for, was not exported.

I tackled it by adding an alert that fires on "absent" values:
expr: absent(up{job="myjob"})

Might it be helpful to include information about this issue in general?

Hey :)

A quick question. In the useQueryParams example we have:

const [query, setQuery] = useQueryParams({
    x: NumberParam,
    q: StringParam,
    filters: ArrayParam,
  });
  const { x: num, q: searchQuery, filters = [] } = query;

setQuery(
            { x: Math.random(), filters: [...filters, 'foo'], q: 'bar' },
            'push'
          )

And the question is

The documentation seems fairly limited. Looking for a way to execute a "WHERE EXISTS" or "WHERE NOT EXISTS" type query.

Is the recommendation to extend pypika to include it or is there a way to custom write part of the query?

Not seeing much documentation on extending the module.

Introduction

This is a proposal for adding more explicit and extensive, and even ASCII art inspired support for set algebra in openCypher.

In my opinion sets of graphs is a once-in-a-lifetime opportunity that is much more than a revival: Doing set algebra on sets of graphs is potentially several orders of magnitude more powerful than SQL-based set algebra (or the simple lists etc. offered

Feature request: In an ORM I used to use in my former life, there was an alternative to .on for joins that was called .with. Basically, what it did was take the original join conditions, and add another condition to it using AND. I found this to be extremely helpful, as part of the reasons why

add as a gitbook plugin

Minor issue with "Example usage" curl command in comments of /cmd/sbserver/main.go. The url being evaluated should be appended with [PLATFORM]/[THREAT TYPE]/[THEAT ENTRY TYPE]. Working example:

$ curl \
  -H "Content-Type: application/json" \
  -X POST -d '{
      "threatInfo": {
          "threatTypes":      ["UNWANTED_SOFTWARE", "MALWARE"],
          "platformTypes":    ["ANY_PLATFORM"],
 

To help users unfamiliar with SMW to find features and supplementary functions which are normally not enabled by default, I created [0] as starting point.

I would appreciate if some people from the community find the time to finalize and complete the list.

Tasks

• Identify features and supplementary functions
  • SMWSearch
• Add separate summary sections to the smw@wiki

I suggest an attribute in the bot overview, which displays if the bot is currently in use or rather currently playing something, so if you use multiple bots its easier to see which bot is the one you want to control.

In this picture I added "Current Song" into the table via Firefox Source Edit.

The has-key(obj, 'x') should be equivalent to

is-object($o) and contains("key", $o)

On a first glance it may seems that just .x checks for the existence of key x but

• what if . is an array
• what if . contains key x but the value is null or a falsy value