-
```
TEA Version?
1.2.0
SMF Version?
2.0 RC5
What steps will reproduce the problem?
1. Have a member that has 2 toons on their api.
2. 1 toon is blue to your alliance, another is in the alliance.
3.…
-
```
TEA Version?
1.2.0
SMF Version?
2.0 RC5
What steps will reproduce the problem?
1. Have a member that has 2 toons on their api.
2. 1 toon is blue to your alliance, another is in the alliance.
3.…
-
See https://github.com/the-blue-alliance/the-blue-alliance/pull/1389#issuecomment-225730626
Edit: Make sure different channel url patterns are supported properly.
-
Once we flip all writes to go through py3, we shouldn't need https://github.com/the-blue-alliance/the-blue-alliance/pull/3488 anymore
-
From https://github.com/the-blue-alliance/the-blue-alliance/pull/2339 - my guess is that `shasum` isn't outputting what I expect it to
-
**Is your feature request related to a problem? Please describe.**
Nope, just an enhancement.
**Describe the solution you'd like**
Add an "X" if no stages were activated.
**Additional context*…
-
This includes:
- YouTube Data APi
- The Blue Alliance read API
- The Blue Alliance trusted API
- FRC Events API
If one of these APIs is unavailable, we may need to fallback to a different API or paus…
-
These routes didn't get ported to py3. Should be an easy fix https://github.com/the-blue-alliance/the-blue-alliance/blob/3f45ed77a0bfcf170801300022b6981f76b54d16/main.py#L181-L182
-
We need to be able to pull data from Blue Alliance on one phone before we sync it to the rest (ie it gets passed off to #2). Note that this requires a Blue Alliance API key.
-
Post update tasks for `MatchManipulator` and `EventDetailsManipulator` have been timing out on GAE because they're taking over 30s+ and are causing things such as duplicate notifications to get sent. …