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

Bug: Export Stuck at 0% #2264

Open
jb-cloud opened this issue Feb 27, 2023 · 0 comments
Open

Bug: Export Stuck at 0% #2264

jb-cloud opened this issue Feb 27, 2023 · 0 comments
Labels
C-bug Type: Bug

Comments

@jb-cloud
Copy link

Describe the bug
After clicking Export Data in the UI the button changes to Exporting 0%. After more than a day the Exporting 0% is still observed and a link is not created. Exporting has worked as expected before.

To Reproduce
I'm not certain how to reproduce this as it has worked previously and there is nothing interesting about this export.

Expected behavior
A link to download would appear after refreshing.

Screenshots
image

Platform (please complete the following information):

  • OS: macOS 13.2
  • Browser: Firefox 110.0 (64-bit)
  • Desktop
  • Spoke Version 12.2
  • Heroku Hosted

Additional context
Heroku with Bucketeer. The Bucketeer credentials are in both the AWS and Bucketeer env vars. That seemed a little odd, but this has worked like this in the past with the same vars.

The larger file of successful export would be ~63k rows. In Heroku I don't see any memory or load spikes.

image

JOBS_SAME_PROCESS=1

Accessing the bucket from the aws cli, I don't see any files with the name of this campaign.

After deleting the job from the job_request table and running FLUSHDB in redis, the button reappears in the UI, but clicking it produces the same result.

The name of the campaign contains a '/' which I think would be part of the export file name. I believe that would be problematic for aws bucket names, but not an individual file's name.

@jb-cloud jb-cloud added the C-bug Type: Bug label Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Type: Bug
Projects
None yet
Development

No branches or pull requests

1 participant