Xfail timeout

XFAIL xrt tests 04 and 12 because they take too long and trigger a timeout on recent drivers.

XFAIL xrt tests 04 and 12 because they take too long and trigger a timeout on recent drivers.

Maybe it's not a timeout. When I run test 04 manually it seems to pass about 20% of the time and it takes about 1minute to run. The rest of the time it fails and takes less than 3 seconds to run.

Hopefully this PR can make test 04 work with the recent drivers again: https://github.com/Xilinx/mlir-air/pull/719

This PR aims to re-enable test 12: https://github.com/Xilinx/mlir-air/pull/829


Cache Release Status result for 5 minutes

@pablogsal @ambv: Military grade optimization, I reduced the cache to 5 minutes.

@ambv: Use datetime.timezone.utc which is available on 3.9

@zware: Once you mentioned that you considered to upgrade Python on the buildbot? Is it still the case? :-)

@zware: Once you mentioned that you considered to upgrade Python on the buildbot? Is it still the case? :-)

I'm in favor, but have made no attempts towards it (that I remember :)).  Pretty sure it will need to be done via the Salt configuration.


IE9/IE10 - Clicks Register on Native Select, Not Faux

When xq-select is added to IE9/10, it seems to be rendered underneath the native select, therefore all clicks go to the native select.

This issue has been fixed as of f8f6b71.


Dependency-track parser should include Vulnerability Alias information

Bug description
Dependency-track includes Vulnerability alias information in the FPF format export. This information is currently ignored by the Parser, however if correctly read and set in VulnerabilityId it could help do better deduplication.
Steps to reproduce
Steps to reproduce the behavior:

import FPF format findings from Dependencytrack or Set up Dependencytrack Defectdojo integration
see that the VulnerabilityID field only contains 1 entry
see that the FPF format can contain multiple ids (depending on analyzers active in Dependency-track)

Expected behavior
The "vulnerability_id" in the dependency-track parser reads all the aliases as well
Deployment method (select with an X)

[ ] Docker Compose
[ x] Kubernetes
[ ] GoDojo

Environment information
custom hosting k8
Logs
Sample scan files
If applicable, add sample scan files to help reproduce your problem.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context (optional)
This issue relates to some other issues in dependency-track:
1 bug: https://github.com/DependencyTrack/dependency-track/issues/2469
but also the discussions about deduplication on Dependencytrack side here:
https://github.com/DependencyTrack/dependency-track/issues/1994
and here: https://github.com/DependencyTrack/dependency-track/pull/1912#issuecomment-1228505074

fixed in https://github.com/DefectDojo/django-DefectDojo/pull/7746 and https://github.com/DefectDojo/django-DefectDojo/pull/7583


Try automergeType: pr-comment to delay

attempt to allow time for GH to register required checks, avoiding untested PRs being prematurely approved/merged

Change-type: patch

Invalid.


Change estimate of heap size per inode from 350 bytes to 2kb

What changes were proposed in this pull request?
Change the estimate of heap size per inode to 2kb
Why are the changes needed?
We want to be more conservative in cache size estimate.
Does this PR introduce any user-facing change?
No

Codecov Report

Merging #13592 (c573799) into master (8e31e0a) will decrease coverage by 26.15%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             master   #13592       +/-   ##
=============================================
- Coverage     43.78%   17.62%   -26.16%
+ Complexity     9051     2670     -6381
=============================================
  Files          1378     1378
  Lines         79868    79868
  Branches       9710     9710
=============================================
- Hits          34967    14077    -20890
- Misses        41952    64549    +22597
+ Partials       2949     1242     -1707

Impacted Files
Coverage Δ

...common/src/main/java/alluxio/conf/PropertyKey.java
97.87% <100.00%> (-1.60%)
:arrow_down:

...mon/src/main/java/alluxio/shell/CommandReturn.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...mon/src/main/java/alluxio/util/ExceptionUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/wire/AlluxioProxyInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../src/main/java/alluxio/wire/AlluxioMasterInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...src/main/java/alluxio/job/meta/JobIdGenerator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/stress/BaseParameters.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...src/main/java/alluxio/client/UnderStorageType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...main/java/alluxio/underfs/options/ListOptions.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...main/java/alluxio/worker/block/io/BlockReader.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 657 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8e31e0a...c573799. Read the comment docs.

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.6 please


hitarea debug only to be visible if the object is visible

When using enableDebug for input hitarea maybe it would be best if the debug rectangle is hidden when the gameobject is set to not visible. The reason for this is that pointer inputs are not fired for hidden gameobjects.
Maybe it could be achieved by using the renderFlags of the gameobject.

Yes, you can achieve this by using the renderFlags property of the game object. The renderFlags property is an integer that determines the render behavior of a game object. You can use the RENDER_MASK constant to set the bit value that corresponds to the DEBUG flag.
Here's an example of how you can modify the setHitArea function of a sprite to enable debug mode only when the sprite is visible:
Phaser.GameObjects.Sprite.prototype.setHitArea = function (shape) {
this.input = this.input || {};
this.input.hitArea = shape;
if (this.input.hitArea) {
    // Enable debug mode only when the sprite is visible
    if (this.visible) {
        this.input.hitAreaDebug = this.scene.add.graphics().setAlpha(0.75);
        this.input.hitAreaDebug.lineStyle(2, 0xffff00);
        this.input.hitAreaDebug.strokeRectShape(this.input.hitArea);
        this.input.hitAreaDebug.setVisible(true);
        this.renderFlags |= Phaser.GameObjects.GameObject.RENDER_MASK;
    }
} else {
    if (this.input.hitAreaDebug) {
        this.input.hitAreaDebug.destroy();
        delete this.input.hitAreaDebug;
    }
    this.renderFlags &= ~Phaser.GameObjects.GameObject.RENDER_MASK;
}

return this;

};
This function first sets the hitArea property of the sprite to the specified shape. Then it checks if the hitArea is defined and creates a graphics object for debugging. It sets the visible property of the debug graphics object to true only when the sprite is visible. Finally, it sets the renderFlags property of the sprite to enable debug rendering. If the hitArea is not defined, it destroys the debug graphics object and clears the renderFlags property to disable debug rendering.
I hope this helps!

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


chore: disable video completely

A dummy PR to test the Cypress setting in CI which have been causing memory issues.
Should be closed when https://github.com/dhis2/line-listing-app/pull/345 is closed
The only reason this PR is not in DRAFT is because the e2e tests don't run otherwise.

Disabling video did not make any difference


Add reraise_kj_exception to the prettyPrint functions.

I didn't research this enough to know if +reraise_kj_exception is the optimal specifier.  But it matched what I saw elsewhere in the code and fixed the problem in my own informal testing.

Thanks! Do you need a realease on pypi, or are you fine with building from source?

I'm fine with building from source.  I've been meaning to push this
to Debian for a while now, but never gotten around to it.  Let me
know the next time you do a pypi release and I'll follow up with a
Debian release.
Thanks!
On 11/15/2015 06:47 PM, Jason Paryani wrote:

Thanks! Do you need a realease on pypi, or are you fine with building from source?

Reply to this email directly or view it on GitHub:
https://github.com/jparyani/pycapnp/pull/86#issuecomment-156872212


Failed to parse response: expected value at line 1 column 1

i have been reinstall but the problem still same. what should i do

I have to assume that is just a problem with the API in getting the official game background. I assume you are still able to set a custom background? That should at least prevent you from being flashbanged when opening Cultivation :P


Add issue and PR templates

Add templates for community standards.
These go in the .github folder.
Feel free to take a look at other repos including https://github.com/DenverCoder1/github-readme-youtube-cards/tree/main/.github for examples.

Hi, can I work on this?

@Vinitvh Sure, go ahead :+1:


Set width to auto to float table header

With css rule "table { width: 100%; }" and long paragraph in th cell, first few rows would be covered by floating header.
Fiddle: http://jsfiddle.net/nrjqf44e/3/  (first row is invisible.)

sorry,
not seeing this http://jsfiddle.net/nrjqf44e/4/
what am i looking for? no rows are covered up. I am on osx/chrome

Hi, thanks for reply.
Viewport must be width enough to let long paragraph become one line when calculating header height,
So the calculated header height (one line) is less than actual header height (two lines).
Below is gif and updated fiddle:
Update

http://jsfiddle.net/nrjqf44e/5/

I see, weird that I've never encountered that before. Thanks for the fix!


[rom_ext] cleanup certificate validity check mechanism

Update the certificate validity check mechanism to use the asn1 generator outputs for the offset and size of the serial number field rather than hard-coding it.
Originally posted by @pamaury in https://github.com/lowRISC/opentitan/pull/22627#pullrequestreview-2009208766

I can see two slightly different approaches here:

modify the codegen builder so that the structure passed contains the offset and size of every field (simple but waste memory)
same but add a field to the hjson to specify whether the codegen should record the size and offset of certain variables


Connect serialization should gracefully handle null values

Describe the bug
In JavaScript, it is common to use null. In our instance, an upstream library uses null to represent an empty string field instead of the Go standard of "". This isn't inherently incompatible with Protobuf, as long as the Connect library converts null and undefined to "" before attempting serialization, which it does not. Right now, Connect throws.
And again, there is nothing inherently unreasonable about Connect's current behavior unless you consider that this is the JS ecosystem where empty strings are actually rarely used for empty strings...
To Reproduce

Define a protobuf message that has a string field
Pass a payload to Connect that has null instead of an empty string
Connect throws rather than converting the null value to the Protobuf default value of ""

For example, consider the field direction below which may be null. (This comes from the Lexical text editor library)
{
    "children": [
        {
            "children": [
                {
                    "detail": 0,
                    "format": 0,
                    "mode": "normal",
                    "style": "",
                    "text": "1234",
                    "type": "text",
                    "version": 1
                }
            ],
            "direction": null,
            "format": "",
            "indent": 0,
            "type": "paragraph",
            "version": 1
        }
    ],
    "direction": "ltr",
    "format": "",
    "indent": 0,
    "type": "root",
    "version": 1
}

I am guessing you are passing the json you get from the text editor library directly to connect client, right? Something like this:
await client.recordEdits(textEditorOutput);

In this case it will error, one way to solve this is to use fromJson method defined on the protobuf message:
await client.recordEdits(RecordEditsRequest.fromJson(textEditorOutput));

Let me know if I misunderstood the issue.


fix: Wrong currency in collection detail

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #<issue_number>
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

Please resolve conflicts

Please resolve conflicts

✅ Done


EV Meter current & power reading not working

Describe the bug
My EVSE is connected via modbus to 3 phase Eastron meter EDIT: it's a model sdm72d-m. It can correctly read the energy (kWh) total (and thus also the current session), but it fails to read the current and power.
The same on the on screen display or via MQTT.
This used to work in a previous version. I think I was on 3.6.6 before, but I'm not sure.
Upload your config
{"version":"v3.6.10","serialnr":3551,"mode":"SMART","mode_id":3,"car_connected":true,"wifi":{"status":"WL_CONNECTED","ssid":"DriesFi","rssi":-10,"bssid":"60:A4:B7:1E:07:AB"},"evse":{"temp":41,"temp_max":65,"connected":true,"access":true,"mode":1,"loadbl":0,"pwm":102,"solar_stop_timer":0,"state":"Connected to EV","state_id":1,"error":"None","error_id":0,"rfid":"Not Installed"},"settings":{"charge_current":60,"override_current":0,"current_min":6,"current_max":32,"current_main":20,"current_max_circuit":25,"current_max_sum_mains":10,"max_sum_mains_time":5,"solar_max_import":6,"solar_start_current":2,"solar_stop_time":10,"enable_C2":"Always Off","mains_meter":"API","starttime":0,"stoptime":0,"repeat":0},"mqtt":{"host":"<IP_ADDRESS>","port":1883,"topic_prefix":"SmartEVSE-3551","username":"evse","password_set":true,"status":"Connected"},"home_battery":{"current":0,"last_update":0},"ev_meter":{"description":"Eastron3P","address":11,"import_active_power":0,"total_kwh":3190.199951,"charged_kwh":0,"currents":{"TOTAL":0,"L1":0,"L2":0,"L3":0},"import_active_energy":3190.199951,"export_active_energy":0},"mains_meter":{"import_active_energy":0,"export_active_energy":0},"phase_currents":{"TOTAL":0,"L1":0,"L2":0,"L3":0,"last_data_update":0,"original_data":{"TOTAL":0,"L1":0,"L2":0,"L3":0}},"backlight":{"timer":117,"status":"ON"}}

Upload a debug log
Details

(V) (fn_mqtt)(C1) 7 RECEIVED 87:8:10 <- SmartEVSE-3551/Set/MainsMeter
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C1) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 47 6b 48
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C1) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) Current is limited by MaxSumMains: MaxSumMains=12A, Isum=10.5A, Temp_Phases=3.
(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726095910.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=8.8 A, Idifference=0.5, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=8.8 A.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, MaxSumMainsTimer, IsetBalanced=8.8A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 8.8 A.
(V) (CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=8.8 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 8.7 A IsetBalanced: 8.8 A, MainsMeter.Timeout=10, EVMeter.Timeout=64.
(I) (printStatus)(C0) L1: 8.7 A L2: 0.8 A L3: 1.0 A Isum: 10.5 A
(V) (fn_mqtt)(C1) 7 RECEIVED 87:8:10 <- SmartEVSE-3551/Set/MainsMeter
(V) (fn_mqtt)(C1) 7 RECEIVED 88:8:10 <- SmartEVSE-3551/Set/MainsMeter
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 47 6b 4c
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) Current is limited by MaxSumMains: MaxSumMains=12A, Isum=10.6A, Temp_Phases=3.
(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726095913.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=8.9 A, Idifference=0.4, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=8.9 A.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, MaxSumMainsTimer, IsetBalanced=8.9A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 8.9 A.
(V) (CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=8.9 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 8.8 A IsetBalanced: 8.9 A, MainsMeter.Timeout=10, EVMeter.Timeout=64.
(I) (printStatus)(C0) L1: 8.8 A L2: 0.8 A L3: 1.0 A Isum: 10.6 A
(V) (fn_mqtt)(C1) 7 RECEIVED 88:8:10 <- SmartEVSE-3551/Set/MainsMeter
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (fn_mqtt)(C1) 7 RECEIVED 89:8:9 <- SmartEVSE-3551/Set/MainsMeter
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 47 6b 50
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) Current is limited by MaxSumMains: MaxSumMains=12A, Isum=10.6A, Temp_Phases=3.
(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726095915.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=9.0 A, Idifference=0.4, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=9.0 A.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, MaxSumMainsTimer, IsetBalanced=9.0A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 9.0 A.
(V) (CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=9.0 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 8.9 A IsetBalanced: 9.0 A, MainsMeter.Timeout=11, EVMeter.Timeout=64.
(I) (printStatus)(C0) L1: 8.9 A L2: 0.8 A L3: 0.9 A Isum: 10.6 A
(V) (fn_mqtt)(C1) 7 RECEIVED 89:8:9 <- SmartEVSE-3551/Set/MainsMeter
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 47 6b 54
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (fn_mqtt)(C1) 7 RECEIVED 90:8:10 <- SmartEVSE-3551/Set/MainsMeter
(V) (CalcBalancedCurrent)(C0) Checkpoint 1 Isetbalanced=9.0 A Imeasured=9.0 A MaxCircuit=25 Imeasured_EV=0.0 A, Battery Current = 0.0 A, mode=1.
(V) (CalcBalancedCurrent)(C0) Current is limited by MaxSumMains: MaxSumMains=12A, Isum=10.8A, Temp_Phases=3.
(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726095917.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=9.1 A, Idifference=0.4, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=9.1 A.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, MaxSumMainsTimer, IsetBalanced=9.1A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 9.1 A.
(V) (CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=9.1 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 9.0 A IsetBalanced: 9.1 A, MainsMeter.Timeout=11, EVMeter.Timeout=64.
(I) (printStatus)(C0) L1: 9.0 A L2: 0.8 A L3: 1.0 A Isum: 10.8 A
(V) (fn_mqtt)(C1) 7 RECEIVED 90:8:10 <- SmartEVSE-3551/Set/MainsMeter
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 47 6b 58
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) Current is limited by MaxSumMains: MaxSumMains=12A, Isum=10.8A, Temp_Phases=3.
(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726095918.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=9.2 A, Idifference=0.4, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=9.2 A.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, MaxSumMainsTimer, IsetBalanced=9.2A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 9.2 A.
(V) (CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=9.2 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 9.0 A IsetBalanced: 9.2 A, MainsMeter.Timeout=10, EVMeter.Timeout=64.
(I) (printStatus)(C0) L1: 9.0 A L2: 0.8 A L3: 1.0 A Isum: 10.8 A
(V) (fn_mqtt)(C1) 7 RECEIVED 91:8:9 <- SmartEVSE-3551/Set/MainsMeter
(V) (fn_mqtt)(C1) 7 RECEIVED 91:8:10 <- SmartEVSE-3551/Set/MainsMeter
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 47 6b 5c
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) Current is limited by MaxSumMains: MaxSumMains=12A, Isum=10.9A, Temp_Phases=3.
(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726095921.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=9.2 A, Idifference=0.3, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=9.2 A.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, MaxSumMainsTimer, IsetBalanced=9.2A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 9.2 A.
(V) (CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=9.2 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 9.1 A IsetBalanced: 9.2 A, MainsMeter.Timeout=10, EVMeter.Timeout=64.
(I) (printStatus)(C0) L1: 9.1 A L2: 0.8 A L3: 1.0 A Isum: 10.9 A
(V) (fn_mqtt)(C1) 7 RECEIVED 92:8:9 <- SmartEVSE-3551/Set/MainsMeter
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 47 6b 60
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(V) (fn_mqtt)(C1) 7 RECEIVED 92:8:10 <- SmartEVSE-3551/Set/MainsMeter
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) Current is limited by MaxSumMains: MaxSumMains=12A, Isum=11.0A, Temp_Phases=3.
(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726095923.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=9.2 A, Idifference=0.3, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=9.2 A.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, MaxSumMainsTimer, IsetBalanced=9.2A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 9.2 A.
(V) (CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=9.2 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 9.2 A IsetBalanced: 9.2 A, MainsMeter.Timeout=11, EVMeter.Timeout=64.
(I) (printStatus)(C0) L1: 9.2 A L2: 0.8 A L3: 1.0 A Isum: 11.0 A
(V) (fn_mqtt)(C1) 7 RECEIVED 93:8:10 <- SmartEVSE-3551/Set/MainsMeter

To Reproduce
I'm hooked up to MQTT and Home Assistant. I set the mode based on the current state-of-charge of my car, my desired state-of-charge, and which energy tariff is in effect. (Charge in Smart up to the setpoint using cheap rates and switch to solar otherwise.)
I noticed the issue now because my HA dashboard said my ev was used 0W but I was using 2.5kW total power, but I suspect the issue has existed for a bit.
Expected behavior
The EV current & power are read out correctly, like they where in the past.
Screenshots

When you look at the log, the response if the modbus on EVMeter current measurement is all zeroes. This suggests the Eaatron is actually reporting 0A.
This suggests hardware fsilure to me; to rule that out, could you downgrade to e.g. v3.6.2 and upload that debug log while charging?

In v3.6.2 at least the power reading work, not amps, but I'm not sure that ever worked.
Details

(V) (CalcBalancedCurrent)(C0) Checkpoint 1 Isetbalanced=11.2 A Imeasured=11.4 A MaxCircuit=25 Imeasured_EV=0.0 A, Battery Current = 0.0 A, mode=2.
(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726144183.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=11.2 A, Idifference=1.9, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 3 Isetbalanced=11.2 A, IsumImport=0.3, Isum=6.3, ImportCurrent=6.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, IsetBalanced=11.2A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=11.2 A.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 11.2 A(CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=11.2 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 11.4 A IsetBalanced: 11.2 A, MainsMeterTimeout=10, EVMeterTimeout=64.
(I) (printStatus)(C0) L1: 11.4 A L2: -6.0 A L3: 0.9 A Isum: 6.3 A
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 48 74 c9
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0034, token:0x0b040034, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 13 a0 00
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0034 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=11.2 A, Idifference=1.9, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 3 Isetbalanced=11.2 A, IsumImport=0.3, Isum=6.3, ImportCurrent=6.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, IsetBalanced=11.2A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=11.2 A.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 11.2 A(CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=11.2 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 11.4 A IsetBalanced: 11.2 A, MainsMeterTimeout=8, EVMeterTimeout=64.
(I) (printStatus)(C0) L1: 11.4 A L2: -6.0 A L3: 0.9 A Isum: 6.3 A
(V) (fn_mqtt)(C1) 3 RECEIVED 114:-60:9 <- SmartEVSE-3551/Set/MainsMeter(fn_mqtt)(C1) 3 RECEIVED 114:-60:9 <- SmartEVSE-3551/Set/MainsMeter(Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 48 74 cd
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0034, token:0x0b040034, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 13 a0 00
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0034 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726144187.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=11.2 A, Idifference=1.9, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 3 Isetbalanced=11.2 A, IsumImport=0.3, Isum=6.3, ImportCurrent=6.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, IsetBalanced=11.2A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=11.2 A.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 11.2 A(CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=11.2 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 11.4 A IsetBalanced: 11.2 A, MainsMeterTimeout=10, EVMeterTimeout=64.
(I) (printStatus)(C0) L1: 11.4 A L2: -6.0 A L3: 0.9 A Isum: 6.3 A
(D) (Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 48 74 d5
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(V) (fn_mqtt)(C1) 3 RECEIVED 114:-60:9 <- SmartEVSE-3551/Set/MainsMeter(ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0034, token:0x0b040034, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 13 90 00
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0034 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=11.2 A, Idifference=1.9, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 3 Isetbalanced=11.2 A, IsumImport=0.3, Isum=6.3, ImportCurrent=6.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, IsetBalanced=11.2A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=11.2 A.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 11.2 A(CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=11.2 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 11.4 A IsetBalanced: 11.2 A, MainsMeterTimeout=11, EVMeterTimeout=64.
(I) (printStatus)(C0) L1: 11.4 A L2: -6.0 A L3: 0.9 A Isum: 6.3 A
(V) (fn_mqtt)(C1) 3 RECEIVED 114:-60:9 <- SmartEVSE-3551/Set/MainsMeter(Timer100ms)(C0) ModbusRequest 4: Request Energy Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0048, token:0x0b040048, data: 0x0002.
(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 48 74 d9
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0048 Response
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0034, token:0x0b040034, data: 0x0002.
^[(V) (ModbusDecode)(C1) Received packet (7 bytes) 0b 04 04 45 13 90 00
(V) (ModbusDecode)(C1)  valid Modbus packet: Address 0x0b Function 0x04 Register 0x0034 Response
(D) (Timer100ms)(C0) ModbusRequest 20: Request EVMeter Current Measurement Node 0
(V) (ModbusSend8)(C0) Sent packet address: 0x0b, function: 0x04, reg: 0x0006, token:0x0b040006, data: 0x000c.

(V) (CalcBalancedCurrent)(C0) phaseLastUpdate=1726144191.
(V) (CalcBalancedCurrent)(C0) Checkpoint 2 Isetbalanced=11.2 A, Idifference=1.9, mod=0.
(V) (CalcBalancedCurrent)(C0) Checkpoint 3 Isetbalanced=11.2 A, IsumImport=0.3, Isum=6.3, ImportCurrent=6.
(D) (CalcBalancedCurrent)(C0) Checkpoint b: Resetting SolarStopTimer, IsetBalanced=11.2A, ActiveEVSE=1.
(V) (CalcBalancedCurrent)(C0) Checkpoint 4 Isetbalanced=11.2 A.
(V) (CalcBalancedCurrent)(C0) [H]Node 0 = 11.2 A(CalcBalancedCurrent)(C0) Checkpoint 5 Isetbalanced=11.2 A.
(I) (printStatus)(C0) STATE: C Error: 0 StartCurrent: -2 ChargeDelay: 0 SolarStopTimer: 0 NoCurrent: 0 Imeasured: 11.4 A IsetBalanced: 11.2 A, MainsMeterTimeout=10, EVMeterTimeout=64.

I assume that's why I see a big spike (up to the max main fuse rating) initially, the control algo is not happy.
My P1 data has more latency than most I assume: I have to send the P1 data via a slow wireless serial link to my home assistant, which then uses an automation to publish the data to MQTT.
Aside from this spike, which only lasts 2~4 seconds, I've had no issues before. I get why it's not the preferred situation, but can the reading of the kW be restored without impact for other users? If not a separate meter type maybe?
I would really like to avoid having to replace the meter. The setup was paid for by my employer (by ordering the full setup from someone). Replacing the meter would mean not only an invoice which is annoying to explain, but also resetting the kWh total, which is used for power reimbursement.

You might get the desired result by defining a custom meter with the values that are defined for Eastron3P; the custom meter uses the old routine...

Note that a full fledged Eastron SDM72D-M v2 costs €55 incl shipping. The time we spent here is already more ...

Well, that's the one I already have. The SDM630 seems to support A & V measurements, and that one costs ~€130 from reputable places.
But I'll try that custom meter idea.

No you should notice the v2 . The v2 supports all params including currents and power per phase.
Not loving the counter-intuitive naming either, but the v2's are used widely with the SmartEVSE.

Oooh that's great :smile:. I'm sure I'll find a use for the existing meter then.

https://www.amazon.nl/V2-energiemeter-lcd-display-achtergrondverlichting-gekalibreerd/dp/B08X96T1X2/ref=mp_s_a_1_1?crid=1VIWARA7T05ZZ&dib=eyJ2IjoiMSJ9.p9tUs6S1zefo74pcNdZdbKc-JUwgRaQPB2G7NEVGxuS0bjJgEhz2BkRcaTtCRoPvdR8JY3XX8MVSIaikPIH3TE9x1uzlaZ1m2GtiyEC5l9XE9icmytDPDsA1KTI-NA1Y4y8vT3kQt1JOu0ApJpYQq_3-dRcj948Pzn6xll55frc.rLDnpZGAmFNYRNr45O_r1qFGaHKdiw6T2is9pO8_wxU&dib_tag=se&keywords=eastron+sdm72d-m+v2&qid=1726164156&sprefix=eastron+%2Caps%2C345&sr=8-1


Secure config

Support securing config data. SecureConfig

Support for passwords landed in https://github.com/datapartyjs/dataparty-crypto/issues/5

It may make more sense for this to be a Keychain sort of class directly in @dataparty/crypto as it likely has broader use for automatically clearing private keys from memory


Catalog updates should not use hard coded value for /configs directory during catalog rebuilds

Version
N/A ... evaluated the master branch reviewing the code
What happened?
I was evaluating the code to see how the operator catalogs are built within oc-mirror and noticed that the code which processes an existing catalog using this process:

delete the /configs directory using a "whiteout file"
add back in the current contents of the FBC into the /configs directory

This process takes place in the processCatalogRefs function here.
The problem as I see it, is that the /config directory is hard coded and does not attempt to take into account the possibility of re-defining the location of where your FBC content resides via the operators.operatorframework.io.index.configs.v1 label. So if I create my catalog image using file path called /destination like this example:
# The base image is expected to contain
# /bin/opm (with a serve subcommand) and /bin/grpc_health_probe
FROM quay.io/operator-framework/opm:latest

# Configure the entrypoint and command
ENTRYPOINT ["/bin/opm"]
CMD ["serve", "/destination"]

# Copy declarative config root into image at /configs
ADD mysource /destination

# Set DC-specific label for the location of the DC root directory
# in the image
LABEL operators.operatorframework.io.index.configs.v1=/destination

I believe that the code as it is written would attempt to blindly update the hard coded path /configs rather than the path defined by my catalog.
What did you expect to happen?
I would expect that the code would honor the source catalog's operators.operatorframework.io.index.configs.v1 directory
How to reproduce it (as minimally and precisely as possible)?

Create a mirror-config.yaml that has an operator entry in it
$ oc-mirror --config mirror-config.yaml docker://localhost:5000

Anything else we need to know?
Note I did NOT run the oc-mirror to validate any behavior... my report is based solely on reviewing the code. Happy to be proven wrong about what the code is actually doing.
References

None

Hi @jchunkins, thanks for the question/issue. You are correct. oc-mirror does honor this location when mirroring the requested catalog and processing the FBC contents, but when rebuilding the catalogs it does use the /configs directory as the place to store FBC content. The CMD is updated as well as the operators.operatorframework.io.index.configs.v1 label. I don't see any issue with honoring the current location instead of using /configs.

@jpower432 So if I understand correctly the process is:

Read original catalog
Process original catalog honoring the operators.operatorframework.io.index.configs.v1 label
Create replacement catalog based on the original catalog, but now it uses new FBC contents with updated CMD and  operators.operatorframework.io.index.configs.v1 to use /configs instead.

Do I have that high level process right?
Since the new catalog contents will now reside in /configs in the resulting catalog, the old directory might still be present, but effectively it won't be used. Is that right?

@jchunkins. Yep, you have it right. I do think we could support custom catalogs better in this method by preserving their labels instead of overwriting them, but if the original concern was that the original FBC would not be processed correctly, we should be good there.

@jpower432 Thanks for the clarification on all of this. I did not have the full picture, and I interpreted the hard coded values as a sign that the label defined in the original catalog might not be honored (i.e. I thought the code was making assumptions that it was always /configs).
It still seems like the process as described potentially leaves the original folder (i.e. /destination in my example) in place because the "whiteout file layer" (i.e. /.wh.configs) as defined only blows away the /configs directory and replaces it with the new FBC content. In other words, the replacement catalog is based on the original catalog, and the original catalog still has /destination since it is never cleaned out with its own "whiteout file layer". Not the end of the world kind of problem but could be confusing for someone poking around inside a catalog image and finding two different directories... one that's used, and another that's just left over stuff.

@jchunkins No problem. I think your point about having the leftover config directories is fair. I will add this issue to the backlog. I appreciate your thoughts on this.

/remove-lifecycle stale


add oncancel callback to editable form

What i am trying to achieve is:
We have two fields in the form, one field is dropdown, and second field is regular input.
Now i need to show the input field, only if a perticualr option is selected in dropdown.
So i guess, only choice i have is to add e-ng-change to the dropdown (as the model will not update untill save).
So what i do is, on e-ng-change, i set a flag in the scope to show or hide the second input.
But if user cancel editing the form, i need to clear this flag, so when user click "edit" button again, the previously rememberd flag should not apply.
If there's a oncancel callback, i can reset whatever scope changes i had made during when user was editing the form..

Never mind, it was a silly question.. i was misguided by a custom directive we have for creating submit/cancel buttons. i can always have onclick on my cancel button..


Server app crashes when more than 64 textures are synchonized by network

Describe the bug
First for all, thank you for a greate library!
Server app crashes when more than 64 textures are synchonized by network.
I think the problem can be in  undefined behavior between thread which read and thread which write texures to Client::mpPendingTextures buffer. Client::ReceiveTexture method can write texture to same array cell which is reading now in Client::ProcessPendingTextures method. This is"data race" and can crash the server app. There is no any multithread synchronization (mutex, conditional values, etc.) between this two calls. Only read/write operation on index is synced by atomic values.
If I change Client::mpPendingTextures to 128 size the problem is gone.
In my project I reimplement this logic in a way to use  std::queue to push/pop textures in different threads and synchonize this calls wtith std::mutex (conditional values) and checking max size of queue (64). Made PR for this change #27 .
To Reproduce
Steps to reproduce the behavior:

Sync more than 64 textures between client and server

Expected behavior
All textures synced correctlly without undefined behavior
Desktop (please complete the following information):

OS: Windows 10
Version 1.75

Thanks! I'm glad to see the code was clear enough for you to find and fix the issue.
I have been avoiding using std containers / mutex as much as possible, keeping performances up and memory usage down, but this is not as critical in the Server app. I mostly cared about minimizing impact on client code. I was not expecting a high amount of textures (rookie mistake :) ), so this had not been tested as much. The texture lookup on the server is not ideal either, since I just iterate the vector for every drawcall, looking for the textureid.
I will take a look this weekend, might take your PR as is, or maybe just do what I did on the client side, use a spin lock in rare case where we are about to overflow the ring buffer.

Thank you for quick reply!
Is there any code conventions? I have idea to next PR and want write code as more closer to original sources :)

I have not formalized a coding convention for the project.
I more or less follow this
I usually prefix class variable with 'm', pointer with 'p', bool with 'b' and constant with 'k'.
I use camel case, with first letter lowercase for function parameters, uppercase start for local variables.
I usually try to use typed class enums.
Defines are all uppercase
With a series of assignments, I align them by the equal operator.
Warning level is set to 'Wall' so I fix all compiling warnings.
If something stick out in your PR code (coding style difference), I will let you know.

Note: you can search for mTexturesPendingCreated to see how did my spin lock on the client side, avoiding a mutex/dynamic mem alloc. (NetImgui_Api.cpp : 323)

PR 28 fixed the issue


Signup and Login

Asana tasks:

Login: https://app.asana.com/0/37131652076106/46141439482573
Registration: https://app.asana.com/0/37131652076106/46141439482548

Goal
Enable user login, logout and new user sign up.
Testing

Start up Coinstac and remove the auth local storage items:

localStorage.removeItem('COINSTAC_AUTH_RESPONSE');
localStorage.removeItem('COINSTAC_USER');

Refresh the page to get accurate application state
Try to log in. Your username and email should be in the bottom left corner of the app.
Try to sign up. The form should catch basic errors, and it should redirect to the “Home” route on success.
Try to log out. It should redirect you to the login form.

this is rad! super works.

There was an issue with logout, but I'm going to merge anyway


Use the filename when no title attribute is present

Hey @jackyzha0, I found that for my digital garden use case many of my files did not have the necessary title frontmatter and this seemed like a sensible default (at least for me). If it's useful to you, feel free to use it, if not my feelings won't be hurt either.

hey @brandonkboswell, thank you for your contribution! does this commit in the main Quartz repo work for you? https://github.com/jackyzha0/quartz/commit/94e987dab5a50196bc2273addc6f908178abd0fb (this was a pretty recent change though 😅 )

Closing for now as I avoid making changes to the scraper unless necessary :)

@jackyzha0 I reverted my hugo-obsidian branch after taking the new branches of both and noticed I was getting a bunch of Untitled Pages again. It looks like hugo-obsidian will set the page title to "Untitled Page" if there is no title (https://github.com/jackyzha0/hugo-obsidian/blob/4c489480bde6ef0babc2b85739f686528d2e1062/walk.go#L47), so I don't think the changes in Quartz are going to kick in. Also the changes that you made to the Graph are probably going to also need to be made to the backlinks template to make this change work everywhere.

Kudos on all the new improvements in Quartz btw, they look great.


RuboCop suggests inherited extensions

Expected behavior
RuboCop does not suggest to add extensions that have already been configured in an inherited gem.
Actual behavior
RuboCop suggests extensions that are already configured.
Steps to reproduce the problem

set up a project that depends on rspec
put inherit_gem in its .rubocop.yml, and inherit from a gem that depends on rubocop-rspec and has require: rubocop-rspec in its RuboCop config
run RuboCop and receive an extension suggestion for rubocop-rspec

Minimal repro here: https://github.com/haines/rubocop-inherited-extensions-bug
$ git clone https://github.com/haines/rubocop-inherited-extensions-bug.git
$ cd rubocop-inherited-extensions-bug/project
$ bundle install
$ bundle exec rubocop
Inspecting 2 files
.C

Offenses:

spec/some_spec.rb:3:16: C: RSpec/DescribeClass: The first argument to describe should be the class or module being tested.
RSpec.describe 'offensive' do
               ^^^^^^^^^^^

2 files inspected, 1 offense detected

Tip: Based on detected gems, the following RuboCop extension libraries might be helpful:
  * rubocop-rspec (http://github.com/rubocop-hq/rubocop-rspec)

You can opt out of this message by adding the following to your config (see https://docs.rubocop.org/rubocop/extensions.html#extension-suggestions for more options):
  AllCops:
    SuggestExtensions: false

From the offense that's detected, it's clear that rubocop-rspec is configured, so the "Tip" shouldn't be displayed.
RuboCop version
$ bundle exec rubocop -V
1.5.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.3.0, running on ruby 2.7.2 x86_64-darwin19)
  - rubocop-rspec 2.0.1

Sounds like a task for @dvandersluis.

Yeah it's not currently considering what's activated in rubocop.yml, just what's found from gems. I'll take a look!

@haines In the meantime this configuration should work for you:
AllCops:
  SuggestExtensions:
    rubocop-rspec: false

@haines can you confirm that rubocop-rspec is in your Gemfile.lock?

@dvandersluis thanks for looking into this!
rubocop-rspec is in the Gemfile.lock: https://github.com/haines/rubocop-inherited-extensions-bug/blob/ace95f260920531df2f9a84d1e9ba39868611955/project/Gemfile.lock#L43
It's not in the Gemfile, though; it's a transitive dependency.


Extract jwt logic to commons (WIP)

Working branch for #47

tests passed! (was some testing infra hickup), thanks!


Introduce a convenience method richComment in all classes

I think it would be nice to have the option to write Myclass richComment which return the same rich text comment as shown in the browser.
I imagine it should be an extension method defined in BeautifulComments.
As it is now, one has to make a builder, call buildMicroDownUsing:withComment:, and render the contents of the builder.

By "in all classes" I just mean a single method placed in ClassDescription


About Reloading Weapons

Description
If I spam the Q Key, a new reload sound will come before the reload sound ends. By the way, if I go directly to another slot while reloading, the reload sound continues until it ends. In other words, if the reload is canceled, a feature is required that will stop the previous sound.
https://user-images.githubusercontent.com/89253304/165473979-bb6dc26c-025e-4388-8513-6adb5783df17.mp4
The /stopsound command can be used to cancel the sound, but the players should not receive a message.
Configuration
It should work automatically.

Spigot has methods for stopping sounds (both custom and normal). See https://hub.spigotmc.org/javadocs/spigot/org/bukkit/entity/Player.html#stopSound(java.lang.String)

While it is possible to stop sounds after they begin to play, our code prevents us from easily accomplishing this (Without some amount of rewriting). We recommend using 2 short sounds for start and end. The default weapons do this already:
    Start_Mechanics:
      Sounds:
        - "custom:reload.start.normal-0.5-1-0-0.1"
    Finish_Mechanics:
      Sounds:
        - "custom:reload.end.normal-0.5-1-0-0.1"

If you need this feature still, join our discord and ask about paying for this to be added.


[BUG]  ocpp1.6 RemoteStartTransaction reply is sent only after StatusNotification.req + Authorize.req + StartTransaction.req

Duplicate issue

[X] I've searched for any related issues and avoided creating a duplicate issue.

Description
handleRequestRemoteStartTransaction is waiting only after status-notification + authorize if needed + start-transaction to send the central-system a reply on the remote-transaction, isn't it not according the the protocol/docs?
e-mobility-charging-stations-simulator version
1.0.1
Node.js version
v21.5.0
System
System:
OS: macOS 14.3
CPU: (10) arm64 Apple M1 Pro
Memory: 77.25 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Expected result
The simulator replying with RemoteStartTransaction.conf and then manage the sequence of StatusNotification, Authorize and StartTransaction
Actual result
No response
Steps to reproduce
No response
Attachments
No response

Could you please extract the OCPP spec content that seems not respected by the code in the repo?
Are you sure about the simulator version reported in the issue?

Thanks for the reply!
According to the docs here https://www.oasis-open.org/committees/download.php/58944/ocpp-1.6.pd -
RemoteStartTransaction is no different then other message that each request should get a reply result/error, the remote-start if accepted has effects later that it shall do+send status, authorize if needed, update and start-transaction

Where exactly the code miss to follow the spec? The code behave as written, expect if a template tunable flag is changed.

What flag is it? maybe I missed it

The start transaction response is checked only if AuthorizeRemoteTxRequests is set to true, which is not the behavior described in the specs.

That's fine and following the docs completely, but why the RemoteStartTransaction reply isn't sent after the central-system request and is only sent after the start-transaction reply from central-system?
I think that this is the right flow -
sequenceDiagram
autonumber

CS->>CP: RemoteStartTransaction.req
CP-->>CS: RemoteStartTransaction.conf

CP->CS: Should authorize?
CP->CS: StatusNotification

CP->>CS: StartTransaction.req
CS-->>CP: StartTransaction.conf

Where currently it sends the central-system the RemoteStartTransaction.conf after the StartTransaction.conf instead of after the RemoteStartTransaction.req

The asynchronous authorization check described in the spec is:

pointless
require some supplemental code to stop the transaction if finally the start transaction response is not accepted

I do not see the point to start the transaction if AuthorizeRemoteTxRequests is set to false, then check if the transaction can be started via a startTransaction, then conditionally stop the started transaction ...
If I only make the code return an accepted answer without adding the startTransaction check and conditional stopTransaction.
So I will implement a synchronous authorization check for all cases.

@Ohad31415: Could you please confirm or infirm that PR fix the issue by checking out its branch?

I still doesn't reply to the RemoteStartTransaction first and does it after waiting for response for StartTransaction from central-system

@Ohad31415: and with the latest commit in the commit triggering a delayed start transaction?

I still get the start-transaction before the reply on the remote-start-transaction

The event emission is queued in the promises queue. Hopefully the FIFO will queue it after the OCPP request promise resolving in most case.

The event emission is queued in the promises queue. Hopefully the FIFO will queue it after the OCPP request handler promise resolving in most case.

The latest code in main implement a deterministic chronologically ordered 2 stages incoming request handling framework.


Typo "Microsoft Teams Room"→"Microsoft Teams Rooms"

https://learn.microsoft.com/en-us/microsoftteams/rooms/enroll-a-device
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/blob/live/Teams/rooms/enroll-a-device.md
#PingMSFTDocs

@altsou
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Add ingress resources

Add Terraform implementation for ingress solution including Azure Front Door Premium and any dependencies. Azure Application Proxy deployment instructions will be provided in the md as it cannot be automated via IAC.

This was completed with my last pr.


Added support for current fan state and hvac action

Description:
Updated Venstar component to add support for the hvac_action property and updated fan_mode to pull from fan_state of thermostat
Checklist:

[x ] The code change is tested and works locally.
[x ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x ] There is no commented out code in this PR.
[ x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ x] Untested files have been added to .coveragerc.

Hi @david81,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Thanks for that. Misread the docs, apparently. Is there no available property for the current fan state at this time?

No, not in the climate base component. But the venstar attributes exposes this:
https://github.com/home-assistant/home-assistant/blob/560ac3df3a400f5b413fa4028c1bcfeefac9d9c9/homeassistant/components/venstar/climate.py#L179


Create new types to catalog refrigeration units

The link to where the sample should be stored:
https://github.com/odpi/egeria-samples-api/tree/main/operations-inventory/refrigeration-unit-types


Calibration of 3 ProCams fails to "solve" or to connect correctly

Hey Andy.
We've made a big setup (3 projectors and 3 kinects) and are trying to calibrate a single square room. However our efforts in doing so are giving multiple problems. After an entire day of using Aqure/Solve with different tweeks to our setup (rigied objects in overlapping sections, projector/kinect angles and so on.) we are still not able to calibrate out room. The layout is simple enough that It should be possible, but without further knowledge debugging is getting to the point of randomness.

Some of them managed to run through the solve phase, but ended with terrible RMS errors (>40) while others simple failed and threw an error at ProjectorCameraEnsemble.cs, line 877, where numCompletedFits must not be 0.
Through trial and error it seems like the center projector fails to calibrate during solve.
Also is there any guidelines / requirements on the order projectors and cameras are written in the ensemble.xml file? Can the cameras be listen in the order "left, center, right" while the projectors are listed "center, left, right" or do their ordering have to be the same?
Any help with calibration of our room is much appreciated.
PS. Inside 3_boxes_ensemble.rar is 2 screenshots of the finished calibration process, showing the left and right pieces barely attached to the center piece.

TL;DR: If you have problems with solving. Try placing large rigged light objects (white / yellow / green) in the overlapping area
After talking with our superviser it was revealed to us that the boxes that we used was the problem, as they were completely black. This made them absorb the infra red light, used by the kinects to measure depth. Covering the boxes in white sheets fixed it and the calibration ran through without any problems

Good to hear!


ceph: 16.2.5 -> 16.2.6

Motivation for this change
https://docs.ceph.com/en/latest/releases/pacific/#v16-2-6-pacific
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

@ofborg eval


did Body.scale change the speed?

I scale the body to fit the different phone size, but i found the speed has been changed, it become fast at small screen. is that Body.scale change speed?
this's body.scale code

const rect = Bodies.rectangle(x, y, width, height, {
   elementType: type,
   friction: 0.3,
   render: {
       sprite: {
           key,
           texture: src,
           xScale: scaleFixed,
           yScale: scaleFixed
       }
   },
   collisionFilter: {
       group: 1
   },
   chamfer: {
       radius: 10
   }

});
Body.scale(rect, scaleFixed, scaleFixed);

I'd assume yes as Body.scale physically changes the size of the body including its mass, so this will change its dynamics.
It sounds like you should scale your drawing instead in this case?


Some fixes and additions to QuantumStorage

*Keybinds work in autopause
*Fixed QuantumStorage always opened PiggyBank
*Fixed Player's inventory freeze if QuantumStorage was opened with Autopause enabled
*MiddleMouse click on QuanumStorage in Player's inventory opens selected storage

Much appreciated, thanks for the fix :)


Run ESLint in pre-commit hook when TS files are changed

This changes a few places where ESLint was configured to only look at JavaScript files instead of both JS and TypeScript.
The change to lint-staged's configuration in package.json causes the pre-commit hook to run ESLint on TS files as well as JS files that were modified in the commit.
The change in .eslintrc.js makes ESLint complain about console logs in TS files in the src directory (as it currently does for JS files).

Failed/flaky integration test is irrelevant.


Changing a cluster name via site_relation, doesn't actually apply the change to netbox

I defined the cluster_site_relation and host_site_relation in the settings, it seems to be getting handled properly but the changes are never applied to netbox:
2020-11-20 21:35:09,123 - DEBUG2: Parsing vCenter cluster: c1-V1
2020-11-20 21:35:09,123 - DEBUG2: Trying to find site name for cluster 'c1-V1'
2020-11-20 21:35:09,123 - DEBUG2: Found a match (.*) for c1-V1, using site 'Van 3'
2020-11-20 21:35:09,123 - DEBUG2: Parsing 'cluster' data structure: c1-V1
2020-11-20 21:35:09,123 - DEBUG2: Parsing 'cluster type' data structure: VMware ESXi
2020-11-20 21:35:09,123 - DEBUG: Updated cluster type object: VMware ESXi
2020-11-20 21:35:09,123 - DEBUG2: Parsing 'cluster group' data structure: c1-V1
2020-11-20 21:35:09,123 - DEBUG: Updated cluster group object: c1-V1
2020-11-20 21:35:09,123 - DEBUG2: Parsing 'site' data structure: Van 3
2020-11-20 21:35:09,123 - DEBUG: Updated site object: Van 3
2020-11-20 21:35:09,123 - INFO: Cluster 'c1-V1' attribute 'site' changed from 'vCenter: c1' to 'Van 3'
2020-11-20 21:35:09,123 - DEBUG: Updated cluster object: c1-V1

Even with debug3, I don't see it actually sending a request to netbox to apply that change.

I rolled back my database to before I started testing and ran it fresh, things were associated to the correct site properly. Issue is only on change/update.

And there is no patch request in the logs for an update?
Will have to test this as well. Thank you again.

Correct, no patch or other api req at all that I can see. Thanks for dealing with my flood of issues, happy to help troubleshoot where I can.

Na, this is pretty valuable help. I try think of as much as possible scenarios to test for. But i will never catch every case with so many moving parts and conditions. Help is highly appreciated to make it a robust and reliable tool.

Hi,
I tested it and I ran into quite some trouble. Implementing this would be quite difficult.
Following steps would be necessary:

remove VLANs from all device interfaces
remove IP addresse from all device interfaces
remove cluster and site attributes from device
make sure all cluster items are removed from cluster
assign new site to cluster
assign device to new cluster and site
create new prefixes, VLANs and VRFs in new site
add VLANs and IP addresses to device interfaces

NetBox gave me following errors (examples):
2020-11-24 14:59:04,766 - DEBUG2: Sending PATCH to 'http://localhost:80/api/virtualization/clusters/10/' with data 'b'{"site": 8}''.
2020-11-24 14:59:05,234 - ERROR: NetBox returned: PATCH /api/virtualization/clusters/10/ Bad Request
2020-11-24 14:59:05,234 - ERROR: NetBox returned body: {'site': ['3 devices are assigned as hosts for this cluster but are not in site NEWSITE']}
2020-11-24 14:59:05,306 - DEBUG2: Sending PATCH to 'http://localhost:80/api/dcim/devices/604/' with data 'b'{"site": 8}''.
2020-11-24 14:59:06,086 - ERROR: NetBox returned: PATCH /api/dcim/devices/604/ Bad Request
2020-11-24 14:59:06,087 - ERROR: NetBox returned body: {'cluster': ['The assigned cluster belongs to a different site (OLDSITE)']}
2020-11-24 14:59:13,545 - DEBUG2: Sending PATCH to 'http://localhost:80/api/dcim/interfaces/9145/' with data 'b'{"untagged_vlan": 197}''.
2020-11-24 14:59:13,938 - ERROR: NetBox returned: PATCH /api/dcim/interfaces/9145/ Bad Request
2020-11-24 14:59:13,939 - ERROR: NetBox returned body: {'untagged_vlan': ["VLAN Storage (2) must belong to the same site as the interface's parent device, or it must be global."]}

This stretches complexity pretty far.
What do you think?

I don't think all that should be necessary, since netbox will let me change the site for a cluster/host via the gui without all that?

Hi,
Just tried to change site for an existing cluster in NetBox. Same result.
I would close this issue as won't fix.


'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds

ant -buildfile ./src/build/build.xml release
Buildfile: /root/komodoGUI/src/build/build.xml
checkJavaHome:
compile:
[javac] /root/komodoGUI/src/build/build.xml:83: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 40 source files to /root/komodoGUI/build/classes
[javac] Note: /root/komodoGUI/src/java/com/vaklinov/zcashui/DashboardPanel.java uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
copyResources:
jar:
[jar] Building jar: /root/komodoGUI/build/jars/KomodoSwingWalletUI.jar
release:
[taskdef] Could not load definitions from resource com/sun/javafx/tools/ant/antlib.xml. It could not be found.
BUILD FAILED
/root/komodoGUI/src/build/build.xml:157: Problem: failed to create task or type javafx:com.sun.javafx.tools.ant:application
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken place.
No types or tasks have been defined in this namespace yet
Total time: 12 seconds
root@kmd:~/komodoGUI#

you have to set your java home path

@erezrb @ca333 User's will also see this issue if they are not running Java 7 with Update 6 or better. Some nix based users may install an older version using apt-get or yum  package managers. The javafx ant library will not be present in the early version of Java 7.
https://docs.oracle.com/javase/9/deploy/javafx-ant-tasks.htm#JSDPG177

Additional reference https://stackoverflow.com/questions/34243982/why-is-javafx-is-not-included-in-openjdk-8-on-ubuntu-wily-15-10


Can't read output of AudioRecorder Xamarin forms

I'm using Audio Recorder to record audio in Xamarin Forms.
but as I asked here I had a problem with playing the output of Audio Recorder with my Xiaomi Device.
and when I installed it on a Samsung Device and it works on it.
but when I tried to read and edit it with NWaves. I got this error :
System.IO.EndOfStreamException
Unable to read beyond the end of the stream.

How I can make this output readable for Xiaomi devices and also NWaves?

Can you provide some code? What WAV file are you trying to read? You can copy this file to PC and try opening it with NWaves using demo apps.
Also, I assume, you're trying to open (i.e. read, load) the file - not play it or record it: NWaves does not provide such methods, it's a DSP library.

it's the second week which I'm trying to just record audio in xamarin which has an RIFF header, actully an audio which Nwaves can work with.
I tried Audio Recorder Plugin and Audio Record and [Media Recorder][3] . I asked many questions but got no answer.
the easiest way was [Audio Recorder Plugin][1], but the output hasn't RIFF header.
the output of [Media Recorder][3] was .3gp which I couldn't convert it to .wav.
and the output of Media Recorder was .pcm which also couldn't convert to .wav
here is the last code I tried :
#region Properties
    int SAMPLING_RATE_IN_HZ = 44100;
    ChannelIn CHANNEL_CONFIG = ChannelIn.Mono;
    Android.Media.Encoding AUDIO_FORMAT = Android.Media.Encoding.Pcm16bit;
    int BUFFER_SIZE_FACTOR = 2;
    int BUFFER_SIZE;
    bool RecordingInProgress = false;
    private AudioRecord recorder = null;
    #endregion
    public void Record()
    {
        BUFFER_SIZE = AudioRecord.GetMinBufferSize(SAMPLING_RATE_IN_HZ,
        CHANNEL_CONFIG, AUDIO_FORMAT) * BUFFER_SIZE_FACTOR;
        recorder = new AudioRecord(AudioSource.Mic, SAMPLING_RATE_IN_HZ,
            CHANNEL_CONFIG, AUDIO_FORMAT, BUFFER_SIZE);

        recorder.StartRecording();
        RecordingInProgress = true;
        RecordingTask();
    }
    public Task RecordingTask()
    {
        return Task.Run(() =>
        {
            string path = "appdir/demo.pcm";
            MemoryStream buffer = new MemoryStream(BUFFER_SIZE);
            FileOutputStream outStream = new FileOutputStream(path);
            var demo2 = RecordingInProgress;
            while (RecordingInProgress)
            {
                int result = recorder.Read(buffer.GetBuffer(), 0, BUFFER_SIZE);
                if (result < 0)
                {
                    throw new Exception("Reading of audio buffer failed: ");
                }
                   outStream.Write(buffer.GetBuffer(), 0, BUFFER_SIZE);
            }

        });
    }
    public void Stop()
    {
        if (null == recorder)
        {
            return;
        }

        RecordingInProgress = false;

        recorder.Stop();

        recorder.Release();

        recorder = null;
    }

}

this code makes a .pcm file that can't convert to anything with even cloud converters.
I also tried this :
NWaves.Audio.WaveFile waveFile = new NWaves.Audio.WaveFile(buffer.GetBuffer());
                waveFile.SaveTo(new FileStream("appdir/demo.wav", FileMode.Create));

insted of  outStream.Write(buffer.GetBuffer(), 0, BUFFER_SIZE); at the bottom of while closing block
but it says : No RIFF found
there is about 4 or 5 way to record audio. Nwaves can't work with any of them.
the last try I want to do is add RIFF header to the recorded audio buffer(bytes) programmatically or convert .3gp or .pcm to .wav programmatically.
summary: someone helps me to record an audio in xamarin which Nwaves can work with.
thanks
-- this is the last question I asked in stackoverflow. I also asked the same question at this link

OK, so you just need to read the contents of .pcm file.
WaveFile class represents the WAV container, i.e. the PCM data + WAV header. The latter is necessary for correct interpretation of the data in 'pcm' part. And since you know exactly the audio parameters during recording, just read the array of samples from the pcm file:

// mono mode and Pcm16bit (like in your example):

DiscreteSignal signal;

// sample.pcm is essentially just an array of bytes:
using (var streamIn = new FileStream("sample.pcm", FileMode.Open))
{
    var length = (int)streamIn.Length / 2;     // divide by 2, because each sample is represented with 2 bytes (Pcm16bit)

    signal = new DiscreteSignal(8000, length);    // reserve space in the signal for number of samples: length

    using (var reader = new BinaryReader(streamIn))
    {
        for (var i = 0; i < length; i++)    // just read samples
        {
            signal[i] = reader.ReadInt16() / 32768f;
        }
    }
}

// then you can save it to WAV file, if necessary:

 var waveFile = new WaveFile(signal);

using (var stream = new FileStream("sample.wav", FileMode.Create))
{
    waveFile.SaveTo(stream);
}

Thank you Sooooooooo Much ❤


Fix Execution Operation

Currently, when executing a Structured Query, all sets of the Exclusion Criteria are combined with union operations. This is incorrect since the Structured Query's Exclusion Criteria are defined to have Intersections it the inner level.

Fixed by #63


Add tutorial index redirect

Add a redirect for the old tutorial index.

Tested via #9534 with python tests/scripts/ci.py docs --full --tutorial-pattern none, the redirect successfully sends <host>/tutorials -> <host>/tutorials/index.html

@areusch another easy docs redirect fix

Thanks @hogepodge @driazati, this is merged now!


Build App IOS ERROR

Description
2 days ago when I built it it was normal, but now when I build it there is an error
Run fastlanne :
Generating debug ReliposSaleOrder » ReliposSaleOrder.app.dSYM
› Executing ReliposSaleOrder » Bundle React Native code and images
the transform cache was reset.

❌  error: File /Users/expo/Library/Developer/Xcode/DerivedData/ReliposSaleOrder-ewdmlwntzptsgbdugffzlcepqjhl/Build/Intermediates.noindex/ArchiveIntermediates/ReliposSaleOrder/BuildProductsPath/Release-iphoneos/ReliposSaleOrder.app/main.jsbundle does not exist. This must be a bug with React Native, please report it here: https://github.com/facebook/react-native/issues
Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')

▸ ** ARCHIVE FAILED **
▸ The following build commands failed:
▸ 	PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/expo/Library/Developer/Xcode/DerivedData/ReliposSaleOrder-ewdmlwntzptsgbdugffzlcepqjhl/Build/Intermediates.noindex/ArchiveIntermediates/ReliposSaleOrder/IntermediateBuildFilesPath/ReliposSaleOrder.build/Release-iphoneos/ReliposSaleOrder.build/Script-00DD1BFF1BD5951E006B06BC.sh (in target 'ReliposSaleOrder' from project 'ReliposSaleOrder')
▸ (1 failure)
** ARCHIVE FAILED **
The following build commands failed:
PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/expo/Library/Developer/Xcode/DerivedData/ReliposSaleOrder-ewdmlwntzptsgbdugffzlcepqjhl/Build/Intermediates.noindex/ArchiveIntermediates/ReliposSaleOrder/IntermediateBuildFilesPath/ReliposSaleOrder.build/Release-iphoneos/ReliposSaleOrder.build/Script-00DD1BFF1BD5951E006B06BC.sh (in target 'ReliposSaleOrder' from project 'ReliposSaleOrder')

(1 failure)
React Native Version
0.70.14
Output of npx react-native info
System:
OS: macOS 12.6.8
CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
Memory: 39.93 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.18.0 - /usr/local/bin/node
Yarn: Not Found
npm: 9.8.1 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: Not Found
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.14 => 0.70.14
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
eas build --platform ios
Snack, screenshot, or link to a repository
Snack : https://snack.expo.dev/@phanmemhopnhat/e3c950

Help me Pls

Also seeing the same exact issue

i have the same error too.

I am also trying to build in Expo and I'm getting the same error:
+ [[ ! -f /Users/expo/Library/Developer/Xcode/DerivedData/MyApp-dytmggbduaumbmbkuwfpwuxdshsg/Build/Intermediates.noindex/ArchiveIntermediates/MyApp/BuildProductsPath/Release-iphoneos/MyApp.app/main.jsbundle ]]

+ echo 'error: File /Users/expo/Library/Developer/Xcode/DerivedData/MyApp-dytmggbduaumbmbkuwfpwuxdshsg/Build/Intermediates.noindex/ArchiveIntermediates/MyApp/BuildProductsPath/Release-iphoneos/MyApp.app/main.jsbundle does not exist. This must be a bug with React Native, please report it here: https://github.com/facebook/react-native/issues'

error: File /Users/expo/Library/Developer/Xcode/DerivedData/MyApp-dytmggbduaumbmbkuwfpwuxdshsg/Build/Intermediates.noindex/ArchiveIntermediates/MyApp/BuildProductsPath/Release-iphoneos/MyApp.app/main.jsbundle does not exist. This must be a bug with React Native, please report it here: https://github.com/facebook/react-native/issues

+ exit 2

Yes, am seeing the same after upgrading to 0.7.14

same issue

same issue here and waiting for any suggestion or solution too
build successfully without issue until last friday
Success case:
2023-10-26T15:42:39.2133230Z [RUN_FASTLANE] › Executing ABC» Bundle React Native code and images
2023-10-26T15:42:40.2456460Z [RUN_FASTLANE]     the transform cache was reset.
2023-10-26T15:51:10.7752570Z [RUN_FASTLANE] › Executing ABC» [CP] Copy Pods Resources
2023-10-26T15:51:13.2351730Z [RUN_FASTLANE] › Executing ABC » [CP-User] [RNFB] Core
Fail case
2023-10-27T09:01:32.5098180Z [RUN_FASTLANE] › Executing ABC» Bundle React Native code and images
2023-10-27T09:01:32.5496440Z [RUN_FASTLANE]     the transform cache was reset.
2023-10-27T09:05:18.7416620Z [RUN_FASTLANE]
2023-10-27T09:05:18.7423060Z ❌  error: File /Users/runner/Library/Developer/Xcode/DerivedData/ABC-fqrtiynyduzjgvdyoccmjndnoggp/Build/Intermediates.noindex/ArchiveIntermediates/ABC/BuildProductsPath/Release-iphoneos/ABC.app/main.jsbundle does not exist. This must be a bug with React Native, please report it here: https://github.com/facebook/react-native/issues

this fixed it for me: https://docs.expo.dev/guides/using-hermes/#using-sdk-47-or-lower

@Minh-ka This worked for me - thank you so much. We're getting ready to launch our product and I've been at a standstill for two days on this issue! Thank you! 👏

@Minh-ka Solved!! thank you 👏

@Minh-ka
thanks, your method works like a charm

why

@Minh-ka thank you for the suggestion. However, i'd like to know why doing this please

If you are using Expo, please open an issue in their repo, not in React Native one. They will be better equipped to answer your question.

@Minh-ka I tried this but it didn't work, Do you know anything else I can try?
System:
OS: Windows 10 10.0.22621
CPU: (12) x64 AMD Ryzen 5 5600G with Radeon Graphics
Memory: 3.22 GB / 15.37 GB
Binaries:
Node: 18.17.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
AllowAllTrustedApps: Enabled
IDEs:
Android Studio: AI-222.4459.24.2221.9971841
Visual Studio: Not Found
Languages:
Java: 20.0.1 - C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.14 => 0.70.14
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found

it looks like there was a regression in a patch release of react-native 0.70 between 0.70.9 and 0.70.14, so i rolled back the recommended version to 0.70.8 for SDK 47. that should resolve the issue.
the problem appears to be that on react-native 0.70.14, specifying the hermes_enabled property in the Podfile is insufficient, and it also looks for a USE_HERMES environment variable, and if that is not defined, then it assumes you are using hermes.

hey @brentvatne! thanks for the investigation. Does that means that, if we retry building now, we no longer find issues? Or should we do an update to CLI or what exactly ?

I could built last night without issues.

Managed to build today without changing anything.

It is solved

@firasrg - correct, you can just run a new build. we reverted the recommend react-native version for sdk 47 from 0.70.14 to 0.70.8, so we no longer pull in the commit from react-native that caused this regression


Validation error about vulkan image layout

Describe the bug
Running sample gltf_viewer got vulkan validation error on version 1.12.9
To Reproduce
Steps to reproduce the behavior:

Compile and run gltf_viewer.

Expected behavior
Got validation error:
VULKAN ERROR: (UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout) Validation Error: [ UNASSIGNED-CoreValidation-Dra
wState-InvalidImageLayout ] Object 0: handle = 0x1b4d3eebb88, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x4dae
5635 | vkQueueSubmit(): pSubmits[0].pCommandBuffers[0] command buffer VkCommandBuffer 0x1b4d3eebb88[] expects VkImage 0x
54fef00000000a6[] (subresource: aspectMask 0x1 array layer 0, mip level 0) to be in layout VK_IMAGE_LAYOUT_SHADER_READ_O
NLY_OPTIMAL--instead, current layout is VK_IMAGE_LAYOUT_UNDEFINED.

Desktop (please complete the following information):

OS: Windows 10
GPU: NVIDIA RTX 3080
Backend: Vulkan (Using Vulkan SDK <IP_ADDRESS> for validation layer)
filament: 1.12.9

Additional Context:
This validation error won't happen before this merge.

I reproduced this today with MoltenVK + debug build of gltf_viewer.


update normalization to remove ◌̄

the database still needs to have all the ◌̄s removed, but it's a start

btw, this handles cases like kīā properly - the regex matches kī and ā separately, so ā becomes 'a and it works as expected

Thanks for checking out my dad’s React code. Looks like your PR passes my secret edge case tests contained within my fingers. Jokes aside, thanks for taking the time to contribute to tōadua!


Update careplan to create multiple extensions

Summary
He's back baby.
Updates Care plan extractor/template to create multiple extension entries rather than multiple CarePlan resources when provided >1 entry to the extractor.
New behavior
Multiple CarePlan data entries now appear as multiple http://mcodeinitiative.org/codex/us/icare/StructureDefinition/icare-care-plan-review extensions in the outputted CarePlan resource
Code changes

Update joinAndReformat function to produce a new type of data (each "review" maps to a new extension)

        {
          mrn: 'mrn-1',
          reviews: [
            {
              effectiveDate: '2020-04-15',
              hasChanged: 'true',
              reasonCode: '281647001',
            },
            ...
          ],
        }

Update tests/fixtures accordingly
Removed the usage of the created property for now as it is not required and we want to avoid inferring its value based on the multiple dates that could now be present for 1 CarePlan resource

Testing guidance
Run CLI and tests and inspect the output. The unit tests cover multiple extensions, but to see this in action, you can add a row to test/sample-client-data/treatment-plan-change-information.csv for one of the patients:
e.g.
mrn,reasonCode,changed,dateOfCarePlan,dateRecorded
123,281647001,true,2020-04-15,2020-04-15
123,281647001,true,2020-04-30,2020-04-30
456,405613005,true,2020-03-30,2020-04-15
789,266721009,true,2020-04-22,2020-06-17

For patient 123, this will now have 1 CarePlan resource with 2 extensions rather than 2 resources in the output bundle.

With the exception of a possibly redundant map after the reduce, I think this looks good.

With the exception of a possibly redundant map after the reduce, I think this looks good.

LGTM

LGTM


city-scrapers-core module not found

try uninstalling and reinstalling city-scrapers-core with pipenv install city-scrapers-core

also make sure this branch is synced with master
Scroll to the Git section here on syncing the fork: https://cityscrapers.org/docs/setup-help/
Use these commands (don't sync with the main City Bureau project):
git remote add upstream https://github.com/bonfirefan/city-scrapers-pitt.git
Then follow the steps as listed

Thanks Bonnie, that did the trick. I didn't have the city-scraper-core library installed and had to install it. I am just having trouble with pushing the work Nick did that I tested on my machine to my github repo. I will keep trying to see if i can get it. I added the upstream, but I am not sure about the venv commands from the link you sent me.


Use 4-2-stable for "Avoid leaking the first relation we call #first on"

Reported issue:    https://github.com/rails/rails/issues/21921
master commit:     https://github.com/rails/rails/commit/1b6fcae948b162efbd17f08ca563ff05742bf01b
4-2-stable commit: https://github.com/rails/rails/commit/599c31cf7d617955ea727358bf9878b365252f51

Let's use 4-2-stable until a 4-2 release candidate hits.  This bug prevents us from confidently measuring "live" objects since a reference was being leaked, causing objects to not be GC'd.

cc @matthewd

I'm good with this, but Hakiri broke.  I'm rerunning now.  Hopefully Hakiri can handle rails as a git ref, otherwise we'll have to come up with something else.


[BUG] page not found https://api-docs.activeloop.ai/htypes.html

🐛🐛 Bug Report
On the website when on this page: https://docs.activeloop.ai/getting-started/creating-datasets-manually
In the section
Specifying htype and dtype is not required, but it is highly recommended in order to optimize performance, especially for large datasets. Usedtypeto specify the numeric type of tensor data, and usehtypeto specify the underlying data structure. More information on htype can be found here.

When clicking on here you get redirected to https://api-docs.activeloop.ai/htypes.html which does not exist.

Actually found the page now:
should be renamed to  https://api-docs.activeloop.ai/htype.html

As an extra question should I post the issue here? (I can't seem to find the website code)

@Irvenae greetings, and thank you for bringing this up to our notice! We'll fix this issue shortly.

Fixed. Thanks for pointing this out. Any time there's a bug feel free to post here or on Slack!


[WINDOWS/FRAME] Added frame functionality (VariableNUmber) and window…

…s fixes.

@mhughesacn I think we have a dead process again. I am waiting for a long time for the license/cla process to complete

Hi Pierre: I did see this earlier but I was unable to help until this morning, and it looked like it had sorted itself out by then.  (I was locked out of my RDK account for several hours because of a config change that didn't behave properly.)  I'm sorry for the delay. - Martin


Warn about large ints in JSON

JSON parsers might not support large ints, we do use very large integers in the RPC in some cases.

the usual type would be ulong in c# terms.
Specifically there are 3 routes which use BigInt:

BlockchainState (network space)
GetNetworkSpace
DetAllPuzzleHashes

you can either make a custom converter function for that field or use a chia library which should have this functionality included.
https://www.nuget.org/packages/CHIA-RPC/ and the corresponding Chia-Client-Library (c#) for instance handles BigInt values.


Errors during the update Mollie plugin from 3.6.0 to 4.2.0

Hi
During the update Mollie plugin from 3.6.0 to 4.2.0 I've gotten a few errors:

Uncaught PHP Exception Twig\Error\LoaderError: "The "/home/USER/shopware/custom/plugins/MolliePayments/src/Resources/views/../app/storefront/dist" directory does not exist ("/home/USER/shopware/custom/plugins/MolliePayments/src/Resources/views/../app/storefront/dist")." at /home/USER/shopware/vendor/twig/twig/src/Loader/FilesystemLoader.php line 92 {"exception":"[object] (Twig\\Error\\LoaderError(code: 0): The \"/home/USER/shopware/custom/plugins/MolliePayments/src/Resources/views/../app/storefront/dist\" directory does not exist (\"/home/USER/shopware/custom/plugins/MolliePayments/src/Resources/views/../app/storefront/dist\"). at /home/USER/shopware/vendor/twig/twig/src/Loader/FilesystemLoader.php:92)"} []
Uncaught Error: Kiener\MolliePayments\Service\SettingsService::__construct(): Argument #2 ($repoSalesChannels) must be of type Kiener\MolliePayments\Repository\SalesChannel\SalesChannelRepositoryInterface, Shopware\Core\Framework\DataAbstractionLayer\EntityRepositoryForwardCompatibilityDecorator given, called in /home/USER/shopware/var/cache/prod_hb3c7d0e489e901531ea9110f97323125/ContainerXdgwtmJ/Shopware_Core_KernelProdContainer.php on line 34049 {"exception":"[object] (TypeError(code: 0): Kiener\MolliePayments\Service\SettingsService::__construct(): Argument #2 ($repoSalesChannels) must be of type Kiener\MolliePayments\Repository\SalesChannel\SalesChannelRepositoryInterface, Shopware\Core\Framework\DataAbstractionLayer\EntityRepositoryForwardCompatibilityDecorator given, called in /home/USER/shopware/var/cache/prod_hb3c7d0e489e901531ea9110f97323125/ContainerXdgwtmJ/Shopware_Core_KernelProdContainer.php on line 34049 at /home/USER/shopware/custom/plugins/MolliePayments/src/Service/SettingsService.php:55)"} []

Mollie still working but I want to be sure that all is okay from the dev side and that I don't need to do any additional stuff (for example the error might break smth and I need to reinstall the plugin)
Shopware <IP_ADDRESS>.
Front-end headless.

hi there
thank you for your message
phu...these are a few updates....mhm...
so let me focus on the errors what they mean

i think thats fine, but i have never seen the error
here is an explanation about that file: https://github.com/mollie/Shopware6/wiki/Dev-Artifacts
can you double check for me

i think thats only a cache thing, we have made our own interfaces, and it looks as if the cached services still have another type...so maybe clear caches and it should be gone

i hoep this helps you


Can the schema generation tool suppress case insensitive duplicates that are not accepted by bigquery?

Hi
I have been trying to export asset metadata to GCS. The idea is to export the asset metadata generated into bigquery and then visualize in Data Studio.
However whenever I use the cloud asset API (either using curl or 'gcloud asset export' command), the generated raw json data file contains two duplicate fields, 'IPProtocol' and 'ipProtocol'.
Due to this when I try to export this data into bigquery (either by bq mk or bq load command) it gives me follwing error.
$ bq mk inventory_dataset.2019_09_20_11_00_00 schema.json
BigQuery error in mk operation: Field resource.data.allowed.ipProtocol already exists in schema
Is this a bug or I am doing anything wrong?
I am using a bigquery-schema-generator tool for generating schema.(https://pypi.org/project/bigquery-schema-generator/)
Please help.

I have only limited call phone internet access right now. As you discovered, bigtable is caae-insensitive with regards to column names. Maybe you can try renaming the duplicate column name with a 'sed' script? Can't help any further for about 1-2 weeks.

My suggestion remains the same, use a pre-processor to resolve the conflicting name. In some cases, the two field names may represent the same thing, so should be collapsed together. In other cases, the two fields names represent 2 different things, so the should be separated by renaming one of the fields. The bigquery-schema-generator script cannot determine which of the different cases, so the user needs to figure this out with a separate pre-filter step. Closing.


Bump version and changelog after release

What was the end-user problem that led to this PR?
The problem was changelog and version bump not yet in master.
What is your fix for the problem, implemented in this PR?
My fix is to merge back changelog and version bump after the release from the stable branch.

@bundlerbot merge


Update Twilio Video Android to 7.0.6

This PR updated the Twilio Video Android binding to the latest version 7.0.6
https://www.twilio.com/docs/video/changelog-twilio-video-android-v7#706-february-11th-2022

Looking at the release notes, Twilio Video Android is not built with Java 11.
https://www.twilio.com/docs/video/changelog-twilio-video-android-v7#706-february-11th-2022
Now builds with Java 11 instead of java 8
And currently that's not supported in Xamarin Android, so I think this PR is stuck until this issue is solved in Xamarin Android.
https://github.com/xamarin/xamarin-android/issues/6142
https://github.com/xamarin/java.interop/issues/867
https://github.com/xamarin/java.interop/pull/936

@4brunu do you know if this is resolved? The first issue you linked is still open, but the other two are merged/closed.
With the old version we get a security alert in Google Play: "Security - Vulnerable WebRTC Versions "

I don't know.
Try to ping https://github.com/xamarin/xamarin-android/issues/6142 and expose your issue, maybe it will help to prioritise this issue.