thread 'main' panicked at src/main.rs:3002:37: about angryoxide

[GobiasSomeCoffeeCo]

Did it only happen this once? And was the name of the AP "zEQQ3XJPK+30/+aP", or is there an AP with that name in your environment? I noticed that's the file name it errored out on. Which given the fact it contains a '+' and a '/' could be problematic for writing in a Linux file structure.

[jakkpotts]

No, it stays consistent and crashes every time I have it hopping a particular combo of 2 and 5 ghz band channels. Nothing visible in the environment with that AP name that I can see, I noticed that as well. I suspect it is a hidden AP on the 5 ghz band or perhaps something is happening in the buffer. I will do some more testing report back. Excellent utility btw On Mar 15, 2024, at 4:56 PM, Gobias ***@***.***> wrote: Did it only happen this once? And was the name of the AP "zEQQ3XJPK+30/+aP", or is there an AP with that name in your environment? I noticed that's the file name it errored out on. Which given the fact it contains a '+' and a '/' could be problematic for writing in a Linux file structure. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Ragnt]

Yeah, this is for sure because the AP has that SSID. I can add a check for illegal characters before attempting to write.

For now, as a workaround you can use --combine to not write separate files per-AP.

[Ragnt]

This should be fixed after the latest commit. You will have to build from source until the next release.

[GobiasSomeCoffeeCo]

A fix was just pushed to the master branch that should fix your issue. If you want, you can do git pull and then cargo b --release and let us know how it goes.

[jakkpotts]

This should be fixed after the latest commit. You will have to build from source until the next release.

yes, this solved the issue. thanks.