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

Problem with adding entries after last update #30

Open
Flowy opened this issue Dec 28, 2023 · 2 comments
Open

Problem with adding entries after last update #30

Flowy opened this issue Dec 28, 2023 · 2 comments

Comments

@Flowy
Copy link

Flowy commented Dec 28, 2023

After last update, I started getting this error

1452x invalid key to 'next' [string "=[C]"]: in function next'
[string "@unitscan/unitscan.lua"]:270: in function `UPDATE'
[string "@unitscan/unitscan.lua"]:3: in function <unitscan/unitscan.lua:3>

Locals:
(*temporary) =

{
LIL TIMMY = true
GOBBLER = true
SEWER BEAST = true
GAZELE = true
}
(*temporary) = "MOTHER FANG"`

Its triggered when I'm changing zones, because I have WA that changes scanned names based on zone. The problem does not happen always, it depends on how many names there is to add.

Would it be possible to change the iteration so its not affected by latest updates, or use one that accepts removing/adding entries?

Also other option would be to allow public API, that would prevent the iteration from failing. Expected functions would be to read currently tracked, add, remove,
bonus function would be to add listener for when the name is triggered, and option to disable default announcement (sounds and visuals)

mentioned WA is this https://wago.io/Pyfd62ceG , its using direct table unitscan_targets as thats only public entry that you provide, it is triggered when changing zones, does not fail every time, but quite often, after fail unitscan keeps failing until reload or the original entries are added

@shirsig
Copy link
Owner

shirsig commented Dec 29, 2023

Is it fixed now?

@Flowy
Copy link
Author

Flowy commented Dec 29, 2023

Yes, seems to not throw errors now, thank you

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

2 participants