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

Add log messages when listen fails #6549

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Add log messages when listen fails #6549

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2018-03-01 10:11:52 +0100
From: Zhouyang <>
To: clients devs <>
Version: 11.27.13 (Jul2017-SP4)

Last updated: 2018-03-29 15:39:08 +0200

Comment 26234

Date: 2018-03-01 10:11:52 +0100
From: Zhouyang <>

Created attachment 600
Fix reported problems

Hi,

I analyzed the monetdb source code and found some potential API bugs.
The function listen may fail, when it happens, there would be unexpected results, which are hard to debug without proper logs.
This patch (against the latest master branch) adds log messages when listen fails.

Best,
Zhouyang

Attached file: listen_monetdb-trunk.patch (text/plain, 1550 bytes)
Description: Fix reported problems

Comment 26235

Date: 2018-03-01 15:09:38 +0100
From: MonetDB Mercurial Repository <>

Changeset a7ac54dc0fa4 made by Pedro Ferreira pedro.ferreira@monetdbsolutions.com in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=a7ac54dc0fa4

Changeset description:

Fixes for bug #6549, check for system calls failures

Comment 26245

Date: 2018-03-08 16:00:08 +0100
From: @sjoerdmullender

Patch was applied.

Comment 26303

Date: 2018-03-29 15:39:08 +0200
From: @sjoerdmullender

The Mar2018 version has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant