github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-15 18:12:14 -05:00
Code Issues 479 Packages Projects Releases 83 Wiki Activity

[GH-ISSUE #1054] Error "no method named set found" When Compiling diesel_migrations During Build #13534

New Issue
Closed
opened 2026-04-23 05:09:38 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-23 05:09:38 -05:00
Owner
Copy Link

Originally created by @nezartarbin on GitHub (Jul 10, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1054

Subject of the issue

I pulled the latest from master and attempted to build by running:
cargo build --features postgresql --release

But I ran into this error around the end. I was able to resolve the issue by checking out v1.15.x and building that instead, but thought I would report the issue just in case.

Your environment

  • Bitwarden_rs version: latest in master
  • Install method: build from source
  • Clients used:
  • Reverse proxy and version:
  • Version of mysql/postgresql:
  • Other relevant information:

Steps to reproduce

clone the latest from master, run cargo clean && cargo build --features postgresql --release

Expected behaviour

Should build correctly

Actual behaviour

It did not build and instead produced the error logs below

Relevant logs

Compiling migrations_internals v1.4.1
   Compiling migrations_macros v1.4.2
   Compiling diesel_migrations v1.4.0
   Compiling rocket_contrib v0.5.0-dev (https://github.com/SergioBenitez/Rocket?rev=1010f6a2a88fac899dec0cd2f642156908038a53#1010f6a2)
error[E0599]: no method named `set` found for struct `diesel::query_builder::InsertStatement<db::schema::users_collections::table, diesel::pg::upsert::on_conflict_clause::OnConflictValues<diesel::query_builder::ValuesClause<(diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::user_uuid, diesel::expression::bound::Bound<diesel::sql_types::Text, &str>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::collection_uuid, diesel::expression::bound::Bound<diesel::sql_types::Text, &str>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::read_only, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::hide_passwords, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>), db::schema::users_collections::table>, diesel::pg::upsert::on_conflict_target::ConflictTarget<(db::schema::users_collections::columns::user_uuid, db::schema::users_collections::columns::collection_uuid)>, diesel::pg::upsert::on_conflict_actions::DoUpdate<diesel::query_builder::update_statement::changeset::Assign<db::schema::users_collections::columns::read_only, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>>>>` in the current scope
   --> src/db/models/collection.rs:231:14
    |
231 |             .set(users_collections::hide_passwords.eq(hide_passwords))
    |              ^^^ method not found in `diesel::query_builder::InsertStatement<db::schema::users_collections::table, diesel::pg::upsert::on_conflict_clause::OnConflictValues<diesel::query_builder::ValuesClause<(diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::user_uuid, diesel::expression::bound::Bound<diesel::sql_types::Text, &str>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::collection_uuid, diesel::expression::bound::Bound<diesel::sql_types::Text, &str>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::read_only, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::hide_passwords, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>), db::schema::users_collections::table>, diesel::pg::upsert::on_conflict_target::ConflictTarget<(db::schema::users_collections::columns::user_uuid, db::schema::users_collections::columns::collection_uuid)>, diesel::pg::upsert::on_conflict_actions::DoUpdate<diesel::query_builder::update_statement::changeset::Assign<db::schema::users_collections::columns::read_only, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>>>>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
error: could not compile `bitwarden_rs`.

To learn more, run the command again with --verbose.
Originally created by @nezartarbin on GitHub (Jul 10, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1054 <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unneccessary for your issue, feel free to remove them. Remember to hide/obfuscate personal and confidential information, such as names, global IP/DNS adresses and especially passwords, if neccessary. --> ### Subject of the issue <!-- Describe your issue here.--> I pulled the latest from master and attempted to build by running: `cargo build --features postgresql --release` But I ran into this error around the end. I was able to resolve the issue by checking out v1.15.x and building that instead, but thought I would report the issue just in case. ### Your environment <!-- The version number, obtained from the logs or the admin page --> * Bitwarden_rs version: latest in master <!-- How the server was installed: Docker image / package / built from source --> * Install method: build from source * Clients used: <!-- if applicable --> * Reverse proxy and version: <!-- if applicable --> * Version of mysql/postgresql: <!-- if applicable --> * Other relevant information: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start bitwarden_rs? --> clone the latest from master, run `cargo clean && cargo build --features postgresql --release` ### Expected behaviour <!-- Tell us what should happen --> Should build correctly ### Actual behaviour <!-- Tell us what happens instead --> It did not build and instead produced the error logs below ### Relevant logs <!-- Share some logfiles, screenshots or output of relevant programs with us. --> ``` Compiling migrations_internals v1.4.1 Compiling migrations_macros v1.4.2 Compiling diesel_migrations v1.4.0 Compiling rocket_contrib v0.5.0-dev (https://github.com/SergioBenitez/Rocket?rev=1010f6a2a88fac899dec0cd2f642156908038a53#1010f6a2) error[E0599]: no method named `set` found for struct `diesel::query_builder::InsertStatement<db::schema::users_collections::table, diesel::pg::upsert::on_conflict_clause::OnConflictValues<diesel::query_builder::ValuesClause<(diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::user_uuid, diesel::expression::bound::Bound<diesel::sql_types::Text, &str>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::collection_uuid, diesel::expression::bound::Bound<diesel::sql_types::Text, &str>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::read_only, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::hide_passwords, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>), db::schema::users_collections::table>, diesel::pg::upsert::on_conflict_target::ConflictTarget<(db::schema::users_collections::columns::user_uuid, db::schema::users_collections::columns::collection_uuid)>, diesel::pg::upsert::on_conflict_actions::DoUpdate<diesel::query_builder::update_statement::changeset::Assign<db::schema::users_collections::columns::read_only, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>>>>` in the current scope --> src/db/models/collection.rs:231:14 | 231 | .set(users_collections::hide_passwords.eq(hide_passwords)) | ^^^ method not found in `diesel::query_builder::InsertStatement<db::schema::users_collections::table, diesel::pg::upsert::on_conflict_clause::OnConflictValues<diesel::query_builder::ValuesClause<(diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::user_uuid, diesel::expression::bound::Bound<diesel::sql_types::Text, &str>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::collection_uuid, diesel::expression::bound::Bound<diesel::sql_types::Text, &str>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::read_only, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>, diesel::insertable::ColumnInsertValue<db::schema::users_collections::columns::hide_passwords, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>), db::schema::users_collections::table>, diesel::pg::upsert::on_conflict_target::ConflictTarget<(db::schema::users_collections::columns::user_uuid, db::schema::users_collections::columns::collection_uuid)>, diesel::pg::upsert::on_conflict_actions::DoUpdate<diesel::query_builder::update_statement::changeset::Assign<db::schema::users_collections::columns::read_only, diesel::expression::bound::Bound<diesel::sql_types::Bool, bool>>>>>` error: aborting due to previous error For more information about this error, try `rustc --explain E0599`. error: could not compile `bitwarden_rs`. To learn more, run the command again with --verbose. ```
GiteaMirror commented 2026-04-23 05:09:39 -05:00
Author
Owner
Copy Link

@jjlin commented on GitHub (Jul 11, 2020):

Sorry, my mistake. I thought CI would've caught this error.

<!-- gh-comment-id:656948670 --> @jjlin commented on GitHub (Jul 11, 2020): Sorry, my mistake. I thought CI would've caught this error.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#13534
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?