-
Notifications
You must be signed in to change notification settings - Fork 87
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
CLI Generated sample program does not work #241
Comments
What error are you getting? |
Had same issue, updated Rust to 1.65.0 and worked. |
Ah, I see. That would be because Perseus relies internally on GATs, which were only stabilized in 1.65.0. I haven't updated the MSRV yet (since usually it's in line with Sycamore). Thanks for the report! |
@HBnetDE please let me know if updating to Rust v1.65.0 doesn't solve your issue. |
I am already at rust 1.65.
Errors produced by
|
Seems that you are getting the wrong wasm. On instructions when creating a new app you should write: instead of just: i guess is part of being in beta |
@enrand22 you're right that this looks like a Wasm problem, but not adding that extra flag shouldn't cause this. If that were the problem, you shouldn't be able to even get to compiling the app. @HBnetDE could you provide the outputs of |
|
Alright, your engine-side build is normal, but the Wasm build is completely broken. Are you using |
Yes, I am using rustup. My OS is Linux - Ubuntu 22.04. |
Same issue here. I'm using GitHub Workflows and build with Debian 11 based Docker. However, work fine in Windows 10 (all cli command,
FROM rust:slim AS build
ARG CLI_VERSION=0.4.0-beta.11
# -------------------- snip --------------------
RUN rustup toolchain install nightly
RUN rustup default nightly
RUN rustup update
RUN cargo install perseus-cli --version ${CLI_VERSION}
RUN perseus deploy
# -------------------- snip --------------------
# snip
[dependencies]
perseus = { git = "https://github.com/framesurge/perseus.git", features = [
"hydrate",
] }
sycamore = { version = "*", features = ["hydrate", "ssr"] }
[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
perseus-axum = { git = "https://github.com/framesurge/perseus.git", features = [
"dflt-server",
] }
tokio = { version = "*", features = ["macros", "rt", "rt-multi-thread"] }
[target.'cfg(target_arch = "wasm32")'.dependencies]
wasm-bindgen = "*"
wee_alloc = "*"
# snip workflows log:
with
|
@rieval as an aside: you should know that |
@rieval could you try with a usual crates.io dependency? The main branch has about 8 breaking changes on it right now, some relating to how error pages are handled, which could be causing your problem. I'm fairly certain these two problems are different though, so would you mind opening a separate issue? |
@HBnetDE can you try renaming |
I realized that it was really two different problems, and it was my fault. I tested [dependencies]
perseus = { version = "0.4.0-beta.11", features = ["hydrate"] }
serde = { version = "*", features = ["derive"] }
serde_json = "*"
sycamore = { version = "*", features = ["hydrate", "ssr"] }
[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
perseus-axum = { version = "0.4.0-beta.11", features = ["dflt-server"] } |
Oops! Thanks for letting me know. |
@rieval no problem, likely my fault, there are a lot of breaking changes on |
Output of
|
I really have no clue what could be causing this, sorry. I'm on Ubuntu 22.04 as well, and I'm not experiencing this issue. The output of Also, maybe run The only other thing I can think of right now is that you might have an override somewhere in |
It definitely isn't the missing target, since I can build and run sycamore on its own just fine. And yes it is definitely unmodified. I even deleted the app and recreated it before I opened the issue, just to be sure. I'll check the snoop and the override when I have time. |
That's weird because somehow |
This is why I thought about clearing the registry, in case there was an old version of Tokio doing weird things. Unless there's a new version of Tokio doing weird things? |
Hey, sorry it took so long! Here is the output of
I also double checked my Cargo.toml: [package]
name = "client"
version = "0.1.0"
edition = "2021"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
# Dependencies for the engine and the browser go here
[dependencies]
perseus = { version = "=0.4.0-beta.11" }
sycamore = "^0.8.1"
serde = { version = "1", features = [ "derive" ] }
serde_json = "1"
# Engine-only dependencies go here
[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
tokio = { version = "1", features = [ "macros", "rt", "rt-multi-thread" ] }
perseus-warp = { version = "=0.4.0-beta.11", features = [ "dflt-server" ] }
# Browser-only dependencies go here
[target.'cfg(target_arch = "wasm32")'.dependencies] |
No problem! Your |
@HBnetDE have you had any luck with this? There have been a few new beta versions over the last few weeks, so it might be worth trying those as well. |
@HBnetDE let me know if you're still experiencing this issue and I'll reopen. Closing for now. |
@arctic-hen7 Sorry it took me so long to get back to this. I just tried this with version 0.4.0-beta.17 and it's working now |
No problem, glad it's working! Let me know if you ever figure out what the problem was! |
It seems I was experiencing this same issue when the crate was included in my workspace with other crates, but when it wasn't, it was fine. I added |
Ah yes @El-Wumbus I've had the same problem myself a few times! Pretty sure that was in the FAQs at some point, but I'm not sure if it still is. |
This issue is reporting a bug in the code of Perseus. Details of the scope will be available in issue labels.
The author described their issue as follows:
The steps to reproduce this issue are as follows:
A minimum reproducible example is available at <>.
Tribble internal data
dHJpYmJsZS1yZXBvcnRlZCxDLWJ1ZyxBLWNsaQ==
The text was updated successfully, but these errors were encountered: