Skip to content
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

Busy job crashes UI #1624

Open
djalan opened this issue Dec 13, 2024 · 3 comments
Open

Busy job crashes UI #1624

djalan opened this issue Dec 13, 2024 · 3 comments
Labels

Comments

@djalan
Copy link
Contributor

djalan commented Dec 13, 2024

Hello

I upgraded to Dkron 4.0.0 for Windows AMD64 and the UI crashes for Busy job when I try to expand the output. It used to work on version 3.7 for the same shell command line.

return (<div className="execution-output">{record.output || "Empty output"}</div>);

A quick fix would be the below. I opened this PR: #1625

record?.output

image

image

@djalan
Copy link
Contributor Author

djalan commented Dec 13, 2024

I tried running the following shell executor command lines and they all give the above error

  • python script with buffered output
    • python program.py
  • force the stdout and stderr streams to be unbuffered
    • python -u program.py
  • powershell
    • powershell ./script.ps1

@djalan
Copy link
Contributor Author

djalan commented Dec 13, 2024

LOAD FULL OUTPUT does not work either as per the below image.

I tried to show a python log, but it failed.
Showing the full output of the powershell script works.

It makes sense because record: t is probably undefined for this call too.

image

@vcastellm vcastellm added the bug label Dec 20, 2024
@djalan
Copy link
Contributor Author

djalan commented Dec 20, 2024

@vcastellm

Hello! I will make a sample repo next week because the problem seems deeper than just adding ? to record?.output to fix the Busy tab.

The variable record seems to just not exist in certain cases and that's why loading the full output in the Executions tab does not work either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants