OSError: sbatch: error: Batch job submission failed: Invalid generic resource (gres) specification

Hi NVIDIA,
Slurm should be ready:
root@user:~/container_tools/NeMo-Megatron-Launcher/launcher_scripts# sinfo
PARTITION AVAIL  TIMELIMIT  NODES  STATE NODELIST
dgx*         up   infinite      1   idle user
First, download the pile dataset offline
Then,  only place 00.jsonl.zst to the launcher_scripts/data/bpe path.
~/container_tools/NeMo-Megatron-Launcher/launcher_scripts/data/bpe#ls
00.jsonl.zst  merges.txt  SHA256SUMS.txt  test.jsonl.zst  val.jsonl.zst  vocab.json

But when I execute "python3 main.py" the following error occurs.
main.py:57: UserWarning:
The version_base parameter is not specified.
Please specify a compatability version level, or None.
Will assume defaults for version 1.1
  @hydra.main(config_path="conf", config_name="config")
/usr/local/lib/python3.8/dist-packages/hydra/_internal/hydra.py:119: UserWarning: Future Hydra versions will no longer change working directory at job runtime by default.
See https://hydra.cc/docs/next/upgrades/1.1_to_1.2/changes_to_job_working_dir/ for more information.
  ret = run_job(
=================== save_dir /root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/data/bpe file_name vocab.json
=================== save_dir /root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/data/bpe file_name vocab.json
File /root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/data/bpe/vocab.json already exists, skipping download.
=================== save_dir /root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/data/bpe file_name merges.txt
=================== save_dir /root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/data/bpe file_name merges.txt
File /root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/data/bpe/merges.txt already exists, skipping download.
Job nemo-megatron-download_gpt3_pile submission file created at '/root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/results/download_gpt3_pile/download/nemo-megatron-download_gpt3_pile_submission.sh'
sbatch: error: Batch job submission failed: Invalid generic resource (gres) specification
Error executing job with overrides: []
subprocess.CalledProcessError: Command '['sbatch', '/root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/results/download_gpt3_pile/download/nemo-megatron-download_gpt3_pile_submission.sh']' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "main.py", line 87, in <module>
    main()
  File "/usr/local/lib/python3.8/dist-packages/hydra/main.py", line 90, in decorated_main
    _run_hydra(
  File "/usr/local/lib/python3.8/dist-packages/hydra/_internal/utils.py", line 389, in _run_hydra
    _run_app(
  File "/usr/local/lib/python3.8/dist-packages/hydra/_internal/utils.py", line 452, in _run_app
    run_and_report(
  File "/usr/local/lib/python3.8/dist-packages/hydra/_internal/utils.py", line 216, in run_and_report
    raise ex
  File "/usr/local/lib/python3.8/dist-packages/hydra/_internal/utils.py", line 213, in run_and_report
    return func()
  File "/usr/local/lib/python3.8/dist-packages/hydra/_internal/utils.py", line 453, in <lambda>
    lambda: hydra.run(
  File "/usr/local/lib/python3.8/dist-packages/hydra/_internal/hydra.py", line 132, in run
    _ = ret.return_value
  File "/usr/local/lib/python3.8/dist-packages/hydra/core/utils.py", line 260, in return_value
    raise self._return_value
  File "/usr/local/lib/python3.8/dist-packages/hydra/core/utils.py", line 186, in run_job
    ret.return_value = task_function(task_cfg)
  File "main.py", line 75, in main
    job_id = stage.run()
  File "/root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/nemo_launcher/core/data_stages.py", line 70, in run
    job_id = launcher.launch(command_groups=command_groups)
  File "/root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/nemo_launcher/core/launchers.py", line 58, in launch
    job_id = self._launcher.launch(command_groups)
  File "/root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/nemo_launcher/core/launchers.py", line 96, in launch
    job_id = self._submit_command(submission_file_path)
  File "/root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/nemo_launcher/core/launchers.py", line 393, in _submit_command
    output = job_utils.CommandFunction(command_list, verbose=False)()  # explicit errors
  File "/root/container_tools/NeMo-Megatron-Launcher/launcher_scripts/nemo_launcher/utils/job_utils.py", line 124, in __call__
    raise OSError(stderr) from subprocess_error
OSError: sbatch: error: Batch job submission failed: Invalid generic resource (gres) specification

Thanks
Aaron

If your cluster does not support gres, try setting gpus_per_node: null
https://github.com/NVIDIA/NeMo-Megatron-Launcher/blob/master/launcher_scripts/conf/cluster/bcm.yaml#L5


[RFC] Hide when online / offline directives

Directives using injectNetwork to hide components when the browser is online or offline.
@Directive({
  selector: '[hideIfOnline]',
  standalone: true,
})
export class HideIfOnline {
  private renderer = inject(Renderer2);
  private elementRef = inject(ElementRef<unknown>);
  private network = injectNetwork();

  constructor() {
    effect(() => {
      if (this.network.supported() && this.network.online()) {
        this.renderer.setStyle(this.element.nativeElement, 'display', 'none')
      }
    })
  }
}

@Directive({
  selector: '[hideIfOffline]',
  standalone: true,
})
export class HideIfOffline {
  private renderer = inject(Renderer2);
  private elementRef = inject(ElementRef<unknown>);
  private network = injectNetwork();

  constructor() {
    effect(() => {
      if (this.network.supported() && !this.network.online()) {
        this.renderer.setStyle(this.element.nativeElement, 'display', 'none')
      }
    })
  }
}

Hi @Dafnik - Setting display: none hides it from the view, but it does not remove it from the DOM, nor does it block the execution of the component that is being hidden. This component may make API calls or some computation that shouldn't be triggered.
Instead of:
<comp-which-calls-apis-internally hideIfOffline />
<placeholder-comp hideIfOnline />

Prefer:
private network = injectNetwork();
public isOnline = computed(() => this.network.supported() && this.network.online());

@if (isOnline()) {
  <comp-which-calls-apis-internally />
} @else {
  <placeholder-comp />
}

If you find isOnline often used for your requirements, I suggest making your own injectDeviceIsOnline() based on injectNetwork().

I see what you mean. It was more intended for something like heads up banner to show that your device has no internet connection or smth like that. But directly using the signal is also fine. :)
Thx!


After built the z-index changed

Version
not just v2.8.1
Reproduction link
Just init any project.
Steps to reproduce

Just make a vue component，write z-index in style
Run command: npm  run dev，everything fine
Run command: 'npm run build`，what a mess...my z-index value changed

I think the z-index value shouldn't be changed，because we may use the third party plugin like jQuery plugin which could use z-index. In this condition, the z-index calculation is unnecessary, and make mistakes.
What is expected?
keep my z-index value
What is actually happening?
my z-index changed

Please report issue in relevant template repo.

Oh, it's webpack template.


Blurry screenshots

Can you please replace the blurry screenshots with clear ones? They all seem to be low quality and blurry.
Thank you

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

ID: a70f3ebd-4e7d-25c7-56d7-91f8d9f39b03
Version Independent ID: a70f3ebd-4e7d-25c7-56d7-91f8d9f39b03
Content: Connect to Azure Communication Services
Content Source: ce/customer-service/voice-channel-acs-resource.md
Service: dynamics-365-customerservice
GitHub Login: @mh-jaya
Microsoft Alias: v-jmh

Hello
Owing to a couple of technical changes, doc restructuring, and other content guidelines, the topic has been split up into sub-topics, providing links to the Azure documentation whereever relevant. This has meant removal of graphics as they weren't needed. Request you to check the Azure documentation where necessary.
Thanks,
Jaya


Attached to player

Free carts become attached to the player after restart

I am unable to reproduce this issue.
Are there any other steps required other than having a unattached cart nearby?
Which version of this mod are you playing on?

Closing since nobody else seems to be able to reproduce this issue.


Support for non-Identity generator monad

Fixes #2

runSpecAndGetResults and runSpecAndExitProcess' are now generic in the generator monad that has to support unwrapping the Aff via the new class TestTreeGenerator
runSpecAndExitProcess, however, still insists on Identity. This is because making it generic would require explicit specification of which monad to use (either via a type signature or with VTA), which will needlessly complicate the most base use case. On the other hand, when the use case becomes more complex, the SpecT value usually already has a type signature anyway.

:+1:


Request 0.18 binary for Linux 32-bit

Please restore the 32-bit Linux binary of version 0.18.0 to the releases page.
I found installing 0.18.0 via npm to be more complicated and difficult.
With 0.18.0, I'm merely touching-up an old project. Some others may be doing the same.

The old releases are here:
https://github.com/elm-lang/elm-platform/releases


No driver for kernel version 5.15.0-1042-gke

Describe the bug
No driver for kernel version 5.15.0-1042-gke
No prebuilt falco kernel module for driver v5.0.1 5.15.0-1042-gke_47.
How to reproduce it
Created new GKE cluster with gke 1.26.9 - europe-west1.  I was given nodes with linux kernel 5.15.0-1042-gke
NAME                                                  STATUS   ROLES    AGE     VERSION               INTERNAL-IP    EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION    CONTAINER-RUNTIME
gke-dp-xxxxx-gke-e-default-101ed21e-nl1d   Ready    <none>   6h33m   v1.26.9-gke.1256000   <IP_ADDRESS>   <none>        Ubuntu 22.04.3 LTS   5.15.0-1042-gke   containerd://1.6.18

Expected behaviour
either have driver pre-built and ready for download or able to build.
https://download.falco.org/driver/site/index.html?lib=5.0.1%2Bdriver&target=all&arch=x86_64&kind=all&search=5.15.0-1042

Screenshots
* Setting up /usr/src links from host
* Running falco-driver-loader for: falco version=0.35.1, driver version=5.0.1+driver, arch=x86_64, kernel release=5.15.0-1042-gke, kernel version=47
* Running falco-driver-loader with: driver=module, compile=yes, download=yes

================ Cleaning phase ================

* 1. Check if kernel module 'falco' is still loaded:
- OK! There is no 'falco' module loaded.

* 2. Check all versions of kernel module 'falco' in dkms:
- OK! There are no 'falco' module versions in dkms.

[SUCCESS] Cleaning phase correctly terminated.

================ Cleaning phase ================

* Looking for a falco module locally (kernel 5.15.0-1042-gke)
* Filename 'falco_ubuntu-gke_5.15.0-1042-gke_47.ko' is composed of:
 - driver name: falco
 - target identifier: ubuntu-gke
 - kernel release: 5.15.0-1042-gke
 - kernel version: 47
* Trying to download a prebuilt falco module from https://download.falco.org/driver/5.0.1%2Bdriver/x86_64/falco_ubuntu-gke_5.15.0-1042-gke_47.ko
curl: (22) The requested URL returned error: 404
Unable to find a prebuilt falco module
install: /usr/lib/gcc/x86_64-linux-gnu/5/
* Trying to dkms install falco module with GCC /usr/bin/gcc
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"

Creating symlink /var/lib/dkms/falco/5.0.1+driver/source ->
                 /usr/src/falco-5.0.1+driver

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'/tmp/falco-dkms-make'...(bad exit status: 2)
* Running dkms build failed, dumping /var/lib/dkms/falco/5.0.1+driver/build/make.log (with GCC /usr/bin/gcc)
DKMS make.log for falco-5.0.1+driver for kernel 5.15.0-1042-gke (x86_64)
Wed Oct  4 18:22:10 UTC 2023
'/tmp/falco-dkms-make' -C /lib/modules/5.15.0-1042-gke/build M=/var/lib/dkms/falco/5.0.1+driver/build modules
make[1]: Entering directory '/host/usr/src/linux-headers-5.15.0-1042-gke'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
  You are using:           gcc (Debian 5.5.0-12) 5.5.0 20171010
  CC [M]  /var/lib/dkms/falco/5.0.1+driver/build/main.o
gcc: error: unrecognized command line option '-mharden-sls=all'
make[2]: *** [scripts/Makefile.build:297: /var/lib/dkms/falco/5.0.1+driver/build/main.o] Error 1
make[1]: *** [Makefile:1909: /var/lib/dkms/falco/5.0.1+driver/build] Error 2
make[1]: Leaving directory '/host/usr/src/linux-headers-5.15.0-1042-gke'
make: *** [Makefile:16: all] Error 2
install: /usr/lib/gcc/x86_64-linux-gnu/5/
* Trying to dkms install falco module with GCC /usr/bin/gcc-5
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'/tmp/falco-dkms-make'...(bad exit status: 2)
* Running dkms build failed, dumping /var/lib/dkms/falco/5.0.1+driver/build/make.log (with GCC /usr/bin/gcc-5)
DKMS make.log for falco-5.0.1+driver for kernel 5.15.0-1042-gke (x86_64)
Wed Oct  4 18:22:10 UTC 2023
'/tmp/falco-dkms-make' -C /lib/modules/5.15.0-1042-gke/build M=/var/lib/dkms/falco/5.0.1+driver/build modules
make[1]: Entering directory '/host/usr/src/linux-headers-5.15.0-1042-gke'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
  You are using:           gcc-5 (Debian 5.5.0-12) 5.5.0 20171010
  CC [M]  /var/lib/dkms/falco/5.0.1+driver/build/main.o
gcc-5: error: unrecognized command line option '-mharden-sls=all'
make[2]: *** [scripts/Makefile.build:297: /var/lib/dkms/falco/5.0.1+driver/build/main.o] Error 1
make[1]: *** [Makefile:1909: /var/lib/dkms/falco/5.0.1+driver/build] Error 2
make[1]: Leaving directory '/host/usr/src/linux-headers-5.15.0-1042-gke'
make: *** [Makefile:16: all] Error 2
install: /usr/lib/gcc/x86_64-linux-gnu/6/
* Trying to dkms install falco module with GCC /usr/bin/gcc-6
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'/tmp/falco-dkms-make'...(bad exit status: 2)
* Running dkms build failed, dumping /var/lib/dkms/falco/5.0.1+driver/build/make.log (with GCC /usr/bin/gcc-6)
DKMS make.log for falco-5.0.1+driver for kernel 5.15.0-1042-gke (x86_64)
Wed Oct  4 18:22:11 UTC 2023
'/tmp/falco-dkms-make' -C /lib/modules/5.15.0-1042-gke/build M=/var/lib/dkms/falco/5.0.1+driver/build modules
make[1]: Entering directory '/host/usr/src/linux-headers-5.15.0-1042-gke'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
  You are using:           gcc-6 (Debian 6.3.0-18) 6.3.0 20170516
  CC [M]  /var/lib/dkms/falco/5.0.1+driver/build/main.o
gcc-6: error: unrecognized command line option '-mfunction-return=thunk-extern'
gcc-6: error: unrecognized command line option '-mharden-sls=all'; did you mean '-mhard-float'?
make[2]: *** [scripts/Makefile.build:297: /var/lib/dkms/falco/5.0.1+driver/build/main.o] Error 1
make[1]: *** [Makefile:1909: /var/lib/dkms/falco/5.0.1+driver/build] Error 2
make[1]: Leaving directory '/host/usr/src/linux-headers-5.15.0-1042-gke'
make: *** [Makefile:16: all] Error 2
install: /usr/lib/gcc/x86_64-linux-gnu/8/
* Trying to dkms install falco module with GCC /usr/bin/gcc-8
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'/tmp/falco-dkms-make'...(bad exit status: 2)
* Running dkms build failed, dumping /var/lib/dkms/falco/5.0.1+driver/build/make.log (with GCC /usr/bin/gcc-8)
DKMS make.log for falco-5.0.1+driver for kernel 5.15.0-1042-gke (x86_64)
Wed Oct  4 18:22:12 UTC 2023
'/tmp/falco-dkms-make' -C /lib/modules/5.15.0-1042-gke/build M=/var/lib/dkms/falco/5.0.1+driver/build modules
make[1]: Entering directory '/host/usr/src/linux-headers-5.15.0-1042-gke'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
  You are using:           gcc-8 (Debian 8.3.0-6) 8.3.0
  CC [M]  /var/lib/dkms/falco/5.0.1+driver/build/main.o
gcc-8: error: unrecognized command line option '-mharden-sls=all'; did you mean '-mhard-float'?
make[2]: *** [scripts/Makefile.build:297: /var/lib/dkms/falco/5.0.1+driver/build/main.o] Error 1
make[1]: *** [Makefile:1909: /var/lib/dkms/falco/5.0.1+driver/build] Error 2
make[1]: Leaving directory '/host/usr/src/linux-headers-5.15.0-1042-gke'
make: *** [Makefile:16: all] Error 2
* Trying to load a system falco module, if present
Consider compiling your own falco driver and loading it or getting in touch with the Falco community

Environment
GKE

Falco version: 0.35.1

System info: GKE 1.26.9

Cloud provider or hardware configuration:
OS: ubuntu 22.04.3

Kernel: 5.15.0-1042-gke

Installation method: Docker image: falcosecurity/falco-driver-loader:0.35.1

Additional context

Running falco-driver-loader for: falco version=0.35.1, driver version=5.0.1+driver, arch=x86_64, kernel release=5.15.0-1042-gke, kernel version=47
Running falco-driver-loader with: driver=module, compile=yes, download=yes

Would you be able to try Falco 0.36.0? Or is there some other issue that prevents you from running 0.36.0?

@LucaGuerra , I'll give that a try, but I'm still not seeing a falco kernel driver (5.0.1, 6.0.0, or 6.0.1) matching kernel release 5.15.0-1042-gke

@nfaust-edb would you mind trying the modern-bpf? I've seen that you are using docker as installation method, this is the command to run Falco with the modern-bpf https://falco.org/docs/install-operate/running/#modern-ebpf

@LucaGuerra ,
Results for upgrading to falco 0.36.0.  The kernel driver still isn't available for download, but the compile is working.
I'm in the process of upgrading my falco deployment from 0.35.1 >> 0.36.0.
% kubectl logs -n falco falco-5zpsn -c falco-driver-loader
* Setting up /usr/src links from host
* Running falco-driver-loader for: falco version=0.36.0, driver version=6.0.1+driver, arch=x86_64, kernel release=5.15.0-1042-gke, kernel version=47
* Running falco-driver-loader with: driver=module, compile=yes, download=yes

================ Cleaning phase ================

* 1. Check if kernel module 'falco' is still loaded:
- Kernel module 'falco' is still loaded.
- Trying to unload it with 'rmmod falco'...
- OK! Unloading 'falco' module succeeded.

* 2. Check all versions of kernel module 'falco' in dkms:
- OK! There are no 'falco' module versions in dkms.

[SUCCESS] Cleaning phase correctly terminated.

================ Cleaning phase ================

* Looking for a falco module locally (kernel 5.15.0-1042-gke)
* Filename 'falco_ubuntu-gke_5.15.0-1042-gke_47.ko' is composed of:
 - driver name: falco
 - target identifier: ubuntu-gke
 - kernel release: 5.15.0-1042-gke
 - kernel version: 47
* Trying to download a prebuilt falco module from https://download.falco.org/driver/6.0.1%2Bdriver/x86_64/falco_ubuntu-gke_5.15.0-1042-gke_47.ko
curl: (22) The requested URL returned error: 404
Unable to find a prebuilt falco module
install: /usr/lib/gcc/x86_64-linux-gnu/12/
* Trying to dkms install falco module with GCC /usr/bin/gcc
Sign command: /lib/modules/5.15.0-1042-gke/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Certificate or key are missing, generating self signed certificate for MOK...
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
Creating symlink /var/lib/dkms/falco/6.0.1+driver/source -> /usr/src/falco-6.0.1+driver

Building module:
Cleaning build area...
'/tmp/falco-dkms-make'.....
Signing module /var/lib/dkms/falco/6.0.1+driver/build/falco.ko
Cleaning build area...

falco.ko:
Running module version sanity check.
depmod...
* falco module installed in dkms
* falco module found: /var/lib/dkms/falco/6.0.1+driver/5.15.0-1042-gke/x86_64/module/falco.ko
* Trying to insmod
* Success: falco module found and loaded in dkms

Thank you for the feedback! In any case, if there are no drivers for your kernel you could always use the modern-bpf. It should work out of the box.
I will close this, if there are further issues feel free to re-open!


server error 500 after debug=false

Describe the bug
The project runs quite fine when debug=True in settings.py but after debug=false it shows server error 500.
Additional context
Stackoverflow and other articles are useful for resolving the bug.

I am interested

Go ahead @Amit366 and can you plz tell me the program under you are participating.

The program is DWOC

Can you tell me which file should I look into?

Can you tell me which file should I look into?
settings.py looks like creating this problem.

I am getting error that the python version needs to be updated

The error is No name 'config' in module 'decouple'pylint(no-name-in-module)

Could you please help me in this

The error is No name 'config' in module 'decouple'pylint(no-name-in-module)

you need to install requirements so that required packages get istall

I did install the packages but still it is showing this error

can you show me the screenshot of error so that it will be easier for Me to solve

Ok I will show it tomorrow

This is the error.

@harsh-9in i am interested in this issue.

This is the error.

@harsh-9in i want to know that we need run it locally and then correct it or deploying it on heroku and then run it.Because i find that your project is no problem when debug==false and i commented out these two lines import django_heroku and django_heroku.settings(locals()).So the problem is with heroku .

Do we need to signup on heroku for this.

Do we need to signup on heroku for this.

no you don't need to do this.

@harsh-9in i want to know that we need run it locally and then correct it or deploying it on heroku and then run it.Because i find that your project is no problem when debug==false and i commented out these two lines import django_heroku and django_heroku.settings(locals()).So the problem is with heroku .

are you able to run the project locally when debug=false?

yes i am able to run the project locally even when debug==false when i commented out these two lines from setting.py file
import django_heroku and django_heroku.settings(locals()

okk fine can you create a pr so i can review the code.

@harsh-9in ,I have made the PR. Please check it out.

@harsh-9in ,I have made the PR. Please check it out.


Latest version not found on pypi?

$ pip install django-after-response==0.2.2
Collecting django-after-response==0.2.2
  Could not find a version that satisfies the requirement django-after-response==0.2.2 (from versions: 0.1.0, 0.1.1, 0.2.0, 0.2.1)
  No distributions matching the version for django-after-response==0.2.2

I had to install from git to get 0.2.2:
$ pip install git+git://github.com/defrex/django-after-response@98e00c766b5160b529a4ef810412eb9d2e6fc9a3

Should be up there now.

Yup, looks like it's up there now. Thanks @defrex !


Layers in Nextdraw

Please describe your feature.
What if there are is layers in Nextdraw , where you can select between the position of the shape in the vertical direction . In the form of STACK.
Describe the solution you'd like
Need to discuss
Additional context

Every stack element is having shapes in it . If some one want to move one shape from one layer to another , he/she have to move it using the layer changing button .

Can we do something like whenever bring to front button is clicked we get the elements object from the local storage and change the order of the I'd that you've given to each element (#0,#1,#2..) and put it back to local storage?

That seems preety good idea . We can do this , in such . For this we have to change the current State of the website , where the elements are stored . (Local storage , is a storage that is only used to get the elements when we reopen the website and loads the locally stored data of the previous session) .

Basically we have to take care of elementsStore

ShapedCache (May be) as the id's will be changed .

Assigning you .


AudioSink is not updated when audio source component is replaced

Bevy version
bevy = { version = "0.12.1"}

What you did
Here is the code I have problems with:
https://gist.github.com/rambip/43a977c833edef252ae7e3d17203287a
To resume, I:

create a custom audio source like in the "decodable" official example
add it as a component to start playing it
change the component with another audio source
set a control on the space bar to play and pause the sink associated with the entity

What went wrong
I expected this code to play and pause the lowest-pitch sample.
But it plays nothing.
I tried a few other experiments (like rechanging the audio-source to the original one, and then it worked)
I found a way to do what I intended: forcing the sink to be destroyed when I change the source.
Discussion
I don't think it is the expected behaviour, or at least I think it is very confusing. My take is that the Sink should be removed when you insert an audio-source on an entity that already has one.
The user should know how the sinks are created and modified when the sources are spawned. Otherwise you quickly run into strange behaviours that are hard to debug.

So this, counter-intuitively, the expected behavior. AudioSource is only queried as Added, and re-inserting the component does not count as added, just mutated. This means that we don't catch the re-insert in your change_sound system.
Perhaps the solution is to also take mutations into account, and checking if the source is the same as the one still playing, but unless we have some sort of diffing system I don't see how we can efficiently implement that.
There is a draft PR (#12035) which allow re-using a sink, which would allow you to be able to change the source to a different Decodable instance like you want


Some unit tests require Administrator privileges/specific users prevent

Type  Bug
NLog version: Latest
Platform: ..Net 4.5, but I assume all
In case of a BUG:
When running unit tests, there are lots of tests that fail, which came as a surprise since I just cloned NLog and had changed nothing.
Some tests try to create a file in C:, which is only allowed if you are an administrator, which again require that you start VS with "Run as Adminstrator".
Some tests fail because you cannot create event log sources as a non-administrator.
Two tests in ImpersonatingTargetWrapperTests fail even if you run as administrator because it require specific users present on the system.
It would be nice if all tests could run as a regular user, but I can understand that some tests require Administrator permissions, but perhaps those should be tagged with a category, "RequireAdministratorPermissions", so that when you run them and they fail, you know that it could be the reason why its failing.
In regards to the ImpersonatingTargetWrapperTests - since a lot of tests already require administrator permissions, I guess the tests could create a user on the local system if its not already present, I'm sure there uis a DllImport somewhere that can create a user.

Some tests try to create a file in C:, which is only allowed if you are an administrator, which again require that you start VS with "Run as Adminstrator".

Well in the past we also skipped writing those test, but we got some bugs when writing to the root. So know we think it's better to have those unit tests then buggy code.

those should be tagged with a category, "RequireAdministratorPermissions", so that when you run them and they fail, you know that it could be the reason why its failing.

That is a good idea! PR would be nice!


Idea: Rename feeds

For various reasons feeds could have an uninformative name, for example when subscribed to subfeeds of publications, which cover only part of a topic but their name doesn't show that. There are quite a few scenarios.
I propose being able to change the display name of a feed.

@tschellenbach What are your thoughts on this / how to implement?

Since there hasn't been any activity around this topic, we're going to close the issue. Please submit a PR if you're interested in adding this functionality. Thank you!


Create a timeline

Add a list of all your activities, achievements, work experience. Add as much info as you can remember. In case you don’t have working experience tell about your pet-projects or student projects. Don’t be shy :)

Find all the work experience

Making a list of experiences

There are the most important experiences


Diagnose source of duplicated Iris warnings

Steps

[x] Diagnose
[x] Write up
[x] Discuss with Iris devs to decide on next steps to fix

Possible causes:

Once per file
Once per NetCDF variable
Once per Dask worker
E.g. Some work happens within a NetCDFDataProxy, and there is one of these per chunk
Use of generators

Finding examples

Try loading some of the iris-test-data files
Read the Iris CI output (example)
Get a list of warnings generated by Iris, then check them with users for familiar 'culprits'

out.txt
Took the warning summary from a recent Pytest run to take a look at this.
15717 warnings in total, 882 lines in the file. A few highlights

8 unique external Deprecation Warnings (30 total)
9 unique internal IrisDeprecation warnings
69 separate UserWarnings, although some of these are almost the same warning (warning for x coord vs y coord for example)
42 Seperate instances of the FutureWarning about netCDF load datum.

After conducting some experiments, I'm now of the conclusion that iris isn't doing anything wrong in the way that it is using the builtin Python warnings module.
I used the following simple script as the basis of the investigation:
import iris

dname = "/home/h05/itwl/projects/git/iris-test-data/test_data/NetCDF/mercator"
fnames = ["false_east_north_merc.nc", "non_unit_scale_factor_merc.nc", "toa_brightness_temperature.nc"]

for fname in fnames:
    print(fname)
    _ = iris.load_cube(f"{dname}/{fname}")

(Note that, this script was call with python -Wd warnings.py for the normal default warnings behaviour, and python -Wo warnings.py for the once warnings behaviour)
Which should generate the following single warning to the console, but instead it occurs 3 times, once for each netCDF file loaded:
FutureWarning: Ignoring a datum in netCDF load for consistency with existing behaviour. In a future version of Iris, this datum will be applied. To apply the datum when loading, use the iris.FUTURE.datum_support flag.

This warning is generated as part of the iris load pipeline in iris.fileformats._nc_load_rules.helpers._get_ellipsoid
The approach taken was to reduce the functionality within the iris load pipeline to the point where the duplicate warnings generation stopped, hence attempting to identify the root cause of the issue.
Initial "hunches" of culprits revolved around:

the use of the threading module for iris futures support
using the generators pattern throughout the loading pipeline
use of itertools

i.e., this is all seeded by the statement in the warnings documentation that the warnings.catch_warnings context manager is not thread safe.
Note that, the warnings module as part of its implementation injects the __warningregistry__ dictionary into the global namespace of the executing process. This dictionary keep the state of issued warning by the client and is used by warnings to filter warnings as part of its advertised behaviour.
It was observed that the ID object instance of the __warningregistry__ did not change during loading runs, but the contents of the registry was reset; a cause for concern and perhaps an explanation of the behaviour that we're witnessing in iris.
Essentially, I was able to eventually able to incrementally turn-off all of the iris loading pipeline but still maintain the high level call tree and witness the same duplicate warning behaviour by injecting new warnings at different stages of the loading pipeline call tree.
In essence, we see duplicate warnings and yet not call any of the iris loading infrastructure code; confusing and concerning.
Stripping the problem right back to the bare bones, the following script behaves as expected generating only 1 warning for both -Wd and -Wo:
import warnings

for _ in range(5):
    import iris
    warnings.warn("oops!", category=UserWarning)

However, the following pattern generates 2 warnings for both -Wd and -Wo:
import warnings

for _ in range(5):
    warnings.warn("oops", category=UserWarning)
    import iris

i.e., importing iris after generating a warning causes this behaviour.
Note that, this behaviour is also observed when importing matplotlib, numpy, cartopy and netCDF4 instead of iris.
However, this is not the case when importing dask. Odd.
Conclusion
@stephenworsley Has in parallel uncovered that this type of behaviour is a know bug with warnings (he can write his findings up to support this)
The behaviour that I've witnessed through this investigation leads me to the conclusion that iris isn't doing anything wrong per se, but though our heavy use of warnings we are exposing this bug with the side-effect of generating duplicate warnings messages to the console.
My recommendation is to now investigate community work arounds, assess those, and choose the best workaround for iris, which we are willing to support and maintain in the code base.

A probable source for this issue appears to be a bug with the warnings.catch_warnings context manager in python https://github.com/python/cpython/issues/73858 .
Looking through responses to this issue, it appears that there exists a relatively simple workaround using functools.lru_cache as demonstrated here:
https://github.com/karlicoss/promnesia/commit/78e7d73b40c88c4c0374cd9a495d2347017f4b55#diff-d29a3e5d675970f57a9788e5104d7f47831449ac62ff7441dddfd6491a4ddcdaR80

Also worth noting, when I stepped through loading code, this appears to be where the context manager gets called in iris code: https://github.com/SciTools/iris/blob/b6e39d758fc17e167b9323b25484965453846dbf/lib/iris/fileformats/_nc_load_rules/helpers.py#L417-L431


Try to solve issue 3417.

Add two tests first for #3417. Close #3417.

Setting normalize_comments and wrap_comments to true no longer imply setting format_doc_comments. And I wonder should I change the option format_doc_comments to format_code_in_doc_comments or just change the description of the option?

Travis CI build break because of rand crate has format_doc_comments in rustfmt.toml.

The code change looks good to me @xiongmao86
With the stability guaranty of rustfmt, we can't simply rename the option: rand's build failure is a good example. A possible solution would be to introduce the concept of options "aliases":

an option, here format_doc_comments, can be used with another name, here format_code_in_doc_comments
the first variant of the option's name would be marked as deprecated and removed in a major release.

@topecongiro What do you think of such a mechanism ? Just improving the format_doc_comments description could be enough for this issue, but I think a more obvious option's name would be good.

With the stability guaranty of rustfmt, we can't simply rename the option

All of these are unstable options though, so I'd expect it to be fine to play with naming / values until stabilized?

Appveyor build fatal: unable to access 'https://github.com/rust-lang/rustfmt.git/': Could not resolve host: github.com
May be failed because of network accessibility. How can I retry testing?

@RReverser ahah indeed ;oD that comment can be discarded then!

I believe mentioning the name change in the CHANGELOG should be good enough.

How to deal with that problem?

Given both options are unstable, nothing needs to be done. The behaviour of wrap_comments implying format_code_in_doc_comment was wrong to begin with.

@RReverser @scampi @topecongiro, Thank you for helping and reviewing my commit. What should I do to get the pull request merge?

Given the discussion above, I'd say rename the option back? (I see you reverted that change)

Only rand build in Travis CI failed. I think this is probably good to go. @scampi, @topecongiro, What do you think?

@xiongmao86 Sorry for the late review. LGTM, thanks!


New notebook

New documentation reffering to plotting.py.

@FloraSauerbronn please let me know when this one is ready for review. Don't worry about the CIs failures for now, focus on the doc text and examples only.

@ocefpaf is ready. I've already shown it to Calumn a couple of weeks ago to see if the text fit the documentation. Yesterday, I just corrected the example of the new axis in the CTD plot.

pre-commit.ci autofix

@ocefpaf
Actually something went wrong. The notebook that was merged was not the one that I've recently updated.

@ocefpaf Actually something went wrong. The notebook that was merged was not the one that I've recently updated.

It has some edits but it is based on your work. The text was too heavy on descriptions and did not made use of the dataframe methods (the whole reason we added pandas_flavor) vs imported functions.


Reporting members of SCF

This work is based on @gvwilson work in #577.
This fixes #539.
Comments welcome!

:+1: from me


Update index.md

Just added a missing word

@bkokash : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Show LO confirmation alert based on toggle

Jira issue:
https://glia.atlassian.net/browse/MOB-2707
What was solved?
This PR will take into account the possibility of toggling out LO confirmation alert, meaning that engagement can start without explicitly allowing LO. The toggle is fetch from the site information
Release notes:

[ ] Feature
[X] Ignore
[ ] Release notes (Is it clear from the description here?)
[ ] Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

[ ] Tests fixed, added? Unit, acceptance, snapshots?
[ ] Logging necessary for future troubleshooting of customer issues added?

Screenshots:

!squash


Suggestions for dynamic selectors

Running the o1vm with this code seems to work.
cc @Fizzixnerd

Rebasing on top of https://github.com/o1-labs/proof-systems/pull/2589 and amending the commit messages to a better description.

I'm adding regression tests, in particular for the degree of the constraints. This PR doesn't include any.


#1791 - Enable Assessments tab view and NOA view for Public Institution Users - Part 1

Created Institution assessment summary page with student appeal, exception, and original assessment (NOA in next PR)
moved shared logic to controller.service file
updated caniuse-lite

moved/created application details component/views to applicationDetails/
Added notes part of appeal and exception for public users as I got confirmation from @JasonCTang . (but double checking with @JasonCTang, if to hide it or not, if it's to hide I will do it as part of the next PR because student view does not have a note section)
- UPDATE - got an update from @JasonCTang to hide the note, I will be hiding it in my next PR.
Student appeal view will be updated as part of the next PR
As per Figma, the request forms don't have a sidebar but the current ministry view has a sidebar, so keeping the institution the same as the ministry,

Screenshots,

Next PRs
PR 2. Remaining request form views and NOA views
PR 3. e2e tests

Great work @ann-aot. Added few minor comments.


Update StackBuilderSchema.designer.cs

add xmlAnalysis.allowedBoxPositions with XmlFileLoader.cs.

It's bug.


Connection Failed

I would like to use this great API in my project, but when browsing your demo's on CodePen i occasionally get a "Connection Failed" error to the Yahoo API. It seems a bit unstable. Am i the only one getting these errors ?

Same issue since last week  :  'There was a problem retrieving the latest weather information'. Yahoo weather API not stable ?

Yahoo's API has been pretty unstable. Their developer console was also throwing errors for most of today but everything seems to be back up now. The console is located at https://developer.yahoo.com/weather/ and is always worth checking there if it seems down.

Happening to me too. Often.

Happening a lot to me too.

The best alternative if Yahoo is proving too unstable is to use another weather API like https://darksky.net/dev/docs or https://openweathermap.org/api. Both require creating an account and using an API key which is why simpleWeather has never switched.


Implement ability to directly prime the cache

This PR implements a new prime(key, value) API that directly primes the cache with a given key and value.
This is mentioned in #2 as a way to enable building a two-way cache, but I think a more basic motivation for this API would simply be to allow cache pre-warming. Another use case I have for this is to allow creating a DataLoader subclass that implements loadAll() (https://gist.github.com/ryanspradlin/1e951a4dcf737e3fb194).

Looks like this build is failing right now just due to the babel-eslint/escope issue: https://github.com/babel/babel-eslint/issues/243 (fixed in newest babel-eslint).

Here's a PR to upgrade the babel-eslint dependency: #19

Friendly bump -- any thoughts on this PR?

Sorry for the delay on this. Last time we discussed this we were concerned about the race-condition case where a current request is already outbound when prime is called. In other words, what should the behavior of prime be the promise cache already has a value in it for the given key? It could be possible for a get, prime, get call to happen in that order such that the two subsequent gets do not result in the same value, which could cause issues.
I think the uses of building a two-index cache and pre-warming a cache are in some ways at odds with each other.
Maybe the right way is to do nothing if they key already exists? That way you would have to explicitly declare if you wanted to forcefully prime the cache with loader.clear(key).prime(key, value).

Apologies for the delay on my end this time. Thanks for the feedback -- that makes sense, and your suggestion sounds great to me. I've updated the PR to reflect the new logic (priming an existing key will do nothing), and updated the documentation and tests to match.
Thanks!

Coverage remained the same at 100.0% when pulling 5e21df616533047561f01ec2e68ee9a9dce5e33a on ryanspradlin:features/prime into a57c44f214a4445194264e2f9fd32375e6f66303 on facebook:master.

Excellent work!


Lack of token permission should state all scope requirements in error message, instead of causing multiple adjustment roundtrips

Hello there, and thanks for this very helpful action!
I just had my "add newly created issues and PRs to a project" workflow fail that's based on actions/add-to-project@main:
Request failed due to following response errors:
 - Your token has not been granted the required scopes to execute this query. The 'projectV2' field requires one of the following scopes: ['read:project'], but your token has only been granted the: ['repo', 'write:org'] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.
 - Your token has not been granted the required scopes to execute this query. The 'id' field requires one of the following scopes: ['read:project'], but your token has only been granted the: ['repo', 'write:org'] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.

Ok, easy enough, I guess with the latest changes to the whole projects API some things changed, no prob, dutifully obliged. Added read:project as instructed, reran the failed action. Which then failed again with:
Request failed due to following response errors:
 - Your token has not been granted the required scopes to execute this query. The 'addProjectV2ItemById' field requires one of the following scopes: ['project'], but your token has only been granted the: ['read:project', 'repo', 'write:org'] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.

Doing that as well, then rerunning, and things are finally green again.
However, it raises the question, is there any way to maybe ask for all required scopes right away to guarantee an error free operation, instead of sending me on multiple errands and also briefly making me doubt my sanity? 😅

I agree. Sorry for my confusing reply.

👋 Thank you for reporting this issue! I agree that our messaging here is somewhat confusing and could be improved. I've created an issue in our internal backlog to make sure that this gets passed along to the right team and handled accordingly. Thank you again for your feedback, and please feel free to add any additional information to this issue!


Error in rewritten selector when styling distributed children (::content)

Hi,
I started a <gold-password-input> which is without surprise based on a <paper-input-container> and includes an additional addon that takes care of displaying the strength score of the password.
You could find the page of the element (and the demo) here.
Depending on the strength score, I apply different classes on a subelement of the strength addon element to change the text color. The different classes are correctly applied but when the input has focus, the selector rule defined in the  is overriding the local DOM selector.
See the following screenshot that you can reproduce on the demo page of the component.
Non Working

Working (because the elements have two classes...)

Working (when the input looses focus)

This is the way <paper-input-container> defines the CSS with the highlighted addon:
      .add-on-content.is-highlighted ::content * {
        color: var(--paper-input-container-focus-color, --default-primary-color);
      }

This is the way I define my CSS on the addon:
      .None {
        color: var(--gold-password-input-strength-meter-none-color, --paper-grey-700);
      }
      .Very.Weak {
        color: var(--gold-password-input-strength-meter-veryweak-color, --paper-red-700);
      }
      .Weak {
        color: var(--gold-password-input-strength-meter-weak-color, --paper-orange-700);
      }
      .Medium {
        color: var(--gold-password-input-strength-meter-medium-color, --paper-yellow-700);
      }
      .Strong {
        color: var(--gold-password-input-strength-meter-strong-color, --paper-blue-700);
      }
      .Very.Strong {
        color: var(--gold-password-input-strength-meter-verystrong-color, --paper-green-700);
      }

Any idea why this happens?
Cheers,
Pascal aka MeTaNoV

The paper-input-container rule has two classes, so I'd expect that to trump the single selector (.Weak). Have you tried just adding another class (or an ID) to the strength meter, so it's
.stength-mether.Weak

or:
#meter.Weak

Sound weird to have to do this... but I suppose it will do the job! As a work around I used myself !important but I am not sure 100% it should be this way... Thanks for your tip @arthurevans !

Shouldn't the definition of <paper-input-container selector remove ::content since it uses * selector?

Also imagine a case where I defined the following selector in my-element
.class1 .class2 ::content * { ...some style }

then a content sub-element styling has no way to win the specificity race against it? Doesn't this break somehow the styling encapsulation we want or I misunderstand the problem?

@arthurevans , after investigation, I found out this in the Polymer Documentation about Styling:
"
Under shady DOM, the <content> tag doesn’t appear in the DOM tree. Styles are rewritten to remove the ::content pseudo-element, and any combinator immediately to the left of ::content.
"
This style rewriting is in line with my previous comment, and is not properly done in my example.
In my case:
      .add-on-content.is-highlighted ::content * {
        color: var(--paper-input-container-focus-color, --default-primary-color);
      }

is rewritten to
.paper-input-container-0 .add-on-content.is-highlighted.paper-input-container *
instead of
.add-on-content.is-highlighted.paper-input-container *
which will solve therefore the issue!
@ebidel I browsed the opened issues w/o finding any good similar candidate, is it an issue you know of?


Add tests for exponential extrapolation

Context: The last PR (first, second) to add exponential extrapolation capabilities to catalyst.
Description of the Change: This PR ensures that pennylane.transforms.exponential_extrapolate works inside catalyst's mitigate_with_zne function.
Benefits: ZNE has increased functionality.
Possible Drawbacks: As part of the testing, I've removed 0.1 and 0.2 from the list of values being used to create different circuits. This is because exponential extrapolation is not necessarily as stable as polynomial fitting. For example, when extrapolating near constant values exponential extrapolation can struggle due to the fact that a linear fit is first performed to understand the "direction" (or sign) of the exponential. If the slope is positive, the data is flipped to fit something that looks like $A\mathrm{e}^{-Bx} + C$ where $B\in\mathbb{R}_{> 0}$.
An example of this happening can be seen here.
>>> exponential_extrapolate([1,2,3], [0.3894, 0.3894183, 0.38941])
-1.0000000000000059e-06
>>> richardson_extrapolate([1,2,3], [0.3894, 0.3894183, 0.38941])
0.3893551000000072

If we want to ensure to continue testing values 0.1 and 0.2 for polynomial extrapolation, we can create separate tests. Let me know what would be best.
Related GitHub Issues:
fixes https://github.com/PennyLaneAI/catalyst/issues/754

just pinging @rmoyard / @dime10 / @josh146 in case y'all didn't see the discord message.

Closes https://github.com/PennyLaneAI/catalyst/issues/754

@rmoyard just added a snippet to the changelog, and added a missing docstring to satisfy CI. Feel free to take another look, or merge!


Support reloadOnChange and add better validation

Previously, TwilioClientOptions and TwilioRequestValidationOptions would be configured during startup and would not automatically change when the .NET configuration is changed.
With these changes, these options will update when configuration from configuration sources with reloadOnChange enabled are changed.
Additionally, the options are now validated using the built-in validation APIs.
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

Thank you @IEvangelist for the guidance and support!

I added the recommended overload following options guidance for library authors: https://learn.microsoft.com/en-us/dotnet/core/extensions/options-library-authors
Closes #117


Possibility to change affinity rules

Is it possible to define a specific PVC so that the underlying volume can be created/attached on more than one node ? what i mean is basically to change the affinity rule:

i need to define a localpath for some sort of "cache volume"
the cache volume does not need to be defined on a specific host
in fact if a node goes down, i would like the Pod to be able to re-spawn on another node and create the volume there
once the node comes back up, the older volume can be picked up without no issue

is this possible ?

i need to define a localpath for some sort of "cache volume"

Do you mean you don't care about the data loss?

exactly, i know that 99% of the time the pod and the local volume will reside on the same node, except from when that node is down (1% of the time). in such instance then the pod is allowed to start on another node.
data loss is a minor concern in cache systems, however i would still like this cache to be persisted on a local volume most of the time

Is it possible that we can write some setup/teardown scripts to copy/sync data from old node to new node ?
such that pods can be automatically migrated to other nodes.

hi there any update?


Can't download doc over HTTP

Details
Download links (PDF/HTML/EPUB) lead to a "Fail.  Check back in a bit!" when trying to access them in HTTP. Since the navigation is in HTTP by default when coming from the project page, I guess it's not the intended behaviour.

Both the links on the dashboard and the links from doc pages download the generated docs okay for me. Is this still a problem for you? Both requests should redirect to HTTPS pages, but I don't think that would be an issue.

My bad, the browser won't follow the redirection of HTTP links from the doc pages, but requesting the same links from the command line works. It seems that the problem comes from my side, maybe some issue with our corporate proxy. Thanks !

Interesting. Well feel free to include more information if you have any. It might be an issue on your side, but something we can address on our side. Chances are you aren't the only one noticing the problem.


Allow creategroup command to take weight and display name as optional arguments

An idea I've been having for a while (mainly for the weight), and a possible solution for #2696 :)

Looks good, thanks!


Adding parse tree support for parsing select statements

Adding improvements to the query language parsing.

Adding a command, SelectCommand.
Adding an interface, Expression to aid the evaluation of the time series. No implementation is given yet.
Adding go logic around select... statement grammar tree. Not done yet.
Adding additional node structs, parser helpers, etc.
Moving a block of parser tests to test command generation also.

@achow

This PR looks big, but it's (mostly) the language change.


Allow VuePDF component to also handle data loading state

Currently the VuePDF component emits an event (loaded) when loading is done and has a slot for showing content while loading. This "loading" only pertains to rendering the page however. I think most time is usually spent loading the actual PDF file from the server.
It is possible to track said state separately using the onProgress callback from usePDF but it would be nicer if the VuePDF component could also handle that so you just have to provide the loading text/spinner.
So for example, rather than doing this:

<template>

Loading...

	<VuePDF v-else :pdf="pdf">

Loading...

	</VuePDF>
</template>

One would be able to do this:

<template>
	<VuePDF :pdf="pdf" includeDataLoading>

Loading...

	</VuePDF>
</template>

Note: I am still new to using VuePDF so if there already is a better way to do what I want to do here: my apologies.

The issue here is that VuePDF is a page component, so that loaded event and the loading slot are for the page not for the document.
Some sort of document features could be implemented using usePDF and pdf.js but most of them are more like application's requirements than feasible features for this package.


Fix/location tracking activity to component activity

Update the LocationTrackingActivity to be a ComponentActivity to make it consistent.

And we can migrate the theme to not using AppCompat to fully get rid of AppCompat.
https://github.com/googlemaps/android-maps-compose/blob/e43b9383c8d686660a924a379bc30b180949bebe/app/src/main/AndroidManifest.xml#L28-L28


Move status keeper into jockey file

Currently, status_keeper.py handles the caching of the local Juju status.  This file needs to be merged into jockey.py, as there is not a good reason for it to be separated out.

This may not be necessary if #6 is closed, given that the entire application would be bundled as a static executable. The one-file program requirement would become nil and you could expand out to several files and modules for organization purposes.

I agree that #6 resolved this.
This issue is now stale and I am closing it.


Handle sbt distributions containing non-standard folder names

Some sbt distributions have different folder names inside their tarballs. For example sbt-0.13.13.tgz distribution contains a folder named sbt-launcher-packaging-0.13.13 whereas the sbtenv libexec scripts expect just sbt.
This PR changes the sbtenv-install script to rename the extracted folder to sbt.
Fixes #20.

@all-contributors please add @j1mr10rd4n for code


This is an empty commit to test running comparison benchmarks

/run-benchmark

/run-benchmark

/run-benchmark


Get zld compiling with latest version of zig

Tested with 0.10.0-dev.5908+cd435211d
This was just me going through compile errors and fixing things as reasonably as possible with no information about the context of the problems I was fixing - as naively as possible. Hopefully this is actually helpful!

Oh oops, apologies @moosichu I didn't see you submitted a PR! I've resolved those already in 7da0f2eca3595d91c7a503c5398faadb65a4e2b2 :-)


Parity: MeasurementFormatter, DateComponentFormatter

ICU currently doesn’t have a C header or implementation for these. Mark as unavailable until we do.

@swift-ci please test


Flaky behaviour in settings with large enum

Issue Type: Bug
I've written an extension and one of the settings selects from a large number of strings that name CSS stylesheets. When editing in settings the picker behaves erratically with a populous enum. Originally it had 90 items. Culling it to 30 improved things but it's stilly flaky. This has nothing to do with my extension code; it happens before my code is loaded or activate is called.

VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 x 3293)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_offsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.87GB (2.18GB free)

Process Argv

Screen Reader
no

VM
0%

FYI @cleidigh

Hey @roblourens
I can look at this tomorrow, it seems most likely it's  in selectBox.
If I can reproduce it I will report/fix-it.

@roblourens
I did a quick and dirty test artificially adding 40,90,180 options to Auto File Save with selectbox.  This did not present any discernible problem ,  but probably does not match the issue closely enough.  I can do two things , make a hello world extension with a large enum setting or:  another slightly different test would be to artificially expand a built-in setting.  Both experiments might be necessary.
@roblourens  any particularly easy setting to do this?

I also have https://github.com/Microsoft/vscode/issues/69306 which I think is caused by changing the setting then immediately reopening the dropdown. I see some different behaviors, sometimes it shows up attached to the wrong setting. There is also an issue that sometimes the editor scrolls down a bit after changing a setting. These are on me and there may not be a new issue from having lots of items in a dropdown...

@roblourens
yeah, I've seen some of the oddities.  I was going to post an issue regarding Alt-Down  which should open drop downs, but sometimes goes off elsewhere.  If that's a duplicate, I will post.
I just saw the following glitch which I will look into.  There may be multiple issues.  One thing I am looking at is layout changes either from zoom or having to open to the top.  I will keep looking at this book because I do think there is at least some issue with selectBox even if it does not relate to the number of items.
Last note:  In the screenshot below you can see an erroneous description attached to the cursor style, is that something you have seen when you say "attached to a different setting" ?

@roblourens
This glitch almost seems to have retained the height calculations from a longer list (viewed prior)  along with doing zooming.

Yes! That is exactly the behaviour I've been seeing. Is something stored in a wrong scope? Or at the right shared but not updated appropriately?

Hello Australia!
I think both @roblourens and myself believe this might be some combined issues.  Knowing the selectBox as I do and after some experiments, I do not believe the number of items is the direct cause.
Probably 30 items just fits under the drop-down IF the drop-down is nearer to the top of the screen.  If the drop-down needs to flip up, or a zoom is done, a relay out as necessary and somewhere in that is where I think there is at least one of the issues.

@PeterWone
our post just crossed your observations do seem to line up with my comments above.

Yes I agree.

Yes I agree.

So where might that fit in the ten thousand things on your list? :)

@roblourens
I am going to spin a configuration where the drop down will NOT allow flipping up to eliminate one layout scenario for experimentation.  Since we think there might be more than one thing going on here,  Do you want to post a branch which you can also use in your experiments?

I don't think I've seen it go off to the side like that. Do you have good repro steps?
One thing that's different recently with the new list is that when it is rerendered, it's more likely to render a setting with a different template. So one of the bugs I know comes from editing a setting then immediately clicking a different dropdown. Then we refresh and the dropdown which is already being displayed can be overwritten by data from a different setting.

I only got the erroneous position to the side once.  I think I'm close to a reproducible scenario for my second image showing the gap in the drop down , but there's clearly multiple things going on at the same time.  I will work on solid set of steps to reproduce...

@roblourens
I posted a link to my test branch (didn't think a PR was appropriate)  I added extra items for both Auto Save (first setting) and cursor style.
I have not found a totally consistent set of reproduction steps, the following repeated several times will usually trigger a layout problem within 4-5 view changes:

open settings page
tab to Cursor Style - open DD - Escape
change zoom++
reopen DD
change zoom in and out ( sometimes DD re- renders other times it disappears, sometimes you get the gap )

Sometimes I have seen the focus change to the following DD but with the settings of Cursor Style
I will continue looking, but I thought you could use the experimental branch possibly.
https://github.com/cleidigh/vscode/tree/select-box-items-issue

@cleidigh did you figure anything out? I am able to repro this without making code changes, just by editing a dropdown then expanding another one a few times.

@roblourens
I was going to ask you the same thing.  I can reproduce it but it's not completely consistent.  I think your prior comment on crossing the list contents when switching between drop downs looks evident.  I can't really see well from my side how that is happening.  What can I do to help?

I think I see the problem, we are not cleaning up completely when reusing a custom select box for multiple settings.

Verified by filtering the settings to theme, then opening the color theme drop down followed by the icon them drop down. On stable, there is an odd gap in the icon theme drop down. On insiders, it is fixed :).


Fix crash on invalid values in EditorPropertyArray/Dict

Fixes https://github.com/godotengine/godot/issues/78630#issuecomment-2039805841

Thanks!


Yarn GPU update

update gpu patch

Coverage decreased (-32.3%) to 51.84% when pulling 44e97a55b793d4fdb04082583b3a35ae6c3c4a4e on zimiao/gpupatch into 4662147d7a6b8f76f86748dcdd830683b5ac1821 on master.


improve XCTest.xcconfig defaults

don't provide default INFOPLIST_FILE
add [sdk=*] to GCC_PREPROCESSOR_DEFINITIONS to append TEST=1 to all values

👍


Update module to support RHEL5

RHEL5 only needs a .PEM style certificate located in /etc/pki/tls/certs and then c_rehash run after the certificate is copied.
This should be an easy addition but unfortunately, the init.pp module appends '.crt' to the end of every certificate file name.  '.pem' is required for proper certificate rehashing and modifying the code will create backwards compatibility issues.
Thoughts?

The approach you took in your commit makes sense since the default extension is still crt on distribution/versions where it works now. To explicitly keep backwards compatibility we could set the default to crt regardless of distribution/version and it could be set when declaring `ca_cert. Is there something else I'm overlooking?

I would love to be able to make the spec testing but after days of trying
to find out the HOWs and most importantly, the WHYs, I've determined that
I'm completely incompetent at SPEC testing.
On Tue, Dec 29, 2015 at 6:00 PM, Phil Fenstermacher <
<EMAIL_ADDRESS>wrote:

The approach you took in your commit
https://github.com/bschonec/puppet-ca_cert/commit/c0551e94e30f0a0fa068a257b32a210b2855bf35
makes sense since the default extension is still crt on
distribution/versions where it works now. To explicitly keep backwards
compatibility we could set the default to crt regardless of
distribution/version and it could be set when declaring `ca_cert. Is there
something else I'm overlooking?

—
Reply to this email directly or view it on GitHub
https://github.com/pcfens/puppet-ca_cert/issues/8#issuecomment-167896622
.

I've done research on RHEL5 and only PEM files are acceptable in the /etc/pki/tls/certs directory.  Any other extension is ignored by the 'c_rehash' binary.  The modifications I've made ensure that .CRT is the default for all but RHEL5.  I've got no RHEL4 servers available to me so I can't test or comment on compatibility.
Please take a look at my manifests/update.pp changes.  I'm not sure if I should be doing anything there (other than ''c_rehash').  My changes have worked perfectly on my RHEL5 servers so far.

Can you take a look at the rh5 branch to see if that works for you? I've taken your commit, tweaked it, and added some tests around it.
The spec tests for this have gotten a little sloppy because I was trying to avoid lots of repeated logic, but I think it ended up making things more confusing. spec tests are designed to test code and logic to make sure we haven't made any mistakes, and lets us re-check quickly before releasing a change.

I have found a small problem.  The $ca_package needs to be installed before executing $update_cmd.  In my tests, I uninstalled 'openssl-perl' and the module failed to rehash the /etc/pki/tls/certs directory.  In my tests, sometimes the openssl-perl RPM installed before running $update_cmd, other times, not.
Other than that, the module passed both 32bit and 64bit RHEL5 runs.

Did you drop the rh5 branch?  The master branch doesn't have support for RHEL5.

Unfortunately I'm not sure where it went - if I deleted it (I must have if it's not here) it must have been long ago enough that I don't remember much about it.
If you have it cloned anywhere (I don't here at work) we should be able to get it back up here without a lot of trouble.

#23 created.

RHEL5 support has ended, so can this be dropped now?

@djjudas21   Regular support has dropped however extended support is available from Red Hat.   I still have 100+ RHEL5 servers in my environment.    The change is pretty insignificant, IMHO and can be added w/o much trouble at all.

I personally don't have time to work on this one right now (and we don't have any RHEL5 servers left). If someone else can take the time to either submit a PR (or clean up #23) I'd be happy to merge something.

I think this issue can be closed. Regarding metadata.json RHEL5 is supported in master branch.

I would think so after eight years....

:)


Mandatory and Optional properties indication is missing for VPC CIDR block

File: themes/default/content/registry/packages/aws/api-docs/ec2/vpc/_index.md
In the earlier version of the API docs, there used to be a red asterisk for mandatory properties. It seems like it is missing now. Similar to how you indicate a sign for trigger replacement (for example on CIDR Block) can we add mandatory or optional indication ?

Hi @patilpappmodz1, thank you for reporting this. Looking at the EC2 VPC docs you linked, I do see the red asterisk for the name and id properties. Reading through the resource properties, they all seem to have defaults, meaning they're optional.
Are there any particular properties that you noticed that should have the asterisk?

i don't see the asterisk in the INPUT properties section. i am assuming you see the red asterisk in the output section. For VPC, i understand that CIDR Block is a mandatory property.

I see the red asterisk in the constructor section:

VPC:CidrBlock is not a required input. The docs on the page linked above say "... CIDR can be explicitly set or it can be derived from IPAM". I double-checked with Amazon's API specification and it is not listed as a required input there.


Increase commit window for detecting flakes

The current flake bot use recent 100 commits to calculate flake percentage and file flaky bugs if exceeding 2%. However it happens that we just hit flakes/failures within the window. If considering a bigger range, the real flake percentage is way below the threshold.
We need to increase the window to a bigger number like 200+ commits if there are enough data. Another plus is an easy way to reset/flag the counter. For example when we have a fix, we can reset and then the bot will only pick up newer runs/commits.
On the other hand, sometimes we mark a test as flaky, then it runs in staging. When newly deflaked, it will start running in prod, where we will have limited runs in the beginning. For this case, we will use whatever is available as the denominator.
/cc @Hixie

Closing because the bug has not been updated for more than one year.
Feel free to reopen any bugs that you believe are important but please provide updates on how to resource the fix of the bug and what can be done to prevent the issue from not getting updates for another year.


Add Contributors Table in README.md

Added contributors table in README.md file
Related Issuse or bug
Fixes: #103
Proposed Changes

I have made README.md file beautiful and given credit to contributors

Screenshots
Original

Updated

Great!!

Great!!


Update docs examples of react-tinacms -> tinacms

@ncphillips, need some clarification here. Is it that anything imported from react-tinacms can now just be imported from tinacms? I was trying to look through the changelogs but couldn't find a version where this change occurred.

whoops, duplicate of #146 😬


More FAQ entries and contact functionality

This fleshes out the help page. See if you agree with the FAQ entries and want more or less. Also, tapping the Contact us button now launches the default email app with an appropriate subject.

Do you agree with the decision to include the profile ID in the mail subject? I thought that might help solve potential issues faster if you can look them up in the database as a developer. But we don't expose IDs anywhere else yet afaik, so it does expose a little bit of our internal structure

I think it should be fine. The id does not need to be secret afaik

Most of your suggestions are implemented @Showcas


Policy decision message is not shown in Dutch

This issue is imported from pivotal - Originaly created at Oct 28, 2016 by Thijs Kinkhorst
When access is denied based on a policy decision from the PDP, a deny message is shown.
This deny message itself is not translated to English when this language is selected in the upper right corner. It will show the Dutch message. The PDP will deliver this message correctly however:
https://github.com/OpenConext/OpenConext-engineblock/issues/348

This must be investigated further in the Pdp\PolicyResponse::getAssociatedMessage() method. (Alex Rothuis - Oct 28, 2016)

A functional test should be created for this issue. (Alex Rothuis - Nov 18, 2016)

We currently have no infrastructure for functionally testing PEP/PDP. It is probably worth the effort to refactor the PDP client a bit using our already built standard HTTP client.
This makes testing / mocking a bit easier as it will work in a standardized manner. (Alex Rothuis - Nov 18, 2016)

Definitely worth the effort because we surely want to functionally test PEP aswell. (Thijs Kinkhorst - Nov 21, 2016)

This behaviour is caused by the way the PDP messages are introduced, stored and retrieved.
Engineblock enforces the policy and throws an Exception with an untranslated, thus English, message if access was denied.
This Exception gets caught by the ErrorReporter and stored in the session as "feedbackInfo".
In the template, this feedbackInfo is read from the session and shown to the user.
This approach is flawed in two ways. The PDP message is not translated according to a locale. More importantly, if it were translated according to a locale, the message displayed is retrieved from session, so it will not be translated when someone switches locales.
(Alex Rothuis - Dec 14, 2016)

PDP client fails, see https://github.com/OpenConext/OpenConext-engineblock/issues/382 (Thijs Kinkhorst - Feb 16, 2017)


Does not work with new SparseVHD settings on WSL2 pre-release

As per title, this app fails on the new SparseVHD experimental settings format which is enabled here:
Experimental Settings

Sorry, I rarely use Windows now so I can no longer maintain this project. I will archive this repository but feel free to fork :)


Add secondary alignment for BoxContainer

(bugsquad edit) Fixes #9504.

Surely more user friendly.

@akien-mga @reduz
Are you going to mege the feature with commit #7c679dd830 into 2.1?

@Geequlim I guess we could try, to keep a similar API in 2.1 and 3.0, but doesn't 7c679dd break compat?

On 3.0 this was already implememted in a different way
On Sep 21, 2017 6:00 AM, "Rémi Verschelde"<EMAIL_ADDRESS>wrote:

@Geequlim https://github.com/geequlim I guess we could try, to keep a
similar API in 2.1 and 3.0, but doesn't 7c679dd
https://github.com/godotengine/godot/commit/7c679dd8303d906ffbb469ee5b1f53efe25f69af
break compat?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/9509#issuecomment-331096445,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z28CXK99WwIPji8WNFTWcuHGoosNNks5skiXDgaJpZM4OOYR4
.

Closing as I'd prefer not to add diverging APIs in 2.1 now as 3.0 is going to be released. But I'd be ready to consider a PR that backports 7c679dd to 2.1 while ensuring that it doesn't break compatibility with existing projects.


Fix: remove manually drop from test

When I want to manually inspect the vault state after a test, I add a std::mem::ManuallyDrop to prevent Drop from running and cleaning the Vault. Sadly this one got committed into master.

As this is a one line with trivial change, I merge this without review @Haennetz


QR code generator

Describe the project you want to add with tech stack
Using HTML, CSS and Javascript, generates QR code with any text provided
Expected behavior
Provide some text to the website and accordingly, QR is generated
Screenshots (optional)

@MohitGupta121

i know html ,css ,javascript well.
please assign this issue to me under GSSoC'23

@swatisingh42 please go ahead

@MohitGupta121  I made this issue!
Should it not be assigned to me??

Thanks!

Sorry @swatisingh42 first @PoulavBhowmick03 commented on this please pick another
It's okay
no problem


Are empty frames actually influencing the loss?

Issue with torchvision?
Try adjusting focal loss parameter

Yes and improved in the newer implementation


Menu navigator

Task from 'React Revolution'
https://github.com/CodeForPoznan/pah-fm/tree/react-revolution

Done here: https://github.com/CodeForPoznan/pah-fm/pull/580


Support for Protocol 20: Soroban

Hello team! I am aware of #333 which appears to cover this protocol upgrade, but I just wanted to post this mega-issue here nonetheless so that you are aware of the full scope of changes and expectations for this release. If all of the bases are covered, please just close this issue with a reference to the GitHub release that supports Protocol 20.

Protocol 20: Soroban
The next version of the Stellar network will feature a new smart contract platform called Soroban. Note that this version features only additive changes: existing operations, etc. have not changed. (Protocol 20 will be the same thing as "Preview 11," the latest release of Soroban to Stellar Futurenet.)
New XDR Schema

Your SDK should support encoding and decoding the new XDR schemas. The network protocol will use the XDR schema defined here: stellar-xdr @ 9ac0264.
There are three new operations. The former is for invoking contract actions, while the latter two are related to state expiration (see Interacting with Soroban via Stellar and State Expiration):

invokeHostFunctionOp takes a function to invoke (e.g. contract creation, uploads, method invocation) and the corresponding authorization to perform that action (JS reference: )
bumpExpirationFootprintOp, which takes a ledgersToExpire and bumps the expiration ledger of the ledger keys specified in the transaction
restoreFootprintOp restores the expiration of the ledger keys specified in the transaction
Notice that the latter two have no parameters to describe what ledger entries are bumping or restoring. This is because they reference the transaction-level Soroban data access pattern, which is a bit of a paradigm shift of the "all-inclusive" operations we've seen before.

Ideally, it should also provide abstractions for various high-profile components of building Soroban applications. You can use the JavaScript SDKs for references, though these are likely not idiomatic, and may change in the near future as use-cases are better understood. These are in relative order of priority:

a way to add xdr.SorobanTransactionData to a transaction when building it, which is a data structure that describes the resource usage of a Soroban transaction (see Transaction resources), including its storage access footprint, memory usage, etc. (JS reference: SorobanDataBuilder)
support for contract addresses in StrKey format (see SEP-23; JS reference: StrKey.encodeContract)
a way to represent contract objects and convert them to addresses (see Contract-specific Authorization, which demonstrates that an address can either be an account ID [G...] or a contract ID [C...]; JS reference: Contract and Address)
conversion to and from language-native values to the smart contract values (xdr.ScVal) used by Soroban (see Primitive Types; JS reference: scValToNative, scValToBigInt, nativeToScVal, and ContractSpec)
abstractions to perform multi-party authentication of contract invocations (see Authorization; JS reference: authorizeInvocation and authorizeEntry)

You may also want to look into how the TypeScript bindings are generated (code link) via the new soroban command line tool and add a generator for your particular language.
New client libary: Soroban RPC

Unlike Horizon, Soroban RPC uses JSON-RPC as its transport mechanism
The methods are all documented here: https://soroban.stellar.org/api/methods
You can use https://rpc-futurenet.stellar.org/ for testing or connect to the network with your own instance (see the RPC docs)

Horizon API
The following APIs have changed:

/effects can produce two new effects:

contract_credited occurs when a Stellar asset moves into its corresponding Stellar Asset Contract instance
contract_debited occurs when a Stellar asset moves out of its corresponding Stellar Asset Contract instance

/assets/:name contains two new fields:

num_contracts - the integer quantity of contracts that hold this asset
contracts_amount - the total units of that asset held by contracts

/operations has three new response schemas corresponding to the Soroban operations (described above):

// when type: 'invokeHostFunction'
{
    function: string;
    parameters: { value: string, type: string }[];
    address: string;
    salt: string;
    asset_balance_changes: {
        asset_type: string;
        asset_code?: string;
        asset_issuer?: string;

        type: string;
        from: string;
        to: string;
        amount: string;
    }[];
}
// when type: 'bumpFootprintExpiration':
{
    ledgers_to_expire: number;
}
// when type: 'restoreFootprint':
{
    // empty
}

SDF Reference Implementations

JavaScript: low-level XDR structures, RPC API, Horizon API (note that there is no requirement to split out the APIs in this way: it's a case-by-case language/design choice)
Golang
Java
Python

Hello @Shaptic, thank you for opening this issue!
This is the Github release that supports Protocol 20: v0.18.1


[Feature] Report form for irregularities

Task

[ ] to create a form for whistleblowing.

https://www.figma.com/file/MmvFKzUv6yE5U2wrOpWtwS/Podkrepi.bg?node-id=3904%3A13406 - FRAME 8

We might reuse the contact form and add a dropdown for the reason of contact.
https://dev.podkrepi.bg/contact

We have considered adding a button on a campaign`s details page. This will redirect to 'campaigns/[slug]/report', where it will be the step form from Figma. For e.g.:

Is it fine or I shall change it?

@nradkova You can find the backend implementation at https://github.com/podkrepi-bg/api/pull/226

Thank you.


Missing OIDC group/role bindings on the management cluster (for admin role/first user)

While onboarding a new customer we ran into the problem that it was hard to follow the gitops tutorial because the customer didn't have the correct role bindings on the management cluster.
Error:
Error from server (Forbidden): error when creating "01-source.yaml": gitrepositories.source.toolkit.fluxcd.io is forbidden: User cannot create resource "gitrepositories" in API group "source.toolkit.fluxcd.io" in the namespace "flux-system"

Tutorial:
https://docs.giantswarm.io/advanced/gitops/#setting-up-sources
The solution is to bind the role write-flux-resources

Question is if we add a hint to the tutorial or make sure that the initial user at least get's this permission.

flux-demo repository and docs have been updated. They now use default namespace and automation ServiceAccount, which allow customers to follow the steps without taking extra action.
If they still want to set up their own ServiceAccount, an explanation along with link to MAPI RBAC documentation is provided.


better core/lib improvement and update

move inject-data from routing to lib
update apollo.js from ref: https://github.com/apollographql/meteor-integration
better configureStore function update
add Utils.findWhere and Utils.defineName
move apollo_server from core to lib
can add webapp connect handlers middleware with order number, so it will run by order
ssr store initialization same as client, it init in nova:lib
GraphQLSchema.addToContext({ getViewableFields: Users.getViewableFields }) move to nova:user

and something i want to do, but no time do in this pr

remove meteorhacks_inject-initial because we have inject-data

That's awesome!

So this PR (I've pulled from comus/devel) causes problems with our extensions. We have a redux-thunk based middleware and a set of actions/reducers to interact with our domain-specific REST api that pulls entities into the same store as apolloClient uses.
From a behaviour perspective, the first issue I see:
We have extended the category schema and added in some queries, mutations, fragments, etc. and the edit form for categories is now unpopulated when the application first starts. This seems to resolve itself after a minute or so. The browser console shows an error Warning: Unknown prop slug on <option> tag. Remove this prop from the element. when the dialog is unfilled. Once the problem resolves itself, the warning no longer is logged. I speculate the SSR (or pre-hydrated store) doesn't have our schema extensions or something? Then when the query is re-executed on the client, the additional fields are supplied.

Warning: Unknown prop slug on  tag. Remove this prop from the element.

This is because the <option> tag only excepts a value & label 😄

I speculate the SSR (or pre-hydrated store) doesn't have our schema extensions or something?

Oh interesting!

@xavcz I'm trying to understand the apollo SSR strategies and how they are leveraged in Telescope so just staggering around a little. 😅  So I have no idea what the root cause is of the <option> tag error. I can't replicate it in our production instance so I think it's been introduced with the PR?
In terms of the inject_data.js, it also looks like I'm getting two identical <script type="text/inject-data"> tags in the head of the SSR-ed html? I'll keep looking at this, but am feeling a little overwhelmed.

This checks out great with the TRN packages. Thanks so much @comus!


Exception Middleware not being called

On errors the exception middleware defined is not being called.
Config via app.UseMiddleware().
HandleExceptionAsync is not being called after exception thrown from Endpoint and validation enabled.

does #186 help?

updated beta docs: https://dev--fast-endpoints.netlify.app/docs/exception-handler.#disable-validation-error-catching


Cassandra Store Catalog Function || Issue with Store.Item.getExpiration() function

Version Information

Software
Version(s)

BusinessEvents
6.3.0

OS Type?
NA

OS Version?
NA

What is the expected behavior?
getExpiration() function, should return time left to expire (in seconds).
What is the actual behavior?
While using getExpiration() function, it returns the same value which has set for TTL, even after providing wait to engine
Please provide log files.
ActiveSpaces_ItemEvents.zip
getExpirationTest3.log

As discussed, this method is not supported
TTL_1.log


feat(linter): implement no-lone-blocks rule

implement: https://eslint.org/docs/latest/rules/no-lone-blocks

This PR uses span() 4 times but I think we can not convert it to span.
related: https://github.com/oxc-project/oxc/pull/8149#discussion_r1898625689


Remove Flask-MySQLdb

Remove Flask-MySQLdb and simply use MySQLdb, no need for the flask extension (low usage on github) I think.

db_handler, Setup/src/backend-db/pip3.deps
https://github.com/admiralobvious/flask-mysqldb


Add Linux Mint installation guide

Added a linux mint installation guide - it differs a little bit from direct Ubuntu, mainly because of  using  UBUNTU_CODENAME instead of VERSION_CODENAME.

Checklist

[x] npm test passes
[x] documentation is changed or added (if applicable)
[x] permission has been obtained to add new logo (if applicable)
[x] contribution guidelines followed here

Are the steps not the same as Debian? All I can see that's changed is that you've removed sudo and switched VERSION_CODENAME to UBUNTU_CODENAME. I'd suggest just adding a note to the existing instructions saying to use UBUNTU_CODENAME if you're on Mint

Are the steps not the same as Debian? All I can see that's changed is that you've removed sudo and switched VERSION_CODENAME to UBUNTU_CODENAME. I'd suggest just adding a note to the existing instructions saying to use UBUNTU_CODENAME if you're on Mint

Yes indeed -  the hint would be appropriate and enough. Will change it...


[CARBONDATA-1847] Add inputSize for value read

Update inputSize metric for ColumnBatch and InternalRow

[X] Any interfaces changed?
No
[X] Any backward compatibility impacted?
No
[X] Document update required?
No
[X] Testing done
No new testcase added
[X] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/402/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2062/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1675/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/408/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2066/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1680/

LGTM


feat(opentelemetry-collector): use Kubernetes recommended label for c…

Use Kubernetes commended labels for component label.

I agree this is a breaking change.  We can add a new label but should leave the existing one for now.

/ping

@nlamirault please bump the patch version of the chart and run make generate-examples CHARTS=opentelemetry-collector

(once this is updated with the latest and examples are generated, should be good)

@z0rc thanks, I'll submit a pr to fix this.


to_sql throws latin-1 encoding error even though everything seems encoded in utf-8

I want to upload a file from csv to mysql with the following commands
 df = pandas.read_csv('test.csv', encoding = 'utf-8')
engine = sqlalchemy.create(<Mysql-Connection-URI>, encoding = 'utf-8')
df.to_sql('testtable', con = engine)

mysql has utf-8 as global encoding. If I upload the file manually to the database it goes without problems.
using to_sql throws the following errror:
UnicodeEncodeError: 'latin-1' codec can't encode character '\u015e'etc...
Any ideas, where Latin-1 becomes part of the games and how this could be fixed? Thanks for any advice!

What driver, driver version and pandas version are you using?
See also https://github.com/pydata/pandas/issues/10963 (there, providing ?charset=utf8 to the connection string solved the issue), and http://stackoverflow.com/questions/32235696/pandas-to-sql-gives-unicode-decode-error (which seems a bug in sqlalchemy pymysql dialect or the pymysql driver)

thanks! so funny, I figured it just by myself just before lunch and actually wrote the above answer you found on stackoverflow before I could return here. Thanks for the quick response!

Aha :-)
Maybe you raise the issue at sqlalchemy or pymysql (not sure which of the two is to blame that the encoding is not passed through properly)


Hub Support!

Finally got hub support working!
The big issue was first having an outdated TinyUSB which I fixed in 0.7.9. This caused a MASSIVE amount of issues and was the major blocker for 0.7.9 release.
Next issue was keeping track of "dev address" and "instance" inside of each listener.
Final issue was taking care of figuring out if we're a keyboard, dongle, or xbox one dongle. This code could use improvements but works well for now.

whats hub? what does it do?


ADR: Policy API performance, open ended querying for entitlements (MatchedSubjectMappings) has known performance concerns at scale

Background
Once the work in https://github.com/opentdf/platform/pull/347 and its dependent work in https://github.com/opentdf/platform/pull/321 are merged in, there will be platform support for matching of Subjects to Attribute Values through Subject Mappings (also known as entitlements) via external fields and values (SubjectProperty in the protos) like those found in an idP or external User Store.
It is understood that the Attributes and Policy services should serve as CRUD for storage of policy objects, and that interpretation of those objects is the concern of other services. Relevant to this performance note is the separation of concerns that Attributes Service will do a wide and liberal lookup to find any potential match of a Subject Mapping referencing one of the provided External Field / Value pairs provided when matching in a single Condition, with only the slightest filtering for IN/NOT_IN in the matching.[^1] From those liberally matched Subject Mappings, the client service (most often Authorization Service) will maintain the responsibility of interpreting the potential matches into informed Policy Decisions with the boolean logic and multiples of Conditions, ConditionGroups, and SubjectSets within a given match. Client PEPs or other services should rely on Authorization Service for trustworthy results on the Attribute Values entitled to a Subject.
There are known performance concerns with the current approach that are increasingly likely to be experienced as the number of Subject Mappings and Subject Condition Sets scales.
The current approach (brought in by https://github.com/opentdf/platform/pull/347):

uses a SQL subquery on the subject_condition_set table, which means O(n^2) on that table
accesses the column's stored JSONB [2]
iterates through the Subject Sets array's Condition Groups
iterates through each Condition Groups' individual Conditions
builds the query such that every SubjectProperty provided in the RPC is matched against the Condition's field, values array, and operator match

While there is a potential for a bottleneck caused by the Attributes Service liberal lookup matching too many Subject Mappings for performant processing by the Authorization Service, that is not the concern of this issue, which is focused on the performance time to query at scale.
Potential paths forward

[!NOTE]
:warning: These are the current obvious paths forward, but may not be best. Further time for exploration should be given to Option 1 and 3 before a decision is finalized as they may have simple and obvious feasibility once time is allotted to explore.

Option 1. SPIKE and invest more time attempting to optimize the SQL query
It's possible we could use something like a Common Table Expression (CTE) to optimize the SQL.

🟢 Admins are generally very cautious
🟢 Cause strain on admins potential to reduce the lookup to O(n) from O(n^2) on the Subject Condition Sets table, which is huge
🟢 faster to explore, test, and implement
🟢 no additional maintenance cost or implementation changes
🔴 does not resolve any performance lag from querying keys/values within the stored JSONB, which may be significant or negligible
🔴 may not work; needs more time investment

Option 2. Move the JSONB tree structure into individual tables
We could create individual tables so that each Subject Set is a row, each Condition Group is a row, and each Condition is a row, all on independent tables that relate one to many down the tree with Foreign Keys.

🟢 definite would work to reduce Big O to O(n) instead of O(n^2) because the JOIN would be on the matched Conditions alone
🟢 potential of component reuse, so instead of storing Condition Groups that are often used in individual but different Subject Condition Sets, that sole row on the Condition Group table could reference multiple different Subject Sets
🔴 adds complexity to the platform admins and developers both would need to understand, and a large goal is to reduce complexity
🔴 more room for bugs and complexity of maintenance with more tables and more RPCs to support
🔴 less flexibility for iterative changes, like allowing Boolean AND/OR logic at the Subject Set or Subject Mapping level (changing how to interpret multiple Subject Sets or multiple Condition Groups)
🔴 will take time to build user-intuitive RPCs and durable data layer to power them

Option 3. Employ some kind of a "search term cache" of just the SubjectProperty fields
We could keep a list of the individual Condition's known subject_external_field names in a column of the Subject Condition Set table as a varchar[] to significantly reduce n in the O(n^2) lookup time to just Subject Condition Sets that are known to relate to one of the provided fields instead of every row on the Subject Condition Set table.

🟢 iterating through a varchar[] column at the top of the table should be able to be work with a CTE, unlike the questions around JSONB
🟢 it is expected that reads far outnumber writes, so any performance concerns about writes to the cached field names would be negligible in comparison
🔴 all the common concerns around cache consistency would need to be addressed
🔴 similar to the concern in footnote [^1], a single field name used very widely would eliminate any performance gain from this path forward

[^1]: The Attributes Service unfortunately must look at the IN/NOT_IN state of the Condition when matching to avoid potentially common extreme edge cases. For example, if a policy admin relies heavily on a very widely used external field name like username or emailAddress and IN rules, should the Attributes service query without filtering by recognizing the IN/NOT_IN scenario, it may return nearly every Subject Mapping in the database, which is not only unhelpful but has its own suite of follow-on concerns.
[^2]: It was decided to store the relation of Subject Sets > Condition Groups > Conditions in JSONB for a few reasons documented with the migration and it is known that there is a need to iterate.

We need to create an issue to run performance tests across the platform:

KAS concurrency (under 3s)
authorization caching of policy data (maybe needed)

defer until doing benchmarking tests - https://github.com/virtru-corp/data-security-platform/issues/63


[Docs] Mermaid anchor fix test 2

Continuing here because the RTD docs stopped uploading changes to the commits.

@vvbandeira Looks like this now.


Fails to install on IRIS 2023.1 Dev Preview (build 207U)

When trying to import v0.5.2 from Studio, or loading with $SYSTEM.OBJ.Load() it fails.
Error is:
Load finished successfully.
2023-03-07 10:36:36 0 %ZPM.Installer: ERROR #5001: Could not find %ZLANGC00 routine contents in %ZPM.PackageManager

Yes, due to changes in 2023.1, version 0.5.2 and earlier not compatible with it, check the latest betas, until the final release

Thank you Dmitry for such a prompt reply, I installed 0.5.3-beta.2 and it worked like a charm!


ParallelPostFit excessive scheduler memory use and CancelledError

Notebook with MCVE and all notes: https://nbviewer.jupyter.org/gist/rikturr/43336377678018d01d4f21f19dd7ef11
When using ParallelPostFit to train with pandas/numpy objects then predict on dask objects, I noticed that the scheduler memory use runs extremely high. Many times I would get a CancelledError and scheduler dying when calling .predict() with pretty small data sizes (refer to notebook for full code with outputs):
X_train, X_test, y_train, y_test = ...
rf = ParallelPostFit(
    RandomForestClassifier(n_estimators=100, random_state=seed, n_jobs=-1)
)
_ = rf.fit(X_train, y_train)

preds = rf.predict(X_test)
_ = preds.compute()  # failure happens on this line after ~40 minutes

The scheduler memory balloons to npartitions of X_test * size of rf, which can get into the multiple GBs very fast. I noticed that each time an operation would get called on preds, this memory exchange would happen again. I realize that this is because ParallePostFit uses map_partitions behind the scenes, but does not broadcast the model objects. This causes Dask to send the object through the scheduler to each worker each time you do something with preds (unless of course you persisted it).
Workaround is to broadcast the model object then use map_partitions yourself instead of the ParallelPostFit wrapper:
rf = RandomForestClassifier(n_estimators=100, random_state=seed, n_jobs=-1)
_ = rf.fit(X_train, y_train)

rf_fut = client.scatter(rf, broadcast=True)

def dask_predict(df, model):
    return model.predict(df)

preds = X_test.map_partitions(
    dask_predict,
    model=rf_fut,
    meta=np.array([1])
)

I plan to follow up with a PR to fix this in the ParallelPostFit class

Just confirmed this happens with a LocalCluster too it is easier to reproduce that way