RTSP not working using FFmpeg

Somehow i can't get RTSP working with FFmpeg.
See debug log down below:
[10/27/2020, 13:08:36] [Camera FFmpeg] [Küche] Snapshot requested: 480 x 270
[10/27/2020, 13:08:36] [Camera FFmpeg] [Küche] Sending snapshot: 480 x 270
[10/27/2020, 13:08:36] [Camera FFmpeg] [Küche] Snapshot command: /usr/lib/node_modules/homebridge-camera-ffmpeg/node_modules/ffmpeg-for-homebridge/ffmpeg -i http://<IP_ADDRESS>:8080/cgi-bin/snapshot.sh  -frames:v 1 -filter:v scale='min(480,iw)':'min(270,ih)':force_original_aspect_ratio=decrease,scale=trunc(iw/2)*2:trunc(ih/2)*2 -f image2 -
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] Video stream requested: 1280 x 720, 30 fps, 299 kbps
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] Starting video stream: 1280 x 720, 30 fps, 299 kbps
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] Stream command: /usr/lib/node_modules/homebridge-camera-ffmpeg/node_modules/ffmpeg-for-homebridge/ffmpeg -i rtsp://cam1:batavis@<IP_ADDRESS>:554/ch0_0.h264 -an -sn -dn -codec:v libx264 -pix_fmt yuv420p -color_range mpeg -r 30 -f rawvideo -preset ultrafast -tune zerolatency -filter:v scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease,scale=trunc(iw/2)*2:trunc(ih/2)*2 -b:v 299k -payload_type 99 -ssrc 8556460 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params 9PhXuPPuZG5WlOSEpTygkZKJQkeGbfTCrvg88jN8 srtp://<IP_ADDRESS>:62725?rtcpport=62725&pkt_size=1316 -vn -sn -dn -codec:a libfdk_aac -profile:a aac_eld -flags +global_header -f null -ar 16k -b:a 24k -ac 1 -payload_type 110 -ssrc 5651798 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params lm43GneVopeov3qlFiZ1synlnFdM1cYE33IA56cz srtp://<IP_ADDRESS>:53131?rtcpport=53131&pkt_size=188 -loglevel level+verbose
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info] ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1+deb9u1) 20170516
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   configuration: --pkgconfigdir=/build/workspace/lib/pkgconfig --prefix=/build/workspace --pkg-config-flags=--static --extra-cflags=-I/build/workspace/include --extra-ldflags=-L/build/workspace/lib --extra-libs='-lpthread -lm' --enable-static --disable-debug --disable-shared --disable-ffplay --disable-doc --enable-openssl --enable-gpl --enable-version3 --enable-nonfree --enable-pthreads --enable-libvpx --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libx264 --enable-runtime-cpudetect --enable-libfdk-aac --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --enable-decoder=h264 --enable-network --enable-protocol=tcp --enable-libspeex --enable-demuxer=rtsp --enable-omx-rpi --enable-mmal --enable-indev=alsa --enable-outdev=alsa
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   libavutil      56. 51.100 / 56. 51.100
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   libavcodec     58. 91.100 / 58. 91.100
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   libavformat    58. 45.100 / 58. 45.100
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   libavdevice    58. 10.100 / 58. 10.100
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   libavfilter     7. 85.100 /  7. 85.100
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   libswscale      5.  7.100 /  5.  7.100
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   libswresample   3.  7.100 /  3.  7.100
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [info]   libpostproc    55.  7.100 / 55.  7.100
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [tcp @ 0x3f79a20] [verbose] Starting connection attempt to <IP_ADDRESS> port 554
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche] [tcp @ 0x3f79a20] [verbose] Successfully connected to <IP_ADDRESS> port 554
[10/27/2020, 13:08:43] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] [rtsp @ 0x3f779f0] [verbose] SDP:
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] v=0
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] o=-<PHONE_NUMBER>870323 1 IN IP4 <IP_ADDRESS>
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] s=Session streamed by "rRTSPServer"
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] i=ch0_0.h264
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] t=0 0
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=tool:LIVE555 Streaming Media v2020.05.15
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=type:broadcast
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=control:*
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=range:npt=0-
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=x-qt-text-nam:Session streamed by "rRTSPServer"
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=x-qt-text-inf:ch0_0.h264
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] m=video 0 RTP/AVP 96
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] c=IN IP4 <IP_ADDRESS>
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] b=AS:500
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=rtpmap:96 H264/90000
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=fmtp:96 packetization-mode=1;profile-level-id=4D0020;sprop-parameter-sets=Z00AIJZUA8ARLyzcBAQECA==,aO48gA==
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=control:track1
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] m=audio 0 RTP/AVP 0
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] c=IN IP4 <IP_ADDRESS>
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] b=AS:64
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] a=control:track2
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] [udp @ 0x3f7c910] [warning] attempted to set receive buffer to size 393216 but it only ended up set as 360448
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] [udp @ 0x3f8cc70] [warning] attempted to set receive buffer to size 393216 but it only ended up set as 360448
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] [rtsp @ 0x3f779f0] [verbose] setting jitter buffer size to 500
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] [udp @ 0x3f9d9e0] [warning] attempted to set receive buffer to size 393216 but it only ended up set as 360448
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] [udp @ 0x3fadd30] [warning] attempted to set receive buffer to size 393216 but it only ended up set as 360448
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] [rtsp @ 0x3f779f0] [verbose] setting jitter buffer size to 500
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche] [h264 @ 0x3f7ae90] [verbose] Reinit context to 1920x1088, pix_fmt: yuvj420p
[10/27/2020, 13:08:45] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [warning] Guessed Channel Layout for Input Stream #0.1 : mono
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info] Input #0, rtsp, from 'rtsp://cam1:batavis@<IP_ADDRESS>:554/ch0_0.h264':
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]   Metadata:
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     title           : Session streamed by "rRTSPServer"
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     comment         : ch0_0.h264
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]   Duration: N/A, start: 0.000000, bitrate: N/A
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     Stream #0:0: Video: h264 (Main), 1 reference frame, yuvj420p(pc, bt709, progressive, left), 1920x1080 (1920x1088), 20 fps, 20 tbr, 90k tbn, 180k tbc
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info] Stream mapping:
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]   Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]   Stream #0:1 -> #1:0 (pcm_mulaw (native) -> aac (libfdk_aac))
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info] Press [q] to stop, [?] for help
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [h264 @ 0x3ff2880] [verbose] Reinit context to 1920x1088, pix_fmt: yuvj420p
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [graph_1_in_0_1 @ 0x3fd4530] [verbose] tb:1/8000 samplefmt:s16 samplerate:8000 chlayout:0x4
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [format_out_1_0 @ 0x40924b0] [verbose] auto-inserting filter 'auto_resampler_0' between the filter 'Parsed_anull_0' and the filter 'format_out_1_0'
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [auto_resampler_0 @ 0x40653b0] [verbose] ch:1 chl:mono fmt:s16 r:8000Hz -> ch:1 chl:mono fmt:s16 r:16000Hz
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info] Output #1, rtp, to 'srtp://<IP_ADDRESS>:53131?rtcpport=53131&pkt_size=188':
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]   Metadata:
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     title           : Session streamed by "rRTSPServer"
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     comment         : ch0_0.h264
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     encoder         : Lavf58.45.100
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     Stream #1:0: Audio: aac (libfdk_aac) (ELD), 16000 Hz, mono, s16, delay 288, 24 kb/s
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]     Metadata:
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [info]       encoder         : Lavc58.91.100 libfdk_aac
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche]
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [libfdk_aac @ 0x3ff0b60] [warning] Queue input is backward in time
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [rtp @ 0x40e37c0] [warning] Non-monotonous DTS in output stream 1:0; previous: 1764, current: 1054; changing to 1764. This may result in incorrect timestamps in the output file.
[10/27/2020, 13:08:48] [Camera FFmpeg] [Küche] [rtp @ 0x40e37c0] [warning] Non-monotonous DTS in output stream 1:0; previous: 1764, current: 1566; changing to 1764.  So no problem here.

Never a good idea to share those information, but as you wish.

Please, check this issue:
https://github.com/roleoroleo/yi-hack-MStar/issues/36


HIP 45: LoRaWAN Frequency Plan Selection

Author(s): @lthiery, @ivandigiusto
Start Date: 2021-10-25
Category: Technical
Original HIP PR: https://github.com/helium/HIP/pull/298
Tracking Issue: this
Status: In Discussion

Problem Statement
There are over a dozen of officially recognized LoRaWAN channel plans cited in the LoRaWAN Regional Specification. In each region, the Helium Network must select one and only one frequency plan (based on current design constraints). In cases where only one channel plan is possible (eg: Anguilla) or where only one has regulatory type approval (eg: American Samoa), the selection for the Helium Network may default to that one.
This HIP proposes methodology for the selection of a channel plan for each region.
Rendered View
https://github.com/helium/HIP/blob/master/0045-lorawan-frequency-plan-selection.md

We are already experiencing problems in Australia where there seem to be a lot of 'misconfigured' gateways. According to the documentation https://docs.helium.com/lorawan-on-helium/frequency-plans/ (and I completely agree with this choice), the officially supported frequency plan is AU915 FSB2.
The issue seems that gateway manufacturers seem to be shipping gateways to Australia with US915 configuration as well as various AS923 configurations. Whilst AS923 happens to be legal (as it's just a subset of the 64 AU915 channels) US915 is not.
The same problem has happened during the TTN Public deployment (see an extensive explanation and discussion here: https://www.thethingsnetwork.org/forum/t/future-strategies-for-au915-and-as923-in-australia/) and has caused a fragmentation of the network which makes tracking use-cases impossible. Helium would have a huge potential in such use-cases, but I fear we are already seeing the same problem occurring on the currently ~3000 Helium gateways. I am aware that DEWI tried some very hasty and in my opinion very short-sighted and ill-considered change to AS923 which thankfully was reversed quickly.
Currently, there is no way of seeing which channel plan a Helium gateway is configured to. I think this would be of critical importance for a consistent countywide network.
I believe for Helium to be able to live up to its potential in Australia really has to fix this problem urgently before it ends up a nightmare for people actually trying to roll out sensors in the real world,

There has been strong support for this proposal. The coredevs support it, the newly formed LoRaWAN committee supports it, it has 90%+ support in Discord straw polling, and there have no concerns raised either here or on the monthly community call.
I believe this proposal has passed our standard for rough consensus. On behalf of the DeWi, the HIP Editors, and the wider Helium community, I am marking this proposal as approved and recommending that the coredev team implement the necessary changes as soon as reasonably possible.

Several times I've heard Helium staff refer to Australia as though it is undecided between 2 frequency plans.
That's not the case. AU915 is the default standard (it's named that way) and AS923 is allowed for historical reasons and supply issues that apply anymore.
This discussion is essential for anyone who needs to understand this https://www.thethingsnetwork.org/forum/t/future-strategies-for-au915-and-as923-in-australia/44218
At least one commercial operator uses AS923, and some private operators probably do too, but for public LoRaWAN ie TTN it's overwhelmingly AU915. AU915 also has technical superiority, and it is the frequency that Helium began with in Australia.
So if anyone wants to change the Helium frequency plan for Australia now, they need to address these points.
If a commercial operator wants this change to happen they need to justify to the Australian Helium community the benefit for the community. It could be that they bring enough roaming traffic to make it worthwhile, but that would be weighed against losing TTN compatibility.

Since this is about Frequency Plan, I do need to highlight that we face the same problem in Malaysia. The allowed frequency is actually 919-923MHz with an EIRP of 500mW (max), and 923-924MHz with an EIRP of 500mW (max) and some extra conditions. So legally, LoRa or LongFi should not transmit outside of 919 - 924MHz and best is to stay within 919-923MHz only. The official document is here: https://www.mcmc.gov.my/skmmgovmy/media/General/pdf/Class-Assignment-No-1-of-2021_.pdf.
However, referring to LoRa Alliance document: https://lora-alliance.org/wp-content/uploads/2021/05/RP002-1.0.3-FINAL-1.pdf, There are 3 frequency bands listed for Malaysia, 433-435MHz(EU433), 916-919MHz(AS923-1), 919-924MHz (AS923-1). But the hotspots in Malaysia are transmitting frequencies of 923.2, 923.4, 923.6, 923.8, 924.0, 924.2, 924.4, 924.6 MHz. As you can see, any freq above 924MHz are out of the range allowed by Malaysia authority. Even 923MHz have special condition of < 1% duty cycle, or freq hopping or LBT.
In short preferable frequency band should be within 919-923MHz, which I think should be AS923-2=921.4, 921.6, 921.8, 922.0, 922.2, 922.4, 922.6, 922.8. These freq band are within the allowed operating freq in Malaysia.
Hope to get the attention from the Helium community. We want to grow the network legally in Malaysia.

Grabbed this info from the Australian helium discord chanel. Seems like changing to As923 is going backwards.
AU915:

Official ACMA Regional Standard
64 available channels (8 sub-bands)
Higher antenna power (30 dBm max EIRP)
no duty cycle limitation

AS923:

16 channels (2 sub-bands)
Limited antenna power  (16 dBm max EIRP)
Multiple implementations depending on which Asian country (AS923-1, AS923-2)

There is a number of other minor things, but that would be the major stuff. If you want the full low-down: https://www.thethingsnetwork.org/forum/t/future-strategies-for-au915-and-as923-in-australia/44218 or https://www.thethingsnetwork.org/docs/lorawan/regional-parameters/
We need 915 for the extra power in rural areas. Connecting towns and farms together Australia wide could be huge.

I am providing this feedback based on having run LoRaWAN networks (both AS923 and AU915) over a number of years. I have previously run other IoT networks in the same spectrum (915-928 MHz) in Australia. I am also a contributor to the LoRaWAN Regional Parameters document.
I completely understand @Ravenitt points and concerns and would like to address them here. There is a difference in what the spec says vs what it means in the real world.

Comment
Response

AU915

Official ACMA Regional Standard
Not the case. The ACMA does not have a position on which LoRaWAN channel plan should be used in Australia. This is not their purpose nor their authority.  The ACMA sets the radio rules (allowed frequencies, power and interference) for the use of radio spectrum. Also, the LoRa Alliance label of AU915 only indicates it as the first channel plan that could be used in Australia/New Zealand, not as the only one. AS923 was developed as it became clear that regional uniformity existed in the Asia-Pacific region and that a more flexible channel plan would be beneficial.

64 available channels (8 sub-bands)
Correct. 64 channel max, but all Helium hotspots at this point are using only 8 channels.

Higher antenna power (30 dBm max EIRP)
AS923 can use up to 30 dBm. More info in AS923 section below.

no duty cycle limitation
There is no duty cycle limitation for AS923 when used in Australia/New Zealand.

AS923

16 channels (2 sub-bands)
At this point, maximum number of channels that can be configured in one device is 16. This does not mean that all devices have to use the same 16 channels.   By having channels dynamically assigned, you can spread your devices however you want, allowing you to use a wide frequency range.  Additionally, this allows the option to use the newly opened 928-935 MHz spectrum (or any other band that is open to public), once Helium in AU/NZ gets to a point of needing to expand to two bands.

Limited antenna power (16 dBm max EIRP)
1. The protocol allows devices to enable higher transmit power after connection (up to 36 dBm but you need to operate within the ACMA regulations).2. There is nothing prohibiting you from setting the device to a high power transmit in the firmware (within ACMA regulations) if the device will only be used in AU/NZ. The network does not care.3. This value does not apply to the downlink transmit power which means it can fully utilise the maximum allowed power (within the ACMA regulations).

Multiple implementations depending on which Asian country (AS923-1, AS923-2)
All implementations use the same logic, The only difference is the initial two uplink frequencies.

I would also like to point out the technical benefits of AS923 not discussed by others:

Feature
Benefit

Uplink channels configurable
Other than the two mandatory channels (923.2 and 923.4), the rest of the channels can be freely configured to desired frequencies.  This allows for better management of future capacity expansion, interference management and day-to-day network operation. It is possible to have different sets of devices operate on different frequencies.Imagine a future where we start needing more than 8 channels due to a large number of devices. The network would end up having 8 channels across the country, and dense areas would retask some hotspots to cover a new band of 8 channels. Devices that are mobile would be configured with 8 channels that are most common across the region. Devices that are stationary (water meters, environmental sensors, rain gauges, etc.) could be switched to the new 8 channels. While you could do this with AU915, you would have to pick a fixed bank of channels. With AS923, that spectrum can be anywhere (within the ACMA regulations) That flexibility is very valuable for the continued success of Helium.

Downlink channels can be customised for each uplink frequency
Instead of being stuck with hard-coded downlink frequencies, AS923 allows for customisation of each downlink frequency. This allows the network to deal with potential interference and congestion issues in the future. Future interference and congestion issues can severely impact the viability of the Helium network, so it is essential to have tools at our disposal to deal with them as they arise.

Slowest downlink SF12BW125
AS923 downlink will be able to reach further than on AU915 (SF12BW500). The difference is about 5 dB which is close to doubling the downlink range

I am providing this feedback based on having run LoRaWAN networks (both AS923 and AU915) over a number of years. I have previously run other IoT networks in the same spectrum (915-928 MHz) in Australia.

Well, that is good for you. I am assuming that these were insular private LoRaWAN networks. However, what we are talking about here is a public network on a global scale. Helium in Australia is already at a scale no other LoRaWAN network has ever achieved.

There is a difference in what the spec says vs what it means in the real world.

That is a very dangerous comment to make. Standards are there for a reason. This is not the wild west.
Just because you could ignore the standard and make all these changes on a private network where you control all the aspects end-to-end (devices, gateways and NS) does not mean that this is relevant with a large public ecosystem of gateway and device manufacturers worldwide.
Gateway radios are controlled by standardised configuration files and devices by respective libraries which enforce the official (AS923/AU915) specs.
Just because there is the theoretical ability for these things to be different in Australia is totally irrelevant. It will never happen on a public network.

Also, the LoRa Alliance label of AU915 only indicates it as the first channel plan that could be used in Australia/New Zealand, not as the only one. AS923 was developed as it became clear that regional uniformity existed in the Asia-Pacific region and that a more flexible channel plan would be beneficial.

This is also a very misleading comment.
AS923 was never developed for Australia. Quite obvious by the first two characters. It just happens to fit into the rules as it is just a subset of the AU915 channels plan and with lower limits on TX and duty cycle limitations.
The fact is also that AS923 only became useable in Australia after LoRa Alliance made some changes.
Anybody with a history of LoRaWAN in Australia knows it wasn't chosen for reasons of being better suited for Australia by some private operators - it was chosen purely as in the early days because of issues with certain device availability. That pretty much is a non-issue these days for devices using recent LoRaWAN modules.

64 available channels (8 sub-bands)	Correct. 64 channel max, but all Helium hotspots at this point are using only 8 channels.

The important part in this comment is "at this point". It is shortsighted to assume that this is not going to change as the Helium and LoRaWAN ecosystem matures. We are building this network for the future - not just for today.
Downgrading the Helium network at this point (by adopting AS923) is incredibly counterproductive and short-sighted.

Higher antenna power (30 dBm max EIRP)	AS923 can use up to 30 dBm. More info in AS923 section below.

Could theoretically be used - again just a misleading comment.
The AS923 specs say 16 dBm max EIRP and that's what is in the radio configuration the gateway manufacturers are shipping.
The fact is that this is totally irrelevant in the real world. Just because theoretically you could doesn't mean it has any realistic chance of ever happening on a public network ecosystem.
This TX limitation is actually the most crucial deficiency of AS923.
You might be able to mask that fact in the densely populated metropolitan areas. But that is a very small part of Australia. This would be absolute madness in the rest of Australia.
A large number of these devices would never be able to get through an OTAA join procedure outside of dense metro areas because of the limited TX power of AS923.
Changing the Helium frequency plan for Helium in Australia is the equivalent of taking out a shotgun, aiming straight for your foot and pulling the trigger.

no duty cycle limitation	There is no duty cycle limitation for AS923 when used in Australia/New Zealand.

Again - as per the previous point. These limitations are enforced by gateway radio configuration and devices libraries. What you are effectively arguing for is "AS923-4" - YAFFP (yet another f....g frequency plan).

All implementations use the same logic, The only difference is the initial two uplink frequencies.

You are totally missing the point. AS923 has 3 variations (AS923-1, AS923-2 and AS923-3).
The point is that the whole region "roaming" argument is a furphy. AS923 is fragmented and in fact, Australia's closest neighbour (and by far the largest population in our region) is AS923-3.
Much more important is the huge differences between the countries adopting AS923 and AU915.

(thanks @rockinrobstar for the image)
Countries adopting AS923-1 are mainly countries that have high population density. That is the EXACT opposite of Australia. If you look at the list of countries adopting AU915 they are large countries with vast areas of very sparsely populated regional areas. Look at Brazil or Argentina or Chile. There is an obvious reason for this.

Overall these comments are mostly irrelevant in the context of a global PUBLIC network with phenomenal growth and in a country as vast as Australia. And they are downright dangerous for everyone who has invested their time and money in the Helium network in this country. They serve no purpose other than saving face for some private network operators that have bet on the wrong horse years ago.
The same private network operators I actually notice on your list of employers (LinkedIn). Would it not be appropriate declaring that conflict of interest here?
As for some of the RF details, I would highly recommend reading the comments from @tonysmith55 in the main PR

"AS923-4" - YAFFP (yet another f....g frequency plan).

AS923-4 already exists for Israel. So you will need to go to AS923-5.
I think this probably proves your point even more though 😉

@shawaj @leogaggl @ivandigiusto @oberchoo @buzzware
It seems many of these comments relate to AU+NZ in particular and I request such comments move to the dedicated topic:
https://github.com/dewi-alliance/hplans/pull/28
HIP45 amendments or related governance topics might be related here, but this HIP has nothing to do with AU+NZ in particular and instead covers frequency plan changes in general.

Explanation here: https://discord.com/channels/404106811252408320/813452716286017557/1006694552557596733

HIP45 has been closed, and the corresponding Discord channel has been archived. Some thoughts have been raised that HIP45 needs to be unlocked as frequent changes are planned and need discussion.
Going forward, #poc-discussion in Discord is the best place to talk about HIP45. HIP 45 was a HIP to create a way of deciding on which frequencies to use where there was more than one, or it was undefined. But, since we became more involved with the LoRa Alliance, Helium made a decision to follow their defined or recommended default standards for a country rather than decide on our own and break with the rest of the alliance.

Country frequency plan issues can also be raised at
hplans is a geojson representation of the LoRaWAN regional parameter channel plans. It is based on the LoRaWAN Alliance's RP2-1.0.3 LoRaWAN Regional Parameters, as well as the Helium Network's country definitions.


CLT detection fails, even if Xcode installed

brew doctor output
Your system is ready to brew.

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
HOMEBREW_VERSION: 4.4.12
ORIGIN: https://github.com/Homebrew/brew
HEAD: 3001afe88112c13b5aafdd92e097680897060881
Last commit: 6 days ago
Branch: stable
Core tap JSON: 21 Dec 09:31 UTC
Core cask tap JSON: 21 Dec 09:31 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 3.3.6 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 16.0.0 build 1600
Git: 2.39.5 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.2-arm64
CLT: N/A
Xcode: 16.2
Rosetta 2: false

What were you trying to do (and why)?
brew upgrade
What happened (include all command output)?
 % brew upgrade
==> Upgrading 3 outdated packages:
<EMAIL_ADDRESS>3.12.7_1 -> 3.12.8
awscli 2.18.2 -> 2.22.22
gcc 14.2.0 -> 14.2.0_1
Error<EMAIL_ADDRESS>the bottle needs the Apple Command Line Tools to be installed.
  You can install them, if desired, with:
    xcode-select --install

If you're feeling brave, you can try to install from source with:
  brew install --build-from-source<EMAIL_ADDRESS>
It is expected behaviour that most formulae will fail to build from source.
It is expected behaviour that Homebrew will be buggy and slow when building from source.
Do not create any issues about failures building from source on Homebrew's GitHub repositories.
Do not create any issues building from source even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help building from source in Homebrew's discussions but are unlikely to receive a response.
If building from source fails, try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
==> Downloading https://ghcr.io/v2/homebrew/core/awscli/manifests/2.22.22
Already downloaded: /Users/justin/Library/Caches/Homebrew/downloads/661009034b4916322d1d2aff939d38ffa1c8e3600d3e455b90852eccf73b5fa2--awscli-2.22.22.bottle_manifest.json
==> Fetching dependencies for awscli: pkgconf and<EMAIL_ADDRESS>==> Downloading https://ghcr.io/v2/homebrew/core/pkgconf/manifests/2.3.0_1-1
Already downloaded: /Users/justin/Library/Caches/Homebrew/downloads/4a660f26297baafd06fb3109f473edfa592f4aa00adbd8a2506b05d0374c5c1d--pkgconf-2.3.0_1-1.bottle_manifest.json
==> Fetching pkgconf
==> Downloading https://ghcr.io/v2/homebrew/core/pkgconf/blobs/sha256:6b946f8b716f639a88b6fb05fadf57de8309a53d04d4daef93dda1365f0222e3
Already downloaded: /Users/justin/Library/Caches/Homebrew/downloads/e6b0ced15213e02c1914d4dfc12d9fc60b77cca3b997b96a70e44106a6ef239d--pkgconf--2.3.0_1.arm64_sequoia.bottle.1.tar.gz
Error<EMAIL_ADDRESS>the bottle needs the Apple Command Line Tools to be installed.
  You can install them, if desired, with:
    xcode-select --install

If you're feeling brave, you can try to install from source with:
  brew install --build-from-source<EMAIL_ADDRESS>
It is expected behaviour that most formulae will fail to build from source.
It is expected behaviour that Homebrew will be buggy and slow when building from source.
Do not create any issues about failures building from source on Homebrew's GitHub repositories.
Do not create any issues building from source even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help building from source in Homebrew's discussions but are unlikely to receive a response.
If building from source fails, try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
Error: gcc: the bottle needs the Apple Command Line Tools to be installed.
  You can install them, if desired, with:
    xcode-select --install

If you're feeling brave, you can try to install from source with:
  brew install --build-from-source gcc

It is expected behaviour that most formulae will fail to build from source.
It is expected behaviour that Homebrew will be buggy and slow when building from source.
Do not create any issues about failures building from source on Homebrew's GitHub repositories.
Do not create any issues building from source even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help building from source in Homebrew's discussions but are unlikely to receive a response.
If building from source fails, try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.

What did you expect to happen?
I expect it to upgrade those packages.
I have Xcode installed, and the command line tools are available from that. I do not have the tools at /Library/Developer/CommandLineTools.
The problem appears to be at this line of xcode.rb, in detect_clang_version: https://github.com/Homebrew/brew/blob/master/Library/Homebrew/os/mac/xcode.rb#L407
This code assumes that clang is installed in /Library, but this isn't true for Xcode users.
This change was introduced in this commit: https://github.com/Homebrew/brew/commit/b58fa4ebb1e6b918d8556cba629cb55b79d423f5
Editing xcode.rb and removing the use of PKG_PATH fixes it for me, but I realize that will probably break other users.
Step-by-step reproduction instructions (by running brew commands)
Install Xcode.
Remove /Library/Developer/CommandLineTools.
Verify that the command line utils are available from Xcode: `xcode-select -p`.
Install any package that requires CLT, like<EMAIL_ADDRESS>

This is intentional. When Homebrew says it needs the CLT, it means that it needs the Xcode CLT installed at
/Library/Developer/CommandLineTools

Having dev tools provided by an Xcode.app installation does not suffice.

Thanks for the quick error update! I will say I'm a bit surprised that this is the case. Poking around in Xcode.app, it looks like the tools provided there are a superset of the ones provided by the "Xcode CLT" package. I don't have proof of this, but I looked at the file listings in both.
The reason why I bring this up is because having the Xcode CLT installed requires an additional 1.7GB of storage, which seems a bit heavy when Xcode already takes up so much space on its own.
Is there something specific that's needed from the CLT, or is this just a sanity-driven design decision for Homebrew?

Is there something specific that's needed from the CLT, or is this just a sanity-driven design decision for Homebrew?

We need:

the right SDK (i.e. one with the version matching your OS)
at a known installation path (because paths get baked into binaries for some formulae)

For macOS versions that aren't the latest release, only the CLT at /Library/Developer/CommandLineTools meets the first requirement. Xcode.app will typically always only contain the SDK for the newest version of macOS. For example, Xcode.app 16 contains only MacOSX15.2.sdk.
Xcode.app also cannot be relied on to meet the second requirement. It can be installed anywhere on disk, and does not have a fixed canonical location.
If you don't want to install the CLT, you can try:

building the relevant formulae from source; or
using the --force-bottle flag (i.e. brew install --force-bottle)

Note that neither option is supported. The first option will usually work, but takes time and can often fail for arbitrary reasons. The second option will cause you issues as soon as you touch a code path that requires one of the two requirements I stated above. (Example: try compiling anything with gcc-14 or g++-14)

Got it. Thanks for the explanation! Today I learned.
In those cases, the Homebrew requirements indeed make a lot of sense 👍


fix: Subscriptions require offerToken on Google Play

fix: github issue template (#1805)
fix: limit promotedProductListener to iOS (#1801)
8.6.3
fix: missing method (#1812)
fix: make all types optional (#1813)
8.6.4
docs: add @jeremybarbet to maintainer
chore: new examples (#1807)
removed old methods
yarn.lock
fixed example
fix subscription type
fix: removed optional parameters from examples (#1816)
[iOS] Fix issues related to pending transactions. (#1809)
8.6.5
ci: remove example proj on release (#1819)
ci: verify no file changed ignoring the example project
remove commitlint
fix lint
fix: OfferToken is required
lint fixes

Fixes this issue: https://github.com/dooboolab/react-native-iap/issues/1823


fmt PEG error messages produce stacktrace

Should the calls to error in fmt's PEG be caught by the formatting functions so that rather than a stacktrace to the functions producing the error, the message instead shows the line with the error and a visual indication (perhaps with ^) showing the character that caused the issue?

PEGs (error) form now gives line and column information by default.


Not playing

There's a lot of ads on the movies so no matter how much i try to play a movie an ad keeps popping up and TV series don't play, could you add a built in video player? Maybe that would help with the ads

I am working on it.
Thanks for the feedback!

You're welcome, thank you 😌

Hello dear user, I also have an app much like it obviously better than it without ads, https://yogesh-hacker.github.io/yogesh-hacker/App

Hello dear user, I also have an app much like it obviously better than it without ads, https://yogesh-hacker.github.io/yogesh-hacker/App

See this comment.


Initial value for Material UI checkbox

I have a couple of Material UI Checkboxes on a Redux form and they work fine - except that the initial values are always undefined. They look something like this:
<Checkbox
  defaultChecked={false}
  checked={ieee.value}
   onCheck={(e, checked) => ieee.onChange(checked)}
/>

<Checkbox
  defaultChecked={true}
  checked=active.value}
  onCheck={(e, checked) => active.onChange(checked)}
/>

I also tried setting checked to active.checked and a couple of other things, but no matter what cannot seem to figure out how to get the initial field values to match whether the boxes are checked or not. Once I toggle them by clicking one... the values are fine.

Finally figured it out... needed initialValues: {ieee: true, active: false} in the form.

Having this issue too, can you please describe a bit more where and how you are setting the initiaValues?
I tried setting it in my container for a route like so:
const mapStateToProps = (state) => ({
  NewPatient: state.NewPatient,
  initialValues: {prescribed: true}
})

But nothing happens. I suspect that I am just not mapping correctly, but can't really conceive of what the current state is here. For example, the form is an empty object at this point from what I can tell.
TIA!

I figured it out too. I misunderstood where to set these initialValues obviously.
For anyone else having this issue, I set these values in the call to the form like so:
NewPatient = reduxForm({
  form: 'NewPatient',
  fields,
  initialValues: {prescribed: true},
  validate
})(NewPatient)


Replace fse with AzExtFsUtils where possible

I couldn't get rid of fse entirely unfortunately...

There's a createWriteStream command in requestUtils that there's no equivalent in workspace.fs
The gulpfile doesn't actually have access to the utils package because the gulpfile doesn't run with the extension as far as I know. Whenever one is resolved, we should be able to move fse-extra to a devDependency or replace with fs calls
A couple of calls to copy had to have the "overwrite" property added to them. It was causing issues in the tests when the backup templates were being updated.

I couldn't get rid of fse entirely unfortunately...

There's a createWriteStream command in requestUtils that there's no equivalent in workspace.fs

Can't we make our own leveraging fs.writeFile along with an in-memory stream buffer?

I couldn't get rid of fse entirely unfortunately...

There's a createWriteStream command in requestUtils that there's no equivalent in workspace.fs

Can't we make our own leveraging fs.writeFile along with an in-memory stream buffer?

Yeah, I think we can but I wanted to do that separately just since it's a bit more of a complex change than just changing out some fs calls with VS Code's implementationm


feat(@angular/cli): add vrsource-tslint-rules

This is a proposition to include a few interesting rules from vrsource-tslint-rules.
It adds:

no-duplicate-imports (see docs)
no-jasmine-focus (see docs)
prefer-literal (see docs)

Please rebase on top of master.

Those rules seem useful, but I'm not sure if it's worth it to add them at the expense of another library and slightly increased complexity. @hansl @Brocco @sumitarora thoughts?

Closing as I think it's better to not add another dependency.


Still no updates?

almost 4 months no updates....

I also hope there will be updates. It's the - only - browser based on Chrome with extension support on Android. I like the clean standard Chrome experience degoogled and with all ad-blockingand possibilities.

Some web pages that use new chrome features are no longer visible :(, it's too bad.
I'd have to change my browser to edge canary and install extensions from dev setting.

Some web pages that use new chrome features are no longer visible :(, it's too bad.
I'd have to change my browser to edge canary and install extensions from dev setting.
@PawelGu Now edge canary also can install extensions from dev settings. You can download it from google play.

Thanks for pointing out Edge Canary, so there is another Chromium based browser supporting extensions.
Kiwi seems to be abandoned, continuing to use it is a major security risk.

Some web pages that use new chrome features are no longer visible :(, it's too bad. I'd have to change my browser to edge canary and install extensions from dev setting.
@PawelGu Now edge canary also can install extensions from dev settings. You can download it from google play.
Thanks for all developers made such a great app, but it's little bit slow to update, so i have to change a browser app temporarily and wait for update.

Great, I didn't have this one on my radar. I tried it out and it seems to work well except my mobile gets unusually hot with some of the extensions installed by extension id through developer options. Well it's very new and alpha so I hope it eventually will work out. Only problem then still will be Microsofts heavy telemetry.

@PawelGu
Yes, this is a alpha version, some plugins still have problems, and even some times the screen will go blank, but it still works fine, my phone has no heating problems, presumably it may be that the plugin is not compatible with browsers?
Plugin compatibility work is complicated, so I have a feeling that it will be in canary version for a long time, and will not be open for download in the stable version

Only problem then still will be Microsofts heavy telemetry.

There are 3 options now:

use Fennec from F-Droid, which is Firefox with telementry removed and about:config enabled, supports Firefox extensions but may have less website compatibility than Chromium and no tab-based process isolation
use Edge Canary with MS telemetry
use abandoned Kiwi with known security holes

Chose the lesser evil.

@CyanDragonS
Probably, not to mention extensions only arrived half a year ago for Edge Canary, maybe we will have the honor of a beta implementation next year.
@lje

-> Better 'Mull'.


Unwrap ListOrSingle values in helpers

Currently helpers e.g. eq and jsonPath don't work properly with ListOrSingle values unless you explicitly use the indexed form.
This is pretty confusing so helpers should check for this condition and unwrap singular values from ListOrSingle so that the index becomes unnecessary.

@tomakehurst Is this issue still active?

I notice there is a previous commit https://github.com/wiremock/wiremock/commit/618d82517f3180340b7b54ce051dbfd3004addd3 in JsonPath.  Does anything require to improve so far?

I haven't yet found a way to do this that doesn't cause regressions. I think it's safe to assume it's not going to happen for quite a while, if at all.
You always have the option of using the indexed form of the attributes, or if you've got multiple values you can use the new contains helper e.g. {{#contains request.query.myParam 'value'}}


Automated Windows builds using Appveyor

Doesn't yet automatically upload to Pypi but this does 90% of the required work.
Currently covers:

Python 2.7, Windows 64bit
Python 3.5, Windows 64bit

[Current coverage][cc-pull] is 46.87%

Merging [#408][cc-pull] into [devel][cc-base-branch] will not change coverage

@@              devel       #408   diff @@
==========================================
  Files           182        182
  Lines         17942      17942
  Methods           0          0
  Messages          0          0
  Branches       2513       2513
==========================================
  Hits           8411       8411
  Misses         9100       9100
  Partials        431        431

Powered by Codecov. Last updated by [893b9a7...04ce73b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/SheffieldML/GPy/branch/devel?src=pr
[cc-compare]: https://codecov.io/gh/SheffieldML/GPy/compare/893b9a7eba8dcb1aae5188bbdf3de13980f693ac...04ce73b858b372bdb60aa098b913f2f3e409c5c5?src=pr
[cc-pull]: https://codecov.io/gh/SheffieldML/GPy/pull/408?src=pr


Read dom feature Updated and Improved

Property syntax used to retrieve property, if defined return properties else throws an error using _error() function

Hi @lindelwa122  the code has been updated do review it. I had used index.html to test, later on deleted and i have committed the necessary files.

Hey, @sinster2003, thanks for your efforts towards this project. I have merged your PR, please make sure to inspect other issues or features that might be of interest to you. :1st_place_medal:


Code formatting config + github workflow for PR

Hello
Here is a code formatting configuration with Prettier and EditorConfig.

The configuration generally follows the current formatting
I added a command in the package.json to reformat everything with pnpm prettier:format
Specific files are ignored in .prettierignore
Finally, I added a GitHub workflow to check the formatting in PRs (pull requests).

Hum... the check should be failed !

:ok_hand:

nice work

tho it should only be triggered by pull requests
the push is uneeded.
since you can validate locally
this is only for review

tho it should only be triggered by pull requests the push is uneeded. since you can validate locally

fully agreed with you, it's a mistake
thanks for review


fix($rootScope): fix potential memory leak when removing scope listeners

This attempts to fix #16135, but is assuming that browsers will use some type of memory efficient array implementation for sparse arrays (which they appear to do, see 1, 2, 3).  In the worst case this should have no change may cause some extra swapping of array implementations and/or not fix the bug, in the best case it will be more memory efficient in this edge case.
Also added a couple tests that show why we don't simply use splice.
Thanks @jvilk for investigating this delete solution.

The errors look weird. An incompatibility between yarn and dgeni-packages? Strange because I don't think we changed anything.

@jbedard can you please rebase this? The tests currently don't run because of a Travis problem at the branch point.

Rebased. Adjusted the tests a bit like @gkalpak suggested.

Another good read about array storage/optimizations: https://www.html5rocks.com/en/tutorials/speed/v8/#toc-topic-numbers
Again v8 specific, but this confirms what we've been talking about (and what @jvilk measured) with array vs dictionary versions of an array. Using delete could cause a switch to the dictionary implementation which forces memory reallocation/copying, but then (for sparse arrays) it will use less memory.

Actually... I came up with an alternative that might be better, essentially doing the same as $$digestWatchIndex. Basically making the $$listeners iteration index global (per event type per scope) so it can be adjusted, if necessary, when a listener is removed. The only constraint is this means you can not iterator over $$listeners recursively which I think is already a restriction due to the prevoius array cleanup that essentially had the same restriction.
See https://github.com/jbedard/angular.js/commit/68247ee4c13d6ef7fedb0aad09b8ce80d8a9fd61 - WDYT?

The only constraint is this means you can not iterator over $$listeners recursively

You mean iterate over $$listeners and modify while you iterate over them? That sounds like an acceptable tradeoff.

I think it would be recursive $emit or $broadcast calls of the same event name. I'm pretty sure this was already broken in some cases, but this (storing the iteration index on the array) would break it in all cases.

Since I don't really use events in AngularJs, I can't say if there are valid use cases for recursive emission and broadcasting. It's probably a BC for someone ...

We decided to land this PR as is for 1.6.0 (to avoid any breaking changes and still avoid the memory leak).
For 1.7.0, we will implement something like jbedard/angular.js@68247ee (which avoids making iterations slower as the array grows in length) with an explicit check to prevent nested listener iterations and a breaking change notice.

SGTM

Don't forget to change the branch target to v1.6.x for this one

I've rebased this onto v1.6.x, also updated the first commit to include the changes from #16293.

I've merged this to v1.6.x and cherry-picked the first commit (extra tests, not specifically for this bug) into master.


Scrollbar improvements

PR fixes #11190.
PR fixes #11194.
This PR includes an update in the Perfect Scrollbar dependency. You can see the proper update in https://github.com/nobuti/perfect-scrollbar/pull/1. Also, this allows us to remove the polling in the scroll view to check when new children are appended to the container in order to update the scroll. That is delegated to the plugin now.
Also, check that #11194 is fixed with these improvements.

@piensaenpixel, could you point me which new things I should notice in the UI?

Ok, scrollbar always visible, I like it 👍 . One thing I've notice is:

Wouldn't you separate the scrollbar at least a pixel to the edge of the content?

Test if this fixes https://github.com/CartoDB/cartodb/issues/11194, please

Yeah, it is fixed.

Talking with @piensaenpixel offline, rest of the designers said that scrollbar is ok where it appears, so 👍 .

I'm agree with you but it is an @urbanphes and @josecruz decision...
El El jue, 19 ene 2017 a las 14:18, Javier Álvarez Medina <
<EMAIL_ADDRESS>escribió:

Ok, scrollbar always visible, I like it 👍 . One thing I've notice is:
[image: screen shot 2017-01-19 at 14 17 23]
https://cloud.githubusercontent.com/assets/132146/22108173/12bb290e-de52-11e6-8ab7-fa22e6cd0a39.png
Wouldn't you separate the scrollbar at least a pixel to the edge of the
content?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/pull/11233#issuecomment-273773851,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABKG-Sr6jpBf80RKM6BQD6_C9iqv_xcfks5rT2KggaJpZM4LhjjJ
.


Windows support

I've updated the logic for relative paths and the tests, which pass under Windows and OSX.
I've left in the substitution of \ for / in Windows paths, as it matches my use case, although I'm not sure if that makes sense for others.

Sweet, looks rad! Thanks!


Localize show All & show Less button in  @adobe/react-spectrum/TagGroup component

Provide a general summary of the issue here
Consuming tag group in another unified shell app leaves these button unlocalized.
🤔 Expected Behavior?
Test should follow localization
😯 Current Behavior
english text always shown.
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
set maxRows to 1 and enable show/hide overflowing tags.
Btn is not localized
Version
2.28.0
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
MacOS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

It is localized automatically. It will use your browser's language by default, unless you override the locale set on the Provider. https://react-spectrum.adobe.com/react-spectrum/Provider.html#locales If this is already being set, then you need to check for duplicate node_modules (perhaps tag group is using a different version from provider).


Why does my sdkmanager always vanish?

My problem is: Every time I run this: flutter doctor --android-licenses --verbose, I will receive this:

And when I get into the tools\bin folder, the sdkmanager.bat will vanish, but in fact, it was there before I run that command.
Here is my flutter doctor:

Well, I think that .bat file also vanish when I run flutter doctor -v too ....
Does it mean to vanish? ...
Hope you can help me with that because I really want to build an app for my niece!!!

Hi @dinhan1192
please follow up on https://github.com/flutter/flutter/issues/56628,
I'm closing the current one as duplicate.
If you disagree please write in the comments
and I will reopen it.


Add break-point

Add a break-point for debugging.

https://github.com/ZenHarbinger/torgo-javascript/commit/a7879c92f03fc7dc165880cc2fffac985253c82b
Would like t add line highlighting.

https://github.com/ZenHarbinger/torgo-javascript/commit/eaf1430a4b20191e6654cbdda23dd145f563d0aa


N20: Kajiya

Hullo! Hope this fits here somewhere 🤪
Part of https://github.com/rust-gamedev/rust-gamedev.github.io/issues/531

Thanks for the PR!

Thanks for the invitation! :)


Document since when ARG before FROM is allowed

File: engine/reference/builder.md
I just broke a build since the documentation is unclear since when ARG before FROM in a Dockerfile is allowed.
A simple reference that this works since v17.06 only, but the ARG directive is accepted before as documented on stackoverflow (see https://stackoverflow.com/questions/40273070/docker-build-arg-in-source-file ) would have saved me quite some time.

Thanks for sharing this issue. This particular content is maintained in an upstream repo. If the issue is still applicable, please help create an issue in the repo at https://github.com/docker/cli/tree/master/docs/reference


How to stop Mail triggering in Elmahcore when HttpStatusCode value is 401 UnAuthorized

Hi
I am using Elmahcore for logging exceptions in .net core web api 2.2 application.
In that i have done the settings for Mail Triggering in startup.cs file is
services.AddElmah(options =>
{
            options.Path = @"elmah";
            options.LogPath = "~/logs";
            options.Notifiers.Add(new ErrorMailNotifier("Email", emailOptions));
        });

whenever i tried to hit the web api url i am getting the unauthorized exception through mail
i need to stop the mail triggering whenever there is UnAuthorized  exception came
please kindly help me out how to resolve this issue using filters.

Try this
services.AddElmah(options =>
{
            options.Path = @"elmah";
            options.LogPath = "~/logs";
            options.Notifiers.Add(new ErrorMailNotifier("Email", emailOptions));
            options.Filters.Add(new DemoFilter());
});

...
 public class DemoFilter : IErrorFilter
    {
        private bool _dismissAll = false;
        public void OnErrorModuleFiltering(object sender, ExceptionFilterEventArgs args)
        {
            if (_dismissAll || args.Exception is UnauthorizedAccessException)
            {
                _dismissAll = true;
                args.DismissForNotifiers(new[] {"Email"});
            }
        }
    }

Thanks for reply..
i will try and let you know

Working fine!!!
Thanks.


Fix timestamp parser error in cisco_catalyst plugin

In customer environment we were seeing a * in front of the timestamp which would cause the regex to fail to parse. Updated regex and routers to handle this without error.

I used this log entry to test.
54: *Feb 28 19:02:23 EST: %DHCP-6-ADDRESS_ASSIGN: Interface Vlan1 assigned DHCP address <IP_ADDRESS>, mask <IP_ADDRESS>, hostname test

It outputs
{
  "timestamp": "2021-02-28T19:02:23-05:00",
  "severity": 30,
  "severity_text": "6",
  "labels": {
    "log_type": "cisco_catalyst",
    "net.host.ip": "::",
    "net.host.port": "514",
    "net.peer.ip": "<IP_ADDRESS>",
    "net.peer.port": "59094",
    "net.transport": "IP.UDP",
    "plugin_id": "cisco_catalyst"
  },
  "record": {
    "facility_text": "DHCP",
    "message": "Interface Vlan1 assigned DHCP address <IP_ADDRESS>, mask <IP_ADDRESS>, hostname test",
    "mnemonic": "ADDRESS_ASSIGN",
    "sequence_number": "54"
  }
}

This command
nc -w1 -u localhost 514 <<< '54: *Feb 28 19:02:23 EST: %DHCP-6-ADDRESS_ASSIGN: Interface Vlan1 assigned DHCP address <IP_ADDRESS>, mask <IP_ADDRESS>, hostname test'


Go (golang) Auto Complete (Half) Works

VSCode Version: 1.7.1
OS Version: Ubuntu 14.04

Steps to Reproduce:
Can't provide steps to reproduce. It happens spontaneously. Others had this issue too (on gitter).
The default gocode auto built option is not changed: "go.gocodeAutoBuild": true.
And I have these personal settings (just FYI; and I do not know if they matter in this matter):
// Place your settings in this file to overwrite the default settings
{
    // Is git enabled
    "git.enabled": false

    , // Migrated from previous "File | Auto Save" setting:
    "files.autoSave": "afterDelay",

    // Controls the delay in ms after which a dirty file is saved automatically. Only applies when "files.autoSave" is set to "afterDelay"
    "files.autoSaveDelay": 2000
}

And I have this script rs-gocode:
#!/bin/bash

gocode close
gocode

But it does not help (Should I run it inside current directory?).
Sometimes after login/logout or restart, the problem goes away and the problem is mostly with code that is currently being written (it compiles & passes the tests - not broken).

https://github.com/Microsoft/vscode-go is the golang plugin repositorie
PS maybe some screenshots for when it happens? Anyway it works for me on osx but i do remember i had to do the gocode close and empty my golang path and reinstall the tools the go plugin is using

Please file against https://github.com/Microsoft/vscode-go  (thanks @gertcuykens )


Activity page ui

closes #25
the "interested" button doesn't perform a function yet
everything else should be working fine.

@geooot @phulsechinmay for some reason the lint thing is failing on GitHub but I can't reproduce the error locally and don't know how I can fix it. Could you guys look into it and help me out?


Provider stops updating after hot restart on the web.

Provider stops updating when listening to Firestore updates after performing a hot restart.
To reproduce the issue run the code below:
final counterProvider = Provider((ref) {
  return ref.watch(counterStreamProvider).value?.data() ?? {};
});

final counterStreamProvider = StreamProvider((ref) {
  return FirebaseFirestore.instance.collection("channels").doc(AuthService().getUid()).snapshots();
});

void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  await Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);

  runApp(ProviderScope(
    child: MaterialApp(home: Consumer(
      builder: (context, ref, _) {
        // provider stops updating after hot restart
        print(ref.watch(counterProvider));
        return Scaffold(
          floatingActionButton: FloatingActionButton(onPressed: () {
            FirebaseFirestore.instance
                .collection("channels")
                .doc(AuthService().getUid()).set({"random_number": "${Random().nextInt(10000)}"});
          }),
        );
      }
    ),),
  ));
}

This is working fine for me. Either this was fixed or the reproduction doesn't work for me.
Considering it's quite old and with no activity, I'll close this.


ARROW-7519: [Python] Build wheels, conda packages with dataset support

@ursabot crossbow submit -g conda -g wheel

@ursabot crossbow submit -g conda -g wheel


Simulated Devices

Apparently I cannot delete the simulated devices-this is a bit annoying, I obviously want to customize the solution to my own needs, and I don't need telemetry of simulated devices appearing on the dashboard(and filling it up), so it does not make sense to prevent deleting a simulated device.

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

ID: 51abdbe5-3e9e-4e52-223e-2f7e8b35649a
Version Independent ID: 0827746b-8343-3672-8894-474f6935836c
Content: Advanced monitoring in remote monitoring solution - Azure
Content Source: articles/iot-suite/iot-suite-remote-monitoring-monitor.md
Service: iot-suite
GitHub Login: @dominicbetts
Microsoft Alias: dobett

@wechuli Thanks for sharing how you resolved this! We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


[BUG]: expo-sqlite initial migration silently fails

What version of drizzle-orm are you using?
0.29.4
What version of drizzle-kit are you using?
0.20.14
Describe the Bug
When following the steps within the drizzle-orm docs I ended up not being able to do anything with the sqlite db since the initial migration seems to silently fail. I've tried a lot of different possible fixes ie. rename of table, clearing drizzle directory, etc. but no dice.
Expected behavior
If drizzle fails to push the migration, I'd expect some form of feedback on this matter.
Environment & setup
arch linux, expo go (most recent testing release) on iPhone 15.
Repo: https://github.com/GlitchTech-Developments/iungo-manager

Closing since issue seemed to be schema related.


MTLCompareFunction requires iOS 9.0

Fixes #issue
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[x] tested examples with the following backends:

[x]metal

[x] rustfmt run on changed code

We can reuse an existing code and error! the cause, or add a new code aka generic Unsupported.

On Jan 5, 2019, at 13:37, Michael(LAI<EMAIL_ADDRESS>wrote:
@Michael-Lfx commented on this pull request.
In src/backend/metal/src/device.rs:

@@ -1575,7 +1575,10 @@ impl hal::Device for Device {
}

     if let Some(fun) = info.comparison {

       descriptor.set_compare_function(conv::map_compare_function(fun));

       if (caps.os_is_mac && caps.has_version_at_least(10, 11)) ||

           (!caps.os_is_mac && caps.has_version_at_least(9, 0)) {

           descriptor.set_compare_function(conv::map_compare_function(fun));

But there is not suitable error of AllocationError for the case.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes, sure!
Note that this issue has been discussed in MoltenVK repo with the conclusion that we still support comparison samplers if they are immutable (provided at the descriptor set layout creation), so your application can still use them. (Link needed)

On Jun 4, 2019, at 22:29, Michael(LAI<EMAIL_ADDRESS>wrote:
@Michael-Lfx commented on this pull request.
In src/backend/metal/src/device.rs:

@@ -1575,7 +1575,10 @@ impl hal::Device for Device {
}

     if let Some(fun) = info.comparison {

       descriptor.set_compare_function(conv::map_compare_function(fun));

       if (caps.os_is_mac && caps.has_version_at_least(10, 11)) ||

           (!caps.os_is_mac && caps.has_version_at_least(9, 0)) {

           descriptor.set_compare_function(conv::map_compare_function(fun));

Should we add a bool field in PrivateCapabilities to indicate that whether set_compare_function works on the current platform?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@Michael-Lfx

Should we add a bool field in PrivateCapabilities to indicate that whether set_compare_function works on the current platform?

Yes, we need that.
Important to note that we'd still allow the samplers to be created, but disallow them being used in immutable sampler bindings (in create_xxx_descriptor_sets).
And as I mentioned, we need to panic right away if this isn't followed by the user.

Closed by #2885


Centre Window Functionality

Description of the new feature / enhancement
Centre a window on the screen.
Scenario when this would be used?
More of a QOL feature.
Supporting information
No response

Can you be more descriptive on what you are looking for? I have no idea if you are referring to a specific PowerToy Utility, or a suggestion for a new Utility, or something else. /needinfo


boost-errors when compiling library

Hi!
I want to use this library for making the ems-collector able to send and receive MQTT.
The compiler throws errors like this:
MqttAdapter.cpp:41:22:   required from here
/usr/include/boost/multi_index/composite_key.hpp:460:53: error: no match for call to ‘(const std::less<short unsigned int>) (const std::tuple<short unsigned int, unsigned char>&, short unsigned int)’
     if(comp.get_head()(vc.get_head(),c.get_head()(v)))return true;
                                                     ^
In file included from /usr/include/c++/4.9/string:48:0,
                 from /usr/include/c++/4.9/random:40,
                 from /usr/include/c++/4.9/bits/stl_algo.h:66,
                 from /usr/include/c++/4.9/algorithm:62,
                 from MqttAdapter.cpp:20:
/usr/include/c++/4.9/bits/stl_function.h:367:12: note: candidate is:
     struct less : public binary_function<_Tp, _Tp, bool>
            ^
/usr/include/c++/4.9/bits/stl_function.h:370:7: note: bool std::less<_Tp>::operator()(const _Tp&, const _Tp&) const [with _Tp = short unsigned int]
       operator()(const _Tp& __x, const _Tp& __y) const
       ^
/usr/include/c++/4.9/bits/stl_function.h:370:7: note:   no known conversion for argument 1 from ‘const std::tuple<short unsigned int, unsigned char>’ to ‘const short unsigned int&’
In file included from ../../mqtt_client_cpp/include/mqtt/client.hpp:24:0,
                 from ../../mqtt_client_cpp/include/mqtt_client_cpp.hpp:8,
                 from MqttAdapter.h:28,
                 from MqttAdapter.cpp:22:
/usr/include/boost/multi_index/composite_key.hpp:461:53: error: no match for call to ‘(const std::less<short unsigned int>) (short unsigned int, const std::tuple<short unsigned int, unsigned char>&)’
     if(comp.get_head()(c.get_head()(v),vc.get_head()))return false;
                                                     ^
In file included from /usr/include/c++/4.9/string:48:0,
                 from /usr/include/c++/4.9/random:40,
                 from /usr/include/c++/4.9/bits/stl_algo.h:66,
                 from /usr/include/c++/4.9/algorithm:62,
                 from MqttAdapter.cpp:20:
/usr/include/c++/4.9/bits/stl_function.h:367:12: note: candidate is:
     struct less : public binary_function<_Tp, _Tp, bool>
            ^
/usr/include/c++/4.9/bits/stl_function.h:370:7: note: bool std::less<_Tp>::operator()(const _Tp&, const _Tp&) const [with _Tp = short unsigned int]
       operator()(const _Tp& __x, const _Tp& __y) const
       ^
/usr/include/c++/4.9/bits/stl_function.h:370:7: note:   no known conversion for argument 2 from ‘const std::tuple<short unsigned int, unsigned char>’ to ‘const short unsigned int&’
Makefile:49: recipe for target 'MqttAdapter.o' failed
make: *** [MqttAdapter.o] Error 1
bananapi@fhem:/home/bananapi/ems-collector/collector$

I have discussed the issue with the author of ems-collector, but without success:
https://github.com/maniac103/ems-collector/issues/18
Can you give me the right hint to resolve that?

My -std=c++14 was on -std=c++1y and tat did cause the errors. Fixed now.

It seems that the error is caused by https://svn.boost.org/trac/boost/ticket/10315
It is fixed as  https://github.com/boostorg/multi_index/commit/6d6bb7550460503b27da72c2c583344b1e99f50b
Which version of the boost library are you using? If it is 1.55 or older, please update 1.57 or newer.

The standard library is 1.55 in Debian Linux
https://packages.debian.org/jessie/libboost-all-dev

Thanks, redboltz. I'll update my readme accordingly. It would be great if you could update your readme to list the requirements of boost 1.57 and c++14 (which isn't bitfield only anymore,  it's also required for auto in lambda parameters).

Compile worked with c++1y also

@maniac103 , I updated README.md. Also I removed generic lambda from the library code.
I close the issue. Thank you for your cooperation.
If there are any problems, please reopen the issue.

I can confirm the library compiles fine again with GCC and -std=c++0x. Thanks!


[feat] Use Ulysses/FastSeq for QKV computation in DiT/Latte/MMDiT

--Borrowed from OpenDiT--
FastSeq boosts performance thanks for improved attention memory communication time
https://github.com/NUS-HPC-AI-Lab/OpenDiT?tab=readme-ov-file#fastseq
Example diff implementation on top of existing DiT/Latte
https://github.com/NUS-HPC-AI-Lab/OpenDiT/pull/92/commits/d7be4992cbe028c7068f35e8463f9ce1003aabb1
Utility functions reference:
https://github.com/kabachuha/OpenMMDiT/blob/d7be4992cbe028c7068f35e8463f9ce1003aabb1/opendit/utils/operation.py#L1

This PR has it as a part of OpenDiT borrowing https://github.com/PKU-YuanGroup/Open-Sora-Plan/pull/73

I will check it.


Various improvements on the FSLeyes run script

Look for the TODOs in the file:
https://github.com/neuropoly/spinalcordtoolbox/blob/master/contrib/fsl_integration/sct_plugin.py

Looks like there is a good chunk of improvements that can be made to the plugin. Will tackle this.

I noticed that sct_plugin.py is not an actual FSLeyes plugin, but instead a runtime script that can be executed by FSLeyes. Do we want to migrate to code to an actual plugin structure (https://users.fmrib.ox.ac.uk/~paulmc/fsleyes/userdoc/latest/plugins.html#for-developers) ?

I noticed that sct_plugin.py is not an actual FSLeyes plugin, but instead a runtime script that can be executed by FSLeyes.

yup! sorry for the confusing title (now fixed)

Do we want to migrate to code to an actual plugin structure (https://users.fmrib.ox.ac.uk/~paulmc/fsleyes/userdoc/latest/plugins.html#for-developers) ?

good question. I see pros/cons. We have another project (AxonDeepSeg), for which we created an actual FSLeyes plugin, and I found some issues with the plugin features. Notably:

when fsleyes is installed within a venv and we install a plugin in it, fsleyes will write under the ~/.fsleyes unique folder. Meaning: if people have another fsleyes software, which was installed as an app (vs. pip install within the venv), everytime people open this fsleyes app, it will complain that it cannot find the pluging. That's annoying.
we need add a layer of version tracking for the plugin if we make it a plugin: when people install the plugin for the first time, they have the possibility to have it everytime they open fsleyes. If they decide to do so, fsleyes will copy the plugin (simple copy of the .py file) under ~/.fsleyes/. 3 months later, SCT is updated, but the plugin is not...

Both issues mentioned above seem like shortcomings of FSLeyes in my opinion. We could submit issues to the project.
Technically speaking I don't see any value added  to refactor into a plugin since you have something that works and does what you need it to do. Moving to a plugin architecture, although it may be architecturally cleaner, will introduce the complications mentioned above.
The only pro is that users are generally more aware about loading plugins (for example this is what I tried to do at first, but failed) vs running scripts, but at this point they can simply read the docs and see how to load the script properly (again, what I did).

Below is a breakdown of some of the TODOs currently in the code and associated comments/questions:

# TODO: display error if number of input arguments is not correct

Ok, but is this something useful if the user doesn't event have control over what input arguments are passed? Right now it looks like he can only select some input parameters (e.g contrast) and press run. Showing him that the number of input params is wrong is not useful for the user, instead I propose to refactor the existing ErrorDialog class to accept a specific error msg and present the user with a relevant error message.

# TODO: add shortcuts to Run

Not sure what that means.

# TODO: add help when user leaves cursor on button

Sure can be done by catching mouse events and showing a wx.TipWindow()

# TODO: try to use MessageBox instead, as they already include buttons, icons, etc.

(In the context of ProgressDialog) : it is better to keep the custom dialog since the MessageBox does not offer the flexibility to customize the contents of the dialog and also does not allow to have a dialog with just the cancel button (surprisingly).

# TODO: retrieve action from the cancel button

(In the context of ProgressDialog): sure, in this case I assume that we want to cancel the current command that was run. In that case we can use Popen.send_signal(CTRL_C_EVENT) or Popen.terminate()
I have a few general comments about the current implementation:

Is there a reason that this runtime script that lives in the repo does not use shared memory as IPC, but instead subprocess.Popen()? It's seems to be a hybrid between plugin/runtime script.
The user doesn't have any visibility on what is happening (unless he has a terminal open). It would be useful to have at a text box with some updates and the output of the subprocess.Popen() calls at least (since the error dialog isn't very helpful..)
If this runtime script is meant to be serious feature of the toolbox we should probably consider refactoring it into a proper plugin architecture, rework the IPC to at least have real time progress, proper error messages, etc and make some UX improvements. This would make it easier to extend in the future and improve the overall experience. Otherwise I can fix the above in a few hours and not refactor too much.

Below is a breakdown of some of the TODOs currently in the code and associated comments/questions:

# TODO: display error if number of input arguments is not correct

Ok, but is this something useful if the user doesn't event have control over what input arguments are passed? Right now it looks like he can only select some input parameters (e.g contrast) and press run. Showing him that the number of input params is wrong is not useful for the user, instead I propose to refactor the existing ErrorDialog class to accept a specific error msg and present the user with a relevant error message.

agreed-- we could remove this todo

# TODO: add shortcuts to Run

Not sure what that means.

IIRC this is a suggestion for adding a keyboard shortcut (e.g. CTRL+R) for running the script. Definitely not a priority.

# TODO: add help when user leaves cursor on button

Sure can be done by catching mouse events and showing a wx.TipWindow()

👍

# TODO: try to use MessageBox instead, as they already include buttons, icons, etc.

(In the context of ProgressDialog) : it is better to keep the custom dialog since the MessageBox does not offer the flexibility to customize the contents of the dialog and also does not allow to have a dialog with just the cancel button (surprisingly).

👍

# TODO: retrieve action from the cancel button

(In the context of ProgressDialog): sure, in this case I assume that we want to cancel the current command that was run. In that case we can use Popen.send_signal(CTRL_C_EVENT) or Popen.terminate()

👍

I have a few general comments about the current implementation:

Is there a reason that this runtime script that lives in the repo does not use shared memory as IPC, but instead subprocess.Popen()? It's seems to be a hybrid between plugin/runtime script.

i have no idea, but please take the liberty to explore further if you see potential improvements.

The user doesn't have any visibility on what is happening (unless he has a terminal open). It would be useful to have at a text box with some updates and the output of the subprocess.Popen() calls at least (since the error dialog isn't very helpful..)

yes! that would be awesome indeed.

If this runtime script is meant to be serious feature of the toolbox we should probably consider refactoring it into a proper plugin architecture, rework the IPC to at least have real time progress, proper error messages, etc and make some UX improvements. This would make it easier to extend in the future and improve the overall experience. Otherwise I can fix the above in a few hours and not refactor too much.

hum, i see. So you think there are strong pros for making it a plugin (as opposed to a script), despite my list of cons above?
The current user situation is the following:

we have a significant amount of users who would welcome a GUI (this has been a repetitive feature request),
one downside of FSLeyes is that it does not work on windows, although we now have a fairly good (although not "super easy to install") workaround with WSL: https://github.com/neuropoly/spinalcordtoolbox/pull/2643
pros of FSLeyes: a large body of our users are familiar with this software (and have it installed already);
FSLeyes is an active project (there was recently a new release that came out, with interesting new features: see twitter post)

so, all in all, i think it is reasonable to spend efforts in further improving the FSLeyes-based GUI. Making it a plugin? i am not sure what would be the long terms implications (pros/cons).

Ok got it will add the improvements mentioned above.


"Appears to be a git repo or submodule" error w/ npm 3

npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/bin/iojs" "/Users/casey/.npm/bin/npm" "install"
npm ERR! node v4.1.0
npm ERR! npm  v3.2.1
npm ERR! path /Users/casey/Code/UniversitySite/node_modules/flippant
npm ERR! code EISGIT

npm ERR! git Appears to be a git repo or submodule.
npm ERR! git     /Users/casey/Code/UniversitySite/node_modules/flippant
npm ERR! git Refusing to remove it. Update manually,
npm ERR! git or move it out of the way first.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/casey/Code/UniversitySite/npm-debug.log

and relevant package.json section
"napa": {
  "flippant": "mintchaos/flippant.js",
}

My current workaround modifying the install script in package.json to napa && rm -rf node_modules/*/.git/

Ah interesting. Yeah that would be good to fix. Thanks for reporting!

I can probably take care of this.

:sunglasses: :+1:

Fixed on dcfa42d

Still happening in 2.0.1 as far as I can tell:
"scripts": {
    "install": "napa"
  },
  "napa": {
    "js-marker-cluster": "googlemaps/js-marker-clusterer"
  }

$ ls -al node_modules/js-marker-cluster
total 584
drwxr-xr-x   14 anahkiasen  staff     476 Oct 13 11:31 .
drwxr-xr-x  894 anahkiasen  staff   30396 Oct 13 11:31 ..
drwxr-xr-x   13 anahkiasen  staff     442 Oct 13 11:31 .git
-rw-r--r--    1 anahkiasen  staff     322 Oct 13 11:31 AUTHORS
-rw-r--r--    1 anahkiasen  staff    1184 Oct 13 11:31 CONTRIBUTING.md
-rw-r--r--    1 anahkiasen  staff     505 Oct 13 11:31 CONTRIBUTORS
-rw-r--r--    1 anahkiasen  staff   11324 Oct 13 11:31 LICENSE
-rw-r--r--    1 anahkiasen  staff    1473 Oct 13 11:31 README.md
-rw-r--r--    1 anahkiasen  staff     505 Oct 13 11:31 bower.json
drwxr-xr-x    4 anahkiasen  staff     136 Oct 13 11:31 docs
drwxr-xr-x    7 anahkiasen  staff     238 Oct 13 11:31 examples
drwxr-xr-x   16 anahkiasen  staff     544 Oct 13 11:31 images
-rw-r--r--    1 anahkiasen  staff  263841 Oct 13 11:31 screenshot.png
drwxr-xr-x    4 anahkiasen  staff     136 Oct 13 11:31 src

$ npm install scriptjs --save
npm ERR!  Update manually,
npm ERR! git or move it out of the way first.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/anahkiasen/Sites/madewithlove/weholi/npm-debug.log

@shama I have pushed a fix to master, I need to bump version and publish to npm (if you trust me)
@Anahkiasen this will be published shortly, in the meantime if this is blocking, you can install napa via shama/napa in your package.json. This will just install from master's HEAD commit.

@caseyWebb Yep! I've added you as an owner (at least I hope it is you on npm, https://www.npmjs.com/~caseywebb). I consider any significant contributor to any project I've started to have the same level of ownership as myself. So feel free to make and publish any changes you see fit. I really appreciate your help!
I use this script: https://www.npmjs.com/package/npm-release to publish releases as it will commit, tag and publish in one swoop. But I know there is plenty of other tooling. Feel free to use whatever suits you best.

Hello,
The same thinks now :
`npm ERR! Linux 3.16.0-4-amd64
npm ERR! argv "/home/sofiane/.nvm/versions/node/v6.7.0/bin/node" "/home/sofiane/.nvm/versions/node/v6.7.0/bin/npm" "install"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.3
npm ERR! path /home/sofiane/sygefor/node_modules/jquery-slimscroll
npm ERR! code EISGIT
npm ERR! git /home/sofiane/sygefor/node_modules/jquery-slimscroll: Appears to be a git repo or submodule.
npm ERR! git     /home/sofiane/sygefor/node_modules/jquery-slimscroll
npm ERR! git Refusing to remove it. Update manually,
npm ERR! git or move it out of the way first.`
best regards,

I'm also seeing this. What's the workaround?

Just for reference - I had this issue when publishing my module.
Refer to NPM "files"
It's a safer & less tedious way than using .npmignore

For reference after I searched around for this a while the do the following to fix this issue.

Run npm pack check the logs and see if anything is being packed from .git
For me it was .git/index im not exactly sure the cause but adding .git to the .gitignore fixed this for me. I believe this is safe since Git will ignore that entry.


Edit by text - Feature

Dear WyattBlue,

As an enthusiastic user of Auto-Editor, I have a suggestion for a new feature that would extend the tool's functionality: An "Edit By Text" feature. This feature would allow cutting videos based on the transcribed text. For example, one could remove specific words, sentences, or sections from the video by selecting and deleting the corresponding text.

I often produce video tutorials where I speak. It happens regularly that I misspeak, use filler words, or have passages that I would prefer to cut out afterwards. With an "Edit By Text" feature, I could quickly find and remove these parts in the transcript without having to search for them manually. This would significantly speed up my workflow and improve the quality of my videos.
In the CLI tool, parameters like --cut_words "uhm" or --cut_sentence "This was a bad take" could be introduced for this purpose. In the GUI, it would be awesome if one could see the transcript with timestamps and then cut out specific parts of the video with a click or key combination.

This feature would have a great added value for me personally. While there are some providers that offer such a feature, they are often very expensive. An integration into Auto-Editor would allow me and many other content creators to optimize our videos more easily and quickly without having to dig deep into our pockets.

I am using the latest version of Auto-Editor.
Best regards,
Jay

I forgot to mention: i could be implemented by integration of whisperx

You can already do this with little monetary cost, although it’s a bit manual. You can use a audio transcription tool (like whispercpp) to transcribe the audio, mux it in with the video, then use
--edit subtitle:regex=um or similar.
Related, I don’t believe this is a good idea. This program isn’t a full-fledged video editor, nor is it a transcription app. Implementing these significantly inflate the project’s size and broadens the scope of the project.


Install pypi dependencies and run all commands from activated anaconda envs

Currently, tox-conda does not activate an anaconda environment, this has some drawbacks:

some anaconda packages set environment variables that are only accessible in an activated environment,
the PATH environment variable lacks some search paths on Windows (#24),
Numpy have troubles on Windows (#37).

This PR fixes these issues not by activating an anaconda environment but by using the conda run command which can run an arbitrary command from a temporarily activated environment.
With this PR, I no longer have to add the following workaround on Windows:
setenv =
    CONDA_DLL_SEARCH_MODIFICATION_ENABLE = 1
    PATH = {envdir}{:}{envdir}\Library\mingw-w64\bin{:}{envdir}\Library\usr\bin{:}{envdir}\Library\bin{:}{envdir}\Scripts{:}{envdir}\bin{:}{env:PATH}

Hi @gaborbernat, will you have a chance to give a look at this PR?

https://github.com/tox-dev/tox-conda/releases/tag/0.8.0


feat(mount): request remount when volume mount becomes read only

ref: https://github.com/longhorn/longhorn/issues/6386
- VolumeController periodically use engineProxyClient to request instance-manager to check the globalMountPoint of the Volume
- If it is read only, we request remount of the pod by adding requestRemountAt

Instance-Manager will periodically monitor the volume mount point and update the engine status
Engine/Replica will sync the errorMsg from Instance-Manager
Volume then check the Engine CRD to get the errorMsg

Pros:
using errorMsg to get the information from process allow us to extend the feature for more situations.
Blocked by: https://github.com/longhorn/longhorn-instance-manager/pull/316

Is this ready for review? What's does [BLOCKED] mean? If not ready, just mark this PR draft.

Is this ready for review? What's does [BLOCKED] mean? If not ready, just mark this PR draft.

It is blocked by the PR: https://github.com/longhorn/longhorn-instance-manager/pull/316
instance-manager PR needs to merge first so this can update the vendor
I will change it to draft, thanks

Hi @c3y1huang @derekbit
This PR has been fixed, PTAL, thanks!


Run the Employee Onboarding Sample Scenario

Tutorial URL: https://developers.sap.com/tutorials/cp-starter-ibpm-employeeonboarding-5-run.html
Please specify the step you are referring to: Step1: Set up sample events for workflow
5.The sentence should be choose Filter select Process Definition ID  and enter onboard to see all the imported events.
Expected:

Actual:

Regards,
Nidhi

Updated the tutorial.
@thecodester - close the issue


Unable to save project with virus objects

I am getting the following error:
Traceback (most recent call last):
File "C:\Users---\AppData\Local\Continuum\anaconda3\envs\herbs\lib\site-packages\herbs\herbsgui.py", line 5532, in save_project_called
data_2d = self.get_hist_single_layer_vis_data(single_layer_link)
File "C:\Users---\AppData\Local\Continuum\anaconda3\envs\herbs\lib\site-packages\herbs\herbsgui.py", line 5188, in get_hist_single_layer_vis_data
pnt_vec = np.stack([temp[1], temp[0]], axis=1) + 0.5
IndexError: tuple index out of range

Hi Natalie, Sorry for the late reply. I will check and come back to you on this. Which version are you using?

Hi Jingyi, so glad to hear from you!
Thank you! I am using Herbs 0.2.2.

Hi Jingyi, hi Natalie,
For future reference, I've been encountering the same issue with Herbs 0.2.2, both with a Python 3.8.10 and a Python 3.9.16 conda environment.

I'm having the same issue on Win10 with Python 3.8.16 and Herbs 0.2.2.
Project saves without issue once the virus object removed.
Fingers crossed this can be solved because so far this has been the best registration/visualization tool I've come across!

Thank you all for reporting this issue. Last week was Easter holiday in Norway, so I was not at work. I am in the process to update my operating system through University system( all files will be cleaned up afterwards), so I have to wait until IT guys finish this. Sorry for the delay. I will update you all after I have a working computer. And please do report other issues if any during this period.

Hi, bug fixed in HERBS 0.2.3. Thank you all again for reporting this issue and waiting for so long! Please do let me know if there is further problems.


fix semantic-release setup to follow latest rules

Semantic-release was setup for this repo but it was not working and not following our latest setup with BUGFIX-RELEASE: etc. prefixes.

Let's see if it works :)

Did not: https://travis-ci.com/github/adobe/node-cgroup-metrics/jobs/363544630
Not quite sure what the issue is, but I see these discrepancies:

it ran the release stage on Windows (why?), but we say  condition:  $TRAVIS_OS_NAME == linux so it skipped it, doing no release
it run npm run report-coverage which failed as it did not run npm test before (we don't need to report coverage here)

Ok, possible answers:

the .travis.yml here listed windows before linux, maybe that tells Travis what OS to use for the release/deploy stage

this seems to happen everywhere, but get ignored. see here, expand the npm run report-coverage part in the logs and see it fails too: https://travis-ci.com/github/adobe/aio-cli-plugin-asset-compute/jobs/363148121

maybe we should switch to after_script so it doesn't run after deploy (which is where we run the release): https://docs.travis-ci.com/user/job-lifecycle/

Drop the other OS from travis.yml: https://github.com/adobe/node-cgroup-metrics/blob/master/.travis.yml#L12
This will be a start. Also drop https://github.com/adobe/node-cgroup-metrics/blob/master/.travis.yml#L17, we already test 10.15 and 10.19 (should reduce wait times too).
And there seems to be a syntax issue: https://github.com/adobe/node-cgroup-metrics/blob/master/.travis.yml#L39, there should only be one = for the test, according to documentation (https://docs.travis-ci.com/user/deployment-v2/conditional)

https://github.com/adobe/node-cgroup-metrics/pull/24

See #25.

#25 mostly worked, and semantic-release was triggered, but now it failed with This operation requires a one-time password from your authenticator. because likely the github token set in travis is old and needs a new one. Will try to update it.

Latest try in #27.

Worked!

Regarding 2. from above: after_script did not help, it also runs on the release stage, see https://travis-ci.com/github/adobe/node-cgroup-metrics/jobs/363568375
But it doesn't fail it either, so we can just keep ignoring it. Suggest we stick to after_success.


Validation issue with +234906180XXXX (NG)

Country/region affected : NG
Example number: +2349061804869
The phone number range to which the issue applies ("+234 90 6XXX-XXXX"):
The type of the number(s) ("fixed-line", "mobile", "short code", etc.):
Supporting evidence (for example, national numbering plan, announcement from mobile carrier, news article): https://en.wikipedia.org/wiki/Telephone_numbers_in_Nigeria
link to demo

Hi,
Thanks for providing all the details we need! We've accepted this issue and will fix this in an upcoming release.
Please note that you have submitted this information with the knowledge that we may use, modify, reproduce, publicly display, and distribute the information in accordance with our open source policies. Please let us know if you did not intend to submit the information for such use.

Fixed in release 8.0.1.


Fix #880

Fix #880
The addition to CaseGenerator provides the specific file that the test cases are being pulled from. It makes the Go To Test VS action go to the actual test source file and not the C# adapter file. This is a new feature in the most recent release of the Nunit Test Adapter here and here

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


Cannot analyze/select queries with Postgres arrays in params

DjDT currently doesn't support PostgreSQL Array syntax and returns 500 when trying to analyze or reselect queries that contain Postgres arrays in params.
From the looks of it DjDT query tracker assumes no nested values when serializing query params. The error occurs when these incorrectly serialized params are fed into the cursor.

The toolbar also doesn't support queries with contains or contained_by on a HStoreField and any of the RangeFields.

@aaugustin Do you know if there was a reason why we chose to create our own _decode rather than pickling the params? I'm thinking we may want to convert to pickling the params since the range fields need to have the actual class instance passed as the parameter.
Right now the toolbar is decoding a parameter of (NumericRange(0, 999999, '[)'),) to be '["NumericRange(0, 999999, \'[)\')"]' which when the form cleans and outputs the parameters it becomes "NumericRange(0, 999999, \'[)\')"

I don't know. If you have an idea to fix the problem, please go ahead :-)


Downloader unwind method

Complete the implementation of the downloader unwind method.
Test are still missing.

LGTM. @AndreaLanfranchi have your concerns been addressed?

No other concerns atm ... would suggest @mriccobene a pass on changed files to clear Clang-Tidy suggestions by Clion (I know he uses it).
One small issue only. In sentry_client.hpp
class SentryClient : public rpc::Client<sentry::Sentry> {
  public:
    using base_t = rpc::Client<sentry::Sentry>;

    // ...

    void exec_remotely(SentryRpc& rpc);  // send a rpc request to the remote sentry

    // ...
};

exec_remotely is a non virtual function of rpc::Client<sentry::Sentry>
As the implementation is
void SentryClient::exec_remotely(SentryRpc& rpc) { base_t::exec_remotely(rpc); }

why hide it in the inherited class ?

@AndreaLanfranchi I will check Clang-Tidy suggestions in a future PR even if I and Clang-Tidy don't get along.
Also SentryClient will be completely rewritten in a following PR where I will introduce gRPC reconnect logic.
Please note that your requested changes has been implemented in past commits.


Provide a clear log message when a cluster can't be handled

When a cluster is missing its id.k8s.io cluster claim, it can't be handled. There was no indication that this was happening except a debug log message that is not displayed by default. This commit makes the log message clearer and changes it to a regular info log.
Relates:
https://issues.redhat.com/browse/ACM-2625

/cc jlpadilla
/cc xrajesh
/cc SherinV
/cc zlayne

/lgtm
/hold

@SherinV could you please merge this?


Update manifest.xml

Add Epix2 support

Thanks @hyzteric, I'll integrate this and deploy a new version next week. Have you tested that it works as expected for your model?

Hi @zmullett , I only tested it on the simulator but it worked well! I could connect to my own Sonos installation right away.


Start a new line at last indent

A feature request to start every new line at the last indent location.

Atom already does this, doesn't it?  Can you give some steps to show where Atom gets this wrong?

Any news on this?

It already does.  To reproduce: cmd-n to create a new file, hit tab, then hit return.  Your new line is at the same indent as the previous.  I also see this working in JS and Ruby.
Can you describe steps to reproduce a failure?

There was this issue, but it was quite a while ago: https://github.com/atom/atom/issues/8013

Apologies, a new user to this Package and the problem was on my end. Thanks for the quick reply, amazing work regardless.

You're welcome, glad it was an easy answer.
And, really, someone could close this issue.  :)


Form Not Clearing via Reducer Plugin (Regression in v5.2.5)

Since v5.2.5, clearing the form with method "A" on this page no longer works.
I have made a JSFiddle that demonstrates the issue:
https://jsfiddle.net/minznerjosh/aLc0uvxw/6/
If you like, I could look at fixing the issue myself and send a PR. I could get it done sometime tomorrow.
P.S. Thanks for all your work on redux-form! I've been using it quite extensively for a new app I've been building and it's been great overall!

@minznerjosh would you be willing to update us on the status of this ticket?

@danielrob I'm afraid I'm now using v6+ so I'm not sure what the status of this is.

Thanks for the update! v5 is on sort of PRs accepted support level now so I'll go ahead and close this :).


controller.calculateProfit doesn't work properly with sqlite database

In this test replace
require.NoError(t, err)

with
require.NoError(t, err)
defer func() {
	os.RemoveAll(file.Name())
}()

storage, err := storage.FromSQL(sqlite.Open(file.Name()), &gorm.Config{})
require.NoError(t, err)

and run this test. You will see the following error:

Hi @magicaleks, thank you for your report. I tried testing the controller using SQL storage, and it seems to be working normally. Perhaps the error stems from your file creation process.
In sqlite package, you can specify a filename instead of manually creating the file. It will be created if it doesn't already exist.

FYI: calculateProfit was updated to updatePosition nine months ago. Please ensure you're using the latest version.

Hi @panapol-p
I see function calculateProfit was refactored by @rodrigo-brito in this PR: https://github.com/rodrigo-brito/ninjabot/pull/276
And now it uses map position map[string]*Position. But this will not work if we restart bot when we have open position.
Does it make sense to derive positions from persistence database?

Hi @magicaleks
Is expected to fail if you drop the database.
In the current version, we do not load the position info from the storage in case of restart.
In your test, are you dropping the database? I think this is something wrong, it is not a expected behaviour

@rodrigo-brito the issue was tested on old version of ninjabot when we tried to use sql database with old implementation of calculateProfit method. It is no longer reproduced on latest version but, it seems there is an issue when we restart the bot when we have an open position

sure, it is something that requires improvements.
Currently, we do no support load open positions after a restart, we do not store the state of avg price.
It is something that is not too much complex to deal, I will try to work on this feature.

It is something that is not too much complex to deal, I will try to work on this feature.

It would be really helpful. If you don't mind, could you describe how would you do it? Maybe I can implement it myself

The main change is:
When the bot initialize, it executes a query in the local database looking for open positions, calculate the average price for each pair and store it in memory (controller)