KeyError on serving exception #283
Labels
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: M-Labs/nac3#283
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When trying two standalone Urukuls (since I was trying suservo anyway) at the same time I got this (not all exception messages ported?)
Seems ValueError needs to be added to EXCEPTION_ID_LOOKUP in eh_artiq.rs and artiq/language/embedding_map.py.
comm_kernel has those:
Should also be kept consistent...
May I ask how can I reproduce this issue? I tried to reproduce the issue to see if this branch can help, but cannot seem to reproduce the issue by
artiq_sinata_tester -o urukuls
, with this change:without the modification the initialization seems will just stuck:
On what system? Obviously you need a device with a Urukul properly set up.
And I suspect the easiest way to reproduce this is simply to raise ValueError, without touching Urukul.
Thanks, I just tested in zeus using
artiq_sinara_tester -o urukuls
.Yes I think the reason the unmodified test is stuck is because I do not have an urukul device set up properly. The system stuck at
return self.bus.read()
.With the above mentioned modified code (which I tried to keep the as much original code as possible), and the modification below (another try):
the
ValueError
can be raised normally:Simply raising a
ValueError
directly also cannot reproduce the bug:gives:
Using what device db and what core device?
You need a device db for Kasli or Kasli-SoC, with the corresponding Urukul entries, and the core device hardware set up accordingly. KC705 and ZC706 do not support Urukul.