Yes, the example shows setting the current tenant id to all ones and then performing a select revealing a tenant id of all twos.
The same result is displayed in another example when correctly using a tenant id of all twos. A mistake perhaps of wrong output with the wording in the article is all.
I've been capturing a list of GitHub Actions gotchas;
1. If you reference an environment in a build step, this causes an `on: deployment` event trigger. This is not intuitive.
2. Environments with deployment protection rules are just for branches. Using tagged releases for a production environment means we must allow all branches to be deployed to that environment.
3. Workflows are unable to start other workflows to prevent cyclic actions. Understandable, there are exceptions however e.g (1) above.
4. Pull requests raised by Dependabot will not have the `id-token: write` permission needed to create an OIDC ID token that we use to access external systems (the benefit of then not having to manage secrets). Note: Using `on: pull_request_target` will be granted the permission but then you're executing the `main` branch and not building/testing the Dependabot changes.
Then we have secrets, Organisation, Repository, Environment and Dependabot.
Anything in Organisation, Repository or Dependabot should really be at most read only permissions. Environment based secrets may have write permissions but be wary of the malicious PR that then references this environment, what protections are in place? Environment approval? Deployment branch protection?
I'm still waiting to get Buzz enabled so I'm not sure on this, but is there an option for per 'buzz' use of location data? I could see good use for the odd occasion of "meet me here" message with the data added. Even better if it knew the recipients location and they could be provided with a route on how to get there!
I do not like long variable names and believe it is a combination of good commenting and inference through the code, that one should understand the role of the variable.
I was taught camel case for everything, which I don't agree with. Camel case for class names, everything else lower case, short and separated with underscores if needed. Collections are plural, e.g addresses, so that one can be generic in iteration and talk of an 'address'.
'sandbox' is organised by language, with code snippets and small projects in each folder. If anything becomes of the small projects they migrate to the 'projects' folder. Anything in the projects folder means it must be in a repository, git or svn.
The article on [1] rumours pricing, costing €20 per month for roaming on HSDPA. One just has to wait until it is released to find out I guess, but I too look forward to seeing the device being launched in Europe/UK.
The same result is displayed in another example when correctly using a tenant id of all twos. A mistake perhaps of wrong output with the wording in the article is all.