152
86
6
Events
ynca resources
ynca commands
notes
rename to last_payload
execution via service
unbreak tests
volume down test
better diagnostics
sleep 1 to 2 seconds before retrying
production error handling
0.2.8
denon protocol (network)
harman/kardon docs
harman/kardon repo links
response parsing
integration test
move unit tests
unpend unit tests
this doc covers rx-v1400 also
add yamaha identifiers from docs
split yamaha constants
command response parsing
p push p/pubfiles
gitignore yarn-error.log
gtkterm improve blue color
p push p/react-easy-router
replace componentWillReceiveProps with componentDidUpdate
build
3.2.2
p push p/react-easy-router
no such thing as componentDidUnmount
build
3.2.1
p push p/react-easy-router
remove componentWillMount / componentWillUnmount usage
build
update react-helmet for componentWillMount warning
adjust createMemoryHistory import
rename readme
3.2.0, release notes
p push p/react-easy-router
Segment name test in link
Needed segmentValueCharset
Docs
Merge pull request #3 from p/segment-value
Support for arbitrary path segment values
3.1.0
rebuild for 3.1.x
update package
3.1.0
dependencies
p push p/pubfiles
x over ssh note
fox privacy
fox file description
do not compress .deb files
sonamp auto off
move code
ruby installer
pubnpm
install ruby
p push p/scan-to-pdf
skip check if resolution is 0
p push p/pubfiles
bundler configuration
p push p/pubfiles
iw: improve experience
iw: note zenity
iw dependency
fix photo export script
x via ssh
x via ssh part 2
x over ssh
organize readme
increase yamaha timeout
timeout option to web launchers
redo sonamp locking
sonamp test
thread safe test
still need a recursive mutex
0.2.3
skip probing for a single device matching patterns
short circuit when no devices match
typo fix
integra power
increase integra timeout
status string now requires status issuance
handle rx-v1800 status response
0.2.4
yamaha volume note
integra volume
integra volume notes
integra volume
p push p/pubfiles
bypass the prompt if noninteractive
node base
node base
debug node base
node base remove debug
node base
fix node modules symlinking for webpack 4
use PropTypes from prop-types package instead of React.PropTypes
Bump react to 0.14.9 for prop-types package compatibility
run build to be able use patch while waiting for PR to be merged
update for 1.0.0 release (forked)
u[date readme with fork info
bump version
remove componentWillMount usage
build
Install pycurl on windows
Last I checked I couldn't find the documentation for how to build binary wheels. Locating it would be a good start.
Curl objects do not support serialization
You cannot reuse some parts of libcurl handles while changing other parts. A handle contains both options and connection state. If you want two pycurl objects to reference the same libcurl handle, any change to any of the pycurl objects will affect all other pycurl objects using the same libcurl handle. So, you either need to create new pycurl objects for your different operations, or you might as well reuse a single pycurl object.
pycurl implements deep copy via duphandle, after the copy you will have two separate libcurl handles. Read https://curl.se/libcurl/c/curl_easy_duphandle.html, specifically:
The new handle will not inherit any state information, no connections, no SSL sessions and no cookies. It also will not inherit any share object states or options (it will be made as if CURLOPT_SHARE was set to NULL).
p push p/pubfiles
universalizing apt-cache config
crx downloader
alsa spdif configuration
also adjust dmesg permission on running systems
skip ntpd installation for firewalled machines
fix apt cache configuration
update mongodb installer
Websocket support
Please feel free to contribute the required code as per @swt2c comment above.
Websocket support
Prior to creating an issue, please review the troubleshooting documentation: http://pycurl.io/docs/dev/troubleshooting.html
What did you try to do?
When will websockets be supported?
PyCurls hangs after running continuously
You need to, therefore your energy will be better spent figuring out how to do it. Most servers have tens of gigabytes of available disk, that should suffice for a lot of logs.
