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

v4.0.2RC fails when accessing input in druid #483

Closed
beels opened this issue May 13, 2023 · 2 comments
Closed

v4.0.2RC fails when accessing input in druid #483

beels opened this issue May 13, 2023 · 2 comments

Comments

@beels
Copy link
Contributor

beels commented May 13, 2023

First a couple of notes on the release: Like others, when I install relaase 4.0.2 (via fledge or via dfu-util) crow reports in druid that it is running v4.0.1-14-g7721314, not v4.0.2. I note that github has a 4.0.2RC tag, but no actual 4.0.2 tag. 4.0.2RC contains a commit that does bytecode cross-compilation, but does not contain the i2c fixes in commit 34166ec.

The issue I see is: if I connect to crow running v4.0.1-14-etc via druid I get the following response if I try to access the inputs:

//// druid. q to quit. h for help

 <crow connected>
 <listening at ws://localhost:6666>
> print(input[1].volts)
?:-1: attempt to call a nil value (field 'io_get_input')
stack traceback:
  ?: in function <?:44>
  (...tail calls...)
  repl:1: in main chunk
runtime error.

If I do not try to interact with the DAC, things seem to work fine. I haven't attempted to use any of the v4 functionality, though.

This crow is serial number 0x002e00133756501420383558.

I am running druid 1.1.4 under python 3.8 on Windows.

@discohead
Copy link
Contributor

same issue here. downgrading to v4.0.1 makes this go away.

@trentgill
Copy link
Collaborator

fixed in 4.0.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants