Skip to content

Sometimes the communication lock error is masked by a "no device configured" error #557

@ChucklesOnGitHub

Description

@ChucklesOnGitHub

Describe the Bug

Sometimes the communication lock error is masked by a "no device configured" error

To Reproduce

When encountering communication lock errors, sometimes a " no deviec with the specified name xxx has been configured" error shows up on top of the popup, "masking" the error, when the devices names are in fact properly specified.

Due to #556, it has become second nature to close the popup and attempt to start the worflow again, as this generally resolves it.

Image

Bonsai Version

2.9.0

OpenEphys.Onix1 Version

0.6.0

Attach your workflow

any wf

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions