Stopped Working on 1.0.0-alpha.3 #59
Comments
|
I run the kv-example with debug-level again: |
|
Additionally |
|
@baer-devl thanks for sharing! I'll look into it as soon as I can |
|
@baer-devl I've added some more debugging around bootstrap, can you please retry with the latest master and send the debug logs again? Thanks! |
|
@daschl thanks for the response! Unfortunately I cannot run it in gdb to give you more information as I struggle to setup it correctly to find the correct libcouchbase.so.6 (which gdb is complaining about). Maybe you have an advice to solve this? However, when I run the same code with info|warn|error debugging levels, same result as previously- it stucks somewhere on full CPU thread. |
|
@baer-devl this is good info, looks like there is no bucket name associated after the callback is complete. Let me push another more defensive change |
|
Can you try on top of b2f8491 ? |
|
Output is as follows: |
|
@baer-devl ok looks like I need to reproduce this as close as possible. Can you provide some more info on:
|
|
Services:
|
|
@baer-devl did you create a user with the same name of the bucket? I think I could reproduce the issue if I also create a user of the same name as the bucket. Can you to verify try to create a user with a different name? |
|
@daschl sry that I missed this detail, yes I did! |
|
@baer-devl the access level should not make a difference, I think something is tripping it up with the same user name as the bucket name. I'll go look into it but for now I can unblock you I think if you use a different username than the bucket name. |
|
@daschl You are right thank you! If I use the user "test" I just created, it works! |
|
@baer-devl I'm looking into this with @avsej from the libcouchbase side, but what's going on is that during KV auth the server "auto-selects" a bucket if the user name is the same as the bucket name. This is for backwards compatibility with old clients, where we did not have RBAC. Back in the days we only had bucket-level credentials so it is a bit difficult to distinguish those cases. In any case the SDK should handle that so we are currently trying to figure out the root cause. |
|
@daschl Thanks for the info! |
|
Is it necessary to use different user than the bucket name with the latest release. We are trying to set up a sample code with rust to do performance comparison with vertx, go and rust. I am very newbie to rust and is thinking of using async api using warp to see the performance. |
|
@himanshumps I'm trying to fix the issue for the next release so that the user doesn't have to worry about it. |
|
Any updates on this @daschl |
|
@himanshumps I've recently pushed a alpha.4, can you try if it works there? |
|
The issue is still there with alpha 4 release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently tried to update from old alpha to newer on my project. Now I cant run it anymore as it will block on any operation I try.
To exclude that the issue comes from my project- i cloned the actual repository, change the login data for my actual Couchbase-Instance and try to run the example 'kv' with the very same result.
rustc 1.41.0 (5e1a79984 2020-01-27)
cargo 1.41.0 (626f0f40e 2019-12-03)
Community Edition 6.0.0 build 1693
Any Idea what is causing this Error?
The text was updated successfully, but these errors were encountered: