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

6.0 Feedback: App side analysis failing when custom labware folder has many files #10960

Open
shlokamin opened this issue Jun 30, 2022 · 0 comments
Assignees
Labels
6.0-feedback Feedback for the 6.0 release

Comments

@shlokamin
Copy link
Member

shlokamin commented Jun 30, 2022

Overview

When the custom labware directory in app settings has many files, app side analysis fails with an opaque error of Maximum call stack exceeded.

Upon further investigation, I found that it came from this line of code in app-shell/src/protocol-analysis/index.ts :

  const auxLabwareDirContents = globby.sync(
    path.posix.join(getConfig().labware.directory, '**')
  )

The code above has been changed in the 6.0 release branch, but the replacement code still does not have a depth limit.

Since this seems like it might be something that a nontrivial amount of users might experience, we should evaluate adding a depth limit.

Also, it's worth noting this same error probably happens on the labware page in the app, because that page does the same logic to grab custom labware.

Current Behavior

App side analysis fails when custom labware dir has many files with an opaque error.

Expected Behavior

Not sure, but at the very least we should get a better error

Steps To Reproduce

In app settings, make your custom labware dir a folder that has many files. In my case, I had a ton of screenshots.

Operating system

No response

Robot setup or anything else?

No response

@shlokamin shlokamin added the 6.0-feedback Feedback for the 6.0 release label Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.0-feedback Feedback for the 6.0 release
Projects
None yet
Development

No branches or pull requests

3 participants