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

CLI Errors during Dataset Upload: Axios Error and CPU Kernel Panic #21

Open
artyaltanzaya opened this issue Aug 9, 2023 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@artyaltanzaya
Copy link

artyaltanzaya commented Aug 9, 2023

Environment:

  • OS: macOS with M1 Max
  • Command: roboflow import ./"foldername"

Description:

While attempting to upload a large dataset using the CLI, I encountered two distinct problems:

  1. Axios Error:
node: internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise *);
AxiosError: read ECONNRESET
at TLSWrap. onStreamRead (node: internal/stream_base_commons:217:20) {
syscall: 'read' code: 'ECONNRESET', errno: -54,

  1. CPU Kernel Panic: After reducing the value for the -c option and allowing the process to run for around 6 minutes, my Mac shuts down with an error indicating a CPU kernel panic. Here's the related error message:

panic(cpu 1 caller 0xfffffe002a74da4c): Spinlock[0xfffffe24cb9b5be8]

This panic effectively limits the number of images I can upload to around 5000.

Steps to Reproduce:

  1. Run the command roboflow import ./"foldername"
  2. Observe the Axios error, or, if that error does not occur,
  3. Reduce the -c option value and observe the CPU kernel panic after approximately 6 minutes of operation.

Expected Results:

The CLI should successfully upload the dataset without causing any errors or system shutdowns.

Actual Results:

Two distinct errors are encountered: an Axios error that requires further investigation and a CPU kernel panic that causes a system shutdown.

Additional Context:

Understanding the best practices for uploading large datasets to the platform would be beneficial, as current limitations are posing challenges for clients with significant amounts of data.

Attachments:

Screenshot 2023-08-07 at 1 16 55 PM
Screenshot 2023-08-07 at 11 39 28 AM

@artyaltanzaya artyaltanzaya added the bug Something isn't working label Aug 9, 2023
@artyaltanzaya artyaltanzaya self-assigned this Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants