-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More graceful handling of full documents errors #467
Comments
Is that from adding logs to a job? if so, maybe the logs should be split out into 1 doc per log entry |
Maybe. but why are apps making so many logs in the first place? do they really need to? If we do want so many log lines, why can users only see 10k logs in the job browser? Whats the point of keeping them if the user cannot even see them (unless they are calling the job logs api) and the causes the browser to crash to attempt to load in so many log lines. Not exactly related, but in addition, I think that logs should expire after some time as well like they do on github actions. |
If we're talking about completely redoing logs, then yeah, I would drastically change stuff. Most of the app logs are not fit for human consumption (especially not user consumption)
|
|
This spams the logs and makes the logs less useful.
The text was updated successfully, but these errors were encountered: