Re: [PR] ci: validate multiple version builds and use golangci-lint-action [pulsar-client-go]

2024-07-13 Thread via GitHub
nodece commented on code in PR #1250: URL: https://github.com/apache/pulsar-client-go/pull/1250#discussion_r1677012337 ## .github/workflows/ci.yml: ## @@ -20,25 +20,35 @@ on: [pull_request] jobs: build: runs-on: ubuntu-latest +strategy: + matrix: +go-ve

Re: [PR] ci: validate multiple version builds and use golangci-lint-action [pulsar-client-go]

2024-07-13 Thread via GitHub
tisonkun commented on code in PR #1250: URL: https://github.com/apache/pulsar-client-go/pull/1250#discussion_r1677011659 ## .github/workflows/ci.yml: ## @@ -20,25 +20,35 @@ on: [pull_request] jobs: build: runs-on: ubuntu-latest +strategy: + matrix: +go-

(pulsar-client-go) branch master updated: ci: validate multiple version builds and use golangci-lint-action (#1250)

2024-07-13 Thread tison
This is an automated email from the ASF dual-hosted git repository. tison pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/pulsar-client-go.git The following commit(s) were added to refs/heads/master by this push: new 2ff2c2cd ci: validate multiple version

Re: [PR] ci: validate multiple version builds and use golangci-lint-action [pulsar-client-go]

2024-07-13 Thread via GitHub
tisonkun merged PR #1250: URL: https://github.com/apache/pulsar-client-go/pull/1250 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@

[PR] ci: validate multiple version builds [pulsar-client-go]

2024-07-13 Thread via GitHub
nodece opened a new pull request, #1250: URL: https://github.com/apache/pulsar-client-go/pull/1250 ### Motivation Improve CI. ### Modifications - build and test uses the `go-version: [ '1.20', '1.21', '1.22' ]` matrix - lint uses the go stable version -- This is an

Re: [D] Pulsar JDBC postgres Sink always return null value [pulsar]

2024-07-13 Thread via GitHub
GitHub user alexandrebrilhante added a comment to the discussion: Pulsar JDBC postgres Sink always return null value I think the issue is that you're sending messages like `{"id"=123, "name":"John"}` to the sink connector, I think the solution is to exclude the `id` field from the message, al