Conversation
|
I see changes in the source code, it is verified that it correctly works with these changes especially into the related things that depends of this code ? |
|
@Thanatermesis for some reason it was working earlier and not now, thanks for catching that. currently workingon fixing the issue
What depends on this code, so that I can test it? |
|
I found the issue in my fork by debugging. It's because there's a space between '383' and 'KB/s' and in my dummy file I didn't have that field. I'm not sure how to get around this - I'll keep thinking. In case you're wondering, here's my debug output: |
|
Thinking - maybe I could use regex to look for |
Elive Forum Replace wikipedia link with elive forum topic about it Also... Comment out useless stuff
|
I fixed it using a "hacky" approach - it looks for a ValueError while doing it; if so it will combine the third value and the second value. |
|
Can you test this? It works for me, but I'd rather have two pairs of eyes rather than just one. :) |
Also...
Notes:
/etc/elive-versionto find this)