Update to a more recent rocket and rust toolchain #205
レビューアなし
ラベル
ラベルなし
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
マイルストーンなし
プロジェクトなし
担当者なし
2 人の参加者
通知
期日
期日は未設定です。
依存関係
依存関係が設定されていません。
リファレンス: Plume/Plume#205
読み込み中…
Add table
新しいイシューから参照
説明はありません。
ブランチ "recent_rocket" の削除
ブランチの削除は恒久的です。 実際に削除されるまでの短い期間、ブランチが存在したままになることもありますが、たいていは元に戻すことはできません。 続行しますか?
So, I have made some progress tonight, but unfortunately, this has become way more complicated than initially expected. The main reason is pretty simple: rocket has introduced some serious breaking changes related to the
Uri
type, and I am not familiar enough unfortunately to fix them easily.I push this so you folks can have a look, maybe with enough familiarity this is trivial to fix.
Beware that this PR uses my forks of
rocket_{i18n,csrf}
. They are basically working, AFAICT at least, but I wanted to have a working Plume before creating PR there.So, yeah. TL;DR: I tried and failed, but maybe what I achieved will help you?
To do before merging:
rocket_i18n
rocket_csrf
So yeah, I just want to emphasize once again, just to be clear, that this is meant to be temporary, until my changes (or equivalent changes) are pushed to the rightful upstream.
Related commits:
rocket_i18n
::b9bd6b9674
rocket_csrf
::9828be7546
(cc @fdb-hiroshima)Thanks a lot for your help! Looks like a lot of errors are happening because of
56c6a96f6a
, so adding.into()
afteruri!
invocations should fix it.I will try to do that, if that’s okay with you.
Yes, of course! If you have any question about the code, you know you can ask me 😉
I’ve pushed a new commit that fixes the remaining errors. There remains a lot of warnings, though.
Some warnings are due to a change in
rustc
that affectsdiesel
. The crate has already been updated, but not released.@lthms Could you please use the git repository directly in the Cargo.toml then, with a pinned
rev
? We will go back to a stable version once it will be released.I think the PR of interest is https://github.com/diesel-rs/diesel/pull/1787
So we need to depend on at least this revision. Unfortunately, I don't know if there are pending issues in current
diesel
master
branch, so I have to admit I am not sure which revision to choose…Another solution could be to ignore these warnings for the moment… https://github.com/rust-lang/crates.io/pull/1469/files
Once https://github.com/fdb-hiroshima/rocket_csrf/pull/1 is merged, I will update
Cargo.toml
to use the upstreamrocket_csrf
, squash my commits and I think it will be okay, at least from my side.From my perspective, this PR is now ready. I don’t think I have broken something, but I guess you never know :D.