magical | MAGICAL benchmark suite for robust imitation learning | Reinforcement Learning library

This is extreme weird behaviour, and I dont really think github and slack are linked together somehow that magically remove APP as soon as its Token got exposed.

They are, though: https://docs.github.com/en/code-security/secret-security/about-secret-scanning

Secret scanning is a mechanism to do just that, detect accidentally leaked secrets in GitHub and report them to the affected service. There are 40+ partners already participating in this, including Slack.

GitHub scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.

Secret scanning is automatically enabled on public repositories. When you push to a public repository, GitHub scans the content of the commits for secrets. If you switch a private repository to public, GitHub scans the entire repository for secrets.

Probably intentionally publishing a live token to a public GitHub repo is a not the right approach, I'd recommend using a private repo instead.

You would need the template parameter from the method for SFINAE:

As far as I understood both your question and the Blazor concepts, the answer to your question is « no ». There is no possibility to retrieve statically the current HTTP context in Blazor. Because you never know if the context is an initial page load or just SignalR communication to update the current page. Here is the manner I save this situation:

• Create a cascading parameter that is shared by all razor components

• This cascading parameter is a class with many information coming from initial HTTP request, caught in the _Host.cshtml from the httpContextAccessor.HttpContext

• This cascading parameter class gets all the methods of my previous static methods.

• These methods can use the properties of the cascading parameter: RawUrl, UserAgent, ClientIp, …

This implies hard refactoring work to migrate legacy ASP web sites. But the performances of Blazor are worth it.

Here is a "direct" translation of the python code to ruby - note that the syntax is almost identical! (The only subtle differences are elif vs elsif and the print/puts syntax.)

Meson build here ; basically I have two "executable" target with a shared source, and it seems the first overlap the second for some reason although it should be sequentially.

Example :

In short - base C does not have support for this without macro trickery or libraries

If you are open to the two - you could use something homegrown like this:

From the question, I believe you have understood most of it so I'm not going to details about why this multi-loss architecture can be useful. I think the main part that has made you confused is why does "loss1" back-propagate through "B"? and the answer is: It doesn't. The fact is that loss1 is calculated using this formula:

Refer to the docs:

A stickily positioned element is an element whose computed position value is sticky. It's treated as relatively positioned until its containing block crosses a specified threshold (such as setting top to value other than auto) within its flow root (or the container it scrolls within), at which point it is treated as "stuck" until meeting the opposite edge of its containing block.

So your problem is not caused by td or div itself. It's because of their containing block:

If the position property is static, relative, or sticky, the containing block is formed by the edge of the content box of the nearest ancestor element that is either a block container (such as an inline-block, block, or list-item element) or establishes a formatting context (such as a table container, flex container, grid container, or the block container itself).

For sticky with the div inside td, it's clear that the containing block is its parent td(because td establishes a formatting context) so each div have its own containing block and will not be stacked.

For sticky with td, I haven't found any official document about containing block of td, only found this, so I'm not sure it's a tbody, table or the div that wrap the table. The only thing can be sure is all the td sharing the same containing block, that's why it's stacked.

There are two ways to bind collections when posting forms. One, which is what you are currently doing, is to use a sequential index that starts from 0 and increments by 1 for each element in the collection.

The other is to use an explicit index, which can be any value which it doesn't need to be sequential. It doesn't even need to be numeric. This approach requires an additional hidden field for each item, named [property].Index which represents index of the item.