projects | Runtime Evironment library

I don't know if I understood your question, but this is what the code is doing:

var_list is a list with two elements [100, 2025].

slice1 and slice2 are being defined as (var_list + [None]*2)[:2]. This expression adds the var_list to a new list of 2 None objects ([None] * 2 == [None, None]). The result of this expression ((var_list + [None] *2)) is the addition of these 2 lists, which is: [100, 2025, None, None]

Then the last part ([:2]) is just slicing the first 2 elements of this resulting list and assigning it to the variables. And since, in this case, the first 2 items are the var_list itself, it will assign the first element to slice1 and the second to slice2.

I haven't come across such a ConcurrentCounter library, but crates.io is huge, maybe you find something. However, if you are mostly concerned with primitives such as i32, there is a better alternative call: Atomics, definitely worth checking out.

Nevertheless, your approach of generalizing the ConcurrentCounter is going in a good direction. In the context of operation overloading, std::ops is worth a look. Specifically, you need Add, Sub, and Mul, respectively. Also, you need a Copy bound (alternatively, a Clone would also do). So you were pretty close:

The error messages states that the service account does not have the permission compute.disks.list.

What permissions does the role roles/resourcemanager.organizationViewer have?

Put everything in an object.

This way the 2 defs that depends on each other will be available at the same time.

IntelliJ worksheets do not like such definitions as they are "evaluated" one by one. You cannot define 2 depending on one the other at the top-level, they need to be encapsulated.

Yes you're using 3 times the same function, so we sure can do better. Here is a first simple idea, make a loop on the tree elements :

JAVASCRIPT

The version 202.7660.26.42.7322048 is

Upgrade your dagger-hilt dependencies to the same version.

Your project's root gradle file

classpath "com.google.dagger:hilt-android-gradle-plugin:2.31.2-alpha"

Your app level gradle file

implementation "com.google.dagger:hilt-android:2.31.2-alpha"

kapt "com.google.dagger:hilt-android-compiler:2.31.2-alpha"

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.

Just do that and you will be fine (all external classes will be excluded):