Comments (14)
Fixed with 0.4.33 in #1383. Thank you for reporting, and @jtmoon79 for investigating.
from chrono.
I could not find failed builds here on github under the Actions tab. But I did find this build failure at docs.rs
...
[INFO] [stderr] warning: Target filter specified, but no targets matched. This is a no-op
[INFO] [stderr] Checking rkyv v0.7.43
[INFO] [stderr] error: one of ["size_16", "size_32", or "size_64"] features must be enabled
[INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.43/src/macros.rs:114:1
[INFO] [stderr] |
[INFO] [stderr] 114 | core::compile_error!(r#"one of ["size_16", "size_32", or "size_64"] features must be enabled"#);
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]
[INFO] [stderr] error: cannot find macro `pick_size_type` in this scope
[INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.43/src/lib.rs:723:23
...
At first glance, this looks to be an rkyv oddity.
Tag #644 and @dovahcrow
from chrono.
Thanks @dovahcrow for following up too.
from chrono.
Thanks for fixing.
A small issue remains so:
All tests and builds are still failing at least according to the badge...
But I think there is something wrong with job naming and not the testing it self.
Since chrono is a very popular crate I think this isn't something that should left that way.
Even removing the badge is a better option.
from chrono.
That's from the main branch, whereas we mostly release from the 0.4.x branch. The badge should fix itself when we do our next merge from 0.4.x to main. Perhaps we should rename main to 0.5.x and keep 0.4.x as main?
from chrono.
I failed to reproduce locally. Here's what I ran:
cargo +nightly rustdoc --lib -Zrustdoc-map --features rkyv
.
Rust version: v1.77.0-nightly
Seems to me --no-default-features
is passed to rkyv somehow.
from chrono.
Would be better if the "landing page" is actually the current published version.
After all the same badges are also shown in the docs.
from chrono.
Perhaps we should rename main to 0.5.x and keep 0.4.x as main?
I'm all for it. We would have to change the target branch of all open PRs though.
from chrono.
I can't find the reason why the badge is still red but made an attempt in #1388.
Edit: still red because the latest merge is still running on the CI 😄.
from chrono.
Perhaps we should rename main to 0.5.x and keep 0.4.x as main?
I'm all for it. We would have to change the target branch of all open PRs though.
@djc I don't have permission, but it may just work when you rename the branches via the GitHub interface.
from chrono.
Done -- let's use #1390 to coordinate any necessary changes in the repo contents.
from chrono.
Should we yank 0.4.32?
from chrono.
Nah, it doesn't seem bad enough for that.
from chrono.
Nice 👍🏼
Looooks way better this way.
Thx for fixing it.
from chrono.
Related Issues (20)
- Version 0.4.36 has breaking changes with 0.4.35 HOT 2
- the trait bound `DateTime<Utc>: OptionFrom/ToWasmAbi` is not satisfied when targeting wasm32 HOT 3
- 0.5: Consider using smaller types for arguments
- Make Weekday::num_days_from public HOT 2
- Add a method to the `Offset` trait to return DST info HOT 5
- 0.5: Add a `LocalOffset` type HOT 4
- Verification of published packages HOT 2
- `gh-pages` branch HOT 3
- Releases has problematic naming of 0.4.8 release which puts it at the top HOT 3
- 0.4.37 semver-incompatibly removes trait bounds on `DateTime` HOT 10
- How do I get the raw underlying bytes of a `NaiveDate` HOT 4
- Parsing from string to DateTime - input is not enough for unique date and time HOT 3
- TimeDelta always returning a PT in seconds HOT 2
- NaiveDate::years_since wrong documentation
- Saturating operations HOT 9
- Datetime Parse Error when converting rfc2822 date to chrono Datetime HOT 2
- Extra slow Utc to Local conversion HOT 6
- Wasm support for NaiveTime, NaiveDate and alike HOT 2
- Bincode 2.0.0 support HOT 2
- Need Duration to Represent Time in Months/Years HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chrono.