Add eventignore to prevent autocommand triggering

Fixes #43
Added appropriate eventignore settings wherever  is used to prevent `Insert{Enter,LeavePre,Leave} autocommands from running. Currently feels a little verbose, would be nice if a better solution can be found

Got it. I didn't realize <cmd> was that new. I'll work on a wrapper. Might take a couple of days though, have a slightly packed schedule right now

Quick update, I've spent some time working on this, and there doesn't seem to be a way to leave and re-enter insert mode without triggering autocommands if <cmd> is not used (my understanding is that it was introduced to solve issues like these). The closest I got was eliminating the insertleave autocommands, but insertenter is still triggered

Until a better solution is found, would you consider implementing a fix with <cmd> on a separate branch, with a notification regarding compatibility?

Sounds like a good idea. And nice catch btw - didn't notice that both <C-r> and <C-o> triggered autocmds. That means there's no backwards compatible fix for it.
That means some type of compat branch is the best option, though I haven't entirely made up my mind on how I wanna structure that. Could merge it into 4.0.0, could make a separate branch... lots of options here.
A separate branch would have the major benefit of providing compatibility without the potential breakage 4.0.0 could cause. I'll have to decide on this tomorrow, but a different branch sounds good to me

Tomorrow became in two days because reasons, but I actually came up with an alternative. Let's make use of variables instead: a string containing cmd and eventignore, with one for enabling and one for disabling. That avoids redundant copy-pasta, and we can leave the string empty if the cmd patch isn't included. Probably need to make the SID for return or whatever execute for that to work, but it's a minimal fix, and means it automatically activates in versions of Vim that support it (I.e. no need to mess around with branches to get an applicable version more than necessary). Not sure how long a version check would be applicable though, but I at least want it around until the next major version. That's not something we need to worry about here though

Okay so your last comment got me thinking, and I came up with a working solution to properly set eventignore without using <cmd>. It still uses global state to restore the previous value of eventignore, but overall it works and it should also be fairly simple to update it to use <cmd> later by only modifying the wrapper. Take a look and let me know if it seems okay, and if it does, whether I need to move stuff around or make changes to follow conventions

(Side note, it appears <C-r>= does not trigger insert{leave,enter} autocommands)

Looks like older (not sure what that means; breaks on 8.2.950 on my pi, fine locally on 8.2.3458, nothing breaks in the  docs) chokes on InsertLeavePre. Does it still work properly with just InsertLeave? Suspecting InsertLeavePre is classified as "a part of" that event in older versions

Okay, I've added some comments where we can update the implementation later down the road, and it should work in general now

LGTM. Final change request before merging though, I believe the last key we need to do anything with is <BS>. The original bug report indicated that this happened when pressing backspace. If any keys causing a mode switch are missed after fixing <BS>, I'd rather just leave that until reports surface. Or testing is added, though that's not an immediate concern either.
But yeah, when <BS> is handled, assuming it doesn't break the tests (which I don't believe it should, considering none of the other keys broke any tests), I'll merge it in.
Thanks again!

I recall trying it out with <BS> and not being able to reproduce the issue. Will try it out again and handle it if required

Yep, just verified again. Both with and without g:AutoPairsMapBS set, no insert autocmds are triggered on <BS>. Also did a cursory check through the codebase, no mappings seem to leave insert mode while handling <BS>, so we should be good. As you said, we can check again if reports surface with more specific details.

Yep, sounds good to me


After Insert Trigger request

Is your feature request related to a problem?
Hi I tried to find perfect alternate method of after insert trigger like mysql in opensearch.
https://www.javatpoint.com/mysql-after-insert-trigger
Also checked the document level monitoring - (https://opensearch.org/docs/latest/monitoring-plugins/alerting/monitors/#per-document-monitors). But couldn't able to find any suitable alternatives.
What alternatives have you considered?
For now I'm considering to try using the cloudwatch logs of opensearch insert, update happenings & try an invocation using the logs.

This is currently out of scope for the Alerting plugin due to scale of data volume and big performance implications to execute the monitor whenever a new record is inserted in the index. Document level monitors will be close to that, but can only get executed every minute and will ensure it will only looks at the newly indexed data.


Respect the users ARFLAGS

A follow-up to #601: CMAKE_STATIC_LINKER_FLAGS are supposed to be passed to the archiver, the name is wrong for backwards compatibility reasons.

Changelog entry please :)

Changelog entry please :)

I would prefer to restrict changelog entries to user facing changes, with "user" meaning the role. If we put in minor things like this the changelog will get very long, and people will lose interest before reading all the way to the bottom.

I see your point. However, having a small amount of bugfixes in there creates a "warm fuzzy feeling" that the product is evolving. As long it's not resulting in distraction and is relevant to the user, it's important to not brush these under the carpet. Here, a crash caused by a certain input strikes me as noteworthy information.

Here, a crash caused by a certain input strikes me as noteworthy information.

That's #603. This one is just a fix for people who have custom LDFLAGS or ARFLAGS.

Looks great, thanks!

I have rebased this to fix the conflict on recent master.


[apostrophe-schemas] The last item of an array currently can't be deleted & saved as deleted.

The populate and convert methods for the schema fields in the array still are running, even when the array has no items.

Resolved in #513


Assignment operators?

   self.pos += Vector(*self.velocity)
   File "kivy/properties.pyx", line 497, in kivy.properties.Property.__set__
   File "kivy/properties.pyx", line 1353, in kivy.properties.ReferenceListProperty.set
   File "kivy/properties.pyx", line 1337, in kivy.properties.ReferenceListProperty.convert
 ValueError: PongBall.pos must be a list or a tuple

is the error that occurs when I change this self.pos = Vector(*self.velocity) + self.pos to this self.pos += Vector(*self.velocity)...  I do understand this is technically a list/vector but I think it would work.  I understand you've made __iadd__ be a unit addition, I suggest you look into using the __matmul__ operator.  At the moment this is very frustrating.
So first off I guess you should move __mul__ to __matmul__ and change all the __i*__ operators to actually make coding cleaner.  Maybe leave __r*__ methods to allowing interger/float operations.
I would like to know the design decision behind this

I am very confused why you are talking about __matmul__ here when there is no multiplication, let alone matrix multiplication here. There generally isn't enough context to understand this.
Please consider posting a short complete program we can test, or even better, a PR with your proposal.


docs: fix-sample chart config

Thank you for such a nice library! I'm using it for my private project.
I found a small mistake in README.md. Please check it 😉

great, thanks


Connect problem

Hi,
I've got problem, I can only connect to server when I've got open "Preferences" tree view.

Please remove this package and install new Remote-FTP version.
If the problem persists, report it again.


fix: fix coderabbit config

to exclude a path, it should start with ! in path_filters
tested in this PR: https://github.com/zeta-chain/protocol-contracts/pull/202

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 59.25%. Comparing base (a8343cb) to head (574a9e4).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #207   +/-   ##
=======================================
  Coverage   59.25%   59.25%
=======================================
  Files          31       31
  Lines        1048     1048
  Branches      217      262   +45
=======================================
  Hits          621      621
  Misses        427      427

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


FAILED TO GET CERTIFICATE INFORMATION

I receive the below error when attempting to run this for my customer. Any ideas?

Errors:
mail.customer.com.au:ipaddress :: FAILED TO GET CERTIFICATE INFORMATION

@lukejtm I'd guess that a certificate could not be found or it could not be parsed. Not sure I can provide much more guidance or debugging without knowing the domain.

I resolved the issue by enabling TLS1.0 in my openssl.conf


Fix a build warning in the git status plugin.

#102 introduced a warning when building the GitStatus executable, which we use to get repo information during building:

[!WARNING]
swift-testing/Sources/GitStatus/main.swift:65:24: warning: no calls to throwing functions occur within 'try' expression
    guard let output = try? stdoutPipe.fileHandleForReading.readData(ofLength: maxOutputCount) else {
                       ^

This PR resolves the warning.
Checklist:

[x] Code and documentation should follow the style of the Style Guide.
[x] If public symbols are renamed or modified, DocC references should be updated.

@swift-ci please test


KOGITO-7418 - Move predictions to kogito-predictions-api

Jenkins rerun kogito-apps tests

Jenkins run native

Jenkins run kogito-apps native


Is this project unmaintained?

I don't see any activities regarding pull requests and issues in this project. @davidhellsing @sorl which way will galleria go? Do you need help?

I switched to http://photoswipe.com/ =/

@cussack I believe with the MIT license in place you could always fork the project and maintain your own version.  It doesn't seem to have gotten any attention in a couple of years, so if you have changes in mind that would be one way to do it.

Are there any recommendable forks, yet?
(For example, fixing the YouTube issue https://github.com/aino/galleria/issues/357?)
Cheers!

we're the new maintainer, aino transferred the project over to us. expect a major release version in the near future.


chore: Refactor example typescript stack by extracting a base class

What does this PR do?
Right now
class CdkTypeScriptStack extends Stack

This PR adds a class CdkTypeScriptStackBase, and makes:
class CdkTypeScriptStackBase extends Stack

and
class CdkTypeScriptStack extends CdkTypeScriptStackBase

CdkTypeScriptStackBase contains the setup of AWS resources, not related to Datadog.
CdkTypeScriptStack contains Datadog instrumentation code.
Motivation
I'm going to rename the interfaces like I did in https://github.com/DataDog/datadog-cdk-constructs/pull/288. To make sure both the new API and old API work, I will need to to write two stacks for testing the two APIs. The two stacks will share the non-Datadog setup code, so I'm putting this part in the base class.

Testing Guidelines
cdk deploy successfully deploys the TypeScript stack.

Additional Notes

Types of Changes

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[x] Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

[x] This PR's description is comprehensive
[ ] This PR contains breaking changes that are documented in the description
[ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
[ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
[ ] This PR's changes are covered by the automated tests
[ ] This PR collects user input/sensitive content into Datadog

/merge


a lot of websocket traffic after some time when a lot of generated tags are present

I received about 30-40 MBit of Websocket Traffic for autogenerated tag updates in a tab that was open for a long time, refreshing page fixed it.

100000 streamids in a generated tag mark were resent over the websocket everytime a new stream got added to the tag. We should only send the difference of the added/removed streamids instead of all of them all over everytime the tag changes.


Dynamic Forms Step

Description
Create RainCatcher step implementation that will allow developers to use to use angular4 dynamic forms.
https://github.com/udos86/ng2-dynamic-forms

Outdated.


Track blocked by stationary wagon, order cannot be carried out

Jobs don't invalidate when you leave the station with PJ, so you could have just pulled them away (and later back if you like), as the LH you delivered was unassigned afterwards anyway.
There's only two track requirement for wagons: when (un)loading and when delivering the job. Everything else is your responsibility as there is no "magic shunting crew" anymore that frees up the tracks like in vanilla
Generally its a good idea to start new games when you install major mods like that, in case of PJ it should still work with existing savegames though. as long as you dont do anything crazy

I'm closing this as I think it's either a user fault or a border effect when enabling PJ with an already existing savegame. Either way, such situations can be resolved by moving the blocking waggons away from the target track.


READme.md mistake in Gujarati translation and also add hindi translation

This are some few snapshot.
Also add hindi readme.md file

see pull request #150

✌


Usecase: scheduling

How can we enable people to automate their calendars?
This task involves creating recordings involving one or more relevant applications, and implementing tests for corresponding completions:

Gmail/Google Calendar
Outlook
what else?

Many of the current "AI-powered calendars" interface with the user's existing calendar and automatically schedule events given user preferences, considering buffer times, traffic, etc. I wanted to find automation opportunities that are currently not being implemented by current apps on the market. I would implement OpenAdapt's scheduling automation by interfacing with the relevant APIs below, then call a given "booking", "email response", etc. workflow.
Task Possibilities:

interface with Zoom, Google Meet, Microsoft Teams to automatically sign-in/start the meeting without having to go back to the email/calendar to retrieve the link
automatically send an email to the event attendees if the user is running late (online: the user is not on their device (no input detected in the last x minutes; in-person: if the user's location is not within x meters of the meeting location)
going through the user's email, checking the user's calendar, automatically responding to them with availability/confirmation (eg. using the Outlook Rest API)
similarly, automatically booking weekly events, or events with a consistent location/format (eg. going to gym, coffee chats, learning how much time the user realistically spends with the event by using their location)


Update specs2-core, specs2-mock to 4.20.6

About this PR
📦 Updates

org.specs2:specs2-core
org.specs2:specs2-mock

from 4.20.0 to 4.20.6
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.specs2" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, version-scheme:semver-spec, commit-count:1

Superseded by #94.


PermissionError: [Errno 13] Permission denied: '/tmp/tmpzrluurcb/bin/python3'

Bug description
if /tmp/ is mounted with noexec you get the following stack trace.
Expected behavior
need an option to put tmp files in a different location
(venv) rdinoff@audit:~/audit$ pip-audit -r requirements.txt
Traceback (most recent call last):
  File "/home/rdinoff/audit/venv/bin/pip-audit", line 8, in <module>
    sys.exit(audit())
  File "/home/rdinoff/audit/venv/lib/python3.9/site-packages/pip_audit/_cli.py", line 509, in audit
    for spec, vulns in auditor.audit(source):
  File "/home/rdinoff/audit/venv/lib/python3.9/site-packages/pip_audit/_audit.py", line 67, in audit
    for dep, vulns in self._service.query_all(specs):
  File "/home/rdinoff/audit/venv/lib/python3.9/site-packages/pip_audit/_service/interface.py", line 154, in query_all
    for spec in specs:
  File "/home/rdinoff/audit/venv/lib/python3.9/site-packages/pip_audit/_dependency_source/requirement.py", line 134, in collect
    yield from self._collect_from_files(collect_files)
  File "/home/rdinoff/audit/venv/lib/python3.9/site-packages/pip_audit/_dependency_source/requirement.py", line 180, in _collect_from_files
    ve.create(ve_dir)
  File "/usr/lib/python3.9/venv/__init__.py", line 75, in create
    self._setup_pip(context)
  File "/usr/lib/python3.9/venv/__init__.py", line 313, in _setup_pip
    subprocess.check_output(cmd, stderr=subprocess.STDOUT)
  File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.9/subprocess.py", line 505, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/usr/lib/python3.9/subprocess.py", line 951, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.9/subprocess.py", line 1837, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: '/tmp/tmpzrluurcb/bin/python3'

Platform information

OS name and version: ubuntu 20.04
pip-audit version (pip-audit -V): 2.7.0
Python version (python -V or python3 -V): 3.9.8
pip version (pip -V or pip3 -V): 24.0

Thanks for the report! Summarizing to make sure my understanding is correct:

You have /tmp mounted as noexec
You ran pip-audit in requirements mode (pip-audit -r ...)
pip-audit failed because it couldn't run a python3 shim from within a venv that was created within /tmp

This is an eventuality we hadn't considered 🙂 -- did you manually configure your fstab on Ubuntu 22.04? As far as I know, this isn't the default.
(We'll need to think about how/if we want to handle this -- there are myriad ways for users to trip up userspace programs with filesystem options.)

Your understanding is correct.  This happened on a Ubuntu VM image that was "improved" for security reasons.

Thanks for confirming! Out of curiosity: where did that VM image come from, if you can say?
(Also: could you check to see if /var/tmp allows +x? That may be a better choice for us here.)

I asked around about this, and TIL that noexec on /tmp is a somewhat common configuration:

https://www.stigviewer.com/stig/oracle_linux_6/2021-06-14/finding/V-209071
https://bugzilla.redhat.com/show_bug.cgi?id=1420068#c4

Given that, I think pip-audit can do a better job of surfacing the state here. My current idea: we'll try and detect if the default tmpdir is noexec and render an intelligible error, rather than failing well into the audit process.
Longer term, we could probably try a shortlist of temporary directories to find one that allows +x, and/or improve the documentation to make it clear that the user will have to pass a different tmpdir or reconfigure their tmpdir.
How does that sound @rdinoff?

/var/tmp does allow +x (not mounted with noexec)

Forgot to mention: as a temporary workaround, TMPDIR=/var/tmp pip-audit -r requirememts.txt should work, since Python's tempfile module will use that variable to determine the temporary directory prefix to use.

Since the error here isn't from our own code, I think we should just fail gracefully (rather than raise an exception) and hint that the user should set TMPDIR.

Since the error here isn't from our own code, I think we should just fail gracefully (rather than raise an exception) and hint that the user should set TMPDIR.

SGTM! That's what #737 will end up doing, once I write a (mocked) test.

We've included an improved error message for this in 2.7.1. Thank you again for reporting @rdinoff!

fix looks good ....
(venv) rdinoff:~/audit$ pip-audit -r requirements.txt
ERROR:pip_audit._cli:Couldn't execute in a temporary directory under /tmp. This is sometimes caused by a noexec mount flag or other setting. Consider changing this setting or explicitly specifying a different temporary directory via the TMPDIR environment variable.
(venv) rdinoff:~/aydit$ echo $?
1
(venv) rdinoff:~/audit$ TMPDIR=/var/tmp pip-audit -r requirements.txt
No known vulnerabilities found


Experimental interfaces and traits for TensorNetwork-derived types

This is a experiment to have a cleaner and more reusable interfaces between types in the TensorNetwork hierarchy of types.
To do

[x] Refactor replace!
[x] Rethink about using Core.kwcall for keyword-dispatching
[x] Write a post on docs about how this works internally
[ ] Remove calls to previous "dispatch system" (not really dispatch)

Related links

https://github.com/bcbi/ExtensibleUnions.jl
https://github.com/jolin-io/WhereTraits.jl
https://github.com/WschW/StructuralInheritance.jl
https://github.com/mind6/Inherit.jl
https://github.com/thautwarm/CanonicalTraits.jl
https://github.com/Suzhou-Tongyuan/ObjectOriented.jl
https://github.com/EdBarrancos/ObjectSystem.jl
https://github.com/rjplevin/Classes.jl

It's weird that the test fails when it works in my laptop...

It's weird that the test fails when it works in my laptop...

They are working in my laptop as well. It is something about the CI that we must check but, from my side, this is ready for merge :+1:

Finally I managed to reproduce the test fails in my laptop. Still don't know why it was working before :shrug:.

Finally I managed to reproduce the test fails in my laptop. Still don't know why it was working before 🤷.

What did you do to make them fail in your laptop?

Nothing really. I think it was something related to some commits or some bug in the code. Still weird.

@jofrevalles @Todorbsc @starsfordummies the only thing that bugs me is if we want all methods to be callable from subtypes; i.e. we want to be able to push!/delete! Tensors from a MPS.


Incorrect display of Min/Max Cell Voltages

Describe the bug
For me, only the 1st cell is shown in color, not the critical cell. I've noticed this for many driver versions.

How to reproduce
Steps to reproduce the behavior:

Go to "Cell-Voltages"
Click on '....'
Scroll down to '....'
See error

Expected behavior
It would be nice if the minimum and maximum cell voltages were displayed
Driver version
1.0.20230711beta
Venus OS device type
Raspberry Pi
Venus OS version
3.01
BMS type
Daly Smart BMS
Cell count
16
Connection type
Serial USB adapter to TTL
Config file
[DEFAULT]

; --------- Battery Current limits ---------
MAX_BATTERY_CHARGE_CURRENT    = 175.0
MAX_BATTERY_DISCHARGE_CURRENT = 350.0

; --------- Cell Voltages ---------
; Description: Cell min/max voltages which are used to calculate the min/max battery voltage
; Example: 16 cells * 3.45V/cell = 55.2V max charge voltage. 16 cells * 2.90V = 46.4V min discharge voltage
MIN_CELL_VOLTAGE   = 2.900
; Max voltage (can seen as absorption voltage)
MAX_CELL_VOLTAGE   = 3.450
; Float voltage (can be seen as resting voltage)
FLOAT_CELL_VOLTAGE = 3.375

; Bulk voltage (may be needed to reset the SoC to 100% once in a while for some BMS)
; Has to be higher as the MAX_CELL_VOLTAGE
BULK_CELL_VOLTAGE  = 3.650
; Specify after how many days the bulk voltage should be reached again
; The timer is reset when the bulk voltage is reached
; Leave empty if you don't want to use this
; Example: Value is set to 15
; day 1: bulk reached once
; day 16: bulk reached twice
; day 31: bulk not reached since it's very cloudy
; day 34: bulk reached since the sun came out
; day 49: bulk reached again, since last time it took 3 days to reach bulk voltage
BULK_AFTER_DAYS =

; --------- Bluetooth BMS ---------
; Description: List the Bluetooth BMS here that you want to install
; -- Available Bluetooth BMS:
; Jkbms_Ble, LltJbd_Ble
; Example:
;     1 BMS: Jkbms_Ble C8:47:8C:00:00:00
;     3 BMS: Jkbms_Ble C8:47:8C:00:00:00, Jkbms_Ble C8:47:8C:00:00:11, Jkbms_Ble C8:47:8C:00:00:22
BLUETOOTH_BMS =

; --------- BMS disconnect behaviour ---------
; Description: Block charge and discharge when the communication to the BMS is lost. If you are removing the
;              BMS on purpose, then you have to restart the driver/system to reset the block.
; False: Charge and discharge is not blocked on BMS communication loss
; True: Charge and discharge is blocked on BMS communication loss, it's unblocked when connection is established
;       again or the driver/system is restarted
BLOCK_ON_DISCONNECT = False

; --------- Charge mode ---------
; Choose the mode for voltage / current limitations (True / False)
; False is a step mode: This is the default with limitations on hard boundary steps
; True is a linear mode:
;     For CCL and DCL the values between the steps are calculated for smoother values (by WaldemarFech)
;     For CVL max battery voltage is calculated dynamically in order that the max cell voltage is not exceeded
LINEAR_LIMITATION_ENABLE = True

; Specify in seconds how often the linear values should be recalculated
LINEAR_RECALCULATION_EVERY = 60
; Specify in percent when the linear values should be recalculated immediately
; Example: 5 for a immediate change, when the value changes by more than 5%
LINEAR_RECALCULATION_ON_PERC_CHANGE = 5

; --------- Charge Voltage limitation (affecting CVL) ---------
; Description: Limit max charging voltage (MAX_CELL_VOLTAGE * cell count), switch from max voltage to float
;              voltage (FLOAT_CELL_VOLTAGE * cell count) and back
;     False: Max charging voltage is always kept
;     True: Max charging voltage is reduced based on charge mode
;         Step mode: After max voltage is reached for MAX_VOLTAGE_TIME_SEC it switches to float voltage. After
;                    SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT it switches back to max voltage.
;         Linear mode: After max voltage is reachend and cell voltage difference is smaller or equal to
;                      CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL it switches to float voltage after 300 (fixed)
;                      additional seconds.
;                      After cell voltage difference is greater or equal to CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT
;                      OR
;                      SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT
;                      it switches back to max voltage.
; Example: The battery reached max voltage of 55.2V and hold it for 900 seconds, the the CVL is switched to
;          float voltage of 53.6V to don't stress the batteries. Allow max voltage of 55.2V again, if SoC is
;          once below 90%
;          OR
;          The battery reached max voltage of 55.2V and the max cell difference is 0.010V, then switch to float
;          voltage of 53.6V after 300 additional seconds to don't stress the batteries. Allow max voltage of
;          55.2V again if max cell difference is above 0.080V or SoC below 90%.
; Charge voltage control management enable (True/False).
CVCM_ENABLE = False

; -- CVL reset based on cell voltage diff (linear mode)
; Specify cell voltage diff where CVL limit is kept until diff is equal or lower
CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL = 0.010
; Specify cell voltage diff where CVL limit is reset to max voltage, if value get above
; the cells are considered as imbalanced, if the cell diff exceeds 5% of the nominal cell voltage
; e.g. 3.2 V * 5 / 100 = 0.160 V
CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT = 0.080

; -- CVL reset based on SoC option (step mode & linear mode)
; Specify how long the max voltage should be kept
;     Step mode: If reached then switch to float voltage
;     Linear mode: If cells are balanced keep max voltage for further MAX_VOLTAGE_TIME_SEC seconds
MAX_VOLTAGE_TIME_SEC = 900
; Specify SoC where CVL limit is reset to max voltage
;     Step mode: If SoC gets below
;     Linear mode: If cells are unbalanced or if SoC gets below
SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 80

; --------- Cell Voltage Current limitation (affecting CCL/DCL) ---------
; Description: Maximal charge / discharge current will be in-/decreased depending on min and max cell voltages
; Example: 18 cells * 3.55V/cell = 63.9V max charge voltage
;          18 cells * 2.70V/cell = 48.6V min discharge voltage
;          But in reality not all cells reach the same voltage at the same time. The (dis)charge current
;          will be (in-/)decreased, if even ONE SINGLE BATTERY CELL reaches the limits

; Charge current control management referring to cell-voltage enable (True/False).
CCCM_CV_ENABLE = False
; Discharge current control management referring to cell-voltage enable (True/False).
DCCM_CV_ENABLE = False

; Set steps to reduce battery current
; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True
CELL_VOLTAGES_WHILE_CHARGING   = 3.55, 3.50, 3.45, 3.30
MAX_CHARGE_CURRENT_CV_FRACTION =    0, 0.05,  0.5,    1

CELL_VOLTAGES_WHILE_DISCHARGING   = 2.70, 2.80, 2.90, 3.10
MAX_DISCHARGE_CURRENT_CV_FRACTION =    0,  0.1,  0.5,    1

; --------- Temperature limitation (affecting CCL/DCL) ---------
; Description: Maximal charge / discharge current will be in-/decreased depending on temperature
; Example: The temperature limit will be monitored to control the currents. If there are two temperature senors,
;          then the worst case will be calculated and the more secure lower current will be set.
; Charge current control management referring to temperature enable (True/False).
CCCM_T_ENABLE = False
; Charge current control management referring to temperature enable (True/False).
DCCM_T_ENABLE = False

; Set steps to reduce battery current
; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True
TEMPERATURE_LIMITS_WHILE_CHARGING = 0,   2,   5,  10,  15, 20, 35,  40, 55
MAX_CHARGE_CURRENT_T_FRACTION     = 0, 0.1, 0.2, 0.4, 0.8,  1,  1, 0.4,  0

TEMPERATURE_LIMITS_WHILE_DISCHARGING = -20,   0,   5,  10, 15, 45, 55
MAX_DISCHARGE_CURRENT_T_FRACTION     =   0, 0.2, 0.3, 0.4,  1,  1,  0

; --------- SOC limitation (affecting CCL/DCL) ---------
; Description: Maximal charge / discharge current will be increased / decreased depending on State of Charge,
;              see CC_SOC_LIMIT1 etc.
; Example: The SoC limit will be monitored to control the currents.
; Charge current control management enable (True/False).
CCCM_SOC_ENABLE = False
; Discharge current control management enable (True/False).
DCCM_SOC_ENABLE = False

; Charge current SoC limits
CC_SOC_LIMIT1 = 98
CC_SOC_LIMIT2 = 95
CC_SOC_LIMIT3 = 91

; Charge current limits
CC_CURRENT_LIMIT1_FRACTION = 0.1
CC_CURRENT_LIMIT2_FRACTION = 0.3
CC_CURRENT_LIMIT3_FRACTION = 0.5

; Discharge current SoC limits
DC_SOC_LIMIT1 = 10
DC_SOC_LIMIT2 = 20
DC_SOC_LIMIT3 = 30

; Discharge current limits
DC_CURRENT_LIMIT1_FRACTION = 0.1
DC_CURRENT_LIMIT2_FRACTION = 0.3
DC_CURRENT_LIMIT3_FRACTION = 0.5

; --------- Time-To-Go ---------
; Description: Calculates the time to go shown in the GUI
;              Recalculation is done based on TIME_TO_SOC_RECALCULATE_EVERY
TIME_TO_GO_ENABLE = False

; --------- Time-To-Soc ---------
; Description: Calculates the time to a specific SoC
; Example: TIME_TO_SOC_POINTS = 50, 25, 15, 0
;          6h 24m remaining until 50% SoC
;          17h 36m remaining until 25% SoC
;          22h 5m remaining until 15% SoC
;          28h 48m remaining until 0% SoC
; Set of SoC percentages to report on dbus and MQTT. The more you specify the more it will impact system performance.
; [Valid values 0-100, comma separated list. More that 20 intervals are not recommended]
; Example: TIME_TO_SOC_POINTS = 100, 95, 90, 85, 75, 50, 25, 20, 10, 0
; Leave empty to disable
TIME_TO_SOC_POINTS =
; Specify TimeToSoc value type [Valid values 1, 2, 3]
; 1 Seconds
; 2 Time string <days>d <hours>h <minutes>m <seconds>s
; 3 Both seconds and time string "<seconds> [<days>d <hours>h <minutes>m <seconds>s]"
TIME_TO_SOC_VALUE_TYPE = 1
; Specify in seconds how often the TimeToSoc should be recalculated
; Minimum are 5 seconds to prevent CPU overload
TIME_TO_SOC_RECALCULATE_EVERY = 60
; Include TimeToSoC points when moving away from the SoC point [Valid values True, False]
; These will be as negative time. Disabling this improves performance slightly
TIME_TO_SOC_INC_FROM = False

; --------- Additional settings ---------
; Specify one or more BMS types to load else leave empty to try to load all available
; -- Available BMS:
; Daly, Ecs, HeltecModbus, HLPdataBMS4S, Jkbms, Lifepower, LltJbd, Renogy, Seplos
; -- Available BMS, but disabled by default (just enter one or more below and it will be enabled):
; ANT, MNB, Sinowealth
BMS_TYPE = Daly

; Exclute this serial devices from the driver startup
; Example: /dev/ttyUSB2, /dev/ttyUSB4
EXCLUDED_DEVICES =

; Enter custom battery names here or change it over the GUI
; Example:
;     /dev/ttyUSB0:My first battery
;     /dev/ttyUSB0:My first battery,/dev/ttyUSB1:My second battery
CUSTOM_BATTERY_NAMES =

; Auto reset SoC
; If on, then SoC is reset to 100%, if the value switches from absorption to float voltage
; Currently only working for Daly BMS
AUTO_RESET_SOC = True

; Publish the config settings to the dbus path "/Info/Config/"
PUBLISH_CONFIG_VALUES = 1

; Select the format of cell data presented on dbus [Valid values 0,1,2,3]
; 0 Do not publish all the cells (only the min/max cell data as used by the default GX)
; 1 Format: /Voltages/Cell (also available for display on Remote Console)
; 2 Format: /Cell/#/Volts
; 3 Both formats 1 and 2
BATTERY_CELL_DATA_FORMAT = 1

; Simulate Midpoint graph (True/False).
MIDPOINT_ENABLE = False

; Battery temperature
; Specify how the battery temperature is assembled
; 0 Get mean of temperature sensor 1 to sensor 4
; 1 Get only temperature from temperature sensor 1
; 2 Get only temperature from temperature sensor 2
; 3 Get only temperature from temperature sensor 3
; 4 Get only temperature from temperature sensor 4
TEMP_BATTERY = 1

; Temperature sensor 1 name
TEMP_1_NAME = BMS

; Temperature sensor 2 name
TEMP_2_NAME = Temp 2

; Temperature sensor 2 name
TEMP_3_NAME = Temp 3

; Temperature sensor 2 name
TEMP_4_NAME = Temp 4

; --------- BMS specific settings ---------

; -- LltJbd settings
; SoC low levels
; NOTE: SOC_LOW_WARNING is also used to calculate the Time-To-Go even if you are not using a LltJbd BMS
SOC_LOW_WARNING = 20
SOC_LOW_ALARM   = 10

; -- Daly settings
; Battery capacity (amps), if the BMS does not support reading it
BATTERY_CAPACITY = 50
; Invert Battery Current. Default non-inverted. Set to -1 to invert
INVERT_CURRENT_MEASUREMENT = -1

; -- ESC GreenMeter and Lipro device settings
GREENMETER_ADDRESS  = 1
LIPRO_START_ADDRESS = 2
LIPRO_END_ADDRESS   = 4
LIPRO_CELL_COUNT = 15

; -- HeltecModbus (Heltec SmartBMS/YYBMS) settings
; Set the Modbus addresses from the adapters
; Separate each address to check by a comma like: 1, 2, 3, ...
; factory default address will be 1
HELTEC_MODBUS_ADDR = 1

; --------- Battery monitor specific settings ---------
; If you are using a SmartShunt or something else as a battery monitor, the battery voltage reported
; from the BMS and SmartShunt could differ. This causes, that the driver never goapplies the float voltage,
; since max voltage is never reached.
; Example:
;     cell count: 16
;     MAX_CELL_VOLTAGE = 3.45
;     max voltage calculated = 16 * 3.45 = 55.20
;     CVL is set to 55.20 and the battery is now charged until the SmartShunt measures 55.20 V. The BMS
;     now measures 55.05 V since there is a voltage drop of 0.15 V. Since the dbus-serialbattery measures
;     55.05 V the max voltage is never reached for the driver and max voltage is kept forever.
;     Set VOLTAGE_DROP to 0.15
VOLTAGE_DROP = 0.00

Relevant log output
@4000000064b8f5ef03190d7c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f5f21543523c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f5f72967d0bc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f5fd03b2a1e4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f60620bf3784 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f60932d753d4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f60f1c931234 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f6143130ac9c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f61e157eb55c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f621266e10ec INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f62700f571fc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f62c165f786c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f6353397254c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f6390a8ef6fc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f63e200359c4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f643348c722c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f64d166c2a6c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f650277a8b64 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f65601ac4a94 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f65b16574e94 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f66432d13184 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f668094fdf7c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f66d1f037dc4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f67233347f64 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f67c15808a1c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f6812a24c7bc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f68704bc556c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f68c196a8204 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f695362af75c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f6990d5c576c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f69f0bb9174c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f6a42193bdc4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f6ae029afc0c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f6b1149f888c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f6b62aa58c94 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f6bc0486ab24 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f6c52230fbac INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f6c833726edc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f6ce0d5a5f84 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f6d322d50bac INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f6dd03cefbb4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f6e016185d4c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f6e606193dbc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f6eb2cf0ff4c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f6f50e805d3c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f6f81f791f0c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f6fd359191d4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f7030fe6f9ec INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f70c2d1a39fc INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f71002cf815c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f715199cd4d4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f71a2f95732c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f72412c8d874 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f72724bd6b1c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f72c3a4580dc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f73228a7a56c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f73c0a68063c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f73f1cbae96c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f7443234e9b4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f74a0c768b4c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f7532ab5f7b4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f75903ddbd0c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f75e1b1f717c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f7633126c18c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f76d13681614 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f770254c8004 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f7753a1a2b1c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f77b15430804 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f784332884fc INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f78808a5d824 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f78d1f72fcbc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f792354f25ec INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f79c1771d6b4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f79f29572eec INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f7a50d101fb4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f7aa378e30dc INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f7b41b218c8c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f7b72cea92c4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f7bd17e43024 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f7c22c5c1634 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f7cc0e865c64 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f7cf20e132bc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f7d4377fbda4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f7da1013b70c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f7e32f230e04 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f7e705b0796c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f7ec1bfda834 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f7f131b1755c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f7fb13c001e4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f7fe261fbe24 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f804007da9ec INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f80916748324 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f8123361a9e4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f81609ce279c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f81b216a7f2c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f82038a0354c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f82a19e40764 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f82d2cd75ccc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f833071f0174 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f83902209034 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f842207787f4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f8453256390c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f84b119bf51c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f8502827da94 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f85a0aa53e1c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f85d1cca8584 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f86232b744cc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f8680bfe2314 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f8713158128c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f87508440cfc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f87a1f399184 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f87f3590edc4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f889185af27c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f88c2b608f94 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f8920605aa04 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f8971c40fa94 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f8a03ab5ea34 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f8a410970c24 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f8a926d05cfc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f8af00ee5d7c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f8b81dfb02bc INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f8bb30234bac INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f8c109a137b4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f8c61efe2e64 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f8d000d4f97c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f8d312519d04 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f8d82829de34 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f8de02e29044 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f8e720cc994c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f8ec378ed8d4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f8f210a1fcec INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f8f739d74a04 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f9011b028ef4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f9042d38ce1c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f90a089b3d4c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f90f1e4d1674 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f919017abefc INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f91c1273f214 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f9212846247c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f927031be7f4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f930219caaec INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f933339200e4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f9390fcdf794 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f93e256bd38c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f94807c5ad6c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f94b191f250c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f9502f28f9a4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f95609765b0c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f95f26e4bfbc INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f96238f3cfa4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f968135b391c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f96d29058c7c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f9770ba3e96c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f97a1e140ce4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f97f3478f1fc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f9850ecd11f4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f98e2d7f0a94 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f992033697fc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f9971a2a6aec INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f99c3018204c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f9a612f56a9c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f9a924ffac0c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f9af00c2a9fc INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f9b416854c04 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f9bd3440da9c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f9c10a5efdbc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f9c61fdf5704 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f9cb359ed844 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f9d51f40c15c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f9d8314a762c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f9de0b24803c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f9e32145b91c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8f9ed0447e4d4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8f9f0164d1564 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8f9f52c7fd2a4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8f9fb06c2df84 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fa042460bc8c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fa073756ec6c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fa0d11f44e4c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fa1226bb003c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fa1c08fee504 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fa1f1b49c954 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fa2432268234 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fa2a2124563c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fa3403d7ecc4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fa37167e915c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fa3c2e79d5b4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fa420f723b34 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fa4b2ed8e98c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fa4f051c8e3c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fa541c110d0c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fa5931dcb3ac INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fa631565f184 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fa6703814144 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fa6c199bc74c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fa71310896e4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fa7b12fd4654 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fa7e2496dc04 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fa833abf0254 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fa89299750e4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fa930c483fbc INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fa961e6a3b64 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fa9b35b64c2c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8faa1108948b4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8faaa2f99d444 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fab00a917f6c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fab520e1cb14 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8faba38257384 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fac41ac5f73c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fac72e428974 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8facd091e8a94 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fad21e9bee0c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fadc0135130c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fadf12944384 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fae4287e052c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8faea02cb242c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8faf320dce914 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8faf632f1a61c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fafc0ed9f2d4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fb0124d2b454 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fb0b06eb3b8c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fb0e187eb2d4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fb132f322164 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fb1909459a94 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fb2226f33eac INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fb2539cf7234 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fb2b1bc7cf0c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fb303931fd9c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fb3a1a46efb4 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fb3d2cf1265c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fb4306fa953c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fb481cbaf90c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fb513a5622ac INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fb550f71b664 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fb5a265bffec INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fb600102cbf4 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fb691e30a534 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fb6c320c5ae4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fb720d1b954c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fb7725416ffc INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fb81083a3d44 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fb841aa5098c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fb8932542d9c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fb8f0c061e0c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fb98292ad75c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fb9e03383224 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fba317bb5334 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fba82e9cf9cc INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fbb2114f53ec INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fbb7276fd534 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fbbd029bf9f4 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fbc217d08114 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fbcb39129e5c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fbcf0ff7556c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fbd425582c4c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fbda07f548ec INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fbe325e30b14 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fbe63916a1b4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fbec1253fe64 INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fbf12800fd5c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fbfb0ba2e79c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fbfe1d229094 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fc0332b24b5c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fc090d9bd16c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fc122bb191dc INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fc1602015fd4 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fc1b1823022c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fc202e56f01c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fc2a114ea424 INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fc2d237d1f04 INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fc340e2738ec INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fc392b3d540c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fc430eb59e0c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fc462001988c INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fc4b377ab87c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fc511281925c INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fc5a31b8e79c INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fc5e08a91ffc INFO: Start service dbus-serialbattery.ttyUSB4 once
@4000000064b8fc631df14e5c INFO: Start service dbus-cgwacs.ttyUSB4 once
@4000000064b8fc68345bc154 INFO: Start service gps-dbus.ttyUSB4 once
@4000000064b8fc7217f579ec INFO: Start service vedirect-interface.ttyUSB4 once
@4000000064b8fc752aac9d2c INFO: Start service dbus-serialbattery.ttyUSB4 once

Any other information that may be helpful
No response

I have 4 Baly-BMS connected and always the same behaviour.

Please post the log of the driver itself: https://louisvdw.github.io/dbus-serialbattery/troubleshoot/#datalogdbus-serialbatteryttyusbcurrent-or-datalogdbus-serialbatteryttyama0current

There seems to be a problem here that I don't understand. All 4 BMS report the same error in the LOG file, but the display of the BMS in the Victron is fine except for the red display of the min/max values. The data (voltage, current, SOC etc.) are displayed correctly by all 4 BMS.
/data/log/dbus-serialbattery.ttyUSB*/current
...
@4000000064bb8a7f22ed9104 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8a802544bbbc INFO:SerialBattery:refresh_data: result: False
@4000000064bb8ab125f36694 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8b2930f0406c INFO:SerialBattery:refresh_data: result: False
@4000000064bb8c23023d8e14 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8c8b08665e24 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8c8c099577e4 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8d2a11fe3574 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8d2b14c72144 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8e7a27b8c8fc INFO:SerialBattery:refresh_data: result: False
@4000000064bb8ec82dce72b4 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8f1030ef0404 INFO:SerialBattery:refresh_data: result: False
@4000000064bb8f273228a8fc INFO:SerialBattery:refresh_data: result: False
@4000000064bb8f8d384e63fc INFO:SerialBattery:refresh_data: result: False
@4000000064bb8f8e3a18d35c INFO:SerialBattery:refresh_data: result: False
@4000000064bb8fc0035b0c04 INFO:SerialBattery:refresh_data: result: False
@4000000064bb90c01992516c INFO:SerialBattery:refresh_data: result: False
@4000000064bb90f412cbf554 INFO:SerialBattery:refresh_data: result: False
@4000000064bb91441a313d04 INFO:SerialBattery:refresh_data: result: False

Why did you not execute the whole command?

 In the screenshot (correct) you see the timestamp and in the logs you posted (wrong) an encoded string.

Is that what you need The logs just tell me that something is wrong...

We always need the timestamp, but we have it in the screenshot.

Please also post the exact model of the BMS you are using as also the soft and hardware version of the BMS.

Here the screenshot (BMS Nr. 2, USB4) from the Daly-App and a photo from my reserve BMS which is the same type.

@transistorgit if you have some spare time could you check this?

Im on vacation right now, but I will check it I find some time.
1st impression:
On my 2 Dalys, it works as expected: random cells get highlighted. The cells are indicated by bits from the daly directly, thats nothing that I calculate. And this Bit is a Fault flag, so the highlight doesnt mean that they are the min/max cells.
I suggest a bms firmware update
Brgds
Bernd
PS: adding the cell index to the min/max voltage fields may be a meaningful feature request

PS: adding the cell index to the min/max voltage fields may be a meaningful feature request

They are on the "Details" page. Are they also needed on the cells page?

I have updated the firmware of my Daly BMS to the latest version from 25.03.2023 (31_230325_001T, obtained directly from the manufacturer/supplier). Unfortunately without success, the error persists.
While researching I found out that there are different hardware versions of Daly, the MCU (ST103 or ST030 or GD230 - first Number of Firmware) and the AFE (309E or 303E or DVCE or 9818 - second Number of Firmware) are different. Maybe this helps.
I have GD230 and 309E.

After reviewing this issue I'm the opinion that this is not a problem of incorrect min/max cell voltage dislay, but only a problem of incorrect cell balancing display. Since the values in Cells (Min/Max/Diff) are always correct in the screenshots.
The red background is displaying which cell is currently being balanced.

In this screenshot I see that you have disabled the active cell balancing. What happens if you turn it on?

The "active cells balacimg" switch is automatically activated by the system and indicates whether balancing is active or not.
the cell voltages are displayed correctly, the red background should always be on the cell with the highest or lowest voltage, the first cell is always displayed, regardless of the voltage of the first cell. this is definitely not correct!

Do you see in the app which cells are being balanced or do you see only that balancing is active?

the App shows always the highest cell in red and the lowest cell in green

the App shows always the highest cell in red and the lowest cell in green

@transistorgit if you find some time can you help me with that?

Hi,
today I looked into this issue. Unfortunately, I have the hardware ST103 which seems different to @centro-max hw. It would be interesting, if any other G230 user could acknowledge the problem.
In the meantime, my only suggestion would be to make a config entry to disable the balance status for these users.
best regards

I don't think that the red and blue colors indicate that these cells are balancing. It's showing only the highes and lowest cell voltage, since the cell balancing is not active in your screenshot.
@centro-max can you confirm that the one cell has only a red background, if the balancing is active?


Unit Testing Stream - Part 2

How to use xUnit / nUnit

Mocking and testing strategies with ASP.NET Core


[Bug]: undefined symbol: ncclcommregister when run docker built from the latest source code

Your current environment
We tested in tow environments, environment info in bellow.
🐛 Describe the bug
We built a docker image from the latest source code (2024/04/18), to run CohereForAI/c4ai-command-r-plus. We test in two environment:
First environment
Everything works fine, we use A100 machine, and output of collect_env.py:
4pdvGPU Msg(682:140318609781760:libvgpu.c:869)]: Initializing.....
[4pdvGPU Warn(682:140318609781760:hook.c:475)]: remap handles for device 0
/usr/lib/python3.10/runpy.py:126: RuntimeWarning: 'torch.utils.collect_env' found in sys.modules after import of package 'torch.utils', but prior to execution of 'torch.utils.collect_env'; this may result in unpredictable behaviour
  warn(RuntimeWarning(msg))
Collecting environment information...
[4pdvGPU Warn(682:140318609781760:utils.c:228)]: get default cuda 1 from (null)
[4pdvGPU Msg(682:140318609781760:libvgpu.c:902)]: Initialized
PyTorch version: 2.2.1+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.3 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.29.2
Libc version: glibc-2.35

Python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-5.4.0-162-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA A100-SXM4-80GB
Nvidia driver version: 535.129.03
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      46 bits physical, 57 bits virtual
Byte Order:                         Little Endian
CPU(s):                             128
On-line CPU(s) list:                0-127
Vendor ID:                          GenuineIntel
Model name:                         Intel(R) Xeon(R) Platinum 8336C CPU @ 2.30GHz
CPU family:                         6
Model:                              106
Thread(s) per core:                 2
Core(s) per socket:                 32
Socket(s):                          2
Stepping:                           6
CPU max MHz:                        3500.0000
CPU min MHz:                        800.0000
BogoMIPS:                           4600.00
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 invpcid_single ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq rdpid md_clear pconfig flush_l1d arch_capabilities
Virtualization:                     VT-x
L1d cache:                          3 MiB (64 instances)
L1i cache:                          2 MiB (64 instances)
L2 cache:                           80 MiB (64 instances)
L3 cache:                           108 MiB (2 instances)
NUMA node(s):                       2
NUMA node0 CPU(s):                  0-31,64-95
NUMA node1 CPU(s):                  32-63,96-127
Vulnerability Gather data sampling: Vulnerable: No microcode
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Retbleed:             Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.2.1
[pip3] triton==2.2.0
[conda] Could not collect
[4pdvGPU Msg(682:140318609781760:multiprocess_memory_limit.c:477)]: Calling exit handler 682

Second environment
In this environment we use vgpu, And when run the command
python3 -m vllm.entrypoints.openai.api_server --dtype half --model /root/.cache/LLM-Repo/model/c4ai-command-r-plus-GPTQ --trust-remote-code

shows the following error:

We can not run python -m torch.utils.collect_env:

But we have nvidia-smi output:

From host machine

Inside docker:

We notice that vllm upgrade torch version to 2.2, i think is might be related.
We don't know which is causing the error on the second environment, any advice is appreciated.

And we find the latest dockerfile build will not include collect_env.py , which will be inconvenient when can't import torch and no have internet connection.

This is not a problem of vllm, but your installation of torch is broken.
What is the output of pip list | grep nccl ? Typically this problem is you installed pytorch 2.2, but has nvidia-nccl-cu12==2.18 .

And we find the latest dockerfile build will not include collect_env.py , which will be inconvenient when can't import torch and no have internet connection.

We may update that script, so it is better to download and execute every time.

This is not a problem of vllm, but your installation of torch is broken.
What is the output of pip list | grep nccl ? Typically this problem is you installed pytorch 2.2, but has nvidia-nccl-cu12==2.18 .

But we use the leatest source code to built docker image， and in one environment it's working fine. I will show output of nccl version later

We upgrade nvidia driver to 535.129, now it's working fine


Fix for Issue #968 - extra ; in gcc --pedantic-errors mode

Without this fix g++ --pedantic-errors will fail with errors, as discussed in Issue #968
Seems like a boost 1.84.0 regression, not seen with previous versions of boost.
nigels@zooropa:~/dev/boost-json/example$ g++ -c validate.cpp -I$(pwd)/../include -I$(pwd)/../tmp/boost_1_84_0 --pedantic-errors
nigels@zooropa:~/dev/boost-json/example$

Merged via 942bbd4cf5e5fd30b7be71d187ab5bd2e54f8939
Thank you for your contribution!


build, macOS: Allow compiling v8 on macOS 10.15 to 13.0

Commit Message: build, macOS: Allow compiling on macOS 10.15 to 13.0
Additional Description: https://bugs.chromium.org/p/v8/issues/detail?id=13428. Will submit an issue to track the patch removal once this is merged.
Risk Level: Low (affects only macOS)
Testing: Manual on macOS 10.15 (Xcode 12.4), 12.6 (Xcode 14.0.1), and 13.0 (Xcode 14.1),
Fixes https://github.com/envoyproxy/envoy/issues/23359
Signed-off-by: Dhi Aurrahman<EMAIL_ADDRESS>

/lgtm deps
Thanks


[TypeUtils.findOverridenMethod] Skip found methods with default access and not same package

What's changed?

What's your motivation?

Fixes #3599
Anything in particular you'd like reviewers to focus on?

Since it is an utility method that is invoked from different scenarios check if this change can affect any other behaviors.
Anyone you would like to review specifically?

@timtebeek
Have you considered any alternatives or workarounds?

Checklist

[ ] I've added unit tests to cover both positive and negative cases
It seems affected method is being invoked from another unit tests already so specific test was not added.
Should add a specific unit test for MissingOverrideAnnotation recipe to verify this bugfix.
[ ] I've added the license header to any new files through ./gradlew licenseFormat
no new files were added
[x] I've used the IntelliJ IDEA auto-formatter on affected files

It would be very nice if we could get a unit test for this. Something like this:
    @Test
    void packagePrivateMethodOverride() {
        rewriteRun(
          java("..."),
          java("...",
            spec -> spec.afterRecipe(cu -> {
                assertThat(...);
            })
          )
        );
    }

Thanks for getting this started @joteri ! I've added a test and pushed a small change such that there's less negations in the code. Hope you agree!


[WIP] Allow reusing nested objects

Closes #1362.
Closes #1800.
I'm just opening this up because I'm at a loss on how to refactor this to make it not so ugly, and would appreciate input from the team. This is very much a work in progress, I'd just like some design help at this point.
\c @jpsim @kishikawakatsumi @TimOliver

One potentially less ugly option would be to store the persisted version of the object as an associated object on the original, but that might perform even more terribly (and might have lifetime problems?). Other than that I don't have any ideas that don't involve completely reworking object insertion.


mjml-cli: track custom components as dependencies when using watch

Is your feature request related to a problem? Please describe.
Currently the watch flag in mjml's cli builds a dependency tree of mjml partials. However, custom components are not tracked. It would be valuable for components to trigger a rebuild.
Describe the solution you'd like
Track components as a file dependencies. Reload component and rebuild on change.
Describe alternatives you've considered
The alternative is either a slow gulp process that doesn't consider dependencies, or manually restarting the watch when components are changed.
Additional context
Since it doesn't seem like this has been brought up in a previous issue, I mainly want to record it for the future. It isn't currently a bottleneck, however, any suggestion on how to get this working would be appreciated. 🙏

I don't know if we want to do such thing as it a bit tricky to hot reload stuff like component

I can see that reasoning. I haven't dug too deeply into the internals of how the cli is doing the watch operation. I imagined running the mjml renderer as a subprocess and reloading the subprocess when a component changes.
I mostly put in this issue to track it. This isn't a large blocker for me at the moment since I've set up two processes in gulp, one for template development and the other for component development. It seems to be working well.

I'm fine if someone willing to open a PR for this (maybe behind a flag?) but I'm closing for now


chore(master): release 3.4.0

:robot: I have created a release beep boop
3.4.0 (2024-08-07)
Features

directive: move directive to define (2ba450b)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v3.4.0
:sunflower:


Don't check author of tag

I initially added it to avoid unwanted packages being built but you need write permission to the repo.

@balena-ci I self-certify!


How to load deep learning model in jni

Preparation && Getting Started,
5.Before using a model, you need to load the model.
The DDK supports both single-model and multi-model loading.
In sync mode, the app layer loads the model by calling the loadModelSync function at the JNI layer.
In async mode, the app layer loads the model by calling the loadModelAsync function at the JNI layer.
Here, it says to load the model in JNI, but I'm not sure.
If it was keras in python
model = load_model ('squeezenet_v1.0.caffemodel')
I think I will write.
Assuming that you use squeezenet_v1.0.caffemodel, please tell me how to write it.

loadModel only support HiAI Offline Model.
For details about the development process, refer to the development guide
HiAI guides：
https://developer.huawei.com/consumer/en/doc/development/hiai-Guides/integration-model-v1-0000001053153080
For the code, refer to the example
HiAI Demo ：
https://developer.huawei.com/consumer/en/doc/development/hiai-Examples/sample-code-0000001052989807
FYI


make bpkg friendly

I love this little script!
See bpkg for more information.
We also built something more generic for drawing in the terminal. Check out term

:+1:


Add Auto merge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/flask-paginate-feedstock#4.


⚠ Processors has degraded performance

In 2e5d40a, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 40 ms

Resolved: Processors performance has improved in fc2b420.


Shellsort

I have added shell sort in C++ algorithms. Please let me know if you want any changes

PLease let me know if you want any changes. I have added shell sort in C++ algorithms.


Any chance of supporting this 3x2 with wheel?

Purchased off TEMU and curious to see whether I might be able to get it to work on a Mac.
Thanks.
Product ID:  0xdc81
Vendor ID:  0x6d80
Speed: | Up to 12 Mb/s
Manufacturer: | SDINNOVATION

It's hard to do anything without having keyboard in hands.


[BUG] vSphere Multi VM Import, vSphere Task Shows "Export OVF template, Status: Operation timed out."

Describe the bug
Importing either a single or multiple via kubectl create on VirtualMachineImport resources create "Timed Out" task result on:
 Export OVF template
Status:
Operation timed out.
Initiator: place.com\mrussell
Target:
gm-bionic-image
Server: place.com

Yet, in Harvester, they succeed - but vSphere shows that export as timed-out as a side-effect.

To Reproduce
Steps to reproduce the behavior:

Have multiple VMs "turned off" in vSphere
Leverage kubectl create -f your_yaml_file_with_multiple_virtual_machine_imports.yaml creating that against the Harvester's kubeconfig
Audit vSphere tasks.

Expected behavior
vSphere tasks wouldn't show the "Export OVF template" as a "timed out" status when it succeeds, since VM is accessible in Harvester
Environment

Harvester ISO version: v1.1.0-rc1
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context

vSphere: <IP_ADDRESS>0000

Relates to: https://github.com/harvester/harvester/issues/2879

@ibrokethecloud - if I recall correctly this has been implemented, and I didn't see any issues with it from the last testing, correct?

@ibrokethecloud - I'll be closing this out :smile: as this was checked in the last set of testing in:
https://github.com/harvester/harvester/issues/2274


Warning in crypto.pbkdf2 with NodeJS 6.

I recently upgraded to NodeJS 6.1.0, npm 3.8.6. Now Superlogin APIs result in this deprecation warning -
(node:11324) DeprecationWarning: crypto.pbkdf2 without specifying a digest is deprecated. Please specify a digest

OK, I haven't even tested on Node 6 yet. It works for now, but I will be making these adjustments for future versions. The warning is coming from couch-pwd. I recommend you file an issue there or do a pull request yourself to fix the issue.

I filed an issue here: https://github.com/zemirco/couch-pwd/issues/1
I'll wait a few weeks for the maintainer of this package to fix, otherwise I will fork it

Thanks Colin.
On May 16, 2016 2:47 AM, Colin Skow<EMAIL_ADDRESS>wrote:I filed an issue here: zemirco/couch-pwd#1
I'll wait a few weeks for the maintainer of this package to fix, otherwise I will fork it
—You are receiving this because you authored the thread.Reply to this email directly or view it on GitHub

Hi guys, thanks for the ticket,
Is it blocking, because I can register user and I can't connect with the login route ?

@numerized that problem should have nothing to do with the Crypto warning. It will work fine until Node 7.
What problem are you having with the login route?

I simply didn't know that username has to be in small letters to be accepted. I could create my account with capital letters in the username with a rest client but I couldn't login with the same credential accepted before ! now I create my usernames in small it works well.

@colinskow What is the status of this? Node 7 has been out for a while

@antonyRoberts https://github.com/zemirco/couch-pwd/pull/2

This now breaks in Node 8. Superlogin throws now -- no longer just deprecated. It is a straight failure now.
TypeError: The "digest" argument is required and must not be undefined
    at pbkdf2 (crypto.js:635:11)
    at Object.exports.pbkdf2 (crypto.js:623:10)
    at Object.exports.hash (/.../node_modules/couch-pwd/index.js:41:12)
    at Object.exports.verifyPassword (/.../node_modules/superlogin/lib/util.js:37:10)
    at /.../node_modules/superlogin/lib/local.js:55:18
    at <anonymous>

Can we get this updated? Also, the npm module version hasn't been updated in quite a while and it would be good to get some recent fixes in a distributable package form.
Thanks!

ps. couch-pwd is a tiny little package with no non-native deps (https://github.com/zemirco/couch-pwd/blob/master/index.js) so it maybe can just be copied into a core superlogin file, rather than waiting for it to be updated/published?

Relevant: https://github.com/colinskow/superlogin/issues/167

I'd be happy to do this (and some other things) if I could be a contributor.

Running into this as well. It looks like the fix is already in this repo, can we get a publish?

You can add following dependency in your package.json for npm to fetch dependency directly from github repo which already has the fix.
"couch-pwd": "zemirco/couch-pwd"

I had the same issue and now use the fork https://www.npmjs.com/package/@sensu/superlogin which already includes the fixed version of couch-pwd and also other updated dependencies like pouchdb 6.4.3 instead of 5.3.2 in the current release of this repository.
However it would be great if a new release of this "official" repository with fixed/updated dependencies would be published or another fork would be declared as new "official" repository where development continues. At the moment it seems to be quite a mess.

>>> Superlogin is broken / dead <<<, as far as I can tell, unless and until couch-pwd gets replaced.  I see sen-su made an updated fork: https://github.com/sen-su/couch-pwd, but it looks like he has an entirely new fork of superlogin, so I will check that out.  Adios, dead project.

Sounds good. I honestly stopped using CouchDB, so I haven't had any resources to devote to maintaining it. If sen-su would like to take over the official package I would be happy to hand over the repo and NPM package.

I've also made a fork of superlogin, updated all dependencies and some tests (Travis CI for node 10 & Snyk scans) and refactored it a bit:
https://github.com/LyteFM/superlogin
I also considered to publish it on npm, but would of course be nicer to contribute to the official package if he'd like to work on it.

@LyteFM could you please make a pull request with your updates?


Update translator to 1.4.9

Update the ruler to use the 1.4.9 translator and the 1.4 engine

resolved on devleop


schema-inspector is missing

I believe this one should be benchmarked as well.
schema-inspector

PRs wellcome :-)

@ebdrup I will see to that ;)

awesome :+1:

hmm, it looks like they are not implementing the official JSON-schema standard, but have come up with their own schema standard. As such it would not make sense to add it to this benchmark. This benchmark is only for implementations of the official JSON-schema standard.


Add a test for issue #283 (commented out)

I verified the #283 issue  by running the excellent example, and the bug certainly does exist. However, there's a another bug around .useFakeTimers and .restore() that still plague us, so this is commented out to avoid the cascade of false positives.
This pull request adds a test to verify that #283 has been fixed (for when it does get fixed).
Related: #624

I did things in the wrong order... Mind rebasing?

Hmm, master is now failing with these: The command "if [ "x$TRAVIS_NODE_VERSION" != "x0.6" ]; then $(npm bin)/jscs .; fi" failed and exited with 2 during .
Any idea?

Probably a style violation. I'll have a look when I am in the office

Fuck, I need to look further than my nose... I didn't even read the whole line. Sorry, fixed and pushed.

I've rebased (and fixed the style violations). Could you give Travis a kick? (It failed on some npm timeout).

Took my chances:
➜  sinon git:(master) npm run lint

><EMAIL_ADDRESS>lint /Users/n06974/projects/sinon
> jscs **/*.js

No code style errors found.


How to change which item is selected?

I am using a dropdown together with a clickable map. If someone clicks an item in the map, I want to update the <select> list to show that item as being selected.
Doing this doesn't seem to work:
$('#map-container .sample select').val("3");

Yes I was wondering if there was a way to programmatically change selected option.

You can change the selection in the select element and trigger the change event

I tried this the following but it doesn't work, did I miss something?
    $('.select-dropdown').on('change', function() {
            $(".select-dropdown").dropdown();
    });

    $('.select-dropdown').on('change', function() {
            $(".select-dropdown").dropdown({ "dropdownClass": "my-dropdown"});
    });

What about
$(".select").value("x").trigger("change");

$(".select").val("x").trigger("change");
Does not work..

It was working, looks like some commit removed the feature..

Had to fix it by myself, please support your plugin.. I'll be using it at my projects.
Fix:
$select.on("change", function(e) {
var $this = $(e.target);
if (!$this.val().length) return;
      if (!multi) {
        var $selected;
        if ($select.find(":selected").length) {
          $selected = $select.find(":selected").last();
        }
        else {
          $selected = $select.find("option, li").first();
          // $selected = $select.find("option").first();
        }
        methods._select($dropdown, $selected);
      } else {
        methods._select($dropdown, $select.find(":selected"));
      }
    });

Add this on line 171

Now $(".select").val("x").trigger("change");  // works..

Feel free to send a PR

Thanks for the fix nekkon.

I got the same issue. In my case, I cannot use .trigger("change") because I want 2 selects are both the same value when each one changed. How should I do?

Does this fix address when no item is selected?
selectedIndex = -1
Doesn't seem to work.

nekkon's fix still works


[WIP]: Store private keys in kubernetes secret

Summary of Changes
This PR moves the SSH private keys into a kubernetes secret such that when the builder is restarted (or destroyed), it retains the same private keys for authenticating clients.
Since the host keys are supplied by kubernetes, we no longer need to generate the host keys, so that code has also been removed.
Issue(s) that this PR Closes
Closes #157
Associated End To End Test PR(s)
No changes required. The existing end-to-end tests ensure that the user can deploy applications to Workflow given this change. However, end-to-end won't work until deis/charts#237 is merged.
Associated Documentation PR(s)
No changes required.
Associated Design Document(s)
No design document required.
Testing Instructions

Create a Deis Cluster using the chart changes in deis/charts#237
Deploy a buildpack app (example-go)
Destroy the builder with kubectl --namespace=deis destroy pod deis-builder-xxxx
Deploy a second buildpack app

Originally, you would see a warning that "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" and to check ~/.ssh/known_hosts, but now it should pass without a warning.
Pull Request Hygiene TODOs
Please make sure the below checklist is complete.

 As every have the same public key for each deis install. rather we should generate them randomly via helm generate

All righty. I'll keep this out for beta3 until I can get helm generating the ssh keys for us. If not then we can keep this one out.
Marking as a WIP

@smothiki see Masterminds/sprig#10 for an implementation :)

see Masterminds/sprig#10 for an implementation :)
:+1:

@bacongobbler If the apps exists in the database and there is a release object but no build object then namespaces are created but scheduler deploy function failed. This use case we are completely missing

To add to my above comment app.create() was called successfully at that time which we are avoiding in this code fix

How can I reproduce that?

@bacongobbler wrong comments meant for this pR https://github.com/deis/controller/pull/651
deleteing and commenting in appropriate pr

Masterminds PR got merged. So helm should work with the new ssh keys generating features?

helm should work with the new ssh keys generating features

Once helm/helm#440 is merged and the 0.6.0 release is tagged, but not quite yet.

@mboersma no need to update helm :P

@smothiki looks like ParseHostKeys is important:
><> git push deis master
ssh_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
><> kd logs deis-builder-8h6r3
2016/04/22 17:30:25 Running in debug mode
2016/04/22 17:30:25 Starting health check server on port 8092
2016/04/22 17:30:25 Starting deleted app cleaner
2016/04/22 17:30:25 Starting SSH server on <IP_ADDRESS>:2223
[debug] Name: EXTERNAL_PORT, Val: 2223
[info] Listening on <IP_ADDRESS>:2223
[info] Accepting new connections.
[info] Checking closer.
[info] Builder is running.
[info] Checking closer.
[info] Accepted connection.
[debug] Failed handshake: ssh: server has no host keys

Manually tested:
><> deis create go
Creating Application... done, created go
Git remote deis added
><> git push deis master
The authenticity of host '[deis.<IP_ADDRESS>.xip.io]:2222 ([<IP_ADDRESS>]:2222)' can't be established.
ECDSA key fingerprint is 61:a2:5a:da:b8:28:71:f7:fb:0f:d0:2c:b0:cf:7c:c2.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[deis.<IP_ADDRESS>.xip.io]:2222,[<IP_ADDRESS>]:2222' (ECDSA) to the list of known hosts.
Counting objects: 80, done.
><> kd get po
NAME                        READY     STATUS    RESTARTS   AGE
deis-builder-9hk88          1/1       Running   0          13m
deis-controller-6p9px       1/1       Running   1          37m
deis-database-n44zy         1/1       Running   0          37m
deis-logger-fluentd-3q84h   1/1       Running   0          37m
deis-logger-sc0xm           1/1       Running   0          37m
deis-minio-kbvvv            1/1       Running   0          37m
deis-registry-ukqdb         1/1       Running   1          37m
deis-router-kca6k           1/1       Running   0          37m
><> kd delete po deis-builder-9hk88
pod "deis-builder-9hk88" deleted
><> git remote rm deis
><> deis create goo
Creating Application... done, created goo
Git remote deis added
remote available at ssh://git@deis.<IP_ADDRESS>.xip.io:2222/goo.git
><> git push deis master
Counting objects: 80, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (45/45), done.
Writing objects: 100% (80/80), 19.02 KiB | 0 bytes/s, done.
Total 80 (delta 30), reused 75 (delta 30)

Oh I didn't realize the importance . Please add parse host keys I'll folowup on this issue again

I forgot that this PR will keep going red until deis/charts#237 is merged. Since that PR does not affect anything else other than reliability on helm 0.6.0, I've merged it so we can test this.

:+1: for removing code


New version: chrisant996.Clink version 1.3.42.ef446e [FP-O]

Result: Installation Failed

Manifest
Add/Remove Programs

Name
Clink

Version
1.3.42.ef446e

Publisher
Christopher Antos

ProductCode

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 2821

2022-09-03 05:45:10.760 [FAIL] Installer failed security check. Url: https://github.com/chrisant996/clink/releases/download/v1.3.42/clink.1.3.42.ef446e_setup.exe Result: 0x80004005

@wingetbot run


[PE-D][Tester C] remark replaces current remark

When I execute the remark command and there is already an existing remark command, it replaces the previous remark. Might be problematic because if i wish to update it, i would have to type everything that was there before.
Maybe can implement more of an append feature for remark.

Labels: severity.Low type.FeatureFlaw
original: xuwen-ho/ped#6

Duplicate with #141

Not allowed to fix


Stellar now returns to Exchange after a successful sign

Codecov Report
Patch and project coverage have no change.

Comparison is base (83f1e8e) 77.72% compared to head (cdb479c) 77.72%.

Additional details and impacted files
@@                    Coverage Diff                     @@
##           fbe/stellar_donjon_review      #62   +/-   ##
==========================================================
  Coverage                      77.72%   77.72%
==========================================================
  Files                             12       12
  Lines                           2352     2352
==========================================================
  Hits                            1828     1828
  Misses                           524      524

Flag
Coverage Δ

unittests
77.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

https://github.com/LedgerHQ/app-exchange/pull/115

The warning
src/swap/handle_swap_sign_transaction.c:53:1: error: function declared 'noreturn' should not return [-Werror,-Winvalid-noreturn]
}
^
1 error generated.

Is a false positive caused by a missing flag in the SDK API, fix in progress

The issue in test_stellar_swap_refuse_double_sign is expected as the test will need an update

Zemu tests seem broken because the Speculos is out of date