There are two different things mentioned here, which I feel I need to clarify:
First, what you said about merging / creating a PR with broken tests. Absolutely you shouldn't do that, because you should only merge once the feature is finished. If a test doesn't work, then either it's testing for the wrong aspect and should be rewritten, or the functionality doesn't work 100% yet, so the feature isn't ready to get merged. Even if you're waiting for some other feature to get ready, because you need to integrate it or something, you're still waiting, so the feature isn't ready.
At the same time, the OP's point about tests being supposed to fail at first isn't too far off the mark either, because that's precisely how TDD works. If you're applying that philosophy (which I personally condone), then that's exactly what you do: Write the test first, checking for expected behaviour (which is taken from the specification), which will obviously fail, and only then write the code implementing that behaviour.
But, even then, that failing test should be contained to e.g. the feature branch you're working on, never going in a PR while it's still failing.
Once that feature has been merged, then yes, the test should never fail again, because that indicates a new change having sabotaged some area of that feature. Even if the new feature is considered "essential" or "high priority" while the old feature is not, ignoring the failure is one of the easiest ways to build up technical debt, so you should damn well fix that now.
Isn't the copyright specifically for the recordings/streams the league produces? I don't actually know if it's illegal to offer a stream using your own camera. Almost certainly against stadium rules, but as you said, they shouldn't be able to claim copyright in that case.
I've never used Mercurial, but a simple one based on the explanations and my experience with Git:
Locating the branch a commit originated from.
If a git branch has been merged into (or rebased on) main or another branch, there's no way to tell which commit came from which branch. But sometimes I'd really like that information to figure out what prompted a certain change. Without it, I need to use external tools like a ticketing system and hope the other developers added in the necessary information.
Ich kann an der Stelle zumindest teilweise relaten:
Ich war in einer Verteilerliste drin, die einem die Möglichkeit gibt, eine tägliche Zusammenfassung statt lauter einzelner Mails zu erhalten. Aber mein Mail-Client hat dann wohl die Mail für zu lang befunden und nur einen Teil davon angezeigt und den Rest abgeschnitten (vielleicht als Spam-Schutz oder so, keine Ahnung). Man hatte aber auch einen sehr offensichtlichen Button, um sich die komplette Mail anzeigen zu lassen. Vielleicht hat ihr Mail-Client ja etwas ähnliches gemacht und dort war der Button dann nicht so offensichtlich?
how about forcing LaLiga to show evidence about damages? Because surely everyone who pirated their content would have paid if free streams weren't available, right guys???
Das stimmt, deswegen lassen wir uns mittlerweile auch kaum noch breit reden. Entweder man hat die nötigen Voraussetzungen oder man bekommt keinen Termin.
Teilweise schlicht und einfach für den Lerneffekt. Jeder meint, man müsste ja nicht mehr lernen, weil man das ja schon alles kann, also gib mir gefälligst einen Termin. Wenn man dann ca. 70€ für einen neuen Versuch bezahlen muss, dann werden (meistens) ganz kleine Brötchen gebacken.
Außerdem kann ich mich nicht erinnern, wann wir das letzte Mal einen Schüler mit gerade mal 70% zugelassen haben (so wie der interviewte Fahrlehrer), mittlerweile fordern wir sogar meistens 97%.
I've got several hits, but none of them have permission to request my location. If I understand the README correctly, that should mean I'm safe, right?
I mean, they make me feel bad too, no question about it... But that's exactly why they're necessary.