We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We currently don't allow blank log lines to be stored.
However a lot of people emit blank console.log() and should be able to see the logs like as if they were running the job locally.
console.log()
Blank log lines should be persisted, and this Elixir.LightningWeb.RunChannel.Error error should no longer be experienced in the RunChannel:
#Ecto.Changeset<action: :insert, changes: %{timestamp: ~U[2025-02-07 09:32:16.249492Z], run: #Ecto.Changeset<action: :update, changes: %{}, errors: [], data: #Lightning.Run<>, valid?: true, ...>, source: "ADA", step_id: "162e723f-0fee-4ec8-b40b-8994fb50168d", run_id: "1fe6ee9a-046a-4af9-9471-ae7b7013dbea"}, errors: [message: {"can't be blank", [validation: :required]}], data: #Lightning.Invocation.LogLine<>, valid?: false, ...>
The text was updated successfully, but these errors were encountered:
Refactor log message handling to allow nil values and improve error v…
b447651
…alidation ``` console.log(); => new line console.log(''); => new line console.log(null); => null console.log(undefined); => new line ``` Closes #2914
stuartc
Successfully merging a pull request may close this issue.
Details
We currently don't allow blank log lines to be stored.
However a lot of people emit blank
console.log()
and should be able to see the logs like as if they were running the job locally.User acceptance criteria
Blank log lines should be persisted, and this Elixir.LightningWeb.RunChannel.Error error should no longer be experienced in the RunChannel:
The text was updated successfully, but these errors were encountered: