profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/engn33r/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
engn33r engn33r @PalindromeLabs https://security.erikelbieh.com https://twitter.com/bl4ckb1rd71

websocket-client/websocket-client 2730

WebSocket client for Python

engn33r/awesome-bluetooth-security 122

List of Bluetooth BR/EDR/LE security resources

PalindromeLabs/Java-Deserialization-CVEs 46

Compiled dataset of Java deserialization CVEs

engn33r/awesome-redos-security 4

List of RegEx DoS (ReDoS) CVEs and resources

PalindromeLabs/zgrab2 2

Fast Go Application Scanner

engn33r/awesome-kubernetes-security 0

A curated list of awesome Kubernetes security resources

engn33r/awesome-websockets 0

A curated list of Websocket libraries and resources.

engn33r/Common-Bash-Patterns 0

A helpful reference of common bash script features and functions

engn33r/Fuzzing-Survey 0

The Art, Science, and Engineering of Fuzzing: A Survey

starteddefparam/haptyc

started time in a day

startedjtesta/ssh-audit

started time in 2 days

startedOrange-Cyberdefense/arsenal

started time in 8 days

issue closedwebsocket-client/websocket-client

On_message handling for high volume stream

Apologies, this is not an issue but rather a clarification request. I have looked in the documentation and I couldn't find an answer.

I would like to ask how a high volume of incoming data to the websocket client is handled by the on_message event. I understand that the function linked to the on_message event is triggered every time a new message is received from the server. What happens if/when a high volume of messages is received and the on_message function takes some time to handle the data? Are the "on_message" queued and executed once there are free resources?

Thank you in advance

closed time in 14 days

Spino1981

issue commentwebsocket-client/websocket-client

On_message handling for high volume stream

I don't have an exact answer about on_message, but a similar question about high volume WebSockets was recently asked in #735. You can always use the Python trace tool to examine the details of a particular piece of code, since most of the project's documentation attempts to remain high level.

If you are encountering specific issues with your program, please share details as outlined in the contribution guidelines.

Spino1981

comment created time in 14 days

issue commentwebsocket-client/websocket-client

recv() missing 2 required positional arguments: 'sock' and 'bufsize'

There is insufficient information here to provide an answer. Please follow the contribution guidelines if you want help.

adambauer1

comment created time in 15 days

issue closedwebsocket-client/websocket-client

how to install websocket-client in linux system?

is there a tutorial?

closed time in 15 days

bmw7

issue commentwebsocket-client/websocket-client

how to install websocket-client in linux system?

See the readme: https://github.com/websocket-client/websocket-client#installation

If this is your first time using Python or Linux, I'd suggest using a basic intro tutorial. This project's documentation assumes you have performed similar steps before.

bmw7

comment created time in 15 days

issue commentwebsocket-client/websocket-client

WebSocketApp close() hangs on broken connection despite of timeout

@elderlabs have you tried replicating this issue with multiple WebSocket servers, or do you always encounter it with the same server? I haven't looked at this problem closely yet, but if you have a minimum reproducible example that lets me recreate the issue on my end, I'll be able to dig deeper into this when I have the time.

yhhsteven

comment created time in 23 days

issue closedwebsocket-client/websocket-client

why did you name your module the same as websocket?

it makes my life harder. If possible, in the next release, could you change it to websocket_client? It's a widespread issue for the people who make websocket bots and host them using repl.it

closed time in 23 days

MaleVTuber

issue commentwebsocket-client/websocket-client

why did you name your module the same as websocket?

This is covered in the FAQ: https://websocket-client.readthedocs.io/en/latest/faq.html#what-s-going-on-with-the-naming-of-this-library

MaleVTuber

comment created time in 23 days

push eventengn33r/awesome-bluetooth-security

engn33r

commit sha 9a9e52b3b1005c42c9bb506b3868fecaf9269424

Add more new 2021 CVEs

view details

push time in 23 days

pull request commentwebsocket-client/websocket-client

Add docstring to WebSocket.send_binary

Thanks!

benhoyt

comment created time in 25 days

push eventwebsocket-client/websocket-client

Ben Hoyt

commit sha f7480f6781e7e81248f108a1993ac639255d9d45

Add docstring to WebSocket.send_binary (#737) Fixes #736

view details

push time in 25 days

issue closedwebsocket-client/websocket-client

Document `WebSocket.send_binary` method?

The WebSocket class has a handy send_binary() method, however, it doesn't have a docstring and doesn't appear in the documentation, so I wasn't sure whether it was supposed to be part of the public API or not. (Though I notice there's at least one test for it.)

We should add a docstring either way, either to say "yes, here's what it does, use it" or "here's what it does, but it's deprecated, use send(x, opcode=websocket.ABNF.OPCODE_BINARY) instead".

I'm happy to submit a PR to add the docstring once I know which direction you want to go.

closed time in 25 days

benhoyt

issue commentwebsocket-client/websocket-client

Document `WebSocket.send_binary` method?

I don't have any immediate thoughts because I haven't used the send_binary() function in my projects, but it does appear in a unit test. I would lean towards send_binary() not being deprecated but just infrequently used, unless you see something indicating otherwise.

benhoyt

comment created time in a month

push eventengn33r/awesome-bluetooth-security

engn33r

commit sha 7e7206b656bc4cf1348a877557f72d81ab165ed1

Remove Travis CI yml

view details

push time in a month

push eventengn33r/awesome-bluetooth-security

engn33r

commit sha 96754c8993950da9481e23e621675dd519218422

Fix link issue from Github Action CI

view details

push time in a month

push eventengn33r/awesome-bluetooth-security

engn33r

commit sha de661895072e06d3aebebb9f0b427bee346fd42d

Add Github Action to check for broken links

view details

push time in a month

push eventengn33r/awesome-redos-security

engn33r

commit sha 151b81ef7e521c2c84c4692a63dc5cb645086ac2

Remove less feature-fill and more error-prone Github Action

view details

push time in a month

push eventengn33r/awesome-redos-security

engn33r

commit sha b932fdd45710d21c4c1450b7f6a27bf650e397fa

Fix incorrect link for CVE-2021-33502

view details

push time in a month

push eventengn33r/awesome-redos-security

engn33r

commit sha 6eda6ae5cd540e784e7de63502f8603b9bd4a879

Fix dead link found by CI

view details

push time in a month

startedxwiki-labs/cryptpad

started time in a month

push eventengn33r/awesome-redos-security

engn33r

commit sha 248df3309a9a1c2c513e4630b5d3e362b49fc017

Add Github Action config file for 429 response

view details

push time in a month

push eventengn33r/awesome-redos-security

engn33r

commit sha e28c60e618158d4d1b8b3582fab7c7f3b5c22db3

Add 2nd URL checker in CI for comparison

view details

push time in a month

push eventengn33r/awesome-redos-security

engn33r

commit sha 1e11233a5430b7dd095021b03a0c501880903369

Add Github Action to test URLs

view details

push time in a month

push eventengn33r/awesome-redos-security

engn33r

commit sha 47c6fb97bf80d72c2bf2c30d9449e5582a32177f

Add new 2021 CVEs

view details

push time in a month

push eventwebsocket-client/websocket-client

engn33r

commit sha 701a0d8539d7c01215d633bac99f0faebb8a16c0

Fix #734 improve extra_requires documentation in README

view details

push time in a month