Specific PCAP TTL for Errors

Context:

When an error is reported in the dashboard, the only artifact that matters is the PCAP. At this point, when the TTL is 10s, I can only either record the traffic or increase PCAP TTL for everything - both methods aren't convenient.

Requested:

Add a special Error PCAP TTL that will covern the TTL of reported errors (e.g. TCP, ICMP and other errors)

https://github.com/kubeshark/kubeshark/commit/92dab2e2f768d2437c79e35bae761a65cc4b097f
https://github.com/kubeshark/worker/commit/ce1b491c1399ef6307e1033b85f1fc4ed05305bd


CCL and DCL in new Capacity and Count modes does not take in to account "Allow to charge" and "Allow to discharge"

New modes does not take into account the Allow to charge and Allow to discharge if any of the parallel batteries goes into protection and the total CCL and DCL remains well pass the actual limits. Or may be we have a problem with the correlation of the battery capacity and BMS capacity. I mean, you may have a large battery ie, 460 ah. but a relative small bms like 150a. 430ah 0.5C is 215a (quite common charge rate). but the BMS has a lower capacity 150a. So maybe the problem I have with single battery  with 230a 0.5C rate and a 150 BMS. Your limits computation may only have a  C rate computation when actually, an smaller limit is BMS capacity.
It's a theory actually....

Would it be useful if I added the ability to be able to manually specify something like the "capacities" so it could be manually tuned?

Battery capacity and BMS capacity  are published in dbus and can be easily read. I think its a matter of limiting the computed values (whatever system is selected by user IR, Capacity and Count) and verify before publishing if battery is under protection for charging and/or discharging,  and limit the value to the max bms capacity,  if applicable.  That should work with any computation. With dbus-serialbattery there is already implemented a max charge protection that could be based on SOC, Battery temperature or cell voltage.  In this scenario batteries are well protected and the direct sum of CCL and DCL is enough.  Other batteries like CAB BUS connected will take real benefit of your extra level of protection. So behaviour can be automated and all info read from dbus or CAN. I don't actually know if there is other connection type available for batteries...

I already do this: for each battery I calculate the overall current reqd to reach its ccl then pick the lowest overall current as the aggregated ccl. I don't think there is anything additional I can do to know whether it is going to result in an overcurrent for a particular battery.
Maybe what I could do is start at 90% of that value and slowly increase upwards.

Yes, all good but when a Battery goes into protection, its capacity
shouldn't be taken in consideration for the total CCL if the charge is
closed and DCL if the discharge is closed. At the moment if I close the
charge of one battery to simulate a protection. The CCL does not change and
remaining battery goes to protection due to overcharge.
If Capacity is used, the ah remaining in that battery (protected one)
should be removed from the computation. Only remaining batteries ah should
be used.
Same with Count mode...
El sáb., 27 abr. 2024 15:28, pulquero @.***> escribió:

I already do this: for each battery I calculate the overall current reqd
to reach its ccl then pick the lowest overall current as the aggregated
ccl. I don't think there is anything additional I can do to know whether it
is going to result in an overcurrent for a particular battery.
Maybe what I could do is start at 90% of that value and slowly increase
upwards.
—
Reply to this email directly, view it on GitHub
https://github.com/pulquero/BatteryAggregator/issues/47#issuecomment-2080660334,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFPOLCWQ57UABT7ALYYOAILY7ORXRAVCNFSM6AAAAABGYNJL4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGY3DAMZTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

The code already tracks /Io/AllowToCharge etc and excludes disconnected batteries from consideration. Please turn on debug logging and capture what dbus messages are flying about so we can verify what is actually happening.

Hello! Testing day today. But unfortunatelly i I follow your debug activation sentence, I get an invalid json file and I'm unable to do the test. Thats probably a silly question but I'm stuk.
Here is my json file. It only includes the exclusion of the installed victron shunt on possition 6.
Any  try to include debug: 	"logLevel": "DEBUG"
becomes in log as invalid JSON.
Can you create me a valid JSON with my setup?
config.json

Sure,
{ "logLevel": "DEBUG", 	"excludedServices": ["com.victronenergy.battery.ttyS6"] }
Note, you can change the loglevel dynamically too. BatteryAggregator has a LogLevel dbus path that you can switch between DEBUG and INFO.

Ok here the logs. The test has been performed firs, disconecting and conecting charge and discharge of battery ONE. this test resoult was correct. So behaviour as expected. The test is repeated with battery TWO. Here the reduced limit is not applied and regardless of the disconection (chrge or discharge) there is no significant reduction in CCL and DCL

Count mode is the only one that seems to work.
Here logs
@400000006630d8783033031c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Power
@400000006630d8783045f2c4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM1: -90.11} now has values {'com.victronenergy.battery.ttyACM0': -78.93, 'com.victronenergy.battery.ttyACM1': -90.11} with result -169.04000000000002
@400000006630d878347ce1cc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MinCellVoltage
@400000006630d878348db27c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.329} now has values {'com.victronenergy.battery.ttyACM0': 3.326, 'com.victronenergy.battery.ttyACM1': 3.329} with result 3.326
@400000006630d87834a04464 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MaxCellVoltage
@400000006630d87834b7337c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.33} now has values {'com.victronenergy.battery.ttyACM0': 3.331, 'com.victronenergy.battery.ttyACM1': 3.33} with result 3.331
@400000006630d87930df8efc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Current
@400000006630d879318a9c0c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM1: -6.68} now has values {'com.victronenergy.battery.ttyACM0': -5.93, 'com.victronenergy.battery.ttyACM1': -6.68} with result -12.61
@400000006630d8793221d6e4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Power
@400000006630d87932391bec DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM1: -88.91} now has values {'com.victronenergy.battery.ttyACM0': -78.93, 'com.victronenergy.battery.ttyACM1': -88.91} with result -167.84
@400000006630d8793541fad4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MinCellVoltage
@400000006630d87935bb0334 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.328} now has values {'com.victronenergy.battery.ttyACM0': 3.326, 'com.victronenergy.battery.ttyACM1': 3.328} with result 3.326
@400000006630d87935d91284 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MaxCellVoltage
@400000006630d87935ed80fc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.329} now has values {'com.victronenergy.battery.ttyACM0': 3.331, 'com.victronenergy.battery.ttyACM1': 3.329} with result 3.331
@400000006630d87a0c802454 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@400000006630d87a0d2d5444 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -6.02} now has values {'com.victronenergy.battery.ttyACM0': -6.02, 'com.victronenergy.battery.ttyACM1': -6.68} with result -12.7
@400000006630d87a0e4e394c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@400000006630d87a0e71132c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -80.13} now has values {'com.victronenergy.battery.ttyACM0': -80.13, 'com.victronenergy.battery.ttyACM1': -88.91} with result -169.04
@400000006630d87a10a066ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@400000006630d87a10d253ec DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C3} now has values {'com.victronenergy.battery.ttyACM0': 'C3', 'com.victronenergy.battery.ttyACM1': 'C1'} with result C3
@400000006630d87a2feb6ee4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Current
@400000006630d87a3052c01c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM1: -6.86} now has values {'com.victronenergy.battery.ttyACM0': -6.02, 'com.victronenergy.battery.ttyACM1': -6.86} with result -12.879999999999999
@400000006630d87a312e918c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Power
@400000006630d87a323c8ebc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM1: -91.31} now has values {'com.victronenergy.battery.ttyACM0': -80.13, 'com.victronenergy.battery.ttyACM1': -91.31} with result -171.44
@400000006630d87a334298c4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MaxCellVoltage
@400000006630d87a33f53f24 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.33} now has values {'com.victronenergy.battery.ttyACM0': 3.331, 'com.victronenergy.battery.ttyACM1': 3.33} with result 3.331
@400000006630d87b0b2460fc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@400000006630d87b0b357414 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -5.93} now has values {'com.victronenergy.battery.ttyACM0': -5.93, 'com.victronenergy.battery.ttyACM1': -6.86} with result -12.79
@400000006630d87b0e7fad74 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@400000006630d87b0edce0d4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -78.93} now has values {'com.victronenergy.battery.ttyACM0': -78.93, 'com.victronenergy.battery.ttyACM1': -91.31} with result -170.24
@400000006630d87b1041f2fc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@400000006630d87b11380714 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C1} now has values {'com.victronenergy.battery.ttyACM0': 'C1', 'com.victronenergy.battery.ttyACM1': 'C1'} with result C1
@400000006630d87b310074dc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Current
@400000006630d87b314ab0c4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM1: -6.77} now has values {'com.victronenergy.battery.ttyACM0': -5.93, 'com.victronenergy.battery.ttyACM1': -6.77} with result -12.7
@400000006630d87b31a56b54 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Power
@400000006630d87b31bacbfc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM1: -90.11} now has values {'com.victronenergy.battery.ttyACM0': -78.93, 'com.victronenergy.battery.ttyACM1': -90.11} with result -169.04000000000002
@400000006630d87c30d3699c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Current
@400000006630d87c310b4664 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM1: -6.86} now has values {'com.victronenergy.battery.ttyACM0': -5.93, 'com.victronenergy.battery.ttyACM1': -6.86} with result -12.79
@400000006630d87c317d559c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Power
@400000006630d87c3239cf9c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM1: -91.31} now has values {'com.victronenergy.battery.ttyACM0': -78.93, 'com.victronenergy.battery.ttyACM1': -91.31} with result -170.24
@400000006630d87c330c794c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MaxCellVoltage
@400000006630d87c33299a54 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.329} now has values {'com.victronenergy.battery.ttyACM0': 3.331, 'com.victronenergy.battery.ttyACM1': 3.329} with result 3.331
@400000006630d87d0df76aa4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Soc
@400000006630d87d0e1cadb4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Soc updated with {com.victronenergy.battery.ttyACM0: 96.8} now has values {'com.victronenergy.battery.ttyACM0': 96.8, 'com.victronenergy.battery.ttyACM1': 80.75} with result 88.775
@400000006630d87d0f4bbbbc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@400000006630d87d0f64ecf4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -6.02} now has values {'com.victronenergy.battery.ttyACM0': -6.02, 'com.victronenergy.battery.ttyACM1': -6.86} with result -12.879999999999999
@400000006630d87d0f95c4dc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@400000006630d87d0fef2f7c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -80.13} now has values {'com.victronenergy.battery.ttyACM0': -80.13, 'com.victronenergy.battery.ttyACM1': -91.31} with result -171.44
@400000006630d87d1019e514 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Capacity
@400000006630d87d103e5534 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Capacity updated with {com.victronenergy.battery.ttyACM0: 356.24} now has values {'com.victronenergy.battery.ttyACM0': 356.24, 'com.victronenergy.battery.ttyACM1': 297.17} with result<PHONE_NUMBER>000001
@400000006630d87d10a99e0c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /ConsumedAmphours
@400000006630d87d10e0463c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /ConsumedAmphours updated with {com.victronenergy.battery.ttyACM0:<PHONE_NUMBER>9999999} now has values {'com.victronenergy.battery.ttyACM0':<PHONE_NUMBER>9999999, 'com.victronenergy.battery.ttyACM1':<PHONE_NUMBER>9999998} with result 267.59
@400000006630d87d2fa33e6c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Capacity
@400000006630d87d300ebdf4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Capacity updated with {com.victronenergy.battery.ttyACM1: 297.16} now has values {'com.victronenergy.battery.ttyACM0': 356.24, 'com.victronenergy.battery.ttyACM1': 297.16} with result<PHONE_NUMBER>000001
@400000006630d87d30b5e304 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /ConsumedAmphours
@400000006630d87d31302f9c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /ConsumedAmphours updated with {com.victronenergy.battery.ttyACM1:<PHONE_NUMBER>9999997} now has values {'com.victronenergy.battery.ttyACM0':<PHONE_NUMBER>9999999, 'com.victronenergy.battery.ttyACM1':<PHONE_NUMBER>9999997} with result<PHONE_NUMBER>9999997
@400000006630d87d329c2f34 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MaxCellVoltage
@400000006630d87d32afcabc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.33} now has values {'com.victronenergy.battery.ttyACM0': 3.331, 'com.victronenergy.battery.ttyACM1': 3.33} with result 3.331
@400000006630d87e0c44116c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@400000006630d87e0d0c62ac DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -5.93} now has values {'com.victronenergy.battery.ttyACM0': -5.93, 'com.victronenergy.battery.ttyACM1': -6.86} with result -12.79
@400000006630d87e0d7af35c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@400000006630d87e0d94a964 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -78.93} now has values {'com.victronenergy.battery.ttyACM0': -78.93, 'com.victronenergy.battery.ttyACM1': -91.31} with result -170.24
@400000006630d87e31aa3db4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MaxCellVoltage
@400000006630d87e31c343f4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.329} now has values {'com.victronenergy.battery.ttyACM0': 3.331, 'com.victronenergy.battery.ttyACM1': 3.329} with result 3.331
@400000006630d87f2ff7888c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MaxCellVoltage
@400000006630d87f30b93e64 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM1: 3.33} now has values {'com.victronenergy.battery.ttyACM0': 3.331, 'com.victronenergy.battery.ttyACM1': 3.33} with result 3.331
@400000006630d880306bca44 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /System/MinVoltageCellId
@400000006630d8803088e37c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinVoltageCellId updated with {com.victronenergy.battery.ttyACM1: C4} now has values {'com.victronenergy.battery.ttyACM0': 'C4', 'com.victronenergy.battery.ttyACM1': 'C4'} with result C4

What I'm expecting to see are /Io/AllowToCharge messages everytime a battery connects/disconnects. These are one of the messages that trigger a recalculation of the CCL. In the first log there was only ever one for disabling ACM1. Never one for enabling it. I think you need to ascertain whether this is being correctly set on the batteries, and maybe if for some reason the aggregator is not picking them up. Or whether the aggregator should be listening to some other alternative message instead.

Hi.
Battery is connecting and disconnecting both of  them. I have checked with bluetooth app and in cerbo UI and they repond properly. So Battery aggregator is not caching the changes...
I send you an additional. Just changed to mode to IR

here last log
@4000000066311ddb0085cfdc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311ddb0085f6ec DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -25.74} now has values {'com.victronenergy.battery.ttyACM0': -25.74, 'com.victronenergy.battery.ttyACM1': 0.0} with result -25.74
@4000000066311ddb036fdc24 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@4000000066311ddb03824ae4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C3} now has values {'com.victronenergy.battery.ttyACM0': 'C3', 'com.victronenergy.battery.ttyACM1': 'C3'} with result C3
@4000000066311ddb37734254 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Voltage
@4000000066311ddb378c8ee4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyACM1: 13.68} now has values {'com.victronenergy.battery.ttyACM0': 13.69, 'com.victronenergy.battery.ttyACM1': 13.68} with result 13.684999999999999
@4000000066311ddb39be4b94 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311ddb39f3d2b4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -1.97} now has values {'com.victronenergy.battery.ttyACM0': -1.97, 'com.victronenergy.battery.ttyACM1': 0.0} with result -1.97
@4000000066311ddb3a22be6c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311ddb3a6afe84 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -26.97} now has values {'com.victronenergy.battery.ttyACM0': -26.97, 'com.victronenergy.battery.ttyACM1': 0.0} with result -26.97
@4000000066311ddc37c45054 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311ddc37ddb83c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -2.06} now has values {'com.victronenergy.battery.ttyACM0': -2.06, 'com.victronenergy.battery.ttyACM1': 0.0} with result -2.06
@4000000066311ddc38ac85a4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311ddc38ef4394 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -28.2} now has values {'com.victronenergy.battery.ttyACM0': -28.2, 'com.victronenergy.battery.ttyACM1': 0.0} with result -28.2
@4000000066311ddc39805834 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@4000000066311ddc3990c73c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C1} now has values {'com.victronenergy.battery.ttyACM0': 'C1', 'com.victronenergy.battery.ttyACM1': 'C3'} with result C3
@4000000066311ddc3a073b74 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MinCellVoltage
@4000000066311ddc3b0828e4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.42} now has values {'com.victronenergy.battery.ttyACM0': 3.42, 'com.victronenergy.battery.ttyACM1': 3.42} with result 3.42
@4000000066311ddd027e38c4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxCellVoltage
@4000000066311ddd0296394c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.424} now has values {'com.victronenergy.battery.ttyACM0': 3.424, 'com.victronenergy.battery.ttyACM1': 3.424} with result 3.424
@4000000066311ddd02be33ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /Dc/0/Voltage
@4000000066311ddd02d4f7cc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyACM1: 13.69} now has values {'com.victronenergy.battery.ttyACM0': 13.69, 'com.victronenergy.battery.ttyACM1': 13.69} with result 13.69
@4000000066311ddd37c4831c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@4000000066311ddd37e17544 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C3} now has values {'com.victronenergy.battery.ttyACM0': 'C3', 'com.victronenergy.battery.ttyACM1': 'C3'} with result C3
@4000000066311ddd38f3ac7c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxCellVoltage
@4000000066311ddd390f4acc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.425} now has values {'com.victronenergy.battery.ttyACM0': 3.425, 'com.victronenergy.battery.ttyACM1': 3.424} with result 3.425
@4000000066311dde3729a2ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311dde373e4004 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -2.15} now has values {'com.victronenergy.battery.ttyACM0': -2.15, 'com.victronenergy.battery.ttyACM1': 0.0} with result -2.15
@4000000066311dde38274c2c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311dde38da0614 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -29.43} now has values {'com.victronenergy.battery.ttyACM0': -29.43, 'com.victronenergy.battery.ttyACM1': 0.0} with result -29.43
@4000000066311dde3a92879c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MinCellVoltage
@4000000066311ddf002c077c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.421} now has values {'com.victronenergy.battery.ttyACM0': 3.421, 'com.victronenergy.battery.ttyACM1': 3.42} with result 3.42
@4000000066311ddf37e52694 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@4000000066311ddf37f56e8c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C1} now has values {'com.victronenergy.battery.ttyACM0': 'C1', 'com.victronenergy.battery.ttyACM1': 'C3'} with result C3
@4000000066311ddf3a5d75ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MinCellVoltage
@4000000066311ddf3a6e32d4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.42} now has values {'com.victronenergy.battery.ttyACM0': 3.42, 'com.victronenergy.battery.ttyACM1': 3.42} with result 3.42
@4000000066311ddf3a824f44 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxCellVoltage
@4000000066311ddf3a93eefc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.424} now has values {'com.victronenergy.battery.ttyACM0': 3.424, 'com.victronenergy.battery.ttyACM1': 3.424} with result 3.424
@4000000066311de037409d7c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311de037621bb4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -1.97} now has values {'com.victronenergy.battery.ttyACM0': -1.97, 'com.victronenergy.battery.ttyACM1': 0.0} with result -1.97
@4000000066311de0385bc5c4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de0389a2a6c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -26.97} now has values {'com.victronenergy.battery.ttyACM0': -26.97, 'com.victronenergy.battery.ttyACM1': 0.0} with result -26.97
@4000000066311de1373994b4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311de1377e1bac DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -2.06} now has values {'com.victronenergy.battery.ttyACM0': -2.06, 'com.victronenergy.battery.ttyACM1': 0.0} with result -2.06
@4000000066311de1387558a4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de138a42cec DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -28.2} now has values {'com.victronenergy.battery.ttyACM0': -28.2, 'com.victronenergy.battery.ttyACM1': 0.0} with result -28.2
@4000000066311de33854576c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311de338548264 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -2.15} now has values {'com.victronenergy.battery.ttyACM0': -2.15, 'com.victronenergy.battery.ttyACM1': 0.0} with result -2.15
@4000000066311de33b3612cc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de33b363dc4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -29.43} now has values {'com.victronenergy.battery.ttyACM0': -29.43, 'com.victronenergy.battery.ttyACM1': 0.0} with result -29.43
@4000000066311de33b5867dc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Info/MaxChargeVoltage
@4000000066311de33b6b3c2c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Info/MaxChargeVoltage updated with {com.victronenergy.battery.ttyACM0: 14.14} now has values {'com.victronenergy.battery.ttyACM0': 14.14, 'com.victronenergy.battery.ttyACM1': 13.8} with result None
@4000000066311de4013b355c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /TimeToGo
@4000000066311de4013b6824 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /TimeToGo updated with {com.victronenergy.battery.ttyACM0: 1103724} now has values {'com.victronenergy.battery.ttyACM0': 1103724, 'com.victronenergy.battery.ttyACM1': 700456} with result 902090.0
@4000000066311de40340254c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM1 /TimeToGo
@4000000066311de403522a94 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /TimeToGo updated with {com.victronenergy.battery.ttyACM1: 1013496} now has values {'com.victronenergy.battery.ttyACM0': 1103724, 'com.victronenergy.battery.ttyACM1': 1013496} with result 1058610.0
@4000000066311de438f3e32c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311de43943acf4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -1.88} now has values {'com.victronenergy.battery.ttyACM0': -1.88, 'com.victronenergy.battery.ttyACM1': 0.0} with result -1.88
@4000000066311de439d71f0c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de439ec29c4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -25.74} now has values {'com.victronenergy.battery.ttyACM0': -25.74, 'com.victronenergy.battery.ttyACM1': 0.0} with result -25.74
@4000000066311de43b92d4e4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@4000000066311de5000a855c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C3} now has values {'com.victronenergy.battery.ttyACM0': 'C3', 'com.victronenergy.battery.ttyACM1': 'C3'} with result C3
@4000000066311de538d6490c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311de5392c40dc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -2.06} now has values {'com.victronenergy.battery.ttyACM0': -2.06, 'com.victronenergy.battery.ttyACM1': 0.0} with result -2.06
@4000000066311de539886e84 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de539bf6ca4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -28.2} now has values {'com.victronenergy.battery.ttyACM0': -28.2, 'com.victronenergy.battery.ttyACM1': 0.0} with result -28.2
@4000000066311de637944b5c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Voltage
@4000000066311de637d4e284 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyACM0: 13.68} now has values {'com.victronenergy.battery.ttyACM0': 13.68, 'com.victronenergy.battery.ttyACM1': 13.69} with result 13.684999999999999
@4000000066311de638f4c9a4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311de6395c70cc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -2.15} now has values {'com.victronenergy.battery.ttyACM0': -2.15, 'com.victronenergy.battery.ttyACM1': 0.0} with result -2.15
@4000000066311de63a10400c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de63a294a34 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -29.41} now has values {'com.victronenergy.battery.ttyACM0': -29.41, 'com.victronenergy.battery.ttyACM1': 0.0} with result -29.41
@4000000066311de73a1d1534 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Voltage
@4000000066311de73a669d6c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyACM0: 13.69} now has values {'com.victronenergy.battery.ttyACM0': 13.69, 'com.victronenergy.battery.ttyACM1': 13.69} with result 13.69
@4000000066311de801087144 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de80146129c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -29.43} now has values {'com.victronenergy.battery.ttyACM0': -29.43, 'com.victronenergy.battery.ttyACM1': 0.0} with result -29.43
@4000000066311de8017ada54 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@4000000066311de80198979c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C1} now has values {'com.victronenergy.battery.ttyACM0': 'C1', 'com.victronenergy.battery.ttyACM1': 'C3'} with result C3
@4000000066311de837f687cc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Voltage
@4000000066311de83806eb1c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyACM0: 13.68} now has values {'com.victronenergy.battery.ttyACM0': 13.68, 'com.victronenergy.battery.ttyACM1': 13.69} with result 13.684999999999999
@4000000066311de838dde25c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de838fe2044 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -29.41} now has values {'com.victronenergy.battery.ttyACM0': -29.41, 'com.victronenergy.battery.ttyACM1': 0.0} with result -29.41
@4000000066311de839ab8acc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Info/MaxChargeCurrent
@4000000066311de83a003a7c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Info/MaxChargeCurrent updated with {com.victronenergy.battery.ttyACM0: 75.3} now has values {'com.victronenergy.battery.ttyACM0': 75.3, 'com.victronenergy.battery.ttyACM1': 0} with result None
@4000000066311de83a60928c DEBUG:com.victronenergy.battery.aggregator:Charging batteries: ['com.victronenergy.battery.ttyACM0']
@4000000066311de83a9d265c DEBUG:com.victronenergy.battery.aggregator:Current ratios: [(2.002173913043478, 'capacity')]
@4000000066311de83ad4ebb4 DEBUG:com.victronenergy.battery.aggregator:CCL estimates: [150.7636956521739]
@4000000066311de83b0d35dc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MinCellVoltage
@4000000066311de83b300fbc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.419} now has values {'com.victronenergy.battery.ttyACM0': 3.419, 'com.victronenergy.battery.ttyACM1': 3.42} with result 3.419
@4000000066311de83b4919e4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxCellVoltage
@4000000066311de83b7efec4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.423} now has values {'com.victronenergy.battery.ttyACM0': 3.423, 'com.victronenergy.battery.ttyACM1': 3.424} with result 3.424
@4000000066311de9381f7c2c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Voltage
@4000000066311de93831b054 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyACM0: 13.69} now has values {'com.victronenergy.battery.ttyACM0': 13.69, 'com.victronenergy.battery.ttyACM1': 13.69} with result 13.69
@4000000066311de9392ff9fc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311de9398b971c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -2.43} now has values {'com.victronenergy.battery.ttyACM0': -2.43, 'com.victronenergy.battery.ttyACM1': 0.0} with result -2.43
@4000000066311de93a1e49cc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311de93b33152c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -33.27} now has values {'com.victronenergy.battery.ttyACM0': -33.27, 'com.victronenergy.battery.ttyACM1': 0.0} with result -33.27
@4000000066311dea01a55d24 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MinCellVoltage
@4000000066311dea01cf99a4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.42} now has values {'com.victronenergy.battery.ttyACM0': 3.42, 'com.victronenergy.battery.ttyACM1': 3.42} with result 3.42
@4000000066311dea01f6f3dc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxCellVoltage
@4000000066311dea020ddb24 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyACM0: 3.424} now has values {'com.victronenergy.battery.ttyACM0': 3.424, 'com.victronenergy.battery.ttyACM1': 3.424} with result 3.424
@4000000066311dea38ee2a54 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Current
@4000000066311dea397fdb34 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyACM0: -2.06} now has values {'com.victronenergy.battery.ttyACM0': -2.06, 'com.victronenergy.battery.ttyACM1': 0.0} with result -2.06
@4000000066311dea3a128de4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /Dc/0/Power
@4000000066311dea3aba5704 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyACM0: -28.2} now has values {'com.victronenergy.battery.ttyACM0': -28.2, 'com.victronenergy.battery.ttyACM1': 0.0} with result -28.2
@4000000066311dea3b6b6ef4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@4000000066311deb003e2fec DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C3} now has values {'com.victronenergy.battery.ttyACM0': 'C3', 'com.victronenergy.battery.ttyACM1': 'C3'} with result C3
@4000000066311deb393587dc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyACM0 /System/MaxVoltageCellId
@4000000066311deb39a312d4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyACM0: C1} now has values {'com.victronenergy.battery.ttyACM0': 'C1', 'com.victronenergy.battery.ttyACM1': 'C3'} with result C3

To check for inconsistencies between the batteries and aggregator, I've create a dbus_dump.py tool available in the latest version. Please run:
python3 dbus_dump.py com.victronenergy.battery
before and after a battery connection/disconnection. It'll write files to /data/dbus_dump_*. Please attach these files to this issue, thanks.

may be something misssing?
python3: can't open file 'dbus_dump.py': [Errno 2] No such file or directory

You probably havent changed directories, try cd /data/BatteryAggregator first. Sure, happy to have a remote session via discord or something.

Hi. I wont be able to test untill next week initially. We keep in touch to prepare a remote session

@pulquero  Hi, if you want. About 1030 am, I'll be able for a remote session

Good with me.

im online right now. Alexdekairos in discord


InputObject Invoke-DscConfigurationByRoles

This is great, exactly what I've been looking for.
My goal is to avoid files on the local systems all together. I forked this just to add InputObject param to Get-ModuleFromConfiguration and Invoke-DscConfiguration, it's working well. Simple thing to add, but I can open pull request if you want.
I haven't thought through how Invoke-DscConfigurationByRoles could be modified to support recursing through several objects in a url and processing them.

absolutely put in a PR to add the inputobject, I didn't do that out of laziness and should have to support your use case of no files on disk. It's awesome someone else found this useful! I've made some breaking changes to the json format to declare objects instead of arrays. This allowed you to use Octopus Deploy to transform variables and that's the context as to why I made the change. So before the PR make sure you've forked the latest build. As for the recursive roles, I'm not sure what the usecase would be. The cmdlet assumes you know the roles you want to invoke. Might be a good helper function depending on the scenario you've got.

@MisterTK good to close our this issue?


IE 7/8 with STIX-Web fonts

I am finding that IE7 and IE8 are having issues loading the STIX-Web fonts. They freeze during the font load, and trigger the error in the console along the lines of:
CSS3111: @font-face encountered unknown error.
File: STIXMathJax_Main-Regular.eot

Here is a quick test file that triggers the error:
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=8" />
<script type="text/x-mathjax-config">
MathJax.Hub.Config({
  "HTML-CSS": {webFont: "STIX-Web"}
});
</script>
<script type="text/javascript" src="http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=AM_HTMLorMML"></script>
</head>
<body>
`sin(2/3 x + pi/2)`
</body>
</html>

This was tested on two systems, neither having the STIX fonts installed locally.  Removing the STIX-Web config and using the default webfonts does not trigger the issue.

Support for IE7 and IE8 has been dropped.


Swift 3

it'd be cool to have a swift 3 version, if you have any interest to create a branch i would like to help with that.

Any chance of a Swift3 update?

I already made a pull request here [https://github.com/evnaz/ENSwiftSideMenu/pull/152](Pull Request) and you can also check out my fork for temp solution: [https://github.com/Sadmansamee/ENSwiftSideMenu](My Fork)
@justdan0227  @nschucky

Any updates on this?

Current one is swift3 compatible @Charlesleonius

It seems that this lib is Swift 3 compatible, but I can't download it through cocoapods because of #154 🤕. Any thoughts?

@rojasbjm  @evnaz  need to update the pod version

@Sadmansamee To what version? I'm using the most recent version of the pod and it's still not pulling the new code.

@coharness  because version number in POD is not updated by the Repo owner, you can simply download project files and good to go.


how can I use the Town07_0.9.5?

Hi,
Make sure that you have the following line in CarlaUE4/Config/DefaultGame.ini:
+MapsToCook=(FilePath="/Game/Carla/Maps/Town07")
Then package CARLA again (with make package).
Then run the packaged version of CARLA (located in Dist/xxxxx/LinuxNoEditor) with ./CarlaUE4.sh Town07
You should now see Town07 and should be able to run the training provided you set up the CARLA_ROOT env variable as briefly described here.
Good luck!


Dropdown menu does not close on click if page contains element with transition

Describe the bug
Describe the bug
The the page contains an element with a transition, the dropdown menu does not close when clicking a dropdown item. The transition is run, and the page navigates, but the dropdown menu stays open on the new page.
This even happens if the transition has 0 duration, so I have found no way to work around it except removing all out-transitions.
As you can see in the video below, the issues does not happen every single time, but usually when navigating from About to Home, since About contains an SVG with an out transition. It never happens when navigating from Home to About, since Home does not contain a transitioning element.
https://github.com/user-attachments/assets/9c1cda98-80df-44f4-bcfb-c6986255aff5
Reproduction
https://www.sveltelab.dev/w49gnj29qhqvsby
Logs
No response
System Info
System:
    OS: Linux 5.15 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (16) x64 Intel(R) Xeon(R) W-11955M CPU @ 2.60GHz
    Memory: 4.90 GB / 15.23 GB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 20.17.0 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
  npmPackages:
    @sveltejs/kit: ^2.5.18 => 2.5.18
    bits-ui: ^0.21.15 => 0.21.15
    formsnap: ^1.0.1 => 1.0.1
    svelte: ^4.2.19 => 4.2.19
    svelte-sonner: ^0.3.28 => 0.3.28
    sveltekit-superforms: ^2.16.1 => 2.16.1
    vaul-svelte: ^0.3.2 => 0.3.2

### Severity

annoyance

Can you reproduce this with bits-ui@next?


Logical Flows: graph should display flows for child datatypes

Currently the logical flow 'boingy' graph (the force directed graph) has a simplistic data type filter.  It does not take into account child types and is therefore misleading.  This issue will address that by making the filter aware of the parent child relationships between data types.


Merge PRs that get master back to good state

Creating this issue purely to track everything that's remaining to get master back to good state:
The e2e test on Travis has been consistently failing for several days:
https://travis-ci.org/facebook/react-native/builds
My understanding is the root cause is the interaction between these two PRs (reverting both makes npm install from master and running an app work again): https://github.com/facebook/react-native/pull/5812 (75869519e6703b5afd74dfcbcb886c73098e199a), https://github.com/facebook/react-native/pull/5813 (9f01f9677096117da8be721913a09db870505c2f).
The following PRs should get us back to good state: https://github.com/facebook/react-native/pull/6039 (depends on https://github.com/facebook/node-haste/pull/33) and https://github.com/facebook/react-native/pull/5084. Possibly also https://github.com/facebook/react-native/pull/6040.

This one too: https://github.com/facebook/react-native/pull/5811
Updates Babel to 6.5.x, which has a ton of bug fixes, and also puts React in "devDependencies" (in addition to peer) so that it works properly in Travis/Circle.

@bestander if you run into trouble when trying out npm 3.7, it's most likely because React needs to be a dev dep, which is fixed in that PR ^^ :)

:+1:

Is there anything else to do on this issue? I have just checked and all PRs mentioned here were either closed or merged.

I guess it should be good to close. Please re-open if 'm wrong.


Update KeepAliveTimeout from 300 to 5

Setting KeepAliveTimeout to a high value may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients.
https://httpd.apache.org/docs/2.4/mod/core.html#keepalivetimeout

Thanks @abhishekshah67 !


Feat progressbar config

Current coverage is 82.14% (diff: 100%)

Merging #1337 into development will increase coverage by 0.10%

@@           development      #1337   diff @@
=============================================
  Files               66         67     +1
  Lines             1904       1910     +6
  Methods             17         17
  Messages             0          0
  Branches           270        269     -1
=============================================
+ Hits              1562       1569     +7
+ Misses             248        247     -1
  Partials            94         94

Powered by Codecov. Last update d8870d6...86bc5a7


CardView is not a constructor error

Hello,
I'm using CardView with TNS 4 & Angular,
but i'm receiving this error upon initializing the page that has the CardView

Looks like a build issue that the library did not get bundled. Make sure to give this a read: https://bradmartin.net/2016/07/20/ahhh-this-nativescript-plugin-doesnt-work/_

Having the exact same problem as OP even after following the steps from your link.

Make sure to update your android build tools and support libs. I prefer android studio to manage the SDKs but can open the sdk manager via terminal also.

That didn't do it for me. Using the nativescript angular template and newest Android SDK.

Hi, @bradmartin. I'm facing this error in NS Playground site. It works fine for iOS only. Any thoughts?

Don't know if adding native deps is supported by the playground. I would assume no for security reasons and technical challenges of allowing libs to be pulled in at random by adding a dependency to the playground project which would need to be compiled. iOS is all in JS so no native deps. @carloscabral hope that helps and makes sense 😄

It does make sense. Thank you, @bradmartin.

Make sure to update your android build tools and support libs. I prefer android studio to manage the SDKs but can open the sdk manager via terminal also.

@bradmartin there is a way to do this works on NS Playground?

It does make sense. Thank you, @bradmartin.

Fala @carloscabral , você conseguiu fazer isso funcionar no NS playground?


Wrong structure in rendering of header

The contentelements has to decide, how to render the  header and subheader

fixed with https://github.com/FriendsOfTYPO3Headless/typo3-bootstrap-react/pull/12


fix: remove got dependency #6866

Motivation
For the solution of #6488
Description
Changed all codes which use got to fetch module.
Closes # #6488
Steps to test or reproduce
yarn build
yarn test:unit

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

The correct way to remove a dependency is to use the yarn remove command.

@jeluard is there a difference between that and just removing it from package.json + running yarn install afterwards?

The correct way to remove a dependency is to use the yarn remove command.

@jeluard is there a difference between that and just removing it from package.json + running yarn install afterwards?

Probably not, somehow it feels safer to use yarn remove :)

The correct way to remove a dependency is to use the yarn remove command.

@jeluard is there a difference between that and just removing it from package.json + running yarn install afterwards?

Probably not, somehow it feels safer to use yarn remove :)

Sorry, should delete by yarn remove

closing as stale


agent: Rollback properly when container creation fails

In case the container creation fails, we need a proper rollback
regarding the mounts previously performed.
Fixes #195
Signed-off-by: Sebastien Boeuf<EMAIL_ADDRESS>

@egernst @bergwolf PTAL

lgtm

@laijs @bergwolf PTAL


[Vulkan] fix vkDescriptorPool thread unsafety issue

vkDescriptorPool guards free's and resource tracking with a lock but doesn't guard the actual allocation of memory.
To illustrate this, run something like this from the NeoDemo sample (with preferred backend set to Vk). It should crash with undefined behaviour within a minute (usually a false 'pool out of memory' error). After this lock is added it will no longer crash.
`
void CrashMe()
{
   void ThreadProc()
        {

            ResourceLayout rl = _gd.ResourceFactory.CreateResourceLayout(
                new ResourceLayoutDescription(
                    new ResourceLayoutElementDescription("sampler" + System.Threading.Thread.CurrentThread.ManagedThreadId.ToString(),
                    ResourceKind.Sampler, ShaderStages.Fragment)));

            while (true)
            {
                Console.WriteLine($"{System.Threading.Thread.CurrentThread.ManagedThreadId} creating rset");
                _gd.ResourceFactory.CreateResourceSet(new ResourceSetDescription(rl, _gd.PointSampler)).Dispose();
            }

        }

        System.Threading.Thread WorkerThread = new System.Threading.Thread(ThreadProc);
        WorkerThread.Start();

        for (var i = 0; i < 25; i++)
        {
           new System.Threading.Thread(ThreadProc).Start();

        }
        WorkerThread.Join();

}

`

Thanks for the fix here. Pushed this to master.


Artifacting with older GPU hardware (AMD)

i7-7700k
Radeon 6870 w/ 1GB GDDR5
AMD 15.7.1 drivers
Click here to play freezes with GPU enabled
Turned GPU off, can log in, turn it back on and experienced lots of artifacting.

GPU passes benchmarks just fine.

On close of client, this thread stays running

GPU data while artifacting

Draw distance reduced to 10:

@snapstermap
Could you post your system specs.
My guess is that you both have under 2GB VRAM.

@RuddeK OP says 1GB GDDR5, so that's likely the culprit.

2gb seems a bit much tbh, wonder why so much is needed?

Memory usage right now seems to not be optimized. I tested with a 7970 as well and it quickly eats up 3gb of vram.

Does this still happen on the latest release of RuneLite?

Does this still happen on the latest release of RuneLite?

reopen if this is still an issue


support multi select(API suggestions?)

Hi,
dose it support multi select date by click?!

Related to #11

Hi @mohammadsaleh,
This feature will be implemented soon in 1.2.0. I will be working on it 😊

@thebrodmann @mohammadsaleh I'm thinking of a great API for this feature. For now, we only have 2 main types of date picker:

Single-day selection
Range day selection
It's noteworthy that they're distinguished by isDayRange  prop. By implementing multi selection, there will be a 3rd type.  Any suggestion is welcome! maybe we would have something like a new prop e.g isMultiSelectable (and the type change for the selectedDay and selectedDayRange props). Or, we can simply support Array type for these two. Any other idea? 💡 🤔

I put my proposal for API change in #22 because it was somewhere between this issue and new issue so I just preferred to open a new issue for that.

Hi @mohammadsaleh,
This feature will be implemented soon in 1.2.0. I will be working on it 😊

Thanks ;)

Moved to #22


Implement PSBTv2

BIP 370 specifies a version 2 for PSBT that HWI should support.
Given that the PR for adding the BIP hasn't been merged into the bips repo yet, and that there are no test vectors, we should implement this for a future release when those (and hopefully Core support) are done.
This won't be an API breaking change since all we need is to support deserializing PSBTv2s and reflect them back to the user when given. Since HWI doesn't produce PSBTs itself, there won't be anything that breaks the API.

Done in #549


swing + nuxt/ssr

Hey there,
I'm having a bit of trouble dropping this into nuxt - has anyone here had any experience with ssr based apps?
Cheers

I haven't tried using this with Nuxt yet. Do you know what needs to be changed to add compatibility with SSR? Otherwise, I don't have time to work on that now, but a PR would help a lot.

I will have a few more attempts at getting this working and will let you know how I go.

@mavrick : And how did it go? I have trouble to make this lib work with nuxt.js

Just seen this today and I have this working fine in Gridsome with SSR.
All I did was include the component inside one of my own components, wrap the markup on the page of that component with  tags, and then where I include my component in the javascript change the import to look like this:
components: {     ComponentName: () =>       import('./Component.vue')       .then(m => m.default)       .catch()   },

hi guys !
did it finally work for all of you ?
I'm having some issues :-(


Comment -UI ( Back )

Sry for the Text.txt You can delete that file.

Sry for the Text.txt You can delete that file.

Just delete this file and make a commit to the same PR

give @Tushardeepak 75 points


feat: Theming - Inline svgs

would I then have to specify an INLINE_THEME.TS file to replace the icons or change the color if I, as a third party theme write was trying to create one?
I imagined it would have just been like variable as part of theme:
--icon-whatever: url("svg path blah blah blah fill="var(--some-color)"...")
and then before you insert the variables/on theme change you resolve it to the actual color


Issue with JSON decode on vgs combined stream ouput

I recently ran into a bug which is causing the lvm driver to crash unexpectedly on my systems.
I've traced it to pkg/lvm/lvm_util.go line 666, in ListLVMVolumeGroup()
STDERR and STDOUT are combined via cmd.CombinedOutput(). The vgs program may produce non-critical warning messages on STDERR which don't affect the operation of this driver. Warning messages also don't affect the return code of the vgs program. Any warning messages printed to STDERR will fail the JSON decode step in decodeVgsJSON().

Quick and dirty implementation I did to mitigate this temporarily.
diff --git a/pkg/lvm/lvm_util.go b/pkg/lvm/lvm_util.go
index 0bb4877..e9b52ed 100644
--- a/pkg/lvm/lvm_util.go
+++ b/pkg/lvm/lvm_util.go
@@ -17,6 +17,7 @@ limitations under the License.
 package lvm

 import (
+       "bytes"
        "encoding/json"
        "fmt"
        "os"
@@ -663,11 +664,16 @@ func ListLVMVolumeGroup(reloadCache bool) ([]apis.VolumeGroup, error) {
                "--units", "b",
        }
        cmd := exec.Command(VGList, args...)
-       output, err := cmd.CombinedOutput()
+       var execOut bytes.Buffer
+       // var execErr bytes.Buffer
+       cmd.Stdout = &execOut
+       // cmd.Stderr = &execErr // do something with this useful information
+       err := cmd.Run()
        if err != nil {
                klog.Errorf("lvm: list volume group cmd %v: %v", args, err)
                return nil, err
        }
+       output := execOut.Bytes()
        return decodeVgsJSON(output)
 }

@kro-cat Thank you for reporting the issue. Can it be reproduced easily? If yes, please help us with the steps.
Since you have found the fix for it also. Would you like to raise a PR for this?

@abhilashshetty04 Of course! I'll have a PR up in a bit.
I'm convinced this is a niche issue. My current hypothesis is that it's due to the fact that the host machine has a different lvm system_id than the lvm-driver container. When lvm detects a foreign system id on a volume group, it will print a warning on STDERR; this is the kind of message that led me to this issue.
Since the system id can be set when using vgcreate, this shouldn't necessarily cause problems for volume groups meant to be managed by lvm-localpv so long as I'm aware of the correct system id to set (I think, by default, it's an empty string).
I haven't tested that yet, so I can't be certain that it's entirely correct.

By "in a bit" I guess I really meant to say "when I'm confident it actually solves the problem I'm having instead of just hiding it"

@kro-cat , Thanks for replying. We pre-provision vg (volume group) anyway right?  So what do you mean by lvm-driver detects vg not managed by itself?

@abhilashshetty04
The daemonset can see the any of the host's lvm devices due to its /dev hostPath mount.
I'll try my best to explain why that might cause a problem.
In my particular use case, the host uses lvm logical volumes for its own filesystem (/var, /home, stuff like that). These volume groups cannot be managed by lvm-localpv, so I don't include them in its configuration. Additionally, the host's lvm.conf has been configured beyond defaults; notably, the hosts each have a unique systemid configured. These are the kinds of volumes whose volume groups create this issue.
When the lvm-driver pod executes vgs, it's intention is to discover the volume groups it's configured to manage. However, because the host's own volume group (and lvm.conf) are configured outside of lvm-driver, this has the potential to cause vgs (which shows all volume groups in /dev) to display warnings or errors about the differences or incompatibilities (foreign systemid, no lvmlockd, and others).

I think I should follow-up on my previous comment. The issue here is that lvm-driver crashes unexpectedly when warning messages are mixed with JSON output from vgs.
I've put a lot of effort into explaining why the warnings messages are produced, but that's not the point of this issue, nor is that necessarily an issue with lvm-localpv itself.
The PR for this issue addresses the unexpected crashing: split the STDERR output from vgs and print it to the log. This provides much-needed diagnostic information while not affecting the health of the daemonset.

@kro-cat @Abhinandan-Purkait I have the same issue with lvs and pvs. I think all commands should use RunCommandSplit instead of CombindOutput.

@Mjolkhare I think I'll set up a PR this weekend for that since I never did that refactor in pull #250, unless of course someone beats me to it.

@kro-cat Thanks for being on top of this.


Merge master to java7

This merges the current master branch into java7.

Hi @andy1138
I think there's a few things that we can do for the Scala 2.12 release (there's still time!)
In general, the master branch is in maintenance mode, I don't think there will be many commits to it. Instead, we should make the current java7 branch the main branch. I'd propose to rename the branches: master -> 1.0.x and java7 -> 1.1.x`.
For Scala 2.11, we will continue using 1.0.x. For Scala 2.12 we can then use 1.1.x versions.
But these are just the default versions shipped with the Scala distribution: we can easily cross-build and release both branches against 2.11 and 2.12 (and even include 2.10).
There's a few things that we could do for the Scala 2.12 release

Hi @andy1138
I think there's a few things that we can do for the Scala 2.12 release (there's still time!).
In general, the master branch is in maintenance mode, I don't think there will be many commits to it. Instead, we should make the current java7 branch the main branch. I'd propose to rename the branches: master -> 1.0.x and java7 -> 1.1.x`.
In terms of workflow, I think we should continuously merge 1.0.x into 1.1.x (just like this PR is doing). This way we can make sure things (like release scripts) stay in synch. We do the same in scala/scala, and also for example in the scala/scala-parser-combinators module.
For Scala 2.11, we will continue using 1.0.x. For Scala 2.12 we can then use 1.1.x versions.
But these are just the default versions shipped with the Scala distribution: we can easily cross-build and release both branches against 2.11 and 2.12 (and even include 2.10).
Once we switch make the 1.1.x branch the default, we will also see its README as the default for the repository, so we can clean up a few things.
Let me know if this all sounds good. I'm happy to do the changes (I'll @-mention you).

Hi @lrytz
Thanks for the help.
Scala 2.12 has creeped-up on me. :-)
You seem to be matching what I had in mind. The idea was to have java7 branch included with scala2.12 and also moved to 'master' (as you suggest).
The only difference is that I versioned java7 -> 2.0.x instead of 1.1.x ( showing not only code change but also when it moved from typesafe/epfl to community supported). There has already been on milestone/tagged builds under the 2.0.x numbering system.
As for what gets released with what, 1.x.x (compiled with java6)  should go with scala2.10/11  and 2.0.x' goes scala2.12+(and compiled, I assume, withjava8but could bejava7`)
As your git-fu is probably better than mine then I'm happy to let you do the changes, if not then I'll do it over the weekend.  I'm happy to tidy things up afterwards if you just want to get the basics working.
Note: there is a binary compatible break in java7 (it's still code level compatible) so mima was throwing errors when testing 1.0.x build with 2.0.x  so I ended up disabling that check on 2.x.x (java7) branch

@lrytz  :-) good timing, build has just failed, looks like binary compatibility check, I suggest disabling it for the moment its the first build for this branch.

Thanks @andy1138 for your answer!
Indeed we have to disable MiMa until 2.0.0 is out - that's very easy now, I just had to set mimaPreviousVersion := None.
Using 2.0.x instead of 1.1.x is absolutely fine.
For cross-building: the 2.12.0-M1 release still uses scala-swing version 1.0.x, so for now I'll cross-build the 1.0.x branch with 2.10, 2.11 and 2.12. The 2.0.x branch we can cross-build with 2.11 and 2.12 - maybe some 2.11 users are also interested in using scala-swing 2.0.x.
I'll move to jdk 8 for the 2.0.x branch - soon, the Scala 2.12 compiler will only run on this anyway. There's no drawback in running the 2.11 compiler on jdk 8: the resulting classes will work fine on jdk 7, so 2.11 users on jdk 7 ca use scala-swing 2.0.x.
Lots of version numbers there :)

@lrytz  Thanks for all the work :-)
I think you got the java/scala/scala-swing version numbering correct. I'm basically thinking that any changes will go into swing2.0 and backported to swing1.0 only if really asked for

absolutely, we can keep 1.0.x in maintenance mode, and backport individual
fixes on request.
On Wednesday, May 13, 2015, Andy Hicks<EMAIL_ADDRESS>wrote:

@lrytz https://github.com/lrytz Thanks for all the work :-)
I think you got the java/scala/scala-swing version numbering correct. I'm
basically thinking that any changes will go into swing2.0 and backported to
swing1.0 only if really asked for
—
Reply to this email directly or view it on GitHub
https://github.com/scala/scala-swing/pull/44#issuecomment-101811945.


No NDEF format support

Step 1: Describe your environment

OS version:   Arduino IDE
Arduino IDE version: master
MFRC522 Library version: master
Arduino device: uno
MFRC522 device: RFID-RC522

Step 2: Describe the problem
The library doesn't support NDEF format. This is a normal format for writing to a NFC tag
Observed Results:
reading auth error when dumpinfo
Expected Results:
I expect to be able to read the dump info. Maybe even decode the NDEF.

NDEF is not supported and not planned for the future.
The https://github.com/miguelbalboa/rfid/wiki mention a extension https://github.com/Gargantuanman/MFR522_NDEF .
The data on a tag is always protected by a key. The dumpinfo uses fff..f as key. Maybe there is a different key used by the NDEF specification.


Update Rolltemplate and French

@pjbehr87 I seemed to have uploaded a version missing some translation for the Rolltemplate when converting to UTF-8... Now showing in red, sorry about that.
This fixes it.


can't read api keys

I have my keys set in my fish config. I tried with and without quotes. I reset the terminal session. Weather and repos works fine. But I'm getting "Can't read Twitter without API keys" in TCT.
Node Version: 6.10.2
tiny-core-terminal version: 1.0.8
Shell: fish
Terminal Program: iTerm2
Operating System: Mac

How exactly did you set the environment variables in fish? If you do fish_config can you see them in the Variables tab listing?
Also the screenshot isn't displaying. Perhaps try re-uploading it?

Is the screenshot working now? And yes, the variables appear in fish_config.

Were the variables set with the -x option? That is what allows them to be passed to subprocesses in fish. Looking at the config area I don't see where they explicitly show this through the UX.
The screenshot is still failing with a 410 error.

Hi can you still not see the screencap above?

Have you opened a new tab or restarted your terminal, to make sure that your env variables are actually picked up?

i tried again, now nearly a year later, again, setting the variables with -x and restarting my terminal. still, the api keys were not read properly and i had to opt for scraping instead.

@selfagency Please read up on settings environment variables in fish: https://fishshell.com/docs/current/faq.html#faq-envvar
Try calling set before starting tct to make sure your environment variables are set.

i appreciate that you're trying to help, but i know how to set variables for fish. this is all in my config.fish which loads when you open a shell.
set -x TTC_REPOS dev
set -x TTC_REPOS_DEPTH 1
set -x TTC_GITBOT gitlog
set -x TTC_WEATHER 13214
set -x TTC_CELSIUS false
set -x TTC_APIKEYS true
set -x TTC_UPDATE_INTERVAL 10
set -x TTC_CONSUMER_KEY [my key]
set -x TTC_CONSUMER_SECRET [my secret]
set -x TTC_ACCESS_TOKEN [my token]
set -x TTC_ACCESS_TOKEN_SECRET [my token secret]

everything works fine except twitter which i have to set to scrape instead, otherwise i get an error.

i appreciate that you're trying to help, but i know how to set variables for fish.

:blush: Ok, Sorry!
So let's assume it has nothing to do with the environment variables.

I'm out of ideas here...Maybe generate a new api kay at twitter? Or try your existing key/secret with another app!?

it was a brand new app with a brand new set of keys.

You got me interested, so I installed fish (wich is nice by the way).
I had no problems with the twitter-API or anything else.

closing this because it's 4 years old, twitter banned me for fighting with the nazis they refuse to ban, and i want to clean up my issues tab


[Feature#7441][Doc] Seatunnel Suppoorts Doris connector

It is recommended to give a complete usage example, including the installation and deployment of SeaTunnel (document connection can be given), combined with a Mysql or other data source for ETL and access to Doris, which can be used as a reference for users in the future


[WIP] Add Calico e2e Test

What this PR does / why we need it:
Adds an end-to-end test to validate kubernetes network policy is working when calico network policy is specified.
Add calico network policy e2e test

@jackfrancis so it works as-is?  If so, I'll just remove the [WIP] from the title and you can merge :)

got into rebase hell, see #3146

Understandable, bummed I haven't had a chance to pick this back up.  Hope we can get it in the pipeline soon 👍


Paused subscriptions do not reactivate automatically

PHP Version
8.2.9
Shopware Version
<IP_ADDRESS>
Affected area / extension
Platform(Default)
Expected behaviour
According to the documentation, paused subscriptions do reactivate themselves automatically after one skipped delivery.
Actual behaviour
Paused subscriptions remain paused until they are reactivated manually either front-end by the user or backend by staff.
How to reproduce
Create a subscription
Pause the subscription
Wait until skipped delivery has passed
Check if subscription has reactivated

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-38116
[created from NEXT-38116, comment 491684]

[public]

FixVersion Change: <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>

This issue will be / was solved in Shopware version <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>.
[created from NEXT-38116, comment 510419]

[public]

FixVersion Change: <IP_ADDRESS>, <IP_ADDRESS>

This issue will be / was solved in Shopware version <IP_ADDRESS>, <IP_ADDRESS>.
[created from NEXT-38116, comment 510458]


Merge camunda8-greenfield-installation

This PR will merge the Camunda 8 greenfield repo into this repo. Moving forward it will be easier to maintain a single repository containing scripts for creating Kubernetes clusters as well as scripts related to managing Camunda helm charts.
Please see this issue for progress.

Oops, I didn't mean to push to master just yet! Reverted master back, this PR is technically still open.


Plugin API references + splitting ACL and ACME plugins to test

Description
Adding the ability to split plugin content into API reference docs and splitting two plugins as examples.

API Reference pages: I tried implementing this in a couple of different ways and came around to just having one top-level API reference link in the side navigation instead of a Reference section. I did this for a few reasons:

Less clicks: people are already complaining about the nested config ref content, and we're also nesting "Using this Plugin"
Easy to find critical info
Most plugins don't have a lot of reference content beyond API stuff. I wonder if non-API references can be nested under the "Using this plugin" section.

Split out content from the Overview pages into Using this Plugin and API Reference pages.

Also added a notice for users looking for the config ref, as we've gotten reports that existing users are confused about where to find it and aren't used to all the clicks (probably should've done this in a separate PR, really)

❗ Reviewers: this needs review from a bunch of angles: technical, information architecture/UX, and general visual cohesiveness. Pinging the team for some different points of view :)
Testing instructions
Netlify links:

https://deploy-preview-5660--kongdocs.netlify.app/hub/kong-inc/acme/
https://deploy-preview-5660--kongdocs.netlify.app/hub/kong-inc/acl/

Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

@lena-larionova Overall, I really like the API reference getting split out into it's own section. I also like the separate "Using this Plugin" section. I found myself wondering what the difference was between the pages in "Using this Plugin" and the "Configuration > Example" page. I almost feel like that Example page could be moved as the top page to the "Using this Plugin" section and renamed something like "Basic configuration" since it seems more similar to those pages than the Configuration pages? So something like:

Overview
Configuration parameters (maybe?)
Using the plugin

Basic configuration
[insert specific use case here]

API reference
Changelog

I almost feel like that Example page could be moved as the top page to the "Using this Plugin" section and renamed something like "Basic configuration" since it seems more similar to those pages than the Configuration pages?

I'm really glad to hear you say this, because this has been bothering me as well ([literally just talked about this morning(https://kongstrong.slack.com/archives/G012HLJ4GJJ/p1685729858788559?thread_ts=1685723589.130179&cid=G012HLJ4GJJ)). So it sounds like you're seeing the same issue with the current layout.

@fabianrbz I think this is finally ready to go. I made a couple of small tweaks:

Made sure that the "Using this plugin" section will always appear in Kong plugins, since we're nesting the examples in it now
For third-party plugins, made the examples a top-level item. We can always change it in the future, but the aim is to make it as simple as possible for contributors, which means avoiding any extra markdown files.

Any reviewer, check the following:

Any Kong plugin has a "Using this plugin" section with examples in it, eg basic auth
Third-party plugins with examples have a "Basic config examples" nav entry, eg Imperva
Third-party plugins without examples don't have examples in the nav, eg Wallarm


Width and height settings in the config.

the width and height config settings should be
maxWidth instead of width
maxHeight instead of height

@jfdor1975  You are rigth!
Why dont send a Pull Request? I'll like to merge


No examples for C++/winRT

What one needs to do for C++/WinRT UWP can look quite different than C# and it would be REALLY, REALLY helpful if C++/winRT examples were provided.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cedb9559-6da0-2e91-eaef-12d9e9bfff4f
Version Independent ID: cf9ff409-0028-5b6c-b77e-3987ad23671d
Content: BluetoothLEDevice.FromBluetoothAddressAsync Method (Windows.Devices.Bluetooth) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.devices.bluetooth.bluetoothledevice.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: eliotcowley
Microsoft Alias: elcowle

Hi, @brianreinhold. Thanks for filing this issue, and my apologies for the long delay in responding.
You're right, the two languages do look very different, syntactically. Until we have a C++/WinRT code example in this topic, one suggestion would be for you to study the C++/WinRT documentation, which contains lots of code examples showing many different techniques for calling Windows Runtime APIs from C++. It's likely that you'll learn enough there to use these APIs from C++/WinRT and/or to convert any C# code to C++/WinRT. In addition, fyi, any topic (across the Windows dev content) that has a C++/CX code example now also has a C++/WinRT code example.
Thanks!
Steve

I'll go ahead and close this issue now. Please reopen if I made a mistake in closing. ~Steve


fix(fun_prop): improved handling of terms mixing lambdas and lets

fun_prop: Improved handling of lets and fvars

improved handling of terms mixing lambdas and lets
make sure that fvars are unfolded only when necessary

Right now fun_prop beta reduces the function body but it does not work when the function mixes lets and lambdas. This does not work
example (a : ℝ) : Continuous (fun x0 : ℝ =>
  (fun x =>
    let y := x + x
    fun z : ℝ =>
      x + y + z) x0 a) := by fun_prop

This patch fixes it.
Also local theorems about let fvars were not used properly. For example here the final call to fun_prop does not use h but it unfolds f and reproves everything from scratch again
example (y : ℝ):
  let f := (fun x y : ℝ => x*x*y)
  Continuous (fun x => f x y) := by
  intro f
  have : Continuous f := by fun_prop
  set_option trace.Meta.Tactic.fun_prop true in
  fun_prop

This patch fixes it.

bors merge

bors r+


[feat] Handle multiple deployments on the same day

Today, the dashboard is based on one deployment per day.
If we have multiple deployments on the same day, it can mess up the dashboard.
We should use an external id which would be the current date, and perform an upsert instead of insert in the scripts

https://github.com/tprouvot/apex-analysis/commit/0cbe2f40d52ce9f78c208c6e4b107ac529dd5560


Table calendar and Date Picker

Calendar view base on: https://pub.dev/packages/table_calendar

so, you decided to combine DatePicker and Calendar in one PR?

so, you decided to combine DatePicker and Calendar in one PR?

both need the same change in package/lib/src/models/control.dart so otherwise will be conflict in merge

Please reviewers merge this PR . This is very userful.

It's not ready for the merge: there are conflicts and CI is failing.

any updates?

Close in favor of #1998
Will open a new PR if decide to implement https://pub.dev/packages/table_calendar


Adding threshold (or not) option for the sct_deepseg_gm

This is a pull request to add an enhancement (related issue #1831).
There is now a new parameter on the sct_deepseg_gm command-line tool called -thr where the user can specify a custom threshold to be applied in the predictions of the model. For backward compatibility, this threshold is always active with the recommended value of 0.999, but now the user can specify a different threshold or even disable it with -thr 0.
PS: just fixed some long running strings as well.

Pull Request Test Coverage Report for Build 8809

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.294%

Totals

Change from base Build 8802:
0.0%

Covered Lines:
124

Relevant Lines:
140

💛  - Coveralls


Generic way of adding style overrides

Each element needs some way to override the styling; some concepts are already present in the itemfilter, but no default has been developed yet.
Related to the question of shadow vs. non-shadow.

Interesting summary here: https://nolanlawson.com/2021/01/03/options-for-styling-web-components/

Theming done via style variables in https://github.com/EOX-A/EOxElements/pull/616


Tag last commit which supported compiling iRODS 4.2.12

feb3d83165155d84df67b27fe9806cdfa7a4d506 works for CentOS 7.
This is primarily about compiling for Ubuntu 18.04. Below is the output I get.
=========================================
beginning build of iRODS server
=========================================
+ cd /irods_build
+ cmake -GNinja -DCMAKE_BUILD_TYPE=Release -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_CXX_COMPILER_LAUNCHER=ccache -DIRODS_UNIT_TESTS_BUILD=YES -DIRODS_MICROSERVICE_TEST_PLUGINS_BUILD=YES /irods_source
-- Setting CLANG_STATIC_ANALYZER to 'OFF'.
CMake Error at CMakeLists.txt:146 (message):
  Linux platform name detection failed

  No such file or directory

-- Configuring incomplete, errors occurred!
See also "/irods_build/CMakeFiles/CMakeOutput.log".
See also "/irods_build/CMakeFiles/CMakeError.log".

What is the SHA of the first failure?

It's 1403c26dd750236fff1a8c0041674989d40e88af.
Now we need to settle on a naming scheme since this issue is specific to Ubuntu 18.

perhaps ub18-eol or ubuntu18-end-of-life?
on the last good ub18 commit?

oh, we're trying to convey both ubuntu18 and 4-2-stable...

Right.
So maybe 42s-ub18-eol?

all the letters...
42stable-ubuntu18-end-of-life or, perhaps better, end-of-life-42stable-ubuntu18.
thinking about when we have a number of these over time.

I definitely like the order of the elements. I don't care for spelling out EOL as I think that abbreviation is pretty common, but that's a personal thing. I think git's auto completion helps with that too.

which order?   end-of-life-42stable-ubuntu18 ?
regarding spelling it out... i think EOL is stronger than eol, but capital letters in a git tag feels... wrong/weird.

So with the abbreviation...
eol-42stable-ubuntu18 or EOL-42stable-ubuntu18
I like that the hyphens clearly separate the elements.

agreed on the hyphens as dividers.
are we okay with capital letters?  i think they look fine.
let's go with EOL-42stable-ubuntu18.

Capital letters do seem weird for a git tag, but considering what they are for, it seems okay. As long as there's a convention and it conveys what it's for, I'm fine with it.
I agree. that works for me.
@alanking @SwooshyCueb Any thoughts on the conversation here?

To be clear, we are suggesting tagging the last commit that is able to build packages from irods/irods 4-2-stable branch on the Ubuntu 18.04 core builder with EOL-42stable-ubuntu18?
Seems alright to me.

correct.   and we'll start a practice of doing the same for the other stable/version combos as we come upon them.

Agreed.

Tagged the last working commit.
Closing.


Injector graph looks wrong

This is not a new bug, I believe we've always showed things this way.
In the Augury demo Form app, Augury incorrectly shows "NewUserService" being injected by the AppComponent, this is really not the case.
The NewUserService belongs to the entire app, which is getting injected by the "Root injector". This is defined in App's NgModule.

We need another way to show this, maybe another level simply labeled the "Root Injector"? In the demo app, AppComponent does not make use of or provide the service "NewUserService".
If you look at the code both UserInfoComponent and FormNewUserComponent use DI to create NewUserService in the constructor, which is coming from the "Root injector".
Looking at the Injector graph, I start to think the NewUserService service as being provided at the app level via a meta-data property in the decorator like:
@Component({
...
 providers: [NewUserService],
...
})
export class AppComponent

This is not the case.

@rajinder-yadav Yes, that's because the old injector graph was showing that it was 'provided' at that level (for reasons I never quite grasped). I've included screenshots of what it looks like with the new injector graph.

This is resolved now with the injector graph improvements in #867


Please help me how to use "react-native-router-flux" in my scenario

Hi Pavel,
Please help me how to create two tabs for its parent button or router button.
Please see attached screen grab.

.
Thanks,
Bhanwar

Have you tried A nested tabbar?

Yes, but it's not working.

Sorry, probably it is out of scope for RNRF - as I see underlying react-navigation doesn't support nested tabbars in good way (if you can implement it with pure react-navigation but cannot with RNRF - share your code then). I'd use react-native-tab-view for inner tabs.


I can't read sensor data on windows

hi all;
I read the heat data from the sensor with macos perfectly, but when i try with windows computer this data comes "nan"
I share below the serial monitor  and serialport.js output images for windows and mac.
As seen in the last image, the data comes to "nan".
arduino serial monitor (macos) it's correct

================================
data read via serialport package with electron app (macos) it's correct

================================
putty serial monitor COM8 (windows) it's correct

================================
data read via serialport package with electron app (windows) it's not correct

arduino code (sender)

    float t = dht.readTemperature();
    if (isnan(t))
    {
        Serial.println(F("Failed to read from DHT sensor!"));
    }
    String tempData =  String(t);
    Serial.print("Temperature:");
    Serial.println(tempData);

serialport app code (receiver)
import SerialPort from 'serialport';
import Readline from '@serialport/parser-readline';

const port = new SerialPort(portName, {
  baudRate: 115200
});

const parser = port.pipe(new Readline({ delimiter: '\r\n' }));

parser.on('data', data => {
  console.log(data);
});

how can i fix this :/

ohh i found it.
I use the D3(0) pin of my device (reference)
I guess serialport package is doing kind of process with this pin on windows computers.
(Does anyone know about this?)
When I changed the sensor pin, i started receive healthy data.
Thanks..


Faster LinkedHashMap tail()

Change: LinkedHashMap tail() no longer copies the entire datastructure.
Motivation: We have a use case which looks somewhat like the following.

It's effectively a Queue use case (fifo).
Iteration order needs to be stable.
Elements in the queue frequently need to be verified as present in the queue.
Occasionally, removals must occur, which are usually from the head of the queue although occasionally randomly.

We started with a Queue and eventually found performance issues from too much linear scanning. This was not obviously going to be a bottleneck since our queues are usually of very small size, but ended up so. The next type we considered was a LinkedHashSet, using the head and tail methods to implement a dequeue-like operation and the set operations being sufficient for the other operations. Unfortunately, it seems that tail at present copies the entire queue despite not seemingly needing to.
We moved to our own hand-crafted HashSet+Queue structure, but this PR seems like it'd generally be beneficial for users of Vavr! It affects LinkedHashMap, and because LinkedHashSet contains a LinkedHashMap, LinkedHashSet, too.

Thanks, Daniel! I appreciate the fast review + merge! When should I expect this code to be in a release?

You're welcome. I can prepare a patch release this week!


Add openfga package

Description of changes
Add openfga to Nix packages repository. Will resolve https://github.com/openfga/openfga/issues/1048
It's my first time contributing to the nixpkgs repository, so I've added myself as a maintainer too. Let me know if I've missed anything. One question I have is - should I force the output of go build command to be in ./result/bin/ directory? Currently resulting bin ends up in ./result.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@lolbinarycat I just realised there were a couple of PRs opened over recent weeks for adding openfga (https://github.com/NixOS/nixpkgs/pull/295024, https://github.com/NixOS/nixpkgs/pull/297676) @lucperkins, @gaelreyrol I guess we should pick one?

I've closed my PR in favor of either this one or https://github.com/NixOS/nixpkgs/pull/297676. My vote is still for https://github.com/NixOS/nixpkgs/pull/297676 due its more comprehensive nature but will defer to others!

It seems there's been another PR merged in the meantime: https://github.com/NixOS/nixpkgs/pull/310534

Superseded by https://github.com/NixOS/nixpkgs/pull/310534


Multiple requests urls get concatnated resutling a URL not found and subsequent exceptions

This is running on ubuntu 16.04.4, kernel 4.13.0-39-generic, python 3.5.2
load generator: https://github.com/sc2682cornell/wrk2 running command
./wrk -t8 -c32 -d30s -R8000 http://ip:8080/get/256
The server runs following simple code:
app = Sanic('name')
buf = None
with open('./test_data/256.dat', 'rb') as fin:
     buf = fin.read()

@app.route('/get/<file_size:int>')
async def get_file(request, file_size):
    return response.raw(buf)

app.run('<IP_ADDRESS>', port, workers=32)

The error message I got:
[2018-04-30 23:02:32 -0500] [18297] [ERROR] Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/sanic/app.py", line 546, in handle_request
    handler, args, kwargs, uri = self.router.get(request)
  File "/usr/local/lib/python3.5/dist-packages/sanic/router.py", line 344, in get
    return self._get(request.path, request.method, '')
  File "/usr/local/lib/python3.5/dist-packages/sanic/router.py", line 393, in _get
    raise NotFound('Requested URL {} not found'.format(url))
sanic.exceptions.NotFound: Requested URL /get/256/get/256/get/256 not found
[2018-04-30 23:02:32 -0500] [18281] [ERROR] Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/sanic/app.py", line 546, in handle_request
    handler, args, kwargs, uri = self.router.get(request)
  File "/usr/local/lib/python3.5/dist-packages/sanic/router.py", line 344, in get
    return self._get(request.path, request.method, '')
  File "/usr/local/lib/python3.5/dist-packages/sanic/router.py", line 393, in _get
    raise NotFound('Requested URL {} not found'.format(url))
sanic.exceptions.NotFound: Requested URL /get/256/get/256/get/256/get/256/get/256/get/256 not found

I problem I see here is that the requested URL is concatenated with multiple requests while the load generator only sends requests for /get/256
And some subsequent errors like:
AttributeError: 'NoneType' object has no attribute 'should_keep_alive' at server.py:122
local variable 'keep_alive' referenced before assignment at server.py:356

is the load generator reliable https://github.com/sc2682cornell/wrk2 ? can you try wrk or wrk2 ?

I can confirm same problem when benchmarking Sanic with wrk2. I'm on Ubuntu 16.04.4 with Python 3.6.3.
./wrk -t 1 -c 1 -d 1 -R 500 http://localhost:8000/api/item/banana

[2018-05-06 00:41:19 +0300] [2713] [ERROR] Traceback (most recent call last):
  File "/home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/app.py", line 546, in handle_request
    handler, args, kwargs, uri = self.router.get(request)
  File "/home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/router.py", line 344, in get
    return self._get(request.path, request.method, '')
  File "/home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/router.py", line 393, in _get
    raise NotFound('Requested URL {} not found'.format(url))
sanic.exceptions.NotFound: Requested URL /api/item/banana/api/item/banana not found

[2018-05-06 00:41:19 +0300] [2713] [ERROR] Invalid response object for url None, Expected Type: HTTPResponse, Actual Type: <class 'sanic.response.HTTPResponse'>
[2018-05-06 00:41:19 +0300] [2713] [ERROR] Traceback (most recent call last):
  File "/home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/server.py", line 335, in write_response
    keep_alive = self.keep_alive
  File "/home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/server.py", line 122, in keep_alive
    self.parser.should_keep_alive())
AttributeError: 'NoneType' object has no attribute 'should_keep_alive'

Task exception was never retrieved
future: <Task finished coro=<Sanic.handle_request() done, defined at /home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/app.py:519> exception=UnboundLocalError("local variable 'keep_alive' referenced before assignment",)>
Traceback (most recent call last):
  File "/home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/app.py", line 590, in handle_request
    write_callback(response)
  File "/home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/server.py", line 356, in write_response
    if not keep_alive:
UnboundLocalError: local variable 'keep_alive' referenced before assignment
[2018-05-06 00:42:19 +0300] [2713] [ERROR] Traceback (most recent call last):
  File "/home/shk/Documents/Work/AKB/akbhelp/backend/.venv/lib/python3.6/site-packages/sanic/server.py", line 178, in response_timeout_callback
    raise ServiceUnavailable('Response Timeout')
sanic.exceptions.ServiceUnavailable: Response Timeout

A little bit digging gives me following:
In some pathological cases, when function data_received at server.py:206 is called from some uvloop function.
The data object passed into this function actually consists multiple reqeusts: (e.g)
b'GET /test/ HTTP/1.1\r\nHost: <IP_ADDRESS>:8080\r\n\r\nGET /test/ HTTP/1.1\r\nHost: <IP_ADDRESS>:8080\r\n\r\n'

which results in an invalid URL request of /test//test/

I closed the corresponding uvloop issue. The actual problem here is that httptools doesn't support (or does it?) HTTP pipelining.  Unfortunately I don't have time to look at httptools myself at this moment.  Any further investigation/PRs are welcome.

Yeah, looks like an issue of httptools. But We don't gain a lot from Http 1.1 pipelining though. It'd be better to support http2.

Closing this since pipelining support will be available once we implement ASGI (coming soon).