-
Notifications
You must be signed in to change notification settings - Fork 19
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
TypeError: Couldn't build proto file into descriptor pool! #40
Comments
According to this issue protocolbuffers/protobuf#3002 proto file that collides with name of proto file from another package. Importing both python packages is not possible as I get this error. You can try to solve by pip uninstall protobuf
pip install --no-binary protobuf protobuf |
I have tried this but it does not work. Update: I figured out the solution #41 by checking whether the file descriptor was added before for avoiding duplication. |
I don't think it's a good idea, we need to find the cause and then fix it. |
@tuanngokien I was wrong before, after re-confirmed that there will indeed be duplicate messages when recursive. For example, there're two message A and B, and we recursive A, we already add A and B, then the next B message will add twice.
So your workaround looks correct |
I am using
cyber_record
to read the Cyber record file.At the moment, I could use it to read messages from channels when the record file is produced by Apollo in the SimControl mode.
However, instead of using SimControl, when using LGSVL to simulate the scenario (connect it through bridge to Apollo), the Cyber record file cannot be read by
cyber_record
(although the file could still be playable by officialcyber_recorder
tool).The error happened when reading the file is as follows:
Given record file for reproducing this bug: https://drive.google.com/file/d/1qr_4Jhz0KWrXsdgcGVdrvsfQ65GB0nCq/view?usp=sharing
The text was updated successfully, but these errors were encountered: