A server with no Log tracer has no files for the Logs page to read, and every installer setup starts that way. The query failed with invalidArguments, which the list showed as a bare word, followed by the generic "No log entries yet" (reported on the forum, t/232).
The Logs page now says the log is going to the system journal, gives the journalctl and docker compose logs commands, and links to Tracers to add a Log tracer. Lists in general show the server's description of an error rather than its type (listErrorOf), and skip the empty state while the list couldn't be read. The installer side, which adds a Log tracer, is inbuxa-installer#70.
A server with no Log tracer has no files for the Logs page to read, and every installer setup starts that way. The query failed with `invalidArguments`, which the list showed as a bare word, followed by the generic "No log entries yet" (reported on the forum, t/232).
The Logs page now says the log is going to the system journal, gives the `journalctl` and `docker compose logs` commands, and links to Tracers to add a Log tracer. Lists in general show the server's description of an error rather than its type (`listErrorOf`), and skip the empty state while the list couldn't be read. The installer side, which adds a Log tracer, is inbuxa-installer#70.
Fixes #217
A server with no Log tracer has no files for the Logs page to read,
and every installer setup starts that way. The query failed with
"invalidArguments", which the list showed as a bare word, followed by
the generic "No log entries yet. When one is added, it shows up here."
The Logs page now says the log is going to the system journal, gives
the commands to follow it, and links to Tracers to add a Log tracer.
Lists in general show the server's description of an error rather
than its type, and no empty state while the list couldn't be read.
Fixes#217
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 server with no Log tracer has no files for the Logs page to read, and every installer setup starts that way. The query failed with
invalidArguments, which the list showed as a bare word, followed by the generic "No log entries yet" (reported on the forum, t/232).The Logs page now says the log is going to the system journal, gives the
journalctlanddocker compose logscommands, and links to Tracers to add a Log tracer. Lists in general show the server's description of an error rather than its type (listErrorOf), and skip the empty state while the list couldn't be read. The installer side, which adds a Log tracer, is inbuxa-installer#70.Fixes #217