regex parser is faster than the literal one.

Not a big issue, but for a test 10G TSV file, the "regex" parser is faster than the literal one. (hck with PGO)
# 10G TSV file.

$ wc -l e.sorted.tsv
71741554 e.sorted.tsv

$ timeit hck -d '\t' -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d \t -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:12.01 = 12.01 seconds
  * Elapsed CPU time:
     - User: 8.82
     - Sys: 3.12
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 34
     - Involuntarily (time slice expired): 14
  * Maximum resident set size (RSS: memory) (kiB): 9563064
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 19840
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -d $'\t' -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d 	 -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:11.45 = 11.45 seconds
  * Elapsed CPU time:
     - User: 8.39
     - Sys: 3.00
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 36
     - Involuntarily (time slice expired): 21
  * Maximum resident set size (RSS: memory) (kiB): 9563016
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 21840
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d $'\t' -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d 	 -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:13.61 = 13.61 seconds
  * Elapsed CPU time:
     - User: 10.56
     - Sys: 2.98
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 40
     - Involuntarily (time slice expired): 19
  * Maximum resident set size (RSS: memory) (kiB): 9563132
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 26352
     - # of outputs: 0
  * Exit status: 0

$ timeit hck  -d<PHONE_NUMBER>08200b88dd3ce688a7dcff -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d<PHONE_NUMBER>08200b88dd3ce688a7dcff -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:13.28 = 13.28 seconds
  * Elapsed CPU time:
     - User: 9.80
     - Sys: 3.40
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 46
     - Involuntarily (time slice expired): 20
  * Maximum resident set size (RSS: memory) (kiB): 9563176
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 26304
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d<PHONE_NUMBER>08200b88dd3ce688a7dcff -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d<PHONE_NUMBER>08200b88dd3ce688a7dcff -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:20.61 = 20.61 seconds
  * Elapsed CPU time:
     - User: 17.04
     - Sys: 3.44
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 93
     - Involuntarily (time slice expired): 30
  * Maximum resident set size (RSS: memory) (kiB): 9563024
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 53440
     - # of outputs: 0
  * Exit status: 0

Interesting, that definitely seems odd, but not totally out of the question. Even in my own benchmarks in the REAMDE hck with a literal is very close to hck with a regex when the regex is actually a single character. Under the hood the regex crate handles the single character case and basically boils down to the same code as the -L path in hck with just a few extra function calls in the way.
For splitting on a long but fixed substr I'd be willing to believe that the regex crate is again doing some special handling that I am not for that case. hck just uses substr_split.
I'll do some more looking though because this still seems a bit counter-intuitive / hck should apply the same special casing a the regex crate if possible for long substr delims.
Some follow ups:

What PGO install process did you use?
What OS are you one? (maybe also try --no-mmap)
What cpu do you have?

I know that regex uses a lot of tricks (e.g. first trying to find rare characters) to speedup regex matches,
but I am surprised it is faster for 1 byte matches with all the function call overhead.
I used:
just install-native

OS: CentOS7
With --no-mmap, all commands run much faster.
As the input file is already in shared memory, I didn't expect such a big difference.
$ timeit hck -L -d<PHONE_NUMBER>08200b88dd3ce688a7dcff -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d<PHONE_NUMBER>08200b88dd3ce688a7dcff -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:18.95 = 18.95 seconds
  * Elapsed CPU time:
     - User: 15.78
     - Sys: 3.12
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 3
     - Involuntarily (time slice expired): 7
  * Maximum resident set size (RSS: memory) (kiB): 9563652
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d<PHONE_NUMBER>08200b88dd3ce688a7dcff -f 1,2 --no-mmap /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d<PHONE_NUMBER>08200b88dd3ce688a7dcff -f 1,2 --no-mmap /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:16.76 = 16.76 seconds
  * Elapsed CPU time:
     - User: 14.07
     - Sys: 2.65
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 5
     - Involuntarily (time slice expired): 6
  * Maximum resident set size (RSS: memory) (kiB): 1656
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d $'\t' -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d 	 -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:13.13 = 13.13 seconds
  * Elapsed CPU time:
     - User: 9.93
     - Sys: 3.16
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 8
     - Involuntarily (time slice expired): 5
  * Maximum resident set size (RSS: memory) (kiB): 9563704
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d $'\t' -f 1,2 --no-mmap /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d 	 -f 1,2 --no-mmap /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:10.61 = 10.61 seconds
  * Elapsed CPU time:
     - User: 7.91
     - Sys: 2.67
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 3
     - Involuntarily (time slice expired): 6
  * Maximum resident set size (RSS: memory) (kiB): 1628
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -d $'\t' -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d 	 -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:11.12 = 11.12 seconds
  * Elapsed CPU time:
     - User: 8.15
     - Sys: 2.93
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 3
     - Involuntarily (time slice expired): 62
  * Maximum resident set size (RSS: memory) (kiB): 9563696
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -d $'\t' -f 1,2 --no-mmap /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d 	 -f 1,2 --no-mmap /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:08.67 = 8.67 seconds
  * Elapsed CPU time:
     - User: 6.47
     - Sys: 2.17
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 5
     - Involuntarily (time slice expired): 49
  * Maximum resident set size (RSS: memory) (kiB): 1820
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

# With hck compiled without pgo:
$ export RUSTFLAGS='-C target-cpu=native
$ cargo install --path . --force

$ timeit hck -d $'\t' -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d 	 -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:12.01 = 12.01 seconds
  * Elapsed CPU time:
     - User: 8.88
     - Sys: 3.04
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 18
     - Involuntarily (time slice expired): 5
  * Maximum resident set size (RSS: memory) (kiB): 9563896
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 4936
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -d $'\t' -f 1,2 --no-mmap /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d 	 -f 1,2 --no-mmap /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:09.95 = 9.95 seconds
  * Elapsed CPU time:
     - User: 7.25
     - Sys: 2.67
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 5
     - Involuntarily (time slice expired): 55
  * Maximum resident set size (RSS: memory) (kiB): 1948
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d $'\t' -f 1,2 /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d 	 -f 1,2 /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:13.05 = 13.05 seconds
  * Elapsed CPU time:
     - User: 9.88
     - Sys: 3.13
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 3
     - Involuntarily (time slice expired): 5
  * Maximum resident set size (RSS: memory) (kiB): 9563712
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d $'\t' -f 1,2 --no-mmap /dev/shm/e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d 	 -f 1,2 --no-mmap /dev/shm/e.sorted.tsv
  * Elapsed wall time: 0:10.79 = 10.79 seconds
  * Elapsed CPU time:
     - User: 8.20
     - Sys: 2.56
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 3
     - Involuntarily (time slice expired): 9
  * Maximum resident set size (RSS: memory) (kiB): 1724
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

Is the data that you have sharable by chance?
I think the short answer is that this isn't unexpected.
mmap performance varies a lot across platforms. For OSX for example I default hck to not use mmap.
As for "regex" vs "literal" on a single byte, I think I need to put it in a profiler to check. Looking just a no-mmap for the moment, the regex codepath will use the core::hck_reader method and the literal will use core::hck_reader_fast.
The difference being that hck_reader uses ripline to find lines and then hands them to the line_parser which in turn uses the regex splitter. The hck_reader_fast uses memchr2 to look for seperators and line terminators at the same time. For a single character regex ends up using just memchr and really only adds one, maybe two extra function calls if I remember correctly.
This is a stretch, but possibly depending on the cpu type it is more efficient to have run memchr twice than run memchr2 once. Or alternatively, if you have very very long lines it might be more efficient to not be searching for both seperators and newlines at the same time. What sort of cpu are you on? I'm not sure more can be determined without running some profiling.
Note to future self: add a way to override the "fast-mode" selection so that a single byte literal could be run through the same codepath as the regex code.

One final thought, is the performance the same if you move it out of /dev/shm? I haven't every interacted with shm before, but if my understanding is correct it's kind of like mmap, which means the heuristics about which processing codepath hck is using are... suspect... in this case.

Gzipped test file: https://temp.aertslab.org/e.sorted.tsv.gz
I put the file in /dev/shm after running the same on a shred filesystem (which gave similar time diferences between commands) to see if the filesystem was causing the difference in timings.
With a local file (with warm cache):
$ timeit hck -d $'\t' -f 1,2 e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d      -f 1,2 e.sorted.tsv
  * Elapsed wall time: 0:11.50 = 11.50 seconds
  * Elapsed CPU time:
     - User: 8.88
     - Sys: 2.58
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 7
     - Involuntarily (time slice expired): 5
  * Maximum resident set size (RSS: memory) (kiB): 9563892
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -d $'\t' -f 1,2 --no-mmap e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d      -f 1,2 --no-mmap e.sorted.tsv
  * Elapsed wall time: 0:09.34 = 9.34 seconds
  * Elapsed CPU time:
     - User: 7.53
     - Sys: 1.78
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 7
     - Involuntarily (time slice expired): 4
  * Maximum resident set size (RSS: memory) (kiB): 1944
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d $'\t' -f 1,2 e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d   -f 1,2 e.sorted.tsv
  * Elapsed wall time: 0:14.74 = 14.74 seconds
  * Elapsed CPU time:
     - User: 11.48
     - Sys: 3.21
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 11
     - Involuntarily (time slice expired): 6
  * Maximum resident set size (RSS: memory) (kiB): 9563692
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d $'\t' -f 1,2 --no-mmap e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d   -f 1,2 --no-mmap e.sorted.tsv
  * Elapsed wall time: 0:10.72 = 10.72 seconds
  * Elapsed CPU time:
     - User: 8.80
     - Sys: 1.89
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 7
     - Involuntarily (time slice expired): 5
  * Maximum resident set size (RSS: memory) (kiB): 1724
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

CPU info:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 85
model name      : Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz
stepping        : 4
microcode       : 0x2006906
cpu MHz         : 999.932
cache size      : 25344 KB
physical id     : 0
siblings        : 18
core id         : 0
cpu cores       : 18
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 invpcid_single intel_ppin intel_pt ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts hwp hwp_act_window hwp_pkg_req pku ospke md_clear spec_ctrl intel_stibp flush_l1d
bogomips        : 4600.00
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

...

Okay, I believe I've figured it out.
The "fast mode" parsers do not short-circuit and stop looking for separators after the rightmost field is found. Instead they would just keep running with memchr2. As a result, if your last field was less then ~2/3 through the total number of fields the regex / slow mode parsers would be faster.
In v0.6.6 I've fixed this and the result is a pretty nice speedup across the benchmark numbers.

Thanks. Now it is 1.5 second faster than the regex version:
$ timeit hck --no-mmap -L -d $'\t' -f 1,2 e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck --no-mmap -L -d 	 -f 1,2 e.sorted.tsv
  * Elapsed wall time: 0:07.48 = 7.48 seconds
  * Elapsed CPU time:
     - User: 5.31
     - Sys: 2.14
  * CPU usage: 99%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 7
     - Involuntarily (time slice expired): 14
  * Maximum resident set size (RSS: memory) (kiB): 1644
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck --no-mmap -d $'\t' -f 1,2 e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck --no-mmap -d 	 -f 1,2 e.sorted.tsv
  * Elapsed wall time: 0:08.74 = 8.74 seconds
  * Elapsed CPU time:
     - User: 6.55
     - Sys: 2.02
  * CPU usage: 98%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 7
     - Involuntarily (time slice expired): 3407
  * Maximum resident set size (RSS: memory) (kiB): 1816
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -L -d $'\t' -f 1,2 e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -L -d 	 -f 1,2 e.sorted.tsv
  * Elapsed wall time: 0:11.69 = 11.69 seconds
  * Elapsed CPU time:
     - User: 8.02
     - Sys: 3.03
  * CPU usage: 94%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 8
     - Involuntarily (time slice expired): 191
  * Maximum resident set size (RSS: memory) (kiB): 9563660
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0

$ timeit hck -d $'\t' -f 1,2 e.sorted.tsv > /dev/null

Time output:
------------

  * Command: hck -d 	 -f 1,2 e.sorted.tsv
  * Elapsed wall time: 0:13.48 = 13.48 seconds
  * Elapsed CPU time:
     - User: 8.85
     - Sys: 3.03
  * CPU usage: 88%
  * Context switching:
     - Voluntarily (e.g.: waiting for I/O operation): 7
     - Involuntarily (time slice expired): 157
  * Maximum resident set size (RSS: memory) (kiB): 9563916
  * Number of times the process was swapped out of main memory: 0
  * Filesystem:
     - # of inputs: 0
     - # of outputs: 0
  * Exit status: 0


Error updating whitespace and reformatting data to lowercase in Dbeaver.

Description
Hi everyone, I have a question: after I run the update command to remove spaces and convert the data to lowercase, but after I run the command, the result of the full name column failed. The names of all customers have been replaced with the first person's name. Where is the error in Dbeaver?

DBeaver Version
Dbeaver 24.1.5
Operating System
window 10
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

This is not a Dbeaver issue but a querry issue. You told the query to replace each row with one string as the sub query will return a list of values and I guess the DB used the first value of the result set.
I am not a sqlite user, but I guess it should be this:
Set full_name = LOWER(LTRIM(full_name))
from ....
Or as in oracle you need to provide a joining condition between the value you would update and the value you would write in the field.

@TB-HunBoka Thanks so much. I completed the mission thanks to you


ovsdb-idl: Add support for change tracking.

Ovsdb-idl notifies a client that something changed; it does not track
which table, row changed in what way (insert, modify or delete).
As a result, a client has to scan or reconfigure the entire idl after
ovsdb_idl_run(). This is presumably fine for typical ovs schemas where
tables are relatively small. In use-cases where ovsdb is used with
schemas that can have very large tables, the current ovsdb-idl
notification mechanism does not appear to scale - clients need to do a
lot of processing to determine the exact change delta.
This change adds support for:

Table and row based change sequence numbers to record the
most recent IDL change sequence numbers associated with insert,
modify or delete update on that table or row.

Change tracking of specific columns. This ensures that changed
rows (inserted, modified, deleted) that have tracked columns, are
tracked by IDL. The client can directly access the changed rows
with get_first, get_next operations without the need to scan the
entire table.
The tracking functionality is not enabled by default and needs to
be turned on per-column by the client after ovsdb_idl_create()
and before ovsdb_idl_run().
/* Example Usage */
{
   idl = ovsdb_idl_create(...);
   /* Track specific columns */
   ovsdb_idl_track_add_column(idl, column);
   /* Or, track all columns */
   ovsdb_idl_track_add_all(idl);
   for (;;) {
     ovsdb_idl_run(idl);
     seqno = ovsdb_idl_get_seqno(idl);
     /* Process only the changed rows in Table FOO */
     FOO_FOR_EACH_TRACKED(row, idl) {
       /* Determine the type of change from the row seqnos */
       if (foo_row_get_seqno(row, OVSDB_IDL_CHANGE_DELETE) > seqno)) {
         /* row is deleted */
       } else if {foo_row_get_seqno(row, OVSDB_IDL_CHANGE_MODIFY) > seqno))
         /* row is modified */
       } else if {foo_row_get_seqno(row, OVSDB_IDL_CHANGE_INSERT) > seqno))
         /* row is inserted */
       }
     }
     /* All changes processed - clear the change track */
     ovsdb_idl_track_clear(idl);
   }
}

Signed-off-by: Shad Ansari<EMAIL_ADDRESS>

Thank you for the patch!  I've started a discussion of it on ovs-dev: http://openvswitch.org/pipermail/dev/2015-October/061163.html
I think that it is likely that a new version will be required, so I'm closing this pull request for now.  I hope that later a new version will be posted.


Callback endpoint

Is there any more documentation on the distributedtask/hubs endpoint used for the callbacks?

Permissions required to call it?
Can we do validation on the completion data?
Is the user that made the call logged anywhere?

I want to ensure that only my Azure function can continue the pipeline, but from testing it seems that any user can call the endpoint and continue the pipeline.

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

ID: 788ade26-087e-737f-21fd-5cc9f36666a5
Version Independent ID: 78733f37-e78e-e044-e2e9-5e67a2eae374
Content: Invoke Azure Function task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/azure-function.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

@shashban - can you please take a look?

I guess @shashban doesn't care. I agree, is there no better documentation on this?

The call back API is documented at https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/azure-function?view=azure-devops#where-should-a-task-signal-completion-when-callback-is-chosen-as-the-completion-event
The URL is specific to each job in the release and guarded by the same authentication as other Azure DevOps APIs.

@shashban  - that doesn't quite answer the question - when I say permissions required to call it I mean permissions within Azure DevOps.
I also asked
Can we do validation on the completion data?
Is the user that made the call logged anywhere?


Dashboard: BLV and Metric Improvements

Mirrors changes to BLV categorisation from https://github.com/OlympusDAO/treasury-subgraph/pull/38/
Update treasury-subgraph-client version
Shift to using metrics calculated in treasury-subgraph, instead of calculating them locally (which duplicates code to maintain)
Remove dead code

Production API deployment done.
Confirmed that the Fleek preview build works against the production API.


deployment-state.json

Amplify CLI Version
11.1.1
Question
Hope I'm not going crazy, but I'm not able to locate deployment-state.json file anymore in the S3 deployment bucket. I have deleted this file several times manually in the past to get over the legendary problem of "A deployment is already in progress", but I'm not able to locate it anymore unfortunately. Has anything changed recently with amplify upgrades?

I would check the status of your amplify CloudFormation stack to see if it's in UPDATE_CLEANUP_IN_PROGRESS.
This issue just happened to me, and it turns out it was getting stuck on deleting the lambda layer version.
The managed amplify policy needed the lambda:GetLayerVersionPolicy action. I added it to the build role, and it completed successfully.

Interestingly I did see a layer stack stuck on UPDATE_CLEANUP_IN_PROGRESS. Currently Amplify uses the default role with the managed policy AdministratorAccess-Amplify, which doesn't seem to have the permission for lambda:GetLayerVersionPolicy action. Just curious, did you manually add the additional permission to the role or figured out a way to codify it?

Yeah I had to manually add the permission as an inline policy to the service role.

I did the same and it worked like a charm, yeah hope this issue has gets priority in the backlog. Strangely this issue is only sporadic and not consistent.
The other part of my question where I'm not able to locate the deployment-state.json still remains a mystery.

Related: Is there already a feature request somewhere for a CLI command to fix this problem automatically, so that we don't need a highly-trained DevOps engineer to come to the rescue and [shudder] manually screw with the contents of deployment S3 buckets in order to recover mission-critical production environments?
I find myself struggling daily to defend the idea that Amplify is production-ready and that we can depend on it.  We had a defect in production for over six hours yesterday due to this problem.  PLEASE provide a working amplify env update command of some kind.  Production operators demand it.

AdministratorAccess-Amplify

Same issue, can you please detail the complete procedure to fix the issue ?

Hey @vgthoppae, thank you for reaching out. This is currently being tracked on aws-amplify/amplify-studio#969 to have this added to AdministratorAccess-Amplify policy and the Amplify team is currently investigating this behaviour.

Thank you @ykethan

AdministratorAccess-Amplify

Same issue, can you please detail the complete procedure to fix the issue ?

Find the Service role attached to your amplify app (App -> App Settings -> General)
Look up that role in IAM - you will find AdministratorAccess-Amplify policy attached to it
Add an inline policy as below

Hey everyone, thank you for your patience while the Amplify team investigates this behaviour, wanted provide an update on this issue. The behaviour occurred due to a recent update on the Lambda service. The Lambda team has provided an update that this issue has been mitigated and subsequent amplify push executions should work as expected. To summarize, Amplify CLI utilizes CloudFormation to deploy resources and due to the Lambda service update, CloudFormation did not return the correct status.
Please do let us know if you are still experiencing this issue.

Thanks @ykethan and everyone responding in this thread. I'm gonna close this issue as there is a workaround available with additional permission.


disabled option feature not published

I saw that 'disabled' prop options for FormSelect has been added. (i.e.: https://github.com/elementalui/elemental/commit/3522015341406549e115520121c455757ffaf8b8)
Will we get a new publish on those features soon?

@yaxinn if a feature is on the website, it's published to npm


'NSInvalidArgumentException', reason: '-[FBLPromise HTTPBody]: unrecognized selector sent to instance

I'm stuck integrating firebase with bazel - I have made some progress
https://github.com/firebase/firebase-ios-sdk/issues/6115
but when I run the build - the xcframework that's built with firebase analytics - doesn't have this method - HTTPBody

I'm using this BUILD file inside FirebaseAnalytics directory

load("@build_bazel_rules_apple//apple:apple.bzl",
    "apple_dynamic_xcframework_import","apple_static_xcframework_import"
)

objc_library(
    name = "FirebaseAnalytics",
    deps = ["FirebaseAnalyticsXCFramework"],
    enable_modules = True,
    module_name = "FirebaseAnalytics",
    visibility = ["//visibility:public"],

)

objc_library(
    name = "FBLPromises",
    deps = ["FBLPromisesXCFramework"],
    enable_modules = True,
    module_name = "FBLPromises",
    visibility = ["//visibility:public"],

)

apple_static_xcframework_import(
    name = "FirebaseAnalyticsXCFramework",
    xcframework_imports = glob(["FirebaseAnalytics.xcframework/**"] ),
    library_identifiers = {
        "ios_device": "ios-arm64_armv7",
        "ios_simulator": "ios-arm64_i386_x86_64-simulator",
    },
    deps = ["FBLPromisesXCFramework",
    "FirebaseAnalyticsSwiftXCFramework",
    "FirebaseCoreXCFramework"
    ,"FirebaseCoreDiagnosticsXCFramework",
    "FirebaseCoreInternalXCFramework",
    "FirebaseInstallationsXCFramework",
    "GoogleAppMeasurementXCFramework",
    "GoogleAppMeasurementIdentitySupportXCFramework",
    "GoogleUtilitiesXCFramework",
    "GoogleDataTransportXCFramework",
    "nanopbXCFramework",
    ],
    visibility = ["//visibility:public"],
)

apple_dynamic_xcframework_import(
    name = "FBLPromisesXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["FBLPromises.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "FirebaseAnalyticsSwiftXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["FirebaseAnalyticsSwift.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "FirebaseCoreXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["FirebaseCore.xcframework/**"] ),
      visibility = ["//visibility:public"],
)

apple_dynamic_xcframework_import(
    name = "FirebaseCoreDiagnosticsXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["FirebaseCoreDiagnostics.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "FirebaseCoreInternalXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["FirebaseCoreInternal.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "FirebaseInstallationsXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["FirebaseInstallations.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "GoogleAppMeasurementXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64_armv7",
        "ios_simulator": "ios-arm64_i386_x86_64-simulator",
    },
    xcframework_imports = glob(["GoogleAppMeasurement.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "GoogleAppMeasurementIdentitySupportXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64_armv7",
        "ios_simulator": "ios-arm64_i386_x86_64-simulator",
    },
    xcframework_imports = glob(["GoogleAppMeasurementIdentitySupport.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "GoogleDataTransportXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["GoogleDataTransport.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "GoogleUtilitiesXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["GoogleUtilities.xcframework/**"] ),
)

apple_dynamic_xcframework_import(
    name = "nanopbXCFramework",
    library_identifiers = {
        "ios_device": "ios-arm64",
        "ios_simulator": "ios-arm64_x86_64-simulator",
    },
    xcframework_imports = glob(["nanopb.xcframework/**"] ),
)

someone suggested on stackoverflow to patch it - but I'm new to bazel - and it is not straightforward.
BUILD

objc_library(
    name = "FBLPromises",
    module_name = "FBLPromises",
    enable_modules = True,
    srcs = glob([
        "Sources/*.m",
        "Sources/*.h",
    ]),
    hdrs = glob([
        "PublicHeaders/*.h",
    ]),
    includes = [
       "PublicHeaders",
    ],
    sdk_frameworks = [
        "Foundation",
        "UIKit",
    ],
    visibility = [
        "//visibility:public",
    ],
)

//  FBLPromise+Extension.h
#if __has_include(<FBLPromises/FBLPromises.h>)
#import <FBLPromises/FBLPromises.h>
#else
#import "FBLPromises.h"
#endif
#import <Foundation/Foundation.h>

@interface FBLPromise (Extension)

@property(nonatomic, readonly) NSHTTPURLResponse *HTTPResponse;
@property(nonatomic, readonly) NSData *HTTPBody;

- (instancetype)initWithResponse:(NSHTTPURLResponse *)response HTTPBody:(NSData *)body;

@end

//  FBLPromise+Extension.m
#import "FBLPromises.h"
#import <Foundation/Foundation.h>

@implementation FBLPromise (Extension)
+ (NSData *)HTTPBody {
    return nil;
}

- (NSData *)HTTPBody {
    return nil;
}

+ (void)setHTTPBody:(NSData *)data {
}

- (void)setHTTPBody:(NSData *)data {
}

+ (NSHTTPURLResponse *)HTTPResponse {
    return nil;
}

- (NSHTTPURLResponse *)HTTPResponse {
    return nil;
}

+ (void)setHTTPResponse:(NSHTTPURLResponse *)data {
}

- (void)setHTTPResponse:(NSHTTPURLResponse *)data {
}

+ (instancetype)initWithResponse:(NSHTTPURLResponse *)response HTTPBody:(nullable NSData *)body {
    return nil;
}

- (instancetype)initWithResponse:(NSHTTPURLResponse *)response HTTPBody:(nullable NSData *)body {
    return nil;
}
@end

should this be necessary? does this method exist in this code? is it straightforward to spit out an xcframework for this project? I had a go with carthage and it was ok.

related https://github.com/google/promises/issues/189

this approached doesn't have same problem
demo app
https://github.com/vikage/DemoBazel/blob/firebase/Thirdparty/Firebase/BUILD


when multiple session id is returned, sessionFilter record the first session instead of the last session

From<EMAIL_ADDRESS>on March 03, 2015 17:35:07
What steps will reproduce the problem? 1. our API return the JSESSIONID twice in the response as below:
HTTP/1.1 204 No Content
Server: Apache-Coyote/1.1
X-Powered-By: Servlet/3.0; JBossAS-6
Set-Cookie: JSESSIONID=62D1D59D748A8F4634D6F791881626CC.q2jb1vip1; Expires=Tue, 03-Mar-2015 17:25:43 GMT; Path=/
x-wily-info: Clear guid=E075105A0A27025001E014CEAA23271F
x-wily-servlet: Encrypt1 Xnksvd+miNh9ArlLEFWXNlbi1pnj4cFAxUsse4V8i7u7o23Mnd31l7uwqFABsB1cfashWsgA2RkHs+ITldYaAANknN0YfZgljUDVw5QcoGmnmz91NZRnHjJgseNTyTFB0ggXRjlWZggjV/rvLHN1dJUraJk1bs78Ov3kFc1HTFI=
Set-Cookie: JSESSIONID=538C8DE5DB757636E028BABAB3847A60.q2jb1vip1; Expires=Tue, 03-Mar-2015 17:25:43 GMT; Path=/
Date: Tue, 03 Mar 2015 16:25:43 GMT
2.when use sessionFilter to record the session id returned from the server, it always record the first one. in this example JSESSIONID=62D1D59D748A8F4634D6F791881626CC.q2jb1vip1
3.it should instead record the last oen, in this example will be
JSESSIONID=538C8DE5DB757636E028BABAB3847A60.q2jb1vip1 What is the expected output? What do you see instead? when multiple session id is returned, should always use the latest one, this is how browsers behavior as well. But instead, sessionFilter seems record the first one. What version of the product are you using? On what operating system? using rest-assured-2.3.3.jar, tested on windows. Please provide any additional information below.
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=388

From<EMAIL_ADDRESS>on March 16, 2015 03:58:02
Is it the same with headers and all other values passed in the response? In that case I suppose we should change this for everything. Right now the first value is always returned.
Status: Accepted


A JavaScript error occurred in the main process

Type: Bug
Launch VSCode 1.74.3 after update from 1,5.x  installation, returns the following error message.
Errcr
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot find module 'C:\UsersX______\AppData\LocaI\Programs\Microsoft VS
Code\resources\app\out\main'
at Module. resolveFiIename
at Function.o. resolveFiIename (node:eIectron/js2c/browser
at (node:eIectron/js2c/browser init:
at Object../lib/browser/init.ts (node:eIectron/js2c/browser init:
at webpack_require_ (node: electron/js2c/browser init: I: 128)
at node:eIectron/js2c/browser init: I: 1200
at node:eIectron/js2c/browser init: I: 1267
at NativeModuIe.compiIeForInternaILoader
at NativeModuIe.compiIeForPubIicLoader (nodeinternaI/bootstrap/Ioaders:252: 10)
at loadNativeModuIe
Info from VSCode
Version: 1.74.3 (system setup)
Commit: 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Date: 2023-01-09T16:59:02.252Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No
VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.71GB (1.26GB free)

Process Argv
--crash-reporter-id 1c832343-8e5c-4512-b4ae-98da1af45902

Screen Reader
no

VM
0%

Extensions (87)

Extension
Author (truncated)
Version

vscode-sqlite
ale
0.14.1

1tbs-editorconfig-generator
Alp
0.1.2

aws-toolkit-vscode
ama
1.61.0

cypress-snippets
and
1.2.0

ng-template
Ang
15.1.0

aws-amplify-vscode
aws
0.0.4

ibmi-languages
bar
0.6.8

cobol
bit
9.1.15

vscode-rpgfree
Bri
0.0.23

jsonviewer
cci
1.3.2

npm-intellisense
chr
1.4.4

vscode-eslint
dba
2.2.6

vscode-axe-linter
deq
4.5.0

githistory
don
0.6.19

xml
Dot
2.5.1

gitlens
eam
13.2.0

EditorConfig
Edi
0.16.4

minisphere-vscode-tools
egg
0.1.0

prettier-vscode
esb
9.10.4

git-project-manager
fel
1.8.2

vscode-firefox-debug
fir
2.9.8

vscode-jest-runner
fir
0.4.60

docker-explorer
for
0.1.7

code-coverage-ibmi
hal
0.1.7

code-for-ibmi
hal
1.6.12

git-client-ibmi
hal
0.1.0

ibm-i-development-pack
hal
0.0.10

vscode-db2i
hal
0.2.9

vscode-displayfile
hal
0.0.10

vscode-ibmi-notebooks
hal
0.0.5

vscode-ibmi-walkthroughs
hal
0.2.4

vscode-rpgle
hal
0.17.2

vscode-dynamodb
har
0.0.1

vscode-clle
IBM
1.1.0

terraform-ssm
ita
0.3.6

create-migration
Iva
0.0.1

netdata
jar
1.0.6

angular-essentials
joh
13.0.0

Angular2
joh
13.0.0

vscode-peacock
joh
4.2.2

cypress-fixture-intellisense
Jos
1.2.0

dotnet-core-essentials
Kis
0.0.8

vscode-gutter-preview
kis
0.30.0

ef-core-snippets
Lew
1.0.0

lambda-snippets
log
1.0.0

aws-cli-configure
mar
0.3.0

vscode-scss
mrm
0.10.0

vscode-docker
ms-
1.23.3

csharp
ms-
1.25.2

remote-containers
ms-
0.266.1

remote-wsl
ms-
0.72.0

notepadplusplus-keybindings
ms-
1.0.7

powershell
ms-
2023.1.0

vsliveshare
ms-
1.0.5808

vsliveshare-audio
ms-
0.1.91

vsliveshare-pack
ms-
0.4.0

debugger-for-edge
msj
1.0.15

ibm-i-run-sql-from-acs
Nie
0.0.4

angular-console
nrw
17.28.2

vscode-boot-dev-pack
Piv
0.2.0

vscode-concourse
Piv
1.43.0

vscode-manifest-yaml
Piv
1.43.0

vscode-spring-boot
Piv
1.43.0

material-icon-theme
PKi
4.23.1

dynamodb-vscode-snippets
raf
0.0.6

vscode-thunder-client
ran
2.3.4

java
red
1.14.0

vscode-xml
red
0.23.0

vscode-scss-formatter
sib
2.4.4

sonarlint-vscode
Son
3.13.0

rewrap
stk
1.16.3

pdf
tom
1.2.2

errorlens
use
3.6.0

intellicode-api-usage-examples
Vis
0.2.6

vscodeintellicode
Vis
1.2.30

vscode-java-debug
vsc
0.47.0

vscode-java-dependency
vsc
0.21.1

vscode-java-pack
vsc
0.25.7

vscode-java-test
vsc
0.37.1

vscode-maven
vsc
0.40.4

vscode-spring-boot-dashboard
vsc
0.9.0

vscode-spring-initializr
vsc
0.11.2

vscode-aws-console
vsc
0.0.5

vscode-todo-highlight
way
1.0.5

targetframeworksswitcher
yam
1.0.3

vscode-games
yiw
0.0.4

project-tree
zhu
0.3.0

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
282f8724:30602487
f6dab269:30613381
a9j8j154:30646983
vscsbc:30628655

Can you uninstall and reinstall VS Code fully?

Hi! Would you have any tools to save config information. My setup has a number of extensions as well as NPM, Git, etc. Uninstall will be a multi-hour effort.

Thanks! I do not use the portable option.

No success -  uninstalled via system apps removal, restarted, and re-installed. Other options/ideas?

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

@NNPhilJordan can you also provide the full error output from code --verbose, thanks!

This sounds in the end like a setup problem on your machine and not something we can fix on our side. I suggest to consult IT support.

Disappointed in this resolution. May want to ensure your product is more solid at release. 3rd time I am experiencing work-stopping install issues in last 9 months.

@NNPhilJordan can you list the contents of the directory C:\Users\pjordan\AppData\LocaI\Programs\Microsoft VS Code\resources\app\out\

Hi! The out directory does not exist in ...\app. This has been the recurring problem - the resources are not there.

/cc @joaomoreno seems like an updater issue

A colleague and I reviewed the setup. Since there were prior versions of VSCode still installed, I removed those versions from apps, corrected the link to point to this 'system' version of the code, and I am no longer getting this error. Hope this helps in the future: Add  a reminder to install instructions to remove prior versions after new install and before using newly code. Also verify Startup or shortcuts used point to new code.

Since there were prior versions of VSCode still installed, I removed those versions from apps, corrected the link to point to this 'system' version of the code

Can you expand a bit more on this setup flow, what links did you correct ? Also, are you manually updating VSCode given this description.

From the short cut created...
Target was: C:\users\pjordan\AppData\local\Programs\Microsoft VS Code\Code.exe
Target is: "C:\Program Files\Microsoft VS Code\Code.exe"

IIUC, your setup is that you have user installation of VSCode but have created symlinks at the Program Files location so that it could shared with other users on the system ? This is not a setup our updater can support, you should use system installation for these scenarios https://code.visualstudio.com/#alt-downloads

Understood - original install was 'single user'. When I found that 1.70.x would not remind me of Updates found a reminder in Stack Overflow that suggested the 'system install'. Did not realize only one instance of VSCode could be on system at a time.  That is the solution to this issue - one instance of VSCode at a time. Lesson Learned back up all the settings before doing these installs.


KV-cache for Deepmind's speculative sampling

Hi, I noticed your implementations on speculative sampling implements KV-cache on Google's version, but not on Deepmind's version.
I was curious if you found a limitation with enabling KV-cache with Deepmind's version?

I found no limitations on deepmind's version. I did not implement that just for convenience.


Opt-out of auto-update

https://github.com/actions/runner/issues/246#issuecomment-615293718

Fixed by #10


Load the project roots from a configuration file

Configuration should be loaded form the XDG config directory, maybe as a YAML/TOML file for now so that we can add more complex data to each entry if needed.

libxdg-basedir provide basic support for XDG specification, but no more. We can probably benefit from relying on glib-2.0 which can manipulate path, configuration files, and so on.


Don't embed SDWebImage.framework in SDWebImageSwiftUI.framework

Solves https://github.com/SDWebImage/SDWebImageSwiftUI/issues/96

Good catch.
But you only change the SDWebImageSwiftUI iOS framework target. There are 4 targets totally. The diff should looks like this:

@jonkan Do I need to create another PR ? Or you fix it and commit again ?
I'll wait for reply until tomorrow, or I'll fix it by another PR.

Ah sorry, forgot them. I'll fix.

Fixed and released with SDWebImageSwiftUI v1.3.1. Thanks !


GELF timestamp should include milliseconds

The internal timestamp in Graylog 0.9.6 appears to be
seconds[.thousandths of a second] format, in contrast to the GELF spec
@ [1] which states that the timestamp field is in microseconds (Graylog
is only off by 6 orders of magnitude :)).
Changed setTimestamp to setJavaTimestamp to be consistent with the
constructor, which takes a java timestamp. The internal GELF timestamp
cannot be set from outside the class.
The change here works with Graylog 0.9.6 and correctly interprets the date
value with milliseconds precision.
[1] https://github.com/Graylog2/graylog2-docs/wiki/GELF

Also see: http://jira.graylog2.org/browse/WEBINTERFACE-234

+1
It should be a double, ie.:
	this.timestamp = System.currentTimeMillis()/1000.0;


MAINT: use np.float64_t instead of np.float_t in cKDTree

Fixes floating point precision error carried over from scikit-learn (incorrectly used float instead of double).
Also removes a redundant check for Python exceptions which cannot be raised from the partial sort function.

For SciPy master this is taken care of in PR #4890.

@sturlamolden it looks to me like gh-4890 will take a while longer. How about we merge this and then push it to master as well? I'm not a fan of having changes in a maintenance branch that aren't in master, that increases the change of a regression in the next release.

Just push to master as well, it does no harm to #4890 :)
#4890 is still WIP, but I hope it will be ready for 0.17.x.

And a question on the content: float_t is the same as npy_double (see https://github.com/cython/cython/blob/master/Cython/Includes/numpy/init.pxd#L760), so this isn't actually a bug right?

Allright, so it refers to a Python float which internally is a C double. I still think we should merge this for clarity, but as MAINT instead of BUG,

I agree with merging it. The int -> void change also makes sense. I'd rather keep it out of 0.16.x though - at this point I only want to merge critical bug fixes there.

Yes, since it is not a bug we can keep it out of 0.16.

Okay, rebased and merged into master in 357a1a0. Thanks @sturlamolden


Don't render navigation items for disabled content

Anything with enabled: false should be ignored when building navigation contexts.


Maximum Recursion Depth when field name matches type name

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
When defining an optional field with the name that matches the type name it returns an infinite recursion error.
RecursionError: maximum recursion depth exceeded in __instancecheck__
It doesn't seem to happen if the field isn't optional or the field name doesn't match the type name.
Example Code
from pydantic import BaseModel, Field

class FruitEnum(str, Enum):
    pear = 'pear'
    banana = 'banana'

class CookingModel(BaseModel):
    FruitEnum: Optional[FruitEnum] = Field(default=None)

Python, Pydantic & OS Version
pydantic version: 2.4.2
        pydantic-core version: 2.10.1
          pydantic-core build: profile=release pgo=false
                 install path: ./.venv/lib/python3.11/site-packages/pydantic
               python version: 3.11.2 (main, Mar  7 2023, 15:58:38) [Clang 14.0.0 (clang-14<IP_ADDRESS>)]
                     platform: macOS-12.7-arm64-arm-64bit
             related packages: typing_extensions-4.8.0 email-validator-2.1.0.post1

@jasongilman,
Thanks for reporting. This is a duplicate of this issue: https://github.com/pydantic/pydantic/issues/7327.
I'm going to close for tracking purposes, but feel free to continue discussion on that other issue 👍


fix flaky test

It's better to use a FrameLocator rather than a Frame in playwright, as a Frame can be invalidated by a navigation action. Fixes a sometimes-flaky test by using an appropriate FrameLocator, instead of a Frame, to target the Cody sidebar.
Test plan
Test-only change.

The test here still seems to be flaky, I saw it failing three times in my PR here https://github.com/sourcegraph/cody/pull/4591#issuecomment-2174170405

Same here @olafurpg — up to retry number 11 on this test in #4584: https://github.com/sourcegraph/cody/actions/runs/9556626326/job/26349471607 — strangely there's no artifact upload happening either.


vsock: Add socks which require a credit update to the rx_queue

even if they don't need to be polled. Otherwise a socket which e.g. has
"local_shutdown & SHUTDOWN_TX" won't ever send a credit update and so guest TX
will stall.
Signed-off-by: Ian Campbell<EMAIL_ADDRESS>Plus a fixup to debug mode.

I'm not very familiar with the vsock code, but the changes seem to match your description. And the description seems to explain the issue we were seeing. So LGTM


Cleanup historic vxlan tracking mistakes.

We were cleaning up the wrong etcd path. Additionally, the cluster
cleanup never attempted to find leaked vxlans. Correct that.

This one will deserve a backport too.

Backport is in https://github.com/shakenfist/shakenfist/pull/1235


Why does this library exist?

react-leaflet-markercluster already has widespread adoption and an active repository that includes a 3.0.0-rc1 release for react-leaflet v3 support.
Why not modify the existing library to include TypeScript support and create a pull request?

@MasterEric The existing library contains some issues like performance problems etc. Because of that, I've thought it's was inactive. I'm planning to create another library for react-leaflet. This repository is a preparation for that library.

Okay, that makes sense to me.


[DO NOT MERGE] Auto PR to update dependencies of pilot

This PR will be merged automatically once checks are successful.

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-e2e-smoketest.sh
bc920a9ec24a3f5d69de34f6ad7cad07b0aca7fd
link
/test pilot-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


fix custom features/analyses loader

Overview

We allow custom_features and custom_analyses to be defined for each system. This information is provided as a dict and it may come from the dataset or the system output file provided by the user. In some cases, it is not deserialized so there is a type mismatch. This PR fixes the issue. Please see #596 for details.
Details

References

closes #596

Blocked by

NA

Test is failing for some reason.

Thanks, @odashi! I fixed the tests.
A couple of pointers for what I changed:

Processor.process() takes deserialized custom_features and custom_analyses (according to the README and the integration tests) so the deserialize logic in Processor._custom_analyses() isn't necessary. That's why I removed it.
MachineTranslationTest.test_custom_features() was failing because dataclasses.asdict() serializes the two fields to dict but, as I mentioned above, Processor.process() expects deserialized objects. I am not sure which fields are actually being used by the processor so I followed the current implementation and included all the fields in FileLoaderMetadata when creating metadata. When #575 is implemented, this code probably needs to be updated.

Yeah, It looks the original code was weird, because {de}serialization is the IO feature and shouldn't be happened in any inner processes (Processor here). The change looks good.
Also, in general we shouldn't use dataclasses.asdict due to its too generic behavior: it expands all nested dataclasses in the object, that possibly brings several breakage into the code.


Go to top and chatbot buttons overlapping

Describe the bug
The Go to top button and the chatbot button, there are overlapping and we can't see the chatbot is there due to Go to top button.
Expected behavior
The Go to top button should be in left bottom instead of right bottom.

Hey, @Priyaaa1 let me handle this issue as I was the one who implemented the Go to Top button, Please assign this issue to me under GSSOC'24.
and yeah, here is the feature solution:


Using vitest with jsdom causes an infinite loop in atob

Describe the bug
Note: this is not a duplicate.
Issue #4602 reported the same issue before. It was closed an locked, but I can still reproduce it.
The issue was previously fixed with an upgrade to JSDom 23.x, but it still happens with JSDom 24. Either is a regression or the test coverage does not run with jsdom@24
Related JSDom issue
Reproduction
// index.test.ts
import { describe, expect, it } from "vitest";

describe("atob recursion", () => {
  it("should convert a base64 string", () => {
    expect(atob("SGVsbG8=")).toBe("Hello");
  });
});

npm i jsdom@24 <EMAIL_ADDRESS>vitest run --environment jsdom --single-thread --dir .

System Info
System:
    OS: macOS 14.4
    CPU: (10) arm64 Apple M1 Pro
    Memory: 1.93 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.12.0 - [redacted]/node
    npm: 8.19.1 - [redacted]/npm
  Browsers:
    Chrome: 122.0.6261.112
    Safari: 17.4

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

The fix is in 1.0.0.


Symphony fails to show an ERROR when page can not be written

If you create a new page and Symphony can not write to the "pages" folder (because of permissions), there will be no error upon saving the page. Instead there's the usual success message:
Page created just now. Create another? View all Pages

The apge won't work, of course.
XSLTProcessor::importStylesheet(): I/O warning : failed to load external entity "/var/www/maschine/workspace/pages/home.xsl"
XSLTProcessor::importStylesheet(): compilation error: file /var/www/maschine/ line 3 element import
XSLTProcessor::importStylesheet(): xsl:import : unable to load /var/www/maschine/workspace/pages/home.xsl
XSLTProcessor::transformToXml(): No stylesheet associated to this object

@michael-e Can you provide a little more detail on how you've reproduced this?
ie. Was this a parent/child page? Was this a new page/updated? Did the initial form submit return an error?
I've tried to reproduce by chmoding my PAGES folder to 222 and then creating a page, I however get the correct 'Page could not be written to disk. Please check permissions on /workspace/pages.' message.

No, it was a vanilla 2.2.3 installation, but it already had some extensions added to it. It was the first page to be created (that's why I still had wrong permissions for the pages folder).
To replicate this, I will create another plain vanilla install (without additional extensions, this time using 2.2.4 beta, which is probably more significant).

I actually think it may be related to this commit I just pushed, although it's on the integration branch, not 2.2.x

No, it happens no matter if I cherry-pick that commit or not. (Actually I checked out 2.2.3 from the master branch, so it was not included. Just to be sure that I understood right I cherry-picked that commit and tested it.)
I can replicate this issue on a vanilla install on my localhost (OS X), so it seems server-independent and unrelated to third-party extensions.

Quite strange. Are you able to create events/datasources without issue? (Just trying to figure out where this is breaking down, if it's in General::writeFile or somewhere else.

In the case of events, it works as advertised:

Failed to write Event to /Users/me/Sites/dev/some/path/workspace/events. Please check permissions.

Same for datasources. So I don't think that the problem is in the General class.

Yep, either that or integration (although we're about ~30 commits ahead in integration)

I'll test it soon (i.e. in one or two hours).

Much appreciated :)

I again tested this using beta1. Symphony handles the situation perfectly:

Page Template could not be written to disk. Please check permissions on /workspace/pages.

Consider things Dunn done.


Dashboard column sort has no effect

Component view, default load:

Component view, after clicking component ref sort

I am experiencing the same issue in the vulnerability view

Notes:
pressing the button once seems to send a request to the back end, or the loading circle comes up at least.
If I try to press the selected column a second time, nothing happens (no loading circle)
The desired behaviour for the sort button should be to be able to press the sort button again to change ascending/descending order

TO DO: investigate if this is a back end or front end error


Replace/rewrite InMemory adapter

With #18 we removed all usages of the InMemory adapter.
Either remove it altogether or rewrite it.

Any explanation why this got removed? I have some gauges that I don't really need to store in redis/apc, InMemory would be just fine for the job. I just need the RenderTextFormat, which I can't seem to use without a valid redis or apc adapter.

Ok I seem to have just implemented my ReactHTTP server with this package and only just realised that there is no stats because of no code in the in memory adaptor. Any idea on getting this in?

I have a pull request that implements the in memory adapter, but I haven't received any feedback on it for a while now.
You can use my fork until we get some comment on the PR

Will be fixed by merging #36.

Done.


[dv regr tool] Updates to support LSF

Update to move all tool sources to scratch area before build/run
Added necessary build opts that are required for running VCS on Google
machines
Fixed tool error thrown during the reporting stage when the when build itself fails

VCS no longer works locally on Google machines. With these fixes, VCS can either be deployed on docker or on the LSF.
To run with docker, additional installation steps are required. The legacy make flow for DV only works with docker, it does not work with LSF.
GOOGLE ONLY

# With dvsim script
# using LSF
util/dvsim.py <path-to-sim-cfg-hjson> -i [stuff-to-run] --job-prefix "bsub -P opentitan -I"
# using docker
util/dvsim.py <path-to-sim-cfg-hjson> -i [stuff-to-run] --job-prefix "runlocakdocker stty -nl &&"
$ cd hw/ip/<ip>/dv

# With make flow
# using docker
$ make [options] JOB_OPTS="runlocaldocker"

Signed-off-by: Srikrishna Iyer<EMAIL_ADDRESS>

@rasmus-madsen / @tunghoang290780
I'd appreciate if you could pull this PR and try running a sim with VCS. Goal is to ensure these changes do not affect how sims are run on WDC machines. Just to clarify, the --job-prefix switch indicated in my first comment only applies to Google - you'd continue to run with 'nc'.

Seems like a small typo here: locak -> local
"runlocaldocker stty -nl &&"

@rasmus-madsen / @tunghoang290780
I'd appreciate if you could pull this PR and try running a sim with VCS. Goal is to ensure these changes do not affect how sims are run on WDC machines. Just to clarify, the --job-prefix switch indicated in my first comment only applies to Google - you'd continue to run with 'nc'.

I get an error:
Attribute "tool_srcs" not found for default
command:
../../../../util/dvsim.py -i V1 -s xcelium --map-full-testplan -v n aes_sim_cfg.hjson --job-prefix "nc run -C ncsim_interactive -Il" --verbose

ault
command:
../../../../util/dvsim.py -i V1 -s xcelium --map-full-testplan -v n aes_sim_cfg.hjson --job-prefix "nc run -C ncsim_interactive -Il" --verbose

I just pushed a fix for this. Please try again now. Thanks!


Added option to add configmaps and secrets to jaeger  using helm.

Hello,  In our use case we need to add  custom environment variables and secret variables (username/password) to our jaeger all-in-one inside Istio helm installation but the current char template does not allow the possibility of adding those. So I made the changes to let the user add ( if they want, default is disabled) configmap resource or secrets resources to the jaeger deployment.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ijsnellf
If they are not already assigned, you can assign the PR to them by writing /assign @ijsnellf in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @Stocco. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi @Stocco wanted to see whether you had any thoughts/comments on #9508 for your use case. Aim would be to move more of the configuration aspects to the upstream jaeger-operator - so we need to make sure if would address user's requirements if we go this route.

I signed it!


Remove Cargo.lock

Per https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
libraries shouldn't have committed lock files

Current dependencies on/for this PR:

main

PR #252   👈

This comment was auto-generated by Graphite.

Codecov Report

Merging #252 (605cfe8) into main (45a63dd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #252   +/-   ##
=======================================
  Coverage   89.90%   89.90%
=======================================
  Files          43       43
  Lines        3634     3634
=======================================
  Hits         3267     3267
  Misses        367      367

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@jcape in #251 I noticed you were marked as the code owner, partly because I forgot to add the sgx-tools dir to the CODEOWNERS file, but also because I think the lock is getting captured in the default glob.
per https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners, we could add an entry in the CODEOWNERS file with no owners
Cargo.lock

However from previous discussions we said that lock files should only be present for binaries, which this repo currently doesn't have.
We may wish to leave the lock file with anticipation of binaries for sdk-tools, but that feels like YAGNI and we may change our minds.

@varsha888 I bumped you for another review since this conflicted with changes that made it into main and this repo has "New changes require approval from someone other than author" turned on.


CPU/GPU acceleration

Take advantage of multi threading for better compute times

Working on using accelerate the vector operations of the structure computations. Will figure out if this will also work for parallelizing the graphics operations.

Well getting all the libraries installed has been much more of a pain than expected. Currently trying to figure out how to get stack and docker to play nice together

I'm going to give up on this for now, I cant get things to build


React peer dependency

I would like to use this library in an app which requires react 16.3 or later.
Would it be possible to make react and react-dom as peer dependencies?
Thanks!

Yes, you can use react and react-dom separately in your react app, I write several demo, in the hello world demo links, I use react and react-dom as peer dependencies.  In this js file, import react and react-dom separately.


12 add ceiling and floor functions

Please review and provide me the feedback.

The version needs to be updated.


pull request for e2e test at 11/07/2016 04:26:13

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Issue/2631 configuration fields

Description
closes #2631
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Code is clear and sufficiently documented
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Looks good, a small remark:  To me, the Reset button looks like it's disabled, while it isn't. This is the patternfly default, I know, so if you have an idea to make it more obvious it's great, if not it can stay like this.

I have turned them into actual buttons. This is even more the patternfly standard and it works better.

Processing this pull request

Merged into branches master, iso5 in 2f8ee6beb71b458eb245fdda9b6032a4d72bea66


Automatically use current year for license

From @tcojean suggestion, this now uses the current year for the license. The documentation of reuse is not helpful here, since it doesn't clearly describe that it will use the current year if the --year option is not given.

This also means that the updates to the license will be staggered (i.e. the year in a file is the year it changed last) which I'm totally fine with, but we should note it.

@upsj we can still update all files yearly. With this change we just don't need to update the pre-commit config each year.

I know, I'm just not sure if this is necessary, since the date is supposed to describe when the code was written, so it's fine to leave it unchanged on old files. No strong opinion on either solution though.


Investigate memfs to replace filesystem writing

Investigate using the following package in place of any fs.writeFile (etc.) for non-logging related activity
https://www.npmjs.com/package/memfs
The goal would be to let the app be run without writing to the filesystem itself

May not be able to completely replace the fs writeFIle output as I want an option to output the results locally if the user chooses to. However, still may be worth investigating memfs to see whether it could be used as a cache somehow

Cannot currently think of a way this would be advantageous over simply storing the returned objects into a class/variable


Camera Installations

We need to determine if the camera installation from Johnson Controls at the upper school campus is actually completed from the original request or not. There is some confusion on whether the two cameras on the 2nd floor were add-ons after the fact, or in the original request.
We still have leverage as we haven't paid the bill yet, so now is the time to figure this out before it's too late.

Today, I've requested from Paul an appointment or ETA for next week.


Default CARP allow rule

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
We noticed that the OPNSense has a default rule allowing CARP traffic from any to any, and it is not configurable from the GUI:
pass log quick proto carp all keep state label
The rules come from:
https://github.com/pfsense/pfsense/commit/62010384be01b9a38dca527805164af9cc48adfe
It seems that this rule allows IP packets to forward if the IP protocol header is set to 112 (CARP/VRRP) even if the CARP is not in use.
So when a user thinks that the traffic would be totally blocked, this is not the case.
To Reproduce
Craft an IP packet with IP Header field set to 112 (CARP/VRRP) with and it will be allowed by PF and depending on the destination address, forwarded.
Expected behavior
With default block all rules, the user would expect all traffic to be blocked.
Describe alternatives you considered
CARP is needed for failover cluster communication. The protocol seems to state that the destination address is a multicast address and TTL is 255, as the traffic should stay on local net only.
Would it be sufficient that the rule be defined by default so that the destination address is not any, but the multicast address <IP_ADDRESS> and IPv6 FF02::12 respectively. It seems that the CARP traffic would not need to go to unicast address in any case.
pass in quick inet proto carp from any to <IP_ADDRESS>
pass in quick inet6 proto carp from any to ff02::12
Also if it would be possible to match to the TTL 255 as well, it should be more in line with CARP protocol. But I couldn't find a way to do this with PF.
Also it might be worth considering the rule to be disabled completely where CARP is not used with interface.
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 21.7.7 (amd64, OpenSSL).

https://github.com/opnsense/core/commit/c5c1ed91210fe7665ba79e6542f9f2ab17f021e3 constrains destination addresses to those defined in rfc5798 (https://datatracker.ietf.org/doc/html/rfc5798)


Setup github org - generic CSL mods?

Regarding github org, I think we should consider setting up a generic one for CSL mods, not just something specific to TM:PE.
The possibility is that other mods could join under the banner, allowing other modders to more easily take over (or at least bugfix) if original author leaves the community. It would also aid discoverability of mods for any developer wanting to contribute.
Main potential issue I can currently think of is can each repo have it's own github pages, or is there only one pages per org? Also, I have no idea what other mod devs would think about the proposal.
Also, it would be nice if we could shrink the repo name from what it currently is Cities-Skylines-Traffic-Manager-President-Edition to just TMPE. Would make sharing links to the repo so much nicer: https://github.com/CSLMOD/TMPE for example, although not sure what would happen to existing forks, etc.

Makes little sense unless you have more candidate mods waiting.
CitiesSkylinesMods
CSMods
Some unrelated mod belonging to a TMPE brand is not bad either :)

Also, it would be nice if we could shrink the repo name from what it currently is Cities-Skylines-Traffic-Manager-President-Edition to just TMPE. Would make sharing links to the repo so much nicer: https://github.com/CSLMOD/TMPE for example, although not sure what would happen to existing forks,

According to github docs:

When you rename a repository, all existing information, with the exception of project site URLs, is automatically redirected to the new name

In addition to redirecting web traffic, all git clone, git fetch, or git push operations targeting the previous location will continue to function as if made on the new location. However, to reduce confusion, we strongly recommend updating any existing local clones to point to the new repository URL.

and also

Warning: If you create a new repository under your account in the future, do not reuse the original name of the renamed repository. If you do, redirects to the renamed repository will break.

About Github Pages:

There are three types of GitHub Pages sites: project, user, and organization

User and organization sites are always published from a repository named <user>.github.io or <organization>.github.io. Unless you're using a custom domain, user and organization sites are available at http(s)://<username>.github.io or http(s)://<organization>.github.io.

The source files for a project site are stored in the same repository as their project. Unless you're using a custom domain, project sites are available at http(s)://<user>.github.io/<repository> or http(s)://<organization>.github.io/<repository>.

looks good! let's try and get this setup for v11.2 (month or two from now?) allowing us to also do #659.

BTW, I like @kvakvs ideas for the org name in https://github.com/krzychu124/Cities-Skylines-Traffic-Manager-President-Edition/issues/673#issuecomment-583826595

Setting up an Organisation takes approx 5 minutes and old links and refs to the old address continue working. Ping @krzychu124 let's do this :)

OK, so org name CitiesSkylinesMods and repo TMPE, right? @aubergine10

@krzychu124 Yes :)

Do we need separate e-mail for org?

No, keep your own, i guess.

Repository transferred to organization, looks good 😃


git commit and scrolling issues in integrated terminal

VSCode Version: Code 1.8.1 (ee428b0eead68bf0fb99ab5fdc4439be227b6281, 2016-12-19T14:42:49.304Z)
OS Version: Darwin x64 16.0.0
Extensions:

If I have vi as default git commit editor and does a commit will the integrated terminal scroll to the top instead of staying at the bottom.
 Scroll down while sighing 😞

This whole area was redone in the latest Insiders so it should be fixed in the next version.
In the meantime I recommend replacing step 3 with cmd+end :smiley:


Wayland character callback registers on key release

The character callback event triggers on both key press and key release, this does not happen when using X11.

Good day @cenomla! Could you please also provide the distribution, desktop environment & window manager, in question? I'll try to reproduce the issues you mentioned, so we can debug what is wrong. Going to try reproducing this on Fedora 24 (GNOME and Mutter) since they can also run on Wayland, but it would be best to have your exact setup, since this could be exclusive to only a subset of setups.

I could reproduce using tests/events.c on Weston master (1.11.90 revision 0da12b8) on ArchLinux, and the issue comes from src/wl_init.c:297 being executed no matter which action it is.

Alright, I've also tested this on Fedora 24 Workstation with GNOME 3.20 with Mutter 3.20 using their experimental gnome-shell --wayland compositor. Just as @linkmauve, I can reproduce these issues.

I'm using ArchLinux with Gnome 3.20 and a wayland session. This only seems to happen when glfw is using the wayland platform. When I compile glfw using X11 and run it using xwayland this does not happen.

Hi, sorry for the delay, I just proposed a fix which I only tested on Weston against tests/events, please check against your compositor and application.

Looks fine to me. It'd read clearer if the code that does _glfwInputChar() in its own function and then do if (action == GLFW_PRESS) input_char(...);

I can confirm that this fix works.

jadahl, this is a good suggestion, it makes the code more obvious in what it does, I force-pushed this.

Looks good to me.


Create .gitignore for vignettes folder

One of the preparation steps for:

#33

This change is easy to revert (if needed), so I merge it.


Add grpc_endpoint_get_fd and grpc_transport_get_endpoint

grpc_transport_get_endpoint gets the endpoint used by the transport
grpc_endpoint_get_socket gets the socket (fd in posix, SOCKET in windows) used by the endpoint. It returns NULL if the endpoint does not have a socket.
Add a type GRPC_SOCKET, which is int in posix and SOCKET in windows.

What do we need grpc_endpoint_get_socket for?

These two methods can be used by a channel filter to retrieve information about socket options.

Test failures seem unrelated.


AWS SpotFleet support - very basic

I know this repo is in maintenance - this is here for other users that might want to pick this up. If this interests the maintainers of this repo, I'd be willing to invest some more time to make this mergeable (this was my first encounter with Go).

Problem: Basic aws spot instances cannot automatically (to my knowledge) use different availability zone, based on what spot pools are depleted.
Solution: Introduce basic support for AWS SpotFleet. This is a minimal implementation, that solves the problem for me, but anyone can use it as inspiration or directly.
I will not be supporting this fork. Use at your own risk. I will maintain the fork only for my own needs.
Compiling my fork:

setup the repo like the Contributing guide says
cd src/github.com/docker/machine
make sure you know how to compile the main repo, before continuing
git remote add fprochazka git@github.com:fprochazka/docker-machine.git
git fetch fprochazka
git checkout fp-allow-multiple-availability-zones
make build

I have build & tested this with

go version go1.12.4 linux/amd64
dep version devel (installed today)

Usage: basic
I'm using the docker-machine for my gitlab runners.

test in EC2 Console, that you're able to request and cancel SpotFleet (this should initialize the required role, if your account doesn't already have it)
find out your vpc-id and all the subnet-id's of availability zones, that you want to use.
find out your "IAM fleet role" (the EC2 SpotFleet dialog shows it to you)
profit

docker-machine create --driver amazonec2 \
      --amazonec2-access-key "AKIA" \
      --amazonec2-secret-key "secret" \
      --amazonec2-region "eu-central-1" \
      --amazonec2-vpc-id "vpc-abc123" \
      --amazonec2-subnet-id "subnet-abc1" \
      --amazonec2-subnet-id "subnet-abc2" \
      --amazonec2-subnet-id "subnet-abc3" \
      --amazonec2-instance-type "t3.small" \
      --amazonec2-tags "Name,Gitlab CI Runner,user:Application,Gitlab,user:Stack,production,gitlab,true,gitlab-runner-autoscale,true" \
      --amazonec2-security-group "gitlab-runners" \
      --amazonec2-security-group-readonly \
      --amazonec2-request-spot-fleet \
      --amazonec2-iam-fleet-role "arn:aws:iam::123:role/aws-ec2-spot-fleet-tagging-role" \
      --amazonec2-use-private-address \
      spot-fleet-test

Usage: with gitlab-runner
  [runners.machine]
    IdleCount = 0
    IdleTime = 1800
    OffPeakIdleCount = 0
    OffPeakIdleTime = 0
    MachineDriver = "amazonec2"
    MachineName = "gitlab-runner-micro-%s"
    MachineOptions = [
      "amazonec2-access-key=AKIA",
      "amazonec2-secret-key=secret",
      "amazonec2-instance-type=t3.micro",
      "amazonec2-tags=Name,Gitlab CI Runner,user:Application,Gitlab,user:Stack,production,gitlab,true,gitlab-runner-autoscale,true",
      "amazonec2-region=eu-central-1",
      "amazonec2-vpc-id=vpc-abc123",
      "amazonec2-subnet-id=subnet-abc1",
      "amazonec2-subnet-id=subnet-abc2",
      "amazonec2-subnet-id=subnet-abc3",
      "amazonec2-use-private-address=true",
      "amazonec2-security-group=gitlab-runners",
      "amazonec2-security-group-readonly=true",
      "amazonec2-request-spot-fleet=true",
      "amazonec2-iam-fleet-role=arn:aws:iam::123:role/aws-ec2-spot-fleet-tagging-role"
    ]

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fp-allow-multiple-availability-zones" git@github.com:fprochazka/docker-machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842359068536
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Any progress on this? It'd be great to have Spot Fleet support!

@declension what kind of progress do you expect? :) The maintainers already said no more features.

The maintainers already said no more features.

Oh :disappointed:  Can't find any evidence of this on the home page or contributing guides though, and haven't followed.
Could this become a plugin or even fork, somehow?

@declension https://github.com/docker/machine/issues/4537
You actually can use my fork with this feature very easily, I've tried to describe it in the description. I'm using it on our production. But at your own risk ;-)

It might be useful to get into rancher/machine, which is used by Rancher (and seems to be getting more features than this...)

I tried this on gitlab-runner v12.9.1. but dose not work.

spot fleet request was created

But Docker machine provisioning fails on SSH connection

log text

Checking for jobs... received                       job=8766 repo_url=http://xxxx/xxxx.git runner=bdc652f8
Creating CA: /root/.docker/machine/certs/ca.pem     driver=amazonec2 name=runner-bdc652f8-runner-spottest-1592280235-612023db operation=create
Creating client certificate: /root/.docker/machine/certs/cert.pem  driver=amazonec2 name=runner-bdc652f8-runner-spottest-1592280235-612023db operation=create
Running pre-create checks...                        driver=amazonec2 name=runner-bdc652f8-runner-spottest-1592280235-612023db operation=create
Creating machine...                                 driver=amazonec2 name=runner-bdc652f8-runner-spottest-1592280235-612023db operation=create
(runner-bdc652f8-runner-spottest-1592280235-612023db) Launching instance...  driver=amazonec2 name=runner-bdc652f8-runner-spottest-1592280235-612023db operation=create
(runner-bdc652f8-runner-spottest-1592280235-612023db) Created spot fleet request sfr-a64862c1-dc27-44dc-a2ee-153cbb5e9598 ...  driver=amazonec2 name=runner-bdc652f8-runner-spottest-1592280235-612023db operation=create
WARNING: Failed to parse "X-GitLab-Trace-Update-Interval" header  error=strconv.Atoi: parsing "": invalid syntax header-value= job=8766 runner=bdc652f8

If you know anything, please

@kubokkey I have the same warnings as you, but my runners are working fine, sorry I have no idea how to fix this...
Although, I was considering forking the Gitlab-maintained docker-machine and adding my changes there, because last time I've tried rebasing this and updating dependencies my runners stopped working and I had to revert the binary.

If you came here because you'd like to find a relatively simple way to create an instance using spot fleet, check out custom docker-machine-driver-terraform and usage example for Gitlab runner. You can also check out this PR: https://github.com/npalm/terraform-aws-gitlab-runner/pull/249. :wink:


nqueen solution using recursion

I would like to add nqueen solution in recursion inside algorithms file.
This is a demanding algorithm these days & I would like to contribute it to the repository.

I would like to contribute to the above problem in java as I am a participant of GSSOC'21. Kindly assign this to me.


Strange effects when drawing geometry with LinearGradientBrush

Avalonia version : v0.10.6
Windows 10
var linearBrush = new LinearGradientBrush()
{
    StartPoint = new RelativePoint(0, 0, RelativeUnit.Relative),
    EndPoint = new RelativePoint(0, 1, RelativeUnit.Relative),
};
linearBrush.GradientStops.Add(new GradientStop(Colors.Red, 0));
linearBrush.GradientStops.Add(new GradientStop(Colors.Blue, 1));

drawingContext.DrawGeometry(linearBrush, null, Geometry.Parse($"M100,100 L 110,110 L 120, 90 L 130,150 L140,160 V 200 H 100 Z"));

As shown in the picture, the entire area is covered by blue.

Might be fixed by https://github.com/AvaloniaUI/Avalonia/pull/6066 which should be included in 0.10.7 (should be released in the next few days).


Neovim Python client is not installed

Python 2 provider

WARNING: No Python interpreter was found with the neovim module.  Using the first available for diagnostics.
WARNING: provider/pythonx: Could not load Python 2:
python2 not found in search path or not executable.
/usr/bin/python2.7 does not have the neovim module installed. See |provider-python|.
/usr/bin/python2.6 does not have the neovim module installed. See |provider-python|.
/usr/bin/python does not have the neovim module installed. See |provider-python|.
INFO: g:python_host_prog is not set.  Searching for python2.7 in the environment.
INFO: Executable: /usr/bin/python2.7
ERROR: Command error (4) /usr/bin/python2.7 -c import neovim; print(neovim.file): Traceback (most recent call last):  File "", line 1, in ImportError: No module named neovim
INFO: Python2 version: 2.7.10
INFO: python2.7-neovim version: unable to find nvim executable
ERROR: Neovim Python client is not installed.

SUGGESTIONS:

Error found was: unable to find nvim executable
Use the command $ pip2 install neovim

WARNING: Latest python2.7-neovim is NOT installed: 0.1.13

But problem still exist after run $ pip2 install neovim
Environment：
mac 10.11.6
brew install neovim
brew install python   （version is 2.7.10）
pip2 install neovim

Did you run sudo pip2 (that could be a problem on some versions of pip). Also try pip2 install --user ...


set_exception_visitor: remove the special case for wasi proc exit

while wasi proc exit is not a real trap, what the runtime does on it is mostly same as real traps. that is, kill the siblings threads and represent the exit/trap as the result of the "process" to the user api. there seems no reason to distinuguish it from real traps here.
note that:

the target thread either doesn't care the specific exception type or ignore wasi proc exit by themselves. (clear_wasi_proc_exit_exception)

clear_wasi_proc_exit_exception only clears local exception.

Things have changed since that PR and it seems that the distinction is not needed anymore. We have multiple tests that check exception propagation and the CI is green, so we should be confident to merge.


ENV are ignored

I need to define diffrent DB Ports because of host network.
After setting DB Ports with ENV and creating the container, they are silently ignored

I see no report of an issue. Feel free to reopen and try again.

Haha, this is your way of solving Issues? Nice try

If you would know me, you would know how much time I spend helping other with their issues... so please be careful with what you are writing here...
This here is no chat or forum. If you think you found an issue you have to provide as much information you could to give me a chance to reproduce it. If you are not willing or able to do so, please refer to ioBroker forum or ioBroker Discord channel.
As I wrote: Feel free to reopen this issue with "as much information you could to give".
Regards,
André


feat: #847 adjust forest client information card

Change Forest Client Information Card styles to new design
Forest Client Information Card styles for multiple values
Tag component now uses primevue badge

functionality for inputing multiple values is dependent on task #853
https://app.zenhub.com/workspaces/fsa-fingerprint-61f04f08304d3e001a4f2578/issues/gh/bcgov/nr-forests-access-management/853

Let's merge from the main branch, otherwise the input search doesn't look right, thanks!!

Hi Jota, two more things, when I verify Ian, the userID title shows in multiple lines:

And when search for a forest client not exists, this doesn't look right:

Hi Jota, two more things, when I verify Ian, the userID title shows in multiple lines:
And when search for a forest client not exists, this doesn't look right:

Hello! I believe the handling of non existing user is on task 853. I'll take a look to see if that's the case. Thanks!

Hi Jota, two more things, when I verify Ian, the userID title shows in multiple lines:
And when search for a forest client not exists, this doesn't look right:

Hello! I believe the handling of non existing user is on task 853. I'll take a look to see if that's the case. Thanks!

Hi @J0taFerreira
If Nick is already working on task #853 for showing error message, then if the input is invalid, as discussed in scrum, please hide the table (do not show empty row). Also, I think it shouldn't be hard to just have error icon (it's already there) to show up that when the searched number returns invalid result. Similar like this:

Please see if you can add it.
@MCatherine1994

Hi Jota, two more things, when I verify Ian, the userID title shows in multiple lines:
And when search for a forest client not exists, this doesn't look right:

Hello! I believe the handling of non existing user is on task 853. I'll take a look to see if that's the case. Thanks!

Hi @J0taFerreira If Nick is already working on task #853 for showing error message, then if the input is invalid, as discussed in scrum, please hide the table (do not show empty row). Also, I think it shouldn't be hard to just have error icon (it's already there) to show up that when the searched number returns invalid result. Similar like this:  Please see if you can add it. If you find it is difficult, please comment on this and we can leave it out (just not a good user experience). @MCatherine1994

Hello! I'll do the modification and see the icon in question.

Push some fixes in order to do prod release:

support not found case for user card
support not found case for forest client card
support inactive case for forest client card
get the latest style from the theme package (fix the button on focus effect, table pagination on focus effect, card and tag style, etc.)
fix the position for dashboard notification message


Check labels in function calls on self and external contracts

What was wrong?
As explained in #517, function calls on self or external contracts do not check the labels, allowing developers to apply any kind of label and in the worst case leave the user with the impression that they could use labels to call functions with the arguments ordered as they wish (which isn't the case).
How was it fixed?
Added checks in the analyzer and added tests.

Codecov Report

Merging #518 (12e03be) into master (b4d819f) will decrease coverage by 0.42%.
The diff coverage is 89.91%.

@@            Coverage Diff             @@
##           master     #518      +/-   ##
==========================================
- Coverage   87.93%   87.51%   -0.43%
==========================================
  Files          80       86       +6
  Lines        5306     5550     +244
==========================================
+ Hits         4666     4857     +191
- Misses        640      693      +53

Impacted Files
Coverage Δ

crates/abi/src/elements.rs
77.77% <ø> (-9.84%)
:arrow_down:

crates/common/src/diagnostics.rs
77.41% <ø> (+9.23%)
:arrow_up:

crates/driver/src/lib.rs
76.31% <ø> (+0.64%)
:arrow_up:

crates/lowering/src/context.rs
91.30% <ø> (-8.70%)
:arrow_down:

crates/lowering/src/lib.rs
100.00% <ø> (ø)

crates/lowering/src/mappers/contracts.rs
100.00% <ø> (ø)

crates/lowering/src/mappers/expressions.rs
100.00% <ø> (ø)

crates/lowering/src/mappers/functions.rs
98.49% <ø> (-0.68%)
:arrow_down:

crates/lowering/src/mappers/module.rs
84.44% <ø> (+1.11%)
:arrow_up:

crates/lowering/src/mappers/types.rs
100.00% <ø> (ø)

... and 88 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 bfeffe8...12e03be. Read the comment docs.

so that we could not report a type error in the case that the label is incorrect (or maybe just when the labels are in the incorrect order).

I think I don't follow.
This will only report label errors because the types are correct but mislabeled:
contract Foo:

    pub fn bar():
        self.baz(some=1, input=true)

    pub fn baz(input: u256, some: bool):
        pass

This will report label and type error because they are mislabled and in the wrong order:
contract Foo:

    pub fn bar():
        self.baz(some=true, input=1)

    pub fn baz(input: u256, some: bool):
        pass

Isn't that already what we want?
I'm going to merge this already but happy to follow up if I understand the intention of the proposed change. Or feel free to send a PR if it's less effort to explain it with the code directly :D


feat: add UI for laskugeneraattori

Description
Add form for sending invoices to laskugeneraattori. Invoices are sent to laskugeneraattori from the client with fetch. Errors from Rust backend are shown on the form
Closes #449
Before submitting the PR, please make sure you do the following

[x] If your PR is related to a previously discussed issue, please link to it here.
[x] Prefix your PR title with feat:, fix:, chore:, or docs:.
[x] This message body should clearly illustrate what problems it solves.
[x] Make sure the commit history is linear, up-to-date with main branch and does not contain any erroneous changes

Formatting and linting

[x] Format code with pnpm format and lint the project with pnpm lint

If we want to show this new laskugeneraattori URL today, I think should be possible to deploy as is. Even if the laskugeneraattori url is not set in the infra repo, the form submission should use laskutus.tietokilta.fi

If we want to show this new laskugeneraattori URL today, I think should be possible to deploy as is. Even if the laskugeneraattori url is not set in the infra repo, the form submission should use laskutus.tietokilta.fi

Let's do it 🚀

If we want to show this new laskugeneraattori URL today, I think should be possible to deploy as is. Even if the laskugeneraattori url is not set in the infra repo, the form submission should use laskutus.tietokilta.fi

Let's do it 🚀
Just make sure to also create the PR in infra repo so it's not forgotten

Created the PR. Seems like I am not authorized to merge this (even if approved), so you will have to merge

If we want to show this new laskugeneraattori URL today, I think should be possible to deploy as is. Even if the laskugeneraattori url is not set in the infra repo, the form submission should use laskutus.tietokilta.fi

Let's do it 🚀
Just make sure to also create the PR in infra repo so it's not forgotten

Created the PR. Seems like I am not authorized to merge this (even if approved), so you will have to merge

I am also not authorized to do anything in infra repo, it's @joonatanaatos territory  :sweat_smile:


Create a small rectangle using one point

I have one point, whats the best way to draw a small rectangle with that point being the center point.
Camera Point
const cameraState = {
    x: -13734998.52033772
    y: -41230419.91157826
    z: 26215185.399910662
    heading: 6.283185307179586
    pitch: -1.568415825780305
    roll: 0
}

const destination = new Cesium.Cartesian3(
      cameraState.x,
      cameraState.y,
      cameraState.z
);

https://stackoverflow.com/questions/60266737/cesium-show-a-rectangle-from-1-point

Please ask questions in the Cesium forum. We use GitHub for tracking bug reports and feature requests.


configure worker count

Signed-off-by: Frank Jogeleit<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 5 (60.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 93.514%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/config/load.go
1
3
33.33%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
4008

Relevant Lines:
4286

💛  - Coveralls