apache / apache/pulsar-client-cpp
[Bug] subscribeAsync and createProducerAsync return UnknownErrorCode when built using devtoolset-11
- Linguagem predominante
- C++
- Estrelas
- 71
- Forks
- 90
- Merge médio
- 2h 33min
- PRs com merge (30d)
- 3
Descrição
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar-client-cpp/issues) and found nothing similar.
### Version
OS: CentOS 7
Pulsar C++ client: 3.1.2
### Minimal reproduce step
1. Install gcc 11.
```
yum install devtoolset-11
. /opt/rh/devtoolset-11/enable
```
2. Install the same dependencies as this Dockerfile:
https://github.com/apache/pulsar-client-cpp/blob/v3.1.2/pkg/rpm/Dockerfile
3. Build rpm using this spec file:
https://github.com/apache/pulsar-client-cpp/blob/v3.1.2/pkg/rpm/SPECS/pulsar-client.spec
4. Install pulsar client library.
```
rpm -ivh apache-pulsar-client*.rpm
```
### What did you expect to see?
#subscribeAsync and #createProducerAsync return ResultOk.
### What did you see instead?
#subscribeAsync and #createProducerAsync return UnknownErrorCode.
When I tried to output the value of return value, it returned unexpected values like 1915086316.
### Anything else?
When built using gcc-toolset-11 on Rocky Linux 8, #subscribeAsync and #createProducerAsync return ResultOk.
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Guia de contribuição
Direção de pesquisa
Reproduza o problema no CentOS 7 com devtoolset-11 usando pkg/rpm/Dockerfile e pkg/rpm/SPECS/pulsar-client.spec. Rastreie subscribeAsync e createProducerAsync para determinar por que seus valores retornados se tornam UnknownErrorCode e, em seguida, verifique se ambos retornam ResultOk com valores válidos no build reportado.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- cpp, linux
- Domínio
- api
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 35/100