-
Notifications
You must be signed in to change notification settings - Fork 28
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
Hangs on certain code #10
Comments
I'm unable to reproduce the problem using this code on Win32/DMD 2.062/Vibe.d 0.7.15 with the latest master of mysqln-native:
And this cmdline:
|
Hi Nick, Thanks for testing, it is some weird combination of the build command with Cheers, On Thu, May 30, 2013 at 9:55 PM, Nick Sabalausky
|
What build command does result in the problem? |
I have to build and then link because otherwise the linker never seems to
On Thu, May 30, 2013 at 10:12 PM, Nick Sabalausky
|
The closest I can get to compiling the below results in: On Thu, May 30, 2013 at 9:55 PM, Nick Sabalausky
|
err, forgot to say. That is after I updated to latest mysql-native. On Thu, May 30, 2013 at 11:40 PM, Rory McGuire [email protected] wrote:
|
On Thu, 30 May 2013 14:07:14 -0700
Hmm, it's difficult for me to attempt it that way since I'm not sure On my Debian 6 box with libevent v2.0-5, this command works: rdmd -version=VibeCustomMain -version=VibeLibeventDriver That actually does reach "done" for me. I wonder if maybe the way Oh, and I'd toss in a "stdout.flush();" right after you write "done" |
On Thu, 30 May 2013 14:40:30 -0700
That's very strange. Is that with vibe.d v0.7.15 or something else? Can |
acquire/release/isOwner was removed recently.
That was caused by the latest master changes, where the explicit |
On Fri, May 31, 2013 at 8:04 AM, Nick Sabalausky
I'm pretty sure that writeln does a flush. I know that write doesn't. |
Seems you need to make the dub package depend on vibe now: Building configuration "library", build type debug On Fri, May 31, 2013 at 9:08 AM, Sönke Ludwig [email protected]:
|
It's supposed to use vibe.d only when it's added as a dependency by another package (and thus |
BTW, not sure if this helps, but when debugging why something works with DUB and not when compiling directly, you can run |
thanks, you nailed it. I had put Have_vibe_d in the library config in BTW: how do you get dub to use the system installed packages? It doesn't On Fri, May 31, 2013 at 9:16 AM, Sönke Ludwig [email protected]:
|
thanks yes I've used that quite a few times. On Fri, May 31, 2013 at 9:20 AM, Rory McGuire [email protected] wrote:
|
I've just committed a fix for compiling mysql-native without the
It should automatically use them, but should also prefer user installed packages and packages installed in the .dub folder of a project. However, I'm currently reworking how packages are looked up and installed. So probably, if there is a bug, it will be fixed in the process. |
On Fri, May 31, 2013 at 9:29 AM, Sönke Ludwig [email protected]:
BTW: how does one access the session from a function that is registered Need a way to check what details a authenticated user can see. Thanks. |
A REST service should never have a session running (or it is no actual REST interface), so there is no direct way to do this. But a possibility is to register an interception handler that puts the session parameters (or any other parameters) in the
BTW: That e-mail reply feature of github is seriously broken. How on earth do they think it's a good idea to remove all formatting and even all line breaks from a mail? |
On Fri, May 31, 2013 at 1:50 PM, Sönke Ludwig [email protected]:
Very true. If the user supplied req.param["username"] it would be |
I'm closing this since the original problem has been resolved. |
From vibe-d/vibe.d#231 (comment):
@rjmcguire: Can you grab the latest master of mysql-native and try with that? I don't know if you're using 32- or 64-bit, but I did add some 64-bit fixes since the version where phobos was opt-in. But even if you're using 32-bit, it'll be easier to figure out if we're both working from the latest master.
The text was updated successfully, but these errors were encountered: