text:
sysmon.service failed because the control process exited with error code

Sysmon on a Red Hat Enterprise Linux release 8.4 (Ootpa) running on a Oracle VirtuabBox failed to run.
From the journalctl -xe file:
sysmon[3080]: parent already had regs=0 stack=0 marks
sysmon[3080]: math between map_value pointer and register with unbounded min value is not allowed
sysmon[3080]: processed 4010 insns (limit 1000000) max_states_per_insn 6 total_states 264 peak_states 251 mark_read 105
sysmon[3080]: -- END PROG LOAD LOG --
sysmon[3080]: libbpf: prog 'ProcCreateRawExit': failed to load: -22
sysmon[3080]: libbpf: failed to load object './/sysmonEBPFkern4.17-5.1_core.o'
sysmon[3080]: ERROR: failed to load prog: 'Invalid argument'
sysmon[3080]: Telemetry failed to start: eBPF object could not be loaded
As a newbie will appreciate how to proceed.

Can you add the -t switch and paste a more complete log from ''journalctl -xe"?
Also, is this file present on the system? /sys/kernel/btf/vmlinux

@team480 - I reproduced the issue and a fix will be pushed shortly.

@team480 - Fix has now been merged. Please try it out and let me know. Thanks.

Hi @MarioHewardt  - file vmlinux - exists.

From the ''journalctl -xe":
Mar 28 19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 926: (79) r8 = *(u64 *)(r10 -72)
Mar 28 19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: ; event->m_Extensions[PC_CommandLine] = extLen;
Mar 28 19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 927: (79) r1 = *(u64 *)(r10 -64)
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 928: (63) *(u32 *)(r1 +108) = r8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]:  R0=inv0 R1_w=map_value(id=0,off=0,ks=4,vs=65512,imm=0) R2=inv0 R6=inv(id=0) R7=invP0 R8_w=inv(id=0) R9=map_value(id=0,off=128,ks=4,vs=65512,imm>
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 929: (b7) r1 = 2840
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 930: (79) r6 = *(u64 *)(r10 -80)
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 931: (0f) r6 += r1
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 932: (bf) r1 = r10
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: ;
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 933: (07) r1 += -32
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: ; dentry = BPF_CORE_READ((struct task_struct *)base, fs, pwd.dentry);
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 934: (b7) r2 = 8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 935: (bf) r3 = r6
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 936: (85) call bpf_probe_read_kernel#113
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: last_idx 936 first_idx 926
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=4 stack=0 before 935: (bf) r3 = r6
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=4 stack=0 before 934: (b7) r2 = 8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 937: (b7) r1 = 48
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 938: (79) r3 = *(u64 *)(r10 -32)
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 939: (0f) r3 += r1
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 940: (bf) r1 = r10
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: ;
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 941: (07) r1 += -24
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: ; dentry = BPF_CORE_READ((struct task_struct *)base, fs, pwd.dentry);
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 942: (b7) r2 = 8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 943: (85) call bpf_probe_read_kernel#113
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: last_idx 943 first_idx 926
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=4 stack=0 before 942: (b7) r2 = 8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 944: (7b) *(u64 *)(r10 -56) = r9
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: ; ptr += (extLen & (CMDLINE_MAX_LEN - 1));
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 945: (bf) r7 = r9
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: 946: (0f) r7 += r8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: last_idx 946 first_idx 944
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 945: (bf) r7 = r9
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 944: (7b) *(u64 *)(r10 -56) = r9
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]:  R0_w=inv(id=0) R6_w=inv(id=0) R7=invP0 R8_rw=invP(id=0) R9_r=map_value(id=0,off=128,ks=4,vs=65512,imm=0) R10=fp0 fp-24=mmmmmmmm fp-32=mmmmmmmm >
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: parent didn't have regs=100 stack=0 marks
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: last_idx 943 first_idx 926
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 943: (85) call bpf_probe_read_kernel#113
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 942: (b7) r2 = 8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 941: (07) r1 += -24
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 940: (bf) r1 = r10
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 939: (0f) r3 += r1
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 938: (79) r3 = *(u64 *)(r10 -32)
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 937: (b7) r1 = 48
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 936: (85) call bpf_probe_read_kernel#113
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 935: (bf) r3 = r6
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 934: (b7) r2 = 8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 933: (07) r1 += -32
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 932: (bf) r1 = r10
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 931: (0f) r6 += r1
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 930: (79) r6 = *(u64 *)(r10 -80)
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 929: (b7) r1 = 2840
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 928: (63) *(u32 *)(r1 +108) = r8
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 927: (79) r1 = *(u64 *)(r10 -64)
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: regs=100 stack=0 before 926: (79) r8 = *(u64 *)(r10 -72)
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]:  R0_w=inv0 R1_w=map_value(id=0,off=128,ks=4,vs=65512,umax_value=16383,var_off=(0x0; 0x3fff)) R2_w=inv0 R6=inv(id=0) R7=invP0 R8_w=invP(id=0,umax>
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: parent already had regs=0 stack=0 marks
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: math between map_value pointer and register with unbounded min value is not allowed
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: processed 4010 insns (limit 1000000) max_states_per_insn 6 total_states 264 peak_states 251 mark_read 105
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: -- END PROG LOAD LOG --
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: libbpf: prog 'ProcCreateRawExit': failed to load: -22
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: libbpf: failed to load object './/sysmonEBPFkern4.17-5.1_core.o'
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: ERROR: failed to load prog: 'Invalid argument'
19:28:09 RHEL8.4.myguest.virtualbox.org sysmon[1684]: Telemetry failed to start: eBPF object could not be loaded
Could you elaborate the full command context "with a -t"?

Hi, I was able to reproduce the issue and the fix has been merged. For now, you will need to build Sysmon until a new package has been released (preliminary in a couple of days).
The -t switch adds extended logging that is helpful when troubleshooting. You can add it as a switch when starting sysmon. For example:
sudo sysmon -t -i sysmon_config_file

I have this issue as well with a Proxmox LXC
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/sched/sched_process_exit': relo #5: insn #117 against 'perfErrorsMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'ProcTerminated': found map 7 (perfErrorsMap, sec 13, off 224) for insn #117
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/sock/inet_sock_set_state': collecting relocation for section(9) 'tracepoint/sock/inet_soc>
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/sock/inet_sock_set_state': relo #0: insn #9 against 'configMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'TCPconnection': found map 0 (configMap, sec 13, off 0) for insn #9
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/sock/inet_sock_set_state': relo #1: insn #22 against 'eventStorageMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'TCPconnection': found map 8 (eventStorageMap, sec 13, off 256) for insn #22
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/sock/inet_sock_set_state': relo #2: insn #144 against 'eventMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'TCPconnection': found map 5 (eventMap, sec 13, off 160) for insn #144
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/sock/inet_sock_set_state': relo #3: insn #157 against 'perfErrorsMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'TCPconnection': found map 7 (perfErrorsMap, sec 13, off 224) for insn #157
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/sock/inet_sock_set_state': relo #4: insn #169 against 'perfErrorsMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'TCPconnection': found map 7 (perfErrorsMap, sec 13, off 224) for insn #169
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/sock/inet_sock_set_state': relo #5: insn #182 against 'perfErrorsMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'TCPconnection': found map 7 (perfErrorsMap, sec 13, off 224) for insn #182
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': collecting relocation for section(11) 'tracepoint/skb/consume_skb'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #0: insn #10 against 'configMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 0 (configMap, sec 13, off 0) for insn #10
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #1: insn #44 against 'packetStorageMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 3 (packetStorageMap, sec 13, off 96) for insn #44
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #2: insn #420 against 'UDPsendAge'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 4 (UDPsendAge, sec 13, off 128) for insn #420
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #3: insn #441 against 'UDPsendAge'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 4 (UDPsendAge, sec 13, off 128) for insn #441
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #4: insn #449 against 'eventStorageMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 8 (eventStorageMap, sec 13, off 256) for insn #449
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #5: insn #548 against 'eventMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 5 (eventMap, sec 13, off 160) for insn #548
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #6: insn #561 against 'perfErrorsMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 7 (perfErrorsMap, sec 13, off 224) for insn #561
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #7: insn #573 against 'perfErrorsMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 7 (perfErrorsMap, sec 13, off 224) for insn #573
Apr 05 10:21:50 lino sysmon[47250]: libbpf: sec '.reltracepoint/skb/consume_skb': relo #8: insn #586 against 'perfErrorsMap'
Apr 05 10:21:50 lino sysmon[47250]: libbpf: prog 'UDPsend': found map 7 (perfErrorsMap, sec 13, off 224) for insn #586
Apr 05 10:21:50 lino sysmon[47250]: libbpf: Failed to bump RLIMIT_MEMLOCK (err = -1), you might need to do it explicitly!
Apr 05 10:21:50 lino sysmon[47250]: libbpf: Error in bpf_object__probe_loading():Operation not permitted(1). Couldn't load trivial BPF program. Make sure>
Apr 05 10:21:50 lino sysmon[47250]: libbpf: failed to load object './/sysmonEBPFkern5.6-_core.o'
Apr 05 10:21:50 lino sysmon[47250]: ERROR: failed to load prog: 'Operation not permitted'
Apr 05 10:21:50 lino sysmon[47204]: Telemetry failed to start: eBPF object could not be loaded

@team480 - Since a fix has been merged, I'm closing this issue. If you see it again, please feel free to reopen. Thanks.

authors: MarioHewardt macolinob team480

repo: Sysinternals/SysmonForLinux


text:
Calling File.Create(@"C:\foo.ifc") fails in latest version

Throws exception
System.IO.DirectoryNotFoundException: 'Could not find a part of the path 'C:\foo.ifc'.'

Just updated from version 178 to 198 and this error has appeared in a test project. The actual project ref is
<PackageReference Include="System.IO.Abstractions.TestingHelpers" Version="2.1.0.198" />

but this does imply System.IO.Abstractions v 2.1.0.198.

@PhilipDaniels this is more than likely an intended change (PR #286).
Assuming you're trying something along the following:
var fs = new MockFileSystem();
fs.File.Create(@"C:\foo.ifc")

This would throw a DirectoryNotFoundException because C:\ does not exist. This is similar behavior you would see in System.IO.File.Create
System.IO.File.Create(@"K:\foo.ifc"); // assuming you don't have a K drive

If this is not the use case that you are experiencing this issue with, please let me know!

Quick response! Yes, that is exactly what is happening. I am sympathetic to making the mock file system more accurately mimic reality, it was just a bit of a surprise to have a minor version bump suddenly fail some tests that have been OK for 2 years :-) Luckily the following both work
fileSystem.Directory.CreateDirectory(@"C:\");
fileSystem.Directory.CreateDirectory(@"C:\a\b\c\d");

So it is not too onerous to ensure that directories get created in the tests.

source: gharchive/issue

authors: PhilipDaniels jpreese

license: MIT

license_type: permissive

license_source: github-api


text:
add LICENSE

This solves the first part of #2

Awesome, thanks!

source: gharchive/pull-request

authors: daviwil japhir

repo: SystemCrafters/rational-emacs


text:
3 addresses for LCD issue

Hello,
I have some minor issues with using the scan.py as well as getting anything loaded onto the LCD screen.
I was going to post a screenshot, but github isn't allowing that at this time for some reason.
Upon running the scan.py script, I receive an array for the LCD address as follows in HEX:
[62, 96, 112]
and converted to decimal with make it
[3E, 60, 70]
This is strange as there should only be one address.
Either way, through troubleshooting, all 3 values work, if used separately, in the test.py script, as it runs and goes each line of testing script for the LCD, but the LCD doesn't illuminate or anything.
If the whole array is used, an error message occurs. Please help on this matter. 3 addresses is strange, and no LCD illumination or messaging is not helping. Thank you.
-Dom

The 3 address might be due to your LCD backpack you may have to check the documentation on which pads short to make which address
Worst comes to worst you may need to state an address for the LCD API

authors: Algester Domingmr


text:
🛑 Fnb storefront is down

In 5e7c1c3, Fnb storefront (https://fnb39.com) was down:

HTTP code: 504
Response time: 11748 ms

Resolved: Fnb storefront is back up in fd2b824 after 10 minutes.


text:
编译的时候march 中rv32imacfxthead 和 rv32imafc的区别是什么？发现生成elf文件不同

编译的时候march 中rv32imacfxthead 和 rv32imafc的区别是什么？发现生成elf文件不同

unsubscribe
在 2022-03-22 18:41:32，"zhushunyi" @.***> 写道：
编译的时候march 中rv32imacfxthead 和 rv32imafc的区别是什么？发现生成elf文件不同
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


text:
Material icons not displaying in IE11

In Firefox and chrome it is working perfectly but in IE icons are not displayed properly.

perfect

license: mit

license_source: bigquery


text:
Jeep Uconnect Portal

Hello, would it be possible to add a Jeep version? It uses same Uconnect stuff just via the uconnect Jeep portal.
Would be great if i can modify the code to login to the jeep portal :-)
With kind Regads
Michael

Need credentials for add this
contact me in the iobroker forum https://forum.iobroker.net/user/tombox

I add blindly the jeep support in the github version but not tested with a vehicle

@TA2k Just to tell you that it works: I own 2 Jepp (Compass PHEV 2021 and Renegade PHEV 2022) and both of them fully work in iobroker. So I think, you could close this issue.


text:
Fafa

fafa é pica

tmj


text:
Add documentation for the vision and progress of the library

What is the end state of the library?
What we aim to support, what do we exclude support for?
How is the library intended to be used?

Thanks @decentralgabe for adding this in.
I can tell you for me this is personally pretty important. l help put together the documentation, but bluntly I am trying to understand how much I should bank on the SSI-SDK to leverage for my project vs. what I need to be building myself. Understanding the vision of this project is imperative to making this happen.

This seems to start getting more and more important as time goes on. @decentralgabe what do you think is best way to move this ticket forward? I can maybe submit a draft PR and we can work off of it?

Hi @andorsk happy to get a draft PR. I plan on taking it after my presentation exchange PR.

Fixed in #173

authors: andorsk decentralgabe


text:
进展总览

大家认领组件的话，可以在本 issue 评论

后续我会在这个 issue 里持续更新 Mobile React 的工作安排和进展

[ ] 视觉问题修复
[ ] API 实现

Avatar 我来处理

我认领Message、Loading、Dialog

认领 tag

[Collapse] 展示demo间距不对

认领 Grid, Cell

[ ] #183
[ ] #184
[ ] #177
[ ] #178

认领 PullDownRefresh、BackTop

认领 Button

[ ]  [Button] 间距不对 #183

认领tabs #99

认领Search

认领picker

Alpha 版本已于 6.30 发布，完结

authors: LeeJim Perisiguiendo Winfans ZWkang laishiwen wwlh200 yilaierwang z2516305651

repo: TDesignOteam/tdesign-mobile-react


text:
profiler handlers added

This enables profiler that can be used for inspecting bottlenecks in the application.
It can be disabled via configuration and it shouldn't be used in production.
Here are the commands that can be used to view different profiles:
go tool pprof http://localhost:8024/debug/pprof/profile?seconds=30
go tool pprof http://localhost:8024/debug/pprof/heap
go tool pprof http://localhost:8024/debug/pprof/block
wget http://localhost:8024/debug/pprof/trace?seconds=5
go tool pprof http://localhost:8024/debug/pprof/mutex
Overview:
http://localhost:8024/debug/pprof/
@tiero @altafan please review.

Solve conflicts @sekulicd

authors: sekulicd tiero

repo: TDex-network/tdex-daemon


text:
Disc Count is not resetting, When a new game is started

Please reset the disc Count back to 2 for both black and white. When 'R' is pressed.
Like in the below attached image. White won a game.

When the new game is started (by pressing 'R'). Then the disc Count instead of being reset to 2 for both; remains the same as the end of last game. As you can see in the image below.

Thanks for reporting the issue, fixed it in the last commit


text:
RuntimeError: CUDA error: unknown error

多轮对话后提示这个错误

查看是否超出显存

没有超出显存

请给出更详细的信息和配置环境，按照issue模板提出issue，我们方便处理问题，该问题先关闭

authors: tjgaozw zRzRzRzRzRzRzR


text:
static pages

[x]  List of pages
[ ] Can the client edit them?
[x] Do they need updating?
[ ] Write instructions for editing
[ ] Share a list of pages with client

List of Pages:
cosite.ipynb → new intro text "co-site glossar"
index.qmd → new text "über dieses projekt"
imprint.qmd → add info about publisher TIB
contributers.qmd → sort authors alphabetically, add headings "Autor:innen" & "Lektorat"

index.qmd has a bit of latex, cosite001.ipynb has a lot of code, maybe those should be updated by us.
the other files are markdown with nothing to break.

We can add https://github.com/TIBHannover/co-site-glossar/blob/main/README.md too

There seems to be no way to give partial editing access to a repo (ie only to single files). So either all files are editable or none

authors: calnfynn mrchristian

repo: TIBHannover/semantic-glossar


text:
Is DoRA necessary during training?

I noticed that DoRA is being used in the training code. Is it necessary? If we switch to LoRA, how significant would the impact on the results be?
https://github.com/TIGER-AI-Lab/VLM2Vec/blob/1ecb8612415e1ce7498e34e3077dc7c2874f2bab/src/model.py#L94C17-L94C31

Thank you for your reply!


text:
Username Checker Error

This error is always occur when using the username checker
full log in the attach
error-log.txt

I will check it. If it is a bug we will fix it.

will check it out , I was busy on some works
On Fri, Oct 16, 2020, 08:34 Kiran Babu Muddam notifications@github.com
wrote:

I will check it. If it is a bug we will fix it.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/TIGMINT/TIGMINT/issues/13#issuecomment-709702709, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQCZGB7FYTXUARSMZAQ6LF3SK6Z4NANCNFSM4SSAM5WA
.

http://localhost:3000/username/result

@shanow7  Fixed it,  pull the latest version and try again.

repo: TIGMINT/TIGMINT


text:
contact

do you have an e-mail address & Discord for communication?

You can leave it here or in morgenleipzig@protonmail.com

authors: TPCTPCTPC heysurfer

repo: TPCTPCTPC/Adblock-gist


text:
🛑 Another Uptime monitoring is down

In ab7d5eb, Another Uptime monitoring ($UPTIME) was down:

HTTP code: 502
Response time: 514 ms

Resolved: Another Uptime monitoring is back up in 3b3dc52 after 1 hour, 21 minutes.

repo: TTRCharlie/Charlie-Cloud-Sites-Uptime


text:
upload the mlora server dependency

I add the python-multipart dependency that the server need

@yezhengmao1

repo: TUDB-Labs/mLoRA


text:
.#33 - Support for multiple HITs and using global_unique_id in their …

…definition

Fixed a bug indexing the nodes assigned to a given HIT in the admin panel
Hiding the Graph for CONFLAB, which is distracting
Fixed a bug which was preventing the creation of multiple HITs, as there was a constraint that per row of the HIT the project_id + project_name had to be unique, which did not make sense.
Now dynamically associating ids to hits in the same way it is done for journeys, through a counter in dev mode and through a secret in deployment

The requested modification was added with 4300103 . Please approve if it's now ok with you.

repo: TUDelft-SPC-Lab/covfee


text:
Update deps

@TabDigital/ping-api updated all dependencies
(detective@4 uses acorn instead of esprima so needed some tweaks to the error reporting)

looks good :+1:

authors: nguyenchr rprieto

repo: TabDigital/require-lint


text:
cafe24 prq.co.kr 개발시작

자꾸만 다운 된다.
12-10
12-14
12-17
벌써 3번째 다운 네트워크 드라이버 교체하고 추이를 지켜 보기로 했다.
어떤일이 있을지 두고 보기로 했다.

지금 현재 까지 큰 문제가 없는 것으로 보인다.
crontab -e
로 현재 모니터 할 수 있도록 로그 발생 중

time setting
14 3 * * * /usr/bin/rdate -s time.bora.net; /sbin/hwclock --systohc
disk backup
0 5 * * * /root/backup/rsync_backup.sh
check system
*/5 * * * * /root/monitor/checkSystemAll.sh > /dev/null 2>&1
*/5 * * * * /root/monitor/apache.py > /var/log/_apache.log 2>&1
*/5 * * * * /root/monitor/disk.py > /var/log/_disk.log 2>&1
*/5 * * * * /root/monitor/mysql.py > /var/log/_mysql.log 2>&1
*/5 * * * * /root/monitor/network.py > /var/log/_network.log 2>&1
*/5 * * * * /root/monitor/uptime.py > /var/log/_uptime.log 2>&1
*/5 * * * * /root/monitor/systeminfo.py > /var/log/_uptime.log 2>&1
*/5 * * * * /root/monitor/checkSystem2.sh swap xml > /var/log/_checkSystem2.log 2>&1
*/5 * * * * /root/monitor/checkSystem2.sh io xml > /var/log/_checkSystem2.log 2>&1
*/5 * * * * /root/monitor/checkSystem2.sh count xml > /var/log/_checkSystem2.log 2>&1
*/5 * * * * /root/monitor/checkSystem2.sh resource xml > /var/log/_checkSystem2.log 2>&1
*/5 * * * * /root/monitor/checkSystem2.sh memory xml > /var/log/_checkSystem2.log 2>&1
*/5 * * * * /root/monitor/checkSystem2.sh etc xml > /var/log/_checkSystem2.log 2>&1

repo: Taebu/prq


text:
[未收錄登載] 泡芙Creampuff Ch. ArkV CN

未收錄 Vtuber 資料

名稱：泡芙
出道日期：
首次直播/影片連結：
YouTube 頻道連結：https://www.youtube.com/channel/UCoNnfgjIlRuOHDnhObJffVQ
Twitch 頻道連結：
團體：
國家：MY

Vtuber 目前活動狀態

[X] 最近一個月內有直播或是影片(YouTube Shorts 不算)

Confirmed added at 8ebc87422406738affc8389eca0a22257f5e9893 .


text:
Fetch ignition config from S3

Fixes https://takescoop.atlassian.net/browse/SEC-8
Instead of passing ignition config (which contains secrets) into EC2 instances via userdata (which is available within every k8s pod via EC2 metadata endpoint), we now pass in a ignition config as userdata which will download the actual ignition config from S3.

@bendrucker Any idea on how to test this? I can hook the commit in kubernetes repo and apply in playground. But I'd like to know whether there's a better way.

@bendrucker I managed to successfully run terraform plan on the existing playground cluster, which means that all syntax issues have been fixed. Will create a new cluster for deeper testing tomorrow.

We decide to postpone this task a sprint to focus on something else (e.g. SOC2). For my own record, testing to create a new cluster in playground failed
/app/environments/playground # terraform apply --target module.test-typhoon

......
Error: Error applying plan:

5 errors occurred:
	* module.test-typhoon.module.typhoon.module.workers.aws_iam_role_policy.worker_read_ignition_configs: 1 error occurred:
	* aws_iam_role_policy.worker_read_ignition_configs: Error putting IAM role policy read-ignition-configs: MalformedPolicyDocument: Resource test-typhoon-ignition-configs/worker.yaml must be in ARN format or "*".
	status code: 400, request id: eb9eed93-be6d-4cd5-a79f-011da3e17891

	* module.test-typhoon.module.peering_main.aws_route.accepter_to_requester[2]: 1 error occurred:
	* aws_route.accepter_to_requester.2: Error creating route: RouteAlreadyExists: The route identified by 10.10.16.0/20 already exists.
	status code: 400, request id: dd6d4c16-3106-4266-8c1c-30d62267fe53

	* module.test-typhoon.module.peering_main.aws_route.accepter_to_requester[1]: 1 error occurred:
	* aws_route.accepter_to_requester.1: Error creating route: RouteAlreadyExists: The route identified by 10.10.16.0/20 already exists.
	status code: 400, request id: e8dcaeb4-f84e-413d-9ff2-8d877c172e21

	* module.test-typhoon.module.typhoon.aws_autoscaling_group.bastion: 1 error occurred:
	* aws_autoscaling_group.bastion: "test-typhoon-bastion terraform-20200114173735200800000007": Waiting up to 10m0s: Need at least 1 healthy instances in ELB, have 0. Most recent activity: {
  ActivityId: "79e5be94-89fc-a741-5cff-b9f919513637",
  AutoScalingGroupName: "test-typhoon-bastion terraform-20200114173735200800000007",
  Cause: "At 2020-01-14T17:38:17Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.",
  Description: "Launching a new EC2 instance: i-0eeb4f77e048214dc",
  Details: "{\"Subnet ID\":\"subnet-080e0159b302a74d0\",\"Availability Zone\":\"us-west-2c\"}",
  EndTime: 2020-01-14 17:38:51 +0000 UTC,
  Progress: 100,
  StartTime: 2020-01-14 17:38:19.049 +0000 UTC,
  StatusCode: "Successful"
}

	* module.test-typhoon.module.peering_main.aws_route.accepter_to_requester[0]: 1 error occurred:
	* aws_route.accepter_to_requester.0: Error creating route: RouteAlreadyExists: The route identified by 10.10.16.0/20 already exists.
	status code: 400, request id: 90589754-58c2-4806-819a-998436a278bb

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Error: failed to retrieve lock info: unexpected end of JSON input

@bendrucker I successfully created a playground cluster, was able to connect via bastion and to list pods. We can sign this off and wait for the next cluster migration!

@beyondbill If you resolve the conflicts here, happy to try to get this released!

@bendrucker All conflicts resolved!

authors: bendrucker beyondbill

repo: TakeScoop/typhoon


text:
设置readTimeOut

你好， 请问一下怎样可以设置Builder 的readTimeOut？ 我只找到了connectTimeOut 和writeTimeOut

我在使用RxUploadWithBody的时候总是出现连接超时的错误，但是文件其实已经成功上传，是不是应该是readTimeOut的问题，默认是十秒

@fanghe 稍等帮查看下

谢谢

@fanghe 是这个问题 okhttp默认的值太短 ，不够读写文件，上传连接耗时和返回的解析数据的时间。

可以在novate实例化的时候设置么？我看到有connectTimeOut和writeTimeOut的

稍等 ！我开放一个接口  后续你更新一下

好的 谢谢！

@fanghe o了 。1.5.3.1版本，开放了readTimeOut novate默认值都是15秒

太感谢了！！

@fanghe 感谢建议 可能上传大文件时会出现你说的这种问题，建议根据Api自己的属性设置长一点

我全部设置成了5分钟，可是总是在20秒左右的时候出现连接超时，有点奇怪。小文件没问题，说明返回没问题，大文件超时。我在novate的build里断点看了一下，TimeOut是修改成功了的，就是总是20秒超时

@fanghe 稍等 我在验证下

好的，麻烦你了

@fanghe 1.5.3.2

好的我试试

好像还有点问题， 当unit不是秒的时候， readTimeout已经被换算成毫秒了
this.readTimeout = Utils.checkDuration("timeout", timeout, unit);
if (timeout != -1) {
okhttpBuilder.readTimeout(readTimeout, unit);
}
return this;

我可能没说清楚，就是timeout先被换算成毫秒，然后按给入的unit一起设置okhttpBuilder的readTimeOUt，好像不是很对。不过我的连接超时问题解决了 ： ）

@fanghe 确实有点 我掠掠

@fanghe 可以用最新的1.5.3.3

可以上传多张图片吗？用upload接口不行，返回连接超时，这是什么情况？

authors: Tamicer fanghe lianchengtong

repo: Tamicer/Novate


text:
The faucet isn't working

The faucet isn't working It hasn't sent out MATIC and always It also keeps saying Network Error.
Please help to fix this,
Thanks

This is not maintained anymore, sorry
I just unhosted the page

authors: TamtamHero alfatih-shell

repo: TamtamHero/polygon-faucet


text:
Update HydrationStreamProvider.tsx + Advanced SSR docs to fix unnecessary suspensions

This PR is based on my findings in #6116 and fixes two cases of unnecessary suspensions during streaming SSR, one on code and the other in the advanced SSR docs. See the full writeup in this comment, which should have all the info needed for reviewing this PR.

@juliusmarminge would you mind taking a look here? Also I think the comment in the issue is super interesting:

https://github.com/TanStack/query/issues/6116#issuecomment-1904051005

authors: TkDodo mgreenw

repo: TanStack/query


text:
Change batch timeouts to be both configurable and based on the time oldest message

This makes two changes:

The batch timeouts are now configurable instead of being hard-coded to 20s
We now run execute when the oldest message in the batcher has exceeded the timeout.

To provide a little context, the current behavior of the timeout is that it is based on the newest message in the batcher.  Consider the scenario where batch size = 10 and timeout = 1m.  If a message came in every 30s, then the batch wouldn't be processed until 5m has passed (because the batch size will then be 10).
I will also be looking for feedback / guidance on whether this should be a minor or major rev change.
/to @gregorysabatino @theo-lanman @StabbyCutyou

Awesome! This looks like the right set of changes here.
My personal thought is that it should be a minor revision. Since batch timeout was not configurable before, but fixed at 20 seconds, at most this will cause systems which process batches less often than every 20 seconds to process batches every 20 seconds.

Awesome! This looks like the right set of changes here.
My personal thought is that it should be a minor revision. Since batch timeout was not configurable before, but fixed at 20 seconds, at most this will cause systems which process batches less often than every 20 seconds to process batches every 20 seconds.

Only other comment is, should we be using Time.zone.now?
Otherwise, seems fine, non blocking nits aside.

We shouldn't use Time.zone.now because that's an active_support thing.  Timezones are typically only interesting when you care about it from a visual perspective or where the underlying system has some dependency on either expecting or ignoring timezones.  In our case, we don't fall under any of those scenario.

Gotcha - I was thinking from the perspective of apps using chore, they'd have zone, but you're right - we lack it in chore itself. So, ignore that one.

Specs have been added and this has been validated locally.  See below:
Before:
[2016-03-23 15:32:06 -0400 (11465)] DEBUG : Found a new job development_report_metrics--20160323-193203-962908.0.job
[2016-03-23 15:32:06 -0400 (11465)] DEBUG : Got message: development_report_metrics--20160323-193203-962908.0.job
[2016-03-23 15:32:06 -0400 (11465)] DEBUG : Last message added to batch: 2016-03-23 15:32:06 -0400: 1
...
[2016-03-23 15:32:11 -0400 (11465)] DEBUG : Found a new job development_report_metrics--20160323-193210-787567.0.job
[2016-03-23 15:32:11 -0400 (11465)] DEBUG : Got message: development_report_metrics--20160323-193210-787567.0.job
[2016-03-23 15:32:11 -0400 (11465)] DEBUG : Last message added to batch: 2016-03-23 15:32:11 -0400: 2
...
[2016-03-23 15:32:16 -0400 (11465)] DEBUG : Found a new job development_report_metrics--20160323-193213-407804.0.job
[2016-03-23 15:32:16 -0400 (11465)] DEBUG : Got message: development_report_metrics--20160323-193213-407804.0.job
[2016-03-23 15:32:16 -0400 (11465)] DEBUG : Last message added to batch: 2016-03-23 15:32:16 -0400: 3
...
[2016-03-23 15:32:26 -0400 (11465)] DEBUG : Found a new job development_report_metrics--20160323-193223-412877.0.job
[2016-03-23 15:32:26 -0400 (11465)] DEBUG : Got message: development_report_metrics--20160323-193223-412877.0.job
[2016-03-23 15:32:26 -0400 (11465)] DEBUG : Last message added to batch: 2016-03-23 15:32:26 -0400: 4
...
[2016-03-23 15:32:31 -0400 (11465)] DEBUG : Found a new job development_report_metrics--20160323-193231-239298.0.job
[2016-03-23 15:32:31 -0400 (11465)] DEBUG : Got message: development_report_metrics--20160323-193231-239298.0.job
[2016-03-23 15:32:31 -0400 (11465)] DEBUG : Last message added to batch: 2016-03-23 15:32:31 -0400: 5
...
[2016-03-23 15:32:41 -0400 (11465)] DEBUG : Found a new job development_report_metrics--20160323-193238-869654.0.job
[2016-03-23 15:32:41 -0400 (11465)] DEBUG : Got message: development_report_metrics--20160323-193238-869654.0.job
[2016-03-23 15:32:41 -0400 (11465)] DEBUG : Last message added to batch: 2016-03-23 15:32:41 -0400: 6
...
[2016-03-23 15:32:51 -0400 (11465)] DEBUG : Found a new job development_report_metrics--20160323-193247-275925.0.job
[2016-03-23 15:32:51 -0400 (11465)] DEBUG : Got message: development_report_metrics--20160323-193247-275925.0.job
[2016-03-23 15:32:51 -0400 (11465)] DEBUG : Last message added to batch: 2016-03-23 15:32:51 -0400: 7
...
[2016-03-23 15:32:59 -0400 (11465)] INFO : Manager shutting down

After:
[2016-03-23 15:37:39 -0400 (17130)] DEBUG : Found a new job development_report_metrics--20160323-193737-432563.0.job
[2016-03-23 15:37:39 -0400 (17130)] DEBUG : Got message: development_report_metrics--20160323-193737-432563.0.job
[2016-03-23 15:37:40 -0400 (17130)] DEBUG : Oldest message in batch: 2016-03-23 15:37:39 -0400, size: 1
...
[2016-03-23 15:37:44 -0400 (17130)] DEBUG : Found a new job development_report_metrics--20160323-193742-258437.0.job
[2016-03-23 15:37:44 -0400 (17130)] DEBUG : Got message: development_report_metrics--20160323-193742-258437.0.job
[2016-03-23 15:37:45 -0400 (17130)] DEBUG : Oldest message in batch: 2016-03-23 15:37:39 -0400, size: 2
...
[2016-03-23 15:37:49 -0400 (17130)] DEBUG : Found a new job development_report_metrics--20160323-193749-280834.0.job
[2016-03-23 15:37:49 -0400 (17130)] DEBUG : Got message: development_report_metrics--20160323-193749-280834.0.job
[2016-03-23 15:37:50 -0400 (17130)] DEBUG : Oldest message in batch: 2016-03-23 15:37:39 -0400, size: 3
...
[2016-03-23 15:37:59 -0400 (17130)] DEBUG : Found a new job development_report_metrics--20160323-193755-007838.0.job
[2016-03-23 15:37:59 -0400 (17130)] DEBUG : Got message: development_report_metrics--20160323-193755-007838.0.job
[2016-03-23 15:38:00 -0400 (17130)] DEBUG : Oldest message in batch: 2016-03-23 15:37:39 -0400, size: 4
[2016-03-23 15:38:00 -0400 (17130)] DEBUG : Batching timeout reached (2016-03-23 15:37:59 -0400), current size: 4
[2016-03-23 15:38:00 -0400 (17130)] DEBUG : Manager#assign: No. of UnitsOfWork: 4)

@StabbyCutyou Any thoughts on this being a minor rev bump instead of a major rev bump?

Mr Lanmans line of thinking is inline with my own - we made a fixed value configurable, and defaulted to the old fixed value.
Seems like a minor bump to me.

@theo-lanman / @StabbyCutyou looking for a final review here

LGTM

This looks good to me. Yay specs!

authors: StabbyCutyou obrie theo-lanman

repo: Tapjoy/chore


text:
🛑 Primal Bushcraft is down

In 902a1a7, Primal Bushcraft (https://www.primalbushcraftsurvival.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Primal Bushcraft is back up in 7a106bd after 10 minutes.

repo: Tartan-Web-Design/monitoring


text:
デザインパターンの輪読資料について記事を書きたい

9章は昨日書いたので、それ以外。

書き終えたのでクローズ


text:
Bug: Titanium can be mined with wood

I dont know if thats an issue but it seems wrong to mine Titanium with wood, just close it if its intended
Thx for your work

i assume the mineable indicator in jade and the recipes of the blocks showable in JEI is not your problem right?

Fixed in dev

authors: FuchsTairn MineDragonCZ


text:
Fails to load on 2.0.205.52

=== Clever Girl [fork] 1.0.5 Errors ===
<...>\steamapps\workshop\content\333640\2921686606\InterfaceCompanions.cs(24,49): error CS1739: The best overload for 'ShowOptionList' does not have a parameter named 'defaultSelected'
<...>\steamapps\workshop\content\333640\2921686606\Feed.cs(90,49): error CS1739: The best overload for 'ShowOptionList' does not have a parameter named 'defaultSelected'
<...>\steamapps\workshop\content\333640\2921686606\ManageGear.cs(229,74): error CS1061: 'BodyPart' does not contain a definition for 'PreferedPrimary' and no accessible extension method 'PreferedPrimary' accepting a first argument of type 'BodyPart' could be found (are you missing a using directive or an assembly reference?)
<...>\steamapps\workshop\content\333640\2921686606\Feed.cs(375,50): error CS1739: The best overload for 'ShowOptionList' does not have a parameter named 'defaultSelected'
<...>\steamapps\workshop\content\333640\2921686606\Feed.cs(620,46): error CS1739: The best overload for 'ShowOptionList' does not have a parameter named 'defaultSelected'
== Warnings ==
<...>\steamapps\workshop\content\333640\2921686606\Feed.cs(416,80): warning CS0618: 'GameObjectBlueprint.GetPartParameter(string, string, string)' is obsolete: 'Use GetPartParameter instead - will remove Q2 2023'

Version 2.0.205.60 currently throws the same errors.

Apologies, I have been engaged in other games, haven't looked at Qud in a while. First Github issue -- Exciting! (I really mean that). I (hopefully correctly) setup email notifications on Github so I should get notified for issues like this. I fixed this on the main branch a while ago, never got around to updating the beta branch. I'll see if i can get that updated now

There appears to be a version mismatch here somehow, at least given the error log being shown. Not sure exactly what's going on. The error log above shows version 1.0.5, which should be showing either 1.0.6_hotfix (main branch) or v1.0.7-beta4 (beta branch).
If you're cloning manually and using the beta branch, you might be using an older version? (should be https://github.com/TealTime/Clever-Girl/releases/tag/v1.0.7-beta4) Or if you're using the steam workshop version, maybe it's just not syncing correctly? I speculate that an unsubscribe/subscribe to the steam workshop might fix that if that is the case. I know there's been issues with updates propagating correctly in the past, which I admittedly need to investigate further.
FWIW, I'm loading the mod without errors on both the current Clever-Girl [fork] branches (main/beta) with the beta version of Caves of Qud right now, unless something in my setup is wrong (which is a definite possibility).

Also if I don't reply to one of your followup messages in the near future, please ping me on the steam workshop. I'm still not confident that I've got these Github email notification settings correct

There appears to be a version mismatch here somehow, at least given the error log being shown. Not sure exactly what's going on. The error log above shows version 1.0.5, which should be showing either 1.0.6_hotfix (main branch) or v1.0.7-beta4 (beta branch).
If you're git-cloning manually and using the beta branch, you might be using an older version? (should be https://github.com/TealTime/Clever-Girl/releases/tag/v1.0.7-beta4) Or if you're using the steam workshop version, maybe it's just not syncing correctly? I speculate that an unsubscribe/subscribe to the steam workshop might fix that if that is the case. I know there's been issues with updates propagating correctly in the past, which I admittedly need to investigate further.
FWIW, I'm loading the mod without errors on both the current Clever-Girl [fork] branches (main/beta) with the beta version of Caves of Qud right now, unless something in my setup is wrong (which is a definite possibility).

Ahhh this was the issue apparently! It would be nice if Steam Workshop was actually capable of keeping things up to date! It loads fine once unsubbing/resubbing to force Steam to download the correct version. (Though even that's marked as v1.0.6_hotfix, but at least it loads and doesn't throw errors.)

authors: LiefAmai TealTime

repo: TealTime/Clever-Girl


text:
Inserting a bearing offers more than just the bearing because the DO NOT USE PARTS is named 'PARTS DO NOT USE'

(This should be a 1 line fix...)
If you attempt to insert the vgroove bearings from goBILDA > MOTION > Bearings > Specialty Bearings > V-Groove Ball Bearings

It should just insert the bearing, but clicking on the first one https://cad.onshape.com/documents/9376d78e0e5488ef406ae789/w/93c5127fe5c4d6048341d3b4/e/4a4b8805aa32b34621b57335 gives you:

Clicking on the second one gives you
https://cad.onshape.com/documents/4f38146bc0abd0dbffa37cef/w/fa9064dc1dd6b37fbdfd1da8/e/5a7bddf1681952a8266aede6

Looking at both models, they seem to follow the standard of having the parts with a "Do not use these parts" and the tab and the information for it appears to be correct.

getInsertChoices should filter them out, but the check on line 1838 Looks for the string 'DO NOT USE THESE PARTS' but the string in the model is 'PARTS DO NOT USE' so we should update the app to look for that string too.

This should be resolved now, @toebes you can make sure.

authors: WilliamBagel toebes


text:
🛑 hostux.net is down

In b31c47d, hostux.net (https://piped-api.hostux.net/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hostux.net is back up in f4e566d after 1 hour, 7 minutes.

repo: TeamPiped/piped-uptime


text:
🛑 projectsegfau.lt us is down

In fc33667, projectsegfau.lt us (https://pipedapi.us.projectsegfau.lt/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: projectsegfau.lt us is back up in 1e040f4 after 59 minutes.


text:
🛑 privacydev.net is down

In d84e49a, privacydev.net (https://api.piped.privacydev.net/healthcheck) was down:

HTTP code: 502
Response time: 732 ms

Resolved: privacydev.net is back up in 43d55f3 after 22 minutes.


text:
🛑 vyper.me is down

In 275b5e6, vyper.me (https://yapi.vyper.me/healthcheck) was down:

HTTP code: 404
Response time: 324 ms

Resolved: vyper.me is back up in 09344c2 after 16 minutes.


text:
🛑 kavin.rocks (Official) is down

In 5b99451, kavin.rocks (Official) (https://pipedapi.kavin.rocks/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kavin.rocks (Official) is back up in 37a2db0 after 8 minutes.


text:
🛑 il.ax is down

In 0517642, il.ax (https://pa.il.ax/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: il.ax is back up in 149c4c8 after 8 minutes.


text:
🛑 esmailelbob.xyz is down

In 1d1a1af, esmailelbob.xyz (https://pipedapi.esmailelbob.xyz/healthcheck) was down:

HTTP code: 503
Response time: 741 ms

Resolved: esmailelbob.xyz is back up in 4fc4d49.


text:
🛑 il.ax is down

In 9a47990, il.ax (https://pa.il.ax/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: il.ax is back up in e40f8e4 after 18 minutes.


text:
🛑 kavin.rocks (Official) is down

In f66a9ac, kavin.rocks (Official) (https://pipedapi.kavin.rocks/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kavin.rocks (Official) is back up in 180580e after 1 hour, 38 minutes.


text:
🛑 privacydev.net is down

In 975a24b, privacydev.net (https://api.piped.privacydev.net/healthcheck) was down:

HTTP code: 502
Response time: 663 ms

Resolved: privacydev.net is back up in f60ce07 after 9 minutes.


text:
🛑 projectsegfau.lt in is down

In 30bfde9, projectsegfau.lt in (https://pipedapi.in.projectsegfau.lt/healthcheck) was down:

HTTP code: 502
Response time: 5185 ms

Resolved: projectsegfau.lt in is back up in 064ca71 after 6 hours, 44 minutes.


text:
🛑 privacydev.net is down

In d439232, privacydev.net (https://api.piped.privacydev.net/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: privacydev.net is back up in e9fd432.


text:
🛑 rivo.lol is down

In ca151a9, rivo.lol (https://pipedapi.rivo.lol/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: rivo.lol is back up in b621b6a after 280 days, 7 hours, 25 minutes.


text:
🛑 privacydev.net is down

In b9abdb7, privacydev.net (https://api.piped.privacydev.net/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: privacydev.net is back up in 819a3e2 after 288 days, 17 hours, 47 minutes.


text:
Close reasons

Add support for differentiating between different types of WebSocket closures by passing code and reason values to ws.close(). This is helpful, because a client may wish to perform different reconnection logic depending on the reason for disconnection.
In particular, it is useful to be able to differentiate intentional disconnections where the server wishes to indicate to the client that it should not reconnect at all or the client should delay for a more extended time before it reconnects. If, for example, a client's application version is no longer supported, the server may wish to disconnect with a reason that indicates the client should not attempt reconnection and it should refresh or update its code first.
In addition, this PR includes a full shim of Node's stream.destroy(), borrowed from current master of Node. The minimal shim was not consistent with the current implementation of stream.destroy() in Node 8+, particularly because it didn't emit passed in errors as an 'error' event. If we're shimming this, I believe we should use the full implementation from current Node for more consistency in API.
Including a shim of stream.destroy() is a key part of this PR, since it now produces a different close code than stream.end()

Coverage decreased (-26.0%) to 72.222% when pulling a6d662ac2a6f9fe0db320c1b8220edee80b3f3d3 on nateps:close-reasons into 95638d8201a1fd0cd72ea0efaf11bec0d6280885 on Teamwork:master.

Regarding coverage testing, Coveralls is not reporting the same output as Istanbul anymore. They made some changes in Coveralls 3.0, and branch coverage is computed within ignored statements.
See output from Travis build showing coverage (with ignores) is 100%: https://travis-ci.org/Teamwork/websocket-json-stream/jobs/408183093
Apparently this can be worked around by downgrading the version of coveralls or by turning off the branch coverage setting for the repo:
https://github.com/lemurheavy/coveralls-public/issues/939
https://github.com/nickmerwin/node-coveralls/issues/158#issuecomment-286318287

Awesome. Thanks for the review!
On Thu, Jul 26, 2018 at 4:59 AM, Greg Kubisa notifications@github.com
wrote:

Merged #1 https://github.com/Teamwork/websocket-json-stream/pull/1.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Teamwork/websocket-json-stream/pull/1#event-1754835341,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOLNCPhXMTob7cxyfHMjr1DCOBKIq5nks5uKa8pgaJpZM4VfcrQ
.

authors: coveralls nateps

repo: Teamwork/websocket-json-stream


text:
Please invite me to the GitHub Community Organization

Name
Shreyas B S
Discord Username (if applicable)
No response
Additional Context
i'm in the journey of exploring more in wed developement, love to contribute to open source

repo: Tech-Phantoms/community


text:
:tada: create about us page :boom:

This task has been assigned to Emmanuel Serem.
Tasks ;
Create an about us page as per screenshot below.
Select and edit suitable images or graphics that visually enhance the page and align with our brand identity.
Center the title about us.
Screenshot.

Steps;
Create a fork .
Clone the repo to your machine.
npm install
npm run dev to start the server
git branch about-page to create your own branch
git switch about-page
commit your changes and push to your github account
Lastly make a PR of your branch in your own Github account to the main branch of indices-trade-lab  repo in TechInnovatorsHub .

I have started working on this

authors: Serem-manu TechInnovatorsHub

repo: TechInnovatorsHub/indices-trade-lab


text:
🛑 J.Leigh Photography is down

In f173c8b, J.Leigh Photography (https://jleighphotography.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: J.Leigh Photography is back up in 47c6ada.

repo: TechSavagery/uptime-monitoring


text:
Mods Downloading, but not all installing

I have gotten my Solder server up fine and I added all my mods to it.   I then linked it to Technic and my modpack on there.  It downloads all the zip files as intended to the cache folder then when it goes to install them it stops about 12 mods in and stops installing.
Any reason this would happen?

This would appear to be a launcher issue. Not Solder.

repo: TechnicPack/TechnicSolder


text:
Decide on frontend framework to use

I haven't made a website in a while.
This entire site will be purely static, so hosting is pretty simple; I'll probably use GitHub Pages on my robotic team's account.
I've been looking at Astro since it seems to excel with static sites.
The vision for Cookbook is to have a robustly searchable "hand book" of common problems easily available and reference-able.
For fast searching, PageFind looks like a great option, which seems to work with a lot of libraries.
My initial thought was to just use SvelteKit since I'm most familiar with that, but I do not think that it's the best option for something like this.
Any external ideas are very welcome, and if you would like to contribute, hit me up at hextanium on Discord.
This is mostly for my own reference though.

mdbook
I loved using md book while learning rust!. The whole thing is super clean and easy to follow and use.

Decided on mdbook as per suggestion. Initial revision released.

authors: Froze-N-Milk TechnoDrive schsdrobotics

repo: TechnoDrive/cookbook


text:
Tekken 8 Overlay not working

so my laptop is really potato and i decided to try using this tekken overlay for better fps. So My laptop specifications are Intel Core i7-1165G7, With 8gb of ram, with Nvidia GeForce MX-330 Graphic card. When i unzip my file and put it in the tekken 8 on steamapps in the overlay folder, when i run it as an administrator it says "Windows can't access the specified dvice, path, or file. You may not have the appropriate permissions to acccess the item".

This is more of a generic Windows problem. So search respectively:
https://www.minitool.com/backup-tips/windows-cannot-access-the-specified-device.html
https://www.google.com/search?q=Can't+run+exe+Windows+cannot+access+specified+path

authors: AndrewFXZ KulaGGin

repo: TekkenOverlay/TekkenOverlay


text:
Error building when using plugin

Hello,
I get an error when building with this plugin.
also mentioned in: https://github.com/katzer/cordova-plugin-badge/issues/70
Can you please update the Telerik Verified Plugin?
Or advise how to use the functionality provided by this plugin.
Greetings
Marcel
Error message:
Warning: Failed to install 'de.appplant.cordova.plugin.badge':CordovaError: Failed to fetch plugin de.appplant.cordova.common.registerusernotificationsettings via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Error: Registry returned 404 for GET on https://registry.npmjs.org/de.appplant.cordova.common.registerusernotificationsettings
at /Users/builder/BpcTooling/Cordova3/pm-5.0+/node_modules/cordova-lib/cordova-lib/src/plugman/fetch.js:170:33
at _rejected (/Users/builder/BpcTooling/Cordova3/pm-5.0+/node_modules/q/q.js:797:24)
at /Users/builder/BpcTooling/Cordova3/pm-5.0+/node_modules/q/q.js:823:30
at Promise.when (/Users/builder/BpcTooling/Cordova3/pm-5.0+/node_modules/q/q.js:1035:31)
at Promise.promise.promiseDispatch (/Users/builder/BpcTooling/Cordova3/pm-5.0+/node_modules/q/q.js:741:41)
at /Users/builder/BpcTooling/Cordova3/pm-5.0+/node_modules/q/q.js:557:44
at flush (/Users/builder/BpcTooling/Cordova3/pm-5.0+/node_modules/q/q.js:108:17)
at nextTickCallbackWith0Args (node.js:419:9)
at process._tickCallback (node.js:348:13)
Warning: Failed to fetch plugin de.appplant.cordova.common.registerusernotificationsettings via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Error: Registry returned 404 for GET on https://registry.npmjs.org/de.appplant.cordova.common.registerusernotificationsettings
Warning: /Users/builder/BpcTooling/Cordova3/node_modules/cordova-build-utils/bin/install-plugins-3.js:190
throw Error("exit code: " + code);
^
Error: exit code: 1
at Error (native)
at ChildProcess. (/Users/builder/BpcTooling/Cordova3/node_modules/cordova-build-utils/bin/install-plugins-3.js:190:14)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

Hi @Lecramed do you still need assistance or did the comment in the upstream repo fix it?

version 0.72 fixed the issue
Thanks

authors: EddyVerbruggen Lecramed

repo: Telerik-Verified-Plugins/Badge


text:
Fix incorrect path

Line 4:
This provider exposes two resources: [proxmox_vm_qemu](docs/resources/vm_qemu.md) and [proxmox_lxc](docs/resources/lxc.md).

This path relative. Using docs/resources will lead to an absolute path like /docs/docs/resources, leading to a 404 error.
I removed the unnecessary docs/ from this line.

Sorry this has the same problem as this PR #260

authors: ggongaware jess-sys

repo: Telmate/terraform-provider-proxmox


text:
support for one hot plugin with dynamic axis other than batch_size dim

I read the code of one hot plugin generation. It seems that it only support dynamic axis of batch size dimension. Can tpat support one hot plugin generation with dynamic axises other than batch_size dimension?

@wenqf11  Hi, why adding Transpose before and after one_hot node can avoid issues of dynamic dims? I suppose the transpose node cannot infer the exact tensort shape runtime.

@frankxyy If you have more than one dynamic dimensions, we cannot support currently. If your ONNX model has only one dynamic diemnsion, you can Transoise it  to the first dimension. It may cost more time to run it with Transpose.

@wenqf11 Thank you. Got it.

repo: Tencent/TPAT


text:
[t-input] ios实机不显示光标

tdesign-miniprogram 版本
1.8.2
重现链接
No response
重现步骤
在 iPhone 15  / ios 18.2 实机中,点击input弹出键盘但是光标不显示
我尝试其它几个型号的 iPhone 实机也不显示光标
我尝试删除以下几个方法，然后光标就能显示了
miniprogram_npm > tdesign-miniprogram > input > input.wxml
<input focus="{{focus}}"
 cursor="{{cursor}}"
 auto-focus="{{autoFocus}}"
 cursor-color="{{cursorColor}}"
 cursor-spacing="{{cursorSpacing}}"
/>

期望结果
No response
实际结果
No response
基础库版本
3.6.4
补充说明
No response

@Monecone hello， 该问题应该在 1.8.0 版本中做了修复，理论上版本号大于等于 1.8.0 光标都会正确显示，辛苦确认一下组件库版本号。
另外，从你贴的部分代码来看和现在的 1.8.2 版本内容不一致。1.8.2版本，t-input 部分源码如下：
https://github.com/Tencent/tdesign-miniprogram/blob/d4b04ba8b4731f408fd07ee5fd70df11f62c5c0a/src/input/input.wxml#L42

authors: Monecone anlyyao

repo: Tencent/tdesign-miniprogram


text:
[DatePicker] 周选择组件在微信浏览器上的显示问题

tdesign 版本
0.40.5
重现链接
https://tdesign.woa.com/react/components/date-picker
重现步骤

微信浏览器对于 table-row 类型的盒子表现有点怪异，子元素上下定位全部失效，宽高也无视 padding 计算，有点难搞

authors: HQ-Lin notFoundTheGuy

repo: Tencent/tdesign-react


text:
[select] minCollapsedNum可配置响应式折叠，当宽度不够时才折叠

这个功能解决了什么问题
多选下通过响应式布局让选项自动收缩，让选择框更灵活的显示多个tag
你建议的方案是什么
实现antd效果：
https://ant.design/components/select-cn/#components-select-demo-responsive

这个功能一直有的https://tdesign.tencent.com/react/components/select#%E8%87%AA%E5%AE%9A%E4%B9%89%E6%8A%98%E5%8F%A0%E9%80%89%E4%B8%AD%E9%A1%B9%E9%80%89%E6%8B%A9%E5%99%A8

这位同学的意思，应该是指固定宽度的场景下，标签超出后自动计算折叠的标签数量，而非父组件指定折叠数量。
见过一些实现这个功能的组件库，总能发现一些奇奇怪怪的 BUG，比如默认位置不正常啊，一次选择过多啊。

authors: chaishi hkaikai uyarn


text:
[Form] 关于 getFieldsValue 的 typescript 的写法优化

这个功能解决了什么问题
useRef 如果指定了数据类型，getFieldsValue 返回的类型回出现问题
你建议的方案是什么
///  srcform/type.ts

// 旧
getFieldsValue?: (nameList: string[] | boolean) => Record<keyof FormData, unknown>;

// 新
interface getFieldsValue<T> {
    (nameList: true): T;
    (nameList: string[]): Record<keyof T, unknown>
}
getFieldsValue?: getFieldsValue<FormData>

0.36.0 fixed


text:
Improve texture quality

Hello, is there any way to improve the texture quality of the generated model? Such as adjusting the config params?

Maybe you can try some post-processing methods like this.

@bluestyle97 Is there a way to eliminate the watermark/texture glitch without such post-processing methods? Example:

I also encountered this problem. Have you any ideas?

repo: TencentARC/InstantMesh


text:
feat(bkpaas_auth): support get tenant_id via bk_token verify

网关测试需要，还没实地验证，改动不多；
待验证

多租户环境，没有bk-esb，所以原先 地址将不可用
    BKAUTH_USER_COOKIE_VERIFY_URL = f"{BK_COMPONENT_API_INNER_URL}/api/c/compapi/v2/bk_login/is_login/"
    BKAUTH_TOKEN_USER_INFO_ENDPOINT = f"{BK_COMPONENT_API_INNER_URL}/api/c/compapi/v2/bk_login/get_user/"

需要换成 bklogin 网关 地址
    # https://bkapi.bk-tenant-dev.woa.com/api/bk-login
    BKAUTH_USER_COOKIE_VERIFY_URL = (
        BK_API_URL_TMPL.format(api_name="bk-login") + "/prod/login/api/v3/open/bk-tokens/verify/"
    )
    # FIXME: there got no endpoint for get user info in multi-tenant mode env
    BKAUTH_TOKEN_USER_INFO_ENDPOINT = f"{BK_COMPONENT_API_INNER_URL}/api/c/compapi/v2/bk_login/get_user/"

登录服务似乎只用到了 BKAUTH_USER_COOKIE_VERIFY_URL,
{
    "data": {
        "bk_username": "5461b239-5ef2-4c81-a682-5907dbd5f394",
        "tenant_id": "system"
    }
}

多租户已经没有 get_user这个接口了（这个在什么场景下会用到？ 拿bk_username获取用户信息，原先是bk-esb封装的）

duplicated with: https://github.com/TencentBlueKing/bkpaas-python-sdk/pull/205

repo: TencentBlueKing/bkpaas-python-sdk


text:
Unittest feature implementation

Description
This PR adds support for Unittest feature in dbt-teradata
Checklist

[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md with information about my change

Tests Result

Do we need to update anything in README?

Readme changes are not required @tallamohan

repo: Teradata/dbt-teradata


text:
Documentation in Chinese

Installation
Admin

Initial draft.
Jaguar 文档中文版.docx

Updater after first-round review.
Jaguar 文档中文版 v2.docx

Jaguar 文档中文版 v3.docx

Update a CLI typo
Jaguar.v3.docx

repo: TeraprocSoftware/jaguar


text:
Add a user defined 'tag' to the connection identifier.

As discussed in various meetings we should add a tag to the connection identifier to allow the user of the voltron api to 'tag' a voltron connection with a human-readable name.  This allows for easier parsing of the connection-ids anywhere that they are referenced, be that the server logs, the client logs, or various locations in the M&M stack where this information is used or extended.

CC @anthonydahanne @ankitamaurya :
Talked to @jd0-sag. He will bring up this feature to the server team. We need it for M&M Slice 2.
Basically, a client will be able to do something like this:
        Properties properties = new Properties();
        properties.setProperty("tag", "123@127.0.0.1:jetty:app:3");
// or
        properties.setProperty("tag", ClientIdentifier.create("jetty:app:3").toString());
        this.connection = connectionService.connect(uri, properties);

And the tag will be exposed into the voltron monitoring tree in the PlatformConnectedClient object.

@jd0-sag , @myronkscott @ramsai1729 : would it be possible to directly expose in PlatformConnectedClient  the whole Properties object used to create the connection ?
The objects could also be "extended" to contain connection.uri, which would be the String representation of the URI used to connect.
This way it would be possible for us, by recovering this properties object from the PlatformConnectedClient  class, to get:

connection.timeout : optional
connection.uri : always there // uri used to connect
connection.tag : string used to tag this connection
any other user-defined properties

What do you think about this ?
I see several benefits for this, including:

ability to show in TMC how the connections have been created
easier shield support / troubleshooting
easy to extend and provide some other user-defined properties for eventually other services or monitoring use cases

(CC @anthonydahanne)

I would generally want to avoid something so open-ended since these properties are really more about interacting with the underlying ConnectionService implementation in on-general "hint"-like ways and pushing any of that data through to the server is arguably the wrong approach.
For a defined key, it seemed like a clearer approach than adding to the API in ways which would otherwise seem somewhat redundant (next to Properties).  Even that is somewhat questionable, though.

OK!
So if we forget about any other user-defined properties, could be still have all the other 3 properties exposed ?

My thinking is either 1 (as it gives something we could generally output as a human-readable identifier, in many situations) or 0 (and connect this other arbitrary data/behavior through a different path).
You are able to associate the PlatformConnectedClient identifier with the other cases where you need to know this information, on your side, right?

Right, but I was just asking for connection-specific properties:

connection.timeout : optional
connection.uri : always there // uri used to connect
connection.tag

If we modify PlatformConnectedClient to expose the tag set by the user, I just say we could also expose the properties used to create the connection. Things that we do not have access locally from the management library and could be exposed by the platform as easily as the tag.

The problem is that this is producing more hidden API:  instead of being able to ask for specific data, we are looking up "magic keys" in a Properties object.  If we wanted specific pieces of data, we should just add them to PlatformConnectedClient, directly.
Even if we were to pass the entire map through (which may be something to consider, for general opaque monitoring, not decision-making - still wary of this, though) we would still need these pieces of data to be top-level (since "connection.uri" is a valid key in the map - which one do you see?).

Ok. So we know that PlatformConnectedClient will expose a sort of tag.
Now, here is my question.
How could we access, from the Tms Entity, the connection properties (_timeout_, _uri_)
that the client set when connecting to the server ? => to know HOW it connected.

Using some management module on client-side to do that is not a solution because not all client will have a management module and the management module is just about exposing the client-side objects. So it has nothing to do with the connection.

There isn't currently a way to do that since this is a new requirement.
What information do we currently want to expose to M&M regarding these client-side network layer options?  Do we actually want this "tag" capability or is this underlying map the data that M&M actually wanted?
If the answer is "both", then we can't use this map to implement the tag and we will have to change the API to make it a first-class piece of information.  Arguably, if the server-side wanted to know about this for decorating logs, etc, then it should be part of the API, directly, and not slid in through the properties which are really more about the implementation details of the ConnectionService, treated as opaque by the rest of the platform.

I'll ask some people to be sure.
Because what we are sure for now is that we need a way to pass a string (client identifier) when connecting.
What I am not sure yet is what we'll need to know about how the client connected. So let's answer that and then I'll come back to you :-)

FYI:

ClientIdentifier class is currently in terracotta-management: source | test

We need this class / representation for client tagging in M&M.
<PID>@<CLIENT-ADDRESS>:<CLIENT-APP-NAME>
CC @cljohnso

@cljohnso @jd0-sag @chrisdennis : about ClientIdentifier integration, here is a proposal:
When a cluster client will create a connection (connectionService.connect(uri, props)), he will need to pass a string tag representation of a ClientIdentifier. This class constructs a client identifier such as <PID>@<CLIENT-ADDRESS>:<CLIENT-APP-NAME> and has several constructors:

create() => create(generated-short-uuid)
create(app-name) => create(discovered-pid, discovered-lan-address, app-name)
create(pid, address, app-name)
valueOf(string)

The idea would be to allow users to put in the ehcache.xml file an optional attribute with their application name. If the attribute is there, then you can call ClientIdentifier.create(app-name) and if it is not there, ClientIdentifier.create(). The ClientIdentifier class discovers the PID and lan address.
Programmatically, here is how it could looks like:
    final CacheManagerBuilder<PersistentCacheManager> clusteredCacheManagerBuilder =
        CacheManagerBuilder.newCacheManagerBuilder()
            .with(ClusteringServiceConfigurationBuilder.cluster(URI.create("http://example.com:9540/my-cache-manager?auto-create"))
                .clientIdentifier("jetty/EhcachePounder")
                .defaultServerResource("primary-server-resource")
                .resourcePool("resource-pool-a", 128, MemoryUnit.GB)
                .resourcePool("resource-pool-b", 128, MemoryUnit.GB, "secondary-server-resource"))
            .withCache("clustered-cache", CacheConfigurationBuilder.newCacheConfigurationBuilder(Long.class, String.class,
                ResourcePoolsBuilder.newResourcePoolsBuilder()
                    .heap(10, EntryUnit.ENTRIES)
                    .with(ClusteredResourcePoolBuilder.fixed("resource-pool-a", 32, MemoryUnit.GB))));

Then the clientIdentifier() method will call ClientIdentifier.create(name). If clientIdentifier() is not called, then an identifier can be generated for this app with ClientIdentifier.create()
Note: I am wondering if we can re-use some part of the cluster URI to make the client identifier ? Do we have ONE server entity per client application, OR we can have 1 client web application that for exemple connects to several cluster URIs ? I guess so, so .clientIdentifier("jetty/EhcachePounder") would be the same for different cluster URI.
This proposal would also any user-made entities to use the ClientIdentifier. As long as a user uses the ClientIdentifier class to generate a unique tag that he can re-use across different connection creation.
I also propose we move this class at a common place to avoid duplication. It could be in terracotta-apis. Or copied in each project that needs it, but it's not really good I think... You might see it as a class that can be used client-side to help generating a logical cluster client  identifier, that should be in this format: <PID>@<CLIENT-ADDRESS>:<CLIENT-APP-NAME>.
Let me know what you think about! We can do a hangout to discuss it.

Meeting conclusion:
Ehcache:
.tag("jetty")
.tag("EhcachePounder")

Server exposes:
- clientAddress => already there
- pid => PlatformConnectedClient.pid

At connection time: "pre" connection step to publish client metadata (will be a new module in terracotta-management project)
root
  | --platform
         |-- connections
                |- <generated-voltron-conn-id> = PlatformConnectedClient (ip, port, PID)
                              |- metadata = ManagementMetadata (product name, tags)

From the metada-connection-entity
producer.addNode({platform, connections, <id>, metadata}, MetadataObject)

UPDATE
Goals:

M&M needs to be able to consolidate all the physical connection information exposed in Voltron tree to regroup connections based on connection uuids (to regroup cluster connections together == logical connection)
M&M also needs to create the client identifier from PID, client addr, connection UUID and regroup all the logical connections having the same tags / client identifier under the same Client object.
M&M needs to have a way to easily display a client (== client identifier) and filter them (== tags)
M&M needs to be able to identify a connected client to a cluster thanks to a client identifier, and then lookup the server entities this client is connected to.

Terminology:

Connection Uuid: string passed when creating a TC connection

Tags: set of strings passed when creating a TC connection

Physical connection == PlatformConnectedClient : client port, client addr, server port, server addr, connection uuid, tags, client PID

Logical connection = connection to a cluster : grouping of several physical connections having the same connection uuid (multi-stripe)

ClientIdentifier = @: : identifier that will be used in M&M to identify a client in the topology

Client: = ClientIdentifier + Tags + etc.. : client object representing a cluster client in M&M.Identified by a ClientIdentifier

Example:
user can open a connection to voltron with a uuid to identify the physical connection (?) and the tags {ehache, my-cache-manager-name}
Todo for server team:

Support a string for the name/uuid + a list of tags when creating a connection
Expose in PlatformConnectedClient the client PID, tags and name/uuid

@mathieucarbou would all this information (topology above) be published in the monitoring tree ?
On a user point of view (read tmc), I guess only the logical information makes sense to be published (but I understand there are other needs than just M&M here)

@anthonydahanne : the tms backend topology needs to have all this information, whether it is shown or not in the TMC.
Yes it needs to be in the monitoring tree.

@jd0-sag : issue automatically closed because of the commit message. You we re-open it, as you told me yesterday that the logical connection uid could be added there ?

This issue has been re-purposed too many times to encapsulate too many divergent ideas.  I have opened #72 to handle the specific details of logical connection name to keep the intent clear.
This means that the existing item describes the platform-intrinsic data while #72 will focus on the API-level, extrinsic, data we want to pass through from the client to monitoring.

authors: anthonydahanne chrisdennis jd0-sag mathieucarbou

repo: Terracotta-OSS/terracotta-apis


text:
[기능] 베이스라인 디자인 개선

Description

로고 사이즈 개선
폰트 NotoSans 변경
노드 디자인 개선
리소스 그룹 재배치
export, region UI 개선

이후 개선 필요

삭제 버튼 UI
노드 병합시 위치 튕김
노드 사이즈 조절
RightDrawer 디자인 개선

Related Issue
close #17
close #16
close #19

추가로 merge때 issue 닫히기 위해서 옆에 Development에 issue 추가할게요

authors: Eeap FacerAin

repo: Terraform-Canvas/front-end


text:
Checking if the linked list is palindrome or not using stacks in C++

💥 Proposal
I would like to add the code for checking if the linked list is palindrome or not using stacks in C++. I am a GSSOC participant. Please /assign this issue to me.
Have you read the Contributing Guidelines on Pull Requests?
Yes

Fixed

repo: TesseractCoding/NeoAlgo


text:
🛑 Proxmox is down

In 10b6e9c, Proxmox (https://pve.tetragg.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Proxmox is back up in 03076e6.

repo: TetraGG/Upptime


text:
🛑 Jellyfin is down

In 59b5563, Jellyfin (https://jellyfin.tetragg.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jellyfin is back up in 8aaa33d.


text:
🛑 Proxmox is down

In 388725e, Proxmox (https://pve.tetragg.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Proxmox is back up in 176f777.


text:
🛑 Jellyfin is down

In 5418772, Jellyfin (https://jellyfin.tetragg.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jellyfin is back up in 7d73c1a.


text:
GitHub Action to publish ASV HTML and copy to rich-benchmarks

Type of changes

[ ] Bug fix
[x] New feature
[ ] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[ ] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
Benchmarks can be run on any machine. Result data included in rich repo. When a release is made, new HTML will be published.

Codecov Report

Merging #2074 (39a5fe6) into master (91e0146) will decrease coverage by 0.00%.
The diff coverage is 93.61%.

@@            Coverage Diff             @@
##           master    #2074      +/-   ##
==========================================
- Coverage   99.49%   99.49%   -0.01%
==========================================
  Files          73       72       -1
  Lines        7361     7336      -25
==========================================
- Hits         7324     7299      -25
  Misses         37       37

Flag
Coverage Δ

unittests
99.49% <93.61%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

rich/__init__.py
100.00% <ø> (ø)

rich/align.py
100.00% <ø> (ø)

rich/highlighter.py
100.00% <ø> (ø)

rich/layout.py
100.00% <ø> (ø)

rich/table.py
100.00% <ø> (ø)

rich/console.py
99.50% <80.00%> (-0.13%)
:arrow_down:

rich/segment.py
99.03% <93.75%> (-0.31%)
:arrow_down:

rich/_win32_console.py
91.48% <100.00%> (+1.48%)
:arrow_up:

rich/cells.py
100.00% <100.00%> (ø)

rich/control.py
100.00% <100.00%> (ø)

... and 4 more

Continue to review full report at Codecov.

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

authors: codecov-commenter darrenburns

repo: Textualize/rich


text:
🛑 node3.th7bo.com is down

In a7842a5, node3.th7bo.com (node3.th7bo.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: node3.th7bo.com is back up in fb2fd19 after 12 minutes.


text:
Can't import the named export 'ChangeDetectorRef' from non EcmaScript module (only default export is available)

My Angular version is 10, and i'm getting this error after this package's been installed.
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 52:171-191
Can't import the named export 'ChangeDetectorRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 59:83-103
Can't import the named export 'ChangeDetectorRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 55:18-27
Can't import the named export 'Directive' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 52:145-158
Can't import the named export 'ElementRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 59:58-71
Can't import the named export 'ElementRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 21:25-37
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 22:26-38
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 60:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 73:18-26
Can't import the named export 'NgModule' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 62:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 64:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 23:22-34
Can't import the named export 'Subscription' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 42:32-44
Can't import the named export 'debounceTime' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 41:22-31
Can't import the named export 'fromEvent' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 42:18-27
Can't import the named export 'startWith' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 52:204-222
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 69:141-159
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 54:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 72:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 53:25-48
Can't import the named export 'ɵɵngDeclareDirective' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 52:25-46
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 69:22-43
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 71:22-44
Can't import the named export 'ɵɵngDeclareInjector' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 70:22-44
Can't import the named export 'ɵɵngDeclareNgModule' from non EcmaScript module (only default export is available)
ERROR in node_modules/ngx-metafizzy-flickity/src/app/ngx-flickity/ngx-flickity.directive.d.ts:16:21

Which version of this package do you use? The current version needed angular13.

"ngx-metafizzy-flickity": "^3.0.0",

which version should I use for angular 10?

and how can I use this for angular 10?

Please try version 2.2.0.
The best way is to update angular in your project :-)

authors: ThRintelen TortuC

repo: ThRintelen/ngx-metafizzy-flickity


text:
Fix srfi-128 for CHICKEN 5.0.2 and later

See this Salmonella output
In older CHICKENs, keywords could be bound like regular symbols, which
was a bit of a strange behaviour.  In 5.0.2 and later this no longer
works, so we'll need to either quote the symbols using pipe characters
or disable the keyword style reader.  The latter is best for portable
code as it requires no actual changes to be made to the upstream code.
So the patch simply disables keyword style, so that identifiers like :comparator: are accepted

Sorry, I've been terrible here at this. I think I understand the change, wondering if I need to do this on other eggs as well, provided they use keywords. In any case, I'm going to accept this pull request, and I'll cut a new version too.

authors: ThatGeoGuy sjamaan


text:
Can I get rid of fetch()?

Why does this source code do fetch() to fetch fonts and css? I want to eliminate fetch() so that it can be used in offline mobile apps.
https://github.com/ThatOpen/engine_components/blob/fc953a6fce8e2160b690a58333a65144a9ac1914/src/ui/UIManager/index.ts#L150-L163

Why does this source code do fetch() to fetch fonts and css?

It's used to style the UI.

I want to eliminate fetch() so that it can be used in offline mobile apps.

You could use https://www.npmjs.com/package/patch-package to load fonts and css from a local file, or better should be included in the repo.

Fixed!


text:
DEF version

If I try to set the version of DEF to be writteon out, I get:
ERROR: set defout version: Command {$def_writer setVersion DEF_5_6}
TypeError in method 'defout_setVersion', argument 2 of type 'odb::defout::Version'
I've updated one of the tests to include this check
07-write_def_test.tcl.gz
The header of the def is:
% more ./OpenDB/build/test.def
VERSION 5.3 ;
NAMESCASESENSITIVE ON ;
DIVIDERCHAR "/" ;
BUSBITCHARS "[]" ;
DESIGN counter ;
UNITS DISTANCE MICRONS 1000 ;
the VERSION value is hardcoded in the defout code. (The version in the incoming DEF is 5.7, so unless otherwise modified by the user, this should be the default value used for the def out version as well)

Addressed in #32.

authors: Colin-Holehouse ahmed-agiza

repo: The-OpenROAD-Project/OpenDB


text:
Document the functionality found in etc/DependencyInstaller.sh

Description
The etc/DependencyInstaller.sh script has a lot of functionality (like being able to do a local install rather than using sudo).
None of this functionality is mentioned in the documentation.
Suggested Solution
Put the output of --help into the documentation.
Additional Context
No response

My suggestion is the setup instructions should actually be;
# Install dependencies which come from the operating system (precompiled packages)
sudo ./etc/DependencyInstaller.sh -base
# Install dependencies which are unavailable from the operating system into ~/.local (alternatively used --prefix=<preferred directory>. These can be removed with `rm -rf ~/.local`.
./etc/DependencyInstaller.sh --common -local

Install into /usr/local by default makes it almost impossible to uninstall things.

It would be nice for the etc/Build.sh script to also support the same -local and -prefix arguments that etc/DependencyInstaller.sh supports.

repo: The-OpenROAD-Project/OpenROAD


text:
Adding obstructions shapes to write_abstract_lef

The write_abstract_left is dumping the shapes rects obstruction instead of the whole layer rect.
The new steps:

collect all the shapes per layer
Bloat all the shapes
Merged all the shapes if overlap ( per layer)
Shrink back the merged polygon
Decomposed the polygon into rects

( The process is in the image below)
The size of the bloat can be determine by the user ( with the -bloat flag), adding it also in the tcl procs, while the default amount is 2*pitch.
This is my first PR, so if there is any comment, suggest for improvement please let me know and I will work to improve it.

Super cool stuff! I wrote the original version of this code, and it's so cool to see it improved

I wrote an abtrace for ng45/gcd and I see
	 LAYER metal4 ;
	   RECT 0.0 0.0 70.11 70.0 ;
	 LAYER metal5 ;
	   RECT 0.0 0.0 70.11 70.0 ;
	 LAYER metal6 ;
	   RECT 0.0 0.0 70.11 70.0 ;
	 LAYER metal7 ;
	   RECT 0.0 0.0 70.11 70.0 ;
	 LAYER metal8 ;
	   RECT 0.0 0.0 70.11 70.0 ;
	 LAYER metal9 ;
	   RECT 0.0 0.0 70.11 70.0 ;
	 LAYER metal10 ;
	   RECT 0.0 0.0 70.11 70.0 ;

which makes no sense since those layer are mostly empty but here they are fully blocked.  How have you tested this?

You are pretty close to having it right.  Thanks for working on this.

Hi, I have fixed the issues that you mention.

for ng45/gcd the blockage for metal3 under various bloat choices:
0:

2:

5:

15:

The last looks like a reasonable model.  I think the others are too detailed.  I'm curious what others think...

Rather than gather all the obs and then merge them it would be better to merge them as you go.  The set of objects to be merged could be huge on a large design.

This is an interesting abstract strategy but generally it seems undesirable. For most macros being abstracted, you want to mark any internal layers as "cover" blockages - the entire layer is covered with a blockage if any shapes exist on that layer. The reasons for this are that:
1, Computation is easier for the router
2. The LEF file size is reduced
3. It disallows routing near the internal nets of the macro, which could cause signal integrity violations that won't be caught by almost any other means.
4. Most macros should be metal filled before abstracting to ensure that the extracted parasitics and therefore timing models are accurate. In this case, the layer will be entirely blocked anyways.
It seems this PR changes the default abstraction method to bloating. I definitely think that if there is no bloating, the old method (which I believe is "all layers are cover layers") should be used.

for ng45/gcd the blockage for metal3 under various bloat choices: 0:
2:
5:
15:
The last looks like a reasonable model. I think the others are too detailed. I'm curious what others think...

15 looks better. Is there a good way to determine the largest bloat factor that would basically create a single sheet for each layer?

I think it is reasonable to have an option to just block the entire area as we do currently.  I think that is a different option than -bloat_factor and a different 'algorithm'.

1, Computation is easier for the router

the point of the bloating is to trade off simplicity versus accuracy.  Its why I objected to bloat 0.

The LEF file size is reduced

Same as above

It disallows routing near the internal nets of the macro, which could cause signal integrity violations that won't be caught by almost any other means.

We can easily add a final bloat option to increase the spacing as desired.

Most macros should be metal filled before abstracting to ensure that the extracted parasitics and therefore timing models are accurate. In this case, the layer will be entirely blocked anyways.

Not if you want to be able to route through the area in question which is a goal here.  Additional spacing / shielding removes most of the RC extraction concerns (inter-layer effects are still possible but can be conservatively modelled as they are smaller).

I'm not objecting to the functionality as long as the default behavior of write_lef_abstract is to generate obstructions for the whole layer. I think bloating is very useful in perhaps a few circumstances.
An ideal interface to me would look like
write_lef_abstract [-bloat_factor bloat_factor [-layers {layers}]]

Examples:
# Write an abstract LEF with cover obstructions on each layer
# There are still cutouts for pins
write_lef_abstract

# Write an abstract LEF with bloat factor of 15 on each layer
write_lef_abstract -bloat 15

# Write an abstract LEF with bloat factor of 15 on M4, M5
# All other layers use cover obstructions
write_lef_abstract -bloat 15 -layers {M4 M5}

# Write an abstract LEF with bloat factor of 15 on M4, M5
# Bloat factor of 0 on M6, M7
# All other layers use cover obstructions
write_lef_abstract -bloat 15 -layers {M4 M5} -bloat 0 -layers {M6 M7}

There is no need for pin cutouts unless they are not on the macro edge

There is no need for pin cutouts unless they are not on the macro edge

It would be nice for consistency/compatibility with other abstracting/P&R tools. It is standard for IP to have pin cutouts.

There is no need for pin cutouts unless they are not on the macro edge

It would be nice for consistency/compatibility with other abstracting/P&R tools. It is standard for IP to have pin cutouts.

It is perhaps common but it isn't standard - you can see plenty of cases where that isn't true.  lef/def specifically allow you to access pins covered by an obs.

Do we really need layer specific bloating?  I'd rather not add complexity unless someone will actually use it.

What if someone doesn't want to allow routing on lower layers but is fine with routing on upper layers?
An example: top-level power mesh is on M6-M7. Signal routing is on M1-M5. Designer is fine with allowing external signals to pass through on M6-M7 but doesn't want signals passing through M1-M5.
Doing all-or-nothing bloating for the whole block seems like kind of extreme.

Just speaking personally, I would use this feature if I could free up routing resources on upper layers. I would probably not use it if I couldn't block all of the lower layers.

Ok if there is value we should add it.  I am also ok to push it into a follow on PR.

You should update the src/README as this change would make the warning there obsolete.

Hi,
I did some changes:

Merge the polygon as we go, which supposed to easier for large design.
I added insts ITerms to the obstructions
Added the insts obstructions to the lef ( I am not sure about this one, please let me know if that what you meant )

There was other discussion about the this, but I don't understand what the conclusion, If you rather to do some change of the bloat_factor default please let me know.

There is a request to have an option for the old behavior.  I don't like calling that '-bloat 0' and suggest we just add a different option like -block_occupied_layers.  In a later PR we can allow users to choose the new or old style on a per layer basis.

So what is the next step here?
Should I add this option to this PR and the next one?
Any change needed regarding the previous requests?

I think you should add that change here as otherwise it would represent a loss of functionality for those who prefer the older style.   Also you need to fix the CI errors.

I added the bloat_occupied_layers option, to cover the whole layer same as the previous functionality.
I would like to get some help with the CI errors, it seems that the build of the project are ok but it failed on certain test ( TestGuide) with undefine reference for dbITermShapeItr.
I don't understand why it's failing since all the correct include are there and the build don't throw error on this.

The dependencies in odb are off.  I'll fix that up and you can merge afterwards.

If you merge master to your branch this problem should be fixed (after you resolve the merge conflicts).

I merge with master and it looks like it passing now, except the lef test that failed as expected.

For the LEF tests - please verify that the new results are correct and update the test.  You can use the save_ok script to do so.

Added the new LEF for test

I used the save_ok script to change the log too.
But the DCO check always failed even when I use git commit -s, any idea why?

Most likely you have a commit that was unsigned.  DCO checks all commits.

Thank, it worked.
The commit pass the tests.

remove src/odb/src/swig/python/.CMakeLists.txt.swo & src/odb/src/swig/common/.odb.i.swp

re: the discussion of having an option for the old behavior - is that implemented?

Done.

re: the discussion of having an option for the old behavior - is that implemented?

Yes, I added the option to use the bloat_occupied_layers flag, and in that way the whole Layer will be cover in the OBS.
I tested it and the results is the same as the previous lef.

Changing the default makes the tests fail so you'll have to update them again

Changing the default makes the tests fail so you'll have to update them again

Yes, forgot about it.
I'm running it now.

@arlpetergadfort I believe your concern about the old mode is addressed by -bloat_occupied_layers.  Since you are out I'm going to merge and if you have further concerns we can address them when you are back.

Thanks!
Sure I will be happy to keep contributing.
Can you suggest on what I could working on next?
I rather to work on something new other then the write_lef for now.

Some ideas that come to mind

GUI performance (opengl, caching, etc)
odb code generator could be improved / used more broadly (more automated generation of database code)
dpo (detailed placement optimization) has a simple hard coded recipe; explore the possibilities looking for improvements
General software improvements - Coverity issues, logger usage, valgrind
If you have specific interests there are always more things that need doing.

dpo is sound very intersting but I hope that is something that I will able to handle with.
Also after the write_lef adventure I was starting to familiar the odb db types, so that also be an option.
BTW, there is another place that we can discuss about it?

I'm on the skywater slack (Matt Liberty)

This PR added tests for the new behavior but removed the tests for the old behavior. Should we have tests for that?

Also requires updates to the README about how to use the new flags.

Also requires updates to the README about how to use the new flags.

@niv280 would you be willing to do a quick PR with updates to the README about the new capability?

Yes, sorry I started it before but didn't succeed to PR in here.
I create new PR with the update README

Sure, sorry I started to add it before but didn't understand how to add another commit after I deleted the branch.
I added it in new PR now.

authors: QuantamHD arlpetergadfort maliberty niv280 rovinski


text:
utl: provide pop_metrics_stage return value

Exposes the return value of pop_metrics_stage to the script.

I'm curious what motivated this change.

@maliberty some changes I'm attempting to make in the SC flow, but also just thought it would be nice to have access to it.

authors: gadfort maliberty


text:
example of sram mock_area flow failing due to shared output file name…

… definition
PR to share test case - do not merge
Enables mock_area flow for two SRAMs, which causes bazel-orfs to try and define the same output file for two different SRAMs.
Proposed fix in bazel-orfs PR: https://github.com/The-OpenROAD-Project/bazel-orfs/pull/180

fixed

authors: jeffng-or oharboe

repo: The-OpenROAD-Project/megaboom


text:
Added refresh for web

When on web, window is reloaded

Please merge this

authors: GoodVibesLab kuyazee


text:
🛑 Law Blog is down

In a9a2bcb, Law Blog (blog.lawcloud.page) was down:

HTTP code: 523
Response time: 3372 ms

Resolved: Law Blog is back up in 4b5c196.

repo: TheBlankness/uptime-lawcloud


text:
Failed to map driver

[<] Loading vulnerable driver, Name: QvxVqegYVXXFT
[+] NtLoadDriver Status 0x0
[-] Can't find pattern
[-] Warning no PiDDBCacheTable Found
[-] Failed to ClearPiDDBCacheTable
[<] Unloading vulnerable driver
[+] NtUnloadDriver Status 0x0
[+] Vul driver data destroyed before unlink

This may be due to my windows version being Windows 11 22449.1000 can I get a confirmation?

Are you using the latest commit? I will check tomorrow if I have time with that Windows version

Ye Im using the latest commit

Yes version 22449 breaks the pattern again I will fix the pattern later when I got time

Update pushed

authors: GraterThumbleed TheCruZ

repo: TheCruZ/kdmapper