rga | R Google Analytics | Analytics library

The JOIN comes after the SELECT and before the WHERE

Could not reproduce your issue, there are three incremental snapshots in my resource group, it works on my side.

Try the code works for me:

You shouldn't be nesting multiple select elements within your parent select element. I believe you meant to use the element. From there, you can assign the respective values to the option value props.

COUNTIFS

A pretty lame solution, since as you get more items you have to manually add them in the orange table (Note: BBB333 isn't there.). The formula in F2 is:

You could take an object with Time as key for nested object which contains the counts of Labels.

The code that creates republishedShadowTopic looks fine. String created by this code should be the same as string literal "Lamp/actualUsername/rs", just look here.

I'm not an expert on Arduino, but as far as I know, string literals may be stored in read-only memory (in case of Arduino that would be flash memory, I guess).

Attempting to modify a string literal results is undefined behavior: they may be stored in read-only storage (such as .rodata) or combined with other string literals.

The reason why it works when you're using string literal could be its static storage duration.

String literals have static storage duration, and thus exist in memory for the life of the program.

On the other hand, your array has an automatic storage duration, which means it may be invalid after exiting current scope.

When you take a look here, you'll see that address of your string has been forwarded and stored right here.

After you exit scope inside this if statement:

if (device.connect(HOST_ADDRESS, const_cast(client_id.c_str())) == 0)

you can no longer rely on this pointer. I assume you will receive a message after you exit that if statement.

You can test my hypothesis very easily. Just make this array as static or global and check that it works. You should do the same with the first array, because you probably were lucky that it worked.

If you check the documentation for the MCF API you will find that the valid values for Max-results is a number between 1000 and 10000.

max-results

max-results=100 Optional. Maximum number of rows to include in this response. You can use this in combination with start-index to retrieve a subset of elements, or use it alone to restrict the number of returned elements, starting with the first. If max-results is not supplied, the query returns the default maximum of 1000 rows.

The Multi-Channel Funnels Reporting API returns a maximum of 10,000 rows per request, no matter how many you ask for. It can also return fewer rows than requested, if there aren't as many dimension segments as you expect. For instance, there are fewer than 300 possible values for mcf:medium, so when segmenting only by medium, you can't get more than 300 rows, even if you set max-results to a higher value.

You should be using nextLink in order to retrieve the next set of data if you have more then 10000 rows in your response.

Update: Out of curiosity I contacted Google Analytics API team. I thought it strange that you are getting more rows back then you should be based upon the documentation. This is the response I got back

To me it sounds like the developer needs to just shorten the date range to not get 500 server timeout. I don't know how he knows how many row's a query will return when he is getting a 500 response so I think there is a bit of confusion in his question still. As far as I know we have not changed the number of rows allowed in the response, but we still need to construct the full response on our side and sort, so if the number of rows is large and the CPU usage on the server is heavy during his request he will easily get a 500 timeout error.

That being said I have asked the Backend team if anything has changed about the 10k limit recently..

- google dev who shall not be named -

The componentDidMount lifecycle method only runs after the first render. Therefore this.animatedValue will be undefined when the component first mounts.

You can declare the animated value as an instance property on the component, so that it will be available from when the component is first created.