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.

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

Can't build code depending on bluer = "0.10.2" #6

Closed
laszlourszuly opened this issue Jul 16, 2021 · 3 comments
Closed

Can't build code depending on bluer = "0.10.2" #6

laszlourszuly opened this issue Jul 16, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@laszlourszuly
Copy link

laszlourszuly commented Jul 16, 2021

Gentlemen!

I'm seeing "no method named try_read_buf found" issues when building my code, having included a dependency to bluer 0.10.2 (please find my config and build output with exact error message below).

I'm not trying to manually build the bluer library, but rather consume it from crates.io (i guess).

I do have a bit aged version of Bluez on my system (5.53 I believe), but I'm not convinced this is the real issue at this stage as I'm experiencing build issues rather than runtime issues.


Development environment:

  • Ubuntu 20.04
  • bluez 5.53-0ubuntu3.3
  • libdbus-1-dev 1.12.16-2ubuntu2.1
  • cargo 1.53.0 (4369396ce 2021-04-27)
  • rustc 1.53.0 (53cb7b09b 2021-06-17)

Cargo.toml:

[package]
name = "hello"
version = "0.0.1-snapshot"
edition = "2018"

[dependencies]
bluer = "0.10.2"

The critical part of cargo build output:

   Compiling bluer v0.10.2
error[E0599]: no method named `try_read_buf` found for struct `tokio::net::UnixStream` in the current scope
   --> /home/monster/.cargo/registry/src/github.com-1ecc6299db9ec823/bluer-0.10.2/src/gatt/mod.rs:134:29
    |
134 |         let n = self.stream.try_read_buf(&mut buf)?;
    |                             ^^^^^^^^^^^^ help: there is an associated function with a similar name: `try_read`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
error: could not compile `bluer`
@laszlourszuly
Copy link
Author

I think I would qualify as a seasoned developer (15+ years in the business) but I am new to Rust, so I am humble to the possibility that the issue is a misconfiguration on my end.

Basically I'm wondering if this is a known issue and if you have any pointers on how i could get around it?

@surban
Copy link
Collaborator

surban commented Jul 18, 2021

In fact we were missing a dependency crate feature and due to how Cargo works it does not show up as an error in CI.

It should be fixed in version 0.10.3.

@surban surban self-assigned this Jul 18, 2021
@surban surban added the bug Something isn't working label Jul 18, 2021
@laszlourszuly
Copy link
Author

laszlourszuly commented Jul 19, 2021

Thank you for your quick actions! I can confirm it working with version 0.10.3. Closing this issue (feel free to re-open if you need it for internal processes etc)

otaviojr added a commit to otaviojr/bluer that referenced this issue May 10, 2023
# This is the 1st commit message:

BLE Passive Scanning

# This is the commit message #2:

monitor

# This is the commit message bluez#3:

monitor

# This is the commit message bluez#4:

monitor

# This is the commit message bluez#5:

monitor

# This is the commit message bluez#6:

monitor

# This is the commit message bluez#7:

monitor

# This is the commit message bluez#8:

monitor

# This is the commit message bluez#9:

monitor

# This is the commit message bluez#10:

monitor

# This is the commit message bluez#11:

monitor

# This is the commit message bluez#12:

monitor

# This is the commit message bluez#13:

monitor

# This is the commit message bluez#14:

monitor

# This is the commit message bluez#15:

monitor

# This is the commit message bluez#16:

monitor

# This is the commit message bluez#17:

monitor

# This is the commit message bluez#18:

monitor

# This is the commit message bluez#19:

monitor

# This is the commit message bluez#20:

monitor

# This is the commit message bluez#21:

monitor

# This is the commit message bluez#22:

monitor

# This is the commit message bluez#23:

monitor

# This is the commit message bluez#24:

monitor

# This is the commit message bluez#25:

monitor

# This is the commit message bluez#26:

monitor

# This is the commit message bluez#27:

monitor

# This is the commit message bluez#28:

monitor

# This is the commit message bluez#29:

monitor

# This is the commit message bluez#30:

monitor

# This is the commit message bluez#31:

monitor

# This is the commit message bluez#32:

monitor

# This is the commit message bluez#33:

monitor

# This is the commit message bluez#34:

monitor

# This is the commit message bluez#35:

monitor

# This is the commit message bluez#36:

monitor

# This is the commit message bluez#37:

monitor

# This is the commit message bluez#38:

monitor

# This is the commit message bluez#39:

monitor

# This is the commit message bluez#40:

monitor

# This is the commit message bluez#41:

monitor

# This is the commit message bluez#42:

monitor

# This is the commit message bluez#43:

monitor

# This is the commit message bluez#44:

monitor

# This is the commit message bluez#45:

monitor

# This is the commit message bluez#46:

monitor

# This is the commit message bluez#47:

monitor

# This is the commit message bluez#48:

monitor

# This is the commit message bluez#49:

monitor

# This is the commit message bluez#50:

monitor

# This is the commit message bluez#51:

monitor

# This is the commit message bluez#52:

monitor

# This is the commit message bluez#53:

monitor

# This is the commit message bluez#54:

monitor

# This is the commit message bluez#55:

monitor

# This is the commit message bluez#56:

monitor

# This is the commit message bluez#57:

monitor

# This is the commit message bluez#58:

monitor

# This is the commit message bluez#59:

monitor

# This is the commit message bluez#60:

monitor

# This is the commit message bluez#61:

monitor

# This is the commit message bluez#62:

monitor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants