Skip to content

Allow "results" to be uploaded after task run #1086

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

Closed
brendo opened this issue Sep 25, 2024 · 5 comments
Closed

Allow "results" to be uploaded after task run #1086

brendo opened this issue Sep 25, 2024 · 5 comments
Labels
enhancement New feature or request stale

Comments

@brendo
Copy link

brendo commented Sep 25, 2024

Our application has a few maintenance tasks which iterate over a collection and then upload a CSV with the results of the task. This is implemented using the after_start/after_complete/after_error callbacks and by flushing to a CSV after each iteration.

What would be neat is if this feature was baked into the gem by default, and the results uploaded was all handled by ActiveStorage and stored on the run model. This would mean that viewing past runs would be able to surface a deep-link to this "results" file.

Is this something that PR's would be accepted for?

@brendo brendo added the enhancement New feature or request label Sep 25, 2024
Copy link

This issue has been marked as stale because it has not been commented on in two months.
Please reply in order to keep the issue open. Otherwise, it will close in 14 days.
Thank you for contributing!

@github-actions github-actions bot added the stale label Nov 25, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 9, 2024
@brendo brendo reopened this Dec 11, 2024
@github-actions github-actions bot removed the stale label Dec 12, 2024
@kylefox
Copy link

kylefox commented Jan 7, 2025

Came to suggest something like this as well. It would be extremely helpful to record the result of a process operation in some way.

Copy link

github-actions bot commented Mar 9, 2025

This issue has been marked as stale because it has not been commented on in two months.
Please reply in order to keep the issue open. Otherwise, it will close in 14 days.
Thank you for contributing!

@github-actions github-actions bot added the stale label Mar 9, 2025
@larouxn larouxn removed the stale label Mar 9, 2025
Copy link

github-actions bot commented May 9, 2025

This issue has been marked as stale because it has not been commented on in two months.
Please reply in order to keep the issue open. Otherwise, it will close in 14 days.
Thank you for contributing!

@github-actions github-actions bot added the stale label May 9, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2025
@larouxn
Copy link
Contributor

larouxn commented May 23, 2025

This issue should probably be reopened. It's tracking a clearly desirable feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

3 participants