Build error

[orhun]

Hey, maintainer of ratatui here! 👋🏼

I originally wanted to give this a try a while ago but it got lost in time. Now I'm checking this out and hit a build error:

    Updating crates.io index
    Updating crates.io index
    Updating git repository `https://github.com/servo/stylo`
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 5 (delta 0), reused 4 (delta 0), pack-reused 0 (from 0)
Unpacking objects: 100% (5/5), 7.73 KiB | 879.00 KiB/s, done.
From https://github.com/servo/stylo
   35e0fa29e..098f1bef3  2024-12-04 -> origin/2024-12-04
    Updating git repository `https://github.com/servo/surfman`
error: failed to select a version for `unicode-bidi`.
    ... required by package `layout_2020 v0.0.1 (/home/orhun/gh/servo/components/layout_2020)`
    ... which satisfies path dependency `layout` (locked to 0.0.1) of package `layout_thread_2020 v0.0.1 (/home/orhun/gh/servo/components/layout_th
read_2020)`
    ... which satisfies path dependency `layout_thread_2020` (locked to 0.0.1) of package `libservo v0.0.1 (/home/orhun/gh/servo/components/servo)`
    ... which satisfies git dependency `libservo` (locked to 0.0.1) of package `cuervo v0.1.0 (/home/orhun/gh/cuervo)`
versions that meet the requirements `^0.3.17` are: 0.3.17

all possible versions conflict with previously selected packages.

  previously selected package `unicode-bidi v0.3.15`
    ... which satisfies dependency `unicode-bidi = "^0.3"` (locked to 0.3.15) of package `style v0.0.1 (https://github.com/servo/stylo?branch=2024-
12-04#098f1bef)`
    ... which satisfies git dependency `style` of package `libservo v0.0.1 (/home/orhun/gh/servo/components/servo)`
    ... which satisfies git dependency `libservo` (locked to 0.0.1) of package `cuervo v0.1.0 (/home/orhun/gh/cuervo)`

failed to select a version for `unicode-bidi` which could resolve this conflict

I'm not sure why some dependencies are pinned to specific commits so I thought it would be best to report it here. I will look into fixing this soon and I appreciate some help!

[orhun]

Ok got this compiling by removing Cargo.lock and retrying but hit a new error now:

error[E0599]: no function or associated item named `new` found for struct `js::jsapi::HandleValueArray` in the current scope
   --> /home/orhun/gh/servo/components/script/dom/bindings/proxyhandler.rs:489:35
    |
489 |         &jsapi::HandleValueArray::new(),
    |                                   ^^^ function or associated item not found in `HandleValueArray`

[mcclure]

Thanks, let me test this on my own. To clarify some things:

• The reason why some of the dependencies are pinned to specific commits is that I forked Servo to make this work. No other reason.
• I'm using an unusual .cargo/config.toml locally, so I might not have tested the checked-in version adequately before publishing. I think I have some time to look at this today so I'll test from a fresh checkout and see if I can fix it to work out of box.

[mcclure]

Hi, I ran some tests today and here's what I found:

1. As described in the README, this does not build unless you create a .cargo/config.toml containing at least:

    [env]
    RUSTC_BOOTSTRAP = "crown,script,style_tests"
   

   I believe more recent main-branch versions of Servo would not require this, but cuervo is based on a Sep 20 version of Servo so it does. However, in my testing on Ubuntu Linux 24.04 with Rust 1.83.0, this plus cargo build is all you need to build (the "unusual" config.toml keys I mentioned above weren't needed).

2. If you delete Cargo.lock, it just doesn't build. Doesn't matter which config.toml keys you're using, it just doesn't build. Apparently one of the dependencies needs a specific version and it is not fully reflected in Cargo.toml.

I'm not sure why you're seeing the specific error with failing to select a version. If you weren't doing so before, I'd suggest trying deleting target/, resetting Cargo.lock to the version in the repo, and building with the config.toml contents above in this post.

If that doesn't work, I think what would make the most sense is for me to just rebase my Servo changes on top of the current Servo HEAD, so that everything can be using the newest versions of everything and an up-to-date Cargo.lock can be used. However, I don't think I'll have time to try that until say next weekend.

Thanks for giving the project a look.

(One other thing that would be helpful to know, by the way: What platform are you building on?)

[orhun]

Thanks for looking into this again!

The reason why some of the dependencies are pinned to specific commits is that I forked Servo to make this work.

I was more curious about why that was needed - e.g. what kind of patches did you need to apply? I'm trying to understand how this works :)

However, in my testing on Ubuntu Linux 24.04 with Rust 1.83.0, this plus cargo build is all you need to build

To make sure I have that configuration and the Rust version pinned, I created #2 and #3. I also tried with a clean target folder.

However, unfortunately I'm still unable to build :/ Getting the same error:

error: failed to select a version for `unicode-bidi`.
    ... required by package `layout_2020 v0.0.1 (/home/orhun/gh/servo/components/layout_2020)`
    ... which satisfies path dependency `layout` (locked to 0.0.1) of package `layout_thread_2020 v0.0.1 (/home/orhun/gh/servo/components/layout_th
read_2020)`
    ... which satisfies path dependency `layout_thread_2020` (locked to 0.0.1) of package `libservo v0.0.1 (/home/orhun/gh/servo/components/servo)`
    ... which satisfies git dependency `libservo` (locked to 0.0.1) of package `cuervo v0.1.0 (/home/orhun/gh/cuervo)`
versions that meet the requirements `^0.3.17` are: 0.3.17

all possible versions conflict with previously selected packages.

  previously selected package `unicode-bidi v0.3.15`
    ... which satisfies dependency `unicode-bidi = "^0.3"` (locked to 0.3.15) of package `style v0.0.1 (https://github.com/servo/stylo?branch=2024-
12-04#098f1bef)`
    ... which satisfies git dependency `style` of package `libservo v0.0.1 (/home/orhun/gh/servo/components/servo)`
    ... which satisfies git dependency `libservo` (locked to 0.0.1) of package `cuervo v0.1.0 (/home/orhun/gh/cuervo)`

failed to select a version for `unicode-bidi` which could resolve this conflict

One other thing that would be helpful to know, by the way: What platform are you building on?

Arch Linux with rustc 1.83.0 (90b35a623 2024-11-26) and I have libunwind package installed as mentioned in README.md

so that everything can be using the newest versions of everything and an up-to-date Cargo.lock can be used. However, I don't think I'll have time to try that until say next weekend.

That would be nice 🙏🏼 I would be also happy to help if I had more context about what kind of changes in servo are necessary for this.

Thanks for giving the project a look.

Of course! Thanks for building it, I'm very interested in getting this to work :)

[mcclure]

Hello @orhun .

Sorry for the long (1 month…) delay. I finally got to look seriously at Cuervo this weekend. I merged my Servo changes with current (2025-Jan-9) Servo, and updated Cuervo to the new embedding API. I tested by checking out a new fresh git checkout (I think this excludes error caused by my "weird" local package setup). Testing in Debian Testing (Trixie) with rust 1.86.0-nightly (I cannot build servo without nightly because of Crown— it doesn't seem to matter which nightly, it just has to be nightly), I was able to successfully run Cuervo. My test steps were:

• Check out a fresh Cuervo, branch unstable_traversal_experiment. The commit I got was e9625047eb and I believe cargo is downloading mcclure fork Servo revision c471443af.

• Place into .cargo/config.toml:

  [env]
  RUSTC_BOOTSTRAP = "crown,script,style_tests"
  

• cargo +nightly build

• cargo +nightly run 2> errors.txt

• On launch, enter CTRL+P

• Enter g

• Enter "https://example.com" and hit return

• Over the next few seconds, hit spacebar 1-2 times a second (on my system, moving the mouse in a circle also works)

• I see:

This is my first successful test with 2025-Jan-9-servo Cuervo, if you wait a few days there are a couple "quality of life" changes I would like to make to the proof of concept just to make the tests easier to run (removing the absurd requirement to pump spacebar,, scrolling, maybe printing errors at the bottom of the screen rather than splatting them to stderr). I have learned a lot about Ratatui in the last three months so I can do these things more easily now. (The deeper problems (most sites don't load, lines on web pages appear out of order!) I do not plan to solve in this pass because I believe the fix is to replace the "DOM exfiltration" method in the current POC with something less slapdash.)

Hope this helps, let me know if there are any problems. I should be able to solve problems with the current build much more easily than with the one I had one month ago.

[mcclure]

Okay, version ee8f2f0 is now in a MUCH nicer state and has improvements such as:

• Pages simply load, you don't have to mash the space bar
• Pages that update in stages will not erase themselves
• Some error messages on-screen
• Scrolling
• Better build instructions

Remember to use the branch unstable_traversal_experiments.

Known problems are voluminous and include:

• The basic means of exfiltrating the DOM is bad, and means text nodes come in out of order (which incidentally means hierarchal stuff like supporting markup/A tags is out of the question) and some pages don't render at all.
• The app requires nightly to build, requires a weird .config/cargo.toml hack to build, and requires the python-packaging debian package. All of these are because of features (crown, etc) that servo as an embedder does not benefit from; it would be good if Servo put some work into building correctly when included as a Cargo dependency instead of built with mach.
• Servo is rendering an entire pixel-based view into a buffer somewhere that cuervo never even looks at
• App sometimes just hangs while quitting?
• Possible to scroll off end of page
• Error messages emitted by Servo are not localized

I'm putting the project back aside for now. @orhun , if you could take a look and see if you can build with the new unstable_traversal_experiments branch that would be great; and if I could get help from the Servo project at some point with DOM exfiltration / building without "crown" I'd be super super appreciative.

[orhun]

Hey @mcclure, I was able to build & run successfully after your recent changes! As a next step, I will read the code a bit and play around. Thank you!

If you're also fine with it, I'm planning to mention cuervo in my upcoming talk at FOSDEM in 2 weeks. I think it is a nice experimentation to explore the bridge between web and terminal :)

if I could get help from the Servo project at some point with DOM exfiltration / building without "crown" I'd be super super appreciative.

I will do my best to bring more eyes to the project and hopefully we'll get some help.

Again, thank you for your awesome work on this!

[mcclure]

Sounds good! I am busy the next couple weeks but may come back by the Zulip with some more specific requests.

By the way if you mention Cuervo in your talk you should at least be aware of https://www.brow.sh/ (Firefox-based TUI browser, works in a weird way but very fully featured, annoyingly mouse-centric UI) and Carbonyl (Chrome-based, may be out of date).