diff options
| author | Leitwolf11 | 2026-10-16 06:00:57 +0300 |
|---|---|---|
| committer | Leitwolf11 | 2026-10-16 06:00:57 +0300 |
| commit | bc653270652c1ab44d2144ddd17ae49b404e7cd2 (patch) | |
| tree | 2cc8867a56273c910d00855ac1eeac22fdee1bd6 /.github | |
| parent | 3877e3318e875cdebc3d7b9bc970b4496e5183a9 (diff) | |
| download | progmaweb-bc653270652c1ab44d2144ddd17ae49b404e7cd2.tar.gz | |
Return a failed Google callback to sign-in and correct stale statements
A Google callback that could not finish ended in an unhandled 500: a
visitor who declined on Google's consent screen, a callback whose state
cookie had expired, and a direct request to the callback path all got an
empty error page. The account API document already promised a redirect
to /login?google=failed for a failed callback; the handler of the Google
scheme now does that through OnRemoteFailure. Three new tests cover a
callback without state, a declined consent and a forged state.
Three statements no longer matched the sites:
- the bug report template still named the catalog paths without the
language and the build system; they are /langs/tala/<Publisher>/<Name>/
and /dslplugins/tazel/<Publisher>/<Name>/;
- the operations guide placed Tala content on xsharp-lang.xyz, which only
redirects to tala.run now;
- the architecture guide described the ViGet routing before the catalogs
per language and build system: it now gives the rewrites of /langs/tala
and /dslplugins/tazel, the redirects of /langs and /dslplugins, three
indexed ViGet pages and a sitemap with the home page and both catalogs.
Diffstat (limited to '.github')
| -rw-r--r-- | .github/ISSUE_TEMPLATE/bug_report.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 69d57bc..ace8b98 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -17,7 +17,7 @@ This repository owns `progmasoft.com`, `account.progmasoft.com`, and `viget.prog ### Observed and expected behavior -Describe what happened, what you expected, and any visible status code or safe error message. If the issue involves a package path, distinguish `/<Publisher>/<Name>/` ViPkgs from `/dslplugins/<Publisher>/<Name>/` JAR plugins; do not attach private packages. +Describe what happened, what you expected, and any visible status code or safe error message. If the issue involves a package path, distinguish `/langs/tala/<Publisher>/<Name>/` ViPkgs from `/dslplugins/tazel/<Publisher>/<Name>/` JAR plugins; do not attach private packages. ### Reproduction |