A Stalwart 0.16 store lists upstream's web interface as an Application, so after an import inbuxa fetched it and served it at /admin.
Now, the first time inbuxa opens a store without its version mark, it switches that Application off, keeps the record, and logs how to switch it back on. The mark is written on the same start, so this happens once: an operator who switches it back on keeps it on. Applications of the operator's own aren't touched.
first_party.rs: disable_imported_web_interface, run from insert_safe_defaults before applications load
test imported_web_interface (tests/src/store_version.rs), plus a unit test for recognising the download
docs/spec/import-0.16.md: open question settled; SPEC.md §5.3 updated
import check: the web interface state is now pass/fail
Checked locally: store_version, imported_web_interface, renamed_identifiers (RocksDb), the common unit test, name and notice checks, cargo fmt --check.
Prod isn't affected: its copy was removed at cutover.
A Stalwart 0.16 store lists upstream's web interface as an Application, so after an import inbuxa fetched it and served it at `/admin`.
Now, the first time inbuxa opens a store without its version mark, it switches that Application off, keeps the record, and logs how to switch it back on. The mark is written on the same start, so this happens once: an operator who switches it back on keeps it on. Applications of the operator's own aren't touched.
- `first_party.rs`: `disable_imported_web_interface`, run from `insert_safe_defaults` before applications load
- test `imported_web_interface` (tests/src/store_version.rs), plus a unit test for recognising the download
- `docs/spec/import-0.16.md`: open question settled; SPEC.md §5.3 updated
- import check: the web interface state is now pass/fail
Checked locally: `store_version`, `imported_web_interface`, `renamed_identifiers` (RocksDb), the common unit test, name and notice checks, `cargo fmt --check`.
Prod isn't affected: its copy was removed at cutover.
A store brought over from Stalwart 0.16 lists upstream's web interface as
an Application, so inbuxa fetched it and served it at /admin. The first
time inbuxa opens a store without its version mark, it now switches that
Application off and keeps the record, logging how to switch it back on.
The mark written on the same start keeps this to once, so an operator who
wants the interface back keeps it. Other applications aren't touched.
Settles the open question in docs/spec/import-0.16.md; SPEC.md §5.3 and
the import check follow.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A Stalwart 0.16 store lists upstream's web interface as an Application, so after an import inbuxa fetched it and served it at
/admin.Now, the first time inbuxa opens a store without its version mark, it switches that Application off, keeps the record, and logs how to switch it back on. The mark is written on the same start, so this happens once: an operator who switches it back on keeps it on. Applications of the operator's own aren't touched.
first_party.rs:disable_imported_web_interface, run frominsert_safe_defaultsbefore applications loadimported_web_interface(tests/src/store_version.rs), plus a unit test for recognising the downloaddocs/spec/import-0.16.md: open question settled; SPEC.md §5.3 updatedChecked locally:
store_version,imported_web_interface,renamed_identifiers(RocksDb), the common unit test, name and notice checks,cargo fmt --check.Prod isn't affected: its copy was removed at cutover.