Sending '!important' as an argument results in a syntax error.

Having:
.box_shadow (@properties: 0) {
	-moz-box-shadow: @properties;
	-webkit-box-shadow: @properties;
	box-shadow: @properties;
}

Results on an error when trying to call it as:
.box_shadow(none !important);

This used to work on Less 1.2

+1 for this feature, or some equivalent.

Have you tried:
.box_shadow(~"none !important");
I've used this hack when doing comma-separated values sent to a single variable, like so:
.box_shadow(~"none, none");

Clever, and useful in some cases, but not where the variable isn't inserted at the end of a property declaration, such as with gradient-generating mixins.

Really? I can't think of a scenario where this syntax wouldn't work. Can you give an example?

Sure. Look, for example, at this (truncated) gradient generating mixin from Bootstrap:
    .horizontal (@startColor: #555, @endColor: #333) {
        background-color: @endColor;
        background-image: -webkit-gradient(linear, left top, right top, color-stop(0%, @startColor), color-stop(100%, @endColor));
    }
}```

Called as `#gradient > .horizontal(#F00, ~"#00F");` would work on background-color, but fail on background-image, since it would get inserted into the color-stop parenthetical.

It just now strikes me that you may have been simply trying to solve @marioestrada's problem, in which case good on yah. I was thinking more about the generic usefulness of this feature, and for gradient mixins specifically.

More generic solution added as #547. Then this could be called as .box-shadow(none) !important;.

I still don't really understand. The syntax can be used to pass in the value as is and avoid parsing errors with special values.
I don't see how your example fails on background-image.  In your example, these are (roughly) equivalent:
#gradient > .horizontal(#F00, ~"#00F");
#gradient > .horizontal(#F00, #00F);

The only difference seems to be that the color value in the second line is translated into a six-digit value, which I didn't know. But in your example, either way would be valid.

I know, sorry. My first example had a typo. I meant #gradient > .horizontal(#F00, ~"#00F !important");. That fails, right?

Oh, I see, it's not the parser that fails, it's how you've defined the variables.  Try this out:
#gradient2 {
    .horizontal (@startColor: #555, @endColor: #333, @important: ~"") {
        background-color: @endColor @important;
        background-image: -webkit-gradient(linear, left top, right top, color-stop(0%, @startColor), color-stop(100%, @endColor)) @important;
    }
}
.test {
#gradient2 > .horizontal(#F00, #00F, ~"!important");
}

Looks crazy, but seems to work. ^_^

Note that I agree with you that it is a bug that !important does seem to fail without the escaped quote syntax, but at least there's a temporary workaround.

Hehe, thanks for that solution, but that would get very messy if implemented across an entire library. It would be better if this was built into the parser. (I'm not saying @cloudhead has any obligation to, just saying it would be the Wrong Solution to leave optional room for !important sprinkled all over our libraries/codebases. Thanks anyway.

Hmmmm.... If your mixin had 14 lines of CSS, would you then expect every line to be appended with !important?
I rarely use the !important keyword, and generally instruct CSS newbies to avoid it for a few reasons, so I hadn't really thought about this scenario.

Response in #547: https://github.com/cloudhead/less.js/issues/547#issuecomment-3375126


Develop > Toolkit > Blockchain > Spawn Testing Chain

This PR:
-uses Zombienet material from PR #31 to create this page for the new IA

moves snippets & images, updates paths
moved code out to snippets
some formatting changes

Did some work on this PR to bring it inline with the review feedback and add back the missing Chopsticks pages. This PR now does the following:

Creates the following pages for Zombienet:

/develop/toolkit/blockchain/spawn-chains/zombienet/get-started.md
/develop/toolkit/blockchain/spawn-chains/zombienet/write-tests.md
/tutorials/blockchains/testing/spawn-basic-chain.md

Creates the following pages for Chopsticks:

/develop/toolkit/blockchain/fork-chains/chopsticks/get-started.md
/tutorials/blockchains/testing/fork-live-chains.md

Addresses the feedback from Kevin and Erin up to this point.
Moves images and code snippets and updates paths to match new pages
Audits all links, all work


”Vărădia”, ”Mercina” are listed in the drop-down menu

Description:
When user writes ”Vărădia”, ”Mercina” the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Vărădia"

Expected results
The location appears in the drop-down menu as "Sat Vărădia, CARAȘ-SEVERIN(Vărădia)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Mercina"

Expected results
The location appears in the drop-down menu as "Sat Mercina, CARAȘ-SEVERIN(Vărădia)".


Fixes #402

Fix bug where some offsets were expressed with a dash
between hours and minutes, and the format/2 function would
crash while formatting the offset

Summary of changes
I'll review the commits, so I mostly want to understand the "why" rather than the "what"
Checklist

[ ] New functions have typespecs, changed functions were updated
[ ] Same for documentation, including moduledocs
[ ] Tests were added or updated to cover changes
[ ] Commits were squashed into a single coherent commit

Coverage increased (+0.01%) to 67.999% when pulling c7aafc59065e87683d57770e087899e03d961d19 on socrata:master into c86a96af43cb0052249a4899d988aaa4f665982b on bitwalker:master.

Thanks!


fabric precision: 32 bit using far less memory than bf16

Hi, was playing with fabric precision and noticed that  bf16 uses quite a bit more memory than 32 (23.83Gi vs 13.37Gi).  It also trains a little bit slower (1.77 Hz vs 1.91 Hz)
Wondering if it is expected behavior, or something's wrong somewhere?
Config:
defaults:
  - dreamer_v3
  - override /algo: dreamer_v3_XL
  - override /env: atari
  - _self_

# Experiment
seed: 5

# Environment
env:
  num_envs: 6
  max_episode_steps: 27000
  id: MsPacmanNoFrameskip-v4
  input_buffer: 12
  use_input_buf_as_obs: True

# Checkpoint
checkpoint:
  every: 2000

# Buffer
buffer:
  size: 100000
  checkpoint: True

# Algorithm
algo:
  learning_starts: 1024
  total_steps: 1200000
  train_every: 12
  per_rank_batch_size: 8
  per_rank_sequence_length: 98
  mlp_keys:
    encoder: [actions_0, actions_1, actions_2, actions_3, actions_4, actions_5, actions_6, actions_7, actions_8, actions_9, actions_10, actions_11]

fabric:
  precision: bf16

Memory using precision: 32, Training at 1.91 Hz.

Memory using precision: bf16, Training at 1.77 Hz.

Hi @geranim0, we are looking into the precision because we sometimes escape from it. There's already an open issue (#236) and a branch where I've already made some changes. If you want you can contribute by looking at the branch 🤟 in the next few days I'll comment with all the activities I've done

Hi @geranim0, can you try out this branch and tell me if anything changes?

Hi @belerico ,
Thanks for that branch.
Here are the results of the tests (it doesn't change current behavior)
python sheeprl.py fabric.accelerator=gpu fabric.precision=bf16 exp=dreamer_v3_100k_ms_pacman yields 3.90/24
python sheeprl.py fabric.accelerator=gpu fabric.precision=32 exp=dreamer_v3_100k_ms_pacman yields 3.61/24
Also, this command using 16-true makes it crash
python sheeprl.py fabric.accelerator=gpu fabric.precision=16-true exp=dreamer_v3_100k_ms_pacman
Error executing job with overrides: ['fabric.accelerator=gpu', 'fabric.precision=16-true', 'exp=dreamer_v3_100k_ms_pacman']
Traceback (most recent call last):
  File "/home/sam/dev/sheeprl/sheeprl/cli.py", line 347, in run
    run_algorithm(cfg)
  File "/home/sam/dev/sheeprl/sheeprl/cli.py", line 186, in run_algorithm
    fabric.launch(reproducible(command), cfg, **kwargs)
  File "/home/sam/dev/sheeprl/.venv/lib/python3.10/site-packages/lightning/fabric/fabric.py", line 839, in launch
    return self._wrap_and_launch(function, self, *args, **kwargs)
  File "/home/sam/dev/sheeprl/.venv/lib/python3.10/site-packages/lightning/fabric/fabric.py", line 925, in _wrap_and_launch
    return to_run(*args, **kwargs)
  File "/home/sam/dev/sheeprl/.venv/lib/python3.10/site-packages/lightning/fabric/fabric.py", line 930, in _wrap_with_setup
    return to_run(*args, **kwargs)
  File "/home/sam/dev/sheeprl/sheeprl/cli.py", line 182, in wrapper
    return func(fabric, cfg, *args, **kwargs)
  File "/home/sam/dev/sheeprl/sheeprl/algos/dreamer_v3/dreamer_v3.py", line 712, in main
    train(
  File "/home/sam/dev/sheeprl/sheeprl/algos/dreamer_v3/dreamer_v3.py", line 243, in train
    imagined_prior, recurrent_state = world_model.rssm.imagination(imagined_prior, recurrent_state, actions)
  File "/home/sam/dev/sheeprl/sheeprl/algos/dreamer_v3/agent.py", line 461, in imagination
    _, imagined_prior = self._transition(recurrent_state)
  File "/home/sam/dev/sheeprl/sheeprl/algos/dreamer_v3/agent.py", line 442, in _transition
    return logits, compute_stochastic_state(
  File "/home/sam/dev/sheeprl/sheeprl/algos/dreamer_v2/utils.py", line 63, in compute_stochastic_state
    stochastic_state = dist.rsample() if sample else dist.mode
  File "/home/sam/dev/sheeprl/.venv/lib/python3.10/site-packages/torch/distributions/independent.py", line 104, in rsample
    return self.base_dist.rsample(sample_shape)
  File "/home/sam/dev/sheeprl/sheeprl/utils/distribution.py", line 397, in rsample
    samples = self.sample(sample_shape)
  File "/home/sam/dev/sheeprl/sheeprl/utils/distribution.py", line 365, in sample
    indices = self._categorical.sample(sample_shape)
  File "/home/sam/dev/sheeprl/.venv/lib/python3.10/site-packages/torch/distributions/categorical.py", line 132, in sample
    samples_2d = torch.multinomial(probs_2d, sample_shape.numel(), True).T
RuntimeError: probability tensor contains either `inf`, `nan` or element < 0

Hi @geranim0, the training with 16-true precision is ok to fail, in fact even PyTorch guys suggest to switch to bf16 or to the mixed precision. Regarding the increase in memory we are still investigating it.
Thank you for your patience

Hi @geranim0, in this branch I've added the possibility to print the CUDA memory allocation since the beginning of the training with torch.cuda.max_memory_allocated().
This is what I've obtained running the following command
python sheeprl.py \
fabric.accelerator=gpu \
exp=dreamer_v3_100k_ms_pacman \
algo.total_steps=1152

fabric.precision=bf16-mixed: 2.57GB
fabric.precision=bf16-true: 2.07GB
fabric.precision=16-mixed: 2.58GB
fabric.precision=16-true: nan in the categorical probs
fabric.precision=32: 5.24GB

This is my env collected with python -m torch.utils.collect_env:
Collecting environment information...
PyTorch version: 2.3.0.dev20240314+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Pop!_OS 22.04 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.11.8 (main, Feb 26 2024, 21:39:34) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-6.8.0-76060800daily20240311-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 4060 Laptop GPU
Nvidia driver version: 550.67
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      39 bits physical, 48 bits virtual
Byte Order:                         Little Endian
CPU(s):                             16
On-line CPU(s) list:                0-15
Vendor ID:                          GenuineIntel
Model name:                         13th Gen Intel(R) Core(TM) i5-13500H
CPU family:                         6
Model:                              186
Thread(s) per core:                 2
Core(s) per socket:                 12
Socket(s):                          1
Stepping:                           2
CPU max MHz:                        4700.0000
CPU min MHz:                        400.0000
BogoMIPS:                           6374.40
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 cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq rdpid movdiri movdir64b fsrm md_clear serialize arch_lbr ibt flush_l1d arch_capabilities
Virtualization:                     VT-x
L1d cache:                          448 KiB (12 instances)
L1i cache:                          640 KiB (12 instances)
L2 cache:                           9 MiB (6 instances)
L3 cache:                           18 MiB (1 instance)
NUMA node(s):                       1
NUMA node0 CPU(s):                  0-15
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] mypy==1.2.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] pytorch-lightning==2.2.1
[pip3] pytorch-triton==3.0.0+989adb9a29
[pip3] torch==2.3.0.dev20240314+cu121
[pip3] torchmetrics==1.3.2
[pip3] torchvision==0.18.0.dev20240314+cu121
[pip3] triton==2.2.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] pytorch-lightning         2.2.1                    pypi_0    pypi
[conda] pytorch-triton            3.0.0+989adb9a29          pypi_0    pypi
[conda] torch                     2.3.0.dev20240314+cu121          pypi_0    pypi
[conda] torchmetrics              1.3.2                    pypi_0    pypi
[conda] torchvision               0.18.0.dev20240314+cu121          pypi_0    pypi
[conda] triton                    2.2.0                    pypi_0    pypi

Can you also try out this branch and tell us your number?
Thank you

Current machine doesn't support all of them, but for 16-mixed I get 5.67 GB
With this config
Collecting environment information...
PyTorch version: 2.2.1+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.2 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.22.1
Libc version: glibc-2.35

Python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce GTX 1080
Nvidia driver version: 537.34
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      39 bits physical, 48 bits virtual
Byte Order:                         Little Endian
CPU(s):                             12
On-line CPU(s) list:                0-11
Vendor ID:                          GenuineIntel
Model name:                         Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
CPU family:                         6
Model:                              158
Thread(s) per core:                 2
Core(s) per socket:                 6
Socket(s):                          1
Stepping:                           10
BogoMIPS:                           7391.99
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology cpuid pni pclmulqdq vmx ssse3 fma cx16 pdcm pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi ept vpid ept_ad fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves md_clear flush_l1d arch_capabilities
Virtualization:                     VT-x
Hypervisor vendor:                  Microsoft
Virtualization type:                full
L1d cache:                          192 KiB (6 instances)
L1i cache:                          192 KiB (6 instances)
L2 cache:                           1.5 MiB (6 instances)
L3 cache:                           12 MiB (1 instance)
Vulnerability Gather data sampling: Unknown: Dependent on hypervisor status
Vulnerability Itlb multihit:        KVM: Mitigation: VMX disabled
Vulnerability L1tf:                 Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
Vulnerability Mds:                  Mitigation; Clear CPU buffers; SMT Host state unknown
Vulnerability Meltdown:             Mitigation; PTI
Vulnerability Mmio stale data:      Mitigation; Clear CPU buffers; SMT Host state unknown
Vulnerability Retbleed:             Mitigation; IBRS
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; IBRS, IBPB conditional, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:                Unknown: Dependent on hypervisor status
Vulnerability Tsx async abort:      Mitigation; Clear CPU buffers; SMT Host state unknown

Versions of relevant libraries:
[pip3] mypy==1.2.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] numpy-ringbuffer==0.2.2
[pip3] pytorch-lightning==2.2.0.post0
[pip3] torch==2.2.1
[pip3] torchmetrics==1.3.1
[pip3] triton==2.2.0
[conda] Could not collect

I can try on windows+wsl too! With fp32 how much memory consumes?

Sure, for fp32, getting 5.24 GB.
I doubt this is a WSL thing, previously tested on ubuntu native with default configs (pip install .) and had the same results

Hi @geranim0, I've tried also on windows+wsl and I've obtained the following:

fabric.precision=bf16-mixed: 2.57GB
fabric.precision=bf16-true: 2.08GB
fabric.precision=16-mixed: 2.57GB
fabric.precision=32: 5.24GB

with the following env:
/home/belerico/miniconda3/envs/sheeprl-p10/lib/python3.10/runpy.py:126: RuntimeWarning: 'torch.utils.collect_env' found in sys.modules after import of package 'torch.utils', but prior to execution of 'torch.utils.collect_env'; this may result in unpredictable behaviour
  warn(RuntimeWarning(msg))
Collecting environment information...
PyTorch version: 2.2.1+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.3 LTS (x86_64)
GCC version: Could not collect
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.10.13 (main, Sep 11 2023, 13:44:35) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 4060 Laptop GPU
Nvidia driver version: 551.61
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      39 bits physical, 48 bits virtual
Byte Order:                         Little Endian
CPU(s):                             16
On-line CPU(s) list:                0-15
Vendor ID:                          GenuineIntel
Model name:                         13th Gen Intel(R) Core(TM) i5-13500H
CPU family:                         6
Model:                              186
Thread(s) per core:                 2
Core(s) per socket:                 8
Socket(s):                          1
Stepping:                           2
BogoMIPS:                           6374.40
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq vmx ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves avx_vnni umip waitpkg gfni vaes vpclmulqdq rdpid movdiri movdir64b fsrm serialize flush_l1d arch_capabilities
Virtualization:                     VT-x
Hypervisor vendor:                  Microsoft
Virtualization type:                full
L1d cache:                          384 KiB (8 instances)
L1i cache:                          256 KiB (8 instances)
L2 cache:                           10 MiB (8 instances)
L3 cache:                           18 MiB (1 instance)
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Mitigation; Enhanced IBRS
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] mypy==1.2.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.3
[pip3] pytorch-lightning==2.2.0.post0
[pip3] torch==2.2.1
[pip3] torchmetrics==1.2.1
[pip3] triton==2.2.0
[conda] numpy                     1.26.3                   pypi_0    pypi
[conda] pytorch-lightning         2.2.0.post0              pypi_0    pypi
[conda] torch                     2.2.1                    pypi_0    pypi
[conda] torchmetrics              1.2.1                    pypi_0    pypi
[conda] triton                    2.2.0                    pypi_0    pypi

It could be the different NVIDIA driver version? Have you tried to update it?

Can you post here the output of your pip freeze please?


Error using PostCSS 8

Processing my css files with the newly released PostCSS 8, I get the error below:
TypeError: string is not iterable
    at Object.split (<omitted>\node_modules\postcss\lib\list.js:13:24)
    at Object.comma (<omitted>\node_modules\postcss\lib\list.js:51:17)
    at Rule.get selectors [as selectors] (<omitted>\node_modules\postcss\lib\rule.js:14:17)
    at isRuleWithinRule (<omitted>\node_modules\postcss-nesting\index.cjs.js:51:102)
    at <omitted>\node_modules\postcss-nesting\index.cjs.js:114:11
    at Array.forEach (<anonymous>)
    at walk (<omitted>\node_modules\postcss-nesting\index.cjs.js:112:23)
    at <omitted>\node_modules\postcss-nesting\index.cjs.js:125:9
    at Array.forEach (<anonymous>)
    at walk (<omitted>\node_modules\postcss-nesting\index.cjs.js:112:23)
    at LazyResult.runOnRoot (<omitted>\node_modules\postcss\lib\lazy-result.js:287:16)
    at LazyResult.runAsync (<omitted>\node_modules\postcss\lib\lazy-result.js:339:26)
    at async Promise.all (index 21)

I don't know if the new version is triggering a bug in postcss-nesting or if it simply needs to be made compatible. Let me know if you need an actual testcase (I'm just filing this quickly to make you aware).

I don't have time atm to do this, but the migration guide is here for anyone else: https://evilmartians.com/chronicles/postcss-8-plugin-migration

I no longer see this issue with PostCSS 8.0.9, so it looks like this was a bug in PostCSS itself. Of course the desire for migration still applies, but I'll close this as the first comment would be misleading.


[stable/coredns] Fix typo in values.yaml

Signed-off-by: Mateusz Gozdek<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Not sure if that make sense, as CI requires chart version bump...
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/lgtm


reselect + formValueSelector doesn't work

I'm trying to use formValueSelector together with reselect. Basically I need to verify if the value of one of the fields matches certain criteria, so I can show some other fields.
const formSelector = formValueSelector('myForm')
const myFieldTitle = (state) => formSelector(state, 'title')
const doSomethingWithTitleSelector = createSelector(myFieldTitle, (title) => {
    return doSomethingWithTitle(title)
})

function doSomethingWithTitle() { ... }

const Form = reduxForm({
    form: 'myForm',
})(TheComponent)

export default connect(
    state => ({
        titleWithSomethingDone: doSomethingWithTitleSelector(state)
    })
)(Form)

I don't see a reason why it wouldn't work. If I send the title on the mapStateToProps the component renders again normally.

My bad. react-select changed their api slightly and I was doing a wrong check. The example above should work.

Thanks for your issue pointed me in the right direction.


Fix the pytest error for async io

This PR fixes #558
The root cause is that POSIX and cuFile report different error messages for the same invalid operation which attempts to read from a write-only file. The unit test needs to take account of these different messages.

/merge


Consider switching to panic="abort"

At the moment of writing, we have panic = "unwind" requirement for all substrate binaries.
This is a historical artifact of us having a native runtime. After https://github.com/paritytech/substrate/issues/10579 and https://github.com/paritytech/substrate/pull/10872 we migth remove the native runtime.
In that case we might be able to lift the panic = "unwind" requirement. Binaries with panic = "abort" should be smaller and more performant, although it's not clear on how much.
Also, since we had this requirement for so long, there is a chance that we relied on this property somewhere either here or in polkadot. Before jumping the gun we should check whether there are any such places.

Hmm.... switching the whole binary to panic="abort" might be somewhat risky and might open us up to a nasty denial of service attack. It'd just take one out-of-bounds array access or a stay unwrap() to crash the whole node, and we need to remember that we do have, like, a thousand dependencies and our nodes are exposed to the network.
So I don't think this is necessarily a good idea to do globally due to the risks involved. That said, if we could maybe split a part of the executable into a separate process (e.g. run the WASM executor in a separate process?) which would be well isolated (especially from the network) and whose potential failure we could handle from the outside (e.g. quickly restart it in case of an abort) then I think it'd make sense to consider using panic="abort" over there.

Current panic handling looks like a bit of a mess currently. Main thread sets a custom panic handler here which aborts. Spawned tasks are split into "essential" that abort on panic, and "non-essentials" somewhat arbitrary. E.g. transaction pool is considered "essential" but libp2p networking and block proposer are not 🤔

Any panic outside of the runtime was already always an abort?

Any panic outside of the runtime was already always an abort?

I assumed so, but looking at the code this does not seem to be the case. Only "essential" tasks abort everything.


List structure

IN This PR I present the To-Do-List app structure :
Below are some of my implementations as well as going over the project requirements 🤝 .
Requirements
-build a basic page structure for the to-do-list app 🧑🔧
-build the structure using Webpack 🟦
-add the necessary logic 🧠 to add items to the list and to the Dom  📜
-add styling 🎨  based off the list structure given
Achievements
-build a basic page structure 🥼  for the to-do-list app 🎖
-build the structure using Webpack 🟦
-add items to their holder and display them on the Dom  📜
-add the necessary styling 🎨
N.B
things like local storage and full page functionality where not a requirement at this point of the project and I why there not implemented in this pull request
Conclusion
I would love to hear 👂  from you my CR in terms of what can be better implemented 👨💻  for the site thankyou!. And I look forward to hearing from you soon.  🙇

After my previous CodeReview I was asked to implement some changes.
Changes requested
-Add an event listener 👂  for Windows load to dynamically ⛓  load list section script 📜  contents.
Implementations
-Add the event listener to load list section dynamically 💹
Conclusion
I would love to here from you my CR on any further changes I can implement for this stage of the project 🙇

After my previous CodeReview I was asked to implement some changes.
Changes requested
-implement a static array of objects and load them as a list dynamically ⛓ in the script 📜  using windows load event listener 👂 .
Implementations
-Add the event listener to load the list section dynamically 💹
Conclusion
My first codeReviwer was not very specific on what had to be changed But the last reviewer made the changes clear and I have implemented them .I would love to hear from you my CR on any further changes I can implement for this stage of the project 🙇


rightTrim Directory Path

Fixes #322.
The test would still work if trimPath() is used.
I just tried to test if writeOutputFile can handle a leading slash in $file_path.

@stefanbauer Perhaps a regression test could be added, to make sure that no new non-build_* directory is created in the project's root after jigsaw build is ran?

That was my plan, care to add it and then I'll merge?

I'm unable to reproduce this issue in the test.
/**
 * @test
 */
public function no_non_build_directories_are_created_after_the_project_is_built()
{
    $this->app['events']->afterBuild(function ($jigsaw) {
        $jigsaw->writeOutputFile('new_directory/file.html', 'test');
    });

    $vfs = $this->setupSource();

    $original_directory_structure = scandir($vfs->url());

    $this->buildSite($vfs);

    $new_directory_structure = scandir($vfs->url());

    $this->assertEquals(array_merge($original_directory_structure, ['build']), $new_directory_structure);
}

While this tests does fail due to different order of items in the compared arrays (this is an issue with the test), no new non-build directory gets created in the virtual file system.

Quick update: I also tried to reproduce the problem with some tests, but when using vfsstream the issue doesn't show up.
I'm not familiar enough with the codebase, but maybe I can replace the code which builds the $directory_path and checks if the folder exists completely. 🤔
I keep you posted 🤙


Release v4.1.0 and deprecate the library

all stakeholders must approve this PR before merge:

[x] @lukesneeringer
[x] @nathanielmanistaatgoogle
[x] @dhermes
[x] @vchudnov-g
[x] @houglum
[ ] @svalentin

LGTM

LGTM

lgtm

LGTM.


invoke-handlers error on CCL/linux

A simple file like this:
(ql:quickload :trivial-signal)

(trivial-signal:signal-handler-bind ((2 (lambda (c)
					  (format t "hi!~%"))))
  (sleep 99))

If you try to Ctrl-c during the sleep, it throws this error:
^C-------- handler invoked in thread: listener -------
hierarchy: (((2 #<Anonymous Function #x30200161994F>)))hi!
> Error: received INT
>
> While executing: TRIVIAL-SIGNAL::INVOKE-HANDLERS, in process listener(1).
> Type :GO to continue, :POP to abort, :R for a list of available restarts.
> If continued: Skip evaluation of (ros:run '((:eval"(ros:quicklisp)")(:script "../test.lisp")(:quit ())))
> Type :? for other options.

By replacing 2 with "foo", I saw an interesting error at compile-time:
> Error: The value "foo" is not of the expected type SYMBOL.

So ccl apparently expects signo to be a symbol, not a number.
That said, it throws the same error when I tried using 'foo:
> Error: The value 'FOO is not of the expected type SYMBOL.

So I'm not sure what it's expecting.

So, three questions...

Why it throws an error, although I handled the signal? -> The behavior of signal-handler-bind is analogous to handler-bind. Therefore your code did not handle the signal, you declined the signal. To see this difference, please refer to the definition of handle and decline: You printed "hi" and returned from the lambda without a local exit, so you declined the signal. To handle the signal, you have to jump outside the handler via non-local exit such as tagbody+go or block+return-from or throw+catch combo.
The valid designator for signals are defined here: It should be a keyword or a number.
This case is interesting, what you saw is actually 'FOO not FOO, which means it is a cons (quote foo) that happened to be pretty-printed. This is confusing for the users and I believe it is a bug.

Thanks for the explanation! I was indeed missing things :)


Crash on simulator, any workaround?

Requirements:

[x] Review the documentation
[x] Search for existing issues in: ViroCommunity/viro
[x] Use the latest ViroReact release

Environment
Mac, iOS 17.2, iPhone 15 Pro simulator
"@reactvision/react-viro": "^2.41.6",
"react-native": "0.73.5",

Bare react native project, non-expo.
Description
Simulator crashes immediately on startup, even without using any viro-react features. I was looking through some previous issues where this is mentioned, but I don't think any of them were actually solved, just closed.
I don't need AR features on a simulator, but it would be nice to run e2e and develop features that are not related to AR on a sim. So, any workarounds? Real device works, of course, but we need simulator to at least not crash.
Trace snippet:
Termination Reason: DYLD 1 Library missing
Library not loaded: @rpath/GTMSessionFetcher.framework/GTMSessionFetcher
Referenced from: <5D09F0A1-93BE-31F2-B28B-565B1A89B535> /Users/me/Library/Developer/CoreSimulator/Devices/91AD94B5-3753-4246-AD68-2962FF689C49/data/Containers/Bundle/Application/5CB74D3C-B33B-45EA-ACEE-E1BD134056F1/Marketplace.app/Frameworks/ViroKit.framework/ViroKit
Reason: tried: '/Users/me/Library/Developer/CoreSimulator/Devices/91AD94B5-3753-4246-AD68-2962FF689C49/data/Containers/Bundle/Application/5CB74D3C-B33B-45EA-ACEE-E1BD134056F1/Marketplace.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file), '/Users/me/Library/Developer/CoreSimulator/Devices/91AD94B5-3753-4246-AD68-2962FF689C49/data/Containers/Bundle/Application/5CB74D3C-B33B-45EA-ACEE-E1BD134056F1/Marketplace.app/Frameworks/ViroKit.framework/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file), '/Users/me/Library/Developer/CoreSimulator/Devices/91AD94B5-3753-4246-AD68-2962FF689C49/data/Container
(terminated at launch; ignore backtrace)

you must run on a physical device, Apple Simulator and Android Emulator don´t acess ARCore (Android) and ARKit (iOS).

It's not an ideal solution but we solved it by adding this condition to the Podfile
if !ENV["EXCLUDE_VIRO"]     puts "adding VIRO.."     pod 'ViroReact', :path => '../node_modules/@reactvision/react-viro/ios'     pod 'ViroKit', :path => '../node_modules/@reactvision/react-viro/ios/dist/ViroRenderer/'   else     puts "removing VIRO.."   end
in package.json then someting like this
"prepare:simulator": "EXCLUDE_VIRO=true; yarn install"..

I solved this a bit hacky by adding a config in the environment variable and dynamically import Viro based on a config say from an environment variable.
In My ARScreen:
let Viro3DObject: any,
  ViroAmbientLight: any,
  ViroARPlaneSelector: any,
  ViroARScene: any,
  ViroARSceneNavigator: any,
  ViroMaterials: any,
  ViroTrackingStateConstants: any;

if (config.USE_VIRO) {
  Viro3DObject = require('@reactvision/react-viro').Viro3DObject;
  ViroAmbientLight = require('@reactvision/react-viro').ViroAmbientLight;
  ViroARPlaneSelector = require('@reactvision/react-viro').ViroARPlaneSelector;
  ViroARScene = require('@reactvision/react-viro').ViroARScene;
  ViroARSceneNavigator = require('@reactvision/react-viro').ViroARSceneNavigator;
  ViroMaterials = require('@reactvision/react-viro').ViroMaterials;
  ViroTrackingStateConstants = require('@reactvision/react-viro').ViroTrackingStateConstants;
}

export default function ArScreen({ route, navigation }: ArScreenProps) {

  if (!config.USE_VIRO) {
    return (
      <View style={styles.placeholderView}>
        <Text style={textStyles.h4}>AR is disabled in this build</Text>
      </View>
    );
  }

  return (
      <ViroARScene
        onTrackingUpdated={handleTrackingUpdated}
        onAnchorUpdated={(_anchor: any) => setAnchorFound(true)}
      >
        <ViroAmbientLight color={'#ffffff'} />
        <ViroARPlaneSelector>
          // other vino stuff
        </ViroARPlaneSelector>
      </ViroARScene>
    );
  };
//

Adding the USE_VIRO env to the scripts:
{
  "scripts": {
    "start:dev": "npx expo start --dev-client -c",
    "start:dev-simulator": "USE_VIRO=true npx expo start --dev-client -c",
    "build:ios-simulator": "USE_VIRO=false eas build --profile development-simulator --platform ios --local",
    "build:ios-dev": "USE_VIRO=true eas build --profile development --platform ios --local",
    "build:android-simulator": "USE_VIRO=false eas build --profile development --platform android --local",
    "build:android-dev": "USE_VIRO=true eas build --profile development --platform android --local",
  },
}


Scribble needs to disallow equality comparisons between reference types

Consider the following sample:
contract Foo {
    struct S {
        uint[] arr;
    }
    /// #if_succeeds a == b;
    function main(S memory a, S memory b) private {
    }
}

Scrible's type-checker will allow the expression a==b and transpile it into the following code:
...
    function main(S memory a, S memory b) private {
        _original_Foo_main(a, b);
        unchecked {
            if (!(a == b)) {
                emit AssertionFailed("0: ");
                assert(false);
            }
        }
    }
...

That code however doesn't compile since you can't compare pointers in Solidity. To fix this the scribble type-checker should be made more precise, to disallow equality comparison between reference types.

Fixed with #87


I want ssh tunnel support in SQLDatabaseChain

Feature request
Due to security reasons, it is not always possible to connect directly to the DB. I want SQLDatabaseChain to support ssh tunnel because I have to connect to a specific kind of stepping stone server before I can connect to the DB.
If there is already a way to accomplish this, I apologize.
Motivation
I want to use llm with all our own data to create an innovative experience, and SQLDatabaseChain makes that possible.
Your contribution
I can contribute with testing. I do not yet have a good understanding of langchain's source code structure and inner workings, so coding contributions would not be appropriate.

It might be interesting to include some args to support this in the SQLDatabase class, but doing this is relatively straightforward so I don't know if it really nesseciates adding complexity to the SQLDatabase class.
Per this SO answer it looks like you could use the sshtunnel library to use Python to port forward a ssh connection to your db server, and then just refer to localhost when you connect to the db.
from sshtunnel import SSHTunnelForwarder
from langchain import OpenAI, SQLDatabase, SQLDatabaseChain

server = SSHTunnelForwarder(
    ('<IP_ADDRESS>', 22),
    ssh_username="my_username",
    ssh_password="my_password",
    remote_bind_address=('<IP_ADDRESS>', 5432)
    )

postgres_user = "user"
postgres_pswd = "password"
db_name = "db"

server.start()
local_port = str(server.local_bind_port)

db = SQLDatabase.from_uri(f"postgresql://{postgres_user}:{postgres_pswd}@<IP_ADDRESS>:{local_port}/{db_name}')
llm = OpenAI(temperature=0, verbose=True)
db_chain = SQLDatabaseChain.from_llm(llm, db, verbose=True)


Track expense-Deleting track expense displays expensify message for a second & in LHN

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.63-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Go to https://staging.new.expensify.com/
Tap fab-- track expense
Enter an amount and tap next
Tap track expense
Tap on newly created expense
Tap on 3dots on top right and delete it

Expected Result:
While deleting track expense, expensify message must not be shown in Track expense page for a second or in LHN
Actual Result:
While deleting track expense expensify message is shown for a second and disappears. LHN also shows expensify message.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/6efba76e-5c58-42e7-a980-a535d189bc02

View all open jobs on GitHub

@stephanieelliott I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

We think this issue might be related to the #vip-vsb.

Production
https://github.com/Expensify/App/assets/115492554/9b3de85e-c02b-4c3f-ab0b-77eb2d32e0d0

I don't think this needs to be a deploy blocker since it's just a flicker of a message, everything else functions as intended. Adjusting labels.

@izarutskaya looking at the video, I'm not sure where the unintended behavior is (probably bc I am unclear what the Expensify message is) -- can you let me know the timestamps in the video where it is occurring?

Ah, I think this is referencing how we see the actionable whisper for a moment before it disappears. The time it shows until it is gone is pretty short so I think we can close this


Create an 'admin service' in PHP

Objective
Create an 'admin service' written in PHP for the web store.
The following features should be supported:

Authentication for 'admin users'
UI for CRUD operations on items in the product catalog.
API for CRUD operations on items in the product catalog.

Linking to the issue in the php repo: https://github.com/open-telemetry/opentelemetry-php/issues/658
@bobstrecansky should I assign the current issue owner to this as well?

Sounds good!

As discussed in the #otel-community-demo slack channel, we can also use Apache WebServer to host 'Admin Service' in PHP through mod_php. Apache instrumentation is already available to generate spans and traces.

@DebajitDas
Thank you.
However we most likely would prefer not to use Apache, as that's a bit outdated, or in fact any web-sever (Nginx,, Caddy, etc.) as a runtime, but a modern faster runtime as Swoole or Roadrunner.

Hey @tidal, @bobstrecansky, is there an update on this? We merged the rust service today, so PHP is the remaining outstanding language not present.

As discussed with @cartersocha I will create a PR with  basic service setup as a draft.
This service will feature roadrunner with OpenTelemetry middleware as an app server.
API Platform  will make the implementation of auth and API easy.
It also allows to generate an admin ui from the API.

@austinlparker can we have that ticket closed?
I believe we do not need an admin service anymore, as PHP was covered in the Quote Service.

Closing this!


Filter projects outside migrated group

Gitlab might return projects that don't belong to the source group. The
API doesn't seem to have an option to restrict listing projects from a
group and subgroups. To avoid this issue, we add a filter step and keep
only projects where the prefix matches the source group.
Signed-off-by: Francis Giraldeau<EMAIL_ADDRESS>

Interessting one that I haven't come accross yet. Did you find a bug report or anything related in the gitlab issue tracker or official documentation why these projects are returned?
And in which version of Gitlab does it occur? (Version Number, OnPrem/SaaS)

Interessting one that I haven't come accross yet. Did you find a bug report or anything related in the gitlab issue tracker or official documentation why these projects are returned?

I checked quickly and didn't find something relevant. I will check of another API attribute is causing that, such as with_shared or something https://docs.gitlab.com/ee/api/groups.html#list-a-groups-projects

And in which version of Gitlab does it occur? (Version Number, OnPrem/SaaS)

This occurs with 13.9 Community.


Zlib::BufError on comparing puma

If I run:
gem compare puma 5.6.2 5.6.4

I got:
Fetching puma-5.6.2.gem
Fetching puma-5.6.4.gem
NOTE: Gem::Specification#has_rdoc is deprecated with no replacement. It will be removed in Rubygems 4
Gem::Specification#has_rdoc called from /home/lobashov/.rvm/gems/ruby-3.0.3/gems/gem-compare-1.0.0/lib/rubygems/comparator/utils.rb:112.
NOTE: Gem::Specification#has_rdoc is deprecated with no replacement. It will be removed in Rubygems 4
Gem::Specification#has_rdoc called from /home/lobashov/.rvm/gems/ruby-3.0.3/gems/gem-compare-1.0.0/lib/rubygems/comparator/utils.rb:112.
ERROR:  While executing gem ... (Zlib::BufError)
    buffer error

But there is no such error on comparing other gems, like:
gem compare aws-partitions 1.570.0 1.571.0

Seems has something to do with puma gem

Seems something wrong with my system, sorry
Reason may be that leftovers of rvm is used while I'm on rbenv
After some tinkering with removal of rvm leftovers problem is not occur any more


Feature/add template for ontology definition update

We should also comment on definition updates in the ontology. They have an own tag [C] but no special template. Template [C] is for changes other than in oeo-files. Issue originated from here

@stap-m - I don't know who created the tag [C] without opening an issue first. In the CONTRIBUTING file it was listed that there was only A and B types of issues.

@stap-m - I don't know who created the tag [C] without opening an issue first. In the CONTRIBUTING file it was listed that there was only A and B types of issues.

Me neither. But I think it makes sense because it's an often used and very small special case of restructuring.


Make sure our unit tests are all run on travis

The glob used meant we only ran .py files two levels deep,
rather than one level deep. We un-nest the contentprovider
tests and simplify the glob

Superceeded by #512


Update to v0.15.0

Description of the change
Backlinking to purescript/purescript#4244
Migrates FFI to ES modules

Checklist:

[x] Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
[x] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation
[ ] Added a test for the contribution (if applicable)

Hi!
Is there going to be a new version number at some point? I seem to have this library as a transitive dependency somewhere.

The functions in this library have been migrated elsewhere (mostly numbers and integers) and this library is going to be deprecated.

I see. Well, I guess I'll have to wait for the upstream libraries to get updated then.


Crontab and Automessage multi instance

hello ,
i have a question i make 2 servers on my dedicated server but i need to make Automessage for eatch server's and but not the same for the 2 servers so can i make crontab's for one instance and a other crontab for my other server ?
And i want to set a config for autoupdate for each server how i can i do that ?
thanks a lot for ur helping :)
and thanks for ur amazing Script !

I use this to check for and update both servers every 2 hours:
00 */2 * * * /home/ark/bin/arkmanager update --safe --warn --saveworld --update-mods @all
But I'm not 100% sure that it works. I just recently setup the second server, and it often looks like it doesn't update.
This sends a chat message from the server ingame:
00 */4 * * * /home/ark/bin/arkmanager rconcmd 'ServerChat No Ark For Old Men: Arksanity.com [ORP]' @all
Although I haven't really tested this either. It works on the default server, I haven't been much on the new one to notice it yet.
Though, the directory above is where arkmanager is installed on my server, you may have to change that.

check the process tab watch it works but it works and overlaps which causes the issue this is what i have been dealing with and its annoying as hell. Checks update then somehow gets a horrible steam server for download and downloads everything then while in the process of updating time has gone by and it has started the update cronjob again which overlaps and causes strain

If you have & at the end of the command in your crontab, then you are bypassing cron's protection against this occurring - the cron daemon should not allow multiple instances of a single cron job to run simultaneously.
If you are removing the .arkupdate.lock file, then you are bypassing arkmanager's protection against this occurring.

One a sidenote for crontab, multi-instance and auto-update, the following is not working for me.
00 */2 * * * /home/ark/bin/arkmanager update --safe --warn --saveworld --update-mods @all
Perhaps someone can fill me in here, this will also be useful for @ReaperBe7062, but when that is run either via crontab or just command line, it doesn't stop both servers. It will start with the first server and if there is an update, it will countdown 15 minutes warning the players, saveworld, stop server, update, start server.
And then it starts to check for update for the second server. But these files have already been updated by the first server, so it won't update. Leaving the second server without getting updated... Even though the files are updated, the server isn't restarted so that the version number updates.
Am I doing this wrong? Is there some other way? I'd prefer to keep checking for updates automatically as often as possible, so that I can stop playing ARK and let the server run it's course. I run a nightly stop and saveworld of both servers so that I can get an offsite backup, so the second server will eventually be updated... still, I'd prefer it to auto-update every 2 hours like the other server.


Support Exoscale cloud controller manager

Exoscale now has a cloud controller manager for Kubernetes. We should make use of it to get better integration with the platform. It currently supports Service of typ LoadBalancer and may add more things in the future.

Future Block storage support in cloud provider would make this more worth it.

Future Block storage support in cloud provider would make this more worth it.


Added cipher to curl command

Curl commands were giving a "DH key too small" error and preventing progress. This fixes error.
This is, more or less, dealing with the same issue as the other PR I made, but I discovered it after making the previous PR because this is affecting a different Qwiklabs lab.
I'm not sure what will end up being the easiest/best solution, but while these PRs fix the Qwiklabs labs, I believe if the server used in chapter 2 were to have a DH key that worked with modern openssl then we wouldn't need either of my PR workarounds. (https://github.com/GoogleCloudPlatform/data-science-on-gcp/issues/93)

@mylenebiddle

You need a similar solution for the monthlyupdate/main.py. I am getting a cipher issue as well (trying to run the end of Chapter 2 code excercise).
urllib2.URLError: <urlopen error [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:727)>


doc: add how to enable JVM debugging for Kafka Connect

Closes #196.

Description

Test Steps

Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Nice! Actually had this PR ready locally, never pushed, and you beat me to it :D

Changed the sentence @embano1.


Copy updated geneinfo.db file to AWS gru backend deployment

This is dependent on https://github.com/iobio/iobio-gru-backend/issues/36.

Nevermind on being dependent on https://github.com/iobio/iobio-gru-backend/issues/36, I went ahead and deployed the new db.

@tonydisera can you review this? I guess in this case it basically means once you're confident it's working.

Yep.  It is working on both Utah Mosaic backend and AWS backend.  Thank you Anders!
Here's how it looks on production (SAM is supposed to be on chr X)

Here's how it looks on stage.gene.iobio:

Assuming previous testing is sufficient

Yes.   I made sure that this is working on stage.gene.iobio.io


[Request Feature]: Not working in React 19

Hope to have this amazing Datepicker compatable with React 19 soon :)
Or if this is a bug, please give me a solution to fix this Error.

Similar error for me, using nextjs 15.0.1

Actually just updating the react dependency works out of the box.

@carstenblt  you are absolutely correct! I thought I had upgraded to React 19 but it appears I did not.
For those coming here with the same problem, upgrading React to version rc (which ends up being 19) and installing fixed this problem for me.

@carstenblt you are absolutely correct! I thought I had upgraded to React 19 but it appears I did not.
For those coming here with the same problem, upgrading React to version rc (which ends up being 19) and installing fixed this problem for me.
@VichetN, give the upgrade a try to verify that fixed it for you. If so then closing this issue out would be ideal.

@austingdev How to upgrade by the way?
Upgrade React of our project?
should be like this?:
yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>Please give me an example

@carstenblt you are absolutely correct! I thought I had upgraded to React 19 but it appears I did not.
For those coming here with the same problem, upgrading React to version rc (which ends up being 19) and installing fixed this problem for me.
@VichetN, give the upgrade a try to verify that fixed it for you. If so then closing this issue out would be ideal.

@austingdev How to upgrade by the way?
Upgrade React of our Nextjs project? should be like this?: yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>Please give me an example

yes for the NextJS project. You can update the package.json libraries like so:
"react": "rc",
"react-dom": "rc",

@carstenblt you are absolutely correct! I thought I had upgraded to React 19 but it appears I did not.
For those coming here with the same problem, upgrading React to version rc (which ends up being 19) and installing fixed this problem for me.
@VichetN, give the upgrade a try to verify that fixed it for you. If so then closing this issue out would be ideal.

@austingdev How to upgrade by the way?
Upgrade React of our Nextjs project? should be like this?: yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>Please give me an example

yes for the NextJS project. You can update the package.json libraries like so:
"react": "rc",
"react-dom": "rc",

then run yarn

Thank you @austingdev

Whut, wait? You just changed the version from 19.0.0-rc-69d4b800-20241021 to rc and it worked? So maybe it works with a newer release of react?
I actually had to rebuilt react-tailwindcss-datepicker with react 19 and push it to npm.

Oh I might have had some kind of cacheing issue going on. I thought it was working but I nuked my dist folder and rebuilt and yea, even with rc it is still broken, same error as above.
Does that mean you have pushed a new version that should work with react@rc?

Oh I might have had some kind of cacheing issue going on. I thought it was working but I nuked my dist folder and rebuilt and yea, even with rc it is still broken, same error as above.
Does that mean you have pushed a new version that should work with react@rc?

Well yes, to @tarabao/react-tailwindcss-datepicker. If you trust that...

Why is this closed?  I do not consider a 3rd party fixing an issue an uploading to a different npm package a fix for the root issue...
Can we get a fix for React 19 RC?
Please reopen until fixed?

@mattschutt  I would tend to agree.
@VichetN  It should be reopened until release from @onesine is provided and works with React RC.

Same for me

FYI this still existing in the stable react 19 release


load method reads at wrong offset

Reading 24bit Bitmaps saved by gimp via load(...) resulted in corrupted image data.
I was able to fix this in the given scenario by adding
ifs.seekg(header->offset_bits);
after reading the header and before reading the image data. (around line 519 of BitmapPlusPlus.hpp)

Hi @seeliger-ec , Thank you for opening this issue!
You are right, I tried to load a 24bpp bitmap saved with gimp and it was not loading correctly.
As you mentioned, pixels reading & writing should always start from header->offset_bits which was not the case.
I guess I just assumed that after std::ifstream reads/writes BitmapHeader, the offset will point automatically at the beginning of pixels data but that is not always the case, gimp seems to put add extra information between the end of the header and the starting offset of pixels data as displayed below (the yellow area):

I have fixed this by adding your suggestion ifs.seekg(header->offset_bits); in the load function.
Thank you again and have a nice day.
Bader


vercel/kv exposes MULTI but not WATCH

Is there a way to use the WATCH command in Redis transactions (like kv.multi().watch(someKeys)...)?

I was thinking of using eval and making the script invoke redis.call('WATCH', ....), but this feels super hacky and, I'm not even sure if it will work as expected or if there are (practical and technical) downsides.

It seems like @upstash/redis does not support this and nor is it planning to.
@vercel/kv is based on upstash so I don't think they can implement it either.
(Note: I'm not affiliated with Vercel or Upstash, but I was running into this issue myself recently).


Problem running Sysbox with ID-mapped mounts on Fedora 35

I found sysbox and was happy, because it support my use cases to setup a CI environment without the limitations and security implications with DinD or similar setup. Thanks for this project and your commitment.
I started to read the documentation and tried to provide the sysbox on my host (Fedora based). I found a few minor issues during source build (separate issues will be coming). Now I started to install and configure it.
But, I am at the point to configure docker and the system and it had stopped me. Because of the change to enable userns-remap of docker. It has a major impact on my running host system and their installed containers. I will try to install shiftfs from source, but I would like to ask, when will "... soon ..." be reached.
In the documentation I found the sentence "In the near future (kernels 5.12+), shiftfs is expected to be replaced ... Sysbox will soon have support for this." Are there any plans (time schedule) to enable this feature. It would help very much (hopefully) to reduce the changes on the host system

Hi @fhaefemeier, thanks for finding Sysbox and giving it a shot.
Your timing is really good, we are just a few days away from the Sysbox v0.5.0 release which includes ID-mapped mounts support. However, the release will only have the .deb packages (for Ubuntu / Debian) and we won't have an RPM package for it for a few more weeks (we are actively working on this too).
The Sysbox upstream code already includes ID-mapped mounts support, so while we work on the RPM package, you can try Sysbox on Fedora (with kernel >= 5.12) by building it from source (it's pretty easy), but let us know if you need assistance.

Hi @ctalledo it good news.

The Sysbox upstream code already includes ID-mapped mounts support, so while we work on the RPM package, you can try Sysbox on Fedora (with kernel >= 5.12) by building it from source (it's pretty easy), but let us know if you need assistance.

You mean, it is already functional in the latest code available? I build yesterday sysbox on Fedora following your guide. So I have now a version which provide the new feature. Do I have to do something special or will it be enough to enable sysbox-runc without 'userns-remap' in docker daemon?

Hi @fhaefemeier,

You mean, it is already functional in the latest code available?

Yes that's right.

Do I have to do something special or will it be enough to enable sysbox-runc without 'userns-remap' in docker daemon?

Simply enable sysbox-runc without userns-remap.
Assuming you have a kernel >= 5.12, when you launch a container with Docker + Sysbox, it should work and you will see some ID-mapped mounts. E.g.:
$ docker run --runtime=sysbox-runc -it --rm ubuntu

root@62adea865594:/# findmnt | grep idmap
|-/etc/resolv.conf                                           /dev/nvme1n1p1[/tmp/sysbox-test-var-lib/docker/containers/62adea8655942f1f382f441ba38c07f2d67ae29187fca9a3e99e53b1a3e6fb75/resolv.conf] ext4    rw,relatime,idmapped,errors=remount-ro
|-/etc/hostname                                              /dev/nvme1n1p1[/tmp/sysbox-test-var-lib/docker/containers/62adea8655942f1f382f441ba38c07f2d67ae29187fca9a3e99e53b1a3e6fb75/hostname]    ext4    rw,relatime,idmapped,errors=remount-ro
|-/etc/hosts                                                 /dev/nvme1n1p1[/tmp/sysbox-test-var-lib/docker/containers/62adea8655942f1f382f441ba38c07f2d67ae29187fca9a3e99e53b1a3e6fb75/hosts]       ext4    rw,relatime,idmapped,errors=remount-ro
|-/usr/src/linux-headers-5.13.0-1017-aws                     /dev/root[/usr/src/linux-headers-5.13.0-1017-aws]                                                                                ext4    ro,relatime,idmapped,discard,errors=remount-ro
|-/usr/src/linux-aws-headers-5.13.0-1017                     /dev/root[/usr/src/linux-aws-headers-5.13.0-1017]                                                                                ext4    ro,relatime,idmapped,discard,errors=remount-ro
`-/usr/lib/modules/5.13.0-1017-aws                           /dev/root[/usr/lib/modules/5.13.0-1017-aws]                                                                                ext4    ro,relatime,idmapped,discard,errors=remount-ro

Let me know if you hit any issues please.

Let me know if you hit any issues please.

I installed sysbox on Fedora 35 with idmapped_mount (see also #513) and start a system container with docker run --runtime=sysbox-runc --rm -it --hostname my_cont debian:latest. It started successfully. But I have a strange behaviour, not sure if it is related to idmapped mounts or something different (I can open another ticket if you want).
The start of a system container is only successful after several failure starts. Failure ends with the message
docker: Error response from daemon: OCI runtime create failed: error in the container spec: failed to request rootfs cloning from sysbox-mgr: failed to invoke ReqCloneRootfs via grpc: rpc error: code = Unknown desc = failed to mount clone for container 489a56472eb8: failed to set up bottom ovfs mount: failed to mount overlayfs on /srv/container/sysbox/rootfs/489a56472eb8f43a157939a69443ee115f87be5d8324fc07358142dd4afbaa7f/bottom/merged: invalid argument: unknown.

I installed sysbox-mgr and sysbox-fs with default parameter. Only data-root is changed to /srv/container/sysbox instead of /var/lib/sysbox. After starting both daemons log shows:
Mär 20 20:01:05 homecloud systemd[1]: Starting sysbox-fs (part of the Sysbox container runtime)...
Mär 20 20:01:05 homecloud sysbox-fs[1391169]: {"level":"info","msg":"Initiating sysbox-fs ...","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-fs[1391169]: {"level":"info","msg":"Initializing with 'allow-immutable-remounts' knob disabled (default)","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-fs[1391169]: {"level":"info","msg":"Initializing with 'allow-immutable-unmounts' knob enabled (default)","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-fs[1391169]: {"level":"info","msg":"FUSE dir = /srv/container/sysboxfs","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-fs[1391169]: {"level":"info","msg":"IOvec memParser elected","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-fs[1391169]: {"level":"info","msg":"Listening on /run/sysbox/sysfs.sock","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-fs[1391169]: {"level":"info","msg":"Ready ...","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud systemd[1]: Started sysbox-fs (part of the Sysbox container runtime).

Mär 20 20:01:05 homecloud systemd[1]: Starting sysbox-mgr (part of the Sysbox container runtime)...
Mär 20 20:01:05 homecloud sysbox-mgr[1391149]: {"level":"info","msg":"Starting ...","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-mgr[1391149]: {"level":"info","msg":"Sysbox data root: /srv/container/sysbox","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-mgr[1391149]: {"level":"warning","msg":"failed to cleanup /srv/container/sysbox: unlinkat /srv/container/sysbox: device or resource busy","time":"2022-03>
Mär 20 20:01:05 homecloud sysbox-mgr[1391149]: {"level":"info","msg":"Listening on /run/sysbox/sysmgr.sock","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud sysbox-mgr[1391149]: {"level":"info","msg":"Ready ...","time":"2022-03-20 20:01:05"}
Mär 20 20:01:05 homecloud systemd[1]: Started sysbox-mgr (part of the Sysbox container runtime).

Let me know how I can help.

Maybe related. Found in kernel log
Mär 20 21:18:53 homecloud kernel: overlayfs: unrecognized mount option "c693"" or missing value

Thanks @fhaefemeier.

Only data-root is changed to /srv/container/sysbox instead of /var/lib/sysbox

Could you please try with the default data-root (i.e., /var/lib/sysbox)? It should work either way, but I wonder if we have a bug that we've not caught.

Modified the title to make it a bit more specific to this issue.

I changed the config and used the default data-root (sysbox-mgr) and mountpoint (sysbox-fs) and have the same behaviour. Before retesting I update to the latest git version (master branch).

No news after server reboot. Still same behaviour. How can I support you?

Hi @fhaefemeier, let me take a look in the next couple of days so we can get to the bottom of this.

Hi @fhaefemeier, finally got a chance to take a closer look.
I created a Fedora 35 VM on Google Compute Engine (GCE), the cloned the Sysbox GitHub repo, and did a make test-shell to get a shell inside the Sysbox test container, and after this was able to create containers without problem.
I did hit a few setup issues (which you probably run into also):

I had to create a Sysbox test container Dockerfile for Fedora 35 (see this commit).

The Sysbox Makefile had a dependency on lsb_release which required me to install the redhat-lsb-core core package on the host machine. I committed a change to remove this requirement going forward.

The Fedora-35 VM instance that I used as my host came with / mounted on a disk formatted with btrfs (rather than ext4). This is an issue because we don't officially support btrfs yet (we've not done much testing on it), and ID-mapped mounts don't yet work on btrfs (a Linux kernel limitation). To overcome this, I added an ext4 disk to the VM and  pointed both the Docker data-root and the Sysbox data-root to that disk.

After this, I was able to do a make test-shell which gets me a shell inside the test container, and from then was able to deploy containers with Docker + Sysbox without problem. This gives me confidence Sysbox works well on Fedora 35.
Then I took the next step and installed Sysbox on the Fedora 35 VM directly, as follows:

Install the fuse package on the host (Sysbox requires it).

$ dnf install -y fuse

Build the Sysbox binaries and install them:

$ make sysbox && make install

Start Sysbox:

$ ./scr/sysbox

Configure Docker with Sysbox (for this I used the convenience script in the Sysbox repo which does the config in /etc/docker/daemon.json and restarts Docker):

$ ./scr/docker-cfg --sysbox-runtime=enable

After this, I was able to run Sysbox containers directly on the Fedora 35 host as follows:
[vagrant@instance-1 sysbox]$ cat /etc/os-release | egrep "^NAME|^VERSION"
NAME="Fedora Linux"
VERSION="35 (Cloud Edition)"
VERSION_ID=35

[vagrant@instance-1 sysbox]$ docker run --runtime=sysbox-runc -it --rm nestybox/ubuntu-focal-systemd-docker

Welcome to Ubuntu 20.04.2 LTS!

[  OK  ] Created slice system-getty.slice.
[  OK  ] Created slice system-modprobe.slice.
[  OK  ] Created slice User and Session Slice.
...
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Finished Update UTMP about System Runlevel Changes.

Ubuntu 20.04.2 LTS 030f7f2a79bf console

030f7f2a79bf login: admin
Password:
Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.14.10-300.fc35.x86_64 x86_64)

...

admin@030f7f2a79bf:~$ docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

admin@030f7f2a79bf:~$ docker run -it alpine
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
40e059520d19: Pull complete
Digest: sha256:f22945d45ee2eb4dd463ed5a431d9f04fcd80ca768bb1acf898d91ce51f7bf04
Status: Downloaded newer image for alpine:latest
/ #

As you can see, I am not hitting the same error you got (not sure why). Please try to follow the steps above and let me know if this fixes it or not. Also, feel free to join the Sysbox slack channel, as that may be a better forum to get to the bottom of the issue you are facing.

@ctalledo Thanks providing your test scenario. I will check it, but it will take a little bit of time. I will keep you informed.
One question, did you repeat creating sysbox containers (in short frequence)? In my case, for a test, I called a docker run several times one after another and aprox. three of ten are working...

Hi @fhaefemeier,

I use XFS as filesystem (md raid/LVM), if it is important...

That could matter; in my VM I have btrfs or ext4.

did you repeat creating sysbox containers (in short frequence)? In my case, for a test, I called a docker run several times one after another and aprox. three of ten are working...

Yes, I see no problem:
[vagrant@instance-1 sysbox]$ for i in $(seq 1 10); do docker run --runtime=sysbox-runc -d --rm ghcr.io/nestybox/ubuntu-focal-systemd-docker; done
50eef94fac681c353d60dc3903ef449cbc165827d8faad32ed34d42e2b2df3bc
50a8b01326c0d0adc29bccaab1605c02980b9aaf1a108ef90153b20162d4228b
a53e04092089e342c9edd5c3e37580990295e4157418bca1649032d9f0567d55
59f99b09f5170b10a986eeadfe8dc1bab8d1e0889a6f882ebe0c3b1c24978eb0
244cb65d8bc3932628b4b5a820a2a5655a6362ca55a3a486779cf543402822da
b874a9870c16bf9b6db3533a7036befb69ce55df085b54dc442bbcf4982091b9
bfbaefaca8c6c0489b73e656a07350c71c369ae971ea429f4b718ba18accf03b
1d565603b68dae93681b2adf4e60d0a7ab069eb3f9f83571dacea778b756424e
538fc3ae59ae309142f4846b445ba005d83dfcfb5d1f8466b31e1b25ff55506d
ad3e89012b3c9f9e6d38b723a84f1f24846ffae6d52d9e876567be727610604c

[vagrant@instance-1 sysbox]$ docker ps
CONTAINER ID   IMAGE                                          COMMAND                  CREATED          STATUS          PORTS     NAMES
ad3e89012b3c   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   4 seconds ago    Up 2 seconds    22/tcp    sleepy_keldysh
538fc3ae59ae   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   6 seconds ago    Up 4 seconds    22/tcp    ecstatic_greider
1d565603b68d   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   8 seconds ago    Up 6 seconds    22/tcp    nifty_fermi
bfbaefaca8c6   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   10 seconds ago   Up 8 seconds    22/tcp    quizzical_bartik
b874a9870c16   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   13 seconds ago   Up 9 seconds    22/tcp    boring_hawking
244cb65d8bc3   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   16 seconds ago   Up 13 seconds   22/tcp    thirsty_driscoll
59f99b09f517   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   18 seconds ago   Up 15 seconds   22/tcp    inspiring_brahmagupta
a53e04092089   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   19 seconds ago   Up 17 seconds   22/tcp    peaceful_burnell
50a8b01326c0   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   21 seconds ago   Up 19 seconds   22/tcp    fervent_austin
50eef94fac68   ghcr.io/nestybox/ubuntu-focal-systemd-docker   "/sbin/init --log-le…"   22 seconds ago   Up 20 seconds   22/tcp    charming_khorana

@ctalledo I had the chance to test it in a separate environment (Fedora 35 installed in a qemu VM). make test-shell was successful and installed sysbox inside the VM following your steps (1-4). The installation use XFS as filesystem and everything (docker, sysbox) use default parameter (e.g. data-root for docker and sysbox).
[sysbox@fedora sysbox]$ cat /etc/os-release | egrep "^NAME|^VERSION"
NAME="Fedora Linux"
VERSION="35 (Server Edition)"
VERSION_ID=35

Creating a sysbox with docker run --runtime=sysbox-runc -it --rm nestybox/ubuntu-focal-systemd-docker was successful without errors and repeatable.
But there is one important difference to my original host system. Selinux is enabled in docker daemon. If I enable it in the VM I have the same/similar error scenarios. At the end system containers can't be created.
[sysbox@fedora sysbox]$ docker run --runtime=sysbox-runc -it --rm nestybox/ubuntu-focal-systemd-docker
docker: Error response from daemon: failed to create shim: OCI runtime create failed: error in the container spec: failed to request rootfs cloning from sysbox-mgr: failed to invoke ReqCloneRootfs via grpc: rpc error: code = Unknown desc = failed to mount clone for container eb2df2642d49: failed to set up bottom ovfs mount: failed to mount overlayfs on /var/lib/sysbox/rootfs/eb2df2642d49f1f2f937fc53f381e77a1ed241d42746dab5d76c84e4810e75ea/bottom/merged: invalid argument: unknown.

Or different error
[sysbox@fedora sysbox]$ docker run --runtime=sysbox-runc -it --rm nestybox/ubuntu-focal-systemd-docker
Welcome to Ubuntu 20.04.2 LTS!

Failed to create /init.scope control group: Permission denied
Failed to allocate manager object: Permission denied
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...

Hi @fhaefemeier,
Thanks for the update.

But there is one important difference to my original host system. Selinux is enabled in docker daemon. If I enable it in the VM I have the same/similar error scenarios. At the end system containers can't be created.

How exactly did you enable SELinux in the VM? I want to see if I can repro on my Fedora 35 host.
Thanks.

If you have done a standard Fedora installation, SELinux is running in enforcing mode (default mode). You can check it in /etc/selinux/config. Additionally the docker daemon is configured with
{
  "log-driver": "journald",
  "selinux-enabled": true,
  "runtimes": {
     "sysbox-runc": {
        "path": "/usr/local/bin/sysbox-runc"
     }
  }
}

You can check the SELinux labels with ls -lZ. There are different labels. The main labels (known and used by me) are

container_file_t
container_var_lib_t

But there are more, for sure. An older post on stack overflow gives some hints.

Any news?

Hi @fhaefemeier, my apologies, did not get a chance to check the SELinux part yet; will try to get to it next week.


How To Implement Drag and Drop File Upload In Next.js Without Any Additional Libraries.

Topic Suggestion
How To Implement Drag and Drop File Upload In Next.js Without Any Additional Libraries.
Writing sample(s):
ENGED PROGRAM CONTRIBUTOR Gisiora Elvis
Proposed article introduction
The Drag and Drop interfaces enable web applications to drag and drop files on a web page, providing a good user experience. This tutorial will guide the reader through how an application can accept one or more files that are dragged from the underlying platform's file manager and dropped on a web page. Will make use of the HTML5 Drag and Drop API and the FileReader API to accomplish this on a Next.js application without any additional libraries.
Key takeaways
Why use a drop zone for file uploads.
An overview of the HTML5 Drag and Drop API and the FileReader API.
How to implement drag and drop file upload in a Nextjs application.
Article quality
This is a beginner-friendly and in-depth guide that covers the HTML5 Drag and Drop API and the FileReader API and how to use them to implement drag and drop file upload in a Nextjs application without any additional libraries.
References

HTML Drag and Drop API
FileReader API
How To Guide Template
Tutorial Template

Seems like a helpful topic. Let's ensure that it adds value to the community. Thanks


Gaps on line charts

I am having an issue with line graphs. For some reason, I am getting gaps between lines and points in the line graph, like this:
http://i.imgur.com/WFEUgr0.png
I understand that this may be caused by gaps in data table. Is there a way to just still have a connection between the lines even if there connection is fragmented?

Yeah, you can change the chart type and it should render lines. Try LineChart ? If it doesn't work please post some code I can run to help you debug

This is what I have on the module call
<Chart
    chartType="LineChart"
    data={this.state.chartData}
    options={this.state.options}
    graph_id="ScatterChart"
    width={"100%"}
    height={"800px"}
    legend_toggle={true} />

Here are my options, if necessary
var options = {
    title: "Mood Analysis Of The Top 500 posts of r/NoMansSkyTheGame. Average per month.",                colors: ['red', 'green', 'orange', 'yellow', 'blue'],
    legend: {
        position: 'right'
    },
    hAxis: {
        title: 'Month',
        gridlines: {
            count: -1
        }
    },
    vAxis: {
        title: 'Mood',
        gridlines: {
            count: -1
        }
    }
}

Are your data points in this.state.chartData sorted by Date (x-axis) ? Could you try that ?

Any update ?

Sorry, yes there;s an update. The reason why there were gaps was because
the dataset dates were not continuous, and the graph would not make the
jump in some of the gaps. My workaround was grouping the data by month
instead.
On Tue, Jan 24, 2017 at 2:10 AM, Rakan Nimer<EMAIL_ADDRESS>wrote:

Any update ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RakanNimer/react-google-charts/issues/97#issuecomment-274726705,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIjAtOg9NmecZNvdwfi1b_YGyvf6E4BGks5rVaPrgaJpZM4LZPv_
.

Great ! Thanks for reporting back :)
Closing issue.


Register for Android Backup and test

This might be useful to users, especially since we cannot export the projects: http://developer.android.com/guide/topics/data/backup.html

Moved from LLK/scratchjr-private#101
/cc @markroth8

closing in favor of https://github.com/LLK/scratchjr/issues/117


Spring Data integration

Can't write command batch to channel: [id: 0x61e3267f, L:/xxxxxxxx:xxx ! R:xxxxxx/xxxxxx:6379]. I found the tcp.socket not exists。 why we not close it  in  CommandBatchService.checkWriteFuture

A new milestone for Redisson. Well done, @mrniko

@jackygurui
Thank you! But it's not finished yet.

Done

Is it finished? When does it officially release?

At early next month

Well done.


chore: 🤖 bump keen deps

Codecov Report

Merging #368 (55fc529) into develop (f6cae01) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #368   +/-   ##
========================================
  Coverage    87.02%   87.02%
========================================
  Files          558      558
  Lines         7158     7158
  Branches       722      722
========================================
  Hits          6229     6229
  Misses         844      844
  Partials        85       85

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 f6cae01...55fc529. Read the comment docs.


Where are pre-trained weights?

I’m writing with regard to your paper, "Experience Report: Deep Learning-based System Log Analysis for Anomaly Detection".  Recently, I have read it and I also referred to your public source code on github. But I had some problems. I can not run .py demo file in the demo folder .
It might be there are no pre-trained weights on this source code. It would be great if you could help me to get it.
Best regards,
Thao Nguyen
Ho Chi Minh University of Science

Hi. You cannot run all .py demo files or just some of them? Most settings do not require pre-trained weights to run. Can you post more error info? Also, make sure the python version is correct. Thanks.

Hi @zbchern,
I have run the .py demo file, I detect the problem is the incorrect position of the .py demo file, it might be moved to deep-loglizer folder. I have another problem. I can not get the results that you have presented in your paper. What are the parameters  and data which you used to train model?
Thank you.


Add kafka-manager

Please, implement kafka-manager (https://github.com/yahoo/kafka-manager) into Kafka service creation.
A ready-to-use docker image - https://hub.docker.com/r/sheepkiller/kafka-manager/ - can be used. Probably the best way is to add a command line keys like -enable-kafka-manager and -kafka-manager-port=9000 to run it along with the kafka service.

kafka-manager is a good project. Will further evaluate how to add it.

The initial Kafka Manager service is added. We decided to add as a separate service, as one Kafka Manager could manage multiple Kafka services. Please take a look and see if it works for you. Thanks!

It does work, awesome! Thanks a bunch!
One thing I noticed is that the log group for kafkamanager looks like firecamp-firecamp-qa-kafkamanager-qa-b52..., while my other loggroups looks like firecamp-qa-kafka-qa-ae9a...
Could you please fix loggroup name generation?
The command line for kafkamanager creation was:
./firecamp-service-cli -cluster=firecamp-qa -region=us-east-1 -op=create-service -service-type=kafkamanager -service-name=kafkamanager-qa -km-heap-size=512 -km-zk-service=zoo-qa

Please, add Kafka Manager readme to the tutorials wiki page

yes, the log group format is firecamp-clustername-servicename-serviceuuid. Your cluster name is "firecamp-qa", so the log group name will start with firecamp-firecamp-qa.

Thanks for the remind! Added to wiki.

yes, the log group format is firecamp-clustername-servicename-serviceuuid. Your cluster name is "firecamp-qa", so the log group name will start with firecamp-firecamp-qa.

it used to be different before, right? the point is that i name my clusters like 'firecamp-uat' or 'firecamp-qa' to differentiate them from other clusters like 'uat' and 'qa' where the apps are running.
could you please revert that back and name log groups after the cluster name w/o any prefixes? this is really more logical than the current implementation (imho).

yes, the firecamp prefix is added recently. sounds a good suggstion. we could revert it.

The fix was committed.


Sandbox security escalation allowing users to read configuration

I recently discovered that when using the sandbox of Twig, the global variables added by Laravel are still available. By default, the framework adds 'app' as a shared variable in the ViewServiceProvider.
The problem with this is that although by itself app, as an instance of Application is quite harmless, the Container instance which it inherits is not.
Twig's sandbox requires you to add the magic __isset() method to your classes in order to allow the sandbox' security policy to check if the method or property you are calling on your class is allowed. Laravel's Container class does not have this method, meaning that the __get() method can be used freely within the sandbox, regardless of the given security policy.
The Application class contains all instances for the application, including the configuration one. This configuration can be requested by simply calling $application->config, which will use the magic get method to fetch the config repository, which in turn allows you to request any value from the current configuration as it implements ArrayAccess (unfortunately #362 doesn't fix this as it's not a Model).
Tl;dr
You can read the configuration of any Laravel application from within Twig's sandbox by using the global app variable added by the framework itself.
For example:
{% sandbox %}
    {% include(template_from_string(user_template) only %}
{% endsandbox %}

with user_template being the following:
The key is {{ app.config.app.key }}

would produce The key is base64:your_app_key..., while using the config_get() function would result in a Twig SecurityException being thrown as intended.
I don't suppose many users of this package are even using the sandbox or care about this issue but my proposed solution for now is to remove the app variable from the global context by either overriding it locally for your template or from within one of your app's ServiceProviders:
{% sandbox %}
    {% include(template_from_string(user_template) with {app: null } only %}
{% endsandbox %}

Or in a ServiceProvider:
public function boot(): void {
    View::share('app', null);
}

Again, I don't know how big of an issue this really is with this package itself but I thought I'd leave it here anyway so it can either be documented somewhere or discussed.

Well we should probably fix that indeed. Not sure how though.

@MaxKorlaar Thanks for logging this. If you have any thoughts on the below, please comment :)
@barryvdh We'd have to handle it here - https://github.com/rcrowe/TwigBridge/blob/2054abdbd8dcde573cd86d8d3856873e2388d47b/src/Node/GetAttrNode.php#L132
It's been a while since I looked at this but could we not just change is_a($object, 'Illuminate\Database\Eloquent\Model') to $object instanceof ArrayAccess. The is_a code has been here pretty much sicne the beginning. I've just copied it around in my previous PRs.
Not sure why https://github.com/twigphp/Twig/pull/1863 was rejected / closed which did what I'm suggesting. Possibly - https://github.com/twigphp/Twig/issues/106#issuecomment-583737

See https://github.com/rcrowe/TwigBridge/pull/398

I've decided to just override base_template_class when I'm using a security policy.
abstract class Template extends \Twig\Template
{
    /**
     * {@inheritdoc}
     */
    public function display(array $context, array $blocks = [])
    {
        \Twig\Template::display($context, $blocks);
    }
}

Any solution to this issue? all attempts at fixing it seems to have been reverted.


After restart doesnt work

After computer restart right click doesnt work.. tried checking reg keys but still doesnt work

Use this command to register a shell. Version 1.8 build 100 is available in portable version
Open command prompt as admin
shell -register -treat -restart

somehow my shell commands is missing

run cmd in shell directory or write shell path
path\to\shell.exe -r -restart -treat

command went through but after restart again theres no context menu unless i unregister or register again.. and i copied files from portable

Did you modify the settings file .nss?

Can you pls provide me link for 1.7 bc its 1.8 that breaks right click on desktop i had to restore back up of system image where was 1.7 and it works fine until you update it to 1.8 even portable 100 doesnt work

Please test this build
Unregister Shell and then register the attached build.

yeah works now... ty.. mark as solved


Add more benches

Get TrueType benches work again.
Note: merge this PR only after #19 . CC me if you'd like me to rebase this branch.

@raphlinus so??

@raphlinus hello?

@raphlinus hello? When will you merge this PR?

Sorry about that. I had this confused with the other one, which I believe still has issues. Thanks for the contribution.


Minor updates

Been experimenting with the library so thought I'd help tidy it up.
Primarily fixing Clippy warnings and suggestions

Thanks. This seems like it'll take a while to review.

Thanks. This seems like it'll take a while to review.

Happy to break it up - just thought rather than say thanks. I’d contribute something back as a thank you 😊

Happy to break it up - just thought rather than say thanks. I’d contribute something back as a thank you 😊

@Darksonn thanks for the review. Will update and looking into the items you've highlighted.

Will also squash the commits.

@Darksonn thanks for the review. Will update and looking into the items you've highlighted.

Will also squash the commits.


WireGuard service fails

Any idea why? It's a clean install of Debian 10 on a VPS with nothing modified.
root@vps37452589:/home# systemctl status<EMAIL_ADDRESS>●<EMAIL_ADDRESS>- WireGuard via wg-quick(8) for wg0
   Loaded: loaded<EMAIL_ADDRESS>enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-09-09 23:27:49 CEST; 1min 50s ago
     Docs: man:wg-quick(8)
           man:wg(8)
           https://www.wireguard.com/
           https://www.wireguard.com/quickstart/
           https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8
           https://git.zx2c4.com/wireguard-tools/about/src/man/wg.8
  Process: 8264 ExecStart=/usr/bin/wg-quick up wg0 (code=exited, status=1/FAILURE)
 Main PID: 8264 (code=exited, status=1/FAILURE)

Sep 09 23:27:49 vps37452589 systemd[1]: Starting WireGuard via wg-quick(8) for wg0...
Sep 09 23:27:49 vps37452589 wg-quick[8264]: [#] ip link add wg0 type wireguard
Sep 09 23:27:49 vps37452589 wg-quick[8264]: RTNETLINK answers: Operation not supported
Sep 09 23:27:49 vps37452589 wg-quick[8264]: Unable to access interface: Protocol not supported
Sep 09 23:27:49 vps37452589 wg-quick[8264]: [#] ip link delete dev wg0
Sep 09 23:27:49 vps37452589 wg-quick[8264]: Cannot find device "wg0"
Sep 09 23:27:49 vps37452589 systemd[1]<EMAIL_ADDRESS>Main process exited, code=exited, status=1/FAILURE
Sep 09 23:27:49 vps37452589 systemd[1]<EMAIL_ADDRESS>Failed with result 'exit-code'.
Sep 09 23:27:49 vps37452589 systemd[1]: Failed to start WireGuard via wg-quick(8) for wg0.

Never mind, for some reason rebooting the machine solved it.

It might been needed to load the kernel module.


Add to printer config  itemTextLength and commentTextLength

It is a good idea to have possibility to define itemTextLength and commentTextLength in printer definition, because printer documentation is not correct and ErpNet.FP doesn't return proper values for some devices.
This can be a config file then can be updated remotely or locally.

Hello,
Thank you for the new settings!
But there is a problem with them. After I set the commentTextLength and apply, the server returned original values:

There is new version, v.1.0.1213.1913. Try with it.


Exam mode: The working time in minutes is not calculated automatically in Test mode

Describe the bug
When you create or import an exam, the working time in minutes is not calculated automatically in Test mode.
To Reproduce

Go to any course
Click on exam
Click on create or import exam
Select Test exam in the mode section.
Adaprt the dates and verify that the working time remains in zero. See the screencast.

Expected behavior
The working time should be calculated just like in the normal Exam mode.
Screenshots
https://github.com/ls1intum/Artemis/assets/88991954/b0bf926e-343a-4132-851a-8951c0df1d92
Which version of Artemis are you seeing the problem on?
6.3.3
What browsers are you seeing the problem on?
Chrome
Additional context
No response
Relevant log output
No response

This is intended. In the test exam students can start the exam in a window (eg 1 week) and instructors need to specify the working time (eg 90min)


Fix IndividualUser first and last name setters

What does this pull request aim to achieve? 💯
Fix Individualuser first and last name setters. Closes #512
🚨Before submitting this pull request🚨:
Please do NOT submit this PR if you have not done the following:

I have checked that no one else is working on similar changes.
I have read the latest README and understand the development workflow.
The name of this branch is: feature/<branch_name> (need to have cloned the repo not forked).
This branch is rebased/merged with the latest master.
There are no merge conflicts.
There are no console warnings and errors.
On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".

Hi @joaofnds thanks this addresses the issue I opened but I've noticed something else. I doesn't seem updating the references works through SchemaType setters because the update is asynchronous while the setters are synchronous. I change org 'name: 'Sourced by FightPandemics - Community' to 'name: Sourced by FightPandemics (from Community), the updateAuthorName function does execute but the post.author.name isn't actually updated.
I think this would be easier to troubleshoot, however, once we have all the endpoints working - create/update post as organization; update individual user. So I can open the issue but let's tackle before launch but after the preceding are done.
What's your suggestion @Naraujo13?
As a resolution, maybe we need to use post-save middleware instead? https://mongoosejs.com/docs/middleware.html

I'm going to close this as we're solving this whole syncing thing a different way


Sometimes callback executing before scrolling has finished

Hello! I've found a little bug with callback mechanism.
In my app i'm relying on window.addEventListener('scroll', /** my super code **/ ).
I also relying on jumper's callback option, and sometimes callback executes before the last scroll event happens.
See: https://jsfiddle.net/mxqfjLge/ (I hope it will reproduce on your screen resolution)

i have prepared PR #56 to fix this

Sry, is somebody there? This bug is significant to me. I'm of cause already using my own patched version of the library, but it would be great to use the offical one. If my solution makes no sense or incorrect it would be nice to know any other workaround :)


Creating a fire weather index calculation diagnistic

We are working on creating a fire weather index derivation diagnostic. I think I will preprocess data for it with the existing preprocessors and fire weather index itself will be derived with xclim package in the diagnostic. Details to follow.

@malininae, you may be interested in https://github.com/zklaus/esmvaltool/tree/fwi-update, where I am doing more or less the same.


Can't do cl for missing items in text format

🚀 Feature Proposal
i am hardcore missing the feature that showed missing cl items in text format.
without it, I'm having trouble finding out what this new item is on misc cl.

dupe of https://github.com/oldschoolgg/oldschoolbot/issues/4381
No idea on the item

dupe of #4381 No idea on the item

item is ivy seed I found out. from treebeard


Create inspection to report missing screenshot files in Terra.validates calls

Summary of scope
The scope is to implement an inspection for Terra.validates.screenshot(); and related calls, so that it would report when a "referenced" screenshot file doesn't exist.
Solution details

The inspection would report the image missing if it doesn't exist for any context (locale, browser, viewport/formFactor).
When the validated calls have a name parameter specified, the inspection would register the name parameter to the problems, otherwise it would the element representing the call's name (e.g. Terra.validates.screenshot) that would be registered.
The calls to include:

Terra.validates.screenshot
Terra.validates.element
Terra.it.validatesScreenshot
Terra.it.validatesElement

Out of scope

latest and diff versions of images won't be included in the validation, only the reference version of the image should be checked.

Done.