jtag-openocd behaviour doesn't match jtag-svf

Apologies in advance if this is an upstream bug in openocd or ecppack.
I have an SVF file which is just a blinky for an ECP5 (LFE5U-12F) FPGA built with ecppack. If I use the jtag-svf applet, it loads on the FPGA fine:
$ glasgow run jtag-svf -M --port A --pin-tck 0 --pin-tms 3 --pin-tdi 2 --pin-tdo 1 blink.svf
I: g.device.hardware: building bitstream ID baa3e836c8b20784cde3bbff3b5fe82e
/home/jeremy/oss-cad-suite/bin/nextpnr-ice40: line 22: /home/jeremy/.config/yosyshq/fonts.conf: No such file or directory
I: g.cli: running handler for applet 'jtag-svf'
I: g.applet.interface.jtag_svf: port A voltage set to 3.3 V
W: g.applet.interface.jtag_svf: SVF: test vector did not reset DUT explicitly, resetting

However, if I try to use the jtag-openocd applet with the following configuration file:
adapter driver remote_bitbang
remote_bitbang port 33333
remote_bitbang host localhost

reset_config none separate

jtag newtap ecp5 tap -irlen 8 -expected-id 0x21111043

init
scan_chain
svf -tap ecp5.tap -quiet -progress blink.svf
shutdown

the FPGA does actually load the bitstream and start running (I can see the blinking LEDs), but openocd throws an error:
$ glasgow run jtag-openocd -M --port A --pin-tck 0 --pin-tms 3 --pin-tdi 2 --pin-tdo 1 tcp:localhost:33333
I: g.device.hardware: building bitstream ID b6ca43076c531bba087e54cd1f647cdb
/home/jeremy/oss-cad-suite/bin/nextpnr-ice40: line 22: /home/jeremy/.config/yosyshq/fonts.conf: No such file or directory
I: g.cli: running handler for applet 'jtag-openocd'
I: g.applet.interface.jtag_openocd: port A voltage set to 3.3 V
I: g.applet.interface.jtag_openocd: socket: listening at tcp:localhost:33333
I: g.applet.interface.jtag_openocd: socket: new connection from [<IP_ADDRESS>]:51492
I: g.applet.interface.jtag_openocd: socket: connection from [<IP_ADDRESS>]:51492 lost

$ openocd -f flash.ocd
Open On-Chip Debugger 0.12.0+dev-00059-g0b6f53e94-dirty (2023-01-29-02:08)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselecting 'jtag'
Info : Initializing remote_bitbang driver
Info : Connecting to localhost:33333
Info : remote_bitbang driver initialized
Info : Note: The adapter "remote_bitbang" doesn't support configurable speed
Info : JTAG tap: ecp5.tap tap/device found: 0x21111043 (mfg: 0x021 (Lattice Semi.), part: 0x1111, ver: 0x2)
Warn : gdb services need one or more targets defined
svf processing file: "blink.svf"
95%    Error: tdo check error at line 28
Error:     READ = 0x6401e10
Error:     WANT = 0x0000000
Error:     MASK = 0x000b000
Time used: 0m16s183ms

svf file programmed failed
Info : remote_bitbang interface quit

Presumably there isn't anything wrong with the SVF file because the jtag-svf applet works fine - unless there are some SVF lines that are skipped in the jtag-svf applet.
blink.svf.txt (.txt extension added to allow it to be uploaded)

Hmm, I’m thinking this is because there is no openocd remote_bitbang command for a delay. The glasgow server is accepting packets as fast as possible, and so the delay in data packets is not transferred to the device due to the fact that the output data rate of the FPGA is slower than the input data rate from the USB interface.

Indeed, that appears to be the issue. Something like this appears to fix the problem: https://review.openocd.org/c/openocd/+/7472
Basically, it just adds two commands to delay either 1ms or 1us. If the patch is accepted, then it should be straightforward to add some delays to the JTAG applet I think.

I wonder if maybe applying backpressure to the bitbang source is actually the correct approach here? Can we do this?

I thought about this (both with some sort of XON/XOFF and a ‘checkpoint’ handshake at points in SVF execution), but I can’t think of a good way to send the back pressure indication to openocd without increasing the complexity of the remote_bitbang protocol (which I don’t think will fly). As I understand it, the original intention for the protocol was for use with simulations, so they probably want to keep it as simple as possible.
Though, I think there is no reason that Glasgow needs to utilise the functionality in the linked patch - perhaps a different way would be more suitable given the extreme flexibility of the hardware. I mostly put the patch together to confirm that was indeed the problem, and also because I’d like to use it with another non-Glasgow device. For this applet, I think that maybe long term it would be better to use/create another adapter in openocd that also allows one to set the clock rate and maybe some other options - this could also include back pressure indication.

LGTM on adding support for this specific interface to jtag-openocd.

The upstream continues being unresponsive for seemingly no reason. :(

This has now been merged upstream: https://review.openocd.org/c/openocd/+/7472

See also https://review.openocd.org/c/openocd/+/8191

@jeremyherbert I think this should be fixed now--could you retest please?

I tried running the following command with the SVF file in the original post:
glasgow run jtag-svf -V 3.3 --port A --pin-tck 0 --pin-tms 3 --pin-tdi 2 --pin-tdo 1 blink.svf

But I receive the error:
I: g.device.hardware: device already has bitstream ID 62239ba31f7697d2809a2646248c966a
I: g.cli: running handler for applet 'jtag-svf'
I: g.applet.interface.jtag_svf: port(s) A voltage set to 3.3 V
Traceback (most recent call last):
  File "/home/jeremy/.local/bin/glasgow", line 8, in <module>
    sys.exit(run_main())
  File "/home/jeremy/Downloads/glasgow/software/glasgow/cli.py", line 939, in run_main
    exit(asyncio.new_event_loop().run_until_complete(main()))
  File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/home/jeremy/Downloads/glasgow/software/glasgow/cli.py", line 707, in main
    return applet_task.result()
  File "/home/jeremy/Downloads/glasgow/software/glasgow/cli.py", line 656, in run_applet
    return await applet.interact(device, args, iface)
  File "/home/jeremy/Downloads/glasgow/software/glasgow/applet/interface/jtag_svf/__init__.py", line 294, in interact
    await coro
  File "/home/jeremy/Downloads/glasgow/software/glasgow/applet/interface/jtag_svf/__init__.py", line 120, in svf_state
    path = {
KeyError: (<JTAGState.UNKNOWN: 'Unknown'>, <JTAGState.IDLE: 'Run-Test/Idle'>)

I also tried with a freshly compiled openocd and the openocd config file above:
Open On-Chip Debugger 0.12.0+dev-00634-g23c33e1d3 (2024-07-02-17:11)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
Info : Initializing remote_bitbang driver
Info : Connecting to localhost:33333
Info : remote_bitbang driver initialized
Info : Note: The adapter "remote_bitbang" doesn't support configurable speed
Info : JTAG tap: ecp5.tap tap/device found: 0x41111043 (mfg: 0x021 (Lattice Semi.), part: 0x1111, ver: 0x4)
Warn : JTAG tap: ecp5.tap       UNEXPECTED: 0x41111043 (mfg: 0x021 (Lattice Semi.), part: 0x1111, ver: 0x4)
Error: JTAG tap: ecp5.tap  expected 1 of 1: 0x21111043 (mfg: 0x021 (Lattice Semi.), part: 0x1111, ver: 0x2)
Error: Trying to use configured scan chain anyway...
Warn : Bypassing JTAG setup events due to errors
Warn : gdb services need one or more targets defined
svf processing file: "blink.svf"
  0%  HDR	0;
(Above Padding command skipped, as per -tap argument)
  0%  HIR	0;
(Above Padding command skipped, as per -tap argument)
  0%  TDR	0;
(Above Padding command skipped, as per -tap argument)
  0%  TIR	0;
(Above Padding command skipped, as per -tap argument)
  0%  ENDDR	DRPAUSE;
  0%  ENDIR	IRPAUSE;
  0%  STATE	IDLE;
  0%  SIR	8	TDI  (E0);
  0%  			MASK (FFFFFFFF);
  0%  SIR	8	TDI  (1C);
  0%  				FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF);
  0%  SIR	8	TDI  (C6);
  0%  SDR	8	TDI  (00);
  0%  RUNTEST	IDLE	2 TCK	1.00E-02 SEC;
  0%  SIR	8	TDI  (0E);
  0%  SDR	8	TDI  (01);
  0%  RUNTEST	IDLE	2 TCK	1.00E-02 SEC;
  0%  SIR	8	TDI  (3C);
  0%  			MASK (0000B000);
  0%  SIR	8	TDI  (46);
  0%  SDR	8	TDI  (01);
  0%  RUNTEST	IDLE	2 TCK	1.00E-02 SEC;
  0%  SIR	8	TDI  (7A);
  0%  RUNTEST	IDLE	2 TCK	1.00E-02 SEC;
  0%  			0000DCFFFFFFFFCDBDFFFFFF006CAC4C82E24282C21CB4624C8CB4AAACA26232045C2E4E860A00FF);
  0%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
  0%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
  5%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
  5%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
  5%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
  5%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
  5%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 10%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 10%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 10%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 10%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 10%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 15%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 15%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 15%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 15%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 15%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 20%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 20%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 20%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
 20%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 20%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 25%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 25%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 25%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 25%<PHONE_NUMBER>000000FF173300000000000000000000FFF4220000000000000000000A40FF17330000);
 25%  			0000FF173300000000000000000000FF173300000000000000000000FF1733000000000000000000);
 25%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 30%<PHONE_NUMBER>00000000000000FFD5360080000000000000000000FF173300000000000000000000FF);
 30%<PHONE_NUMBER>00FFF4220000000000000000000A40FF173300000000000000000000FF173300000000);
 30%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 30%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 30%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 35%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 35%  			00FFF4220000000000000000000A40FFF4220000000000000000000A40FFF4220000000000000000);
 35%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 35%<PHONE_NUMBER>00FFF4220000000000000000000A40FFF4220000000000000000000A40FFF422000000);
 35%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 40%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 40%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 40%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 40%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 40%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 45%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 45%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 45%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 45%<PHONE_NUMBER>000000FF173300000000000000000000FFD5360080000000000000000000FF17330000);
 45%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 50%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 50%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 50%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
 50%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 50%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
 55%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 55%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 55%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 55%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
 55%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 60%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 60%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 60%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 60%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 60%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 65%  			0000FF173300000000000000000000FF173300000000000000000000FF1733000000000000000000);
 65%  			FF173300000000000000000000FFD5360080000000000000000000FF173300000000000000000000);
 65%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 65%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 65%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 70%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 70%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 70%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 70%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 70%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
 75%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 75%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
 75%  			0000FF173300000000000000000000FF173300000000000000000000FF1733000000000000000000);
 75%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 75%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 80%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 80%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
 80%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 80%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 80%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 85%  			0000FF173300000000000000000000FF173300000000000000000000FF1733000000000000000000);
 85%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
 85%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 85%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 85%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 85%<PHONE_NUMBER>0000FFD68E0520000000000000000000FF173300000000000000000000FF1733000000);
 90%<PHONE_NUMBER>0000000000FF170F0720000000000000000000FF170F0720000000000000000000FFD5);
 90%<PHONE_NUMBER>00FF3F8700578200000000000000000A40FF173300000000000000000000FFECC001CF);
 90%<PHONE_NUMBER>FF3B1E00E410000000000000000000FF173300000000000000000000FF3B1E00E41000);
 90%  			FFD55A0010000000000000000000FF173300000000000000000000FF173300000000000000000000);
 90%  			01CEA0000000000000000000FFFB6B005410000000000000000000FFD55A00100000000000000000);
 95%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 95%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 95%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 95%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 95%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 95%  SIR	8	TDI  (FF);
 95%  RUNTEST	IDLE	100 TCK	1.00E-02 SEC;
 95%  SIR	8	TDI  (C0);
 95%  RUNTEST	IDLE	2 TCK	1.00E-03 SEC;
 95%  			MASK (FFFFFFFF);
 95%  SIR	8	TDI  (26);
 95%  RUNTEST	IDLE	2 TCK	2.00E-01 SEC;
 95%  SIR	8	TDI  (FF);
 95%  RUNTEST	IDLE	2 TCK	1.00E-03 SEC;
 95%  SIR	8	TDI  (3C);
 95%  			MASK (00002100);
Error: tdo check error at line 11
Error:     READ = 0x41111043
Error:     WANT = 0x21111043
Error:     MASK = 0xffffffff
Time used: 0m16s208ms
svf file programmed failed
Info : remote_bitbang interface quit

I: g.device.hardware: generating bitstream ID f4351d43ebcc1e42ec5196bfddf74d47
I: g.cli: running handler for applet 'jtag-openocd'
I: g.applet.interface.jtag_openocd: port(s) A voltage set to 3.3 V
I: g.applet.interface.jtag_openocd: socket: listening at tcp:localhost:33333
I: g.applet.interface.jtag_openocd: socket: new connection from [<IP_ADDRESS>]:53502
I: g.applet.interface.jtag_openocd: socket: connection from [<IP_ADDRESS>]:53502 lost
^CE: asyncio: Task exception was never retrieved
future: <Task finished name='Task-22' coro=<JTAGOpenOCDApplet.interact.<locals>.forward_in() done, defined at /home/jeremy/Downloads/glasgow/software/glasgow/applet/interface/jtag_openocd/__init__.py:164> exception=ValueError('Set of coroutines/Futures is empty.')>
Traceback (most recent call last):
  File "/home/jeremy/Downloads/glasgow/software/glasgow/applet/interface/jtag_openocd/__init__.py", line 167, in forward_in
    data = await iface.read()
  File "/home/jeremy/Downloads/glasgow/software/glasgow/access/direct/demultiplexer.py", line 240, in read
    await self._in_tasks.wait_one()
  File "/home/jeremy/Downloads/glasgow/software/glasgow/support/task_queue.py", line 81, in wait_one
    await asyncio.wait(self._live, return_when=asyncio.FIRST_COMPLETED)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 368, in wait
    raise ValueError('Set of coroutines/Futures is empty.')
ValueError: Set of coroutines/Futures is empty.
E: asyncio: Task was destroyed but it is pending!
task: <Task pending name='Task-21' coro=<JTAGOpenOCDApplet.interact.<locals>.forward_out() running at /home/jeremy/Downloads/glasgow/software/glasgow/applet/interface/jtag_openocd/__init__.py:159> wait_for=<Future pending cb=[Task.task_wakeup()]>>

Probe does work though:
glasgow run jtag-probe -V 3.3 --port A --pin-tck 0 --pin-tms 3 --pin-tdi 2 --pin-tdo 1 scan
I: g.device.hardware: device already has bitstream ID 62239ba31f7697d2809a2646248c966a
I: g.cli: running handler for applet 'jtag-probe'
I: g.applet.interface.jtag_probe: port(s) A voltage set to 3.3 V
I: g.applet.interface.jtag_probe: shifted 32-bit DR=<11000010000010001000100010000010>
I: g.applet.interface.jtag_probe: shifted 8-bit IR=<10000000>
I: g.applet.interface.jtag_probe: discovered 1 TAPs
I: g.applet.interface.jtag_probe: TAP #0: IR[8] IDCODE=0x41111043
I: g.applet.interface.jtag_probe: manufacturer=0x021 (Lattice Semi.) part=0x1111 version=0x4

I am using the version 0.1.dev2093+g00ad180 with amaranth 0.5.0.

@wanda-phi That sounds related to your changes, can you take a look?

A small update - the openocd error was caused by me using an ECP5 25F to test rather than an ECP5 12F. Sorry, was just in a bit of a rush.
Here is what a 12F looks like (working):
$ glasgow run jtag-openocd -V 3.3 --port A --pin-tck 0 --pin-tms 3 --pin-tdi 2 --pin-tdo 1 tcp:localhost:33333
I: g.device.hardware: generating bitstream ID f4351d43ebcc1e42ec5196bfddf74d47
I: g.cli: running handler for applet 'jtag-openocd'
I: g.applet.interface.jtag_openocd: port(s) A voltage set to 3.3 V
I: g.applet.interface.jtag_openocd: socket: listening at tcp:localhost:33333
I: g.applet.interface.jtag_openocd: socket: new connection from [<IP_ADDRESS>]:59722
I: g.applet.interface.jtag_openocd: socket: connection from [<IP_ADDRESS>]:59722 lost

$ openocd -f flash.ocd
Open On-Chip Debugger 0.12.0+dev-00634-g23c33e1d3 (2024-07-02-17:11)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
Info : Initializing remote_bitbang driver
Info : Connecting to localhost:33333
Info : remote_bitbang driver initialized
Info : Note: The adapter "remote_bitbang" doesn't support configurable speed
Info : JTAG tap: ecp5.tap tap/device found: 0x21111043 (mfg: 0x021 (Lattice Semi.), part: 0x1111, ver: 0x2)
Warn : gdb services need one or more targets defined
svf processing file: "blink.svf"
  0%  HDR	0;
(Above Padding command skipped, as per -tap argument)
  0%  HIR	0;
(Above Padding command skipped, as per -tap argument)
  0%  TDR	0;
(Above Padding command skipped, as per -tap argument)
  0%  TIR	0;
(Above Padding command skipped, as per -tap argument)
  0%  ENDDR	DRPAUSE;
  0%  ENDIR	IRPAUSE;
  0%  STATE	IDLE;
  0%  SIR	8	TDI  (E0);
  0%  			MASK (FFFFFFFF);
  0%  SIR	8	TDI  (1C);
  0%  				FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF);
  0%  SIR	8	TDI  (C6);
  0%  SDR	8	TDI  (00);
  0%  RUNTEST	IDLE	2 TCK	1.00E-02 SEC;
  0%  SIR	8	TDI  (0E);
  0%  SDR	8	TDI  (01);
  0%  RUNTEST	IDLE	2 TCK	1.00E-02 SEC;
  0%  SIR	8	TDI  (3C);
  0%  			MASK (0000B000);
  0%  SIR	8	TDI  (46);
  0%  SDR	8	TDI  (01);
  0%  RUNTEST	IDLE	2 TCK	1.00E-02 SEC;
  0%  SIR	8	TDI  (7A);
  0%  RUNTEST	IDLE	2 TCK	1.00E-02 SEC;
  0%  			0000DCFFFFFFFFCDBDFFFFFF006CAC4C82E24282C21CB4624C8CB4AAACA26232045C2E4E860A00FF);
  0%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
  0%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
  5%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
  5%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
  5%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
  5%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
  5%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 10%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 10%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 10%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 10%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 10%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 15%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 15%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 15%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 15%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 15%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 20%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 20%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 20%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
 20%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 20%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 25%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 25%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 25%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 25%<PHONE_NUMBER>000000FF173300000000000000000000FFF4220000000000000000000A40FF17330000);
 25%  			0000FF173300000000000000000000FF173300000000000000000000FF1733000000000000000000);
 25%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 30%<PHONE_NUMBER>00000000000000FFD5360080000000000000000000FF173300000000000000000000FF);
 30%<PHONE_NUMBER>00FFF4220000000000000000000A40FF173300000000000000000000FF173300000000);
 30%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 30%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 30%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 35%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 35%  			00FFF4220000000000000000000A40FFF4220000000000000000000A40FFF4220000000000000000);
 35%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 35%<PHONE_NUMBER>00FFF4220000000000000000000A40FFF4220000000000000000000A40FFF422000000);
 35%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 40%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 40%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 40%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 40%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 40%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 45%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 45%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 45%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 45%<PHONE_NUMBER>000000FF173300000000000000000000FFD5360080000000000000000000FF17330000);
 45%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 50%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 50%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 50%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
 50%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 50%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
 55%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 55%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 55%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 55%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
 55%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 60%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 60%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 60%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 60%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 60%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 65%  			0000FF173300000000000000000000FF173300000000000000000000FF1733000000000000000000);
 65%  			FF173300000000000000000000FFD5360080000000000000000000FF173300000000000000000000);
 65%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 65%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 65%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 70%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 70%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 70%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 70%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 70%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
 75%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 75%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
 75%  			0000FF173300000000000000000000FF173300000000000000000000FF1733000000000000000000);
 75%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 75%<PHONE_NUMBER>00000000000000FF173300000000000000000000FF173300000000000000000000FF17);
 80%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 80%<PHONE_NUMBER>00000000FF173300000000000000000000FF173300000000000000000000FF17330000);
 80%<PHONE_NUMBER>0000FF173300000000000000000000FF173300000000000000000000FF173300000000);
 80%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 80%  			000000FF173300000000000000000000FF173300000000000000000000FF17330000000000000000);
 85%  			0000FF173300000000000000000000FF173300000000000000000000FF1733000000000000000000);
 85%  			FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000FF);
 85%<PHONE_NUMBER>000000000000FF173300000000000000000000FF173300000000000000000000FF1733);
 85%<PHONE_NUMBER>0000000000FF173300000000000000000000FF173300000000000000000000FF173300);
 85%<PHONE_NUMBER>000000FF173300000000000000000000FF173300000000000000000000FF1733000000);
 85%<PHONE_NUMBER>0000FFD68E0520000000000000000000FF173300000000000000000000FF1733000000);
 90%<PHONE_NUMBER>0000000000FF170F0720000000000000000000FF170F0720000000000000000000FFD5);
 90%<PHONE_NUMBER>00FF3F8700578200000000000000000A40FF173300000000000000000000FFECC001CF);
 90%<PHONE_NUMBER>FF3B1E00E410000000000000000000FF173300000000000000000000FF3B1E00E41000);
 90%  			FFD55A0010000000000000000000FF173300000000000000000000FF173300000000000000000000);
 90%  			01CEA0000000000000000000FFFB6B005410000000000000000000FFD55A00100000000000000000);
 95%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 95%<PHONE_NUMBER>FF173300000000000000000000FF173300000000000000000000FF1733000000000000);
 95%  			00000000FF173300000000000000000000FF173300000000000000000000FF173300000000000000);
 95%  			00FF173300000000000000000000FF173300000000000000000000FF173300000000000000000000);
 95%<PHONE_NUMBER>00FF173300000000000000000000FF173300000000000000000000FF17330000000000);
 95%  SIR	8	TDI  (FF);
 95%  RUNTEST	IDLE	100 TCK	1.00E-02 SEC;
 95%  SIR	8	TDI  (C0);
 95%  RUNTEST	IDLE	2 TCK	1.00E-03 SEC;
 95%  			MASK (FFFFFFFF);
 95%  SIR	8	TDI  (26);
 95%  RUNTEST	IDLE	2 TCK	2.00E-01 SEC;
 95%  SIR	8	TDI  (FF);
 95%  RUNTEST	IDLE	2 TCK	1.00E-03 SEC;
 95%  SIR	8	TDI  (3C);
 95%  			MASK (00002100);
shutdown command invoked
Info : remote_bitbang interface quit

Unfortunately the jtag-svf applet still gives the same error:
$ glasgow run jtag-svf -V 3.3 --port A --pin-tck 0 --pin-tms 3 --pin-tdi 2 --pin-tdo 1 blink.svf
I: g.device.hardware: generating bitstream ID 62239ba31f7697d2809a2646248c966a
I: g.cli: running handler for applet 'jtag-svf'
I: g.applet.interface.jtag_svf: port(s) A voltage set to 3.3 V
Traceback (most recent call last):
  File "/home/jeremy/.local/bin/glasgow", line 8, in <module>
    sys.exit(run_main())
  File "/home/jeremy/Downloads/glasgow/software/glasgow/cli.py", line 939, in run_main
    exit(asyncio.new_event_loop().run_until_complete(main()))
  File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/home/jeremy/Downloads/glasgow/software/glasgow/cli.py", line 707, in main
    return applet_task.result()
  File "/home/jeremy/Downloads/glasgow/software/glasgow/cli.py", line 656, in run_applet
    return await applet.interact(device, args, iface)
  File "/home/jeremy/Downloads/glasgow/software/glasgow/applet/interface/jtag_svf/__init__.py", line 294, in interact
    await coro
  File "/home/jeremy/Downloads/glasgow/software/glasgow/applet/interface/jtag_svf/__init__.py", line 120, in svf_state
    path = {
KeyError: (<JTAGState.UNKNOWN: 'Unknown'>, <JTAGState.IDLE: 'Run-Test/Idle'>)

Indeed, that is my bug. Could you test if #615 fixes it?

Works great now! Thanks for the fix. Please feel to close this as necessary @whitequark


test: enhancements to reconciler finalizer tests

This change makes a few enhancements to the reconciler-finalizer tests to help with debugging, namely:

Wrap the logging of reconciler logs in a cleanup. This ensures that the logs get printed in the case of a failure, even if kubectl returns before the test fails (e.g. Pod eviction)
Replace usages of Wait with taskgroup/watch. This provides more useful logging as each watch event gets logged.

/assign @karlkfi


SUBMARINE-217. Add Submarine Workbench introduction document

What is this PR for?
Submarine workbench introduction document mainly contains following parts:
1. workbench homepage
2. Project create/list/delete/modify manager
What type of PR is it?
[Documentation]
Todos

[ ] - Interpreter create/list/delete/modify manager
[ ] - Job create/list/delete/modify manager
[ ] - Data create/list/delete/modify manager
[ ] - Model create/list/delete/modify manager
[ ] - System user/role/team/organization manager

What is the Jira issue?

https://issues.apache.org/jira/browse/SUBMARINE-217

How should this be tested?

CI Pass

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? Yes

Thanks @liuxunorg for the great work.
There are some typo, frok should be fork


Support reading the Java version from system.properties file

The system.properties file in Java projects can contain java.runtime.version=11 which indicates the Java version to use. We should support reading that and setting the java version based on the version defined there.
https://howtodoinjava.com/java/basics/java-system-properties/

Has the issue been solved? It seems that Nixpacks cannot recognize the java version from system.properties file automatically.


Unable to remove ec2 instance

[WARNING]	2020-02-20T18:52:51.507Z	a2d2eb-2fc7-441b-8069-1983e7765bfe	security group sg-e15642ca: An error occurred (DependencyViolation) when calling the DeleteSecurityGroup operation: resource sg-e142ca has a dependent object

its looks like the security group is still attached to an ec2 instance.
Maybe the instance is not fully deleted when the lambda function try to nuke this security group

Yes issue is in the code, my job done is via https://github.com/rebuy-de/aws-nuke

Fixed in version 2.7.1 with boto3 waiter.

Worked Thanks


Create a new pull request by comparing changes across two branches

Description

Motivation & Context

Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[ ] I have read the contributing guidelines
[ ] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-{your_pr_number}--twbs-bootstrap.netlify.app/

Related issues

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.07%) to 96.06%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
2020

Relevant Lines:
2070

💛  - Coveralls


Testing PR

This is an example comment2024-05-04 01:04:06

This is an example comment2024-05-05 05:17:31

This is an example comment2024-05-05 05:17:47

This is an example comment2024-05-05 05:34:39

This is an example comment 2024-05-05 05:36:24

This is an example comment 2024-05-05 05:36:43

This is an example comment 2024-05-05 05:44:20

This is an example comment 2024-05-05 05:45:36

This is an example comment 2024-05-05 05:45:59

This is an example comment 2024-05-05 05:49:03

This is an example comment 2024-05-05 05:49:31

This is an example comment 2024-05-05 05:50:38

This is an example comment 2024-05-05 05:53:13


added contributing notes

Added contributing notes for demos
A lot of lines got formatted due to the code formatter on my IDE, apologies for that.

Ok!


Added blog for Manton Reece

Thanks for putting together this directory! Good luck.

Now I feel guilty for making the field called twitter_url, when it clearly should have been twitter_or_microblog_url 😂
Seriously though, thanks for adding it!


Stanford Java course link

Hacktoberfest notes:

due to the volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open-source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s)
For resources
Description
It is a Stanford course.
Why is this valuable (or not)?
It is a good course on fundamentals.
Excerpt from Course description "This course is the largest of the introductory programming courses and is one of the largest courses at Stanford. Topics focus on the introduction to the engineering of computer applications emphasizing modern software engineering principles: object-oriented design, decomposition, encapsulation, abstraction, and testing.
Programming Methodology teaches the widely-used Java programming language along with good software engineering principles. Emphasis is on good programming style and the built-in facilities of the Java language. The course is explicitly designed to appeal to humanists and social scientists as well as hard-core techies. In fact, most Programming Methodology graduates end up majoring outside of the School of Engineering."
How do we know it's really free?
All course videos are in the link.
For book lists, is it a book? For course lists, is it a course? etc.
It is a course.
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

Please review.

Thanks!


Improve assignment BOT logic

https://github.com/codinasion/codinasion/blob/e4a4a4e10739c5a5625bff4da80de081a285f135/github-bots/assign-me/src/index.ts#L8-L12

For now, this will work 👍🏻
But we should also consider that team members can also suggest
Originally posted by @harshraj8843 in https://github.com/codinasion/codinasion/pull/4545#discussion_r1269597123

Reference

#4544

@harshraj8843 Hey, I am interested to contribute. Can you assign me this issue to work on?

!assign

Can you help me understand more about -  But we should also consider that team members can also suggest ?
Any example scenario would be helpful.


port-check.ts does not log when port checking fails

Expected Behaviour
Error logging telling me that the port checking is failing. In this particular case the container does not have bash available, so port-check.ts fails on checking if the port has been bound until it times out.
Actual Behaviour
No logs, even with DEBUG=testcontainers*, only times out after 60 seconds with a error message saying that the port was never bound.
Testcontainer Logs
  testcontainers DEBUG System diagnostics: {"node":{"version":"v16.17.0","architecture":"x64","platform":"linux"},"docker":{"serverVersion":"20.10.18","operatingSystem":"Pop!_OS 22.04 LTS","operatingSystemType":"linux","architecture":"x86_64","cpus":24,"memory":33578258432}} +1ms
  testcontainers DEBUG Not pulling image as it already exists: ghcr.io/<image> +88ms
  testcontainers DEBUG Creating new Reaper for session: f93bb52c39c6705655ea67640c7d2497 +0ms
  testcontainers DEBUG No registry auth locator found for registry: "https://index.docker.io/v1/" +0ms
  testcontainers DEBUG Checking if image exists: testcontainers/ryuk:0.3.2 +0ms
  testcontainers DEBUG Not pulling image as it already exists: testcontainers/ryuk:0.3.2 +86ms
  testcontainers INFO  Creating container for image: testcontainers/ryuk:0.3.2 +1ms
  testcontainers INFO  Starting container testcontainers/ryuk:0.3.2 with ID: d2553b4d2da9ce084fd66546ffc91589d643898b0ed7a11e7e768d8e079a0965 +62ms
  testcontainers DEBUG Waiting for container to be ready: d2553b4d2da9ce084fd66546ffc91589d643898b0ed7a11e7e768d8e079a0965 +228ms
  testcontainers DEBUG Waiting for log message "/.+ Started!/" +0ms
  testcontainers INFO  Container is ready +3ms
  testcontainers DEBUG Connecting to Reaper d2553b4d2da9ce084fd66546ffc91589d643898b0ed7a11e7e768d8e079a0965 on localhost:49263 +0ms
  testcontainers DEBUG Connected to Reaper d2553b4d2da9ce084fd66546ffc91589d643898b0ed7a11e7e768d8e079a0965 +1ms
  testcontainers INFO  Creating container for image: ghcr.io/<image> +0ms
  testcontainers INFO  Starting container ghcr.io/<image> with ID: 863d846339a565fd48a04b194840d65d0d3d9652082a5d9e5733322f77bbf465 +42ms
  testcontainers DEBUG Waiting for container to be ready: 863d846339a565fd48a04b194840d65d0d3d9652082a5d9e5733322f77bbf465 +223ms
  testcontainers DEBUG Waiting for host port 49264 for 863d846339a565fd48a04b194840d65d0d3d9652082a5d9e5733322f77bbf465 +0ms
  testcontainers DEBUG Waiting for internal port 8080 for 863d846339a565fd48a04b194840d65d0d3d9652082a5d9e5733322f77bbf465 +0ms
  testcontainers DEBUG Host port 49264 ready for 863d846339a565fd48a04b194840d65d0d3d9652082a5d9e5733322f77bbf465 +2ms
  testcontainers ERROR Container failed to be ready: Error: Port 8080 not bound after 60000ms for 863d846339a565fd48a04b194840d65d0d3d9652082a5d9e5733322f77bbf465 +1m

Error: Port 8080 not bound after 60000ms for 863d846339a565fd48a04b194840d65d0d3d9652082a5d9e5733322f77bbf465

    at /home/<dir>/node_modules/testcontainers/dist/wait-strategy.js:64:23
    at IntervalRetryStrategy.<anonymous> (/home/<dir>/node_modules/testcontainers/dist/retry-strategy.js:36:28)
    at Generator.next (<anonymous>)
    at fulfilled (/home/<dir>/node_modules/testcontainers/dist/retry-strategy.js:5:58)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Steps to Reproduce
Running any container that has neither /bin/sh or /bin/bash available. You'll see that the commands in port-check.ts:41:43 will all fail like this:
[
  {
    "output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"/bin/sh\": stat /bin/sh: no such file or directory: unknown\r\n",
    "exitCode": 126
  },
  {
    "output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"/bin/sh\": stat /bin/sh: no such file or directory: unknown\r\n",
    "exitCode": 126
  },
  {
    "output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"/bin/bash\": stat /bin/bash: no such file or directory: unknown\r\n",
    "exitCode": 126
  }
]

Environment Information
{
  "node": { "version": "v16.17.0", "architecture": "x64", "platform": "linux" },
  "docker": {
    "serverVersion": "20.10.18",
    "operatingSystem": "Pop!_OS 22.04 LTS",
    "operatingSystemType": "linux",
    "architecture": "x86_64",
    "cpus": 24,
    "memory":<PHONE_NUMBER>2
  }
}

Hi @karl-run, thanks for raising. The reason for not logging the result of the port-check is that it can be very noisy (every 100ms we run several commands). In your example, one of the 3 commands is outputting a 126 exit code, but it doesn't mean that the other commands aren't trying with more success. I worry therefore that outputting this error is misleading.

Hmm, yeah I agree that it can be noisy. But when the overall check times out, maybe one could log the result of the last attempt? That would have saved me quite a few hours of debugging today, for example. :smiling_face_with_tear:

@karl-run it's a good idea, I'll experiment with some approaches. I'd like to be able to fail-fast with an error message but not sure it's safe to do so. If not I'd like to output an error message ASAP to save you from waiting 2 minutes to see what failed. Worst case (if it's too noisy) we can output something at the end.

It might be too specific, but /bin/sh not being available is becoming more and more common as distroless is becoming more and more common. So maybe failing fast on /bin/sh missing? :shrug:
At least it would be very helpful for any poor soul in the future trying to run a distroless based image in testcontainers.

Also, for any poor soul coming to this issue in the future because they are running some distroless based image, this is the solution to your problem:
.withWaitStrategy(Wait.forLogMessage(/.*some log output your container has saying it is ready.*/))

@karl-run have a look at the linked PR, specifically the test names, do you think this covers most things/is a worthwhile improvement?

Looks really good! In my opinion this is definitely worth while.

Excellent, thanks @karl-run, released in 8.14.0

I would like to keep specific container-related info out of my tests. For example, I'd like to avoid something like this:
const environment = await new DockerComposeEnvironment(
    composeFilePath,
    composeFile
).withWaitStrategy(
    'some-specific-container',
    Wait.forLogMessage(/.*some log output specific to the container.*/)
).up();

I'd rather create a healthcheck for that container in my Docker compose file so that all the container-specific configs are defined in one place. This is also an alternative solution to the problem of distroless images if you add a binary like wget as described here: https://github.com/GoogleContainerTools/distroless/issues/183#issuecomment-571723446
This approach has led me to wish for a configurable default wait strategy:
const environment = await new DockerComposeEnvironment(
    composeFilePath,
    composeFile
).withDefaultWaitStrategy(Wait.forHealthCheck());

Or, perhaps, an alternative signature to withWaitStrategy (or a separate method name):
const environment = await new DockerComposeEnvironment(
    composeFilePath,
    composeFile
).withWaitStrategy((container: Dockerode.Container) => {
    if (container.Labels... === "something") return Wait.forHttp(...);
    if (container.Labels... === "other") return Wait.forSomething();
    return Wait.forHealthCheck();
})


CPL file missing

Can you provide the PCB CPL / Centroid file so if one wants they could order the pcbs from pcbway pre done?

Hi, Sorry, but I don't provide the PCB CPL/Centroid files for assembly. You can find pre-assembled boards in my shop though. If you're up for some DIY, all the files you need are on GitHub. You can order a blank PCB and the components, then solder them yourself. I'm trying to avoid having these boards show up on sites like Ali. Hope that works for you!


Add dynamic http endpoints

I really like the shape of this. +1 to merge after squashing the license header in.

Erm..just noticed: why chttpd tests are defined here?

@kxepal: I thought they are integration tests but maybe they aren't. Let me know if you want me to move them into chttpd.

@iilyak mmm..looks like something in between. Ok, let's put them here. Need to handle this question later.

They test various endpoints including the ones defined outside chttpd application.

PR is squashed

I'll move _oauth into here and squash again


feat: generate default/data/ui/* programatically

This PR makes all files under default/data/ui folder programatically instead of copying them from UCC UI repository.

Codecov Report

Merging #749 (dec0798) into release/v5.27.0 (db00649) will increase coverage by 0.78%.
The diff coverage is 65.30%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@                 Coverage Diff                 @@
##           release/v5.27.0     #749      +/-   ##
===================================================
+ Coverage            64.87%   65.66%   +0.78%
===================================================
  Files                   41       42       +1
  Lines                 2309     2327      +18
  Branches               445      446       +1
===================================================
+ Hits                  1498     1528      +30
+ Misses                 769      757      -12
  Partials                42       42

Impacted Files
Coverage Δ

splunk_add_on_ucc_framework/commands/build.py
13.97% <10.52%> (+0.57%)
:arrow_up:

splunk_add_on_ucc_framework/data_ui_generator.py
100.00% <100.00%> (ø)


Add Press Kit page

Audience

Design system / design / tech newsletters
Speakers who want to talk about the DTCG
Youtubers
Twitter
Other tech news / media

Assets

Logo (PNG and SVG)
Short description of the DTCG
Slightly longer description of the DTCG
List of useful URLs to learn more and keep up to date
Twitter handle
List of contributors and their Twitter handles
Anything else you think would be useful

I added more content and working on the long description.

I added the long-form description but could really use a writer/editor!


Possibly maybe fix after update?

The actual issue was that they added some Parameters to the Bark method, which made your Patch fail.
This only makes the mod load into the game without error. If the update otherwise broke the mod, please ignore this and close the PR

Using Aze.Publicize 👎

Thanks, I already had these changes locally and more,.

Thanks, I already had these changes locally and more,
Also what would you use instead of Aze.Publicize?

This is the latest csproj from the nuget template:

Notice the BepInEx.AssemblyPublicizer.MSBuild
With that, you only need to put Publicize="true" into the Reference itself.
There are some other improvements that have been made to the csproj; but that's that

Cool, I will give this a look, since Aze.Publicize is in my opinion clunky to use. Thanks!


No ECDSA host key is known... issue with bosh ssh

When connecting to VM with bosh ssh it fails to retrieve ECDSA key before connection:
ubuntu@zjb:~$ bosh ssh log_parser/1
Acting as user 'admin' on deployment 'logsearch' on 'my-bosh'
Enter password (use it to sudo on remote host): *
Target deployment is `logsearch'

Setting up ssh artifacts

Director task 1753

Task 1753 done
Starting interactive shell on job log_parser/1
No ECDSA host key is known for <IP_ADDRESS> and you have requested strict checking.
Host key verification failed.

Cleaning up ssh artifacts

Director task 1754

Task 1754 done

Workaround:
ubuntu@zjb:~$ ssh <IP_ADDRESS>
The authenticity of host '<IP_ADDRESS> (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is 98:c2:2c:47:d7:5a:23:5c:0a:32:45:3c:28:40:98:d8.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
Ubuntu 14.04.2 LTS
Permission denied (publickey).

After that step bosh ssh it is able to connect VM with bosh ssh.

We recently introduced --strict_host_key_checking flag. We also have a few stories comping up about automatically checking host key fingerprint: https://www.pivotaltracker.com/story/show/102530088

Updated bosh-cli up to 3093.
Still the same.

Still the same with 3094.
$ bosh ssh foo/0

[WARNING] Loading the cli took 15.4 seconds, consider cleaning your gem environment

Acting as user 'admin' on deployment 'foo' on 'bar'
Enter password (use it to sudo on remote host): ******
Target deployment is `foo'

Setting up ssh artifacts

Director task 25

Task 25 done
Starting interactive shell on job foo/0
No ECDSA host key is known for <IP_ADDRESS> and you have requested strict checking.
Host key verification failed.

Cleaning up ssh artifacts

Director task 26

Task 26 queued
$ bosh --version

[WARNING] Loading the cli took 12.7 seconds, consider cleaning your gem environment

BOSH 1.3094.0

As mentioned in release notes: https://github.com/cloudfoundry/bosh/releases/tag/stable-3093 you must have CLI, Director and stemcells updated.
Note that this will not currently work on bosh-lite since we did not publish new bosh-lite stemcells yet.

Got it, thanks


[bug] Lot of API requests when video is not even playing

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
2.0.0-next.13
Current Behavior
When many players were rendered on the list on a screen, there are a lot of API calls. 😞
https://www.veed.io/view/ceb3ecfc-ee52-4797-a8a7-503ce7ed81be?panel=share
Expected Behavior
We can fetch and auto-upload things when there is user interaction like play in the player.
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

cc @0xcadams

This should be fixed by https://github.com/livepeer/livepeer.js/issues/60


Powerset, another solve to the problem

I also use recursive. However, I think my code  is more simple .Here is my code
export const Powerset = arr1 => {
  if (!Array.isArray(arr1) || arr1.length === 0) {
    return [[]]
  }

  let [a1, ...rest] = arr1

  let restResult = Powerset(rest)
  let result = [...restResult]

  for (let subSet of restResult) {
    result.push([a1, ...subSet])
  }

  return result
}

Can you do PR with your change proposal?


RC test: diffusion 1.0.0-rc.1

@KatieWoe, @arouinfar, @ariel-phet, diffusion/1.0.0-rc.1 is ready for RC testing.
This release is for brand=phet only. PhET-iO and a11y are not included.
Document issues in https://github.com/phetsims/gas-properties/issues (not diffusion) and link to this issue.
@ariel-phet instructed me to assign this to @KatieWoe with "top" priority.

General RC Test

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Check this LoL spreadsheet and notify AR or AM if it not there.
If this is rc.1 please do a memory test.
When making an issue, check to see if it was in a previously published version
If there is a console available, check for errors and include them in the Problem Description.

Focus and Special Instructions
Diffusion sim consists of the Diffusion screen from Gas Properties, with no changes.  The majority of testing can therefore be done as part of https://github.com/phetsims/QA/issues/386, with spot testing on a few platforms.

Link(s)

Simulation
iFrame
XHTML
Test Matrix
Legends of Learning Harness

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Actually moving this one to high-priority since as quoted

Diffusion sim consists of the Diffusion screen from Gas Properties, with no changes. The majority of testing can therefore be done as part of #386, with spot testing on a few platforms.

So main sim testing first

[ ] Win 10 chrome
[ ] Win 10 firefox
[ ] Win 10 edge

[ ] Mac 10.14 chrome
[ ] Mac 10.14 safari

[ ] Win 7 IE
[x] Mac 10.11 safari

[ ] ChromeOS
[ ] iOS 12

Removing matrix and adding spotcheck list

QA is done

Thanks you QA team! I'll leave this open until 1.0.0-rc.2 is published.

diffusion 1.0.0-rc.2 is published, testing in https://github.com/phetsims/QA/issues/391. Closing.


Handling users through the DB users table

I changed the DB schema to store users in DB: users table created.
I use now user_ref (int) instead of user_id (VARCHAR) to refer to a user.
In UserInputDto I use pk to refer to the user instead of, as before, his/her email.
I did basic testing and it appears to work, more testing is however needed.
Fixes #6.

Currently, it does not work (Python exceptions).

To be honest, I am a little confused how to rewrite this. I will concentrate on this PR.

It seems that I've finished this PR. It was preliminarily tested and I'd vote to merge it.

After logged in and try to use the UI I got an error
  commands = await agent.handle_user_input(user_input_req)
  File "/Users/alexsandro.souza/projects/my/chatflow/server/src/core/agent/agent_service.py", line 55, in handle_user_input
    add_message_dto = AddMessageDto(
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for AddMessageDto
user_ref
  none is not an allowed value (type=type_error.none.not_allowed)

After logged in and try to use the UI I got an error. user.pk is None

Fixed.

@vporton I will test it and merge if it is working fine


it's a answer to deploy the flaskr demo project with uWSGI and nginx, if therer's a error: unable to load app 0 (mountpoint='') (callable not found or import error)

I have try many way and search to find the answer, but it seems not the real answer to solve the error : unable to load app 0 (mountpoint='') (callable not found or import error)

it's my Solution.

add a file to use the flaskr passage, (here in my try is app), the file to use the flaskr passage is called run.py (the name is created as you like)

the run.py content

add the uWSGI ini file, its content

start the uWSGI with command in your machine

the nginx of the site conf

finally to look in the browser (yes i use the docker to manager the development Environment)

that's all. hope there is some help to you

Please use Stack Overflow for questions about your own code. This tracker is for issues related to the project itself. Be sure to include a minimal, complete, and verifiable example.


AWAY and BACK events are logged under the user

Causes other events like QUIT and NICK to also be included, as it opens up a log entry for that user.
-- [2019-10-03]
[03:30:11] [away] asdf: "Auto-away"
[03:38:17] [back] asdf
[03:52:23] [away] asdf: "Auto-away"
[04:10:58] [back] asdf
[04:11:22] [nick] asdf (fdsa)

-- [2019-10-04]
[07:53:56] [away] asdf: "Auto-away"
[07:54:36] [back] asdf
[08:05:21] [away] asdf: "Auto-away"
[10:08:10] [quit] asdf: "Connection closed for inactivity"

Fixed in 9f4037dd6d431821aec33573b08c5e8bd993a694.


adding area chart

Still not tested but look good to me!

@ali-rostami I added a few small fixes.
Thank you for this update!

thank you @embeddedt  and @kisvegabor  for helping me add this small improvement.


Cartesian Joins Create ALL Combinations, Not All Possible Combinations

While testing this package I noticed that the resulting table contains all possible combinations of values contained within the dimension list, as opposed to all of the possible combinations. This creates rows where the combination of values could never occur in the base dataset.
For example, the testing case I was going through contained two dimensions called user_name and organization_name. There's a relationship between those 2 fields in that an organization can have multiple users but a user is only going to be part of 1 organization.
The dataset produced by the macro has rows for a particular in every potential organization.
In the actual metric calculation, that's not that big of a deal because the values provided are equal to 0 but it could be a bit of an issue when working with BI tools. Drop downs / filters would contain combinations that aren't possible and potentially give the data consumers the wrong conclusion of the relationship between those two fields.
Not sure if this is intended behavior but I figured I'd flag just in case!

Hmm that's an interesting one! We've taken the cross-join approach to have a consistent spine across all dimensions, but you're right that your use case isn't compatible with that.
Can you share a small worked example of what you're trying to calculate, with how it's currently behaving and how you'd rather it work? I can imagine doing something like only date spining a combination of columns if they already exist somewhere else in the dataset, but it's still pretty nebulous

Happy to! Right now, I'm working with a dataset where each row represents a user-session. A very simplistic version of the dataset would look like this:

Person
Organization
Session Time
Session Date

Joel
dbt-labs
2
2022-02-13

Callum
Sisu
4
2022-02-13

When I use the metric package, the result produced looks like:

Date_Day
Person
Organization
Metric_Name

2022-02-13
Joel
dbt-labs
2

2022-02-13
Joel
Sisu
0

2022-02-13
Callum
dbt-labs
0

2022-02-13
Callum
Sisu
4

At small scale with low cardinality columns, it isn't really that big of a deal. But with high cardinality columns it expands out massively. So I think date spining the combination of columns that already exist in the dataset would be my ideal solution. I also think this would massively reduce the compute cost of adding additional fields by lowering the size of the output? I say this because I experimented on 49 rows and 8 dimensions where the resulting output was 81m rows (this is where I stumbled onto the exact user/organization example expressed above). Hope that helps clarify!

@joellabes I know this issue is more of an strategic question and less of a 'how should we do it' but I decided to test it out on my repo this afternoon and was able to make it work with the following changes to the spine__values and spine sections.
),
spine__values as (

select distinct
{%- for dim in dimensions -%}
    {%- if metrics.is_dim_from_model(metric, dim) %}
        {{dim}}
        {% if not loop.last %},{% endif %}
    {% endif -%}
{%- endfor %}
from source_query

),
spine as (

select *
from spine__time
cross join spine__values

),

Now, I'll caveat all that follows by saying I only really tested it on a single metric with two dimensions. But the results that I saw were pretty significant.

The overall row size of the table output dropped from 400k to 11k.
The runtime of the model dropped from 14.3s to 2.91s (though Snowflake caching might have been helping out here)

Yay! I haven’t forgotten you - I just need to get some more tests in before starting to change the macros' behaviours, and before I could do that I had to wrap up https://github.com/dbt-labs/dbt-core/issues/4813 😅
This sounds extremely reasonable! Once I get my act together on testing (hoping to be next week) I'd happily merge a PR to that effect, assuming it still returned the same results.

I thought about this more over the weekend, and I would still like to support this use case, but I think both have a place so we might have to shudder add an option!
@drewbanin what do you think? In Callum's case, a cross join of every dimension is nonsensical, but for low-cardinality use cases I can still see it being valuable.


cargo shuttle too big to dock in saltern

Description
or so some dude in discord said, idk @deltanedas

im 99% sure i made the dock just big enough to fit it but ill see

Can confirm that the lattices block the front of the shuttle from docking.


Trying to re-compile for UE source-code version, 5.2.1 but getting this issue, I only want to compile for win64, but it is getting failed due to android SDK which I don't even need

D:\UnreaSourceCode5.2.1\Engine\Build\BatchFiles>RunUAT.bat BuildPlugin -plugin="D:\AsyncLoadingScreen\AsyncLoadingScreen.uplugin" -package="D:\AsyncLoadingScreen\UE521"
Running AutomationTool...
Using bundled DotNet SDK version: 6.0.302
Starting AutomationTool...
Parsing command line: BuildPlugin -plugin=D:\AsyncLoadingScreen\AsyncLoadingScreen.uplugin -package=D:\AsyncLoadingScreen\UE521
Initializing script modules...
Total script module initialization time: 0.53 s.
Executing commands...
Copying 170 file(s) using max 64 thread(s)
Reading plugin from D:\AsyncLoadingScreen\UE521\HostProject\Plugins\AsyncLoadingScreen\AsyncLoadingScreen.uplugin...
Building plugin for host platforms: Win64
Running: D:\UnreaSourceCode5.2.1\Engine\Binaries\ThirdParty\DotNet\6.0.302\windows\dotnet.exe "D:\UnreaSourceCode5.2.1\Engine\Binaries\DotNET\UnrealBuildTool\UnrealBuildTool.dll" UnrealEditor Win64 Development -Project=D:\AsyncLoadingScreen\UE521\HostProject\HostProject.uproject -plugin=D:\AsyncLoadingScreen\UE521\HostProject\Plugins\AsyncLoadingScreen\AsyncLoadingScreen.uplugin -noubtmakefiles -manifest=D:\AsyncLoadingScreen\UE521\HostProject\Saved\Manifest-UnrealEditor-Win64-Development.xml -nohotreload -log="D:\UnreaSourceCode5.2.1\Engine\Programs\AutomationTool\Saved\Logs\UBT-UnrealEditor-Win64-Development.txt"
Log file: D:\UnreaSourceCode5.2.1\Engine\Programs\AutomationTool\Saved\Logs\UBT-UnrealEditor-Win64-Development.txt
Using 'git status' to determine working set for adaptive non-unity build (D:\UnreaSourceCode5.2.1).
Parsing headers for UnrealEditor
Running Internal UnrealHeaderTool D:\AsyncLoadingScreen\UE521\HostProject\HostProject.uproject D:\AsyncLoadingScreen\UE521\HostProject\Intermediate\Build\Win64\UnrealEditor\Development\UnrealEditor.uhtmanifest -WarningsAsErrors
Total of 6 written
Reflection code generated for UnrealEditor in 12.6795084 seconds
Writing manifest to D:\AsyncLoadingScreen\UE521\HostProject\Saved\Manifest-UnrealEditor-Win64-Development.xml
Building UnrealEditor...
Using Visual Studio 2022 14.34.31947 toolchain (C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933) and Windows 10.0.18362.0 SDK (C:\Program Files (x86)\Windows Kits\10).
Determining max actions to execute in parallel (8 physical cores, 16 logical cores)
Executing up to 8 processes, one per physical core
Building 4 actions with 4 processes...
[1/4] Compile [x64] Module.AsyncLoadingScreen.cpp
[2/4] Link [x64] UnrealEditor-AsyncLoadingScreen.lib
Creating library D:\AsyncLoadingScreen\UE521\HostProject\Plugins\AsyncLoadingScreen\Intermediate\Build\Win64\x64\UnrealEditor\Development\AsyncLoadingScreen\UnrealEditor-AsyncLoadingScreen.lib and object D:\AsyncLoadingScreen\UE521\HostProject\Plugins\AsyncLoadingScreen\Intermediate\Build\Win64\x64\UnrealEditor\Development\AsyncLoadingScreen\UnrealEditor-AsyncLoadingScreen.exp
[3/4] Link [x64] UnrealEditor-AsyncLoadingScreen.dll
Creating library D:\AsyncLoadingScreen\UE521\HostProject\Plugins\AsyncLoadingScreen\Intermediate\Build\Win64\x64\UnrealEditor\Development\AsyncLoadingScreen\UnrealEditor-AsyncLoadingScreen.suppressed.lib and object D:\AsyncLoadingScreen\UE521\HostProject\Plugins\AsyncLoadingScreen\Intermediate\Build\Win64\x64\UnrealEditor\Development\AsyncLoadingScreen\UnrealEditor-AsyncLoadingScreen.suppressed.exp
[4/4] WriteMetadata UnrealEditor.target
Total time in Parallel executor: 4.09 seconds
Total execution time: 64.24 seconds
Took 64.7949502s to run dotnet.exe, ExitCode=0
Building plugin for target platforms: Android, IOS, Linux, LinuxArm64, TVOS, Win64, HoloLens
Running: D:\UnreaSourceCode5.2.1\Engine\Binaries\ThirdParty\DotNet\6.0.302\windows\dotnet.exe "D:\UnreaSourceCode5.2.1\Engine\Binaries\DotNET\UnrealBuildTool\UnrealBuildTool.dll" UnrealGame Android Development -Project=D:\AsyncLoadingScreen\UE521\HostProject\HostProject.uproject -plugin=D:\AsyncLoadingScreen\UE521\HostProject\Plugins\AsyncLoadingScreen\AsyncLoadingScreen.uplugin -noubtmakefiles -manifest=D:\AsyncLoadingScreen\UE521\HostProject\Saved\Manifest-UnrealGame-Android-Development.xml -nohotreload -architectures=arm64 -log="D:\UnreaSourceCode5.2.1\Engine\Programs\AutomationTool\Saved\Logs\UBT-UnrealGame-Android-Development.txt"
Log file: D:\UnreaSourceCode5.2.1\Engine\Programs\AutomationTool\Saved\Logs\UBT-UnrealGame-Android-Development.txt
Using 'git status' to determine working set for adaptive non-unity build (D:\UnreaSourceCode5.2.1).
Platform Android is not a valid platform to build. Check that the SDK is installed properly.
Took 2.0229118s to run dotnet.exe, ExitCode=6
UnrealBuildTool failed. See log for more details. (D:\UnreaSourceCode5.2.1\Engine\Programs\AutomationTool\Saved\Logs\UBT-UnrealGame-Android-Development.txt)
AutomationTool executed for 0h 1m 10s
AutomationTool exiting with ExitCode=6 (6)
BUILD FAILED

Hi, if you only need Win64 platform. You can add WihitelistPlatform Win64 to AsyncLoadingScreen.uplugin:

{
	"FileVersion": 3,
	"Version": 8,
	"VersionName": "1.5.1",
	"EngineVersion": "5.3.0",
	"FriendlyName": "Async Loading Screen",
	"Description": "Allows you to configure a Loading Screen system in the project settings easily and automatically add a Loading Screen in your game whenever you open a new level.",
	"Category": "Loading Screen",
	"CreatedBy": "Truong Bui",
	"CreatedByURL": "https://github.com/truong-bui/AsyncLoadingScreen",
	"DocsURL": "https://github.com/truong-bui/AsyncLoadingScreen",
	"MarketplaceURL": "com.epicgames.launcher://ue/marketplace/product/01f39767dc6b4290877f38365787cbf8",
	"SupportURL": "https://github.com/truong-bui/AsyncLoadingScreen/issues",
	"CanContainContent": true,
	"Installed": true,
	"Modules": [
		{
			"Name": "AsyncLoadingScreen",
			"Type": "Runtime",
			"LoadingPhase": "PreLoadingScreen",
			"TargetDenyList": [
				"Server"
			],
			"WhitelistPlatforms": [
				"Win64"
			]
		}
	]
}


Some pretty cli for trace

See the output to see what the client does.
$ st2 trace list
+--------------------------+----------------------------------------------------+-------------------------------+
| id                       | trace_tag                                          | start_timestamp               |
+--------------------------+----------------------------------------------------+-------------------------------+
| 55d3c9b132ed35435dd6a68f | trigger_instance-55d3c9b132ed35435dd6a68e          | Wed, 19 Aug 2015 00:11:29 UTC |
| 55d3c9ac32ed35435dd6a68d | trigger_instance-55d3c9ac32ed35435dd6a68c          | Wed, 19 Aug 2015 00:11:24 UTC |
| 55d3c9a732ed35435dd6a68b | trigger_instance-55d3c9a732ed35435dd6a68a          | Wed, 19 Aug 2015 00:11:19 UTC |
| 55d3c9a532ed35435dd6a689 | trigger_instance-55d3c9a532ed35435dd6a688          | Wed, 19 Aug 2015 00:11:17 UTC |
| 55d3c9a232ed35435dd6a687 | trigger_instance-55d3c9a232ed35435dd6a686          | Wed, 19 Aug 2015 00:11:14 UTC |
| 55d3c99f32ed35435dd6a685 | trigger_instance-55d3c99f32ed35435dd6a684          | Wed, 19 Aug 2015 00:11:11 UTC |
| 55d3c99f32ed35435dd6a683 | trigger_instance-55d3c99f32ed35435dd6a682          | Wed, 19 Aug 2015 00:11:11 UTC |
| 55d3d29732ed35435dd6a691 | TestPassiveSensor-ec4cf37b7bc94b4aab66cc033f1fbefa | Wed, 19 Aug 2015 00:49:27 UTC |
+--------------------------+----------------------------------------------------+-------------------------------+

$ st2 trace get 55d3d29732ed35435dd6a691
id: 55d3d29732ed35435dd6a691
trace_tag: TestPassiveSensor-ec4cf37b7bc94b4aab66cc033f1fbefa
start_timestamp: 2015-08-19T00:49:27.034587Z
+--------------------------+-----------------+-----------------------------+
| id                       | type            | updated_at                  |
+--------------------------+-----------------+-----------------------------+
| 55d3d29732ed35435dd6a690 | triggerinstance | 2015-08-19T00:49:27.034665Z |
| 55d3c99e32ed354372c0f7fe | rule            | 2015-08-19T00:49:27.057020Z |
| 55d3d29732ed35435dd6a693 | execution       | 2015-08-19T00:49:27.102228Z |
| 55d3d29732ed35435dd6a694 | triggerinstance | 2015-08-19T00:49:27.285334Z |
+--------------------------+-----------------+-----------------------------+

$ st2 trace list -c TestPassiveSensor-ec4cf37b7bc94b4aab66cc033f1fbefa
id: 55d3d29732ed35435dd6a691
trace_tag: TestPassiveSensor-ec4cf37b7bc94b4aab66cc033f1fbefa
start_timestamp: 2015-08-19T00:49:27.034587Z
+--------------------------+-----------------+-----------------------------+
| id                       | type            | updated_at                  |
+--------------------------+-----------------+-----------------------------+
| 55d3d29732ed35435dd6a690 | triggerinstance | 2015-08-19T00:49:27.034665Z |
| 55d3c99e32ed354372c0f7fe | rule            | 2015-08-19T00:49:27.057020Z |
| 55d3d29732ed35435dd6a693 | execution       | 2015-08-19T00:49:27.102228Z |
| 55d3d29732ed35435dd6a694 | triggerinstance | 2015-08-19T00:49:27.285334Z |
+--------------------------+-----------------+-----------------------------+

Wondering if we should switch id and type columns :P.

Wondering if we should switch id and type columns :P.

Likely we can switch stuff around. Almost all our lists have id as the first field so for starters it is better to be consistent with that for now. Lets have some user feedback and then we can make the Ux changes.

$ st2 trace list -c TestPassiveSensor-ec4cf37b7bc94b4aab66cc033f1fbefa
id: 55d3d29732ed35435dd6a691
trace_tag: TestPassiveSensor-ec4cf37b7bc94b4aab66cc033f1fbefa
start_timestamp: 2015-08-19T00:49:27.034587Z
+--------------------------+-----------------+-----------------------------+
| id                       | type            | updated_at                  |
+--------------------------+-----------------+-----------------------------+
| 55d3d29732ed35435dd6a690 | triggerinstance | 2015-08-19T00:49:27.034665Z |

I assume that in this output id refers to the traced resource.
If that's the case, imo, it would make it more clear if the id header field is called resource_id and we display it after the resource type. Otherwise it's a bit confusing (at least to me) and not immediately clear to what this id refers to.

Every list of our has id as column 1. Pretty much everywhere id == resource_id so I picked consistency.
Also we make some assumptions like https://github.com/StackStorm/st2/blob/master/st2client/st2client/formatters/table.py#L49 which makes it preferable to use id as the 1st field and to retain the name. I don't necessarily agree with those impl choices but am very wary of changing the formatter code. It would be nice to be able to A/B test the choice and see which one works better.
At this point I will wait for a few more folks to chime-in and see which direction consensus goes and will change if we all mostly agree on swapping id and type

@manasdk The difference with other operations (list actions, list rules, list executions, etc.) is that in that case id refers to the resource on which you are operating (action / rule / executions).
In the trace case though, you list traces so you would assume the id refers to the trace, but it actually refers to the resource trace is point to so this is what makes it confusing and not consistent (as mentioned above, please correct me if I'm wrong and if that id actually refers to the trace and not the resource - if it does, then we are OK :)).

The difference with other operations (list actions, list rules, list executions, etc.) is that in that case id refers to the resource on which you are operating (action / rule / executions).

Not really. The get for a workflow execution (which this is modeled on) has similar behavior.
$ st2 execution get 55d3fd82fa4bf55edf94934b
id: 55d3fd82fa4bf55edf94934b
action.ref: st2cd.st2_pkg_f20
status: succeeded
start_timestamp: 2015-08-19T03:52:32.549801Z
end_timestamp: 2015-08-19T03:55:13.898937Z
+--------------------------+-----------+-------------------+-------------------------+-------------------------------+
| id                       | status    | task              | action                  | start_timestamp               |
+--------------------------+-----------+-------------------+-------------------------+-------------------------------+
| 55d3fd83fa4bf55ed053c8dd | succeeded | get_build_server  | linux.dig               | Wed, 19 Aug 2015 03:52:35 UTC |
| 55d3fd85fa4bf55ed053c8df | succeeded | clone_repo        | st2cd.git_clone         | Wed, 19 Aug 2015 03:52:37 UTC |
| 55d3fd8dfa4bf55ed053c8e1 | succeeded | version           | st2cd.st2_version       | Wed, 19 Aug 2015 03:52:45 UTC |
| 55d3fd8efa4bf55ed053c8e3 | succeeded | echo_version      | core.local              | Wed, 19 Aug 2015 03:52:46 UTC |
| 55d3fd90fa4bf55ed053c8e5 | succeeded | version_hack      | st2cd.version_hack      | Wed, 19 Aug 2015 03:52:48 UTC |
| 55d3fd91fa4bf55ed053c8e8 | succeeded | make_rpms         | st2cd.make_rpms         | Wed, 19 Aug 2015 03:52:49 UTC |
| 55d3fdf3fa4bf55ed053c8ea | succeeded | check_pkgs        | st2cd.check_pkgs        | Wed, 19 Aug 2015 03:54:27 UTC |
| 55d3fdf4fa4bf55ed053c8ec | succeeded | create_build_dir  | core.remote             | Wed, 19 Aug 2015 03:54:28 UTC |
| 55d3fdf5fa4bf55ed053c8ee | succeeded | update_st2_deploy | st2cd.update_st2_deploy | Wed, 19 Aug 2015 03:54:29 UTC |
| 55d3fdf7fa4bf55ed053c8f0 | succeeded | rsync_st2_deploy  | linux.rsync             | Wed, 19 Aug 2015 03:54:31 UTC |
| 55d3fdfafa4bf55ed053c8f3 | succeeded | rsync_rpms        | linux.rsync             | Wed, 19 Aug 2015 03:54:34 UTC |
| 55d3fdfbfa4bf55ed053c8f5 | succeeded | cp_st2_deploy     | core.remote_sudo        | Wed, 19 Aug 2015 03:54:35 UTC |
| 55d3fdfdfa4bf55ed053c8f7 | succeeded | cp_rpms           | core.remote_sudo        | Wed, 19 Aug 2015 03:54:37 UTC |
| 55d3fdfefa4bf55ed053c8f9 | succeeded | cp_rpms_repo      | core.remote_sudo        | Wed, 19 Aug 2015 03:54:38 UTC |
| 55d3fe00fa4bf55ed053c8fb | succeeded | rebuild_repo      | core.remote_sudo        | Wed, 19 Aug 2015 03:54:39 UTC |
| 55d3fe1ffa4bf55ed053c8fe | succeeded | update_current    | core.remote_sudo        | Wed, 19 Aug 2015 03:55:11 UTC |
| 55d3fe20fa4bf55ed053c900 | succeeded | clean_repo        | st2cd.git_clean         | Wed, 19 Aug 2015 03:55:12 UTC |
+--------------------------+-----------+-------------------+-------------------------+-------------------------------+

But believe me I get your point. I hear it loud and clear and almost agree with you and FWIW was one of the options I considered. This table will guaranteed undergo a redesign in the next week or so. It is not final but is functional at this point so until I gather some more feedback on this and other aspects of the table I am reluctant to make any changes.

but it actually refers to the resource trace is point to so this is what makes it confusing and not consistent

No you are right it is id of a TraceComponent so a resource/entity in StackStorm which is not a trace. If I explicitly tell you that the id is the id of the component then are you still confused? In fact what else could it be?


Autocomplete codes Support

Just need Autocomplete codes Support

I've added support for reference completion #35 it will be in version 0.4
But currently it will only autocomplete references from the same file because multi-file resolve is not implemented yet (see #24)

Cool~


Update Lab05_Home Health.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by AnthonyOakley on behalf of MOC Labs Review.


Failed to parse XML... Error: not well-formed (invalid token): line 1, column 0

Failed to parse XML... Error: not well-formed (invalid token): line 1, column 0
Running on local URL:  http://<IP_ADDRESS>:7860
Parsing PDF...
Parsing XML...

Try this: https://github.com/Weixin-Liang/LLM-scientific-feedback/issues/6#issuecomment-1751886948

Try this: #6 (comment)

I tried, no changes

Try to alter the port of the parser server, 8080 might be occupied by other apps:
python -m sciencebeam_parser.service.server --port=7080
and the main.py:
convert_url = "http://localhost:7080/api/convert"

Try to alter the port of the parser server, 8080 might be occupied by other apps:
python -m sciencebeam_parser.service.server --port=7080
and the main.py:
convert_url = "http://localhost:7080/api/convert"

changed port still not working

Thanks for your interest in our system. It seems this error happens when running on non-linux system. Unfortunately ScienceBeam only supports x86 Linux. Let us know if you find a way to install ScienceBeam on other systems.

We now added a new system that supports texts as input:
Usage:
python main_from_text.py  # If you are using non-linux operating systems or want to generate feedback from the parsed paper in text format


[ Feature Request ] Fast wrap offset

When fast wrapping, an option to specify an offset from the pattern match is needed.
This way, the inserted match could be inserted before the matched pair
Example:
| denotes the cursor position
print([ | foo) -- Trigger fast wrap
print([ | fooa -- Press 'a'
print([foo)]

if an offset can be configured, the use can choose to prefer the square bracket to be placed before the ) by having a negative offset.
I already have a fork with this feature if it sound good and can open a Pull Request.
By default, behaviour is unchanged.

thank pr is welcome


[BUG]: file related dev field extraction is dependent on the Filesystem type

During the development of ppc64 me and @Andreagit97 noticed that some open related tests were failing to assert the dev field:
Expected equality of these values:
 *(T*)(m_event_params[m_current_param].valptr)
   Which is: 29
 param
   Which is: 37

Digging into it, we noticed that vfs_getattr_nosec calls a filesystem dependent getattr callback (https://elixir.bootlin.com/linux/v6.7.7/source/fs/stat.c#L135), that, for btrfs (the filesystem being used by our ppc64 test node), sets dev field differently: https://elixir.bootlin.com/linux/v6.7.7/source/fs/btrfs/inode.c#L8692.
See the call trace:
@[
    generic_fillattr+12
    btrfs_getattr+228
    vfs_getattr_nosec+244
    vfs_fstat+128
    __do_sys_newfstat+80
    system_call_exception+372
    system_call_vectored_common+348
]: 2

This means that our dev field is FS dependent and thus it cannot be relied upon.
There is no way to fix this (at least on eBPF probes), since we miss the needed helpers.

/milestone TBD

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale


scrapcore.scraper.selenium - ERROR - Message: session not created: This version of ChromeDriver only supports Chrome version 76

Hey, this looks like an awesome python project, but I'm not able to run the demo code provided due to this error:
scrapcore.scraper.selenium - ERROR - Message: session not created: This version of ChromeDriver only supports Chrome version 76
I'm on a Mac, and Chrome is up to v83.0.4103.116 now.  I see the SerpScrap changelog shows support for chrome driver versions >= 76.*.  Any ideas on how to fix this?
0.13.0: updated dependencies: chromedriver >= 76.0.3809.68 to use actual driver, sqlalchemy>=1.3.7 to solve security issues and other minor update changes

Hey man, check your chrome version again and download the exact same version of chrome driver so they match. Then it will work.

I use last 72 driver version and scrapper runs.


MultiselectField is not working (with xlsx format)

Describe the bug
In our Django project, we have a model with Multiselectfield, when we import an export from this model, we see that these fields are not loaded.
https://pypi.org/project/django-multiselectfield/
To Reproduce

Create a model with a MultiSelectField. (for example:

class SampleStudent:
    name= models.CharField(max_length=128, null=True, blank=True)
    countries = MultiSelectField(
        choices=COUNTRY_CODE_CHOICES,
        null=True,
        blank=True
    )

Generate a few random rows.
export as xlsx
try to import related file

Versions (please complete the following information):

Django Import Export: 4.2.0
Python 3.11
Django 4.2.13

Expected behavior
What should happen is that MultiSelectField should be exported correctly and imported correctly.

Thanks for raising - if you can create steps to reproduce in a branch using the example app, that would help us to investigate.


Route problem

Hi there,
Could you please help me out with a problem with this package. Actually the problem is that when I try to protect my routes with auth middleware in the web.php file, then the auth middleware doesn't work, but however if I use the middleware in the api.php file then the routes in the web.php is also protected.
It seems that the package is prioritizing api.php file before web.php file. I hope I have made the situation clear.
Thanks

i'll take a look

@Artem-Schander just figured it out. The problem is because both the api.php and the web.php has the same route created in them as a boilerplate when a new module is created. This is what causing the problem. It just hit me as soon as I posted the issue!

cool, so I'm closing this issue


TypeError: Invalid type for attribute: <class 'htmltools._core.TagList'>.Consider calling str() on this value before treating it as a tag attribute.

I got this error when creating a shiny app with python. After ui.sidebar with all input, I added ui.panel_fixed(output_widget('some_plot')). I don't understand what's happening however I've checked many times, and everything was correct.

Can you please share a small app that reproduces your issue? You can use https://shinylive.io/py/ as a quick way to write and share the app.

from shiny import App, ui, session, Outputs, Inputs
from shinywidgets import output_widget, render_widget
from pathlib import Path
TITLE = "Baobab"
page = ui.tags.head(
ui.tags.link(rel="stylesheet",type="text/css",href="style.css")
)
app_ui = ui.page_navbar(
ui.nav_panel("Baobab",
ui.layout_sidebar(
sidebar=ui.sidebar(
ui.input_file('data','Please upload csv file', accept=['.csv']),
ui.input_date('start','Start', value='1980-01-01'),
ui.input_date('end', 'End', value='2024-05-29'),
    ),
     main=ui.panel_fixed(
          output_widget("plot", width="auto",height="auto"),
     )
)

),
ui.nav_panel('Machine Learning',
ui.layout_sidebar(
sidebar=ui.sidebar(
ui.input_select('select', 'Select', ['supervised','unsupervised','deep learning']),
)
  )
),
#id="page",
title = ui.tags.div(#ui.img(src='baobab.jpg', height="40px", style="margin:5px;"),
                    ui.h5(""+TITLE),
                    style="display:flex;-webkit-filter:drop-shadow(2px 2px 2px #222)"),
                    bg="#0062cc",
                    inverse=True,
                    header=page

)
www_dir = Path(file).parent / "www"
def server(input, output, session):
pass
app = App(app_ui, server, static_assets=www_dir)

I want to make a plot on a sidebar but when I run only this code it I got TypeError: Invalid type for attribute: <class 'htmltools._core.TagList'>.Consider calling str() on this value before treating it as a tag attribute.

You're very close! You just need to make two small adjustments.
    ui.nav_panel(
        "Baobab",
        ui.layout_sidebar(
-           sidebar=ui.sidebar(
+           ui.sidebar(
                ui.input_file("data", "Please upload csv file", accept=[".csv"]),
                ui.input_date("start", "Start", value="1980-01-01"),
                ui.input_date("end", "End", value="2024-05-29"),
            ),
-           main=ui.panel_fixed(
+           ui.panel_fixed(
                output_widget("plot", width="auto", height="auto"),
            ),
        ),
    ),

First, instead of main=ui.panel_fixed(), pass ui.panel_fixed() as a direct child of ui.layout_sidebar(). ui.layout_sidebar() doesn't require a main argument, instead all of its unnamed children are added directly to the main area. When you use main=, it's being treated as an HTML attribute to be added to the layout container.
Second, the first argument of ui.layout_sidebar() should be the sidebar, which should be passed positionally, i.e. without the sidebar=.

Thank you so much! It works now!


Fb 90 refactor persistence layer setup

PR Type
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
What Is the Current Behavior?
persistence layer setup in values.yaml
persistence:
  size: 1Gi
  nfs:
    enabled: false
    # existingClaim: helm-iste-icm-7-11-nfs-testdata-pvc
    # server: <<ipaddress or hostname>>
    # path: /export/data/iste/test
  azurefiles:
    enabled: false
    shareName: icm-as-share
    secretName: icm-as-share-secret
  # set enable true for local storage (.e.g. local testing)
  local:
    enabled: true
    sites:
      dir: <local folder>
      size: 1Gi
  cluster:
    enabled: false
    storageClass: azurefile

Issue Number: Closes #91
What Is the New Behavior?
persistence layer setup in values.yaml
persistence:
  size: 1Gi
# type cluster | nfs | azurefiles | existingClaim | local
  type: local
  existingClaim: claimName
  cluster:
    storageClass: azurefile
  azurefiles:
    shareName: icm-as-share
    secretName: icm-as-share-secret
  nfs:
    server: <ipaddress or hostname>
    path: <server folder>
  local :
    path: <local folder>

Does this PR Introduce a Breaking Change?

[x] Yes
[ ] No
Other Information

Readme.md:

local, cluster, azurefiles, nfs are possible persistence options. The default is local where persistence.local.sites.dir need to be set to a valid local folder.

--->persistence.local.sites.path
and existingClaim-option
Could you please also add an analog block to the icm-web/README.md?


[EXAMPLE] Add CRAFT Your Dataset: Task-Specific Synthetic Dataset Generation Through Corpus Retrieval and Augmentation example

Is your feature request related to a problem? Please describe.
We could create an example replicating this paper, we have most of the pieces and seems quite interesting:
CRAFT Your Dataset: Task-Specific Synthetic Dataset Generation Through Corpus Retrieval and Augmentation
Describe the solution you'd like
Add a replica/example of the paper in the documentation (maybe adding relevant steps/tasks if applies).
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

hi @plaguss : Can I take this up?

Hi @bikash119, sure! Other than the special prompts this task would need, it would need a data sampler, specifically from a vector database. Instead of that, for testing I think it would be easier if you play around with a simpler sampler. You can use something like the one in this PR: https://github.com/argilla-io/distilabel/pull/925/files#diff-528f40365aa1e97bc8332703af9a49626c919e5e42145eb12e443fc4021fc1a2. It's not merged yet, but you can copy that.

hi @plaguss , Thank you for pointing the resources. As I go through the code, I am trying to internalize the code. Nothing with the code, just that I am bit slow here.
On another node, as CRAFT needs a vector storage to query the corpus based on few-shots, do you think it will be beneficial to put effort in looking at sqlite-vec and if possible incorporating it as a step in CRAFT task.
Please let me know your thoughts.

Hi! We are still working on the best way of building this. For example, #1006 is still a work in progress, but I would say say LanceDB is a good choice. If you find a way of extending this to other possible databases that would be perfect, but put much effort on that. I would suggest to take a look at the implementation in the PR to see if that would work here for CRAFT, otherwise we will have to update it 😄

Sure!


The Desktop Player occasionally stops responding

OS:
Windows 10
Issue Descriptions:
The program will stop responding when playing a song..sometimes. It will continue playing music. Often, it'll start responding once more at a random point during the song, only to stop responding once more when the next song starts.
I started having this issue after rebuilding my PC with a new processor (i7-6850K, GTX 1070, 32GB of DDR4) - it was working great before.
Steps to Reproduce:
Start playing music on the system listed above.

I have the same issue, using a laptop with Windows 10. i5-6300HQ, GTX 950M, 8GB of DDR4. I started having this problem after I got it back from being fixed by the manufacturer, getting the motherboard replaced.

Do you have native window borders enabled or disabled?

I have it disabled.

Try enabling it and seeing if that helps. I've had freezing issues on windows with it disabled.

It still freezes for me, if I minimize it and pull it back up it turns completely white.

Didn't work for me either. The window doesn't turn white for me, but it does freeze up.

@rapdactyl Please disable desktop notifications and try again 👍

@MarshallOfSound  Whoa, that worked! Thanks :]


Handle different formats of Git SSH URLs

https://github.com/open-cluster-management/backlog/issues/12960
Handle different formats of Git SSH URLs

/retest

/test images


DestiniWright Created using Colaboratory

I think it's fixed now. I think I accidentally put it in the wrong repository when I finished yesterday.


[Homepage] Adding CNCF Landscape to Meshery Home page

Current Behavior
We currently have no section highlighting Meshery as proudly representing service mesh management in the CNCF Landscape.
Desired Behavior
It will be good to created a new section, adding the CNCF landscape in Meshery home page

Below is the design file
https://www.figma.com/file/SMP3zxOjZztdOLtgN4dS2W/Meshery-UI?node-id=1060%3A8

@austinogiza please point to the CNCF Landscape SVG to be used.

@austinogiza what section on the Homepage should this be on?

@Lezette  this should be after the Community and GSOD section

@leecalcote I would like to work on this


Exception thrown: 'System.IO.IOException' in System.Net.Security.dll

From output window in VS:
Exception thrown: 'System.IO.IOException' in System.Net.Security.dll
Exception thrown: 'System.IO.IOException' in System.Net.Security.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Verbose logs are written to:
C:\Users\sam\AppData\Local\Temp\vscode-chrome-debug.txt

I checked vscode-chrome-debug.txt - there is nothing there that appears to be a .net stack trace.  Is there another place I can look for where these errors might be logged?
My app is .net core 3.1 running under IIS/Kestrel.  Nothing in Event Viewer under app or IIS.
Thanks

Could you look in here: https://docs.microsoft.com/en-us/visualstudio/debugger/how-to-use-the-call-stack-window?view=vs-2019
and see if any of the suggested options to see callstack can help you?

@carlossanlop Thanks I set the debugger to break on .net exceptions and I was able to get the stack trace.

Thank you for confirming, @leaderanalytics . I'll close the issue since it seems the question was about getting a meaningful stacktrace, but if you need additional help with the specifics of the callstack, feel free to open a new issue.

I'm getting the same error and im working .Net 5.0 but my call stack section is empty. Do you have a suggestion?

@unurolker this is an old and closed issue, if you think you are hitting a similar problem could you please create a new issue detailing what you are doing and what's the behavior that you expect.

It appears I had the exact same issue. Repairing visual studio did it for me

Same issue here-- ye ole Chat Gippidy says it might could be related to certs? But I have the dev cert installed. As far as I can recall this was happening after project instantiation with the .NET Core 8 Web API project template.

Same here :
Microsoft.Hosting.Lifetime: Information: Application started. Press Ctrl+C to shut down.
Microsoft.Hosting.Lifetime: Information: Hosting environment: Development
Microsoft.Hosting.Lifetime: Information: Content root path: D:\sanr\repos\clean-architecture\GymManagement\src\GymManagement.Api
Exception thrown: 'System.IO.IOException' in System.Net.Security.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Exception thrown: 'System.IO.IOException' in System.Net.Security.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
'GymManagement.Api.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.4\System.Threading.Channels.dll'.
'GymManagement.Api.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.4\System.Net.WebSockets.dll'.
'GymManagement.Api.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.4\System.Threading.Tasks.dll'.
'GymManagement.Api.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.4\System.Net.NameResolution.dll'.
'GymManagement.Api.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.4\System.Text.RegularExpressions.dll'.


fixed PR for #104

fixed PR for #104

sorry. Merge conflict.

I'm sorry. Then, how i can fix this?

Start a new Pull Request is the easy solution. For the proper solution, search online, esp. stackoverflow.

okay, i created the new one. can you please check #108?

Merged.