Issues with ESP after flashing the firmware to a 433Bridge R2 V2.2

I don't know what I did wrong, I followed the tutorial and flashed the Passthrough-firmware to the Sonoff 433Bridge R2 V2.2 (2021.01.19):
>python flashScript.py
Available COM ports:
1. COM1 - Kommunikationsanschluss (COM1)
2. COM6 - USB-SERIAL CH340 (COM6)
Select a COM port (enter the number): 2
2024-10-03 18:55:27,168 - INFO - Serial connection opened on COM6
Select a file by number:
1. blink.ihx
2. main_passthrough_OB38S003.hex
Enter the number of the file you want to select: 2
2024-10-03 18:55:29,211 - INFO - You selected: main_passthrough_OB38S003.hex
2024-10-03 18:55:30,315 - INFO - handshake
2024-10-03 18:55:30,316 - INFO - State changing to handshake
2024-10-03 18:55:30,318 - INFO - cycle power to target (start with power off and then turn on)
2024-10-03 18:55:33,812 - INFO - Handshake succeeded
2024-10-03 18:55:33,930 - INFO - Status: 0
2024-10-03 18:55:33,931 - INFO - Success
2024-10-03 18:55:33,933 - INFO - Chip read: 0xA
2024-10-03 18:55:33,934 - INFO - Connected...
2024-10-03 18:55:33,937 - INFO - Returning to idle state...
2024-10-03 18:55:34,038 - INFO - erase
2024-10-03 18:55:34,539 - INFO - Erasing chip...
2024-10-03 18:55:34,540 - INFO - Status: 0
2024-10-03 18:55:34,541 - INFO - Success
2024-10-03 18:55:34,542 - INFO - Chip erase successful
2024-10-03 18:55:34,643 - INFO -
2024-10-03 18:55:35,143 - INFO - setfuse 18 249
2024-10-03 18:55:35,644 - INFO - Set configuration byte...
2024-10-03 18:55:35,645 - INFO - Status: 0
2024-10-03 18:55:35,646 - INFO - Success
2024-10-03 18:55:35,647 - INFO - Wrote configuration byte
2024-10-03 18:55:35,653 - INFO - :03000000020006F5
2024-10-03 18:55:35,656 - INFO - Write successful
2024-10-03 18:55:35,660 - INFO - Wrote 3 bytes
2024-10-03 18:55:35,673 - INFO - :09005F0075080075090002000398
2024-10-03 18:55:35,681 - INFO - Write successful
2024-10-03 18:55:35,684 - INFO - Wrote 9 bytes
2024-10-03 18:55:35,689 - INFO - :0300030002008870
2024-10-03 18:55:35,692 - INFO - Write successful
2024-10-03 18:55:35,694 - INFO - Wrote 3 bytes
2024-10-03 18:55:35,704 - INFO - :10006800D2809000141200E4C28022D2B09003E83B
2024-10-03 18:55:35,720 - INFO - Write successful
2024-10-03 18:55:35,722 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,733 - INFO - :100078001200E4C2B0D2B09003E81200E4C2B02289
2024-10-03 18:55:35,748 - INFO - Write successful
2024-10-03 18:55:35,751 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,759 - INFO - :1000880012010812012AC2B0C280C287C290C29768
2024-10-03 18:55:35,774 - INFO - Write successful
2024-10-03 18:55:35,777 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,784 - INFO - :100098001200739001F41200E4D2B012010C1201A4
2024-10-03 18:55:35,800 - INFO - Write successful
2024-10-03 18:55:35,803 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,810 - INFO - :1000A80026AF08A296E433F508EFB50802800AE502
2024-10-03 18:55:35,826 - INFO - Write successful
2024-10-03 18:55:35,828 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,836 - INFO - :1000B800086004D2908002C290AF09A291E433F59F
2024-10-03 18:55:35,852 - INFO - Write successful
2024-10-03 18:55:35,854 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,862 - INFO - :1000C80009EFB5090280D7E5096004D28780CFC25D
2024-10-03 18:55:35,877 - INFO - Write successful
2024-10-03 18:55:35,880 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,888 - INFO - :1000D8008780CBAF828F061FEE70FA22AE82AF8385
2024-10-03 18:55:35,903 - INFO - Write successful
2024-10-03 18:55:35,906 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,914 - INFO - :1000E8007C007D00C3EC9EED9F50147A957B051A29
2024-10-03 18:55:35,929 - INFO - Write successful
2024-10-03 18:55:35,932 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,939 - INFO - :1000F800BAFF011BEA4B70F70CBC00E80D80E52243
2024-10-03 18:55:35,955 - INFO - Write successful
2024-10-03 18:55:35,957 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,965 - INFO - :10010800538E8F2275F75575F7AA75F75A75B62865
2024-10-03 18:55:35,980 - INFO - Write successful
2024-10-03 18:55:35,983 - INFO - Wrote 16 bytes
2024-10-03 18:55:35,990 - INFO - :100118002275F75575F7AA75F75A53B6DF2275B7E2
2024-10-03 18:55:36,006 - INFO - Write successful
2024-10-03 18:55:36,008 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,016 - INFO - :10012800552253D3FE43D20153D37F43D28053D5B4
2024-10-03 18:55:36,032 - INFO - Write successful
2024-10-03 18:55:36,034 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,042 - INFO - :100138007F43D48053DBFE43DA0122439180D29E71
2024-10-03 18:55:36,058 - INFO - Write successful
2024-10-03 18:55:36,060 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,071 - INFO - :1001480043878043D91075BA0375AACC22D2992265
2024-10-03 18:55:36,086 - INFO - Write successful
2024-10-03 18:55:36,088 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,096 - INFO - :10015800D2AC22C2AC2243C9202253C9DF22AE82CC
2024-10-03 18:55:36,112 - INFO - Write successful
2024-10-03 18:55:36,114 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,122 - INFO - :10016800AF8343890143D9018F8C8E8AD28C224375
2024-10-03 18:55:36,138 - INFO - Write successful
2024-10-03 18:55:36,140 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,148 - INFO - :10017800892043D90422AE82AF838F8C8E8A227560
2024-10-03 18:55:36,164 - INFO - Write successful
2024-10-03 18:55:36,166 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,174 - INFO - :10018800C16075C8D122A2AFE433F58222AFC37E25
2024-10-03 18:55:36,189 - INFO - Write successful
2024-10-03 18:55:36,192 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,199 - INFO - :1001980000ACC27D00EC4206ED42078E828F8322BE
2024-10-03 18:55:36,215 - INFO - Write successful
2024-10-03 18:55:36,217 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,225 - INFO - :1001A80053C9FD228581822285820A85830B85F0C9
2024-10-03 18:55:36,241 - INFO - Write successful
2024-10-03 18:55:36,243 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,253 - INFO - :1001B8000CF50D900003E4F5F01201DDAC82AD837F
2024-10-03 18:55:36,269 - INFO - Write successful
2024-10-03 18:55:36,271 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,279 - INFO - :1001C800AEF0C313FFEE13FEED13FDEC13F5828DB5
2024-10-03 18:55:36,294 - INFO - Write successful
2024-10-03 18:55:36,297 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,303 - INFO - :0501D800838EF0EF2210
2024-10-03 18:55:36,307 - INFO - Write successful
2024-10-03 18:55:36,310 - INFO - Wrote 5 bytes
2024-10-03 18:55:36,321 - INFO - :06003500E478FFF6D8FD9F
2024-10-03 18:55:36,327 - INFO - Write successful
2024-10-03 18:55:36,329 - INFO - Wrote 6 bytes
2024-10-03 18:55:36,339 - INFO - :100013007900E94400601B7A0090024F780175A0D3
2024-10-03 18:55:36,355 - INFO - Write successful
2024-10-03 18:55:36,358 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,365 - INFO - :1000230000E493F2A308B8000205A0D9F4DAF2754C
2024-10-03 18:55:36,380 - INFO - Write successful
2024-10-03 18:55:36,383 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,388 - INFO - :02003300A0FF2C
2024-10-03 18:55:36,393 - INFO - Write successful
2024-10-03 18:55:36,393 - INFO - Wrote 2 bytes
2024-10-03 18:55:36,406 - INFO - :1001DD00AAF0FBE582850AF0A4FCADF0E583850A63
2024-10-03 18:55:36,422 - INFO - Write successful
2024-10-03 18:55:36,424 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,432 - INFO - :1001ED00F0A42DFDE435F0FEE582850BF0A42DFD88
2024-10-03 18:55:36,447 - INFO - Write successful
2024-10-03 18:55:36,450 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,458 - INFO - :1001FD00E5F03EFEE433FFEA850AF0A42EFEE5F0BD
2024-10-03 18:55:36,473 - INFO - Write successful
2024-10-03 18:55:36,475 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,483 - INFO - :10020D003FFFE583850BF0A42EFEE5F03FFFE58271
2024-10-03 18:55:36,498 - INFO - Write successful
2024-10-03 18:55:36,501 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,508 - INFO - :10021D00850CF0A42EFEE5F03FFFEB850AF0A42F30
2024-10-03 18:55:36,524 - INFO - Write successful
2024-10-03 18:55:36,526 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,534 - INFO - :10022D00FFEA850BF0A42FFFE583850CF0A42FFFCB
2024-10-03 18:55:36,549 - INFO - Write successful
2024-10-03 18:55:36,552 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,561 - INFO - :0E023D00E582850DF0A42F8EF08D838C822239
2024-10-03 18:55:36,575 - INFO - Write successful
2024-10-03 18:55:36,577 - INFO - Wrote 14 bytes
2024-10-03 18:55:36,587 - INFO - :10003B007800E84400600A790175A000E4F309D860
2024-10-03 18:55:36,602 - INFO - Write successful
2024-10-03 18:55:36,604 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,612 - INFO - :10004B00FC7800E84400600C7900900001E4F0A318
2024-10-03 18:55:36,627 - INFO - Write successful
2024-10-03 18:55:36,630 - INFO - Wrote 16 bytes
2024-10-03 18:55:36,636 - INFO - :04005B00D8FCD9FAFA
2024-10-03 18:55:36,640 - INFO - Write successful
2024-10-03 18:55:36,642 - INFO - Wrote 4 bytes
2024-10-03 18:55:36,655 - INFO - :0D00060075810D12024BE5826003020003BC
2024-10-03 18:55:36,668 - INFO - Write successful
2024-10-03 18:55:36,670 - INFO - Wrote 13 bytes
2024-10-03 18:55:36,676 - INFO - :04024B007582002296
2024-10-03 18:55:36,680 - INFO - Write successful
2024-10-03 18:55:36,682 - INFO - Wrote 4 bytes
2024-10-03 18:55:36,687 - INFO - :00000001FF
2024-10-03 18:55:36,787 - INFO - mcureset
2024-10-03 18:55:37,288 - INFO - MCU reset...
Serial connection closed.

After flashing completed, the RED led turned on.
Since then, I'm unable to flash the ESP8266 on the board, as soon as I apply power to the Sonoff, even though pressing and holdinig the button (GPIO0), LED immediately turns on and stays on, so that I'm unable to flash any firmware to the device.
Do you have a clue what went wrong here?

How are you powering the Sonoff?
From what I recall it has to be 3.3V powered (5V USB power would not work), see instructions here:
https://tasmota.github.io/docs/Getting-Started/#hardware-preparation
And what are you using on PC side to flash ESP8285?
What error message does it give?

I'm powering it via 3.3V from the Serial adapter. Before flashing the RF-Bridge-OB38S003 firmware, I already flashed Tasmota to it successfully and also did the Erase.
I tried with Tasmotizer and with Tasmota Web install, all say that they cannot communicate with the Chip.
Normally, when pulling GPIO 0 to GND on startup, the chip should remain silent and wait for flash commands, but after flashing this firmware, suddenly the red LED turned on and now it stays on as soon as I apply power to the board.
Maybe the firmware is spamming the bus as soon as it gets loaded or something like that?
Did I select the wrong firmware?

If you already flashed Tasmota then I do not understand why you are trying again.
Also I do not know what firmware you flashed to the microcontroller.
I believe there is a series resistor on the transmit and receive traces connecting the ESP8285 and microcontroller.
So driving them on the ESP side connector should still work regardless (J2 connector).
However, it's at least possible that serial lines could interfere.
Make sure your adapter is connected to J2 connector.
Alternatively, you can erase flash on microcontroller so you know no code is running.
Then flash ESP with Tasmota.
Then reflash microcontroller with HEX.

If you already flashed Tasmota then I do not understand why you are trying again. Also I do not know what firmware you flashed to the microcontroller.

I had to erase Tasmota from the board again, as the instructions said so (in order to not interfere with the Microcontroller, it was recommended to erase any firmware which I did, so I removed Tasmota again before doing the procedure).
Of course, I used J2 connector for flashing Tasmota. But the hint that the Red led is from RF (as already written on the board, I should have noticed that before) at least tells me that I shouldn't pay attention to it regarding bootup status.
Is it normal that RED light fires up immedaitely after boot using your firmware? To be more precise, it turns red immediately, then it turns off for for approx 0.2 sec  and then starts again and from this point on it is permanently on.
I can try what you suggested to remove firmware from RF controller again and see if I can flash Tasmota then, still the question arises: As it is recommended to do the flash only after erasing main firmware from the ESP, would flashing still work with Tasmota firmware on the ESP without interference?

I looked again at the passthrough source code and it shows two short LED blinks, followed by a delay, and then the LED is set to on, so yes that sounds normal.
I guess you should have left Tasmota on the ESP8285, it cannot really interfere with flashing microcontroller since that flash happens over normally unconnected I2C pins. However, it is possible microcontroller can interfere with ESP flashing  because of sharing serial pins.
So the order should be erase ESP, flash Tasmota (or similar), then erase microcontroller, then flash microcontroller.
It would be nice if the hardware was arranged more like a development board with reset pins accessible/controllable etc but as is it is cumbersome.
If you can point me to where is the suggestion to erase Tasmota, I will look at it, it seems like it is bad advice.

Thanks for your fast reply, I'll try it out.
Advice is from: https://github.com/mightymos/OnbrightFlasher/blob/main/flashing-guide-by-example.md#erasing-the-esp-on-the-pcb

So from what I tested, I can say that the OB38S003 firmware really seems to have blocked ESP flshing.
As soon as I deleted the RF-Bridge-OB38S003 firmware with erase command, I was able to flash Tasmota again.
So I did as advised and flashed the passthrough mode firmware afterwards. Now I have Tasmota running and applied template
{"NAME":"RFB v2.2","GPIO":[1,1,1,1,1152,1120,1,1,1,288,1,1,1,1],"FLAG":0,"BASE":18}
(GPIO4 RfREcv, GPIO5 RfSend)
Tried to receive RF signal from a remote but nothing can be seen in the logs:
00:00:22.383 CMD: SerialLog 0
00:00:22.386 RSL: RESULT = {"SerialLog":{"0":{"Active":"0"}}}
00:00:29.655 CMD: RfProtocol a
00:00:29.663 RSL: RESULT = {"Protocol":"1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37"}

Should I try the other firmware, which directly decodes on the µC, instead or did I miss something?

Sorry for the noise, I used another RF remote now and used GPIO1 and GPIO3 (For the record, template is: {"NAME":"RFB v2.2","GPIO":[1,1120,1,1152,1,1,1,1,1,288,1,1,1,1],"FLAG":0,"BASE":18} and it received signals sometimes (only about 70% of all the time compared with other receivers that I tested). I guess it's as good as it can get.

Sorry for the noise, I used another RF remote now and used GPIO1 and GPIO3 (For the record, template is: {"NAME":"RFB v2.2","GPIO":[1,1120,1,1152,1,1,1,1,1,288,1,1,1,1],"FLAG":0,"BASE":18} and it received signals sometimes (only about 70% of all the time compared with other receivers that I tested). I guess it's as good as it can get.

No problem, yes those are the correct pins.
I don't know anything about the templates but you might consider using the one provided here (or submitting your template to that website since it applies to R2.2 hardware version):
https://templates.blakadder.com/sonoff_RF_bridge.html
It is unlikely my firmware rcswitch would be better than tasmota rcswitch because they are both based on the same decoding principle (i.e. comparing measured timings to known protocols). Passthrough seems to be preferred by most people because many more protocols are supported by tasmota due to more memory availability along with more features.
Usually the problem people have is that they do not know the protocol their fan, blinds, device, etc. is using and therefore do not know if they are receiving a valid code or not.
But in your case it's too bad it seems to be working but unreliable.
Can you post your good codes or just everything shown in your tasmota console and tell me which codes are good so I can possibly understand further?

I only had luck flashing the ESP8266 when I power it using the USB microB.

@leecher1337
Another user has had good success with sniffing remote codes using the Portisch firmware in the new release:
https://github.com/mightymos/RF-Bridge-OB38S003/releases/tag/v0.4.4
I know it is cumbersome to flash new versions, but if you flash Portisch, issue "rfraw AA B1 55" in Tasmota console interface to enter sniffing mode, then press buttons on your remote and post the output from Tasmota here we can hopefully help you to replay them so as to behave like your original remote.

Thank you very much for you kind offer for help! I did the flash for a friend of mine who owns the device and I need to get hold of it again first, that's why I didn't respond yet. Having portisch supported now in your new release looks very interesting, as that's the firmware I basically wanted to substitute for the new RF chip on this hardware.
I'll try as soon as I have the device again.

Closing for now since readme instructions for flashing have been clarified.
Please open issues as needed if testing reveals problems.

Hi,
Just wanted to report back. Portisch Firmware looks good, used it successfully on the target device now.
Thank you!

Hi, Just wanted to report back. Portisch Firmware looks good, used it successfully on the target device now. Thank you!

Great, that's good to note.


Update client-side-data.rst

Summary
Fixed some problems with some changes
Ticket Link

Hello @Sayanta66,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Closing this PR because the changes proposed within aren't changes we intend to apply to the docs.


Can cgpath be supported？

What problem does this solve or what need does it fill?
A description of why this particular feature should be added.
What solution would you like?
The solution you propose for the problem presented.
What alternative(s) have you considered?
Other solutions to solve and/or work around the problem presented.
Additional context
Any other information you would like to add such as related previous work,
screenshots, benchmarks, etc.

Do you mind providing more information about this? A quick google shows cgpath as being a Swift UI API? How would you imagine a Bevy integration here working?

Do you mind providing more information about this? A quick google shows cgpath as being a Swift UI API? How would you imagine a Bevy integration here working?

Bevy is using glam for math: https://crates.io/crates/glam
You can enable the mint feature on cgmath and glam to have compatibility between them, but cgmath won't be supported as first party.


ci: Add Winget Releaser workflow

This action automatically generates manifests for Winget Community Repository (microsoft/winget-pkgs) and submits them.
gdu is available in Winget () but is outdated. I have manually created a PR to update it for now (https://github.com/microsoft/winget-pkgs/pull/96456), but this workflow should automatically keep it up to date for the new versions.
Before merging this:

Add a classic PAT with public_repo scope as a repository secret named WINGET_TOKEN.

Fork https://github.com/microsoft/winget-pkgs under @dundee. The action will use that fork for making a branch and creating a PR with the upstream winget-pkgs repository on every release.
Install Pull on the winget-pkgs fork to ensure that it is constantly updated.

You can test out the action inputs in this playground.
If you want to see an example of a PR created using this action, see microsoft/winget-pkgs/pulls (Pull request has been automatically created using 🛫 WinGet Releaser).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 95.505%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
2656

Relevant Lines:
2781

💛  - Coveralls

Thanks for your PR!

@dundee https://github.com/dundee/gdu/actions/runs/4647275371/jobs/8224182171
Winget Releaser workflow failed. Did you forget to put the WINGET_TOKEN secret in this repo?

@dundee

@dundee

@dundee https://github.com/dundee/gdu/actions/runs/4647275371/jobs/8224182171
Winget Releaser workflow failed. Did you forget to put the WINGET_TOKEN secret in this repo?

I have manually created a PR for now: https://github.com/microsoft/winget-pkgs/pull/102030.

I have somehow miseed the step. Fixed. Thanks!

https://github.com/dundee/gdu/actions/runs/4647275371/jobs/8292671195


Add more logging

Codecov Report

Merging #242 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #242   +/-   ##
=======================================
  Coverage   94.37%   94.37%
=======================================
  Files          12       12
  Lines         693      693
=======================================
  Hits          654      654
  Misses         39       39

Continue to review full report at Codecov.

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


Pinot server side change to optimize LLC segment completion with direct metadata upload.

As designed by @npawar and @mcvsubbu , this is the second part of the code change to optimize LLC segment completion with direct metadata upload. A server config is added to control the code path to upload metadata files or not. By default, it is false.
The code here has been tested on top of #3877. It will be committed after that.

Codecov Report

Merging #3941 into master will increase coverage by 0.21%.
The diff coverage is 77.19%.

@@             Coverage Diff              @@
##             master    #3941      +/-   ##
============================================
+ Coverage        67%   67.22%   +0.21%
  Complexity        4        4
============================================
  Files          1032     1032
  Lines         51047    51102      +55
  Branches       7126     7132       +6
============================================
+ Hits          34202    34351     +149
+ Misses        14506    14395     -111
- Partials       2339     2356      +17

Impacted Files
Coverage Δ
Complexity Δ

...org/apache/pinot/common/utils/CommonConstants.java
35.55% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ot/common/protocols/SegmentCompletionProtocol.java
93.64% <100%> (-0.52%)
0 <0> (ø)

...e/pinot/common/utils/FileUploadDownloadClient.java
81.5% <100%> (+1.5%)
0 <0> (ø)
:arrow_down:

...pinot/server/starter/helix/HelixServerStarter.java
55.14% <100%> (+0.16%)
0 <0> (ø)
:arrow_down:

...altime/ServerSegmentCompletionProtocolHandler.java
50.76% <60%> (+1.67%)
0 <0> (ø)
:arrow_down:

...manager/realtime/LLRealtimeSegmentDataManager.java
71.04% <77.27%> (+0.17%)
0 <0> (ø)
:arrow_down:

...lix/EmptyBrokerOnlineOfflineStateModelFactory.java
86.66% <0%> (-13.34%)
0% <0%> (ø)

...impl/dictionary/DoubleOnHeapMutableDictionary.java
68.88% <0%> (-13.34%)
0% <0%> (ø)

.../impl/dictionary/LongOffHeapMutableDictionary.java
81.81% <0%> (-7.28%)
0% <0%> (ø)

.../impl/dictionary/FloatOnHeapMutableDictionary.java
86.66% <0%> (-6.67%)
0% <0%> (ø)

... and 19 more

Continue to review full report at Codecov.

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


Release/xumo 1

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/3885/rdkcentral/rdkservices

Commit: 978a4f67512eeb7ae138e5002a79862da8f91a0b

Report detail: gist

(The code match was spurious and I have cleared it.)


[FEATURE] Option to integrate "envoy sensors"

Describe the feature
add the (optional) functionality to read all the "envoy sensors" just like the non-custom enphase envoy integration and (DEV) integration do.
For example the "sensor.envoy_############_today_s_energy_consumption_l2"  and "sensor.envoy_############_current_power_consumption"
I like your integration but personally can't miss these sensors for statistics.
Account type

[X] Installer
[ ] DIY / DHZ
[ ] Home Owner (This integration is not (fully) functional with a home owner account!)

Envoy

[X] Metered with CTs installed (3phase)

[ ] Metered without CTs

[ ] Standard

FW version: D8.2.4264.240627

Amount of micro inverters connected: 31

Home Assistant

Version: 2024.8.2

Hi @InitialGKL, the sensors you are referring to should be available (depending on your Envoy configuration). The integration currently supports the following sensors:
sensor.envoy_xxx_batteries_available_energy
sensor.envoy_xxx_batteries_capacity
sensor.envoy_xxx_batteries_charge
sensor.envoy_xxx_batteries_power
sensor.envoy_xxx_current_power_consumption
sensor.envoy_xxx_current_power_consumption_l1
sensor.envoy_xxx_current_power_production
sensor.envoy_xxx_current_power_production_l1
sensor.envoy_xxx_current_voltage
sensor.envoy_xxx_current_voltage_l1
sensor.envoy_xxx_grid_profile
sensor.envoy_xxx_lifetime_energy_consumption
sensor.envoy_xxx_lifetime_energy_consumption_l1
sensor.envoy_xxx_lifetime_energy_production
sensor.envoy_xxx_lifetime_energy_production_l1
sensor.envoy_xxx_today_s_energy_consumption
sensor.envoy_xxx_today_s_energy_consumption_l1
sensor.envoy_xxx_today_s_energy_production
sensor.envoy_xxx_today_s_energy_production_l1
sensor.envoy_xxx_today_s_energy_production_l2
sensor.envoy_xxx_today_s_energy_production_l3
binary_sensor.envoy_xxx_grid_status

If you don't see the sensors you expect, please supply me with the debug/diagnostic information from the integration.

Yes. After removing my previous enphase envoy custom repository again, this time with extra HA restarts, your integration works as expected. Just one thing: for a succesful setup of the envoy i had to configure an increased max time for data retrieval from the envoy, i chose 300s. 60 seconds was too short, it kept failing.
Thanks!


Warnings in randomwalkbssrdf.cpp

In file included from /home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/foundation/math/quaternion.h:35:0,
                 from /home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/foundation/math/matrix.h:36,
                 from /home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/foundation/image/color.h:36,
                 from /home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/renderer/utility/dynamicspectrum.h:33,
                 from /home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/renderer/global/globaltypes.h:34,
                 from /home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/renderer/modeling/bssrdf/randomwalkbssrdf.h:33,
                 from /home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/renderer/modeling/bssrdf/randomwalkbssrdf.cpp:30:
/home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/foundation/math/vector.h:751:9: warning: ‘slab_normal’ may be used uninitialized in this function [-Wmaybe-uninitialized]
         result += lhs[i] * rhs[i];
         ^
/home/oktomus/dev/appleseedhq/appleseed.code/1.9.shared/src/appleseed/renderer/modeling/bssrdf/randomwalkbssrdf.cpp:302:22: note: ‘slab_normal’ was declared here
             Vector3f slab_normal;
                      ^

Can't we do
Vector3f slab_normal(0.0f);

?

I wouldn't want to initialize slab_normal just to silent a warning without making sure there isn't a deeper problem.
For instance, a cursory look reveals that trace_zero_scattering_path_glass() could return true without initializing slab_normal. That looks like a genuine bug.

Taken care of in #2428.


Unable to edit service alias

The wordpress-database alias referenced a service that was cloned and the original deleted.  This led to the alias referencing nothing.  When trying to edit it, to point it to it's new primary service, I encounter an overlay that prevents me from being able to do anything on the page.

Useful
Info

Versions
Rancher v1.5.9 Cattle: v0.178.12 UI: v1.5.9

Access
github admin

Orchestration
Cattle

Route
stacks.index

UI breaks in this case.  A PR has been submitted  for it.
but maybe you have to remove and re-add the service alias for now.

Version - master
Verified fixed


Lint models package

[ ] CHANGELOG.md updated
[X] Rebased/mergable
[X] Tests pass
[X] Sign CLA (if not already signed)

Updates #4098

@nuss-justin Can you rebase?  The intermittent test failure should be fixed in master.

@jwilder Rebased

Thanks @nuss-justin


Investigate build speed

We should profile our build and see if there are any perf improvements we could make as described here:
https://medium.com/coding-blocks/bringing-android-app-build-times-down-by-95-at-zomato-a505d938e9b8
Right now I think we're doing some of the anti-patterns in this article like changing BuildConfig fields.

I made #743 but it needs two more changes to get it fully incremental:

AGP update to 3.5.0 (today I failed with a non-reproducible build on the local machine and CI)
Room support for the incremental annotation processing


Added Simplified Chinese (zh_CN) translations to 3.x branch

Description of Changes
Added Simplified Chinese (zh_CN) translations to 3.x branch.

There is already a zh_CN translation on master branch, but none on 3.x branch which is the current release version. I already tested this on the GUI and it works OK.
Still updating the zh_CN translation for master branch and will prepare pull request when done some days later.
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:
suokunlong

Thanks @suokunlong for this!, we are not sure if we will have many more 3.x releases at this point since the Spyder 4.0.0 official release is in a week and a half.
Would you like to help us moving forward with the Chinese translations?
Also to help our translators, we created automatic translations using google translate whcih might make the process easier.
https://github.com/spyder-ide/spyder/pull/10812
Thanks again!

In my opinion, machine tranalation is not a good idea for localization. It will cause issues which is difficult to discover. One english word may have different meanning, one need to go to the UI and source code to determine the most proper translation. It's even better to start translate with a fresh po file.
As an experienced localizer in the LibreOffice project, I am reviewing carefully all the zh_CN strings of Spyder on master branch, and will send pull request soon.

As an experienced localizer in the LibreOffice project, I am reviewing carefully all the zh_CN strings of Spyder on master branch, and will send pull request soon.

@suokunlong, thanks a lot for your help!! We'll close PR #10812 as soon as you send yours.
I'm also going to close this one because we don't plan to do more releases for Spyder 3.


Update igc_lib.py

Stating the IGC specification for the 'VAT':
Compensated variometer (total energy/NETTO) vertical speed in metres per second and tenths of metres per second with leading zero and no dot (".") separator between metres and tenths. Valid characters 0-9 and negative sign "-". Negative values to have negative sign instead of leading zero.
Proposed change in regular expression allows for negative sign in extras of B record.

Looks good. The build_from_B_record() method needs some test cases, I will add that.

Added test cases in e2406f919c142da34272af10ca49cc1ad21b95fd


Extend stars data to latest date

The GH stars data ends on the day of the latest star increase, instead of extending all the way to the current date.

Fixed in 56c7eaf


Use upstream Spotless configuration

As of https://github.com/jenkinsci/plugin-pom/pull/733 the upstream plugin parent POM provides a standard Spotless configuration that Jenkins plugins can opt into by adding a .mvn_exec_spotless file. This PR removes the custom Spotless configuration in this repository in favor of the upstream one and reformats the entire repository accordingly. The benefit of this PR is increased consistency and standardization with the rest of the Jenkins ecosystem. If this PR is accepted, the next step would be to check in a .git-blame-ignore-revs file so that this commit doesn't clutter up the Git blame view.

Thanks, @basil, much appreciated! :+1:

Thanks, @basil, much appreciated! 👍

You're welcome! I wanted to take this opportunity to remind you that as a long-time contributor, you are eligible to vote in the upcoming Jenkins Board and Officer Elections at https://community.jenkins.io/g/election-voter-2023


Fix bug in regex for scientific notation

The stray backslash prevented parsing of path strings that include
values with scientific notation, quietly claiming there was no
intersection.
Closes #18

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

By sheer co-incidence this fixes another bug which we were not able to dig into until now: https://github.com/bpmn-io/path-intersection/issues/17 :tada:.
Thanks for so much for your PR :clap:.


[Bug][dolphinscheduler-standalone-server] StandaloneServer run failed on Windows system

Since the directory separator is not the same for different operating systems, reading the pom.xml file of registry in Windows system fails.
The error message is as follows :
Exception in thread "main" java.nio.file.InvalidPathException: Illegal char <:> at index 2: ../dolphinscheduler/dolphinscheduler-standalone-server/target/classes/\../../../dolphinscheduler-registry-plugin/dolphinscheduler-registry-zookeeper/pom.xml
	at java.base/sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
	at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
	at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
	at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92)
	at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:229)
	at java.base/java.nio.file.Path.of(Path.java:147)
	at java.base/java.nio.file.Paths.get(Paths.java:69)
	at org.apache.dolphinscheduler.server.StandaloneServer.main(StandaloneServer.java:75)

can you submit a pr for this?

Ok, I will fix it soon. : )

Ok, I will fix it soon. : )

If you have submitted a pr and need a review, please ping me.

+1

We totally get rid of pom.xml now so this is not a problem anymore


Workaround issue in solution targets in MSBuild RC3

Workaround https://github.com/Microsoft/msbuild/issues/1587
Required before we upgrade to RC.3

:shipit:


Issue using both public and private listener with different ports

Describe the bug
I have Ingresses on Port 80 and 443 which are public. Now I am trying to create an Ingress for private-Ips. I know that I cannot reuse 80 and 443 for that, so I am trying to use different ports but with no success.
I am getting following Error:

E1126 13:22:55.640499       1 frontend_listeners.go:47] Can't assign port fp-80 to Private IP Listener fl-kiali.cloud.example.com-80-privateip; already assigned to Public IP Listener fl-admin-portal.cloud.example.com-80; Will not create listener {FrontendPort:80 HostName:kiali.cloud.example.com UsePrivateIP:true}

To Reproduce
Just apply both ingress-resources with their appurtenant services and deployments
Ingress Controller details
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    appgw.ingress.kubernetes.io/use-private-ip: "true"
    kubernetes.io/ingress.class: azure/application-gateway
  name: kiali
  namespace: istio-system
spec:
  rules:
  - host: kiali.cloud.example.com
    http:
      paths:
      - backend:
          serviceName: kiali
          servicePort: 20001
status:
  loadBalancer: {}

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    appgw.ingress.kubernetes.io/backend-path-prefix: /
    appgw.ingress.kubernetes.io/ssl-redirect: "true"
    cert-manager.io/acme-challenge-type: http01
    cert-manager.io/cluster-issuer: letsencrypt-staging
    kubernetes.io/ingress.class: azure/application-gateway
  name: admin-portal
  namespace: istio-system
spec:
  rules:
  - host: admin-portal.cloud.example.com
    http:
      paths:
      - backend:
          serviceName: istio-ingressgateway
          servicePort: 80
  tls:
  - hosts:
    - admin-portal.cloud.example.com
    secretName: admin-portal-staging
status:
  loadBalancer: {}

Ingress admin-portal has appgw.ingress.kubernetes.io/ssl-redirect: "true". So, AGIC will try to create a listener tied to public IP at port 80.
For Ingress kiali, AGIC will try to create a listener tied to private IP at port 80.

Unfortunately, Application Gateway doesn't support public/private IPs on same port. But the great news is that we are already working on removing this limitation and should be able to share some update soon.

For Ingress kiali, AGIC will try to create a listener tied to private IP at port 80.

Why does AGIC create a listener on port 80 and not port 20001, since I explicitly stated that kiali should use service port 20001?

In Ingress resource, convention is to expose a service on either port 80 or 443. 443 is used when TLS is specified, otherwise, port 80 is used on the frontend.
We are planning to add an annotation by which you can specify frontend port to use on the gateway. I don't have an ETA yet.

Thank you, both approaches would suffice!

@akshaysngupta Any update on this topic?

@akshaysngupta
It seems this is high priority requirement, I found so many issues and requests and feedbacks on Azure to make appGw capable using same ports for public and private frontend ip
Do we have any ETA for it please?

Ingress admin-portal has appgw.ingress.kubernetes.io/ssl-redirect: "true". So, AGIC will try to create a listener tied to public IP at port 80.
For Ingress kiali, AGIC will try to create a listener tied to private IP at port 80.

Unfortunately, Application Gateway doesn't support public/private IPs on same port. But the great news is that we are already working on removing this limitation and should be able to share some update soon.

Is there any update on this?  This is a kind of blocking for us that it doesn't support same ports on Public and Private Frontends.

In Ingress resource, convention is to expose a service on either port 80 or 443. 443 is used when TLS is specified, otherwise, port 80 is used on the frontend.
We are planning to add an annotation by which you can specify frontend port to use on the gateway. I don't have an ETA yet.

Hi any developments on it yet? we are also facing same issue like support same ports on Public and Private Frontends.

@akshaysngupta do you have any update about this issue ? Maybe it's a duplicate of another one where we can follow the updates ?


Fix missing alias for decorated classes in es5

The new emitter runs decorators outside of the IIFE created to emulate a class declaration in ES5, and as a result we need to emit the same class alias we emit for ES6.
Fixes #10840
// cc: @mhegazy, @yuit

This fix also affects #11322. Thanks.


(WIP) Backend restructure - Integrations

Integrations
What are they?

Expand...
Integrations hook into a number of different places in the CMS to replace different calls, most (all?) of which would normally go to a backend. Currently the assets store (at least) requires additional work There are currently two integration providers:

Algolia: wraps searching and entry retrieval for large repositories.
Assets store: stores binary assets in a separate data store from entry data. (Currently unclear how this interacts with the media library)

Integrations vs integration providers
Ostensibly, the integration providers are implementations of generalized APIs for a named set of integration hooks:

assetStore - global
listEntries - collection-specific
search - collection-specific

Each of these APIs indicates that certain methods will be available on the provider instance. There doesn't seem to be a list of these anywhere in the code, as they're implicitly required, but I've compiled one here:

assetStore

upload(file, privateUpload) -> { success, url, asset } todo: determine the required shape of the file object
retrieve(query, page, privateUpload) -> fileList
delete(assetID) -> OptionPromise (OptionPromise here just means that the value of the Promise doesn't appear to matter, just whether it succeeds or fails).

listEntries: listEntries(collection, page) -> entryList
search

search(collections, searchTerm, page) -> entryList
searchBy(field, collection, query) -> entryList The field here is expected to be a string, which doesn't seem to match how it's called in src/actions/search.js/query.

There are some other methods implemented by integration providers, like getEntry in the Algolia provider, but they don't appear to be used currently.

How they work currently

Expand...
Configuration
The integrations are added by creating an integrations list in the config. This looks like the following (all currently supported configuration providers and options are listed here):
integrations:
  - provider: algolia

    # provider-specific options
    applicationID: example # algolia API application ID
    apiKey: example # algolia API key
    indexPrefix: example-cms # prefix for index names, which are in the form "${indexPrefix}${collection}"

    # hooks to attach the algolia functions to
    hooks:
      - search
      - listEntries

    # collections to apply hooks to
    collections:
      - example-entries
      - example-pages

  - provider: assetStore

    # provider-specific options
    getSignedFormURL: /example-asset-store/ # Used to generate URLs to the asset store endpoint. This is a constant, not a getter. I'm not entirely sure what this represents.
    shouldConfirmUpload: true # should confirm the upload by PUTing `{ state: "uploaded" }` to the asset URL

    # The assetStore hook is not tied to a specific collection
    hooks:
      - assetStore

Redux state init
In reducers/integrations.js, the exported reducer updates its integrations on a CONFIG_SUCCESS action. Each integration is an object, with several special keys:

provider: integration key.
hooks: a Map that connects hook names to the provider handling them
collections: a list of collection names to apply hooks to, or the string * to apply to all collections (but not the global hooks table)

Other keys are stored as provider data. The final state produced by this has two main keys:

providers: provider data - a Map of each integration's provider to a Map of any unknown keys in the integration object.
hooks: a Map of hooks

If collections is not present on the integration object, then each hook name in hooks is set as a key in the state.hooks Map, with the provider name as the value.
If collections is present on the integration object, then the config
Since this is implemented by reducing over the configured list of integrations, the precedence of integration hooks is determined by the order of the integrations list in the config, so re-ordering the list in the config can cause errors if the precedence is important. This makes generating a config which includes integrations unsafe unless you strictly control the order of the generated integrations list.
Collection names can collide with hook names, since they're both used as keys to the same Map. (e.g., a collection named listEntries would collide with the listEntries hook name). This includes the names in both the collections list in the integration object and, if any integration sets its collections to *, the collections listed in the main CMS config. This has two effects, depending on whether the integration config that sets the global hook comes before or after the integration config that sets the collection hooks for the colliding collection:

If the integration configuration with the global hook comes first, the provider name set as the value of that global hook will have the collection-specific hooks set directly on its string value.

If the integration configuring collection-specific keys for the colliding collection name comes first, the Map of collection hooks for that collection will be overwritten with the provider name of the global hook.

Since the order of the integrations is dependent on the order of their listing in the config.yml, bugs due to this can show up in previously-working configs if that list is reordered, even without any other changes made.
There are two ways to create hooks that apply to the whole CMS: either list hooks without collections in an integration, or set * as the integration's collections to apply collection-specific hooks to all configured collections. It's unclear what the precise roles of these different categories of hooks are.
The source of the reducer described above is as follows:
https://github.com/netlify/netlify-cms/blob/b4b584682473924556a41cae10f64f085b0f432b/src/reducers/integrations.js#L4-L29
Integration provider init
The actual integration providers themselves are initialized in src/integrations/index.js, in resolveIntegrations, which creates the integration providers configured when called (if the integration is included more than once ). resolveIntegrations is called by getIntegrationProvider on its first call and cached (note that getIntegrationProvider is declared in an IIFE, so the integrations declaration happens immediately when the file is loaded). This caching means that integration providers are invisible to the rest of the code, and cannot be reinitialized. The integrations variable here is effectively a singleton, just implemented with a closure instead of a class:
https://github.com/netlify/netlify-cms/blob/b4b584682473924556a41cae10f64f085b0f432b/src/integrations/index.js#L21-L32
getIntegrationProvider is called in a few places:

src/actions/entries.js - called in loadEntries
src/actions/search.js - called in searchEntries and query
src/valueObjects/AssetProxy.js - called in createAssetProxy
src/actions/mediaLibrary - called in loadMedia and deleteMedia

Whichever of these lines run first in a particular CMS setup determines when the integrations objects are set up. For most setups this probably occurs in loadEntries, as this is called whenever a collection is displayed, which is the default view when logging in to the CMS.
Hooks
As described above, hooks are configured and stored as lists of strings. The strings must match both the predefined hook name and a method on the integration provider object.
A hook is called via the following process (this process is not wrapped by anything else, so every site where a hook may be called must implement selectIntegrationProxy and getIntegrationProvider as described below):

selectIntegration is called with the following arguments:

state: the integrations list from the config
collection: the name of the collection (this is set to null for assetStore, the only non-collection-specific hook)
hook: the name of the hook

It then returns, from the integration state in the Redux store, either hooks.<collection name>.<hook> or hooks.<hook>, depending on whether the collection name is set. The value returned from here will either be null or the name of an integrations provider (see the "Redux state init" section above for the shape of the state.integration.hooks Map).

If an integration exists, getIntegrationProvider is called with the following arguments:

interationsConfig: the integrations list from the config
getToken: an async function for retrieving a token to authenticate to the backend (used only by the assetStore integration)
provider: name of the integrations provider

It then returns the actual provider instance (initializing the provider instances with resolveIntegrations as necessary).

The provider instance is called with whatever methods can be assumed to exist on the provider instance based on the API specified in the call to selectIntegration. The methods are listed above.

An example hook call follows:
https://github.com/netlify/netlify-cms/blob/b4b584682473924556a41cae10f64f085b0f432b/src/actions/entries.js#L241-L256

Comparison of potential integration designs

Expand...
Integrations as is
Integrations are currently a very complex API, with multiple layers of setup and configuration. Parts of the API are very general and indirected (e.g., the integration/integration provider distinction), and others are tightly coupled to specific implementations of both integration providers and backends (e.g., getToken or the AssetProxy system, both of which require explicit support from backends).
This leads to a situation where the API is simultaneously so flexible in principle that it's difficult to follow or implement, while so specific in operation that it requires indirect support across wide swaths of the codebase.
It's also inherently stateful - the list of providers instances is a singleton, and providers themselves are class instances which store information on the instance's properties.
Finally, the integrations API has sole responsibility for some concerns, meaning they cannot be implemented by backends. Search, for instance, is either done locally or through an integration - there's no ability for a backend to implement server-side search. Adding this to the backend API as well would introduce further API duplication between the backend and integration API.
TODO: expand
Integrations as backend composition
One potential approach would be to unify backends and integrations into a single API, allowing them to be combined with normal code. For instance, an Algolia integration could be defined as a function which wraps an existing backend and calls its functions, except for search, searchBy, getEntry, and listEntries.
Benefits of this could include removing getToken from the backend API (currently only used for integrations), and unifying the media library integration and backend APIs.
TODO: expand
Integrations as middleware
Redux allows intercepting actions before they hit reducers using middleware. This is very powerful, but it does allow unrestricted access to our Redux actions, essentially making our current action structure the public integrations API.
TODO: expand

Great breakdown here, love it.
Couple of thoughts:
Middleware API
The middleware option doesn't have to involve exposing raw state - we can process the middleware functions however we like. I'd expect that we'd transform the state into a shape matching our published API, allow that to travel through the middleware functions, and then transform the result from there.
The precedence problem
You make it clear that precedence matters here, as it does in almost any plugin architecture. I'm wondering if we can construct the API in such a way that a backend/integration must declare what parts of the API it handles in order to be allowed to handle those parts - e.g., Algolia, or the CMS config, declares that it handles search requests, and is therefore given the ability to handle those requests.
This allows us to statically determine handlers for each action and where overrides occur.
This could easily be an enhancement for later.

@erquhart good point on middleware - if we do use that kind of design, we'd definitely want an abstraction layer.

Is there a PR open for this anywhere? Is there anything the community can do to help with this?

@knpwrs currently I'm working on getting the GitLab and BitBucket backends wrapped up, as well as working on some of the preliminary refactoring that'll be required before we move to a new backend API. You can follow along with that work here: https://github.com/netlify/netlify-cms/pull/517 (GitLab) and https://github.com/netlify/netlify-cms/pull/525 (BitBucket).
Once that work is done, the last step to prepare for combining integrations and backends will be to move the media library integrations into backend.js, so the core code will be calling a single endpoint for all backend and integration functionality. At that point, we can replace the backend API with a compatible version that includes integrations without affecting anything above src/backends/backend.js.
As for the new backend API itself, it's still very much in the design phase. The primary issue for the backend API design is here: https://github.com/netlify/netlify-cms/issues/1134. The best way to help out with that now is to add suggestions and critiques to that issue. As a quick intro, the core ideas of the backend restructure are as follows:

Backends should be stateless functions (not instances of classes) which have state and async setState(newState) passed in as arguments.
The behavior currently implemented by integrations can be done by composing backends (either by simply changing/wrapping the functions that are returned to the CMS, or by some more complex API such as hook-based middleware).
We use a lot of layers to add functionality to backends, but their implementations are coupled to current backend implementations (i.e., everything assumes that the backend is filesystem-based, to the point that there's a backend API method deleteFile which accepts a path argument. These layers can be better implemented as shared code, so backends can choose to reimplement functionality if our built-in version is incompatible.

@Benaiah for when you dig into this:

Provide a heavily condensed, high level proposal (per recent discussion)
Let's go docs driven for this - the documentation would chart out how to create a custom integration/backend. Recommend staying high level to avoid bog down, we can improve the final docs later - go for speed.

Is this released?

No, this is currently in proposal stage.

Hello, is there a status update on this? I've been following #432 searching for a way to integrate NetlifyCMS with another media store such as S3 or GCP Storage. If there already exists an API (such as the one proposed in https://github.com/netlify/netlify-cms/pull/1602#issue-207764837) I'd be happy to help contribute documentation and leverage Netlify Functions if a backend is needed.


ic_skipper activates when addon active (Firefox)

When on Firefox playing Campfire Cooking in Another World with My Absurd Skill Episode 1 "https://www.crunchyroll.com/watch/GX9UQW93N/my-absurd-skill-is-unexpectedly-useful"... etc... I has a button appear right at the beginning and at several places in the playback.
I traced it to 3  elements. Namely;
SKIP TO: 3:38
SKIP TO: 17:31
SKIP TO: 22:58
When the addon is active it causes the button to show at various points including when the position of the button is near or overlapped with subs. Without the addon active then I do not see the buttons but get the usual buttons appearing.
I was able to completely remove the buttons by inspecting the HTML and deleting the offending  elements for each episode on loading but that is tedious. For that series almost all the episodes have at least one or more of those "ic_skipper" elements.
Might be as simple to search the HTML code for "ic_skipper" on page load and just delete them if they exist. Not sure what other anime contain them but they can appear at any time in the playback if the right conditions exist. not sure if this same behavior affects Chrome as I usually use Firefox to play Crunchyroll

Noticed in the Bin folder that this ic_skipper was probably generated by the App. Maybe add an option to turn off the generation of the ic_skipper code in the settings.

There is already an existing option to hide these skip buttons; go to 'player' settings, under the 'skip events' section, set 'Improve Crunchyroll' to 'hide'.
Given that Crunchyroll now provides its own skip functionality, it might be beneficial to set this option to 'hide' by default.

Ok. That does seem to fix the buttons appearing. ic_skipper is not showing up in the page code now. Thanks. Might want to mention this in the documentation incase someone else has the same issue with another series. Great tool otherwise to clean up some of the clutter that Crunchyroll tries to throw out. Consider this issue closed,


Specify build directory

Thank you so much for this - I've been looking for a way to build NodeJS layers easily.
Is there already a way to specify an output directory for the zipped file?
I noticed there is the SUBDIR_MODE in build.sh, but don't really understand how it's used.
What are your thoughts on adding a -o OUTPUT_DIR to the build script?

Well, easiest solution would be just to add a move command after the zip file is created to the build.sh


404 Not Found

Hi, i think maybe there's new update on hamster server? Or maybe something else?

same problem

Original app have issue

Oh it's global trouble, Maintenance maybe?

scum project closed))))

Xixixixixi broken project

all api endpoints work fine, only 2 endpoints give internal server error
api.hamsterkombatgame.io/auth/account-info.
api.hamsterkombatgame.io/auth/me-telegram.

wow, that's interesting, my bot which is on a vps in amsterdam works fine.

Back to normal, but some accounts still in problem. CLOSED


Requirements: allow validation of linkage between requirements instances

A requirement must at least have a conformance test
A requirements class must at least have a conformance class
A requirements class must at least have a requirement
A conformance test must link to one requirement
A conformance test must belong to a conformance class
A conformance class must contain more than one conformance test

This is to be ported from metanorma-ogc.

The tests that were implemented in OGC were:

A requirement must at least have a conformance test
A requirements class must at least have a conformance class
A conformance test must link to one requirement
A conformance class must link to one requirements class

I have just ported these.
The following tests have not been implemented until now:

A requirements class must at least have a requirement
A conformance test must belong to a conformance class
A conformance class must contain more than one conformance test


I have Server Execution Errors and Request Errors all the time. 'The server timed out waiting for the request to be processed. This may be due to high server load. Please try your request again.'  This error was caused due to an issue processing the web request, not because of an issue executing your code. You can retry the request.

A few things to check first:
Is the issue you are filing related to a specific kata?
If so then please file an issue on the discourse page of the kata. You can do so by creating a comment and marking it as an issue. Only issues related to site functionality should be filed here.
Is the issue you are filing related to how a specific language behaves when being executed?
If so then it will likely be better to file the issue on our github.com/Codewars/codewars-runner-cli/issues repo, which is where we have our open source code execution functionality. You also may want to look into forking that repo and fixing the issue yourself if you have the means.
Otherwise delete all of this text and file your issue. Make sure to include steps to reproduce the issue, including which pages/kata you found the issue on, and your Codewars username if its related to your account.

I've had this today too, all day

Closing this because the outage is resolved now. Sorry for the inconvenience.


WIP: test: Ginkgo and Gomega update

The new Gomega version supports testing a function with no return
value (https://github.com/onsi/gomega/issues/198#issuecomment-858240599). This
makes it possible to simplify the metrics test.

We need a formal Gomega release.

Updating to Ginkgo 2.0 once released (see https://github.com/onsi/ginkgo/blob/v2/docs/MIGRATING_TO_V2.md) will also be useful.
Currently we get a deprecation warning:
inkgo 2.0 is under active development and will introduce (a small number of) breaking changes.
To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/v2/docs/MIGRATING_TO_V2.md
To comment, chime in at https://github.com/onsi/ginkgo/issues/711

  You are using a custom reporter.  Support for custom reporters will likely be removed in V2.  Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter.  In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.

  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/v2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.4

This is getting closer to becoming feasible: once Kubernetes 1.25 and https://github.com/kubernetes-csi/csi-test/pull/366 are released, all of our dependencies use ginkgo v2.


python311Packages.pipenv-poetry-migrate: 0.5.6 -> 0.5.7

Description of changes
Release notes
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 317183 run on x86_64-linux 1

4 packages built:

python311Packages.pipenv-poetry-migrate
python311Packages.pipenv-poetry-migrate.dist
python312Packages.pipenv-poetry-migrate
python312Packages.pipenv-poetry-migrate.dist

Result of nixpkgs-review pr 317183 run on aarch64-darwin 1

4 packages built:

python311Packages.pipenv-poetry-migrate
python311Packages.pipenv-poetry-migrate.dist
python312Packages.pipenv-poetry-migrate
python312Packages.pipenv-poetry-migrate.dist


[FR]: More auto baud rate speeds

Hi Jason, thanks for this flasher tool, it works beautifully.
I use many Atom Lite devices, which support these serial speeds (this is their official testing utility that I use to erase the flash):

Before using your program, I was using esptool cli with 1.5Mbps setting: it was fast and reliable on those devices.
esptool.exe -b 1500000 write_flash 0x0 tasmota32-core2.factory.bin
This is the log from ESP-Flasher: it tries 460800 but it doesn't work, so it goes back to 115200.
It would be really nice if it could test more speed rates when autodetecting, and/or have an option to choose Auto, vs manual speed rates.
Using 'COM3' as serial port.
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Connecting....

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-PICO-D4 (revision v1.0)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: YES
 - Has Factory-Calibrated ADC: YES
 - MAC Address: E8:9F:6D:09:63:C0
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Chip does not support baud rate 460800, changing to 115200
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Connecting....
Uploading stub...
Running stub...
Stub running...
 - Flash Size: 4MB
 - Flash Mode: dio
 - Flash Frequency: 80MHz
Erasing flash (this may take a while)...
Chip erase completed successfully in 2.7s

Let me do some tests. My experiences are different, when the speed 460800 is already failing higher speeds never worked. Maybe the ESP32-PICO-D4 is different. Iirc i have one in my drawers. Will do tests. But when only PICO-D4 is supporting the higher speed(s) reliable i will not change the code. It is too specific.

My experiences are different, when the speed 460800 is already failing higher speeds never worked

With the Atom Lite I am flashing with esptool via cli at 1.5Mbps without issues.
Anyway, thanks for taking the time to think about this, the Atom Lite is very widespread, it would be cool to have an efficient GUI flashing tool for users.

The CLI already supports setting ths flash speed.

If in CLI, I always use the official esptool. But I hadn't found a reliable ESP8266/ESP32 GUI flashing tool before.
Thanks Jason.

Did some tests. The updated stub loaders seems improved a lot. Most test devices worked with 1500000 but sadly two get stuck with this high speed and do not fall back to the lower speed. So sadly to say i see currently no way to improve speed without breaking the overall function of the flasher

If you use the python version, you can simply change the starting high speed. Just change this value https://github.com/Jason2866/ESP_Flasher/blob/C2_test/esp_flasher/main.py#L38

Mhh. After a PC restart the all are flashing with 1500000. Let me do some more test.

No problem. 750000 is also a good speed to test. Works fine here.

If you use the python version, you can simply change the starting high speed. Just change this value

Unfortunately I have a lot of users/friends that are not experts, use windows, and prefer GUI tools vs the CLI. I mostly use CLI esptool via scripts and aliases. :)

This evening i will release a version with 1.5M.
Esp8266 was not working. -> Set speed of 115200 as fix value for the esp8266.

This evening i will release a version with 1.5M.

Great! Thank you.

Esp8266 was not working. -> Set speed of 115200 as fix value for the esp8266.

As expected, I think these speed rates are only for ESP32 devices.

No, no speed in between. When 1.5M fails 750k is failing too. As far as i can tell after my tests. So directly fall over to 115200 is imho the only solution which makes sense.
The release will be "just" an pre release, so feedback welcome.

@alexdelprete Give it a try https://github.com/Jason2866/ESP_Flasher/releases/tag/v.2.0.1

@alexdelprete Give it a try https://github.com/Jason2866/ESP_Flasher/releases/tag/v.2.0.1

Worked fine, blazing fast! :)
One issue I just found out, not related, it happened with previous release too: when flashing tasmota firmware.factory.bin it throws an error. With firmware.bin everything ok.
Using 'COM3' as serial port.
Connecting......
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Connecting.....

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-PICO-D4 (revision v1.0)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: YES
 - Has Factory-Calibrated ADC: YES
 - MAC Address: E8:9F:6D:09:63:C0
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
 - Flash Size: 4MB
Unexpected error: The firmware binary is invalid (magic byte=FF, should be E9)

And also...right after flashing, if I click flash again, it throws this error: I have to restart the app to flash again.

By design. Tasmota Esp_Flasher is fetching all files needed to flash Tasmota with the safeboot OTA partition scheme. So no factory file needed and not supported.

Works fine, amazing speed. The message for factory bin images is very clear now.
Only two issues left: the version in the title bar is still 2.0 and then this error message when you click Flash again right after a flashing operation completed:
Using 'COM3' as serial port.
Unexpected error: could not open port 'COM3': PermissionError(13, 'Access is denied.', None, 5)

Release https://github.com/Jason2866/ESP_Flasher/releases/tag/v.2.2.1
Now supporting Tasmota factory images too.
The COM port error is a weird issue. Needs a very deep dive. Dont know if it is possible to solve.
The behaviour on my MAC is different than with Windows...

Now supporting Tasmota factory images too.

Awesome. Now we have the best UI flasher for ESPs. :)
Thanks a lot for accepting the requests Jason, I appreciate it, and my friends will be happy to know they won't have to use CLI.
Regarding the COM port error, it's a niche case, so there's no rush solving that one.
Thanks again.


All installed callstack context menu items are shown during every debug session

I always assumed that during a debugging session, I'd only see the context menu items contributed by the active debug adapter. But in prepping the chrome extension to release, I just realized that I see all of them during every debug session.

This is a Go debug session, and I see callstack context menu items from node2 and chrome. They don't do anything. I think they should both be hidden. Normally if you have the Chrome extension installed, you'll see two instances of "toggle skipping this file".
@isidorn @weinand

Well, what I can do for now is just not contribute it from the Chrome extension. When you click the context menu item during a chrome debug session, it will activate the node2 extension and send the correct message to the chrome debug adapter.
But if it's easy, it might be worth considering for January?

Not for january, this is not critical and only happens if you have chrome extension installed. Also having 2 of the same actions is not the end of the world.
In a perfect world these actions should have a precondition when they are enabled, for instance
'debug:chrome'
'debug:node'
We already have a context 'inDebugMode', but I can look into introducing the dynaminc context based on debug type

@isidorn yes, we need to provide a dynamic context based on debug type.

Ok so I introduced a dynamic context based on debug type, namely you should now be able to do the following:
"when": "inDebugMode && debugType == 'chrome'"

Looks great, thanks


Inline media query cases pseudo-class to be always on

Repro: https://codesandbox.io/s/stitches-poc-inline-media-query-in-variant-62iff?file=/src/App.tsx
Notice

the button is navy by default.

Expected:

the button should change to navy on hover

Fixed in #112


WIP: documentation updates

Clarify LiveContext lifetime
Add section on run_udf_iter

TODO

[ ] Make the test code runnable (add setup)

Contributor Checklist:

[ ] I have added or updated my entry in the creators.json file
[ ] I have added a changelog entry for my contribution
[ ] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases

Reviewer Checklist:

[ ] /azp run libertem.libertem-live-data passed

/azp run libertem.libertem-live-data

/azp run libertem.libertem-live-data


Error with Feature-Policy header: Unrecognized feature: 'notifications'

nginx.conf
This seems to only affect Chromium.
domain.tld/:1 Error with Feature-Policy header: Unrecognized feature: 'notifications'.
domain.tld/:1 Error with Feature-Policy header: Unrecognized feature: 'push'.
domain.tld/:1 Error with Feature-Policy header: Unrecognized feature: 'vibrate'.

Hello @demyxco,
thanks for the report, issue has been fix with the commit 7e0bfd436c96c4be6552bfd8519f2e68a6b68aad .


x/build: limit the number of auto-assigned reviewers

This is a follow-up issue to the discussion at https://groups.google.com/forum/#!topic/golang-dev/CdGrNJDcqec, to make sure it doesn't get lost.
In that thread @mvdan proposed:

If a CL were to ping more than 5 people, simply fallback to pinging someone on the core team (Andy? Ian? Brad?), who can then make a better call than a machine could

I think we should do this.
@dmitshur @andybons

I'll wait to hear @andybons thoughts on this, but I'd say if we're going to treat "would ping more than 5 people" specially, it should just avoid doing anything.
I don't think it's viable to pick only a single person on the core team to always get pinged, and it may not be a trivial effort to add a rotation going just for these kinds of CLs. The safest thing is for gopherbot to say "welp; this is too hard for me to deal with, I'll tag it as no-owners and back out". Then humans can pick it up, just like all previous CLs before gopherbot did the reviewer assignments.

Using a tag instead of pinging someone from the core team seems fine to me. The big priority here is to keep the mass-CCing to a minimum.
Another major offender, which isn't a particularly interesting CL either: https://go-review.googlesource.com/c/go/+/140299


[WIP] Various fixes

This PR is on top of #368. First new commit is 057e2e4. Note that hashes don't line up (but commit messages do) because I rebased this branch because Github didn't like the merge I did as my first try.
This needs a little more testing and ticket-related bookkeeping, but so far these changes all seem to work.

Replace busybox with alpine for couchdb init container
Update couchdb-prometheus-exporter's prometheus-to-sd to the latest, 0.5.1
Update nginx-ingress to the latest, 0.21.1 (I plan to update the chart as well while I'm doing this)
Re-run port-forward each time when checking membership for couchdb.finish_cluster

LGTM

Chart is updated. I also bumped couchdb-statefulset-assembler to the latest, for fun.
I was going to chop this branch into a bunch of PRs for each ticket, but it's kind of a pain for little benefit so I plan to merge this as-is (assuming it passes a few more tests).

Closing in favor of https://github.com/gpii-ops/gpii-infra/pull/373.


Cargo build fails with "error[E0308]: mismatched types" Error

Issue description
I'm trying to build nat with my Debian 10 installation. It fails with a "error[E0308]: mismatched types" error.
Steps to reproduce the issue

git clone https://github.com/willdoescode/nat.git
cd ./nat
cargo build --release

What's the expected result?

The build should work.

What's the actual result?

The build does not work and fails with the following error Message:

Compiling nat v1.0.9 (/home/[USERNAME]/Workspace/git/nat)
     Running `rustc --crate-name nat --edition=2018 src/main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C opt-level=3 -C metadata=adba114910da65c6 -C extra-filename=-adba114910da65c6 --out-dir /home/[USERNAME]/Workspace/git/nat/target/release/deps -L dependency=/home/[USERNAME]/Workspace/git/nat/target/release/deps --extern ansi_term=/home/[USERNAME]/Workspace/git/nat/target/release/deps/libansi_term-eadfc56f31755089.rlib --extern chrono=/home/[USERNAME]/Workspace/git/nat/target/release/deps/libchrono-e6ab3cac18a449c9.rlib --extern libc=/home/[USERNAME]/Workspace/git/nat/target/release/deps/liblibc-bec547172235da48.rlib --extern pretty_bytes=/home/[USERNAME]/Workspace/git/nat/target/release/deps/libpretty_bytes-9706fdfae34e91af.rlib --extern structopt=/home/[USERNAME]/Workspace/git/nat/target/release/deps/libstructopt-95351602fc045da0.rlib --extern termion=/home/[USERNAME]/Workspace/git/nat/target/release/deps/libtermion-ba47c272930f5c21.rlib --extern users=/home/[USERNAME]/Workspace/git/nat/target/release/deps/libusers-640153e22e8cf3ab.rlib`
error[E0308]: mismatched types
   --> src/main.rs:207:27
    |
207 |     let user = triplet(mode, S_IRUSR, S_IWUSR, S_IXUSR);
    |                              ^^^^^^^ expected `u16`, found `u32`
    |
help: you can convert an `u32` to `u16` and panic if the converted value wouldn't fit
    |
207 |     let user = triplet(mode, S_IRUSR.try_into().unwrap(), S_IWUSR, S_IXUSR);
    |                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^

Here's the complete build log:
cargo build --verbose --release > out.txt 2>&1

out.txt
Additional details
Some System Info that may or may not help:
$ cargo --version
cargo 1.42.1

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

$ uname -a
Linux [HOSTNAME] 5.8.0-0.bpo.2-amd64 #1 SMP Debian 5.8.10-1~bpo10+1 (2020-09-26) x86_64 GNU/Linux

Seems like there is already a pull request addressing this issue: https://github.com/willdoescode/nat/pull/28

I am getting this error too. +1 for that PR.

#28


#84 Issue Resolution

#84 Issue Resolved!
Hey Avinash,
I have put the code as promised.
Hope to do more in this repo!
Regards,
Mukund Deepak

@avinash201199 please close pull request

@avinash201199 waiting for review 😄

Info about the program:
This is a C program which converts an infix expression to postfix through the implementation of stacks.
Example: 23+1 -> 231+

pull request merged, you can also contribute to other repo's-https://github.com/avinash201199/Hacktoberfest-Guide
Note- only 2 pr per day on a single repo is accepted.


Triangle Strips?

Discussed in https://github.com/google/filament/discussions/4506

Originally posted by jeanlemotan August 16, 2021
I've noticed that triangle strips are not supported in filament. Any reason for that?
I see that GL_PRIMITIVE_RESTART_FIXED_INDEX is also supported in GL ES 3.0 which allows an even bigger reduction of the index buffer size.

Might be worth investigating.

This is sort of unrelated but another thing to consider is supporting null IndexBuffer (i.e. non-indexed draw calls), which would be useful for glTF and for point sprites.

The app/gltio can always generate an index buffer for this use case. I'm not sure it's worth us supporting it in Filament itself.

It's this even supported in ES?

It's this even supported in ES?

If by "this" you mean triangle strips, then yes, the OpenGL ES documentation for glDrawElements does list GL_TRIANGLE_STRIP as one of the accepted modes.

We're not talking about triangle trips, we know they are supported. We were talking about index-less draw calls.

The change just went in!

https://github.com/google/filament/pull/5017


performance regression (for debug & single binary) after bumping toolchain

Describe the bug
I found risingwave becomes significantly slow on my mac. e.g., e2e_test/batch/basic/array.slt.part takes 30+ seconds. After git bisect, I found the regression happens after https://github.com/risingwavelabs/risingwave/pull/6025.
To Reproduce
No response
Expected behavior
No response
Additional context
@skyzh can't reproduce. CI also works fine. Need someone else to confirm it. Confirmed it happens on debug & single binary mode.

Can you collect some perf result on that? Thanks!

I also found this regression on debug mode and Sysbench QPS dropped to almost zero. However everything works well on release mode.

single-binary doesn't work well, while multi-binary looks good. Is there anything that might goes wrong with the madsim update? cc @wangrunji0408

And ok_or_else seems to consume significant amount of CPU time.

... because backtrace is slow to create

In multi-binary:
backtrace captured in 1ms
backtrace captured in 0ms
backtrace captured in 0ms
backtrace captured in 0ms
backtrace captured in 0ms
backtrace captured in 0ms
backtrace captured in 0ms
backtrace captured in 0ms
backtrace captured in 0ms
backtrace captured in 0ms

In single-binary:
backtrace captured in 393ms
backtrace captured in 369ms
backtrace captured in 370ms
backtrace captured in 365ms
backtrace captured in 362ms

Probably a bug with the Rust compiler, but I would still recommend not returning so many errors.

Related function:
    pub fn get_schema_by_name(&self, db_name: &str, schema_name: &str) -> Result<&SchemaCatalog> {
        self.get_database_by_name(db_name)?
            .get_schema_by_name(schema_name)
            .ok_or_else(|| {
                let x = Instant::now();
                let err = CatalogError::NotFound("schema", schema_name.to_string()).into();
                println!("backtrace captured in {}ms", x.elapsed().as_millis());
                err
            })
    }

The suspicious thing is the dwarf region in the binary.
On 2022-07-29:
objdump target/debug/risingwave  --dwarf=frame | wc -l
     371

On 2022-10-16:
objdump target/debug/risingwave  --dwarf=frame | wc -l
 14671494

Shall we file a bug report to rust-lang? (Though I believe this is more of an LLVM bug / LLVM upgrade)

I would suggest keep this issue open while changing frontend to return Option instead of error.

I would suggest keep this issue open while changing frontend to return Option instead of error.

I think most of the errors generated in the frontend are for responding to the user, which cannot be avoided.

Is it caused by capturing the stacktrace?

I think most of the errors generated in the frontend are for responding to the user, which cannot be avoided.

No. The e2e test cases that timed out should not have any user-facing error. All tables exist.

Is it caused by capturing the stacktrace?

Yes.

There seems to be some new features in Rust / LLVM that generates a special kind of debug info DWARF, which contains stack unwinding region information. In debug mode it's just slow to rewind.

It's not a big issue but still affected the developer's experience 🥲 What is our solution?

Wait for rust community to fix it. (Don't know how much it will take)
Refactor the code that captures the stack-trace into error
Any other ideas?

Wait for rust community to fix it.

I don't think that's something to be fixed. It looks more like a feature that provides better backtrace.

Refactor the code that captures the stack-trace into error

I think a fix is going on to change them to cheaper CatalogEror.

cc. @BowenXiao1999

I've opened an issue for this -> #6157.

Backtrace capturing is not only slower, but can also lead to a segfault: #6205

The performance problem is much better now. It took me 200s to run slt-all for multi-binary and 250s for single-binary (when the issue opened it was forever).

Closing this issue in favor of #4077 and #6205.
The slowness is acknowledged by the doc of Backtrace::capture, and our take on it would be to avoid unnecessary backtrace capture via #4077.
The segfault is worse and tracked by #6205.

TImeout is a separate issue. reopen.


Edit Data: Show SQL Plane button overlaps with dropdown

The Show SQL Pane button overlaps with the Max Rows dropdown when clicked. Screenshot -

I can only repro this while clicking on the button.  This is related to the button animation which enlarges the text font size.  I think this is By Design but we will review with UX.

@abist I've updated the issue title to capture the general toolbar zoom issue rather than specifically the one case noted in Edit Data.  I see similar issue with "Explain" in the Query Editor.


A revert that keep making eth_Call to fail and retry indefinitely

I am getting this error repetitively and my subgraph get stuck :
Trying again after eth_call RPC call failed (attempt #10) with result Err(Web3Error(Transport("Unexpected response status code: 502 Bad Gateway"))), block_hash: 0xc1ba5e2caa2aab52c5bced3e81f08b9e8f3d5e61ffadca9a726904db376c83a3, block_number: 12833778

The following contract: 0x86ca39d10dacdf1cfe490eb984bf0e7c17d1ed37
Subgraph: https://thegraph.com/hosted-service/subgraph/iw001/bsc

hey @dy1006 - this is an issue with the BSC RPC that the hosted service, rather than graph-node - please follow the status page or in the graphprotocol Discord for more up-to-date details


MantineThemeProvider.tsx:11 Uncaught Error: @mantine/core: MantineProvider was not found in component tree, make sure you have it in your app

I'm seeing the following error when I click on any atom in Jotai DevTools panel.
Here's a reproducible repo: https://github.com/npearson72/jotai-devtools-test
How it started:

How it's going:

Thanks for the repro! This is because the repo has a conflict between @mantine/core v6 and v7. Removing these
Mantine deps in your repo should fix it.

Thanks for the repro! This is because the repo has a conflict between @mantine/core v6 and v7. Removing these Mantine deps in your repo should fix it.

@arjunvegda I included Mantine v6 because that's what I use in my real world project, and we haven't migrated yet to v7 because of how big of a change it it is from v6. I take it by your comment that Jotai DevTools does not support Mantine v6?


[ROCM] View llvm ir and gcn asm with module.get_source(...)

Enables viewing generated LLVM IR or GCN assembly with:
dev_module = func.imported_modules[0]
print(dev_module.get_source("llvm"))
print(dev_module.get_source("asm"))

minor code style issue, use stl_case for variable naming to follow google C style. I will merge this in for now, but would be great if we can fix it in future PRs

yeah, that is my style as well. I followed @adityaatluri's style here.


Allow setting Vaadin license key via plugin preferences

Vaadin license keys are normally stored in a file in the users home directory. This is a bit problematic as when using a CI server you might not want to put the key on the server but instead pass it through the build properties.

Hello John,
I am trying to use the Spreadsheet-addon. I have the licence in my home directory, but the widgetset is still not compiling. Is there something more I need to do?

Having the license in the home directory should work, have you named the license file correctly? (should be .vaadin.spreadsheet.developer.license).
Vaadin Spreadsheet also requires a Vaadin 7.4.+ so ensure you also are using that.
Here is my test build.gradle if it helps:
apply from: 'http://plugins.jasoft.fi/vaadin.plugin'

vaadin {
    version '7.4.+'
    widgetset 'com.example.MyWidgetset'
}

dependencies {
    compile 'com.vaadin.addon:vaadin-spreadsheet:1.1.0.alpha2'
}

I named the licence-file wrong (there is no dot in the start on the licence-file when I downloaded it from vaadin.com). But that didnt solve it. I use 7.5.0 and have 10+ other plugins that works great. But if it works nice for you its all in my builds. I will look into this further in a few weeks time when the spreadsheet functionality will be essential. I use intellij:s gradle-plugin if that makes any difference, even if it shouldnt...
Happy friday! :)


Uncaught TypeError: b.className.replace is not a function

Everything is working but i get this console error:
Uncaught TypeError: b.className.replace is not a function     at e.resetAnimation (wow.min.js?ver=4.9.5:2)     at HTMLAnchorElement.<anonymous> (wow.min.js?ver=4.9.5:2) e.resetAnimation @ wow.min.js?ver=4.9.5:2 (anonymous) @ wow.min.js?ver=4.9.5:2
How to fix that?

Still have that problem, it generates repeated errors in console.

me to

How to solve
zone.js:199 Uncaught TypeError: t.className.replace is not a function
at T (client-track.js?20198917:1)
at HTMLDocument. (client-track.js?20198917:1)
at ZoneDelegate.push.../../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:423)
at Zone.push.../../node_modules/zone.js/dist/zone.js.Zone.runTask (zone.js:195)
at ZoneTask.push.../../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask [as invoke] (zone.js:498)
at invokeTask (zone.js:1744)
at HTMLDocument.globalZoneAwareCaptureCallback (zone.js:1802)

How to solve
zone.js:199 Uncaught TypeError: t.className.replace is not a function
at T (client-track.js?20198917:1)
at HTMLDocument. (client-track.js?20198917:1)
at ZoneDelegate.push.../../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:423)
at Zone.push.../../node_modules/zone.js/dist/zone.js.Zone.runTask (zone.js:195)
at ZoneTask.push.../../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask [as invoke] (zone.js:498)
at invokeTask (zone.js:1744)
at HTMLDocument.globalZoneAwareCaptureCallback (zone.js:1802)

Where is the solution? @vijaymobio

same error-  how to solve
zone.js:199 Uncaught TypeError: t.className.replace is not a function
at T (client-track.js?2019102510:1)
at HTMLDocument. (client-track.js?2019102510:1)
at ZoneDelegate.push.../../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:423)
at Zone.push.../../node_modules/zone.js/dist/zone.js.Zone.runTask (zone.js:195)
at ZoneTask.push.../../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask [as invoke] (zone.js:498)
at invokeTask (zone.js:1744)
at HTMLDocument.globalZoneAwareCaptureCallback (zone.js:1813)

Yes,
i get this error,  but everything is working

I also got this problem. I had a block with a .wow class, and inside a svg with hover animation.
This code solved my problem:
svg.addEventListener("animationend", (event) => {                 event.stopPropagation();             });
This error occurs in the resetAnimation() function in wow, which is called on the 'animationend' event. So it's enough just to listen 'animationend' and use stopPropagation().

Hello，我是林昕，我已收到来信~

This error occurs with you try to animate svg element, try to add span and put the svg inside and animate that span.

Hello，我是林昕，我已收到来信~


chore: add git hooks and lint-staged

lint-staged will run on the pre commit hook, it'll call deno fmt and automatically add any modifications it does to the commit
install hooks with deno task hook install

No more "chore: deno fmt" commits!

Amen, brother!

Skill issue hides behind format-on-save config entry /s


Protect sign_certificate endpoint using basic auth

We want to protect the sign_certificate endpoint using basic
authentication. Each MNO will have a username and password.
In a later PR we can then use the basic auth username to check that MNOs
can only issue a CSR for one of their own certificates.

I've just realised that we might not be able to merge this PR - the app will now expect all the basic auth usernames and passwords to be there when it starts and I don't think we have those set up yet. Do I need to rewrite things so that those environment variables are optional for now?

I've just realised that we might not be able to merge this PR - the app will now expect all the basic auth usernames and passwords to be there when it starts and I don't think we have those set up yet. Do I need to rewrite things so that those environment variables are optional for now?

@rjbaker I've added a new commit to make the environment variables optional for now. If we have them all already, I can just delete the commit

@rjbaker I've added a new commit to make the environment variables optional for now. If we have them all already, I can just delete the commit

This will need the basic auth usernames and passwords to exist before it is merged - the code expects those environment variables to be there on startup

This will need the basic auth usernames and passwords to exist before it is merged - the code expects those environment variables to be there on startup


Beter explanation about how set paths to get templates.

Hi! I has some troubles trying set the path to get the inside notebooks as templates because is not clear the needed to be in sub dirs and without checkpoints (.ipynb_checkpoints). Could you note that in Readme.m? Many thanks!

??
https://github.com/timkpaine/jupyterlab_templates/pull/63


Ruby 2.6.5 installation fails on MacOS 11.1 M1 - Interrupted system call

Although I tried to install ruby 2.6.5, I could not install and catch following errors:
compiling ossl_x509name.c
compiling ossl_x509req.c
compiling ossl_x509revoked.c
compiling ossl_x509store.c
installing default openssl libraries
linking shared-object openssl.bundle
linking shared-object ripper.bundle
./revision.h unchanged
linking ruby
*** Following extensions are not compiled:
syslog:
Could not be configured. It will not be installed.
/private/var/folders/zh/v3hksw51419_8_xk980c24cw0000gn/T/ruby-build.20210120213517.13386.vgRndC/ruby-2.6.5/lib/mkmf.rb:556: Interrupted system call -
Check ext/syslog/mkmf.log for more details.
gdbm:
Could not be configured. It will not be installed.
/private/var/folders/zh/v3hksw51419_8_xk980c24cw0000gn/T/ruby-build.20210120213517.13386.vgRndC/ruby-2.6.5/lib/mkmf.rb:556: Interrupted system call -
Check ext/gdbm/mkmf.log for more details.
pty:
Could not be configured. It will not be installed.
/private/var/folders/zh/v3hksw51419_8_xk980c24cw0000gn/T/ruby-build.20210120213517.13386.vgRndC/ruby-2.6.5/lib/mkmf.rb:556: Interrupted system call -
Check ext/pty/mkmf.log for more details.
digest/md5:
Could not be configured. It will not be installed.
/private/var/folders/zh/v3hksw51419_8_xk980c24cw0000gn/T/ruby-build.20210120213517.13386.vgRndC/ruby-2.6.5/lib/mkmf.rb:556: Interrupted system call -
I checked that security software did not work (ref.  #1710).
Do you have any idea to install ruby 2.6.5 correctly ?

Ruby 2.6 does not support Apple M1 chip officially.

Try this solution


Added code for the updated string interpolation tutorial

Supports dotnet/docs#5200
Those two PRs must be merged together as only merging this PR into master would break not updated master of dotnet/docs.

@rpetrusha I'm afraid that breaks all other PRs in dotnet/docs as this PR removed the files that support the current version of the tutorial. If that's true, how can I fix that?

Yes it does @pkulikov. They had to be reviewed and merged together. /cc @BillWagner


Open device using operating system open-function returns EISDIR using .NET Core

Open device using operating system open-function returns EISDIR using .NET Core
I am using interop to access basic file api of linux (Respberry Pi).
[DllImport("libc", SetLastError = true, CharSet = CharSet.Auto)] internal static extern int open(string fileName, int mode);
Opening a device like tty
var handle = Interop.open("/dev/tty", Interop.O_RDWR);
fails with errno=21 (EISDIR)
Same code running full framework (Mono 4.6.2) the device is opened successfully and i can use read and write!
Where comes this difference?

This issue was moved to dotnet/corefx#32442


chore: add license as file

Description
Adding license as file

LGTM, great thank you very much 🎉


Support 200.html

Surge support 200.html for various purposes. And I think it would be nice if Hugo could add this page too. It would be more convenient for me than create a dummy content and use _default/single.html. And that trick doesn't work well if I have a blog that need page content. Using 200.html as static is also out of the question because my 200.html needs data generated from Hugo.
(It would be even cooler if we could have custom Page Kind. But that seems expensive so I'll just request for 200.html)

(It would be even cooler if we could have custom Page Kind. But that seems expensive so I'll just request for 200.html)

Try adding custom output format.

(It would be even cooler if we could have custom Page Kind. But that seems expensive so I'll just request for 200.html)

Try adding custom output format.

Because I couldn't do that so I have come here ask for this feature. Anyway, - how did you do that to archive page 200.html. The custom format doesn't receive new kind of template. Which means Hugo will output 200.html from an index.html, not from 200.html.

The documentation for that is prtety bad, but it would do what you're looking for.
output:
    home: ["HTML", "RSS", "200"]

mediaTypes:
    text/200.html:
        suffixes: [".html"]

outputFormats:
    200:
        mediaType: text/200.html
        baseName: 200
        isHTML: true
        permalinkable: false

You can then create a 200.html inside the layouts folder.

It didn't work. I put 200.html template file in layouts but got nothing.
Do you have a sample repo that actually works?

@faraixyz
I tested it again with a completely clean project, 200.zip. But nothing seems work. It only use your config, (and I disable a certain useless kinds to but nothing changed.). This is not the way and we need 200.html support.
(If you think your way is the right way, please share your code that works so I can learn what did I do wrong.)

Ok, I've figured it out now.
outputs:
  home: ["HTML", "RSS", "200"]

outputFormats:
  200:
    mediaType: text/html
    baseName: 200
    isHTML: true
    permalinkable: true

Then your template should be named index.200.html.

Thanks, so you were correct. I think I will try to update the Hugo docs a bit then close this issue. Therefore here will be what I will do:

Rename this issue (Don't know how to change tag, but if possible I would like to change from Proposal to issue as this is document problem for not being clear)
Update docs: Adding a tip to create a template for specific file. (I'll use Surge as an example case)
PR to fix this issue.

(Until then I would like to keep this open.)


Roll engine to 72a38a6b1343ec09a8d884fff655bfbc8cb01674

72a38a6b1 Build Android engine in presubmit using Cirrus and GCE (#5882)
f9f40badd Log uncaught exceptions from JNI calls at a higher priority (#5891)
723b2784d Update license script README (#5890)
9420da1e2 Roll src/third_party/skia 9acfc6cac2c6..227424b57d28 (10 commits) (#5888)
27c9de59b Roll src/third_party/skia 55b1e6168454..9acfc6cac2c6 (1 commits) (#5887)
8b8c52ed7 Roll src/third_party/skia b935cf8e12d7..55b1e6168454 (1 commits) (#5886)
89602cc64 [scenic] Expose compositor context from rasterizer. (#5739)
9baeb9c1a Roll src/third_party/skia 5f1dc76d0cec..b935cf8e12d7 (1 commits) (#5885)

nit: wrap the rev list in back ticks to prevent referencing a bunch of unrelated issues


[BUG] Populate user's netid when creating group event

Describe the bug
Group event created in UIUC app does not appear in the Admin app. This is because the API for creating group events POST: /gr/api/group/{group_id}/events/v3 does not populate the user's net id in the identifier of the user. It only populates the account id.
Expected behavior
Populate user's NetID when one creates event via the Groups BB.
Additional context
This issue is related to an email Re: University Monday 2024/04/15 from 2024/04/17.
Quote:

3.2 An issue with Groups BB with the Group Creator and attendance taking. Dobromir/Petyo you can ignore my questions, but follow this and help as needed please.
This is two ways to see that the issue is perhaps only with the Creator of a Group:
a) As the Creator of a Public Group with one Assigned Admin, add a new Public Event with Attendance. The take attendance button is not visible.
b) With the same group as in a) above, the Assigned Admin uses Admin Web to make the Creator an Attendance taker. The take attendance button is not visible.

Group id: dd5565c8-1c15-4734-ae55-c31b6e14166d
Event id: b64870f4-3d29-4f70-9a55-d0ffafc35b5e
This happens only for events created via Groups BB. Events created via Calendar BB works as expected.

@stefanvit, please check the corresponding Calendar BB API

Fixed in https://github.com/rokwire/groups-building-block/issues/450


Does this take into account compiler settings?

For instance, the solidity optimizer and the default 200 runs. I think it would be worth it to add a note about how truffle-flattener handles the config file.

This projects just concatenates solidity source files in the right order. It never executes solc, so it doesn't handle settings at all.

Not sure what I was thinking about. It's really late where I am.
Thank you!