profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/xloem/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.

websocket-client/websocket-client 2730

WebSocket client for Python

libbtc/libbtc 224

Tiny Bitcoin Library written in C

Qoracoin/releaseNotes 1

What's new in the release

Community-Maintenance/police-brutality 0

Repository containing evidence of police brutality during the 2020 George Floyd protests

Community-Maintenance/python-delimitedfile 0

Interpret a delimited file as a mutable sequence

fuzzyTew/todo 0

log of simple parts of daily routine

gmkarl/litelog 0

A simple, modular data logging system.

xloem/911-file 0

emergency script for when a file seems lost

PR opened PyCQA/baron

When rendering, skip missing keys

This is a very quick change to provide for rendering structures that are missing nonimportant keys.

>>> baron.dumps([dict(type='print', value=[dict(type='associative_parenthesis', value=dict(type='string', value='"hello, world"'))])])
'print("hello, world")'
+2 -1

0 comment

1 changed file

pr created time in 3 hours

create barnchxloem/baron

branch : opt_render_key

created branch time in 3 hours

fork xloem/baron

IDE allow you to refactor code, Baron allows you to write refactoring code.

http://baron.pycqa.org

fork in 3 hours

create barnchxloem/simple

branch : main

created branch time in 3 hours

created repositoryxloem/simple

Python package for simple missing relations helpful to the runtime design of code.

created time in 3 hours

issue openedgunthercox/ChatterBot

Running instances?

Is anybody running public example chatterbots, for people to talk with or develop live together?

created time in a day

PR opened OLIMEX/DIY-LAPTOP

600 DPI scan of keyboard traces.

This is a scan of the plastic film under the keyboard keys, made with a Canon MX922 printer.

+0 -0

0 comment

1 changed file

pr created time in 2 days

create barnchxloem/DIY-LAPTOP

branch : kb-traces

created branch time in 2 days

push eventxloem/codesynth

0xloem

commit sha 4638edb49a237a1c5f766b013e7d9557b33faf9f

partial weak attempt to connect ctxs to channels; next woudl be separating the command handling from the ctx prefix

view details

push time in 2 days

issue commentctubio/Krypto-trading-bot

Backtesting

the main reason for not implementing backtesting is because it requires to duplicate (some) sources or to hijack time/loop functions to work in real and in fake mode

performance is a priority so i dont wanna wrap functions that are called thousands of times a second just to allow fake trading

there's usually a way to use templates or macros to resolve situations like the one you describe, although I understand you've refactored the code to open better approaches

Lazarth

comment created time in 3 days

issue commentctubio/Krypto-trading-bot

Backtesting

I used this bot to trade and with some experience it can be quite successful. It takes manual tuning. The issue I ran into is that the private APIs kept changing the details of their interface, and the bot couldn't always keep up. I also ran into data that seemed incorrect being delivered to my client via the apis. Due to how licensing is done, it can become expensive to use this bot to trade many different cryptocurrencies or exchanges.

I believe the policy of the project is that backtesting is not to be implemented, and my understanding is that requests for backtesting and additions providing backtesting are to be closed. I do not see any reason for that. Backtesting is a basic feature of a trading bot.

However, the bot uses relatively simple algorithms, and it should be reasonable for one to do manual backtesting to tune some of the parameters.

Lazarth

comment created time in 3 days

pull request commentlibusb/libusb

Android: Calling op_set_option even if no default context is set

@hjelmn would it be helpful here if somebody wrote up a dummy backend that can reproduce the issue without running on android?

harbulot

comment created time in 3 days

issue commentlibusb/libusb

Misc: To release 1.0.25

Should #942 be a blocker for this release, so the release doesn't break existing rootless android code? Or maybe hjelmn's changes to option handling that stimulated 942 could be pulled out into a PR?

mcuee

comment created time in 3 days

push eventxloem/colabaccess

0xloem

commit sha 8207ee73d916432e5645d6e4d1e0da5f82e09de6

fix

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha 9a7bb7df12fe6cdd2644174e5b929f91c05feb52

some output fixes and untested img retrieval

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha b85bfa0f7a9a89b87d65f4027a769a5eded3dfc3

frame bug fudge

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha c1228bd96d6a222a493a7e260af1d672a9e8ceee

-

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha 77e60fdc6c049880da4f2fc74aff6c6d028d1b2e

fields

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha d6534d7fe54d43e419b7d503377e2d77cad480f5

fixes to output streaming and reconnection; autocreates google driver now

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha 0f02f0d0d0e45fc31a2a56ea531953472b3fd454

fixes, added google driver subclasses

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha 896ae896622798b42a24bd7c7ea65fd5018069cd

chrome engine

view details

0xloem

commit sha a516fe69e612d6d895f9f0475923f0391a59554a

removed commented code

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha e18c2f2741fca803677967fe1dfce9a9b6eb135d

added reconnect function, small fix

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha e5692a3304348ed3ce19fe6043ff7ecb15e379a0

possible fixes

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha d82f3b188ded9addbae50e3f2fd8787f471144fa

-

view details

push time in 5 days

push eventxloem/colabaccess

0xloem

commit sha 30b7ab9165b99c74a180fbb4782db6a0c2e0aa10

-

view details

0xloem

commit sha 94e7906cefa2bbdd4fabbb8d30984c8b1f1c5f80

-

view details

xloem

commit sha fe352708199d83ab387222bd22535c0ee61c6afc

fixes

view details

0xloem

commit sha d82f3b188ded9addbae50e3f2fd8787f471144fa

-

view details

push time in 5 days

push eventxloem/technobot

xloem

commit sha c10b9d879f5dd0e7a9ef86b91835184c610f39c8

terminate adventure completion on empty output

view details

push time in 6 days

push eventxloem/technobot

xloem

commit sha 6b573fe858ac16f2d27905c78d6e8d5ff5ec3568

fix logic error

view details

push time in 6 days

push eventxloem/technobot

xloem

commit sha e335d8fb95407cef550217e0ba90468f58b79216

fix for empty string

view details

push time in 6 days

PR opened technobird22/technobot

does this work / fix the issue?

hi technobird

this may or may not fix the two problem cases with the adventure channel. what do you think? i spasm a lot when coding so if you could review for errors it would be great

+4 -2

0 comment

1 changed file

pr created time in 6 days

push eventxloem/technobot

xloem

commit sha 4559b7f97a357700e26d25a548ef745229575b52

does this work / fix the issue? hi technobird this may or may not fix the two problem cases with the adventure channel. what do you think? i spasm a lot when coding so if you could review for errors it would be great

view details

push time in 6 days