Elli Wallbox not reacheable via mdns -> Timeout

Describe the bug
I have a problem when starting evcc. It seems that my wallbox (ID. Charger Pro) is not reachable.
The problem is displayed as “mdns: avahi - no IPv4 addresses available”.
My last successful configuration was with version 0.127.3. and I would like to update to 0.130.2.
Since 0.127.3 I can no longer reach my ID. Charger Pro. Neither with a previously working evcc.yaml nor after replacing the certificate during configuration. I have tried it with every version.
Is there a way to enter a fixed IP address as before? Or another workaround?
I know that this wallbox is defective, but unfortunately I have to use it. That's why I bought an external electricity meter, hoping that the latest optimization for the Elli wallboxes would solve my problem. But unfortunately not.
Tried macOS, Linux and a native home assistant.
Steps to reproduce
Start evcc
Configuration details
# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: trace
levels:
  cache: trace
  eebus: trace
  core: trace

# unique installation id
plant: ***

interval: 30s # control cycle interval

sponsortoken: ***
telemetry: true

meters:
- type: template
  template: kostal-plenticore
  id: 71
  host: <IP_ADDRESS>
  port: 1502
  usage: pv
  modbus: tcpip
  name: pv_kostal
- type: template
  template: kostal-plenticore
  id: 71
  host: <IP_ADDRESS>
  port: 1502
  usage: battery
  modbus: tcpip
  name: battery_byd
- type: template
  template: kostal-ksem-inverter
  id: 71
  host: <IP_ADDRESS>
  port: 1502
  usage: grid
  modbus: tcpip
  name: grid_kostal_ksem
- type: template
  template: shelly-pro-3em
  usage: charge
  host: <IP_ADDRESS>
  name: meter_elli

chargers:
- type: template
  template: ellipro
  ski: ***
  # ip: <IP_ADDRESS> ## kept from 0.127.3
  name: wallbox_elli

loadpoints:
- title: ID.
Linux
Version
evcc version 0.130.2

Does 130.2 still work for you? Current nightly?

Does 130.2 still work for you? Current nightly?

0.127.3 is working. Later released Version not.
I will give the latest nightly a try.

/cc @DerAndereAndi avahi issue

Well, v0.127.3 is also using avahi. If the mDNS entry provided by the wallbox, does not provide an IPv4 address, then no connecting can be provided. Usually shortly after another mDNS entry is provided which includes an IPv4.
The log entry is NOT an error, just an  info. Also, it is NOT the case that only the HEMS shall initiate a connection, the wallbox shall does so as well, but as far as I know hardly ever does.
But please provide a log with eebus on TRACE level to see more details.

Could you please run on your linux system where evcc is running the following command and provide the output (may require to install the avahi-utils apt package):
avahi-browse -d local _ship._tcp --resolve -t

Could you please run on your linux system where evcc is running the following command and provide the output (may require to install the avahi-utils apt package):
avahi-browse -d local _ship._tcp --resolve -t

On macOS you can use the Discovery tool, available in the App Store. And there the "folder" _ship._tcp. is relevant. Open the entry of the Elli wallbox and provide a screenshot with all the data present.

I can only provide the log while running 0.127.3:
avahi-0.127.3.log
0.130.2 now crashes with
[eebus ] DEBUG 2024/08/24 21:25:55 starting websocket server on :4712
panic: send on closed channel

goroutine 41 [running]:
github.com/holoplot/go-avahi.(*ServiceBrowser).dispatchSignal(0xc001066540, 0xc0002fca50)
        github.com/holoplot/go-avahi@v1.0.1/service-browser.go:51 +0x459
github.com/holoplot/go-avahi.ServerNew.func1()
        github.com/holoplot/go-avahi@v1.0.1/server.go:58 +0x1ac
created by github.com/holoplot/go-avahi.ServerNew in goroutine 1
        github.com/holoplot/go-avahi@v1.0.1/server.go:47 +0x219

Well, v0.127.3 is also using avahi. If the mDNS entry provided by the wallbox, does not provide an IPv4 address, then no connecting can be provided. Usually shortly after another mDNS entry is provided which includes an IPv4. I never got a connection with IPv6 working, so I do not try.
The log entry is NOT an error, just an info. Also, it is NOT the case that only the HEMS shall initiate a connection, the wallbox shall does so as well, but as far as I know hardly ever does.
But please provide a log with eebus on TRACE level to see more details.

Is there more to configure for TRACE-Level than in the config above?

The crash is fixed and will be part of the next release. evcc accidentally included the wrong version of the mdns avahi library.
No, set the log level in the configuration file and run evcc. Then grab the output as you did before.
Could you please provide the avahi-browse or Discovery output? evcc doesn't have to run for that, as the data from the Elli wallbox is what's relevant.

Could you please try to set add the network interface `` to the eebus configuration in evcc.yaml? See https://docs.evcc.io/docs/reference/configuration/eebus#interfaces
eebus:
  interfaces:
    - eno1

This way evcc only uses that network interface for its mDNS announcement and all other IPs are ignored.
The log file shows that the IPv4 address is provided for the wallbox, but somehow not visible to the eebus code. I really would need the evcc log with eebus set to level trace and hope I'll see a hint on why it is not reported.

Could you please try to set add the network interface `` to the eebus configuration in evcc.yaml? See https://docs.evcc.io/docs/reference/configuration/eebus#interfaces
eebus:
  interfaces:
    - eno1

This way evcc only uses that network interface for its mDNS announcement and all other IPs are ignored.
The log file shows that the IPv4 address is provided for the wallbox, but somehow not visible to the eebus code. I really would need the evcc log with eebus set to level trace and hope I'll see a hint on why it is not reported.

I retried with the interface 0.130.2 under Linux. eno1 is the right interface (checked ifconfig).
evcc didn't crash, but is not running.
Setting:
log: trace
levels:
  eebus: trace

startup.log

me too. looking forward to the next release...

Could you guys please run this tool for a minute and post the output?
Windows Intel/AMD CPU:
mdns_windows_amd.exe zeroconf

Linux ARM CPU (run both):
mdns_linux_arm avahi
mdns_linux_arm zeroconf

Linux Intel/AMD CPU (run both):
mdns_linux_amd avahi
mdns_linux_amd zeroconf

macOS ARM CPU:
mdns_macos_arm zeroconf

mdns.zip

[eebus ] DEBUG 2024/08/25 17:57:30 connection to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f failed: dial tcp <IP_ADDRESS>:4712: i/o timeout
> $ /Users/jorge/Downloads/mdns/mdns_macos_arm  zeroconf
2024-08-25 17:57:39 DEBUG mdns: announce
2024-08-25 17:57:39 DEBUG mdns: using zeroconf
2024-08-25 17:57:39 DEBUG mdns: start search
2024-08-25 17:57:39 DEBUG mdns: stop announcement
2024-08-25 17:57:39 DEBUG mdns: new - ski: 9a46bcb42045efb7a5f449a89482621ca87eb4dc name: EVCC_HEMS_01 brand: EVCC model: HEMS typ: EnergyManagementSystem identifier: EVCC-6562366335333765 register: false host: MacBook-Pro-8.local. port: 4712 addresses: [<IP_ADDRESS>]
2024-08-25 17:57:39 INFO  Currently known entries:
2024-08-25 17:57:39 INFO    &{EVCC_HEMS_01 9a46bcb42045efb7a5f449a89482621ca87eb4dc EVCC-6562366335333765 /ship/ false EVCC EnergyManagementSystem HEMS MacBook-Pro-8.local. 4712 [<IP_ADDRESS>]}
2024-08-25 17:57:39 DEBUG mdns: new - ski: ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f name: Livo-EVB-500-015-503 brand: EVBox model: Livo typ: ChargingStation identifier: EVBox-Livo-EVB-500-015-503 register: false host: EVB-500-015-503.local. port: 4712 addresses: [<IP_ADDRESS>]
2024-08-25 17:57:39 INFO  Currently known entries:
2024-08-25 17:57:39 INFO    &{EVCC_HEMS_01 9a46bcb42045efb7a5f449a89482621ca87eb4dc EVCC-6562366335333765 /ship/ false EVCC EnergyManagementSystem HEMS MacBook-Pro-8.local. 4712 [<IP_ADDRESS>]}
2024-08-25 17:57:39 INFO    &{Livo-EVB-500-015-503 ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f EVBox-Livo-EVB-500-015-503 /ship/ false EVBox ChargingStation Livo EVB-500-015-503.local. 4712 [<IP_ADDRESS>]}
2024-08-25 18:00:51 DEBUG mdns: remove - ski: ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f name: Livo-EVB-500-015-503 brand: EVBox model: Livo typ: ChargingStation identifier: EVBox-Livo-EVB-500-015-503 register: false host: EVB-500-015-503.local. port: 4712 addresses: [<IP_ADDRESS>]
2024-08-25 18:00:51 INFO  Currently known entries:
2024-08-25 18:00:51 INFO    &{EVCC_HEMS_01 9a46bcb42045efb7a5f449a89482621ca87eb4dc EVCC-6562366335333765 /ship/ false EVCC EnergyManagementSystem HEMS MacBook-Pro-8.local. 4712 [<IP_ADDRESS>]}
^C%

@jomach please contact EVBox. Seems they still have a lot of software issues. They are also the ones who developed the Elli Connect/Pro wallboxes. The Wallbox reports the IP address and port and then doesn't answer. There is absolutely nothing that can be done from the outside.

Ok. Let me know id I can help someone where

Could you guys please run this tool for a minute and post the output?

of course
mdns_linux_amd-zeroconf.log
mdns_linux_amd-ahavi.log

The confusing thing is how that should have worked on 0.127. the only explanation we have sofar is that current version trips different bugs in den FW that lead to this behavior. Fact is: the box has entirely crappy SW, not even featuring a valid certificate to begin with.

here is my output from an Elli Connect wallbox (software release v3.8.12) and evcc 0.127.3:
./mdns_linux_amd avahi
2024-08-25 18:42:15 DEBUG mdns: announce
2024-08-25 18:42:15 DEBUG mdns: using avahi
2024-08-25 18:42:15 DEBUG mdns: start search
2024-08-25 18:42:15 DEBUG mdns: stop announcement
2024-08-25 18:42:15 TRACE mdns: avahi - process add service: Elli-Wallbox-2135A1LQJU _ship._tcp local wallbox-2135A1LQJU.local fe80::cb61:a6b2:cfe3:c78 4712 map[brand:Elli id:Elli-Wallbox-2135A1LQJU model:Wallbox org.freedesktop.Avahi.cookie:2134517928 path:/ship/ register:false ski:991e0fcb2c17c1e372a95178c6408490279e3859 txtvers:1 type:Wallbox]
2024-08-25 18:42:15 DEBUG mdns: avahi - no IPv4 addresses available Elli-Wallbox-2135A1LQJU
2024-08-25 18:42:15 TRACE mdns: avahi - process add service: EVCC_HEMS_01 _ship._tcp local tiksi.ohli.de.local <IP_ADDRESS> 4712 map[brand:EVCC id:EVCC-3531636530656434 model:HEMS path:/ship/ register:true ski:ff32ea1788126d3085a51d0ce3c98a5472db1cb3 txtvers:1 type:EnergyManagementSystem]
2024-08-25 18:42:15 DEBUG mdns: new - ski: ff32ea1788126d3085a51d0ce3c98a5472db1cb3 name: EVCC_HEMS_01 brand: EVCC model: HEMS typ: EnergyManagementSystem identifier: EVCC-3531636530656434 register: true host: tiksi.ohli.de.local port: 4712 addresses: [<IP_ADDRESS>]
2024-08-25 18:42:15 INFO  Currently known entries:
2024-08-25 18:42:15 INFO    &{EVCC_HEMS_01 ff32ea1788126d3085a51d0ce3c98a5472db1cb3 EVCC-3531636530656434 /ship/ true EVCC EnergyManagementSystem HEMS tiksi.ohli.de.local 4712 [<IP_ADDRESS>]}
2024-08-25 18:42:15 TRACE mdns: avahi - process add service: Elli-Wallbox-2135A1LQJU _ship._tcp local wallbox-2135A1LQJU.local fe80::cb61:a6b2:cfe3:c78 4712 map[brand:Elli id:Elli-Wallbox-2135A1LQJU model:Wallbox org.freedesktop.Avahi.cookie:2134517928 path:/ship/ register:false ski:991e0fcb2c17c1e372a95178c6408490279e3859 txtvers:1 type:Wallbox]
2024-08-25 18:42:15 DEBUG mdns: avahi - no IPv4 addresses available Elli-Wallbox-2135A1LQJU
2024-08-25 18:42:15 TRACE mdns: avahi - process add service: EVCC_HEMS_01 _ship._tcp local tiksi.ohli.de.local <IP_ADDRESS> 4712 map[brand:EVCC id:EVCC-3531636530656434 model:HEMS path:/ship/ register:true ski:ff32ea1788126d3085a51d0ce3c98a5472db1cb3 txtvers:1 type:EnergyManagementSystem]
2024-08-25 18:42:15 TRACE mdns: avahi - process add service: EVCC_HEMS_01 _ship._tcp local tiksi.ohli.de.local <IP_ADDRESS> 4712 map[brand:EVCC id:EVCC-3531636530656434 model:HEMS path:/ship/ register:true ski:ff32ea1788126d3085a51d0ce3c98a5472db1cb3 txtvers:1 type:EnergyManagementSystem]
2024-08-25 18:42:15 TRACE mdns: avahi - process add service: EVCC_HEMS_01 _ship._tcp local tiksi.ohli.de.local <IP_ADDRESS> 4712 map[brand:EVCC id:EVCC-3531636530656434 model:HEMS path:/ship/ register:true ski:ff32ea1788126d3085a51d0ce3c98a5472db1cb3 txtvers:1 type:EnergyManagementSystem]

2024-08-25 18:43:27 DEBUG mdns: announce
2024-08-25 18:43:27 DEBUG mdns: using zeroconf
2024-08-25 18:43:27 DEBUG mdns: start search
2024-08-25 18:43:27 DEBUG mdns: stop announcement
2024-08-25 18:43:27 DEBUG mdns: new - ski: ff32ea1788126d3085a51d0ce3c98a5472db1cb3 name: EVCC_HEMS_01 brand: EVCC model: HEMS typ: EnergyManagementSystem identifier: EVCC-3531636530656434 register: true host: tiksi.ohli.de.local. port: 4712 addresses: [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]
2024-08-25 18:43:27 INFO  Currently known entries:
2024-08-25 18:43:27 INFO    &{EVCC_HEMS_01 ff32ea1788126d3085a51d0ce3c98a5472db1cb3 EVCC-3531636530656434 /ship/ true EVCC EnergyManagementSystem HEMS tiksi.ohli.de.local. 4712 [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]}

One reason why this version is working for me is that I can set the IP via the config. So, mdns should not be needed...

Can we verify if mdns leads to different/wrong IPs than manual config?

@sebastianohl some notes:

even avahi never receives an IPv4 address which is very weird
Can you ping wallbox-2135A1LQJU.local or fe80::cb61:a6b2:cfe3:c78 ?

mDNS is needed anyway, since we need to know the port address.

@mbjw77 Can you try to ping wallbox-2040A0ZSTF.local and fe80::b389:a1d7:80d:53c9 ?
Did you quit the app directly or did you let it run a bit? Especially with zeroconf ?

@mbjw77 Can you try to ping wallbox-2040A0ZSTF.local and fe80::b389:a1d7:80d:53c9 ?

user@server:~ $ ping wallbox-2040A0ZSTF.local
PING wallbox-2040A0ZSTF.local (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.628 ms
...

user@server:~ $ ping fe80::b389:a1d7:80d:53c9
PING fe80::b389:a1d7:80d:53c9(fe80::b389:a1d7:80d:53c9) 56 data bytes
64 bytes from fe80::b389:a1d7:80d:53c9%eno1: icmp_seq=1 ttl=64 time=1.77 ms
...

Did you quit the app directly or did you let it run a bit? Especially with zeroconf ?

They ran for about 2 minutes. But I can add some more... running 6 minutes each.
mdns_linux_amd-ahavi.log
mdns_linux_amd-zeroconf.log

Thanks. Sometimes fe80 addresses work, but not always depending on the network setup.
Could you guys please give this updated version a try? The zeroconf option should hopefully now also provide an mDNS entry for the wallbox.
mdns.zip

@DerAndereAndi i can ping the fqdn and the ipv6 address. I let the zeroconf run for a few minutes (<5m)

@sebastianohl thanks. could you retry with the new build and post the outputs ?

By New buidl you mean 130.4 or master? I can try tomorrow...

The new build of the test tool attached here: https://github.com/evcc-io/evcc/issues/15651#issuecomment-2308945481

Thanks. Sometimes fe80 addresses work, but not always depending on the network setup.
Could you guys please give this updated version a try? The zeroconf option should hopefully now also provide an mDNS entry for the wallbox.
mdns.zip

10 minutes each
mdns_linux_amd-ahavi.log
mdns_linux_amd-zeroconf.log

Sadly zeroconf still doesn't show the wallbox. I can't reproduce this over here. What kind of setup do you guys have? WLAN, LAN, both, ... ?
Is anyone maybe able to provide a wireshark trace of the mDNS packages?

@DerAndereAndi  I just tried the version 0.126.1 and I still get the timeout but it works.

on the network config from evcc I removed the .local and I only enter the IP address. Then I get this:
> $ /Users/jorge/Downloads/evcc_0.126.1_macOS-all/evcc -c evcc.yaml
[main  ] INFO 2024/08/25 22:09:28 evcc 0.126.1
[main  ] INFO 2024/08/25 22:09:28 using config file: evcc.yaml
[main  ] INFO 2024/08/25 22:09:28 starting ui and api at :7070
[db    ] INFO 2024/08/25 22:09:28 using sqlite database: /Users/jorge/.evcc/evcc.db
[mqtt  ] INFO 2024/08/25 22:09:28 connecting evcc-1725378163 at tcp://<IP_ADDRESS>:1883
[eebus ] INFO 2024/08/25 22:09:28 Local SKI:  9a46bcb42045efb7a5f449a89482621ca87eb4dc
[eebus ] DEBUG 2024/08/25 22:09:28 mdns: announce
[eebus ] DEBUG 2024/08/25 22:09:28 mdns: using zeroconf
[eebus ] DEBUG 2024/08/25 22:09:28 starting websocket server on :4712
[eebus ] DEBUG 2024/08/25 22:09:28 mdns: start search
[eebus ] DEBUG 2024/08/25 22:09:32 incoming connection request from ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f
[eebus ] DEBUG 2024/08/25 22:09:32 Send:  read 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/08/25 22:09:32 Recv: d:_i:47859_EVBox-Livo-EVB-500-015-503: to NodeManagement read 675 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/08/25 22:09:32 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 reply 2 675 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/08/25 22:09:32 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 result 3 675 ResultData 0
[eebus ] DEBUG 2024/08/25 22:09:32 Recv: d:_i:47859_EVBox-Livo-EVB-500-015-503: to NodeManagement reply 677 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/08/25 22:09:32 Send:  call 4 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/08/25 22:09:32 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 read 5 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/08/25 22:09:32 ev connected
[eebus ] DEBUG 2024/08/25 22:09:32 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 call 6 NodeManagementSubscriptionRequestCall

With 0.130.x it does not work and I get:
[eebus ] DEBUG 2024/08/25 22:13:02 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 86 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:04 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 87 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:06 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 88 DeviceDiagnosisHeartbeatData
[lp-1  ] ERROR 2024/08/25 22:13:06 charge power: not available
[lp-1  ] ERROR 2024/08/25 22:13:07 charge currents: not available
[lp-1  ] ERROR 2024/08/25 22:13:07 charge rater: not available
[lp-1  ] ERROR 2024/08/25 22:13:07 charge power: not available
[lp-1  ] ERROR 2024/08/25 22:13:08 charge currents: not available
[eebus ] DEBUG 2024/08/25 22:13:08 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 89 DeviceDiagnosisHeartbeatData
[lp-1  ] ERROR 2024/08/25 22:13:08 charge rater: not available
[eebus ] DEBUG 2024/08/25 22:13:10 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 90 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:12 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 91 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:14 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 92 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:16 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 93 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:18 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 94 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:20 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 95 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:22 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 96 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/08/25 22:13:24 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 97 DeviceDiagnosisHeartbeatData
[lp-1  ] ERROR 2024/08/25 22:13:25 charge power: not available
[lp-1  ] ERROR 2024/08/25 22:13:26 charge currents: not available
[eebus ] DEBUG 2024/08/25 22:13:26 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 98 DeviceDiagnosisHeartbeatData
[lp-1  ] ERROR 2024/08/25 22:13:26 charge rater: not available
c[eebus ] DEBUG 2024/08/25 22:13:28 Send: d:_i:47859_EVBox-Livo-EVB-500-015-503 notify 99 DeviceDiagnosisHeartbeatData

So something has changed between 0.126.x and 0.130.x

@jomach please create a different ticket, you do have a different issue than the one discussed over here. This gets way too confusing for me to track.

Sadly zeroconf still doesn't show the wallbox. I can't reproduce this over here. What kind of setup do you guys have? WLAN, LAN, both, ... ?

Wallbox, server running evcc, a FritzBox and the Kostal-stuff are directly connected to an unmanaged gigabit switch via LAN.
The Wallbox gets its IP-address via dhcp from the FritzBox.
DNS is a Pi-Hole. Its IP-address is distributed via dhcp.
Server has a static IP-adress and uses the Fritz-Box direct as DNS

Is anyone maybe able to provide a wireshark trace of the mDNS packages?

I would try to generate one. But I'm not that experienced with Wireshark. Do you have a filter-configuration I could apply?

@mbjw77 Can you disable IPV6 from your FritzBox? can you run ifconfig  eno1 ?

@mbjw77 Can you disable IPV6 from your FritzBox? can you run ifconfig eno1 ? @DerAndereAndi Looks to me some network issue on the users network

I disabled IPv6 in my FritzBox

Router Advertisement im LAN aktiv: off
DNSv6-Server auch über Router Advertisement bekanntgeben: off
DHCPv6-Server in der FRITZ!Box deaktivieren: Es sind keine anderen DHCPv6-Server im Heimnetz vorhanden.

and tried 0.130.4
works :-)
Is there anything I could change, to get IPv6 running correctly (actually not in use, but maybe in future)?
startup.log
user@server:~ $  ifconfig eno1
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 2003:dd:af1a:b100:4e52:62ff:fe28:e68f  prefixlen 64  scopeid 0x0<global>
        inet6 fda7:dea9:e24e:0:4e52:62ff:fe28:e68f  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::4e52:62ff:fe28:e68f  prefixlen 64  scopeid 0x20<link>
        ether 4c:52:62:28:e6:8f  txqueuelen 1000  (Ethernet)
        RX packets<PHONE_NUMBER>  bytes<PHONE_NUMBER>806 (1.8 TiB)
        RX errors 0  dropped 398691  overruns 0  frame 0
        TX packets<PHONE_NUMBER>  bytes<PHONE_NUMBER>924 (3.3 TiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xa1200000-a1220000

inet6

I see that you have ipv6 still active on your ethernet card. You can try to disable it. So the issue is confirmed to be related to mdns and ipv6 ?

sorry for the delay. here are my logs.
ohli@magadan:~/Downloads$ ./mdns_linux_amd avahi
2024-08-28 20:00:33 DEBUG mdns: announce
2024-08-28 20:00:33 DEBUG mdns: using avahi
2024-08-28 20:00:33 DEBUG mdns: start search
2024-08-28 20:00:33 DEBUG mdns: stop announcement
2024-08-28 20:00:33 TRACE mdns: avahi - process add service: EVCC_HEMS_01 _ship._tcp local tiksi.ohli.de.local <IP_ADDRESS> 4712 map[brand:EVCC id:EVCC-3531636530656434 model:HEMS path:/ship/ register:false ski:ff32ea1788126d3085a51d0ce3c98a5472db1cb3 txtvers:1 type:EnergyManagementSystem]
2024-08-28 20:00:33 DEBUG mdns: new - ski: ff32ea1788126d3085a51d0ce3c98a5472db1cb3 name: EVCC_HEMS_01 brand: EVCC model: HEMS typ: EnergyManagementSystem identifier: EVCC-3531636530656434 register: false host: tiksi.ohli.de.local port: 4712 addresses: [<IP_ADDRESS>]
2024-08-28 20:00:33 INFO  Currently known entries:
2024-08-28 20:00:33 INFO    &{EVCC_HEMS_01 ff32ea1788126d3085a51d0ce3c98a5472db1cb3 EVCC-3531636530656434 /ship/ false EVCC EnergyManagementSystem HEMS tiksi.ohli.de.local 4712 [<IP_ADDRESS>]}
2024-08-28 20:00:33 TRACE mdns: avahi - process add service: Elli-Wallbox-2135A1LQJU _ship._tcp local wallbox-2135A1LQJU.local fe80::cb61:a6b2:cfe3:c78 4712 map[brand:Elli id:Elli-Wallbox-2135A1LQJU model:Wallbox org.freedesktop.Avahi.cookie:2134517928 path:/ship/ register:false ski:991e0fcb2c17c1e372a95178c6408490279e3859 txtvers:1 type:Wallbox]
2024-08-28 20:00:33 DEBUG mdns: new - ski: 991e0fcb2c17c1e372a95178c6408490279e3859 name: Elli-Wallbox-2135A1LQJU brand: Elli model: Wallbox typ: Wallbox identifier: Elli-Wallbox-2135A1LQJU register: false host: wallbox-2135A1LQJU.local port: 4712 addresses: [fe80::cb61:a6b2:cfe3:c78]
2024-08-28 20:00:33 INFO  Currently known entries:
2024-08-28 20:00:33 INFO    &{EVCC_HEMS_01 ff32ea1788126d3085a51d0ce3c98a5472db1cb3 EVCC-3531636530656434 /ship/ false EVCC EnergyManagementSystem HEMS tiksi.ohli.de.local 4712 [<IP_ADDRESS>]}
2024-08-28 20:00:33 INFO    &{Elli-Wallbox-2135A1LQJU 991e0fcb2c17c1e372a95178c6408490279e3859 Elli-Wallbox-2135A1LQJU /ship/ false Elli Wallbox Wallbox wallbox-2135A1LQJU.local 4712 [fe80::cb61:a6b2:cfe3:c78]}
2024-08-28 20:00:33 TRACE mdns: avahi - process add service: EVCC_HEMS_01 _ship._tcp local tiksi.ohli.de.local <IP_ADDRESS> 4712 map[brand:EVCC id:EVCC-3531636530656434 model:HEMS path:/ship/ register:false ski:ff32ea1788126d3085a51d0ce3c98a5472db1cb3 txtvers:1 type:EnergyManagementSystem]
2024-08-28 20:00:33 TRACE mdns: avahi - process add service: EVCC_HEMS_01 _ship._tcp local tiksi.ohli.de.local <IP_ADDRESS> 4712 map[brand:EVCC id:EVCC-3531636530656434 model:HEMS path:/ship/ register:false ski:ff32ea1788126d3085a51d0ce3c98a5472db1cb3 txtvers:1 type:EnergyManagementSystem]
2024-08-28 20:00:33 TRACE mdns: avahi - process add service: Elli-Wallbox-2135A1LQJU _ship._tcp local wallbox-2135A1LQJU.local fe80::cb61:a6b2:cfe3:c78 4712 map[brand:Elli id:Elli-Wallbox-2135A1LQJU model:Wallbox org.freedesktop.Avahi.cookie:2134517928 path:/ship/ register:false ski:991e0fcb2c17c1e372a95178c6408490279e3859 txtvers:1 type:Wallbox]
2024-08-28 20:00:33 TRACE mdns: avahi - process add service: EVCC_HEMS_01 _ship._tcp local tiksi.ohli.de.local <IP_ADDRESS> 4712 map[brand:EVCC id:EVCC-3531636530656434 model:HEMS path:/ship/ register:false ski:ff32ea1788126d3085a51d0ce3c98a5472db1cb3 txtvers:1 type:EnergyManagementSystem]

2024-08-28 20:02:28 DEBUG mdns: announce
2024-08-28 20:02:28 DEBUG mdns: using zeroconf
2024-08-28 20:02:28 DEBUG mdns: start search
2024-08-28 20:02:28 DEBUG mdns: stop announcement
2024-08-28 20:02:28 DEBUG mdns: new - ski: ff32ea1788126d3085a51d0ce3c98a5472db1cb3 name: EVCC_HEMS_01 brand: EVCC model: HEMS typ: EnergyManagementSystem identifier: EVCC-3531636530656434 register: false host: tiksi.ohli.de.local. port: 4712 addresses: [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> 2001:4091:a243:827c:da3a:ddff:fe66:a33]
2024-08-28 20:02:28 INFO  Currently known entries:
2024-08-28 20:02:28 INFO    &{EVCC_HEMS_01 ff32ea1788126d3085a51d0ce3c98a5472db1cb3 EVCC-3531636530656434 /ship/ false EVCC EnergyManagementSystem HEMS tiksi.ohli.de.local. 4712 [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> 2001:4091:a243:827c:da3a:ddff:fe66:a33]}

also letting it run for some time did not change the logs.

The next nightly build will introduce a few updates:

IPv6 addresses will be used to establish a connection
It is again possible to assign a fixed IPv4 address if nothing else works

Has anyone verified the fix? Can this issue be closed?

I just upgraded my installation to the latest nightly container (sha256:a9dea5584fa4b0990205061fdd9b4575fbc69cd657d73f3bc973e3b7b2eb0407). It is working with an ip in the config. If I remove the IP, it is looking up the announced DNS entry but do not get a reply (and than it is failing). For me the solution with it IP in the config works. So, the ticket can be closed (for my part).

Vielen Dank für euren Support :-)


Reporting of counter items missing global context tags

Prometheus reporting of counter items are missing the global context tags which are applied to the counter itself.
Repro steps:

Create a counter

private readonly CounterOptions counterFooData = new CounterOptions
        {
            Name = "Foo"
        };

Increment an item within the counter

metrics.Measure.Counter.Increment(counterFooData , 1, "bar");

Observe that json metrics (http://appserver/metrics) look sane

 "counters": [
        {
          "name": "Foo|app:myapp,env:production,region:us-west-2",
          "unit": "none",
          "count": 2,
          "items": [
            {
              "count": 2,
              "item": "bar",
              "percent": 100.0
            }
          ],
          "tags": {
            "app": "myapp",
            "env": "production",
            "region": "us-west-2"
          }
        },

Observe that prometheus metrics (http://appserver/metrics-text) lack tags for individual items.

Actual result:
# HELP myapp_foo
# TYPE myapp_foo GAUGE
myapp_foo{app="myapp",env="production",region="us-west-2"} 7

myapp_foo{item="bar"} 7

Expected result:
# HELP myapp_foo
# TYPE myapp_foo GAUGE
myapp_foo{app="myapp",env="production",region="us-west-2"} 7

myapp_foo{item="bar",app="myapp",env="production",region="us-west-2"} 7

I wasn't sure if the problem here was that the Prometheus reporter wasn't aggregating the tags, or that the core app-metrics library should have done that ahead of time. But since the hierarchy is maintained in the json reporter, it seemed like a reporter problem.
Just to see, I was able to "fix" this by editing the MetricSetItemExtensions like so:
        public static Metric ToPrometheusMetric(this CounterValue.SetItem item, IEnumerable<LabelPair> parentPairs)
        {
            var result = new Metric
                         {
                             gauge = new Gauge
                                     {
                                         value = item.Count
                                     },
                             label = item.Tags.ToLabelPairs().Concat(parentPairs).ToList()
                         };

            return result;
        }

and then changing MetricValueSourceExtensions like this:
public static IEnumerable<Metric> ToPrometheusMetrics(this MeterValueSource metric)
        {
            var result = new List<Metric>
                         {
                             new Metric
                             {
                                 counter = new Counter
                                           {
                                               value = metric.Value.Count
                                           },
                                 label = metric.Tags.ToLabelPairs()
                             }
                         };

            if (metric.Value.Items?.Length > 0)
            {
                result.AddRange(metric.Value.Items.Select(x => x.ToPrometheusMetric(metric.Tags.ToLabelPairs())));
            }

            return result;
        }

But that's not very elegant, so I didn't want to put up a PR for it.

Thanks for providing details on your fix, will check it out


The ToolLLaMA repo

The thing about training a ToolLLaMA following these instructions: git clone git@github.com:thuqinyj16/ToolLLaMA.git
is it doesn't work, because https://github.com/thuqinyj16/ToolLLaMA doesn't exist.

Thanks for pointing that out. The related instructions in the readme have been revised.


Relax geojson crate version requirements

It looks like the tests pass with geojson 0.19.0, so it may be worth relaxing the requirements here. Should the new requirement be ">=0.16, <0.20" for now? Looks like the 0.20.0 release might be soon though and not sure if any of the changes there would be breaking
I haven't been active in the georust organization in a while, but interested in getting involved again! Wanted to check on this first though

If you've verified that all of those geojson versions are compatible with the topojson crate, then relaxing the requirements seems like an improvement. Ideally we would have CI test each version of the geojson crate in a test matrix, but not a blocker to moving forward with this

Sounds good to me, I'll put in a PR.
I'd be interested in building out the CI for this as well if that sounds worthwhile. I've worked more with GitHub Actions than Travis CI, and it looks like some of the more active georust crates are using GitHub Actions, but I'm open to either since it sounds like that's an active conversation

We don't have an official stance or recommendation between the two, though I also personally prefer GitHub Actions so that'd be my vote


Don't enhance test:prepare unless it exists

Don't fail build task when test:prepare isn't defined, as described here: https://github.com/rails/jsbundling-rails/issues/10

readme update made here to mirror https://github.com/rails/jsbundling-rails/pull/12


Change Insomnia variables to path parameters in openapi import

Feature Request
With the introduction of path parameters in version 8.6 it would be more fitting to convert path parameters in openapi format to insomnia path parameters with a colon, instead of insomnia variables with double curly brackets.
Current behavior
openapi:
/foo/{bar}
insomnia:
/foo/{{_.$1}}
Wanted behavior
openapi:
/foo/{bar}
insomnia:
/foo/:bar
Affected code
https://github.com/Kong/insomnia/blob/0ddbccfd3e8d010d3b769a8e562325a8e27ac006/packages/insomnia/src/utils/importers/importers/openapi-3.ts#L272-L278
If my proposal is welcomed, I will open a PR with the requested change myself.

Colon led parameters would not be interpolated by nunjucks rendering. It uses brackets to identify syntax to evaluate.

I'm not sure if I'm overlooking something here, but after changing this
path?.replace(VARIABLE_SEARCH_VALUE, '{{ _.$1 }}') ?? '';
to this
path?.replace(VARIABLE_SEARCH_VALUE, ':$1') ?? '';
it works:

A setting to control the behavior would probably be quite suitable, if some people prefer the old behavior, but in my use case it would be a welcomed change.

I guess it's possible the question is can you make url and headers editable without causing bugs or side effects.
@gatzjames what do you think?

Have you got any updates on this?

Any update here ? Just tried insomnia over postman and actually this seems to be the only thing that I use and is not in insomnia


Scroll letter list

Hi everyone. I can't see all the letters (... x, y, z) in the right letter list on devices with a small screen. I can't scroll the list either. How to can I solve this issue? Any ideas?

I found the solution. I need to add height: 'auto' to letterListContainerStyle. It has height: '100%' by default.


Movie Searching feature

Consider using Elastic search

dont need to use elasticSearch, just indexing in MongoDB is OK

done


Update active-directory-scim-provisioning.md

Updated to indicate support for third party OAuth token issuers

Hi @asmalser-msft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (asmalser). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Implement jump-to in search box on homepage

As opposed to jump to. The suggestions take you a results page instead of a specific ontology.

I'll be using this ticket to monitor the implementation of jumping to specific ontologies and entities from search suggestions. I will just create a new ticket for autocomplete suggestions in search.


Limit Token Usage Especially When Caught in Loop

Describe the bug
I really like your product, but the tokens got used up super fast and the ai was stuck in a loop trying to fix the same thing over and over again with the same methods, even though I was telling it what to do, it kept just using and reverting back to old code that we had already decided wasn't good anymore, so I don't know if I want to refund or just some credit just to try to fix it and maybe work with 1 of the developers to show you what's happening because I went through all the 10 million tokens like a day and II mean I got some progress, but I mean that's a lot to not have something have to pay another $30 when I could just use an open source.. Speaking of which, can we connect to open source LLMS like rock or whatever or use our tokens on other LMS? We already have subscriptions too and are paying for the API accents. Thank you.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-zxy1ss
Steps to reproduce
You can just look back through my most recent conversation history and see that even though I gave it the complete open AI real time API instructions, copy and paste it right from their page and the link for it to go itself is still kept using old code that wasn't referenced anywhere in the API guide. So I was really confused. Let's probably use the error and not knowing how to interact with it, but to use up ten million tokens that quickly and not solve anything and repeating the same stuff is kind of crazy
Expected behavior
To just fix the code, because I gave it the sample code to use. It was actually, it did a lot of things. There were a lot harder versus just changing the template api code to match my settings. It was kind of weird
Screen Recording / Screenshot
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

Appreciate the feedback! Agreed, when the LLM is stuck in a loop token usage can be excessive. Sometimes there are programming problems that are too complex for the AI to solve and manual intervention is required. This page here has a number of insights on ways to use tokens most efficiently. We appreciate your patience as improvements continue to be made!


build it no file

hello,when i run this colcon build --packages-select spl_lio_sam
the result is:
[0.162s] WARNING:colcon.colcon_core.package_selection:ignoring unknown package 'spl_lio_sam' in --packages-select
Summary: 0 packages finished [0.05s]
It says there is no file, what should I do next?

Did you start container according to the document and build inside container? and, notice to build in colcon workspace folder

是不是因为下面这两条命令使用的不对呀？
export DATA_DIR=/path/to/download/ros2bag/dir
./docker_run.sh -c /path/to/code/repo -d $DATA_DIR


feat: add support for per-template profiling #25

When used with a Nunjucks global that invokes the timer, we get the following result with this:
┌─────────────────────────────────────────┬──────────┬─────────────────┬─────────────────────────────────────────────────┐
│ Templates                               │        % │            Time │ Stats                                           │
│ /views/base.njk                         │ 1085.26% │ 23 sec, 377.0ms │ 22 calls, 1 sec, 987.0ms max, 1 sec, 62.6ms avg │
│ /views/partials/image-with-text.njk     │   21.24% │         457.5ms │ 40 calls, 19.5ms max, 11.4ms avg                │
│ /views/partials/centered-video.njk      │    4.07% │          87.6ms │ 8 calls, 16.9ms max, 10.9ms avg                 │
│ /views/partials/feature-touts.njk       │    3.34% │          72.0ms │ 4 calls, 21.2ms max, 18.0ms avg                 │
│ /views/partials/two-column-list.njk     │    1.44% │          30.9ms │ 2 calls, 18.5ms max, 15.5ms avg                 │
│ /views/partials/homepage-hero.njk       │    1.16% │          25.1ms │ 2 calls, 13.0ms max, 12.5ms avg                 │
│ /views/partials/secondary-hero.njk      │   12.44% │         268.0ms │ 14 calls, 80.5ms max, 19.1ms avg                │
│ /views/partials/image-with-colorbar.njk │    6.68% │         144.0ms │ 12 calls, 16.0ms max, 12.0ms avg                │
│ /views/partials/explore-cards.njk       │    5.75% │         123.8ms │ 14 calls, 13.6ms max, 8.8ms avg                 │
│ /views/partials/two-column-article.njk  │   19.51% │         420.2ms │ 34 calls, 28.0ms max, 12.4ms avg                │
│ /views/partials/header.njk              │    6.42% │         138.3ms │ 22 calls, 13.6ms max, 6.3ms avg                 │
│ /views/partials/primary-hero.njk        │    2.46% │          53.0ms │ 6 calls, 12.4ms max, 8.8ms avg                  │
│ /views/partials/two-column-text.njk     │    0.69% │          14.8ms │ 2 calls, 8.6ms max, 7.4ms avg                   │
└─────────────────────────────────────────┴──────────┴─────────────────┴─────────────────────────────────────────────────┘

@Zoramite - Do you know why the first row in this table shows 23 sec, 377.0ms for Time? The total build time in my test case is only 2 seconds so I don't know where that 23 seconds would be coming from.

The long time has to do with the 'async' nature of the rendering and that the time is a cumulative value.
It measures the full time for each template run from the beginning to the end of when the template render is complete, and the time is a sum so the 23s is roughly how much time it took for all of the rendering across those 22 calls, even though it was done async and only took about 2 s in real time.

Thanks :) That explains it.


Sample designing

Hi! I came around your package and I'm not fully sure if it does what I'm looking for. If no - you can treat my post as a slight suggestion. So, I'm looking for a library to design a sample for a survey which is going to be conducted (hence no existing data yet). I have desired proportions of key variables and would love to get the full sample design - i.e. all variables combined with proportions and counts. Let's say my goal is to get n = 2000 with the stratification of 3 key variables (gender, age, education) below:
expected_coverage: dict = {
    "woman": 0.64,
    "man": 0.36,
    "18-30": 0.20,
    "31-50": 0.50,
    "50+": 0.30,
    "lower": 0.30,
    "mid": 0.50,
    "higher": 0.20
}

As you can see I treat those variables separately. For example, I need to check what would be the proportion and counts of men, aged 18-30 with higher education (obviously each variable values should not be combined with themselves, within a group). Is there any way to get a sample design with samplics? You can also check my Stack Overflow post to read about the whole issue: SO post.
As a side note: I'm fully aware that this problem could be quite easily solved using random/numpy/pandas libraries but anyways I'm curious if samplics could offer more convenient solution. Additionally, a comprehensive and reliable tool to complex sample designs would be priceless.

Hi! I do not fully understand your question. Let me know if this is what you want to achieve. You have a total sample size of 2,000 and you want to allocate it across the 18 strata formed by gender, age, and education? If so, do you want allocate proportionally or else?


Options to schedule Open BOPIS Order, Ready to pick BOPIS order and open shipping order notifications job from fulfillment/notifications section

What is the motivation for adding/enhancing this feature?
Options to schedule Open BOPIS Order, Ready to pick BOPIS order and open shipping order notifications job from fulfillment/notifications section. This will help to control frequency of each type of notifications separately.
What are the acceptance criteria?

[ ] ...

Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Additional information

Verified and working fine in release v2.23.2. Hence, closing it.


Add jenkins user-ID in submitter

Codecov Report

Merging #589 (8949ff7) into master (1a827ac) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #589   +/-   ##
=======================================
  Coverage   67.91%   67.91%
=======================================
  Files          99       99
  Lines        6172     6172
  Branches     1066     1066
=======================================
  Hits         4192     4192
  Misses       1980     1980

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 1a827ac...8949ff7. Read the comment docs.


Add authentication and port to cassandra tool

Coverage decreased (-0.02%) to 67.377% when pulling d3863f4706e733a49b1f2992c2a3a62173a8d38d on auth into 39ddbc0fe91c79ed686a2c14f11b586da8e0bac4 on master.

Coverage decreased (-0.1%) to 67.251% when pulling d3863f4706e733a49b1f2992c2a3a62173a8d38d on auth into 39ddbc0fe91c79ed686a2c14f11b586da8e0bac4 on master.


issue88 add amount field in UI

add amount field in UI

Mingxi, I might need to change a few things for the purchase endpoint from the backend so I will do a PR and then you can make the changes accordingly. Sorry for the inconvenience.

Codecov Report

Merging #89 (6ec27ef) into master (5d0656a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #89   +/-   ##
=======================================
  Coverage   99.17%   99.17%
=======================================
  Files           2        2
  Lines         242      242
=======================================
  Hits          240      240
  Misses          2        2

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 5d0656a...6ec27ef. Read the comment docs.

IBM Cloud toolchain: Delivery Pipeline deployed products to dev, including commit 1729ea61e024ede18456e8a5d7dfec4fce37161c

IBM Cloud toolchain: Delivery Pipeline deployed products to prod, including commit 1729ea61e024ede18456e8a5d7dfec4fce37161c


Could not determine the dependencies of task ':app:mergeDebugAssets'.

Version of react-native-iap
react-native-iap: 7.5.5
Version of react-native
react-native: 0.66.4
Platforms you faced the error (IOS or Android or both?)
Android
Tested environment (Emulator? Real Device?)
Emulator
Steps to reproduce the behavior
Install react-native-iap and run it on android emulator
Error
Could not determine the dependencies of task ':app:mergeDebugAssets'.
> Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
   > Could not resolve project :react-native-iap.
     Required by:
         project :app
      > The consumer was configured to find a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug'. However we cannot choose between the following variants of project :react-native-iap:
          - amazonDebugRuntimeElements
          - playDebugRuntimeElements
        All of them match the consumer attributes:
          - Variant 'amazonDebugRuntimeElements' capability test:react-native-iap:unspecified declares a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug':
              - Unmatched attributes:
                  - Provides attribute 'com.android.build.api.attributes.VariantAttr' with value 'amazonDebug' but the consumer didn't ask for it
                  - Provides attribute 'store' with value 'amazon' but the consumer didn't ask for it
          - Variant 'playDebugRuntimeElements' capability test:react-native-iap:unspecified declares a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug':
              - Unmatched attributes:
                  - Provides attribute 'com.android.build.api.attributes.VariantAttr' with value 'playDebug' but the consumer didn't ask for it
                  - Provides attribute 'store' with value 'play' but the consumer didn't ask for it
        The following variants were also considered but didn't match the requested attributes:
          - Variant 'amazonDebugApiElements' capability test:react-native-iap:unspecified declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug':
              - Incompatible because this component declares an API of a component and the consumer needed a runtime of a component
          - Variant 'amazonReleaseApiElements' capability test:react-native-iap:unspecified:
              - Incompatible because this component declares an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug'
          - Variant 'amazonReleaseRuntimeElements' capability test:react-native-iap:unspecified declares a runtime of a component:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug'
          - Variant 'playDebugApiElements' capability test:react-native-iap:unspecified declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug':
              - Incompatible because this component declares an API of a component and the consumer needed a runtime of a component
          - Variant 'playReleaseApiElements' capability test:react-native-iap:unspecified:
              - Incompatible because this component declares an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug'
          - Variant 'playReleaseRuntimeElements' capability test:react-native-iap:unspecified declares a runtime of a component:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug'
`

Did you fin a solution ? same issue :(

@simonemarinelli
I've found, you need to follow this documentation :
https://react-native-iap.dooboolab.com/docs/installing/
For my case, I just need to add this line inside the defaultConfig section in android/app/build.gradle :
missingDimensionStrategy 'store', 'play'

@RimApp
It worked after adding missingDimensionStrategy 'store', 'play' and ./gradlew clean


Create auto-comments.yml

I am solving THis  Isuue :https://github.com/subhashis2204/project-annapurna/issues/59
I have created a Workflow that automatically commits when an issue is opened, a pull request is created, an issue is closed, or an issue is assigned or unassigned.
too run this workflow you need to enable the following permission

@subhashis2204 please add gssoc23 label and also level label

Hey @Nishitbaria I am facing an error while merging this

Can you suggest what might be wrong

you have to give some permission on the repository setting

@Nishitbaria  all the permission are granted

@subhashis2204 you have to give some permission on the repository setting

can you show me what the error is coming

@subhashis2204 you have to give some permission on the repository setting

@subhashis2204 can you show me what error is coming? show me logs

Yes I also noticed it now. Thanks @Nishitbaria

Yes I also noticed it now. Thanks @Nishitbaria

@subhashis2204   do you need other workflows which enhances your project ... :)

Umm .. I need a specific workflow for auto deploying any changes in code during a pull request. I also raised an issue regarding this. You can work on this issue. It is highlighted at the top of the issue page.

Hey @subhashis2204  I have workflow but you have to enter a secret aws key in your repo .  so i provide code using your API key with this code :
name: Deploy PR

on:
  pull_request:
    types:
      - opened
      - synchronize
      - reopened

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Set up Node.js
        uses: actions/setup-node@v2
        with:
          node-version: 14

      - name: Install dependencies
        run: npm install

      - name: Build and test
        run: npm run build && npm run test

      - name: Deploy PR
        env:
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        run: |
          aws configure set aws_access_key_id $AWS_ACCESS_KEY_ID
          aws configure set aws_secret_access_key $AWS_SECRET_ACCESS_KEY
          aws elasticbeanstalk create-application-version --application-name MyApp --version-label pr-${{ github.event.pull_request.number }} --description "PR Deployment" --source-bundle S3Bucket=my-bucket,S3Key=pr-${{ github.event.pull_request.number }}.zip
          aws elasticbeanstalk update-environment --environment-name MyEnvironment --version-label pr-${{ github.event.pull_request.number }}

Great !!! but there is a slight problem. I would like to use Azure for this. I don't have a subscription for AWS.

@subhashis2204  you can also try this  : )
name: Deploy PR

on:
  pull_request:
    types:
      - opened
      - synchronize
      - reopened

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Set up Node.js
        uses: actions/setup-node@v2
        with:
          node-version: 14

      - name: Install dependencies
        run: npm install

      - name: Build and test
        run: npm run build && npm run test

      - name: Deploy PR
        uses: azure/login@v1
        with:
          creds: ${{ secrets.AZURE_CREDENTIALS }}

      - name: Set Azure subscription
        run: az account set --subscription "${{ secrets.AZURE_SUBSCRIPTION_ID }}"

      - name: Create resource group
        run: az group create --name MyResourceGroup --location "eastus"

      - name: Deploy to Azure Web App
        run: |
          az webapp deployment source config-zip --resource-group MyResourceGroup --name MyWebApp --src pr-${{ github.event.pull_request.number }}.zip --subscription "${{ secrets.AZURE_SUBSCRIPTION_ID }}"


Fix annotated_types.MaxLen validator for custom sequence types

Change Summary
Makes the validator function used for annotated_types.MaxLen with custom sequences use an inclusive upper bound.
Related issue number
fix #6808
Checklist

[X] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[X] Documentation reflects the changes where applicable
[X] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @dmontagu

please review
didn't add any unit tests as I'm not sure where they would go, can't find any similar ones.

Thanks @ImogenBits for this patch 👍

didn't add any unit tests as I'm not sure where they would go, can't find any similar ones.

You can adjust the test in https://github.com/pydantic/pydantic/blob/53207640a308806373bdeb1f4dea432f9c005ce2/tests/test_types.py#L5379
please update

please review


Update version of @angular/cli

We have a somewhat old version of @angular/cli specified in packages.json, and that should be updated.

Fixed!


DRPolicy: Add CEL and remove webhook

Remove DRPolicy Webhook and add CEL immutability validation for DRPolicy

Tested the DRPolicy PR out and here is what I see...
Initial DRPolicy created on a kind cluster extended with the CRD from the PR:
$ kubectl get drpolicy -A -o yaml
apiVersion: v1
items:
- apiVersion: ramendr.openshift.io/v1alpha1
  kind: DRPolicy
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"ramendr.openshift.io/v1alpha1","kind":"DRPolicy","metadata":{"annotations":{},"name":"drpolicy-sample"},"spec":{"drClusters":["east","west"],"schedulingInterval":"5m"}}
    creationTimestamp: "2024-03-12T22:19:00Z"
    generation: 1
    name: drpolicy-sample
    resourceVersion: "950"
    uid: e59bd15b-5178-476f-bbe7-de8af997831d
  spec:
    drClusters:
    - east
    - west
    schedulingInterval: 5m

Look at last-applied-configuration, does not have replicationClassSelector
Now changed the DRPolicy YAML to add a replicationClassSelector and applied it, and it was successful, and here is the get after that:
$ kubectl apply -f ./drp.yaml
drpolicy.ramendr.openshift.io/drpolicy-sample configured

$ kubectl get drpolicy -A -o yaml
apiVersion: v1
items:
- apiVersion: ramendr.openshift.io/v1alpha1
  kind: DRPolicy
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"ramendr.openshift.io/v1alpha1","kind":"DRPolicy","metadata":{"annotations":{},"name":"drpolicy-sample"},"spec":{"drClusters":["east","west"],"replicationClassSelector":{"matchLabels":{"class":"ramen"}},"schedulingInterval":"5m"}}
    creationTimestamp: "2024-03-12T22:19:00Z"
    generation: 2
    name: drpolicy-sample
    resourceVersion: "967"
    uid: e59bd15b-5178-476f-bbe7-de8af997831d
  spec:
    drClusters:
    - east
    - west
    replicationClassSelector:
      matchLabels:
        class: ramen
    schedulingInterval: 5m
kind: List
metadata:
  resourceVersion: ""

IOW, if we start wit a YAML that has no replicationClassSelector, and then add it later then it is allowed, which we should not allow.
Another test I did was to create a policy with empty list of DRClusters (as below) and it passed. This is a new test case though as older code also allowed this to pass through:
$ kubectl get drpolicy -A -o yaml
apiVersion: v1
items:
- apiVersion: ramendr.openshift.io/v1alpha1
  kind: DRPolicy
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"ramendr.openshift.io/v1alpha1","kind":"DRPolicy","metadata":{"annotations":{},"name":"drpolicy-sample"},"spec":{"drClusters":[],"replicationClassSelector":{"matchLabels":{"class":"ramen"}},"schedulingInterval":"5m"}}
    creationTimestamp: "2024-03-12T22:22:18Z"
    generation: 1
    name: drpolicy-sample
    resourceVersion: "1208"
    uid: 6755a4cb-cdfc-42f2-bb2e-e6a86fee267f
  spec:
    drClusters: []
    replicationClassSelector:
      matchLabels:
        class: ramen
    schedulingInterval: 5m
kind: List
metadata:
  resourceVersion: ""

Overall I think the CEL rules should be amended as below, such that we do not allow the above modifications:
diff --git a/api/v1alpha1/drpolicy_types.go b/api/v1alpha1/drpolicy_types.go
index c5fecea..ff7e80b 100644
--- a/api/v1alpha1/drpolicy_types.go
+++ b/api/v1alpha1/drpolicy_types.go
@@ -8,11 +8,7 @@ import (
 )

 // DRPolicySpec defines the desired state of DRPolicy
-// +kubebuilder:validation:XValidation:rule="!has(oldSelf.replicationClassSelector) || has(self.replicationClassSelector)", message="replicationClassSelector is required once set"
-// +kubebuilder:validation:XValidation:rule="!has(oldSelf.volumeSnapshotClassSelector) || has(self.volumeSnapshotClassSelector)", message="volumeSnapshotClassSelector is required once set"
 type DRPolicySpec struct {
-	// Important: Run "make" to regenerate code after modifying this file
-
 	// scheduling Interval for replicating Persistent Volume
 	// data to a peer cluster. Interval is typically in the
 	// form <num><m,h,d>. Here <num> is a number, 'm' means
@@ -25,19 +21,20 @@ type DRPolicySpec struct {
 	// Label selector to identify all the VolumeReplicationClasses.
 	// This selector is assumed to be the same for all subscriptions that
 	// need DR protection. It will be passed in to the VRG when it is created
-	// +kubebuilder:validation:Optional
+	// +kubebuilder:validation:Required
 	// +kubebuilder:validation:XValidation:rule="self == oldSelf", message="replicationClassSelector is immutable"
-	ReplicationClassSelector metav1.LabelSelector `json:"replicationClassSelector,omitempty"`
+	ReplicationClassSelector metav1.LabelSelector `json:"replicationClassSelector"`

 	// Label selector to identify all the VolumeSnapshotClasses.
 	// This selector is assumed to be the same for all subscriptions that
 	// need DR protection. It will be passed in to the VRG when it is created
-	// +kubebuilder:validation:Optional
+	// +kubebuilder:validation:Required
 	// +kubebuilder:validation:XValidation:rule="self == oldSelf", message="volumeSnapshotClassSelector is immutable"
-	VolumeSnapshotClassSelector metav1.LabelSelector `json:"volumeSnapshotClassSelector,omitempty"`
+	VolumeSnapshotClassSelector metav1.LabelSelector `json:"volumeSnapshotClassSelector"`

 	// List of DRCluster resources that are governed by this policy
 	// +kubebuilder:validation:Required
+	// +kubebuilder:validation:XValidation:rule="size(self) == 2", message="drClusters requires a list of 2 clusters"
 	// +kubebuilder:validation:XValidation:rule="self == oldSelf", message="drClusters is immutable"
 	DRClusters []string `json:"drClusters"`
 }

For the tests, unfortunately as it uses a go struct for the DRPolicy, it is able to write out initial configuration with empty values, and so when we use YAML this is working differently.
I am not sure yet how to test with YAML and envtest, so that is unfortunate. We could test it in a kind cluster though and ensure that CEL rules are adhered to. I just used hack/setup-kind-cluster.sh to get a kind cluster, extended the CRD for DRPolicy and then tested with various YAMLs as above.

Thanks for the detail input. I have pushed the chages.


Checksum address according to Wanchain EIP55 speck

PR aims to solve issue when Wanchain transfers direction incorrectly displayed in Atlas response

What about not wanchain responses? What was the issue with it?

What about not wanchain responses? What was the issue with it?

Amount all ETH forks only Wanchain generates checksum differently, see comment above EIP55ChecksumWanchain

Can we verify that other forks will not have any problems with this normalization?

Can we verify that other forks will not have any problems with this normalization?

added test


implement dispose (needs feedback)

Bun appears to run GC twice; if you uncomment the logged output in destroyTensor (only called @ Garbage Collection), the output is logged multiple times per pointer).
This causes the test to segfault as first GC, bun finds the pointer in alreadyDestroyed & removes the pointer from the set. 2nd Garbage Collection, destroyTensor fails to locate the pointer in alreadyDestroyed (as it was just cleared @ the prev Garbage Collection run).
It seems like there might be a bug in Bun, working on a repro to file an issue w Bun as this is likely blocking.
Once we resolve the above, this will partially implement #50 (still want to implement some equivalent to TFJS tidy in a separate PR).

S/o @jacobkahn & @bwasti for getting releaseAdapterUnsafe merged into Flashlight quickly! Tests are passing, but we'll still need to handle preventing the reuse of a tensor after dispose has been called on it.
The simplest solution is to add is_disposed boolean value to Tensor class, which we flag after dispose has been called; we'd need to then do the following in any Tensor Operation/class method that would throw an error:
if (this.is_disposed) throw new Error(`cannot call "op_name" on disposed tensor; ${this.toString})

I tested and this approach seems to work locally; however obviously it requires hardcoding checks/throwing, so would love feedback to see if we can't brainstorm a smarter approach to handling this!

@cryptodeal any harm in just letting Flashlight throw to avoid the extra check? Or is it seg faulting?

@cryptodeal any harm in just letting Flashlight throw to avoid the extra check? Or is it seg faulting?

I wish, that would be convenient, but it Segfaults unfortunately.

Here's what I think a utility function intended to handle throwing this error might look like:
export const _handle_disposed = (t: Tensor | Tensor[]) => {
  if (Array.isArray(t)) {
    const test = t.filter(tensor => tensor.is_disposed)
    if (test.length) {
      throw new Error(`Cannot operate on previously disposed Tensor(s): ${test.map(t => t.toString()).join(', ')}`)
    }
  } else {
    if (t.is_disposed) throw new Error(`Cannot operate on previously disposed Tensor: ${t.toString()}`)
  }
}

This could be easily added as a check at the start of all relevant JS methods (and easily added to the programmatically generated JS code w/ minimal added work to maintain going forward.


mean() with option na_rm=False does not work

Please, consider the MWE below:
from datar.all import *
import numpy as np
import pandas as pd

df = pd.DataFrame({
    'id': ['A']*2 + ['B']*2,
    'date':['2020-01-01','2020-02-01']*2,
    'value': [2,np.nan,3,3]
})
df

df_mean = (df
    >> group_by(f.id)
    >> summarize(
        # value_np_nanmean = np.nanmean(f.value),
        value_np_mean = np.mean(f.value),
        value_datar_mean = mean(f.value, na_rm=False)
    )
)
df_mean

In df_mean, the first observation of value_np_mean and value_datar_mean  should be NAN instead of 2.
This is the same issue found in Pandas, which discards NAN / None observations automatically during calculations.
The only workaround I found is this: https://stackoverflow.com/questions/54106112/pandas-groupby-mean-not-ignoring-nans/54106520

pandas ignores NAs anyway in a groupby -> agg chain:
>>> df.groupby('id').agg(np.mean)
       value

id <float64>
A        2.0
B        3.0
>>> df.groupby('id').agg(np.nanmean)
       value

id <float64>
A        2.0
B        3.0

Actually, the NAs in the first case should not be ignored, but pandas did that.
I think this is also related:
https://github.com/pandas-dev/pandas/issues/15675
https://github.com/pandas-dev/pandas/issues/15674
https://github.com/pandas-dev/pandas/issues/20824
The current solution for datar is that, don't try to optimize it using agg when na_rm is False.

Hey @pwwang , thanks for the very good feedback as always.
Yes, it is the standard behavior of Pandas, which is wrong and dreadful in my opinion...
Since datar uses Pandas under the hood, I suppose it will be difficult for you to solve this issue, right?
Python would be much better if someday in the future https://github.com/h2oai/datatable could replace Pandas as the default data library

It's fixed by https://github.com/pwwang/datar/commit/ba8b3e712a3dc4dfc9a0dae43e396aa94aa774e7, and will be released in the next version.
It's just a matter of how we want pandas to do it. If we do it like:
>>> df.groupby('id').agg(value=('value', lambda x: mean(x)))
       value

id <float64>
A        NaN
B        3.0

But then we lost pandas' optimization on mean. With this fix, if people still want to take advantage of the optimization, one could do:
df >> group_by(f.id) >> summarise(m=mean(f.value, na_rm=True))
# since pandas loses NAs anyway

This needs to be documented, for sure.
For the datatable backend, I need to dive into it to see we can/need to replace pandas with it.

Great man! Thank you

Hey @pwwang , I believe this issue regressed.
In the latest datar version, this
import datar.all as d
from datar import f
import numpy as np
import pandas as pd

df = pd.DataFrame({
    'id': ['A']*2 + ['B']*2,
    'date':['2020-01-01','2020-02-01']*2,
    'value': [2,np.nan,3,3]
})

df >> d.group_by(f.id) >> d.summarise(m=d.mean(f.value, na_rm=True))

returns:
TypeError: mean() got an unexpected keyword argument 'na_rm'

Also, this used to work:
df_mean = (df
    >> d.group_by(f.id)
    >> d.summarize(
        value_np_nanmean = np.nanmean(f.value),
        value_np_mean = np.mean(f.value),
    )
)

But now it throws these errors, respectively:
ValueError: invalid __array_struct__
TypeError: GroupBy.mean() got an unexpected keyword argument 'axis'

It's all because GroupBy.mean() and alike don't have skipna argument and pandas won't keep NAs any way for groupby data.
See: https://pandas.pydata.org/docs/reference/api/pandas.core.groupby.DataFrameGroupBy.mean.html
Let's say we have gf = df >> d.group_by(f.id). The NAs are ignored anyway even when we do gf.value.agg(np.nanmean) (ridicules, huh?)
In the old days, datar uses apply on groupby data, which makes it easier to customize but sacrifices performance. Now mean(f.value) is actually transformed into gf.value.agg('mean') to maintain the performance, with the sacrifce of functionality (keeping NAs, for example)
Now, with datar v0.15.3, value_np_nanmean = np.nanmean(f.value) should work, but keep in mind that it is implemented with apply, performance may be compromised.

We should be able to support na_rm argument, and just need to expand:

func_bootstrap(mean, func=np.mean, kind="agg")

https://github.com/pwwang/datar-pandas/blob/779a272a15c0d82e37e9025312f45836ccb10210/datar_pandas/api/base/arithm.py#L63
into functions on different types of objects (i.e. Series, SeriousGroupBy) (The func_bootstrap just does it automatically).
I am just short of time to do that.
Pandas3 will require pyarrow as the backend, which supports Nullable datatypes. I believe this won't be a problem then.

The NAs are ignored anyway even when we do gf.value.agg(np.nanmean) (ridicules, huh?)

@pwwang , Yes, man, this is ridiculous, another reason why I hate Pandas. tidyverse design is on a completely different level, that's a work of art software, and that's why a package like datar is so important in python.

I am just short of time to do that.

No problem.

Pandas3 will require pyarrow as the backend, which supports Nullable datatypes. I believe this won't be a problem then.

Yes, let's see if it will be finally solved.
Thank you


Missing doc comments in .d.ts file

Many doc comments aren't copied to the .d.ts file, eg. enums, enum items, structs.
wasm-bindgen = "0.2.59"
build: wasm-pack build
use wasm_bindgen::prelude::*;

/// This is MyStruct
#[wasm_bindgen]
pub struct MyStruct {
    /// This is a field
    pub field1: u32,
}

#[wasm_bindgen]
impl MyStruct {
    /// This is the constructor
    #[wasm_bindgen(constructor)]
    pub fn new(field1: u32) -> Self {
        Self { field1 }
    }

    /// This is a method
    pub fn meth(&self) {}

    /// This is a getter
    #[wasm_bindgen(getter)]
    pub fn value(&self) -> bool {
        true
    }

    /// This is a setter
    #[wasm_bindgen(setter)]
    pub fn set_value(&mut self, value: bool) {}
}

/// This is MyEnum
#[wasm_bindgen]
pub enum MyEnum {
    /// This is Zero
    Zero,
    /// This is One
    One,
}

Note all the missing comments. I expect the getter's docs are copied if there's a getter, else the setters docs are copied.

no enum items docs
no getter docs
no field docs
no struct docs
free() is auto-generated, maybe add some docs there too?

/* tslint:disable */
/* eslint-disable */
/**
* This is MyEnum
*/
export enum MyEnum {
  Zero,
  One,
}
export class MyStruct {
  free(): void;
/**
* This is the constructor
* @param {number} field1
*/
  constructor(field1: number);
/**
* This is a method
*/
  meth(): void;
  field1: number;
  value: boolean;
}

Thanks for the great test case here! Not everything has the docs plumbed all the way through (it seems like we're definitely inconsistent!), but definitely would be a good bug fix to treat docs consistently in all these locations.


Missing Migration-- Error 1054: Unknown column 'ref' in 'field list'

Gitea version (or commit ref): bd1bf2a0720b771cfe2fac3fef0fd9edd68f6317
Git version: 2.7.4
Operating system: ubuntu bionic
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x ] Not relevant

Log gist:

Description
missing migration..
2018/09/06 11:09:42 [I] Migration: add is_fsck_enabled column for repos
2018/09/06 11:09:42 [I] Migration: add size column for attachments
2018/09/06 11:09:42 [I] Migration: add last used passcode column for TOTP
2018/09/06 11:09:42 [I] Migration: add language column for user setting
2018/09/06 11:09:42 [I] Migration: add multiple assignees
2018/09/06 11:09:43 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Error 1054: Unknown column 'ref' in 'field list'
Screenshots

@psywhale which version did you upgrade from?

1.0.2 -> 1.5 -> master

1.5 also had a migration error with "is_fsck_enabled" column missing but master fixed that.

I am trying to migrate from gogs and the documentation said to use a 1.0.X version. Which worked great. Then I tried to upgrade to 1.5 and got migration errors

something to do with this? https://github.com/go-gitea/gitea/blob/e95417ea2c0d9b5e0be0c0f7bf82eabb40919c33/models/migrations/v64.go#L29

my issue table as it now stands:
mysql> describe issue;
+---------------+--------------+------+-----+---------+----------------+
| Field         | Type         | Null | Key | Default | Extra          |
+---------------+--------------+------+-----+---------+----------------+
| id            | bigint(20)   | NO   | PRI | NULL    | auto_increment |
| repo_id       | bigint(20)   | YES  |     | NULL    |                |
| index         | bigint(20)   | YES  |     | NULL    |                |
| poster_id     | bigint(20)   | YES  |     | NULL    |                |
| name          | varchar(255) | YES  |     | NULL    |                |
| content       | text         | YES  |     | NULL    |                |
| milestone_id  | bigint(20)   | YES  |     | NULL    |                |
| priority      | int(11)      | YES  |     | NULL    |                |
| assignee_id   | bigint(20)   | YES  |     | NULL    |                |
| is_closed     | tinyint(1)   | YES  |     | NULL    |                |
| is_pull       | tinyint(1)   | YES  |     | NULL    |                |
| num_comments  | int(11)      | YES  |     | NULL    |                |
| deadline_unix | bigint(20)   | YES  |     | NULL    |                |
| created_unix  | bigint(20)   | YES  |     | NULL    |                |
| updated_unix  | bigint(20)   | YES  |     | NULL    |                |
| closed_unix   | bigint(20)   | YES  | MUL | NULL    |                |
+---------------+--------------+------+-----+---------+----------------+

alter table issue add column ref varchar(255) after num_comments;
fixed this issue but now another migration error see #4883


updating brazilian leagues and teams of first and seconde division

starting my work for brasil teams, leagues and standings
I hope to help a lot :)

You're more than welcome. Looks great. Thanks. Obrigado.

Note: In the teams file I added comments for (MS) (RG) etc. otherwise the lines will not parse (for SQL processing).

Ok, i'll take care about it next time

No worries. Thanks for contributing. Cheers.

@rlpereira  Welcome. Added you to the team - the github invitation (by email) is on its way. On the peoples page you can make your membership public (or private is the default). Cheers.

@rlpereira   Something different - for you information - A plan is to import and (re)use the RSSSF datasets from brazil - still kind of early. You can see examples here at the rsssf brazil repo. Cheers..

Ok, maybe I can help you to import this.
Btw, i saw different formats to describe teams in txt  files, in br-brazil, for example, we use
single line but in the england repository you use [team] new line then the info about the team.
What kind should I use on br repo? is there someone "more" correct than another one?

For the import that needs work in Ruby for the parser etc.  Will try to get a basic version wrapped up (it's still work-in-progress).
About the teams format - there is no "correct" format. The idea is simple:
If you add only basic info e.g. key and name plus maybe alternative names and three letter abbrevation than the one line version is great  (it's "standard" csv)
The second format is multi-line and allows you to add more info e.g.
the address of the team, wikipedia url, team url etc.

@rlpereira  Hello, as always thanks for all the updates. Just to let you know I will be offsite some days and will try to get to add the setup and parser changes done sometime next week. Thanks for the patience. Cheers.

@geraldb np, I'll try add results for Libertadores Cup next week. Cheers


Use NetCDF variable's chunks on load

Get chunks from a NetCDF file when loading the file as Iris cubes. In (limited) testing of a large, compressed NetCDF file this had a significant impact on load speed:
Load speed, chunks not used: 254.186s
Load speed, chunks used: 20.193s

👍 - with some light tests and a what's new

I have now added some tests and a whatsnew entry. Think this is good to go now!

bump for merge!


Add userId param

For server-side

This isn't something we want. Closing but feel free to add more comments in reasoning and we're happy to discuss.


Front-End Web Dev: Form Validation

I would like to contribute to Form Validation in HTML and JS

I want to make audio content on this, May I ?
Lavleen Agrawal (Batch 18 - Frontend)

Hi sir! I would love to contribute on this topic, can you please assign it to me? Debarati Ghatak, Frontend Batch 5

would like to contribute on this topic and prepare a well structure documentation.Can u assign it to me?
Ayushi Chauhan
Batch-01

So, while working on various types of forms I accurately know how to work on form and form validators. I believe that I have sufficient knowledge to work on this issue and complete it beforehand. I can prepare documentation for it.

/assign documentation


Possible missing LISENCE for the website.

In an assumption that the website will run under the same license as the patch repo.
Ill add a PR for this change just in case it is needed and wanted.

Merged https://github.com/Starfield-Community-Patch/Website/pull/6


Modularize grunt tasks

I have moved all the configs to /tasks/options and the custom vagrant tasks to /tasks
This is an implementation of a solution for issue #36 which I just opened for discussion on this topic.
I based this system on http://www.thomasboyt.com/2013/09/01/maintainable-grunt.html I believe it will work as it did before and I have tested locally but can't see any problems yet.

Thanks @EHLOVader! This could go a long way towards long term maintainability. I've been heads down on a few other projects and haven't gotten back to do much testing. I would love @tddewey to take a peak if he has any time. I would want to be careful merging something like this in so we know it's stable.

bump
Hope your other projects have been going well. I am looking to move forward with plans that depend on this and #38


Add example of starting controllers with launch files

Rewrite of #66

The diff view is broken here, this PR actually only adds literal c in line 167. The rest is just restructuring of the section.
I found the old PR interesting and merged it to the new structure. I thought it could be helpful for switching controller from some external interface like a GUI, or probably shows how to integrate controller_manager.launch_utils to a python state machine script. But because it only loads the controller but does not activate it, I agree that the benefit of this launch file is close to zero.

I don't have any hard feelings about this PR. If you think this is not adding any value to the demos but only making them more verbose -> I'll close it.


antimage_female_debut has incorrectly positioned hair in glTF export

Describe the bug

Reference file in a Valve game
Dota 2, antimage_female_debut

It's same in dota tools.


Add packages into requirements.txt needed by G2Tools

See https://github.com/Senzing/g2-python/issues/125

Pull requests:

https://github.com/Senzing/docker-senzing-console/pull/52


Add "file_env" support, especially for Docker secrets

This adds explicit support for the following:

POSTGRES_DB_FILE
POSTGRES_INITDB_ARGS_FILE
POSTGRES_PASSWORD_FILE
POSTGRES_USER_FILE

See also https://github.com/docker-library/wordpress/pull/186

cc @cyli @mstanleyjones


chore: update the default description for tia

Overview
minor PR to update the description of tia
Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #2736 (d1b66a6) into main (6192a5a) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main    #2736   +/-   ##
=======================================
  Coverage   19.62%   19.62%
=======================================
  Files         139      139
  Lines       16999    16999
=======================================
  Hits         3336     3336
  Misses      13341    13341
  Partials      322      322

Files
Coverage Δ

app/default_overrides.go
19.04% <0.00%> (ø)


[[FIX]] allow trailing comma in ArrayBindingPattern

Also, disallow commas after rest elements in ArrayBindingPattern.

Coverage decreased (-0.09%) to 96.21% when pulling 0f187e0178f990b4ec8f516b004aca0da780496a on caitp:destruct into 983fc8de62dc826670b7af8e64fd67de0a4d1a27 on jshint:master.

Coverage decreased (-0.09%) to 96.21% when pulling 6887b3a8c69214afd51bc1243c89a884a1ea3c9e on caitp:destruct into 983fc8de62dc826670b7af8e64fd67de0a4d1a27 on jshint:master.

Coverage decreased (-0.04%) to 96.27% when pulling 066989b7d39980a108ca381aa74f659f84c84686 on caitp:destruct into 983fc8de62dc826670b7af8e64fd67de0a4d1a27 on jshint:master.

Coverage decreased (-0.09%) to 96.21% when pulling 6a21a8762033ed8d5adfa9fab90452ddf4ba59b0 on caitp:destruct into 983fc8de62dc826670b7af8e64fd67de0a4d1a27 on jshint:master.

Coverage decreased (-0.09%) to 96.21% when pulling 95ca7c635b6cb17cee87529782cb283d043ddf18 on caitp:destruct into 983fc8de62dc826670b7af8e64fd67de0a4d1a27 on jshint:master.

Coverage decreased (-0.09%) to 96.21% when pulling 0c3959a8dec9483e1bc5326906f3cd3750b0c5ac on caitp:destruct into 983fc8de62dc826670b7af8e64fd67de0a4d1a27 on jshint:master.

I read right past this earlier today:

As ridiculous as 4 releases in two days is, I think this is important to have in the wild.

yup, me too... that last opt was invisible :(

I'm going to try to fix the other issue in #2223 first, if you want to wait a few hours

Coverage decreased (-0.04%) to 96.27% when pulling b4f1795b61285c8f786663895ec0029b999a06b5 on caitp:destruct into 162dee6d4d3f78ec0e0a1d3e2232454de087cbbc on jshint:master.

fixup removes handling of "..." in advance(), since it's handled specially everywhere that it's valid.

Coverage increased (+0.01%) to 96.32% when pulling a0fce6549d674dde5d51a596c94b65d742b591fb on caitp:destruct into 162dee6d4d3f78ec0e0a1d3e2232454de087cbbc on jshint:master.


Connection-Pool issue when database restarts

I'm not sure this issue has been already reported or not. Issue is
My web application is already running. Connection pool is initialized only once in a static constructor. It works fine and I can connect to database and make queries.
If I restart orient-db server, then all queries break with IOException "Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host."
If I try to drop connection pool in case of IO error again i get same error. So, I have to restart web server to make it work again.
As per my investigation I get error in Connection.ExecuteOperation method at code : _networkStream.Flush();
Thanks

@prah-net ,
Could you please check this is latest code from master branch.
@poindextrose Thank you for test case

It is working.
Thank you @GoorMoon and @poindextrose
Prahlad