Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use new Mozilla 'sandstone' visual style for rust-lang.org #2246

Closed
brson opened this issue Apr 19, 2012 · 3 comments
Closed

Use new Mozilla 'sandstone' visual style for rust-lang.org #2246

brson opened this issue Apr 19, 2012 · 3 comments
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one.

Comments

@brson
Copy link
Contributor

brson commented Apr 19, 2012

https://www.mozilla.org/b/en-US/sandstone/

They don't appear to provide any guidance on when this style should be used, but it is probably appropriate for rust-lang.org.
@bstrie
Copy link
Contributor

bstrie commented Apr 20, 2012

Noticed that the "page template" and "subpage template" download buttons on that page don't point to anything. Not sure where to report that... perhaps you could forward this information to the person in charge of that page?

@graydon
Copy link
Contributor

graydon commented Apr 20, 2012

Not sure I agree on this. I've been pretty intentional about positioning rust as a community that isn't necessarily a subset of mozilla's community. Lots of people have a stake in language development who don't participate in or necessarily care about the mozilla project.

@brson
Copy link
Contributor Author

brson commented Apr 20, 2012

@graydon Your point is persuasive.

@brson brson closed this as completed Apr 20, 2012
bors added a commit to rust-lang-ci/rust that referenced this issue Sep 22, 2022
@bors
Auto merge of rust-lang#2246 - dtolnay-contrib:rustfmt1, r=oli-obk
332f289 
Format tests with rustfmt (51-100 of 300)

Extracted from rust-lang#2097.

Like rust-lang#2244, this is intended to be "easy" cases which don't involve comments in the vicinity.
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@celinval
Remove glob to collect all artifacts introduced by cargo kani (rust-l…
ccec549 
…ang#2246)

This change allows us to pin-point exactly which build artifacts are related to a cargo build run. This is required to re-enable the build cache (rust-lang#2036) where multiple artifacts can co-exist in the same folder.

The solution implemented here is rather hacky, but it's more reliable than other alternatives I've tried (see model-checking/kani#2246). Now, `kani-compiler` will generate stubs in the place of binaries, shared, and static libraries when those types are requested. Those stubs will contain a JSON representation of the new type `CompilerArtifactStub`, which basically contain the path for the `metadata.json` file where the compiler stores the metadata related to a given crate.

`kani-driver` will parse `CompilerArtifact` messages to figure out which artifacts were built for the given build. For libraries, it will derive the name of the metadata file from the `rmeta` filepath. For other types of artifacts, it will parse the output file, convert it to `CompilerArtifactStub`, and extract the path for the `rmeta` filepath.
BoxyUwU pushed a commit to BoxyUwU/rust that referenced this issue Feb 25, 2025
@camelid
Merge pull request rust-lang#2246 from marxin/CI-more-ofter
34db7ba 
Run CI multiple times a day
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@graydon @brson @bstrie