rejuvenile

@havasd If I execute the builds in quick succession (e.g. within a half hour) zero items are rebuilt, even with `--stamp`. The value of the `--stamp` flag doesn't affect that...

In my own project (which uses `all_crate_deps`) I can repro. with `bazel test -c opt //... --nowatchfs --nostamp && sleep 3600 && bazel test -c opt //... --nowatchfs --nostamp`. Simply...

Perhaps unrelatedly, when building with --nowatchfs, I can get into a state where the following symlinks are recreated 100% of the time: ``` Executing action 'BazelWorkspaceStatusAction stable-status.txt': unconditional execution is...

@havasd That was the first thing I tried. I still repros even without any workspace status.

This may not be helpful, as I don't know `rules_rust` very well, but it looks like a certain set of files are always marked as changed, possibly when they shouldn't...

During the spurious rebuilds we also see: ``` 250421 15:12:54.747:I 7793 [com.google.devtools.build.lib.skyframe.SequencedSkyframeExecutor.detectModifiedOutputFiles] Found 2506 modified files from last build ```

Note, I do use `stamp = 1` in one of my Rust libraries, because otherwise it doesn't seem possible to include any of my `:rustc_env.txt` files in the build process,...

Note, when I add "main" back into the configuration, I get a similar error: ``` 2025-03-12T20:26:31.168589Z ERROR nativelink_service::bytestream_server: error: status: Internal, message: "'instance_name' not configured for 'bytestream://:50051/main'", details: [], metadata:...

I have not seen a repeat since toolchain issues resolved.

Alas, I still see this, even with a correctly configured toolchain: ``` 2025-03-12T20:12:54.727079Z ERROR nativelink_service::bytestream_server: error: status: InvalidArgument, message: "Expected WriteRequest struct in stream : In ByteStreamServer::write", details: [], metadata:...