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

Crashing on MONETDB url (monetdb://localhost:5000/) #49

Closed
ghost opened this issue Jun 15, 2020 · 5 comments
Closed

Crashing on MONETDB url (monetdb://localhost:5000/) #49

ghost opened this issue Jun 15, 2020 · 5 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@ghost
Copy link

ghost commented Jun 15, 2020

import monetdbe
remote = monetdbe.connect("monetdb://localhost:5000/sf1?user=monetdb&password=monetdb")

Gives:

monetdbe.exceptions.OperationalError: MALException:monetdbe.monetdbe_startup:Cannot add farm /home/gijs/Work/MonetDBe-Python/monetdb:/localhost:5000/sf1?user=monetdb&password=monetdb

Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
@gijzelaerr gijzelaerr changed the title Crashing Python Crashing on MONETDB url (monetdb://localhost:5000/) Jun 16, 2020
@gijzelaerr
Copy link
Collaborator

I think monetdbe should not crash here, but at the same time, I should detect if the path is valid.

@gijzelaerr gijzelaerr added the bug Something isn't working label Jun 16, 2020
@njnes
Copy link
Member

njnes commented Jun 16, 2020

Does this by any change crash on the removal/freeing of the exception?

@gijzelaerr gijzelaerr added this to the 0.7 milestone Jun 17, 2020
@gijzelaerr
Copy link
Collaborator

this still crashes:

PASSED    [100%]#: BBPaddfarm: !ERROR: /home/gijs/Work/MonetDBe-Python/tests/monetdb:/localhost:5000/sf1?user=monetdb&password=monetdb: cannot create directory: Unknown error 2
#: createExceptionInternal: !ERROR: MALException:monetdbe.monetdbe_startup:Cannot add farm /home/gijs/Work/MonetDBe-Python/tests/monetdb:/localhost:5000/sf1?user=monetdb&password=monetdb

Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

@njnes
Copy link
Member

njnes commented Jun 17, 2020

I looks like python didn't like the output we created on stderr (mixed up the readline library somehow). Seems solved now we don't output these errors anymore

@gijzelaerr gijzelaerr modified the milestones: 0.7, 0.8 Jun 17, 2020
@njnes
Copy link
Member

njnes commented Jun 19, 2020

fixed

@njnes njnes closed this as completed Jun 19, 2020
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