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

stackcount: fix TypeError #2514

Merged
merged 1 commit into from
Sep 15, 2019

Conversation

mwesolowski
Copy link
Contributor

fix for one of the problems mentioned in #2512

@palmtenor
Copy link
Member

[buildbot, ok to test]

@palmtenor
Copy link
Member

@yonghong-song Is it OK for us to hard-code utf-8 as the encoding?

@yonghong-song
Copy link
Collaborator

@palmtenor I think it should be okay in this case as it is already used 'utf-8' encoding in the same file. Typically, we do not want to do encoding for parameters of bcc python library calls. In this case, it is for print and sometimes for python 3, byte array may print with prefix 'b' which may be undesirable in some cases.

@yonghong-song yonghong-song merged commit c99c7c4 into iovisor:master Sep 15, 2019
CrackerCat pushed a commit to CrackerCat/bcc that referenced this pull request Jul 31, 2024
fix type error in stackcount.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants