You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd guess that whatever is generating that data is pulling from multiple sources (LWG subgroup, and something else) and one entry wins at random. I'm not sure where that data comes from or where a fix should be. If anyone knows, please request a fix. Otherwise, is there a way to mitigate the constant thrashing here?
The text was updated successfully, but these errors were encountered:
A couple WG21 refs are trashing back and forth. It makes the commit history a mess. Lots of these, then often flips back next update:
6af3e58
Looks like it's coming from the auto-generated JSON:
https://wg21.link/index.json
If you curl it, it'll change back and forth every so often:
curl https://wg21.link/index.json | jq '.D2652R2,.D2572R1'
There's some extra data in there not used in specref. Will be this:
Or this:
I'd guess that whatever is generating that data is pulling from multiple sources (LWG subgroup, and something else) and one entry wins at random. I'm not sure where that data comes from or where a fix should be. If anyone knows, please request a fix. Otherwise, is there a way to mitigate the constant thrashing here?
The text was updated successfully, but these errors were encountered: