teaching | Teaching Resources for Cuemacro courses | Machine Learning library

I will suggests you change the code to:

Short answer: It was previously 30 minutes per execution, but it is now unclear if it's being reduced from 30 mins/execution to 6 mins/execution or if Google's documentation is just wrong or incomplete.

In the current quotas documentation, there is no explicit mention of quotas for Enterprise (or the equivalent new editions such as the "Teaching and Learning Upgrade") except under the umbrella term "Google Workspace".

Here, the quota is "6 mins per execution" as in the old days.

One of the snapshots from the Wayback Machine shows the "well-known-but-now-no-longer-documented" fact that business customers had 30 mins per execution was removed from the documentation between December 2020 and January 2021, when the new editions were announced.

I (and others) can in fact still run new or existing App Scripts for up to 30 minutes with paid licenses. In my case, I have an "Enterprise for Education" license, which presumably translates into something equivalent in the new editions until it expires.

However, ominously, there is the statement that quotas "...are subject to elimination, reduction, or change at any time, without notice".

It is entirely feasible that Google are in the process of reducing the current 30 minute / execution quota and the documentation is preceding the change.

It is equally feasible that Google have not updated their quotas page correctly since the launch of the new editions.

Therefore, there is no clear answer since we may be in the middle of a change (as per the documentation) or the documentation may just be incorrect.

Array broadcasting in 3 dimensions is pretty tricky to wrap your head around.

lets start with 2 dimensions:

char filename[8]; does not initialize the array, so there is no guarantee that it contains any zero bytes. You must initialize array to zero by using = {} or = "".

Also, 4 bytes is not enough to store ".txt" or "2020". You need 5 bytes so that you can also store the terminator, so char frmt[5] = ".txt";.

But now the rust compiler complains about the lack of a lifetime parameter for the returned reference in the type specifier of cell_access:

The problem here, as I understand it, is that in order to be able to write the code in this shape, the cell_access function's signature needs to refer to the lifetime for which it is valid, and this is impossible because that lifetime doesn't have a name — it's a local reborrow of self that's implicit in the closure creation. Your attempt with &'a mut self doesn't work because it doesn't capture the fact that the closure's self is a reborrow of the function's self and accordingly does not need to live exactly the same lifetime, since mutable borrows' lifetimes are invariant rather than covariant; they can't be arbitrarily taken as shorter (because that would break the exclusiveness of mutable references).

That last point gives me an idea for how to fix this: move the all_in_line code into a function which takes self by immutable reference. This compiles:

This is easier to accomplish with the Stream api that was introduced in Java 8:

This should now be handled in the development version of Tweepy on the master branch by automatically attempting to reconnect. The underlying connection error is likely due to falling too far behind in the stream when processing Tweets. For now, you can attempt to reduce the processing within on_status, handle the error by restarting the stream, wait for Tweepy v4.0, or use the development version of Tweepy.

For more context, see https://github.com/tweepy/tweepy/issues/237 and https://github.com/tweepy/tweepy/issues/448.

You have only one data state that is only ever reduced through searching/filtering, so when you backspace and assume more results should be added back in, they can't since previous setData calls wiped them out.

Use two pieces of state, one to represent the source of truth and the second for search results. Always use the source of truth for searching, update the results.