ERROR: activity_common/vote.go:60 pq: invalid input syntax for type bigint: ""

[brocaar]

Describe the bug

In the logs, this error is occurring many times:

activity_common/vote.go:60      pq: invalid input syntax for type bigint: ""

To Reproduce

I'm not sure what activity triggers this error, but in the log history of the answer process, I see this error occurring many times.

Platform

• Linux (AMD64)
• Version 1.7.1 (built with plugins)
• PostgreSQL v17.7

[brocaar]

@LinkinStars do you have an idea why this is happening? This is a very regular error message I see in the logs.

[LinkinStars]

@LinkinStars do you have an idea why this is happening? This is a very regular error message I see in the logs.

@brocaar Thank you for feedback. This issue occurs when accessing comments while not logged in. Due to differences in how MySQL and PostgreSQL handle data, MySQL automatically removes empty strings while PostgreSQL does not, resulting in this error. We will fix this issue in the next version.

[LinkinStars]

Fix in 2.0.0

[brocaar]

@LinkinStars, this seem not to be resolved unfortunately.....

I still see:

ERROR        activity_common/vote.go:60        pq: invalid input syntax for type bigint: ""

$ ./answer -v
answer version 2.0.0
revision: a6bfd40
build time: 2026-02-03T02:03:19Z

[LinkinStars]

The issue we previously resolved occurred because users accessing comments directly while not logged in triggered this error. Based on your logs, other scenarios may also cause this error to appear. We will continue to investigate this issue.

[brocaar]

@LinkinStars are you sure that the ./answer build ... pulls in the same version as the answer binary that executes it? I noticed that since I'm using ANSWER_MODULE env variable you pointed out in #1493, I do see the Intelligence menu item in the admin site. Before when I downloaded the Answer v2 binary (which should have this menu item I believe), and build a new binary to include the plugins, it did not show. I no longer see the pq: invalid input syntax for type bigint: "" error.

This makes me think that maybe ./answer build ... did not pull in the exact same Go source to rebuild the Answer binary + plugins. Instead it relied on an older source in my $GOPATH. Could that be?

I see that this happens when ANSWER_MODULE is set:
https://github.com/apache/answer/blob/main/internal/cli/build.go#L202

But it is not clear to me if there is something that enforces pulling in the exact same Go source version as the answer binary that builds the new binary?

[LinkinStars]

@LinkinStars are you sure that the ./answer build ... pulls in the same version as the answer binary that executes it? I noticed that since I'm using ANSWER_MODULE env variable you pointed out in #1493, I do see the Intelligence menu item in the admin site. Before when I downloaded the Answer v2 binary (which should have this menu item I believe), and build a new binary to include the plugins, it did not show. I no longer see the pq: invalid input syntax for type bigint: "" error.

This makes me think that maybe ./answer build ... did not pull in the exact same Go source to rebuild the Answer binary + plugins. Instead it relied on an older source in my $GOPATH. Could that be?

I see that this happens when ANSWER_MODULE is set: https://github.com/apache/answer/blob/main/internal/cli/build.go#L202

But it is not clear to me if there is something that enforces pulling in the exact same Go source version as the answer binary that builds the new binary?

If ANSWER_MODULE is specified, the code will be compiled using the path designated by ANSWER_MODULE. If ANSWER_MODULE is not specified, the latest version of the version will be fetched from the remote by default.

[brocaar]

the latest version of the version will be fetched from the remote by default.

I would need to test this further, but it seemed at my side that if Go already cached the package, it might not actually update it. It looked like I had the v2 compiled, but the Intelligence menu-item which was added in v2 was not visible. So I think it did not actually fetch the v2 code, as previously I had built v1.7 on my host.