#EventSetInformation error
43 messages · Page 1 of 1 (latest)
did you do what i asked you to here #1344650798428061717 message ?
I think that post was deleted
yes
wait
not fixed
can you share the output of tauri info of the system you built the app on?
i can't seem to reproduce it on my end anymore but will try again tomorrow
[✔] Environment
- OS: Windows 10.0.26100 x86_64 (X64)
✔ WebView2: 133.0.3065.92
✔ MSVC: Visual Studio Community 2022
✔ rustc: 1.77.2 (25ef9e3d8 2024-04-09)
✔ cargo: 1.77.2 (e52e36006 2024-03-26)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: 1.77.2-x86_64-pc-windows-msvc (default)
- node: 20.18.0
- yarn: 1.22.22
- npm: 11.0.0
- bun: 1.2.4
- deno: deno 2.1.4
[-] Packages
- tauri 🦀: 2.3.1
- tauri-build 🦀: 2.0.6
- wry 🦀: 0.50.1
- tao 🦀: 0.32.7
[-] Plugins
- tauri-plugin-shell 🦀: 2.2.0
- tauri-plugin-opener 🦀: 2.2.5
- tauri-plugin-updater 🦀: 2.5.1
- tauri-plugin-dialog 🦀: 2.2.0
- tauri-plugin-log 🦀: 2.2.2
- tauri-plugin-fs 🦀: 2.2.0
- tauri-plugin-os 🦀: 2.2.0
- tauri-plugin-single-instance 🦀: 2.2.2
[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../dist
- devUrl: http://localhost:1420/
okay it should be one of the plugins. tried to reproduce it without them first with no issues, then when i added them i got an error (a different one than you but close enough). will continue investigating later
the updater seems to be one of the offenders for me (now i really have to leave tho)
another error in another system
yeah, i've seen this one as well. it's probably a race condition between that one and the one above.
i can't seem to reproduce the EventSetInformation error though 🤔
🫠
Is there anything we can do to fix it for now since some of my users have Windows 7?
you could try running cargo update -p tempfile --precise 3.15.0 that should get rid of the processprng
i couldn't reproduce EventSetInformation with latest tao though so no idea where that one comes from
How about bcrypt?
read the error again. The bcrypt error mentions ProcessPrng == my first message
Oh sorry 🫠
Not fixed :}
which error are you seeing afterwards. still the bcrypt one?
yes bcrypt
I downgrade all of these:
tempfile: unknown → 3.15.0
getrandom: 0.3.1 → 0.2.15
uuid: unknown → 1.12.1
can you share the dependencies part of your cargo.toml file?
i feel like i'm missing a dependency here
@cinder void sorry for mention 🫠
i changed the reqwest dependency to ```toml
reqwest = { version = "0.12", default-features = false, features = [
"json",
"rustls-tls",
] }
but afterwards i didn't see any warnings either
i don't have the payload_macro dependency though in case that has os dependencies as well
ah no wait, i forgot to use the crates in the code 🤦♂️
@hot flax did i already ask if your project is public? i already spent much more time than windows 7 is worth on this 🙃
No, unfortunately, it's not public.
Oh sorry
Payload macro is
use proc_macro::TokenStream;
use quote::quote;
use syn::{parse_macro_input, Item};
#[proc_macro_attribute]
pub fn payload(_attr: TokenStream, item: TokenStream) -> TokenStream {
let input: Item = parse_macro_input!(item as Item);
let expanded: proc_macro2::TokenStream = match input {
Item::Struct(input_struct) => {
quote! {
#[derive(Serialize, Deserialize, Debug)]
#input_struct
}
}
Item::Enum(input_enum) => {
quote! {
#[derive(Serialize, Deserialize, Debug)]
#input_enum
}
}
_ => {
return syn::Error::new_spanned(
input,
"Payload can only be used with structs or enums",
)
.to_compile_error()
.into();
}
};
TokenStream::from(expanded)
}
I'll let you know the result in a few days. Thank you so much for your guidance!
thanks. if it's just that then that should be irrelevant
Also this is its cargo.toml if needed
[package]
name = "payload_macro"
version = "0.1.0"
edition = "2021"
[dependencies]
serde = { version = "1", features = ["derive"] }
proc-macro2 = "1.0.86"
quote = "1.0.37"
syn = "2.0.77"
[lib]
proc-macro = true
And for EventSetInformation user must do this? https://github.com/tauri-apps/tauri/issues/5163
yeah, if you still see the error with all tauri deps on latest versions then this should be the issue
It's better not to make this post too long on an unrelated topic and instead create a separate post for this.