Querying [3 - 128] failed with exception [IllegalDataValueError]

Hi,
I have a few microinverters which used to work with the 2mptt yaml file.
Since a few days they no longer work and provide the following error:
2023-08-13 17:10:37.318 DEBUG (SyncWorker_2) [pysolarmanv5.pysolarmanv5] Socket setup completed... <socket.socket fd=27, family=2, type=1, proto=6, laddr=('192.168.xxx.yyy', 60194), raddr=('192.168.yyy.zzz', 8899)> 2023-08-13 17:10:37.318 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.321 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [5] retry attempts left 2023-08-13 17:10:37.323 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.325 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [4] retry attempts left 2023-08-13 17:10:37.327 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.329 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [3] retry attempts left 2023-08-13 17:10:37.331 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.332 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [2] retry attempts left 2023-08-13 17:10:37.333 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.336 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [1] retry attempts left 2023-08-13 17:10:37.338 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.339 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [0] retry attempts left 2023-08-13 17:10:37.340 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying registers [3 - 128] failed, aborting
I really haven’t a clue where to start looking.
I updated to the latest ‘Main’. (I was back an x-number of versions of the ‘Main’. I don’t know which moment did work)
Edit: I ‘downgraded’ to 1.4.3.
I made a copy of the current deye_mppt2.yaml from Github and copied it to custom_parameters.yaml adjusted my configurations to use that file.
It works now for me, but the current Main does not.

same error here

same here

Same here

Did anyone try to use the main and just manually replace the deye_mppt2 with the old working one? Little bit annoying that one can only try to do sth with daylight …

I don’t have the ‘old’ mppt2 yaml file, but the current/live one appears to work for me. It still throws the errors, but ‘only’ a few times per day

I can't find deye_2mppt.yaml in v1.4.3
which yaml did you use?

The one from the main branch.
custom_components/solarman/inverter_definitions/deye_2mppt.yaml

Ok, I used that one, but got IllegalDataValueError with Deye SUN-M80G3-EU-Q0
There are so many values and configurations in deye_2mppt.yaml ...
Did someone fix that error for this microinverter?

I just used the 1.4.3 and the deye_4mptt with my 800G3 so this might work for the M80 as well?

the problem is, both files 2mppt and 4mppt have a ending value of 0x0080.
In the PDF of the inverter the say:
0x0001~ 0x007D
my guess is:
requests:

start: 0x0003
end:  0x007D
mb_functioncode: 0x03

may fix it. you can give it a try

need more debug later.
2023-09-04 09:05:13.870 DEBUG (SyncWorker_11) [custom_components.solarman.solarman] frame_len does not match payload_len.
this error will lead to
2023-09-04 09:05:13.870 WARNING (SyncWorker_11) [custom_components.solarman.solarman] Querying 3 - 112 - failed with exception :V5FrameError: V5 frame contains invalid start or end values
at least, its my guess.
btw, i have a DeyeSun800-G3-EU since a week, so i'm pretty new to this.
2023-09-04 09:05:13.561 WARNING (SyncWorker_11) [custom_components.solarman.solarman] Querying 3 - 112 - failed with exception :V5FrameError: V5 frame contains invalid start or end values 2023-09-04 09:05:13.562 INFO (SyncWorker_11) [custom_components.solarman.solarman] Disconnecting from solarman data logger <IP_ADDRESS>:8899 2023-09-04 09:05:13.859 WARNING (SyncWorker_11) [custom_components.solarman.solarman] Querying [3 - 112] failed, [1] retry attempts left 2023-09-04 09:05:13.861 INFO (SyncWorker_11) [custom_components.solarman.solarman] Connecting to solarman data logger <IP_ADDRESS>:8899 2023-09-04 09:05:13.866 DEBUG (SyncWorker_11) [custom_components.solarman.solarman] Socket setup completed... <socket.socket fd=25, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 58264), raddr=('<IP_ADDRESS>', 8899)> 2023-09-04 09:05:13.866 DEBUG (SyncWorker_11) [custom_components.solarman.solarman] SENT: a5 17 00 10 45 9d 00 d0 99 4f e9 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03 00 03 00 6e 34 26 7b 15 2023-09-04 09:05:13.870 DEBUG (SyncWorker_11) [custom_components.solarman.solarman] RECD: 41 54 2b 59 5a 43 4d 50 56 45 52 3d 4d 57 33 5f 31 36 55 5f 35 34 30 36 5f 32 2e 30 36 0d 0a 0d 0a 2023-09-04 09:05:13.870 DEBUG (SyncWorker_11) [custom_components.solarman.solarman] frame_len does not match payload_len. 2023-09-04 09:05:13.870 WARNING (SyncWorker_11) [custom_components.solarman.solarman] Querying 3 - 112 - failed with exception :V5FrameError: V5 frame contains invalid start or end values 2023-09-04 09:05:13.872 INFO (SyncWorker_11) [custom_components.solarman.solarman] Disconnecting from solarman data logger <IP_ADDRESS>:8899 2023-09-04 09:05:14.168 WARNING (SyncWorker_11) [custom_components.solarman.solarman] Querying [3 - 112] failed, [0] retry attempts left 2023-09-04 09:05:14.170 WARNING (SyncWorker_11) [custom_components.solarman.solarman] Querying registers [3 - 112] failed, aborting. 2023-09-04 09:05:14.173 DEBUG (SyncWorker_11) [custom_components.solarman.sensor] No value recorded for PV1 Voltage 2023-09-04 09:05:14.175 DEBUG (SyncWorker_5) [custom_components.solarman.sensor] No value recorded for PV2 Voltage 2023-09-04 09:05:14.178 DEBUG (SyncWorker_9) [custom_components.solarman.sensor] No value recorded for PV1 Current 2023-09-04 09:05:14.183 DEBUG (SyncWorker_0) [custom_components.solarman.sensor] No value recorded for PV2 Current

`requests:` `  - start: 0x0001` `    end: 0x007D` `    mb_functioncode: 0x03`
``
2023-09-06 08:04:20.833 DEBUG (SyncWorker_10) [custom_components.solarman.solarman] Starting to query for [1] ranges...
2023-09-06 08:04:20.833 DEBUG (SyncWorker_10) [custom_components.solarman.solarman] Querying [1 - 125]...
2023-09-06 08:04:20.833 DEBUG (SyncWorker_10) [custom_components.solarman.solarman] SENT: a5 17 00 10 45 07 00 d0 99 4f e9 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03 00 01 00 7d d4 2b 97 15
2023-09-06 08:04:27.212 DEBUG (SyncWorker_10) [custom_components.solarman.solarman] RECD: a5 0d 01 10 15 07 34 d0 99 4f e9 02 01 85 96 07 00 0c 11 00 00 e5 7f f0 64 01 03 fa 01 00 02 01 32 33 30 34 32 33 33 32 35 39 00 01 00 00 12 0c 07 00 01 02 01 17 12 18 00 00 1f 40 00 00 02 01 00 4b 00 00 00 3c 17 09 06 08 04 13 00 00 00 00 0a be 07 08 14 50 12 8e 00 00 00 00 00 00 13 9c 00 2c 00 00 00 00 00 00 00 00 00 64 00 00 00 00 00 01 00 00 00 00 00 01 00 00 00 00 00 01 ff d5 00 00 00 0a 00 02 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 01 27 00 00 00 00 00 00 00 00 00 00 00 90 00 00 00 90 00 00 09 4c 00 00 00 00 00 01 00 00 00 00 13 88 00 00 00 00 00 00 00 00 00 00 00 00 01 86 00 00 00 00 00 00 0c 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 be 00 02 01 4c 00 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4b 30 20 15
2023-09-06 08:04:27.213 DEBUG (SyncWorker_10) [custom_components.solarman.solarman] Querying [1 - 125] succeeded
2023-09-06 08:04:27.213 DEBUG (SyncWorker_10) [custom_components.solarman.solarman] All queries succeeded, exposing updated values.
With Deye Sun800 G3 EU and FW 2.06
My Serial starts with 39xxx
hf!

Hi,
Just an update.
1.5.0 has just been released.
When I use 1.5.0 (with the 2mppt yaml file) I get the errors mentioned above.
I downgraded to 1.4.3 and use the same 2mppt yaml file (copied in from 1.5.0) and that works fine for me. (it does give an error every now and then, but it does work)

TL;DR
Using DEYE 800 G3 fw 1.57 (MW3_16U_5406_1.57)
After upgrade to solarman 1.5.0 errors were thrown (IllegalDataValueError)
Fixed by downgrade to 1.4.3 incl. yaml configs
long
With both HA 2023-07-xy and HA 2023-08-xy the solarman integration was working fine in version 1.4.3
After upgrading to 1.5.0 incl. yaml configs the integration refused to connect to the inverter.
After replacing the bundled yaml configs with my previous one from a backup the integration was still not working.
It was not until I downgraded the integration to 1.4.3 (and using my backup config from 1.4.3 + HA restarts) it finally connected to the inverter as befroe.
No LAN / IP changes.

Response: [256, 513, 12851, 12340, 12851, 13106, 13625, 1, 0, 4620, 1792, 258, 279, 4632, 0, 8000, 0, 513, 75, 0, 60, 5897, 1546, 782, 0, 0, 2750, 1800, 5200, 4750, 0, 0, 0, 5020, 44, 0, 0, 0, 0, 100, 0, 0, 1, 0, 0, 1, 0, 0, 1, 65493, 0, 10, 2, 0, 0, 0, 0, 0, 4, 8, 0, 0, 303, 0, 4, 4, 0, 0, 148, 0, 148, 0, 2380, 0, 0, 24, 0, 0, 5000, 0, 0, 0, 0, 0, 0, 5800, 0, 0, 0, 5470, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 477, 61, 480, 59, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

now i'm restarting HA to get some results when it's false.

Great.
I used the values you provided for my Deye SUN-M80G3-EU-Q0
`requests:

start: 0x0001
end: 0x007D
mb_functioncode: 0x03`
I rebooted the raspberry ... and voila ... all values are there.
Thanks for diving into this issue.

With these changes, it also works for the Deye SUN-M60G3-EU-Q0

@stvogel @rosch100
u getting all the values you need, is something missing/wrong displayd?

u getting all the values you need, is something missing/wrong displayd?
All the values seem to make sense.

SUN-M80G3-EU-230 here. Works just fine now. Up to now there's only one error still but it look way better than before, even with 1.4.3.
Querying [1 - 125] failed with exception [Empty: ]
Querying [1 - 125] failed, [1] retry attempts left

Otherwise there's only #349 left but that's no big deal. Thanks so far!

here is my yaml file:
# First version : 27.08.2023
# Microinverter SUNX (DEYE/VESDAS ??? - X because i have no dang clue what shares those registers  :) )
# v0.1  Added all the cool registers from Deye_Modbus.-.-.V118.pdf
#
## Tested with:
### SUN-800-G3-EU     FW: 2.06
########## May work with:
### SUN-M80G3-EU-230  FW: ?.??
### SUN-M60G3-EU-Q0   FW: ?.??
 Number"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 7
        registers: [0x000E]
        icon: "mdi:map-marker"

      - name: "Rated Power"
        class: "energy"
        state_class: ""
        uom: "W"
        scale: 0.1
        rule: 1
        registers: [0x0010]
        icon: "mdi:solar-power"

        #Return Unbekannt...
      - name: "Communication Protocol Version"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 7
        registers: [0x0002]
        icon: "mdi:wrench"

      - name: "Start-up Self-checking Time "
        class: ""
        state_class: ""
        uom: "s"
        scale: 1
        rule: 9
        registers: [0x0015]
        icon: "mdi:solar-power"

      - name: "Device Time"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 8
        registers: [0x0016, 0x0017, 0x0018]
        icon: "mdi:clock-time-three-outline"

      - name: "Device Rated Power"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 6
        registers: [0x0008]
        icon: "mdi:map-marker"

      - name: "Device Chip-Typ"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 6
        registers: [0x0009]
        icon: "mdi:map-marker"

      - name: "Soft Start Enable"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 1
        registers: [0x002F]
        isstr: true
        lookup:
          - key: 0
            value: "Disabled"
          - key: 1
            value: "Enabled"
        icon: "mdi:toggle-switch"

      - name: "Power Factor Regulation"
        class: ""
        state_class: ""
        uom: ""
        scale: 0.1
        rule: 2
        registers: [0x0032]
        icon: "mdi:exclamation"

      - name: "Restore Factory Settings"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 1
        registers: [0x0036]
        isstr: true
        lookup:
          - key: 0
            value: "Disabled"
          - key: 1
            value: "Enabled"
        icon: "mdi:factory"

  - group: Alert
    items:
      - name: "Running Status"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 1
        registers: [0x003B]
        isstr: true
        lookup:
          - key: 0
            value: "Standby"
          - key: 1
            value: "Selbsttest"
          - key: 2
            value: "Normal"
          - key: 3
            value: "Alarm"
          - key: 4
            value: "Fault"
        icon: "mdi:home-lightning-bolt"

      - name: "Running Status Code"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 1
        registers: [0x003B]
        icon: "mdi:numeric"

      - name: "Warning Code"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 3
        registers: [0x0067, 0x0068, 0x0069, 0x006a]
        icon: "mdi:alert-octagon-outline"
        isstr: true
        lookup:
          - key: 0
            value: "None"
          - key: W01
            value: "W01 reserve"
          - key: 1
            value: "W01 reserve"
          - key: W02
            value: "W02 FAN_WARN"
          - key: 2
            value: "W02 FAN_WARN"
          - key: W03
            value: "W03 Grid phase wrong"
          - key: 3
            value: "W03 Grid phase wrong"
          - key: W04
            value: "W04 meter_Comm_Fail"
          - key: 4
            value: "W04 meter_Comm_Fail"

      - name: "Fault information"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 1
        registers: [0x0065, 0x0066]
        icon: "mdi:information-slab-circle-outline"
        isstr: true
        lookup:
          - key: 0
            value: "None"
          - key: F07
            value: "F07 - DC/DC_Softsart_Fault"

      - name: "Alert"
        class: ""
        state_class: ""
        uom: ""
        scale: 1
        rule: 6
        registers: [0x0075, 0x0076]
        icon: "mdi:message-alert-outline"
        isstr: true
        lookup:
          - key: 0
            value: "None"

you will find some hex values, i need to figure out what the values mean.
would be nice if you can give it a try and give me feedback

SUN-M80G3-EU-230 here. Works just fine now. Up to now there's only one error still but it look way better than before, even with 1.4.3.
Querying [1 - 125] failed with exception [Empty: ]
Querying [1 - 125] failed, [1] retry attempts left

Otherwise there's only #349 left but that's no big deal. Thanks so far!

yes, this is a pain...
i can post what the PDF says:
实时运行数据区  (Run the data area in real time)
059 (0x003B) 运行状态  (run state) R (read-only) [0,5] (data range) -
0x0000 待机 (Standby)
0x0001 自检 (Self-Test)
0x0002 正常 (Normal)
0x0003 告警 (Alarm)
0x0004 故障 (Fault)
for me, the value is static. its always 4.

you will find some hex values, i need to figure out what the values mean.
would be nice if you can give it a try and give me feedback

So far it seems to look good. Only one entity is missing now, which is "solarman_update_time"

you will find some hex values, i need to figure out what the values mean.
would be nice if you can give it a try and give me feedback

So far it seems to look good. Only one entity is missing now, which is "solarman_update_time". Perhaps a separate inverter definition is needed for our ones. It'll probably break other 2mppt's I guess.

okay, i will look it up in the PDF when i'm back home.

Hier auch das Problem mit dem deye sun 600 Firmware VersionMW3_16U_5406_2.27.
Verbindungsaufbau mit Version 1.50 trotz geänderter .yaml nicht möglich. Mit Version 1.43 keine Probleme.

Hier auch das Problem mit dem deye sun 600 Firmware VersionMW3_16U_5406_2.27.
Verbindungsaufbau mit Version 1.50 trotz geänderter .yaml nicht möglich. Mit Version 1.43 keine Probleme.

Did you try https://github.com/StephanJoubert/home_assistant_solarman/issues/367#issuecomment-1708839274?

@niclas911
Change the first lines of /config/custom_components/solarman/inverter_definitions/deye_2mppt.yaml:
# First version : 22.2.2023
# Microinverter SUN600G3 (DEYE/VESDAS)
# 2x MPPT, 2x inverter
# 1x Logger, 2x Module,

requests:
  - start: 0x0001
    end:  0x007D
    mb_functioncode: 0x03

Restart home-assistant. Works for me.

Hier auch das Problem mit dem deye sun 600 Firmware VersionMW3_16U_5406_2.27.
Verbindungsaufbau mit Version 1.50 trotz geänderter .yaml nicht möglich. Mit Version 1.43 keine Probleme.

Hast du #367 (Kommentar) ausprobiert ?

Ja, leider keinen Erfolg (Solarmann status_connection disconnected).

@niclas911 Ändern Sie die ersten Zeilen von /config/custom_components/solarman/inverter_definitions/deye_2mppt.yaml:
# First version : 22.2.2023
# Microinverter SUN600G3 (DEYE/VESDAS)
# 2x MPPT, 2x inverter
# 1x Logger, 2x Module,

requests:
  - start: 0x0001
    end:  0x007D
    mb_functioncode: 0x03

Starten Sie Home-Assistant neu. Funktioniert bei mir.

@niclas911 Ändern Sie die ersten Zeilen von /config/custom_components/solarman/inverter_definitions/deye_2mppt.yaml:
# First version : 22.2.2023
# Microinverter SUN600G3 (DEYE/VESDAS)
# 2x MPPT, 2x inverter
# 1x Logger, 2x Module,

requests:
  - start: 0x0001
    end:  0x007D
    mb_functioncode: 0x03

Starten Sie Home-Assistant neu. Funktioniert bei mir.

Leider ohne Erfolg. Status ist weiterhin disconnected.

So I tried it with my Deye Sun 800. It does work every now and then after the modification of the 2mptt like mentioned from @niclas911. But then it stoppea working again and pushes a “entity is non-numeric” despite the SOLARMAN Smart app showing devices still online … will report back how the behavior is tomorrow. Right now it’s quite unstable.

 Dieses externe Relais musste hier in Deutschland nachgerüstet werden (fehlender NA-Schutz).  Sehr merkwürdig.

 Dieses externe Relais musste hier in Deutschland nachgerüstet werden (fehlender NA-Schutz).  Sehr merkwürdig.
@wunderbaum wurden bei dir sofort nach dem Neustart Werte angezeigt bei den Entitäten? Habe es testhalber 2 Stunden laufen gelassen ohne Erfolg.

Könntest du einen Auszug aus der Log schicken, am besten mit Debug mode on.
Die FW MW3_16U_5406_2.27 liegt leider nicht auf dem Deye server, so das ich es testen könnte.

Yes, ja. 😃
Bei mir lief es nach der Umstellung gleich wieder. Kann aber nicht sagen welche Firmware gerade drauf ist, im dunklen ist das ja offline.
Man muss natürlich auch in der Konfiguration dann nochmal deye2mpt einstellen.

I'm glad I don't have that thing connected yet. My 80G3 logger unit is running MW3_16U_5406_1.57 and with the modified yank it works fine for about 24 hours now.

No I don’t think it’s related to the relays issue. Haven’t installed mine yet (just received it today) and it’s not working like the 1.4.3 did-

you guys use one or more Home-Assistant to read the data?
because we use 2 Home-Assistants and when i add the 2nd one, it will stop working, and the first Home-Assistant gets all the result. ( even requests from 2nd Home-Assistant... what makes no sens at all)

Only one here.

WR: SUN1600G3-EU-230 (4xMPPT)
Firmware VersionMW3_16U_5406_1.53
Es läuft endlich, danke der Yaml-Datei vom Post 367.
Mir fehlen leider noch die Eingänge von 3 und 4.
Hat da jemand noch eine Übersicht welche register dafür gibt?
Nur einen HA ist am start.

WR: SUN1600G3-EU-230 (4xMPPT) Firmware VersionMW3_16U_5406_1.53
Es läuft endlich, danke der Yaml-Datei vom Post 367. Mir fehlen leider noch die Eingänge von 3 und 4. Hat da jemand noch eine Übersicht welche register dafür gibt?
Nur einen HA ist am start.

meinst du mit 3 und 4 die von PV-3 und PV-4 ?
hier ist die PDF die ich nutze Deye_Modbus.-.-.V118.pdf

@oxynatOr ich hoffe das reicht ihnen.
2023-09-08 12:13:49.406 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Starting to query for [1] ranges...
2023-09-08 12:13:49.406 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125]...
2023-09-08 12:13:49.407 INFO (SyncWorker_9) [custom_components.solarman.solarman] Connecting to solarman data logger 192............
2023-09-08 12:13:49.419 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Socket setup completed... <socket.socket fd=63, family=2, type=1, proto=6, laddr=('192............', 33168), raddr=('192............', 8899)>
2023-09-08 12:13:49.419 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] SENT: a5 17 00 10 45 17 00 b1 56 8c f7 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03 00 01 00 7d d4 2b 90 15
2023-09-08 12:13:49.527 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] RECD: 41 54 2b 59 5a 43 4d 50 56 45 52 3d 4d 57 33 5f 31 36 55 5f 35 34 30 36 5f 32 2e 32 37 0d 0a 0d 0a
2023-09-08 12:13:49.527 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] frame_len does not match payload_len.
2023-09-08 12:13:49.527 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125] failed with exception [V5FrameError: V5 frame contains invalid start or end values]
2023-09-08 12:13:49.530 INFO (SyncWorker_9) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192............:8899
2023-09-08 12:13:49.626 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125] failed, [1] retry attempts left
2023-09-08 12:13:49.631 INFO (SyncWorker_9) [custom_components.solarman.solarman] Connecting to solarman data logger 192............:8899
2023-09-08 12:13:49.639 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Socket setup completed... <socket.socket fd=63, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 33170), raddr=('192............', 8899)>
2023-09-08 12:13:49.639 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] SENT: a5 17 00 10 45 82 00 b1 56 8c f7 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03 00 01 00 7d d4 2b fb 15
2023-09-08 12:13:49.743 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] RECD: 41 54 2b 59 5a 43 4d 50 56 45 52 3d 4d 57 33 5f 31 36 55 5f 35 34 30 36 5f 32 2e 32 37 0d 0a 0d 0a
2023-09-08 12:13:49.743 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] frame_len does not match payload_len.
2023-09-08 12:13:49.743 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125] failed with exception [V5FrameError: V5 frame contains invalid start or end values]
2023-09-08 12:13:49.744 INFO (SyncWorker_9) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192............:8899
2023-09-08 12:13:50.208 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125] failed, [0] retry attempts left
2023-09-08 12:13:50.212 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying registers [1 - 125] failed, aborting.
2023-09-08 12:13:50.216 DEBUG (SyncWorker_9) [custom_components.solarman.sensor] No value recorded for PV1 Voltage
2023-09-08 12:13:50.218 DEBUG (SyncWorker_8) [custom_components.solarman.sensor] No value recorded for PV2 Voltage
2023-09-08 12:13:50.221 DEBUG (SyncWorker_2) [custom_components.solarman.sensor] No value recorded for PV1 Current
2023-09-08 12:13:50.222 DEBUG (SyncWorker_4) [custom_components.solarman.sensor] No value recorded for PV2 Current
2023-09-08 12:13:50.224 DEBUG (SyncWorker_0) [custom_components.solarman.sensor] No value recorded for Daily Production
2023-09-08 12:13:50.226 DEBUG (SyncWorker_6) [custom_components.solarman.sensor] No value recorded for Total Production
2023-09-08 12:13:50.228 DEBUG (SyncWorker_8) [custom_components.solarman.sensor] No value recorded for Grid Voltage L-L(A)
2023-09-08 12:13:50.230 DEBUG (SyncWorker_1) [custom_components.solarman.sensor] No value recorded for Grid Voltage L-L(B))
2023-09-08 12:13:50.231 DEBUG (SyncWorker_4) [custom_components.solarman.sensor] No value recorded for Grid Voltage L-L(C)
2023-09-08 12:13:50.234 DEBUG (SyncWorker_5) [custom_components.solarman.sensor] No value recorded for Grid Current A
2023-09-08 12:13:50.236 DEBUG (SyncWorker_9) [custom_components.solarman.sensor] No value recorded for Grid Current B
2023-09-08 12:13:50.238 DEBUG (SyncWorker_7) [custom_components.solarman.sensor] No value recorded for Grid Current C
2023-09-08 12:13:50.239 DEBUG (SyncWorker_2) [custom_components.solarman.sensor] No value recorded for Grid Frequency
2023-09-08 12:13:50.241 DEBUG (SyncWorker_4) [custom_components.solarman.sensor] No value recorded for Running Status
2023-09-08 12:13:50.242 DEBUG (SyncWorker_0) [custom_components.solarman.sensor] No value recorded for Total Output AC Power
2023-09-08 12:13:50.244 DEBUG (SyncWorker_6) [custom_components.solarman.sensor] No value recorded for Input Active Power
2023-09-08 12:13:50.245 DEBUG (SyncWorker_8) [custom_components.solarman.sensor] No value recorded for Output Apparent Power
2023-09-08 12:13:50.247 DEBUG (SyncWorker_1) [custom_components.solarman.sensor] No value recorded for Output Active Power
2023-09-08 12:13:50.248 DEBUG (SyncWorker_3) [custom_components.solarman.sensor] No value recorded for Output Reactive Power
2023-09-08 12:13:50.249 DEBUG (SyncWorker_5) [custom_components.solarman.sensor] No value recorded for Inverter ID

@oxynatOr ich hoffe das reicht ihnen.
2023-09-08 12:13:49.406 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Starting to query for [1] ranges... 2023-09-08 12:13:49.406 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125]... 2023-09-08 12:13:49.407 INFO (SyncWorker_9) [custom_components.solarman.solarman] Connecting to solarman data logger 192............ 2023-09-08 12:13:49.419 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Socket setup completed... <socket.socket fd=63, family=2, type=1, proto=6, laddr=('192............', 33168), raddr=('192............', 8899)> 2023-09-08 12:13:49.419 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] SENT: a5 17 00 10 45 17 00 b1 56 8c f7 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03 00 01 00 7d d4 2b 90 15 2023-09-08 12:13:49.527 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] RECD: 41 54 2b 59 5a 43 4d 50 56 45 52 3d 4d 57 33 5f 31 36 55 5f 35 34 30 36 5f 32 2e 32 37 0d 0a 0d 0a 2023-09-08 12:13:49.527 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] frame_len does not match payload_len. 2023-09-08 12:13:49.527 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125] failed with exception [V5FrameError: V5 frame contains invalid start or end values] 2023-09-08 12:13:49.530 INFO (SyncWorker_9) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192............:8899 2023-09-08 12:13:49.626 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125] failed, [1] retry attempts left 2023-09-08 12:13:49.631 INFO (SyncWorker_9) [custom_components.solarman.solarman] Connecting to solarman data logger 192............:8899 2023-09-08 12:13:49.639 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Socket setup completed... <socket.socket fd=63, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 33170), raddr=('192............', 8899)> 2023-09-08 12:13:49.639 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] SENT: a5 17 00 10 45 82 00 b1 56 8c f7 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03 00 01 00 7d d4 2b fb 15 2023-09-08 12:13:49.743 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] RECD: 41 54 2b 59 5a 43 4d 50 56 45 52 3d 4d 57 33 5f 31 36 55 5f 35 34 30 36 5f 32 2e 32 37 0d 0a 0d 0a 2023-09-08 12:13:49.743 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] frame_len does not match payload_len. 2023-09-08 12:13:49.743 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125] failed with exception [V5FrameError: V5 frame contains invalid start or end values] 2023-09-08 12:13:49.744 INFO (SyncWorker_9) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192............:8899 2023-09-08 12:13:50.208 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying [1 - 125] failed, [0] retry attempts left 2023-09-08 12:13:50.212 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying registers [1 - 125] failed, aborting. 2023-09-08 12:13:50.216 DEBUG (SyncWorker_9) [custom_components.solarman.sensor] No value recorded for PV1 Voltage 2023-09-08 12:13:50.218 DEBUG (SyncWorker_8) [custom_components.solarman.sensor] No value recorded for PV2 Voltage 2023-09-08 12:13:50.221 DEBUG (SyncWorker_2) [custom_components.solarman.sensor] No value recorded for PV1 Current 2023-09-08 12:13:50.222 DEBUG (SyncWorker_4) [custom_components.solarman.sensor] No value recorded for PV2 Current 2023-09-08 12:13:50.224 DEBUG (SyncWorker_0) [custom_components.solarman.sensor] No value recorded for Daily Production 2023-09-08 12:13:50.226 DEBUG (SyncWorker_6) [custom_components.solarman.sensor] No value recorded for Total Production 2023-09-08 12:13:50.228 DEBUG (SyncWorker_8) [custom_components.solarman.sensor] No value recorded for Grid Voltage L-L(A) 2023-09-08 12:13:50.230 DEBUG (SyncWorker_1) [custom_components.solarman.sensor] No value recorded for Grid Voltage L-L(B)) 2023-09-08 12:13:50.231 DEBUG (SyncWorker_4) [custom_components.solarman.sensor] No value recorded for Grid Voltage L-L(C) 2023-09-08 12:13:50.234 DEBUG (SyncWorker_5) [custom_components.solarman.sensor] No value recorded for Grid Current A 2023-09-08 12:13:50.236 DEBUG (SyncWorker_9) [custom_components.solarman.sensor] No value recorded for Grid Current B 2023-09-08 12:13:50.238 DEBUG (SyncWorker_7) [custom_components.solarman.sensor] No value recorded for Grid Current C 2023-09-08 12:13:50.239 DEBUG (SyncWorker_2) [custom_components.solarman.sensor] No value recorded for Grid Frequency 2023-09-08 12:13:50.241 DEBUG (SyncWorker_4) [custom_components.solarman.sensor] No value recorded for Running Status 2023-09-08 12:13:50.242 DEBUG (SyncWorker_0) [custom_components.solarman.sensor] No value recorded for Total Output AC Power 2023-09-08 12:13:50.244 DEBUG (SyncWorker_6) [custom_components.solarman.sensor] No value recorded for Input Active Power 2023-09-08 12:13:50.245 DEBUG (SyncWorker_8) [custom_components.solarman.sensor] No value recorded for Output Apparent Power 2023-09-08 12:13:50.247 DEBUG (SyncWorker_1) [custom_components.solarman.sensor] No value recorded for Output Active Power 2023-09-08 12:13:50.248 DEBUG (SyncWorker_3) [custom_components.solarman.sensor] No value recorded for Output Reactive Power 2023-09-08 12:13:50.249 DEBUG (SyncWorker_5) [custom_components.solarman.sensor] No value recorded for Inverter ID
Getestet mit requests:

start: 0x0001
end:  0x007D
mb_functioncode: 0x03

in der deye_string.yaml

Naa nicht Ihnen :) ... Hier können wir du verwenden.
 Meine Vermutung ist, das du nur einen HomeAssistant laufen hast?
Der Einwand mit der FW, kann ich ggf später / morgen prüfen.
 Muss ich auf den Kollegen warten, der einen deye M80 mit diesem Relais bekommt.
  Dies ist mehr informativ für mich, da ich nicht wirklich weiß wieso das in 4 files geteilt wurde.. Hybrid, 2 und 4 kann ich mir noch erklären.

@oxynatOr ich benutze nur 1x Home Assistant System genau.
Die String hat damals von Anfang an funktioniert und tut es momentan in der 1.43 immer noch. Deshalb habe ich nicht gewechselt.

tbh its not a fix, its still stop working and complain about wrong framlength.
that the reason why i don't do i mergre request..  but u are welcome :)

@oxynatOr ich benutze nur 1x Home Assistant System genau.
Die String hat damals von Anfang an funktioniert und tut es momentan in der 1.43 immer noch. Deshalb habe ich nicht gewechselt.

Da es nicht deinem Problem helfen wird, kann ich verstehen wenn du keine lust auf Experimente hast.

Working for me again, why do you think it's not a fix?

because there is more then that.  you didn't read the debug message?!
sure, the registers are fixed.. but not the whole issue ppl reporting here.

Working for me again, why do you think it's not a fix?

because there is more then that. you didn't read the debug message?! sure, the registers are fixed.. but not the whole issue ppl reporting here.

Ah no not yet. Will have a look into it.
Everything's fine.
Well ok, "Running Status" is always "Fault"

Der Einwand mit der FW, kann ich ggf später / morgen prüfen.  Muss ich auf den Kollegen warten, der einen deye M80 mit diesem Relais bekommt.

Der Einwand mit der FW, kann ich ggf später / morgen prüfen.  Muss ich auf den Kollegen warten, der einen deye M80 mit diesem Relais bekommt.

 Version 1.5.1 has resolved the issue for me. This version contains the updated files that you guys had conjured up!
My sincere thanks to all that spend so much time and effort in resolving this!!


too large

Hi
Thanks a lot for providing your script.
Sorry, since it is too large it can not be loaded and opened.
Therefore, I would greatly appreciate if you could divide it into two parts.
As long as it is possible for you, could you please create a kernel for your work on Kaggle?
Thanks in advance.
Best regards,

Hi,
Sure, I will do these, perhaps tomorrow.
Thanks,
Keigo
On Mar 7, 2018 02:09, "shahlaebrahimi"<EMAIL_ADDRESS>wrote:

Hi
Thanks a lot for providing your script.
Sorry, since it is too large it can not be loaded and opened.
Therefore, I would greatly appreciate if you could divide it into two
parts.
As long as it is possible for you, could you please create a kernel for
your work on Kaggle?
Thanks in advance.
Best regards,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keigito/FinancialDistressPrediction/issues/1, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AI8ycm5RSh299BonSIIGStiJfDn0f4xcks5tb5XAgaJpZM4SgBQr
.

Hi
Thanks a lot.
Best regards,

Hi,
I deleted a large png file (since the graph didn't provide too much insights), rather than splitting the file in half. Will this change work? Please let me know if I should still split the code.
Thanks,
Keigo

Hi,
I am so grateful for your informative code. Also, for reducing its' size.
Could you please provide the confusion matrix for train and test set after the predictions are converted into zero and one?
Sorry, since this data set is skewed, will RANSACRegressor be useful?
Thanks a lot.
Best regards,

Hi,
Thanks for your comment. Yes, a confusion matrix would have been a good addition! I'll do that and push it in a few days when I have some time. I'll also look into RANSAC regressor, too.
I really appreciate your comments, as I'm very new to the machine learning field (and am in a transition into it), so I find your comments very helpful.
Also, I assume you are the person who contributed the data? If so, I'd like to thank you for providing the data!
Cheers,


feat: enable hcl multi-project autodetect

Enables hcl multi-project autodetection. This allows users to run infracost breakdown at the repo level and get an automatic project output, no config file required. e.g:
With a project structure as such:
foo/
   dev/
   prod/

running infracost breakdown --path foo/ would return something similar to:
Project:  foo/dev

 Name                                                   Monthly Qty  Unit   Monthly Cost

 aws_instance.web_app
 ├─ Instance usage (Linux/UNIX, on-demand, m5.4xlarge)          730  hours       $560.64
 ├─ root_block_device
 │  └─ Storage (general purpose SSD, gp2)                        50  GB            $5.00
 └─ ebs_block_device[0]
    ├─ Storage (provisioned IOPS SSD, io1)                    1,000  GB          $125.00
    └─ Provisioned IOPS                                         800  IOPS         $52.00

 Project total                                                                   $742.64

──────────────────────────────────
Project: foo/prod

 Name                                                   Monthly Qty  Unit   Monthly Cost

 aws_instance.web_app
 ├─ Instance usage (Linux/UNIX, on-demand, m5.8xlarge)          730  hours     $1,121.28
 ├─ root_block_device
 │  └─ Storage (general purpose SSD, gp2)                        50  GB            $5.00
 └─ ebs_block_device[0]
    ├─ Storage (provisioned IOPS SSD, io1)                    1,000  GB          $125.00
    └─ Provisioned IOPS                                         800  IOPS         $52.00

 Project total                                                                 $1,303.28

 OVERALL TOTAL                                                                 $2,045.92

Why

Simplifies running infracost in a multi-project setting. This means it's super easy for users to migrate from CLI to CI.
This autodetection functionality is useful for editor extensions (vscode, e.t.c) that normally run in the context of a repo, not a specific project.

This PR also adds file metadata to the infracost JSON output. e.g:
"resources": [
  {
    "name": "aws_instance.web_app",
    "metadata": {
      "infracost_filename": "examples/terraform/main.tf"
    },
    "hourlyCost": "1.017315068493150679",
    "monthlyCost": "742.64",
    "costComponents": [
        ...
    ],
  }
]

This helps editor extensions locate the resources that are in the current file the user is editing.

@alikhajeh1 / @aliscott - I've added this as a PR to the v0.10 branch, but I'm not sure if we want to block the v0.10 release on this. I think it might be better to just get v0.10 out. However, this might be a nice bonus feature that could make upgrading to v0.10 more appealing.

@hugorut heads up, I had to rebase this again.

Thanks @aliscott

@alikhajeh1 I guess 3 is unrelated to this PR correct? We'd want that in v0.10 if we include this or not?

@aliscott tru dat, we'd want that in v0.10

@alikhajeh1 I've fixed 3 in my branch (https://github.com/infracost/infracost/pull/1630/commits/9753daa59c786195d265b0770f333a885f03184e)

Ok I've fixed up the changes requested by @aliscott and changed project detection to a depth of 5.
However, this highlighted an issue: The HCL provider detects nested Terraform projects by finding folders that have valid Terraform configuration files (.tf/.tf.json), but also makes sure that these files contain a provider block. I did this as I wanted a way to ignore shared modules that might be used across a mono repo. This is exactly the setup we have for the Infracost infra repo (with prod and dev folders and a shared modules folder).
Terraform docs state that provider blocks should only be added at the root module level so I thought this method would be relatively safe for detecting valid projects.
Yet, I ran breakdown with the depth change on the infra project for Infracost and it now thinks that infra/modules/base is a project. That's because it has a provider "kubernetes" block. If we're to believe Terraform docs this is actually invalid and this should be configured at the root level, but Terraform doesn't seem to error with this configuration.
So my question is should we proceed with this method of "asserting" Terraform projects (1. valid tf files, 2. valid provider blocks) or is there a better way? Thoughts @aliscott / @alikhajeh1
p.s the above only applied to nested projects, if a user points Infracost to a top level directory that contains Terraform files we don't validate the provider block. This is done so that users can see cost snapshots of things like third party modules

So my question is should we proceed with this method of "asserting" Terraform projects (1. valid tf files, 2. valid provider blocks) or is there a better way? Thoughts @aliscott / @alikhajeh1

Other options off the top of my head - still thinking of others...

Exclude any directory called modules. This seems to be a fairly well-used path. We could even have an --exclude-paths flag that defaults to **/modules.

Check the .terraform/modules/modules.json file of each directory and exclude any local paths that appear in there. This will only work if the project has been init'd.

@aliscot Yeah I was initially thinking of option 2 with something like the --exclude-paths flag. I believe anything option that involves initing should be avoided, this could have a real speed penalty.
I think option 5 could work and should be pretty easy. i.e right now we just do a shallow parse of the files to return the provider blocks, which could modify this to also return the module blocks and fetch the src attribute. This would build an exclusion list on which we filter the projects.
@tim775 yup nice suggestion, we actually use this library in the module downloading functionality. However, it might be easier and quicker to just do the shallow parse as it'll probably be quicker because we ignore blocks we don't need. Plus we're already doing it this way, so it's less code to change.

I believe anything option that involves initing should be avoided, this could have a real speed penalty.

Yes if we assume it has been init'd this will only work locally, and if we try initing ourselves then we'll require the terraform binary. So either way these options aren't suitable.

@aliscott I've implemented option 5. This branch is technically good to go, but I'll hand it off to you to make any tweaks and additions that you see fit. I don't want to slow down the release because I'm on holiday. I'm assigning this to you now.


COE Updates

Hi there, this is not a bug but an inquiry. I am just wondering when we update solutions in our COE, if the entities are affected in anyway. We are customizing the developer compliance center for one of our clients to implement admin and governance capabilities in their organization, and are required to add new fields to the form. We are trying to decide if we should create a new entity or modify the existing one. Please let us know. Thanks!

This question is about the behavior of the underlying platform. You will need to explore the complexities of upgrade, here is a good starter: How managed solutions merge.
My expectation is that your changes would be fine and not be interrupted by upgrade, but my advice would be that you test this in a sample environment to be sure.
Sorry that I cannot answer with more certainty.


Question: Intentional or a bug?

When I change the font from system to the apps default font I have to reauthenicate with my fingerprint. (Or password)

this happens because change app theme requires activity recreation, when activity create you need auth with pass if enabled.
maybe i will fix it later because i'm busy right so i can only fix critical bugs

fixed in new version


incorrect implementation of Diamond

Diamond contract is a proxy of lookup table of addresses and function selectors. Some of the functions are specified in EIP, but they can be removed. However, current implementation inherit the DiamondReadable and DiamondWriteable, which cause function shadowing and make them unable to be removed. Otherwise, calling these functions doesn't use delegate call (due to function shadowing).

From eip2535 substack, there is a term called Finished Diamond.

Finished Diamond: A finished diamond was an upgradeable diamond and had a number of upgrades. Then its diamondCut function and/or other upgrade functions were removed and upgrades are no longer possible. It is no longer possible to add/replace/remove functions. It has become an immutable diamond.

The SolidStateDiamond contract is the "recommended" configuration for most users.  In my opinion, the need for a "finished diamond" is very rare, so SolidStateDiamond does not support that feature.  However, it is still a valid diamond implementation - all functions inherited into the proxy are properly registered as "immutable functions".
A user who wishes to implement a "finished diamond" can do so manually by using DiamondBase as the proxy, and DiamondWritable as a facet.
I will consider adding another full implementation that can be a "finished diamond", but at the moment I still don't think it's necessary.


Check that personal code (private key) is within secp256k1 range

Users are able to save their progress with a personal code (aka a private key) that is generated in components/chapters/SaveProgressButton.tsx

This key is a random 64 digit hex number (aka 256 bits).
As a user, I would like to use this code to generate addresses of my own in chapter 3. In order for this to work, the secret key must be smaller than 1.1578 * 10^77 (a number that is slightly less than 2^256).
I'm not sure what the chances are of a random 256 bit number being larger than the acceptable range. That will probably determine the priority of this ticket. However, if we don't add a check, it will result in some kind of instability in the chapter 3 challenges, because those challenges have the user generate a public key (aka a point on the secp256k1 elliptic curve) from this secret key.
Possibly a good first issue?

Fixed with #37.


Remove deprecations for 0.18

What does this PR do?
Remove deprecations for 0.18. Mostly models/datasets folders

Hello 👋 Would it be possible to know the motivations behind removing support for well known datasets (in various formats) and some models, including the integration with timm?

Thanks @mvpatel2000! As you said the creating model with timm requires calling two function so no need to provide any abstraction around this. Removing some elements your the API makes a lot of sense. I think some of it would have made good documentation materials to present your support and integration into the larger ecosystem.


VitalRouter-mruby requires UniTask to be installed even if UniTask is already installed

probably, definition of “VITALROUTER_UNITASK_INTEGRATION” is missing in the versionDefines.

It seems that the code in VitalRouter.MRuby was partially dependent on UniTask. A learned version has been released. (1.5.0) Thanks for the report.


Problem parsing URL

I am not sure if this is an error parsing URLs or if Firefox and Chrome are too lenient in their interpretation of the standards, but when the parser encounters the following URL from taobao.com
http://a.tbcdn.cn/p/fp/2010c/??fp-header-min.css,fp-base-min.css,fp-channel-min.css,fp-product-min.css,fp-mall-min.css,fp-category-min.css,fp-sub-min.css,fp-gdp4p-min.css,fp-css3-min.css,fp-misc-min.css?t=20101022.css
Firefox and Chrome both interpret the query string to begin with a '?' (i.e., "?fp-header..."), where as the parser seems to skip over both '?' chars and returns the rest of the query string starting with "fp-header..."
I can create a patch if you want, but I worked around it in one of my callbacks instead.
--Sam

Fixed in 6756842.


Add tvOS Platform

Add tvOS Platform

tvOS support was added in version 2.0.1. Thank you for the PR!

No thank you!


Use overlay repo to build MSVC

~This is WIP - opening with a trial version to test the fix.~
~(loosely) related to https://github.com/avsm/ocaml-dockerfile/pull/79~
The Visual Studio images haven't been building for months for 4.10, 4.12 and 4.13 owing to the need for either https://github.com/ocaml/ocaml/pull/10797 or https://github.com/alainfrisch/flexdll/pull/96. This PR opts for the latter by upgrading the embedded flexdll in opam-repository-mingw to 0.40 (which includes that PR).
I've done this by creating a ocurrent/opam-repository-mingw which houses the patch in the patches branch and has a tiny opam repo in the overlay branch containing just the patched opam files.
I don't expect those compiler packages to change in upstream opam-repository-mingw before ocaml-base-compiler gains Windows support in ocaml/opam-repository later this year, but the patches can of course be updated as necessary.

This is presently pushed live and appears to be working! Cygwin setup has already been patched, but the change is actually worth forcing anyway (at least while we still use cygsympathy).

This now depends on avsm/ocaml-dockerfile#80.

@talex5 / @tmcgilchrist - any objections to the mechanism used here for doing (i.e. having an extra repo which gets selectively added?). It's kernel update day on Wednesday morning, so it'd be nice (though not compulsory) to have this merged before then.


pyramid_multiauth name collision

https://github.com/mozilla-services/pyramid_multiauth

This is solved now.


How does one change their MTGO name on PD website?

@People30044 if you ping a mod on the discord or put the details in this ticket we can unlink your Discord account or alias two different mtgo names. https://pennydreadfulmagic.com/discord/

@bakert Thanks for responding,is it possible we could alias two different mtgo names?  Or  change the current name People30034 to people30044.  thank you for the help!

I can do that but I can only do it once people30044 has at least one league
or tournament match. Ping me here when you have one in the books!
On Tue, Oct 6, 2020 at 11:03 AM People30044<EMAIL_ADDRESS>wrote:

@bakert https://github.com/bakert Thanks for responding,is it possible
we could alias two different mtgo names? Or change the current name
People30034 to people30044. thank you for the help!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PennyDreadfulMTG/Penny-Dreadful-Tools/issues/7919#issuecomment-704450366,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAMBPJ62T55ISTA6TH2GTSJNLVRANCNFSM4SE4ZRHQ
.

I cant do that. My mtgo username is people30044 but my PD username is people30034. so the bot doesnt regonise me when i go into a match

I see. I have unlinked your discord account from people30034. Feel free to sign up to the league as people30044 and link your discord.

Fixed it thanks!


Ambient occlusion request

this is more like a request - i would be interested about the speed and handling of AO for this demo.

Good idea. There's some per-vertex ambient occlusion code, and support to pass per-voxel light-information as input data in stb_voxel_renderer but I haven't looked into this yet.

btw. have you seen this one: https://github.com/nothings/obbg

Looks like I starred it at some time, but forgot about it :)

see pr #10

and without:


fix(Flow): typing

:tada: This PR is included in version 4.217.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


disallow ad-hock transactions in pool queries

fixes https://github.com/edgedb/edgedb-go/issues/97

closing in favor of https://github.com/edgedb/edgedb-go/pull/99


CryptoChill

Hi,
I've added our project CryptoChill to the ecosystem.json file and added a PNG of our logo to the public/images/partners folder.
Thanks,
Matthew

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

Review Error for wbnns @ 2024-12-05 17:04:08 UTC
User failed mfa authentication, see go/mfa-help

Closing due to inactivity


Jenkins slave swarm jar not downloading

I consistently run into the situation where puppet seems to run to completion but none of the slaves come up.
It turned out that swarm-client-1.22-jar-with-dependencies.jar in the jenkins-slave home dir was always 0 bytes. puppet.log also showed problems fetching the file:
master: Error: wget -O /home/jenkins-slave/swarm-client-1.22-jar-with-dependencies.jar http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/plugins/swarm-client/1.22//swarm-client-1.22-jar-with-dependencies.jar returned 4 instead of one of [0]

Downloading it manually (but from here, not the original URL) made things work again.
This looks like it's related to jenkinsci/puppet-jenkins#507, but that is closed, marked (sort-of) resolved (as the upstream issue was resolved). It does not seem to work for me though.

Just found jenkinsci/puppet-jenkins@cb458643fe9adebd3d8e7c8a54865c48db64fbf9:

Use a up-to-date swarm client URL

which is included in 1.7.0. The Puppetfile for master pins rtyler/jenkins to 1.6.1, which doesn't have it.
Adding
  source => 'http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/swarm-client/1.22',

to the jenkins_slave class stanza seems to work around this, but that only works for version 1.22 of the plugin. I'm uncertain where puppet gets the version it should download.
jenkinsci/puppet-jenkins/manifests/slave.pp says:

The version of the swarm client code. Must match the pluging version on the master.  Typically it's the latest available.

I hit this same issue when trying to set up a buildfarm on Ubuntu Trusty. I didn't find a solution and instead forged ahead refactoring the puppet scripts and targeting Ubuntu Xenial (that work is in #146).
As far as I know, the swarm plugin version was determined by the upstream jenkins component module rather than anything in this repository. I created a script to sync/pin all plugin versions configured to the versions on the current buildfarm but the swarm plugin is ignored by that script as it is intended to be managed by the jenkins component module.
I tried to deploy a working trusty buildfarm from these configs for reference before starting the refresh to xenial but while I was able to get something running, it was extremely brittle and required a lot of manual work updating plugins, manually downloading the swarm jar, and hand-tuning configs before it was serviceable.
The xenialize branch isn't quite in a recommendable state yet but if you want to check it out the corresponding changes to the public configuration are in this fork's xenialize branch.
If you wanted to avoid making so drastic a change, I'm pretty sure you can bump the jenkins puppet module version and see if that unblocks you. I can't recall  there being any incompatible changes I had to deal with updating it for xenial.

@nuclearsandwich wrote:

If you wanted to avoid making so drastic a change, I'm pretty sure you can bump the jenkins puppet module version and see if that unblocks you. I can't recall there being any incompatible changes I had to deal with updating it for xenial.

well, there's #143. I didn't want to start experimenting with that yet.
With the set of changes I have I can now quite easily deploy a farm, so as much as I've been intrigued/tempted by your Xenial-porting work I think I'll first get this working :).

so as much as I've been intrigued/tempted by your Xenial-porting work I think I'll first get this working

As I mentioned, we don't yet have a complete farm up and running on Xenial. That config is being used on a test buildfarm but it's building new packages not anything from the existing ROS ecosystem yet. Before it merges I'm hoping to also add additional documentation around setting up a buildfarm as I've been logging the process of spinning mine up for the first time.

As I mentioned, we don't yet have a complete farm up and running on Xenial.

I might've not been entirely clear, but I'm sticking to Trusty for now :). I understand that your xenial work is experimental.

But am I to understand that this issue will not be addressed anymore, now that work is underway to get a Xenial farm working?

But am I to understand that this issue will not be addressed anymore, now that work is underway to get a Xenial farm working?

In short, I don't have plans to implement and test an official solution but if you're able to find an acceptable workaround, I'd create the new trusty legacy branch early and accept pull requests to it.
I don't believe anyone besides myself at OSRF has used this code to set up a buildfarm since the current build.ros.org was originally provisioned some years ago. If everything worked as-is but this slave jar url I'd be in a better position to offer or accept a concrete solution.
I don't see myself updating the current master branch until we move it to xenial since getting it operational under trusty wasn't a slam dunk and a high motivator for moving to xenial is access to up-to-date Java and Docker both of which are impacting the current buildfarm.
It looks like you have two possible workarounds.

Update the Jenkins puppet module to 1.7.0, which still supports trusty and which I believe still works with the current puppet code.

Specify an explicit source url to the swarm plugin. You could likely use version 2.0 or 3.4 and be fine as I've seen both on the upstream buildfarm in recent weeks.

I think my recommendation would be updating the puppet module.

@nuclearsandwich There are several other instances of the buildfarm being run. I can give you more details in person.

@nuclearsandwich There are several other instances of the buildfarm being run. I can give you more details in person.

Sounds good! I'm definitely not trying to make official policy, just stating what I'm comfortable and capable of maintaining.

For now I've setlled on:

using version 1.7.0 of the puppet jenkins module
overriding the version key to download the 1.22 version of the swarm plugin

This keeps the versions used the same without running into the issue that the jenkins module cannot download the jar.
@nuclearsandwich: you mention that versions 2.0 and 3.4 are also used on (one of) the buildfarm(s) you guys run: did you run into #143 there? How was that fixed?

you mention that versions 2.0 and 3.4 are also used on (one of) the buildfarm(s) you guys run

build.ros.org is currently using 3.4. The executor nodes on that farm use AWS's auto scaling and I think just use an image based on a "golden" puppet-configured machine rather than re-running the puppet each time one is spun up. @tfoote and I had an offline conversation about it and I can't recall if we're currently using an AWS Jenkins plugin but wanted more from it, or if we're currently using AWS's built in scaling based on CPU load and haven't incorporated the plugin because it doesn't add the things we want.

did you run into #143 there? How was that fixed?

I don't have an explicit answer as the current buildfarm predates me. What follows is conjecture:
Based on the node names on http://build.ros.org/ it looks like the name of the auto-scaling swarm clients is left to the default aws hostname. If I had to guess I'd say that the plugins have been updated on build.ros.org out of sync with the puppet code there but I don't have console access to those machines at the moment to verify.
I noticed the unique suffix on node names when testing the new xenial code in clusters. I'll likely end up adding the -disableClientsUniqueId flag to the default agent behavior and using Puppet facts to generate a unique-to-host node name but I haven't done so yet or fully validated that approach.

The executor nodes on that farm use AWS's auto scaling and I think just use an image based on a "golden" puppet-configured machine rather than re-running the puppet each time one is spun up. @tfoote and I had an offline conversation about it and I can't recall if we're currently using an AWS Jenkins plugin but wanted more from it, or if we're currently using AWS's built in scaling based on CPU load and haven't incorporated the plugin because it doesn't add the things we want.

We have a snapshot AMI that aws autoscales. And it starts the jenkins swarm agent via a puppet update. So changes to puppet will propogate.

For the tags, I'd highly recommend not relying on the hostnames, but instead use labels related to the capabilities of the machines. For example on_master or on_jenkins could be labels for the executors running on the same machine. This will move us away from requiring multi hosts.


GoalShapes for Taxi Factory Need

Since it is possible to define Shacl Constraints/Shapes for our needs now. it would be good if we could alter our taxibot-factoryneed (as created by @fkleedorfer ttl file) in a way that it will contain the following mandatory shapes:
departureadress (geocoordinates lat lng) min:1 max:1
destinationadress min:0 max:1
(please refer to @heikofriedrich for the right nameconvention of the triples)
we should not worry about any other criteria for now. what would be good is to have the correct shapes defined in the template and a way of "copying" or transferring those shapes to the concrete offer itself (possibly within the needmodelbuilder, just like it is already possible to retrieve the title or description from a need)

is done


x/build: add LUCI linux-mipsle builder

There currently isn't a LUCI builder that tests the linux/mipsle port (other than the misc-compile builder, which tests only that the port compiles). This is the tracking issue for it.
The next steps that a builder owner will need to follow to make progress here are documented https://go.dev/wiki/DashboardBuilders#luci-builders.
CC @golang/mips.

Thank you for offering to provide the builders, and apologies for the delay in getting back to these questions.

Therefore it's hard to get any decent powerful hardware for CI stuff. Should those runners be bare metal, or are e.g. QEMU emulated runners fine?

The ideal hardware for a builder to use is something that most closely resembles the target port being tested, such that it's findings are most likely to be true positives with minimal false negatives. QEMU emulation adds an additional layer of indirection, and may introduce some false positives. But if there isn't too much noise, it's entirely possible that the benefit from the speed up you're able to get that way outweighs the downsides of adding that layer. Ultimately, it's up to the you as the builder owner to decide what builder setup to aim for, based on how well it'll serve and how well you can keep it running.
Note that the builder requirements written down at https://go.dev/wiki/DashboardBuilders#builder-requirements list 512 MB as the minimum, so with only 128 or 256 MB of memory, you'd be below the supported range and may run into trouble.

Will they build the whole Go tree?
Are the test suites cross compiled to MIPS on other runners and only the test suites run?
Are there some docs, where wou could manually run the tasks to get a feeling of how long the build times would be?

As I answer these questions below, please keep in mind that what I'm describing is the default builder setup for ports that have high performance hardware available. It is possible to reduce the scope of testing for certain ports/builders if there's not sufficient builder resources available, but that reduces coverage of testing. See some related discussion in https://github.com/golang/go/issues/67105#issuecomment-2266181870.
By default, builders build and test the main Go repository and all golang.org/x repositories on the main branch ("master") and all supported release branches (e.g., "release-branch.go1.22" and "release-branch.go1.23").
In the default case, builders testing a given port are responsible both for building and testing. This increases coverage (proof that the target OS/arch can be used to build successfully) and makes it easier to have cgo enabled. In special cases, like the Plan 9 builders that can't run the LUCI swarming client due to absence of the python3 dependency, it's possible to arrange for a Linux host to do the building and perform test execution remotely. See https://github.com/golang/go/issues/62025#issuecomment-2116456142 for details.
For the main Go repository, the builders run the equivalent of all.bash. For golang.org/x repositories, they run the equivalent of go test -short ./... for all modules. You can run those commands locally to get a good idea of the performance to expect.
I hope that helps. When you're ready to proceed, see step 2 of https://go.dev/wiki/DashboardBuilders#how-to-set-up-a-builder (step 1 is already done; it's this issue).


Installation script overwrites the global config file

Same as #40 from Salomon for Linux.

In case the config file already exists inside the target directory it remains untouched now.

In case the config file already exists inside the target directory it remains untouched now.

Fixed in version 1.18.2.

Fixed in version 1.18.2.


centos-7.2 minion2 failure...

I tried using the centos-7.2 flavor for minion 2 in the demo, and it ended up like this:
==> minion2: Successfully added box 'bento/centos-7.2' (v2.2.9) for 'virtualbox'!
==> minion2: Importing base box 'bento/centos-7.2'...
==> minion2: Matching MAC address for NAT networking...
==> minion2: Checking if box 'bento/centos-7.2' is up to date...
==> minion2: Setting the name of the VM: salt-vagrant-demo_minion2_1471580390978_72215
==> minion2: Fixed port collision for 22 => 2222. Now on port 2201.
==> minion2: Clearing any previously set network interfaces...
==> minion2: Preparing network interfaces based on configuration...
minion2: Adapter 1: nat
minion2: Adapter 2: hostonly
==> minion2: Forwarding ports...
minion2: 22 (guest) => 2201 (host) (adapter 1)
==> minion2: Running 'pre-boot' VM customizations...
==> minion2: Booting VM...
==> minion2: Waiting for machine to boot. This may take a few minutes...
minion2: SSH address: <IP_ADDRESS>:2201
minion2: SSH username: vagrant
minion2: SSH auth method: private key
minion2: Warning: Remote connection disconnect. Retrying...
minion2:
minion2: Vagrant insecure key detected. Vagrant will automatically replace
minion2: this with a newly generated keypair for better security.
minion2:
minion2: Inserting generated public key within guest...
minion2: Removing insecure key from the guest if it's present...
minion2: Key inserted! Disconnecting and reconnecting using new SSH key...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
minion2: Warning: Authentication failure. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

I suspect you may be using vagrant 1.8.5 which has a bug in it related to generating the new ssh key for RedHat distros. See: https://github.com/mitchellh/vagrant/issues/7610
It only affects RedHat distros because of the default umask that is set for the root account. The URL also has the fix in it. The official fix will be in the next release of the vagrant code.

Interesting.. I'll try both.  Thanks for the info!

Just keep in mind that the firewall stuff is only applicable to the master. If the master is a ubuntu box there is no need to tweak the firewall.

In my case I was only using CentOS as one of the minions, so I don't believe that part is relevant to my setup.  The details in the link you provided did get my environment up and running with a CentOS minion, however.  Thanks!


Fusetools2 82 properties components with parameters completion

requires https://github.com/camel-tooling/camel-language-server/pull/337

Pull Request informations
Rebase & Merge default requirements

Green build for master branch
Wait 24 hours after PR creation
Green job for PR
Approved PR

PR labels default process

READY_FOR_REVIEW  →  REVIEW_DONE  →  READY_FOR_MERGE

Tests

[ ] Are there Unit tests?
[ ] Are there Integration tests?
[ ] Do we need a new UI test?

PR workflow progress

[ ] Tagged with relevant PR labels
[ ] Green job for PR
[ ] PR was created more than 24 hours ago or All committers approved it
[ ] Green master branch build

CamelKafka is using properties files to also define Camel URI.
So if we are inside a Camel URI in properties file, we need to delegate to the CamelEndpointCompletionProcessor. The only code that was capable to detect this condition was inside CamelKafkaConnectParserDSL
But you're right, i think I can extract a part of it.

ok so reworked a bit to have finer grained method to detect if we need to use the completion for Camel URI or the one for Properties.
This part might be better placed in a "CamelPropertyFileValue" and delegate at this place only but as currently the model doesn't take care of Property values, I tend to think that it is simpler to let it here for this iteration.
For "move the Uri parser to a more generic utility class", re-reading the code, it seems legit to delegate the detection of a Camel Kafka specific property to the CamelKafkaConnectDSLParser.
With new version of the PR, the extracted class would contain only:
public boolean isInsideACamelUri(String line, int characterPosition) {
		return line.startsWith(CAMEL_SOURCE_URL) && CAMEL_SOURCE_URL.length() < characterPosition
				|| line.startsWith(CAMEL_SINK_URL) && CAMEL_SINK_URL.length() < characterPosition;
	}

and some cross-references to the constants between the CamelKafkaConnectDSLParser and the utility class.
(at least, it will be the case if we keep the current restriction on notation for properties file that it must be with '=' and without spaces)
@bfitzpat With these explanations, do you agree to keep it in the CamelKafkaConnectDSLParser class? or still prefer to extract a small utility class with cross-references for the constants? (or I missed the concern that you are raising and went in the wrong direction?)

If I understood well, it would give something like that https://github.com/apupier/camel-language-server/pull/1
I'm not convinced that it is clearer.

I'm ok with the kafka approach for now, but think we should extract out anything we're going to use more broadly wherever possible. But I get the difficulty

I created https://issues.redhat.com/browse/FUSETOOLS2-132 to be sure to improve this part of the code


Fixed fasterxml.jackson security vulnerability

Issue #, if available:
Fasterxml-jackson security vulnerability
Description of changes:
Raised version in pom.xml-file
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Merged due to absence of second approver


Add pixels when FB login fails due to unsupported

Task/Issue URL: https://app.asana.com/0/0/1203467208458897/f
Description
This PR adds a pixel whenever a user lands on the unsupported error page on FB and also when londing on login.php. A while ago FB disabled WebView from their auth flow and we get breakage reports every now and then, the idea of this PR is to monitor for a couple of weeks when this error happens using login.php as denominator and then decide next steps.
Steps to test this PR
Feature 1

[ ] Install the app and go to instagram.com
[ ] Click on Log In
[ ] Click on Continue Using Facebook
[ ] You should eventually see the FB page for WebView unsupported
[ ] Two pixels should have been sent m_facebook_login_breakage_investigation and m_facebook_login_error_breakage_investigation

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #2601   👈

This comment was auto-generated by Graphite.


GUVNOR-2030: Guided Decision Table: Empty field results in all Conditions being cancelled

See https://issues.jboss.org/browse/GUVNOR-2030
This PR adds extraction of "Template Keys" to the DRL->RuleModel parsing to support use of IPattern and IAction in BRL Fragments in XLS to Guided Decision Table conversion.

+1

Merged by https://github.com/droolsjbpm/drools/commit/07748111b


No module named virtualfish error

I encountered this issue when using virtualfish. As per the documentation, my config.fish file has:
eval (python -m virtualfish auto_activation compat_aliases projects)
I had to replace python with /usr/local/bin/python to avoid getting that error.

Hi,
A few questions so we can figure out what's going on: What OS are you using? How did you install virtualfish? What's the output of which pip and which python?

I'm on OSX (using Terminal, fish installed from brew) and did a pip install of virtualfish.
which pip: /usr/local/bin/pip
which python: /usr/local/bin/python (brew)
The problem happens when I am already inside a virtualenv - as if it is looking for virtualfish in my virtualenv, but I don't have it installed there. Also, I cannot reproduce it reliably, but using workon or just pressing Enter a few times will cause it to pop up.

After looking into this more, it seems the issue is with a theme that I had, vkovtash/pure. It's causing the config.fish file to be reloaded for some reason.

Did you find a solution to that? What did you have to change? I have the same issue.


"Ambiguous reference to This" in extension method returning This

I'm trying to do something like this:
interface Monoid {
    static const This identity;

    This combine(This b);
}

extension Monoid {
    This wave_reduce() {
        // TODO: actual logic to do wave reduction
        return This.identity;
    }
}

The idea is to implement it for the addition monoid using WaveActiveSum, but let it fall to the generic implementation for monoids that don't have such a specialization. When I compile this, I get:
monoid.slang(25): error 39999: ambiguous reference to 'This'

I'm not sure if this is a real limitation in the language's type system, or just a case not well handled. In Rust, the extension wouldn't be in a separate block, it would just be a default implementation of the method in the trait.

Looks like this is just a bug in the type system.

@raphlinus Does this issue block work for you? It sounds like there's a bit more than a simple bug here, and I'm not sure we can prioritize this in the very near term. We may also be able to identify a workaround if you can share what issue you're attempting to solve.

@raphlinus we plan to address this issue in Q3 2024. Please let us know if that timeline doesn't work for you.

Thanks for the update! I should clarify, this isn't really blocking me, it came up while I was exploring. I'm still doing almost all my shader work in WGSL, but would like to move to Slang when that becomes practical.


SRPM build logs: change url from copr-be to download.copr

We are using this build logs host:
<EMAIL_ADDRESS>Instead, we should use this:
<EMAIL_ADDRESS>As copr-be is 404 and only contains the logs after the build is done; download.copr has them right away

The hardcoded URL is set here both for SRPM and RPM builds.


Design data models

Models

User (mainly for administration)
post

User
id
created
modified
email
name
password
salt

Group
id
created
modified
name
parent

Post
id
created
modified
group
author
name
content


Fix failing release workflow

Fixes #18
NB: Will test the workflow as CI (without releasing) before merging.

Codecov Report

Merging #20 (cc8e0d4) into main (2277546) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage   72.19%   72.19%
=======================================
  Files          12       12
  Lines         464      464
=======================================
  Hits          335      335
  Misses        129      129

Flag
Coverage Δ

linux
72.19% <ø> (ø)

windows
?

Flags with carried forward coverage won't be shown. Click here to find out 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 2277546...cc8e0d4. Read the comment docs.


Improve README

Currently the README.md assumed that the reader has also read the AN12 including the product to platform mapping. In order to keep the burden low, replace the product with platform names. This should avoid confusion for new users.
Btw update servicedesk link and drop stray character.

After creating this pull request i noticed the kirkstone-everest branch. I will try to use that for orientation.

I force pushed the commit.


Uniform Time Profile has bad parameters

The uniform time profile has bad fitting parameters. It currently uses start and end, but this can result in end crossing over start in fitting, or at least wanting to. It's better to use start and length, where length is bounded by 0 on the left.

I will change that. Also I will want to point out that the current TimeDependentPsAnalysis doesn't fit the time profile but just use the fix time profile to evaluate the likelihood. I still haven't figure out a way to better fit the time profile so I will put it on hold for now.

There's not a great way to fit some of the possible profiles. The uniform time profile in particular will have a non-smooth likelihood space due to the hard edges in the PDF. You may be able to get away with a standard minimizer with other PDFs, but a uniform distribution may require a brute force scan instead.

would this problem also extend to the histogram one?

I think you can only fit an off-set to a histogram pdf? So probably ok?

@mjlarson how were the box profiles fit for txs?

fixed.


Image Docker not available for 4.1.0

Bug description
Images docker are available for 4.0.2 or 4.1.1 but not for 4.1.0

The build is automatised (https://superset.apache.org/docs/installation/docker-builds/)
the 4.1.0 image should be present
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

There is a whole thread here: https://github.com/apache/superset/issues/30919. We ran into some issues so we bumped to 4.1.1 to fix the docker issue.


link rel="canonical"

https://yoast.com/rel-canonical/

Is this required if your url is already canonical ?

That yoast page says you should always have one to point out the "cleanest URL"

I didn't know. Ok nice.


hangs with OutOfMemoryError: Java Heap space when trying to create an edge

OrientDB Version: 3.0.12
Java Version: 10.0.2
OS: Windows
Expected behavior
Should be able to create an edge with no error.
Actual behavior
OrientDB hangs and throws OutofmemoryError: Java Heap space when trying to create an edge.
Steps to reproduce
Adding the sample database with three vertex, one edge and one function.
Please execute the function vertex_job_create to reproduce the issue.
db1.gz

Hi guys, please let me know if this issue still actual I will work on it.


Request PAID version

Hi,
Thanks a lot for your code, its amazing; however, It will be great if you can add more function like: creating account and input mail:pass instead of inputing token, nodeid, hardwareid....
Do you have any group or community channel? I will join and contribute in anyway.
I am happy if you have paid version or even donation for your work.
My telegram: @holdtodie93
Happy to connect to you
Thanks.

Thanks for the great feedback and requests, but it probably won't be my top priority to implement that feature since I code only when I have free time.


Generated messages virtual file contains syntax error when some locale files written in yaml is empty

Reporting a bug?
Generated messages virtual file contains syntax error when some locale files written in yaml is empty
Expected behavior
Should not contain syntax errors.
Reproduction
Unable to create a "minimal" one now, but soon
But it should be pretty straight-forward to reproduce using such configuration: vite.config.ts
Issue Package
unplugin-vue-i18n
System Info
Unable to run the command now - will update later using my PC

Screenshot
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the README
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.

Thanks! Sorry for the inconvenience, I'm unable to use my PC now 😓


The InfluxDB version panel is incomplete unless an admin influx user is used

The SPPmon setup instructions recommend using the grafanaReader user to register Influx as a data source.  This prevents the InfluxDB version from determining the version and it reports "No Data".
The explanation includes:
InfluxDB Error: error authorizing query: grafanaReader not authorized to execute statement 'SHOW DIAGNOSTICS', requires admin privilege
Need to find an alternate source of the Influx version that does not require admin privileges.

Apparently to this issue, the version is send with each request. Maybe Grafana is able to read it, though I am not sure if the display of request information is supported.
https://github.com/influxdata/influxdb/issues/1072


Upgrade our issue templates to use GitHub issue forms ✍

Introduction
GitHub has recently rolled out a public beta for their issue forms feature. This would allow you to create interactive issue templates and validate them 🤯.
Appwrite currently uses the older issue template format. Your task is to create GitHub issue forms for this repository. Please use Appwrite's issue templates as a reference for this PR.
Tasks summary:

[ ] Fork & clone this repository
[ ] Prepare bug report issue form in .github/ISSUE_TEMPLATE/bug.yaml
[ ] Prepare documentation issue form in .github/ISSUE_TEMPLATE/documentation.yaml
[ ] Prepare feature request issue form in .github/ISSUE_TEMPLATE/feature.yaml
[ ] Push changes to master and test issue forms on your fork
[ ] Submit pull request

If you need any help, reach out to us on our Discord server.
Are you ready to work on this issue? 🤔 Let us know, and we will assign it to you 😊
Happy Appwriting!

@Meldiron  can i work on this issue?

@vendz Assigned it to you! All the best 🚀

@Meldiron #3 closes this issue so please check it out

@vendz Thanks for the PR! 🤯 Please give us some time to review it.


Theme Picker Color Change Performance is Slow (DevTools)

The theme picker in our DevTools is experiencing significant delays when changing colors. It affects the user experience by making the theme customization process cumbersome and slow.

fixed with layouting rework


Expand does not work after item is moved

Note: for support questions, please use our Gitter channel. This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
What is the current behavior?
When trying the demo on the angular-ui-tree home page, after a node is moved it cannot be expanded. For example, after node 1 is moved its expand button is no longer clickable. It seems that when the node's expand button is clicked a drag event is activated instead of a button click. This seems to happen for any node that is moved (Or any node that is dragged & dropped into the same location).
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar.
If node 1 is moved into the location of node 2 (thus switching node 1 and node 2's location) node 1 can no longer be expanded. When node 1's expand button is clicked, it seems that the drag event is activated instead of a button click event.
What is the expected behavior?
The expected behavior is that after moving a node (via drag & drop) the node's expand button should still be clickable (and treated as a button click and not as a drag activation) after the node is moved.
What is the motivation / use case for changing the behavior?
Which versions of Angular, UI Tree and which browser / OS are affected by this issue? Did this work in previous versions of Angular, UI Tree? Please also test with the latest version.
This problem seems to appear starting in version 2.15.0. The problem does not seem to appear in version 2.14.0. The problem seems to exist in the latest version and it can be reproduced using the "basic example" on the project's main demo page.
http://angular-ui-tree.github.io/angular-ui-tree/#/basic-example
Other information (e.g. stacktraces, related issues, suggestions how to fix)

Can confirm.
Second example, in the basic example on the demo page, just click to move the "node 1.1" but don't move it at all, the bug appears also. Moreover, actions buttons don't work neither after that.

Move ui-tree-handle from the wrapping
 to another element that doesn't wrap your controls (expand, add subitem etc.).

         0" data-nodrag ng-click="toggle(this)">
        {[{ node.title }]}

Thanks bilalmallick - that worked for me! - Maybe something with the floated buttons is screwing with the keypress, anyway it'd be good to update the doc - great component so far...

Great, the solution to move the ui-tree-handle inside the tree-node div worked perfect among all mentioned above. Thanks bilalmallick

Seems like it has been fixed in 2.22.4 (PR #878)

Fixed in v2.22.4


Refactor of Favorites feature

Issue

Addresses #78

Description
Refactor of the frontend and backend favorites feature. When a user logs in, they can now favorite or unfavorite listings from the listings page.

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Prototype/POC (not to merge)
[ ] This change is a refactor/addresses technical debt
[ ] This change requires a documentation update
[ ] This change requires a SQL Script

How Can This Be Tested/Reviewed?
View the console log while adding and removing listings while signed in.
You will see the favorites listing array being added to and removed from.  You can also view the user_preference table in the backend to see the information stored.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have reviewed the changes in a desktop view
[x] I have reviewed the changes in a mobile view
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have assigned reviewers
[ ] I have updated the changelog to include a description of my changes
[x] I have run yarn generate:client if I made backend changes
[x] I have exported any new pieces in ui-components

This branch simplifies the backend favorites storage from a full Listing (#797) to a string array of Listing IDs.  This branch stores and displays correctly on the frontend and backend, but is currently failing the e2e testing.  Upon adding the dummy listing data similar to other existing tests, the test just runs and stays running for multiple hours. Have attempted to leverage Archer listing data, as well as newly created test listing.  Neither solution progresses.

losing this PR as #939 addresses the challenges with this branch, specifically the e2e testing.


Adding styling to the scrollbars, according to theme of the web app

Is your feature request related to a problem? Please describe.
White scrollbars look odd with respect to the current theme of the website.
Describe the solution you'd like
We can add styling to the scroll bar for both dark mode and light mode.
Describe alternatives you've considered
The solution is pretty straightforward, and shouldn't require alternatives
Additional context
Styling can be added to both side and overflow scroll bar

Duplicates #2158


fix: Recursive tag application for array fields

Prior to this fix minLength would've been missing from the []string field

@samlown this is one of the things uncovered during the schema gen for CloudQuery.

@samlown could I get a release for this one, too?

@samlown I've stumbled upon an interesting regression from this change, I'll make a follow-up PR (it's related to default behavior being used both for the array & for the underlying string


Live reload not working with reverse proxy

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
When running Docusaurus behind a reverse proxy (Codespaces, code-server etc.), Docusaurus is likely being accessed under a different url than it is being exposed on. (eg. localhost:3000 --Docker & Reverse Proxy-> dev.mycodespace.io)
In this scenario (Docusaurus needs to be run with --host <IP_ADDRESS>), webpack uses the same options for the web socket server as for the dev server, and passes those on to the client: protocol=ws%3A&hostname=<IP_ADDRESS>&port=3000&pathname=%2Fws&logging=warn&reconnect=10
(https://github.com/webpack/webpack-dev-server/blob/master/lib/Server.js#L634). Luckily, <IP_ADDRESS> is replaced by self.location.hostname (https://github.com/webpack/webpack-dev-server/blob/master/client-src/utils/createSocketURL.js#L91), same goes for the protocol, but there is no way to correct the incorrect port, so there must be a way for the developer to specify this. This should be implemented here: https://github.com/facebook/docusaurus/blob/main/packages/docusaurus/src/commands/start.ts#L190
For those who are looking for a solution for the time being, this patch will make webpack hot reload connect to self.location.port.
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 4fd663b..3678353 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -142,6 +142,9 @@ async function start(siteDirParam = '.', cliOptions = {}) {
                 warnings: false,
                 errors: true,
             },
+            webSocketURL: {
+                port: 0
+            }
         },
         headers: {
             'access-control-allow-origin': '*',

Reproducible demo
No response
Steps to reproduce

Run Docusaurus behind a reverse proxy (inside a Docker Container in this example)
Start dev mode pnpm start --host <IP_ADDRESS>
Open console and see errors (also no live reload)

Expected behavior
Docusaurus should automatically refresh after changes to the source file.
Actual behavior
It does not.
Your environment
pnpm start --host <IP_ADDRESS> inside a Docker Container that rebinds :3000 -> :3007 hidden behind a reverse proxy that serves :3007 on dev.mycodespace.io
Self-service

[x] I'd be willing to fix this bug myself.

Hey
I'm not a Docker / Codespace expert, can you provide us a runnable sandbox or clearer repro instructions so that we are sure to reproduce your problem without having to figure out the details ourselves?
Can you explain why this config solves the problem?
           webSocketURL: {
                port: 0
           }

Where does this solution come from exactly? What does port: 0 do?

The snippet fixes the problem, since it tells HMR to use the same port that the website is currently running on. You should also consider always passing <IP_ADDRESS> as hostname, since that makes it also use the current domain.
The following code snippets go together, and this is where the issue arises:

https://github.com/facebook/docusaurus/blob/main/packages/docusaurus/src/commands/start.ts#L190 (This is where webpack dev server is initialized)
https://github.com/webpack/webpack-dev-server/blob/master/lib/Server.js#L478 (Constructing data to pass to the client)
https://github.com/webpack/webpack-dev-server/blob/49efdf87341d4e40106baae60670a4aabf3285fb/client-src/utils/createSocketURL.js#L75 (Parsing of the passed data)

Will provide a repo with steps to reproduce asap

Yeah no there isn't really a repo to provide.
What you need is a development instance of Docusaurus running, and a reverse proxy (nginx, Apache, IIS etc.) that wraps around Docusaurus, normally port 3000. The only important thing is that Docusaurus is not served on the same port to the client as it is exposed to on the server.
In that situation, hmr will try to use the port the server was started on, unless its told to pick the port the browser is currently accessing (see comment above) by passing port: 0.

@jeengbe this is an edge case and I don't want to spend 1 day relearning how to install and configure apache. If you want it to be solved faster, provide clear instructions to reproduce it, preferably with Docker. Yes, I'm asking you to invest your own time to save mine.
Now if you can create a PR where it doesn't change the behavior at all for regular users, but solve your problem, I'm ok to merge it blindly.
I'm ok to add a secret env variable just for this.

Note I believe this is a decent escape hatch you can use today with a docusaurus plugin:
function CustomDevServerPlugin() {
  return {
    name: "custom-dev-server-plugin",
    configureWebpack() {
      return {
        devServer: {
          client: {
            webSocketURL: {
              port: 0
            }
          }
        }
      };
    }
  };
}

So what we implement here would just be a convenient shortcut for the above?

I do very well understand that. Luckily, I had a similar configuration lying around and quickly managed to throw together a working sample repository. Note that you might have to wait a little for Docusaurus to finish building upon launching it.
Locate to localhost, and open dev tools to see ws:// connections being made to localhost:3000

The fix above fixes this issue as it, as outlined above with code references, makes hmr use the port the site is being accessed on.

Your environment
pnpm start --host <IP_ADDRESS> inside a Docker Container that rebinds :3000 -> :3007 hidden behind a reverse proxy that serves :3007 on dev.mycodespace.io

Do not remap the port with Docker.
"Remap" to the same port and if you need a different port change it via the --port option.
Tested with 2.3.0.

I'm currently seeing this error on a new Docusaurus (2.4.1) running behind Nginx (1.22.0) on a remote server:

I don't want to use --host <IP_ADDRESS> because that defeats the purpose of using Nginx... is there a configuration option I can use to tell webpack to use my real server address to serve up the websocket?

@splurgebudget try v3 canary, cf https://github.com/facebook/docusaurus/pull/7951#issuecomment-1341167782


ext-authz: return error for invalid extension provider only when it is being used

Fixes #30824
If some extension provider is not used by any authz policy, it should not cause errors even if it might be invalid.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[x] Does not have any changes that may affect Istio users.

@yangminzhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b19a0db87b840a6e6b4e590eaddd346d079a26c9
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio

is the error in the original issue coming from the validation webhook when applying the meshconfig updaets? I didn't see other unit test updates other than validation-test.go

is the error in the original issue coming from the validation webhook when applying the meshconfig updaets? I didn't see other unit test updates other than validation-test.go

@incfly not from validation webhook but directly from the authz plugin in pilot, it emits the error every time it is called when pushing xDS configs to proxy.

In response to a cherrypick label: new pull request created: #30959


WIP - Update style to django 1.8

There are a few things that are very much out of date – like using models.permalink, using patterns() in urls.py, etc – this PR is about fixing those small things.

Isn't the whole point of using patterns() to avoid having circular imports do to urls importing other modules which again rely on urls ?

This is probably no longer relevant due to the upgrades to 1.9/10/11 already made and merged in other branches.