You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to use a bucket named test for testing. Couchbase appears fine, but running the test suite, anything that appears to initiate a connection to the datasource / query appears to segfault.
I haven't deduced whether it is the li3 adapter or the php couchbase lib itself. Just wanted to document in case anyone else runs into this.
In the meantime, I've renamed my test database to testdb
The text was updated successfully, but these errors were encountered:
Well, nothing in user land PHP is technically ever supposed to be able to segfault. Seems pretty likely to be the Couchbase lib. Have you looked to see if there are existing issues with certain bucket names in a broader PHP context, or in other Couchbase client libraries? Also, cc: @daschl.
Nate
On Friday, April 26, 2013 at 2:51 PM, Jon Adams wrote:
I wanted to use a bucket named test for testing. Couchbase appears fine, but running the test suite, anything that appears to initiate a connection to the datasource / query appears to segfault.
I haven't deduced whether it is the li3 adapter or the php couchbase lib itself. Just wanted to document in case anyone else runs into this.
In the meantime, I've renamed my test database to testdb
—
Reply to this email directly or view it on GitHub (#16).
which version of the extension are you using? a segfault is definitely inside the extension and not allowed to happen. Also, does it only happen when you use "test" as the name?
Let me know of these two things and then we can sort it out!
I wanted to use a bucket named
test
for testing. Couchbase appears fine, but running the test suite, anything that appears to initiate a connection to the datasource / query appears to segfault.I haven't deduced whether it is the li3 adapter or the php couchbase lib itself. Just wanted to document in case anyone else runs into this.
In the meantime, I've renamed my test database to
testdb
The text was updated successfully, but these errors were encountered: