Bazel splits the build into multiple phases. Starlark only comes into play in the first two, load and analysis. During these phases, Starlark code doesn't have access to the filesystem, except in a few very limited cases like using the glob() function to expand a wildcard to a list of source files. Furthermore, it only generates an abstract graph of build actions. The Bazel engine is responsible for executing this graph in later stages, which might result in non-hermetic things happening but usually not.
Starlark has intentionally limited functionality such as lacking Turing completeness or global variables. This provides guarantees that it can be executed in parallel and will have a finite runtime.
I've seen a Model 3 with very similar sounds coming from the passenger side mirror. There was a loose piece sticking out of the bottom, pushing it back in fixed it.
I assume that both parties have market research showing that enough people (maybe even 36%) don't care enough to figure out how to change the search engine or buy a different phone.
It's price discrimination. Some airline users are not price sensitive (the wealthy, corporate travelers with expense accounts) and they don't care about getting maximum value for their dollar. Economy fliers do.
> Rent control: A random windfall for whatever tenant snags these coveted apartments when someone dies in a 3 bedroom apartment they haven't needed in 30 years but "can't afford" to downsize from since they have been paying $650 since 1989. Also the illegal subletters who are numerous and shameless, from personal experience.
This is a misrepresentation of SF rent control. Rent increases for pre-1979 apartments are only capped if the same tenant lives there continuously -- when the apartment lease turns over, the rent can be raised to market rates.
That being said, there are some people that abuse the system by keeping a lease for a place they haven't lived in for 20 years and subletting it, sometimes for a profit, but there aren't apartments where the rent is permanently capped at 80s levels like you're suggesting.
That's... not a cartel though? A cartel is a group of firms conspiring to artificially control the supply of some good in order to increase its price, what you described is just several independent firms that have a high demand for workers and are bidding up salaries for them.
It was more cartel-like when Apple and Google were conspiring to keep tech salaries down by setting salary caps.
The people that this broke weren't directly depending on the output of git archive being stable, but were assuming that the response data for a particular URL would stay constant. Maybe not a great idea either but not entirely unreasonable IMO.
The setup instructions for almost [1] every [2] major [3] rule set [4] only provide one (GitHub) url in the Starlark blob you're supposed to copy and paste, so hard to blame users here.
At the limit, the exchange would only redeem it at par if Tether the company can also do so, right? That's the big open question since Tether has never publicly completed an audit.
So I guess the only future-proof solution to check for this is to render user input off screen and count the number of solid pixels, at least until "falsehoods programmers believe about names" gets updated to include "Names must consist of at least one readable glyph".
By not having test cases for those specific domains, and by passing your input through some general purpose internal URL handling library that does more than you thought it did [1]. Neither is (very) surprising.
Because this is in Canada, where they aren't bound by US Supreme Court decisions? Also I don't think straight white cis-male is a protected class in any case.
Starlark has intentionally limited functionality such as lacking Turing completeness or global variables. This provides guarantees that it can be executed in parallel and will have a finite runtime.