bug: Avoid race condition while generate secret with re-use flag

Description
There might be a race condition if multiple certgen processes are running
at the same time with ca-reuse-secret and ca-generate flags enabled. The
sequence of flows could be as below:
P1 -> Confirm secret is not available
P2 -> Confirm secret is not available
P1 -> Generate new CA
P2 -> Generate new CA
P1 -> Store its generate CA to secret
P2 -> Store its generate CA to secret, which overwrite what P1 stored.
This commit is to make sure that we will throw IsAlreadyExists error if
the secret is available in StoreAsSecret function, then the caller (e.g
certgen) will decide if it should fail or just reload secret and proceed.
In above example, P2 will reload CA from secret accordingly.
Signed-off-by: Tam Mach<EMAIL_ADDRESS>Background
This is coming out of sync between myself, Sebastian and Alex on PR https://github.com/cilium/cilium/pull/18607
Testing
Testing was done by running two certgen with same arguments at the same time

Running 2 certgen at the same time
$ cat ./temp.sh
./certgen --cilium-namespace=kube-system \
  --ca-generate \
  --ca-reuse-secret \
  --hubble-server-cert-generate \
  --hubble-server-cert-validity-duration=94608000s \
  --hubble-relay-client-cert-generate \
  --hubble-relay-client-cert-validity-duration=94608000s \
  --hubble-server-cert-common-name="*.default.hubble-grpc.cilium.io" \
  --k8s-kubeconfig-path=/home/tammach/.kube/config &

./certgen --cilium-namespace=kube-system \
  --ca-generate \
  --ca-reuse-secret \
  --hubble-server-cert-generate \
  --hubble-server-cert-validity-duration=94608000s \
  --hubble-relay-client-cert-generate \
  --hubble-relay-client-cert-validity-duration=94608000s \
  --hubble-server-cert-common-name="*.default.hubble-grpc.cilium.io" \
  --k8s-kubeconfig-path=/home/tammach/.kube/config &

$ ./temp.sh

$ INFO[0000] Generating server certificates for Hubble     subsys=cilium-certgen
INFO[0000] Creating CSR for certificate                  certCommonName="*.default.hubble-grpc.cilium.io" certUsage="[signing key encipherment server auth]" certValidityDuration=26280h0m0s subsys=generate
INFO[0000] generate received request                     subsys=cfssl syslog=info
INFO[0000] received CSR                                  subsys=cfssl syslog=info
INFO[0000] generating key: ecdsa-256                     subsys=cfssl syslog=info
INFO[0000] encoded CSR                                   subsys=cfssl syslog=info
INFO[0000] signed certificate with serial number<PHONE_NUMBER>84934946033776608488653915802833225245  subsys=cfssl syslog=info
INFO[0000] Generating client certificates for Hubble Relay  subsys=cilium-certgen
INFO[0000] Creating CSR for certificate                  certCommonName="*.hubble-relay.cilium.io" certUsage="[signing key encipherment server auth client auth]" certValidityDuration=26280h0m0s subsys=generate
INFO[0000] generate received request                     subsys=cfssl syslog=info
INFO[0000] received CSR                                  subsys=cfssl syslog=info
INFO[0000] generating key: ecdsa-256                     subsys=cfssl syslog=info
INFO[0000] encoded CSR                                   subsys=cfssl syslog=info
INFO[0000] signed certificate with serial number<PHONE_NUMBER>83653302175083234562251692908153489523  subsys=cfssl syslog=info
INFO[0000] Creating K8s Secret                           k8sSecretName=hubble-server-certs k8sSecretNamespace=kube-system subsys=generate
WARN[0000] Secret already exists                         k8sSecretName=cilium-ca k8sSecretNamespace=kube-system subsys=generate
INFO[0000] Reload secret for Cilium CA                   subsys=cilium-certgen

What I would suggest is to rework the patch so that generateCertificates() works as follow:

Generate a Cilium CA
Try to store the Cilium CA into the cilium-ca Secret
When 2. failed because the cilium-ca Secret already exists, load it from k8s
Generate+sign the Hubble / Clustermesh TLS certificates and store them into k8s

I think by handling the CA first, we ensure that the TLS certificates are consistently signed with the CA stored in cilium-ca. Does that make sense?

Yup, it's completely making sense to me, not sure why I missed this, thanks for pointing it out.
Re-test after the changes

Checking key id for certs
$ kubectl -n kube-system get secret cilium-ca -o jsonpath='{.data.ca\.crt}' | openssl base64 -A -d | openssl x509 -text -noout | grep -A1 "Key Identifier"
            X509v3 Subject Key Identifier:
                EC:A9:9B:42:B2:57:05:1F:81:6D:93:40:A4:33:2E:94:C7:B6:E0:F0
$ kubectl -n kube-system get secret hubble-server-certs -o jsonpath='{.data.ca\.crt}' | openssl base64 -A -d | openssl x509 -text -noout | grep -A1 "Key Identifier"
            X509v3 Subject Key Identifier:
                EC:A9:9B:42:B2:57:05:1F:81:6D:93:40:A4:33:2E:94:C7:B6:E0:F0
$ kubectl -n kube-system get secret hubble-server-certs -o jsonpath='{.data.tls\.crt}' | openssl base64 -A -d | openssl x509 -text -noout | grep -A1 "Key Identifier"
            X509v3 Subject Key Identifier:
                A6:FB:53:2C:EE:BC:18:B2:FF:D5:0B:A4:4A:9D:24:FF:32:D5:0C:A3
            X509v3 Authority Key Identifier:
                keyid:EC:A9:9B:42:B2:57:05:1F:81:6D:93:40:A4:33:2E:94:C7:B6:E0:F0

+1 on removing the initial certificate check that Alex pointed out, let's try to remove it

Thanks both, I still think the first block is required. As these two blocks are guarded by different flags, one is with reuse secret and another is with generate secret. There might be the case that reuse secret is true, but generateCA is false (i.e. load secret from file).

There might be the case that reuse secret is true, but generateCA is false (i.e. load secret from file).

That's a good point, the general workflow has to be reworked in order to remove the first load. What do you think of
ciliumCA = nil

if CAGenerate:
    ciliumCA = Generate CA
    if store ciliumCA into k8s fail IsAlreadyExists:
        ciliumCA = nil
else if load from files:
    ciliumCA = load from files

if ciliumCA is nil and CAReuseSecret:
    ciliumCA = load from k8s

The above flow is making sense to me, thanks for your patience explaining to me :).
Same test was done to make sure I didn't make any silly mistake

$ kubectl -n kube-system get secret cilium-ca -o jsonpath='{.data.ca\.crt}' | openssl base64 -A -d | openssl x509 -text -noout | grep -A1 "Key Identifier"
            X509v3 Subject Key Identifier:
                24:06:D3:46:E2:3D:40:58:79:9A:C3:11:5B:39:9C:B2:6D:A3:74:E1

$ kubectl -n kube-system get secret hubble-server-certs -o jsonpath='{.data.ca\.crt}' | openssl base64 -A -d | openssl x509 -text -noout | grep -A1 "Key Identifier"
            X509v3 Subject Key Identifier:
                24:06:D3:46:E2:3D:40:58:79:9A:C3:11:5B:39:9C:B2:6D:A3:74:E1

$ kubectl -n kube-system get secret hubble-server-certs -o jsonpath='{.data.tls\.crt}' | openssl base64 -A -d | openssl x509 -text -noout | grep -A1 "Key Identifier"
            X509v3 Subject Key Identifier:
                64:B2:AD:B1:D9:B1:8C:C3:98:69:40:E0:E7:C7:80:E3:3F:6D:AE:80
            X509v3 Authority Key Identifier:
                keyid:24:06:D3:46:E2:3D:40:58:79:9A:C3:11:5B:39:9C:B2:6D:A3:74:E1

Merging. @sayboras should we cut a new release with this?

Merging. @sayboras should we cut a new release with this?

Yes, it's more than what I can wish for :ship:


note

代码学习

Hi @Mang30 , from my understanding, it seems this pull request is about your own edits for learning?
Did you mean to submit this pull request for merging to this repo? please confirm and let me know
If you are working on your own internal codebase, you may submit the PR to your own main.
We greatly appreciate and welcome any new features you'd like to provide, if this or anytime you'd like to contribute to this code base, please indicate in the PR description and I will double check and merge it. Thank you for your contribution!

Hi @subercui ,I'm so sorry for the confusion caused by my inappropriate behavior. In fact, I'm dealing with  my internal codebase, and I will close  this wrong pull request . Thank you for your patient reminder . I hope this matter won't affect  your good mood. Wishing  you have a happy weekend!

No worries at all. Please feel free to open a new PR when you want to push any updates


Error: could not set config params: conflicts with existing config

The following error seems to occur after docker compose up
eth-pos-devnet-create-beacon-chain-genesis-1  | time="2023-01-24T07:46:00Z" level=fatal msg="Could not generate beacon chain genesis state" error="could not set config params: config name=interop conflicts with existing config named=mainnet: configset cannot add config with conflicting fork version schedule" prefix=genesis

i am having the exact same issue. i tried building with source it works for the first time but when i restart the beacon chain it never get back to sync state.

I change Config_Name and PRESET_BASE in the config.yml to mainnet, and the container won't exit 1,but i can not see the beacon chain in normal operation, i guess the network configuration is not consistent

Anyone found a solution for this?

You have to add the following fields to the config.yml file and it going to work!
`
Genesis
GENESIS_FORK_VERSION: 0x20000089

Altair
ALTAIR_FORK_VERSION: 0x20000090

Merge
BELLATRIX_FORK_VERSION: 0x20000091

Capella
CAPELLA_FORK_VERSION: 0x20000092
`

Actually this is my issue #31

Thanks for the response @kasey, I changed the config and preset base both to test. This prevents the containers from starting
@seunlanlege ➜ /workspaces/eth-pos-devnet (master) $ DOCKER_BUILDKIT=0 docker compose up
[+] Running 5/5
 ✔ Container eth-pos-devnet-create-beacon-chain-genesis-1  Created                                                                                0.1s
 ✔ Container eth-pos-devnet-geth-genesis-1                 Created                                                                                0.1s
 ✔ Container eth-pos-devnet-geth-1                         Created                                                                                0.1s
 ✔ Container eth-pos-devnet-beacon-chain-1                 Created                                                                                0.1s
 ✔ Container eth-pos-devnet-validator-1                    Created                                                                                0.1s
Attaching to eth-pos-devnet-beacon-chain-1, eth-pos-devnet-create-beacon-chain-genesis-1, eth-pos-devnet-geth-1, eth-pos-devnet-geth-genesis-1, eth-pos-devnet-validator-1
eth-pos-devnet-create-beacon-chain-genesis-1  | time="2023-08-29T14:13:26Z" level=info msg="Specified a chain config file: /consensus/config.yml" prefix=genesis
eth-pos-devnet-create-beacon-chain-genesis-1  | time="2023-08-29T14:13:26Z" level=fatal msg="Could not generate beacon chain genesis state" error="could not set config params: config name=test conflicts with existing config named=mainnet: configset cannot add config with conflicting fork version schedule" prefix=genesis
eth-pos-devnet-create-beacon-chain-genesis-1 exited with code 1
service "create-beacon-chain-genesis" didn't complete successfully: exit 1

In addition to the unique config name, you also need to specify a unique fork version schedule. This is what pelyhe is showing in their config.yaml snippet above: https://github.com/OffchainLabs/eth-pos-devnet/issues/9#issuecomment-1468273851
That's just one example of a unique fork version schedule - I like to pick a 3 hex byte "prefix" that is common to each version (eg 0x424242 in the example below) and then a byte that is unique to each fork (eg 0x42424200, 0x42424201 --  IMO most intuitive is for the final byte to be in ascending order from genesis..capella). For example:
GENESIS_FORK_VERSION: 0x42424200
ALTAIR_FORK_VERSION: 0x42424201
BELLATRIX_FORK_VERSION: 0x42424202
CAPELLA_FORK_VERSION: 0x42424203

Hi @kasey, so i tried this, but unfortunately got the same error. here's my config.yml
CONFIG_NAME: localnet
PRESET_BASE: localnet

# Genesis
GENESIS_FORK_VERSION: 0x52525500

# Altair
ALTAIR_FORK_EPOCH: 0
ALTAIR_FORK_VERSION: 0x52525501

# Merge
BELLATRIX_FORK_EPOCH: 0
BELLATRIX_FORK_VERSION: 0x52525502
TERMINAL_TOTAL_DIFFICULTY: 0

CAPELLA_FORK_EPOCH: 0
CAPELLA_FORK_VERSION: 0x52525503

# Time parameters
SECONDS_PER_SLOT: 12
SLOTS_PER_EPOCH: 6

# Deposit contract
DEPOSIT_CONTRACT_ADDRESS: 0x4242424242424242424242424242424242424242

And the ensuing error:
@seunlanlege ➜ /workspaces/eth-pos-devnet (master) $ DOCKER_BUILDKIT=0 docker compose up
[+] Running 1/0
 ✔ Container eth-pos-devnet-create-beacon-chain-genesis-1  Created                                                                                0.0s
Attaching to eth-pos-devnet-beacon-chain-1, eth-pos-devnet-create-beacon-chain-genesis-1, eth-pos-devnet-geth-1, eth-pos-devnet-geth-genesis-1, eth-pos-devnet-validator-1
eth-pos-devnet-create-beacon-chain-genesis-1  | time="2023-08-29T15:34:49Z" level=info msg="Specified a chain config file: /consensus/config.yml" prefix=genesis
eth-pos-devnet-create-beacon-chain-genesis-1  | time="2023-08-29T15:34:49Z" level=fatal msg="Could not generate beacon chain genesis state" error="could not set config params: config name=localnet conflicts with existing config named=mainnet: configset cannot add config with conflicting fork version schedule" prefix=genesis
eth-pos-devnet-create-beacon-chain-genesis-1 exited with code 1
service "create-beacon-chain-genesis" didn't complete successfully: exit 1
@seunlanlege ➜ /workspaces/eth-pos-devnet (master) $

Ahh, I think the problem is that we added DENEB_FORK_VERSION so now you need to specify that one as well.

DENEB_FORK_VERSION so now you need to specify that one as well, eg DENEB_FORK_VERSION: 0x52525504

Thanks for the help @kasey, adding the DENEB_FORK_VERSION fixes my issues.

Fixed this up as of latest master


Python(undefined-variable) false positiv on loops

Problem:
The extention warn you for Python(undefined-variable) on the loop variable that are in a class in python.
when I do a loop in a class i have an error.

Step to reproduce:
Make a python file, make a class, make a loop in it.

Thank you for the report.
Could you try the following please and let me know what happens?:
If you disable the ErrorLens extension, and restart VSCode, do you still see errors? (These will be red squiggles).
ErrorLens is only enhancing the highlighting of the diagnostics from the language service provider, so it's only showing the problems that the Python provider is passing to the ErrorLens extension.
I tried the code in your first screenshot, and this did not generate any undefined variables.

My bad, that was a python version problem... I was in 3.5.5...

There is no highlighting withtout on thoses varaibles errorLens. Using python 3.7.4 64bits on macOS.
With:

Without:


Dynamic commands

With old Commands module we can do something like:
var commands = _service.GetCommands();

foreach(var command in commands)
{
  _commandService
    .CreateCommand(command.Name)
    .Alias(command.Aliases)
    .Do(async e =>
        {
           await command.Do();
            await e.Channel.SendMessage("Hi!");
        });
}

How is expect to do it with a new commands module?

You can use Command holders. For more support on that, you should join the Discord API guild (invite in the README), and ask in the dotnet_discord-net channel


Alerts are not triggering to its target communications

What did you do?
Trying out to practice prometheus and grafana for POC on a single node cluster, the alerts are triggering in alert manager but not to its communication channel (tried with slack and e-mail)
What did you expect to see?
Alerts triggering the notification on the specified channel or communication target
What did you see instead? Under which circumstances?
Alerts not triggering to those targets (slack and e-mail)

System information:
Running on a single node cluster (colima) on top of mac OS
  Darwin 23.5.0 arm64

Configuration file:

Running my prometheus in a docker container, below is the docker-compose file:
version: '3'
services:
prometheus:
image: prom/prometheus
volumes:
- "./prometheus.yml:/etc/prometheus/prometheus.yml"
- "./myrules.yml:/etc/prometheus/myrules.yml"
networks:
- dockerprome
ports:
- 9090:9090
node-exporter:
image: prom/node-exporter
networks:
- dockerprome
ports:
- 9100:9100
alert-manager:
image: prom/alertmanager
volumes:
- "./alertmanager.yml:/etc/prometheus/alertmanager.yml"
networks:
- dockerprome
ports:
- 9093:9093
networks:
dockerprome:
driver: bridge

Alertmanager configuration file:
global:
smtp_from<EMAIL_ADDRESS>smtp_smarthost: smtp.gmail.com: 587
smtp_auth_username<EMAIL_ADDRESS>smtp_auth_identity<EMAIL_ADDRESS>smtp_auth_password: 'asdvadeqw'
require_tls: true
route:
receiver: admin
group_wait: 40s
group_interval: 5m
repeat_interval: 10m
routes:

match_re:
severity: testing
receiver: testing
match_re:
severity: critical
receiver: admin
receivers:

name: admin
slack_configs:

channel: '#prometheus'
api_url: 'https://hooks.slack.com/services/XXXXX/XXXXXX'

name: testing
email_configs:

to<EMAIL_ADDRESS>

Are there actually any alerts active?
Does you setup actually allow communication from inside the container to public services?
Run alertmanager with --log.level=debug and check its logfiles.

Also, for support questions please consider using https://groups.google.com/g/prometheus-users instead of github issues.


Dropping text (or element) throws TypeError: Cannot read property 'type' of undefined

Hi,
If I just select some text on the page or take some element and drag it into the drop area, instead of some graceful error or validation I get error thrown:
TypeError: Cannot read property 'type' of undefined
    at ng-file-upload-all.min.js:4
    at angular.js:14792
    at r.$eval (angular.js:16052)
    at r.$digest (angular.js:15870)
    at r.$apply (angular.js:16160)
    at angular.js:17927
    at e (angular.js:5552)
    at angular.js:5829

I'm getting this error on Ubuntu Chrome Version 47.0.2526.111 (64-bit) also on the demo page http://angular-file-upload.appspot.com/ (which is actually ng-file-upload 11.1.1 at time of this writing) when dropping a file into the "Select File or Drop File" box.
TypeError: Cannot read property 'type' of undefined
    at ng-file-upload.js:1949
    at wrappedCallback (angular.js:11572)
    at angular.js:11658
    at Scope.$eval (angular.js:12701)
    at Scope.$digest (angular.js:12513)
    at Scope.$apply (angular.js:12805)
    at angular.js:14313
    at completeOutstandingRequest (angular.js:4397)
    at angular.js:4705

The reason seems to be that dataTransfer.files and dataTransfer.items are empty.
On Ubuntu Firefox 43.0.4, it works as expected.

Seems to be related to this: https://code.google.com/p/chromium/issues/detail?id=543940 (at least my issue).

Fixed at 11.2.0


PCB

Supply IMU IC for easy connection and fastening of a tiny IC containing our IMU

New draft added in commit #dcf342a
Please look over design @nammenam

looks good but i hate the headers ngl, might be better to use ffc connection or something. The dimensions are yet to be determined

Made this a single pcp thread

I am thinking we make an onboard programmer and debugger, I have some ideas on how to do this. I have also experimented with some toolchains so that we dont have to use an ide


Unable to disable both the Git and GitHub extensions

Issue Type: Bug
Cannot activate the 'GitHub' extension because it depends on the 'Git' extension, which is disabled. Would you like to enable the extension and reload the window?
VS Code version: Code 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:22:06.216Z)
OS version: Windows_NT x64 10.0.18363
Remote OS version: Linux x64 4.4.0-18362-Microsoft

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
3.90GB (0.42GB free)

Process Argv

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 4.4.0-18362-Microsoft

CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2701)

Memory (System)
3.90GB (0.42GB free)

VM
0%

Extensions (20)

Extension
Author (truncated)
Version

vscode-languagetool
ada
3.8.0

vscode-languagetool-en
ada
3.8.0

project-manager
ale
11.1.0

code-gnu-global
aus
0.2.2

gitignore
cod
0.6.0

git-extension-pack
don
0.1.3

githistory
don
0.6.8

gitlens
eam
10.2.2

code-runner
for
0.11.0

terminal
for
0.0.10

anaconda-extension-pack
ms-
1.0.1

python
ms-
2020.7.94776

cpptools
ms-
0.29.0

vscode-yaml
red
0.9.1

vscode-open-in-github
ziy
1.3.6

project-manager
ale
11.1.0

theme-monokai-pro-vscode
mon
1.1.17

remote-wsl
ms-
0.44.4

vscode-icons
vsc
10.2.0

material-theme
zhu
3.8.4

(9 theme extensions excluded)

Edit: The git-extension-pack and all other git related extensions have been uninstalled.

same issue
vscode version: 1.47.2
os version: macos 10.15.6
remote os version: debian 8
And when I roll back to 1.47.1 everything is fine.

@sandy081 This is what I see when I try to disable Git:

Should we instead offer the opportunity for the user to still disable the entire dependency chain, in that notification? Something like Do you want to disable all these extensions?.

^This is exactly what it says for me whenever I open VScode. However, when I open it without my WSL: Ubuntu remote, it doesn't show this error...

Should we instead offer the opportunity for the user to still disable the entire dependency chain, in that notification? Something like Do you want to disable all these extensions?.

Yeah makes sense.

@avi10malhotra For now, enable the Git extension. Then, if you still want git features to stay disabled, set the git.enabled = false setting.

Install Git Blame extension and try to disable Git extension and you will get following message. Disable All action will disable Git and all its dependencies.


[1.1.0] Update default timeout

Description

Changed timeout to 300000

Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #495 (a3355cd) into aos-<IP_ADDRESS> (29dae17) will not change coverage.
The diff coverage is 100.00%.

@@              Coverage Diff               @@
##             aos-<IP_ADDRESS>     #495   +/-   ##
==============================================
  Coverage          64.18%   64.18%
  Complexity           309      309
==============================================
  Files                102      102
  Lines               4420     4420
  Branches             666      666
==============================================
  Hits                2837     2837
  Misses              1415     1415
  Partials             168      168

Flag
Coverage Δ

dashboards-reports
77.61% <100.00%> (ø)

reports-scheduler
53.42% <ø> (ø)

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

Impacted Files
Coverage Δ

...r/routes/utils/visual_report/visualReportHelper.ts
80.37% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


fix: powerbi-docs/includes/gateway-onprem-faq-shared-include.md

Add code fence language
accessable -> accessible

@nschonni : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@TrishaMc : Thanks for your contribution! The author, @, has been notified to review your proposed change.

Editorial and code fence fixes verified.

@TrishaMc : Thanks for your contribution! The author, @, has been notified to review your proposed change.


Add a tag of @Test in AesEaxTest.java

Add a tag of @Test in AesEaxTest.java to avoid the test error.

please reply here

I signed it !

add another comment
I am the commit author.

please reply here

I signed it !

add another comment

I correct the email address.

Thanks!


replace logging.warn with logging.warning

logging.warn is an alias to logging.warning since Python 3.3 and will be removed in Python 3.13.

Thanks for your contribution! Please replace this text with a description of what this PR is changing or adding and why, list any relevant issues, and review the contribution guidelines below.

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.

Note that this repository uses Gerrit for code reviews. Your pull request will be automatically converted into a Gerrit CL and a link to the CL written into this PR. The review will happen on Gerrit but you can also push additional commits to this PR to update the code review.

Thanks for the contribution, @jelly !


Badges as tags

I want to use this plugin as a substitute to my tags

Please explain and expand upon what you are meaning by "substitute" for tags.


python39Packages.setuptools-rust: 1.1.2 -> 1.2.0

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

staging

Though did manage to build all (no new failures anyway) direct users of this for macos 10.15 & nixos x86_64, python 3.9 & 3.10. Along with a many indirect dependents.


Enabling HTML rendering and deployment

This PR adds the most basic github actions config for running and deploying HTML rendering of the notebooks. It also adds the rendering job to the circleCI config without removing or cleaning up any of the existing CI.
In this first iteration all the notebooks files are rendered, naturally making a sensible selection, or changes to their order/grouping should be done, and probably is best done in a follow-up focusing on more on the content than on getting the infrastructure off the ground.

Hmm, this PR is in the usual catch22 situation, e.g. the github actions are not running on it yet as no config files are present on the main branch.

However, for the sake of the review, here is the link for the rendered HTML pulled manually, use it for the review process for now: https://output.circle-artifacts.com/output/job/1d3515bc-4a35-4955-a145-bcb86f383888/artifacts/0/_build/html/index.html
(and the UX will be better for the follow-ups as the links were be included in the CI status table)

Content checking CI failure is unrelated to this PR, so I suggest to deal with it separately: https://github.com/NASA-NAVO/navo-workshop/issues/59

The basic idea looks fine, as you say just a first iteration with a simple rendering.  Note sure what else to review.  The notebooks have not been run, though, so this is not yet the content we want regardless of organization.


[Bug] [AUTHZ] Spark crashes with ClassCastException when resolving a join of masked tables

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the bug
Hi, we're using your spark-authz lib which started crashing for some workflows after upgrading 1.6.1 -> 1.7.1
This only happens when joining a table that contains masked columns even though they're not used in the join condition.
Exception in thread "main" java.lang.ClassCastException: class org.apache.kyuubi.plugin.spark.authz.ranger.datamasking.DataMaskingStage1Marker cannot be cast to class org.apache.spark.sql.catalyst.plans.logical.Join (org.apache.kyuubi.plugin.spark.authz.ranger.datamasking.DataMaskingStage1Marker and org.apache.spark.sql.catalyst.plans.logical.Join are in unnamed module of loader 'app')
 	at org.apache.spark.sql.Dataset.resolveSelfJoinCondition(Dataset.scala:1069)
 	at org.apache.spark.sql.Dataset.join(Dataset.scala:1117)
       [..] our code

This should be enough to reproduce it:
val df0 = sqlContext.table("table_with_masked_col") // only col2 is masked which is not used
      .select($"col0", $"col1")

    df0.as("a")
      .join(
        right = df0.as("b"),
        joinExprs = $"a.col0" === $"b.col0" && $"a.col1" === $"b.col1",
        joinType = "left_outer") // crashes

We had to downgrade to 1.6.1 where this doesn't happen.
Affects Version(s)
1.7.1
Kyuubi Server Log Output
No response
Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
No response
Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
[X] No. I cannot submit a PR at this time.

I understand the issue. thanks for reporting this

@pilietis93 Hello, can you full in some information about this bug , so I can reproduce it. Such as your spark-version and mark rule.

@xza-m we use Spark 3.3.2, col2 is masked with "nullify" option via a tag based policy. Let me know if you need further info.


BREAKING CHANGES

As a result of your feedback and as a continuation of the execution of our long term roadmap, there will be breaking changes coming soon. The last time we had a major breaking change, it was for the implementation of v3 Web API support. We announced those changes here on GitHub along with some instructions on how to test and provide feedback.
The feedback we got was amazing, but we didn't quite get the amount or thoroughness of feedback we were hoping for.
We want to continue improving this iterative process, so we are reaching out to you for feedback in order to determine the optimum way to move forward as this library is designed to be community driven, SendGrid led.
Please take a moment to share your thoughts with us.
Following are some ideas we are considering, we will likely choose one from Execution and one from Communication, but not all of the items below.
Execution (for large changes):

Utilize the pre-release functionality in GitHub to gather feedback and contributions to a specific branch
Communicate through a dedicated GitHub issue that references that pre-release branch (e.g C# Dynamic Update)

Communication:

Continue using GitHub issues
Opt-in email newsletter for announcements
Opt-in email mailing list
Dedicated social media account (e.g. @sendgrid_libraries)

How do you prefer to get these announcements? Is this too much? Too little? Please let us know!!
As always, we are listening carefully and are looking forward to working with you.
Note: We will always follow the semver.org convention of using major point releases to signify breaking changes. Please DO NOT auto-update your dependencies. It is important to take a look at the CHANGELOG or releases to find out how the breaking changes will impact your code.

As far as I can see in 5.0.4, we cannot set any curl option in the client.
This is a big lack of flexibility.
This broken #149 and #157

@ninsuo,
Thanks, that is great feedback!
I'm thinking the change would go here: https://github.com/sendgrid/php-http-client/blob/master/lib/Client.php#L42
Would you like to give it a shot with a PR, or would you like us to create a ticket for a fix?
With Best Regards,
Elmer

Yep, we need this quickly and your implementation is quite simple, so I will open a PR tomorrow.
Thanks,

Awesome, thank you @ninsuo!

I would like Execution 2 (although I prefer 1 but GitHub notifications don't work well along with that) and Communication 2.
Is that the kind of feedback you're looking for?

Yes, thanks @lode!


Order Loglevel Enums by decreasing severity

I find this ordering easier to relate to when deciding levels in config

OPS Build status updates of commit e775eb8:
:clock10: Preparing: average preparing time is 3 min(s) 23 sec(s)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: randsu sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

OPS Build status updates of commit e775eb8:
:clock10: Incremental building: average incremental building time is 10 min(s) 15 sec(s)

OPS Build status updates of commit e775eb8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

aspnet-core/xml/Microsoft.Extensions.Logging/LogLevel.xml
:white_check_mark:Succeeded

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

per the readme:
API PR's ( api/autoapi/... ) should not be made here. Changes to API documentation should be made in the source repository against the triple slash /// comments.


Update WhiteListPathForCerts for "Verify Signed Installers" task and fix msbuild arguments

Forgot to update the hard-coded WhiteListPathForCerts in the previous PR: https://github.com/microsoft/IIS.Common/pull/22
Fixed the bug on msbuild arguments introduced by https://github.com/microsoft/IIS.Common/pull/24

@bariscaglar ping on this PR


Oak Wood being sent to craft Sand instead of Cobblestone

Issue description:
I'm using a processing pattern with OreDict on in a Nuclearcraft Manufactory to convert cobblestone to sand. Instead, it sends Oak Wood, despite the recipe being set to Cobblestone instead, leading to the system being stuck on a "Machine won't accept item" error.
I've also noticed this with the Thermal Expansion Pulverizer, but there is no error and RS sends the wood in, making sawdust instead of the expected sand.
What happens:
Oak Wood is being sent to craft Sand.
What you expected to happen:
Cobblestone should be sent to craft Sand.
Steps to reproduce:
Pulverizer

Set up a Pulverizer to accept the items from a Crafter.
Create a processing pattern to make Sand from Gravel. Turn OreDict on.
Place into the Crafter, and request some sand.
Logs will be placed into the Pulverizer instead of Gravel, making Sawdust instead of Sand..

Manufactory

Repeat steps 1-3 above for a Manufactory, and replace Gravel with Cobblestone.
The system will give a "Machine won't accept item" error for the Wood it's trying to place into the Manufactory.

Workaround
Turn off OreDict when making processing patterns.
Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: <IP_ADDRESS>84
Refined Storage: 1.6.11

Does this issue occur on a server? Yes, and happens on single-player worlds as well.

I'm using a processing pattern with OreDict on in a Nuclearcraft Manufactory to convert cobblestone to sand.
Oredict, huh.
Is there any change that wood and cobble are in the same oredict group?
Nonetheless, maybe turning Oredict off might help.

I can't reproduce this.

There is wood, so if it could use that, it would:

Furthermore, when actually debugging, the debugger only tells me sand is allowed:

This makes me think your oredictionary is configured wrongly in your pack, and thus is not an RS issue.

Now that I'm thinking about it, Immersive Railroading adds an OreDict tag to all forms of Wood and Cobble as railbed filler. Maybe the bug is due to both being OreDict'd as railbed filler and RS is autocrafting based on that.

Yes, this is a limitation in the Forge ore dictionary. RS can only base itself on that, so the data has to be correct.

Bit of a necro, but google may help someone else one day.  I had the same issue trying to make glass from gravel.  Oredict was causing it to try to grind cobblestone for the exact same reason.  Turning off oredict for that one recipe seems to have fixed it


Refactor/disable prev next when first last page

#26

Codecov Report

Merging #27 into master will increase coverage by 0.82%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
+ Coverage   81.39%   82.22%   +0.82%
==========================================
  Files           1        1
  Lines          43       45       +2
  Branches       13       13
==========================================
+ Hits           35       37       +2
  Misses          5        5
  Partials        3        3

Impacted Files
Coverage Δ

src/components/Paginate.vue
82.22% <100%> (+0.82%)
:arrow_up:

Continue to review full report at Codecov.

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


update dependencies

Codecov Report
Patch coverage has no change and project coverage change: -0.06 :warning:

Comparison is base (0913eef) 73.37% compared to head (05e55d8) 73.31%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #952      +/-   ##
==========================================
- Coverage   73.37%   73.31%   -0.06%
==========================================
  Files         133      133
  Lines       14760    14760
==========================================
- Hits        10830    10822       -8
- Misses       3307     3313       +6
- Partials      623      625       +2

Impacted Files
Coverage Δ

pkg/tracing/tracing.go
35.63% <ø> (ø)

pkg/filters/validator/basicauth.go
75.38% <0.00%> (-1.16%)
:arrow_down:

pkg/cluster/cluster.go
60.10% <0.00%> (-0.53%)
:arrow_down:

pkg/filters/proxies/httpproxy/pool.go
82.49% <0.00%> (-0.48%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


BUG：MOTO360 5.0.2 ClockworkHomeGoogle.apk  decompile error

1、The folder name changes, and lost RAW folder, See the picture。

2、Compiled files can not be used, it would lead to moto360 not boot properly.
Attach the framework-res and files, for testing.
http://pan.baidu.com/s/1eQvolY6

None of the files in res/raw have an extension, which makes this a duplicate of #921.

When I put all the manual after anti compiler is not consistent with the original directory of APK plus -v4, is a directory with the original APK directory, again compiled APK can work.
This should be a BUG, please fix.

No, it is a duplicate of a bug. Trust me, I know my bug tracker.
v4 - #928
res/raw - #921

Thank you for your work, this is indeed a problem, expecting to solve :)


wiki: document struct tag usage

Problem: Due to increased usage of Go and thus Go struct tags, clashes become inevitable.
Proposed Solution: Offer an IANA like registry for struct tags for publically available projects/libraries.
Background:
Go offers struct tags which are discoverable via reflection. These enjoy a wide range of use in the standard library in the JSON/XML and other encoding packages. The community welcomed them and build ORMs, further encodings, flag parsers and much more around them.
Since esp. while handling encodings and ORMs single sourcing data structures is beneficial for data structures.

Seems like a new wiki page would be sufficient, at least to start.

If IANA want to host this more power to them, I don't think this is the
sort of thing the Go team needs to be involved in.
On Mon, 14 Mar 2016, 04:06 Brad Fitzpatrick<EMAIL_ADDRESS>wrote:

Seems like a new wiki page would be sufficient, at least to start.
—
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/14805#issuecomment-196002226.

I'm in favor of a wiki page. If someone wants to do that, please go right ahead.

Started the wiki page here: https://github.com/golang/go/wiki/Well-known-struct-tags and feedback and contribution is very welcome.

@nightlyone nice work. Now we just need people to add all the non-standard-library stuff.

@nightlyone : Would you like help on reviewing all libraries under github and documenting them here? Is that the expectation of the issue?

@balanatarajan yes, that is certainly the idea. But your help would be very welcome!

The page exists and looks up to date, I don't think there's anything else to do here.


Fix master registry bug

Purpose of the pull request
This pull request adds the threadsafe for Master registry and fix the slot distribution bug.

Codecov Report

Merging #6944 (3138cd4) into dev (94f6c5c) will decrease coverage by 0.08%.
The diff coverage is 14.28%.

@@             Coverage Diff              @@
##                dev    #6944      +/-   ##
============================================
- Coverage     33.14%   33.06%   -0.09%
+ Complexity     1622     1618       -4
============================================
  Files           433      433
  Lines         14290    14290
  Branches       1426     1426
============================================
- Hits           4737     4725      -12
- Misses         9101     9116      +15
+ Partials        452      449       -3

Impacted Files
Coverage Δ

...inscheduler/service/queue/MasterPriorityQueue.java
0.00% <0.00%> (ø)

...uler/server/master/registry/ServerNodeManager.java
1.29% <33.33%> (ø)

...r/plugin/registry/zookeeper/ZookeeperRegistry.java
47.27% <0.00%> (-7.28%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
37.77% <0.00%> (-2.23%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.35% <0.00%> (-1.70%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
52.11% <0.00%> (-1.41%)
:arrow_down:

Continue to review full report at Codecov.

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

hi @rewerma , please see the sonar analysis and make UTpass.

No update for nearly a month, and there are conflicts, I'm closing, if @rewerma you are back to this work, feel free to reopen


Add newline conversion for stdout

As noted by @kjbracey-arm, mbed currently prints \r and \n unmodified to stdout and most serial terminals default to requiring a \r\n sequence to actually create a newline. This results in non-standard io for many setups, since the C standard states that \n will be converted to the underlying newline sequence[1]. Annoyingly, this has resulted in the \r\n being used in many programs.
In this patch, stdout/stdin do the following conversions greedily (without delays):
on write:
\n   -> \r\n
\r\n -> \r\n
\r   -> \r
\n\r -> \n\r

on read:
\n   -> \n
\r\n -> \n
\r   -> \n
\n\r -> \n

Serial.output provides support for unmodified binary output (and still requires \r\n). This conversion remains backwards compatibly for all \r\n sequences and only impacts stdio that uses \n or \r in isolation.
cc @kjbracey-arm, @bogdanm
mv #91, #93

cc @adamgreen @Sissors @neilt6

Just to chip in. There's an important difference between '\n' which C defines as "new line" (down AND to the left), and LF which is almost universally interpreted by terminals as "line feed" (down only).
In C strings, ASCII implementations universally encode '\n' as ASCII LF ('\x0a'), but to achieve C's required semantics, the LF must be converted to CR+LF before it reaches a standard terminal.
In POSIX systems this is achieved via stty's ONLCR setting (on by default) which converts LF output from a program to CR+LF. On an embedded system like this, where there is no external line discipline for the serial device, it makes sense for the C library itself to do the conversion (ideally only in binary mode, but only ARMCC's library properly implements the binary flag).
Regardless, someone needs to do it between the application and the serial output.
Otherwise people end up writing "Hello\r\n" in their C code, which is a tautology - moving left twice in a row. And puts() just isn't useful.

Last time I was in the loop about this change, we discussed conditionally eanbling it with a macro, to ensure backward compatibility. I still think that's a good idea.

Agreed. But my vote is for default on.

Agreed. But my vote is for default on.

That would kinda kill the backward compatibility thing though :)

If I am correct this only affects printf, right? And not pc.printf statements? And also not if I retarget stdio to for example an LCD display?
In that case, only downside I see is a discrepancy between pc.printf and printf statements, but even with that seems like good idea to me.

This only affects stdout/stderr/stdin through the C/C++ libraries - the C retarget.cpp does the conversion between those before sending to the serial device.
All direct serial access through mbed APIs is unaffected. The mbed Serial class is also unaffected - it goes through stdio, but is treated by stdio as a file rather than a TTY.
Arguably this patch could be doing the conversion for underlying files that return isatty true, not just stdin/stdout/stderr. Not sure if that's desired. (Serial has isatty false, so wouldn't be affected).

so this shouldn't affect to our cli interface behaviour @kjbracey-arm ? It require both characters (LF&CR) handled separately by cli library.. just want to be sure..

Do you actually require LF (move down only) as opposed to NL (down and left)? I don't think you do. I believe you only use NL ('\n') and CR ('\r').
If you did need LF, you would need to deactivate this.

seems that I'm needed only combination of  CR (\r) and CR+LF (\r\n). So LF (\n) alone is not needed at least for now, but there might be needs for that also if we start juggling with shell ;)..

Don't get confused. ASCII LF is not C '\n'. C '\n' is newline. That's what this PR is about.
Saying "LF (\n)" is a contradiction - they're two different things, that just happen to be represented by the same character code. But that character code means different things in C (down and left) and in a terminal (down only).
C doesn't offer you LF via standard text streams - there's no '\d' character specified to move the cursor down only, only '\n' for down and left.  To go down only, you'd need some sort of non-standard code, like VT100 "ESC[B", or to put the output stream in binary mode, or to bypass stdio altogether (like write direct to the serial device, so you can output LF manually).
So C's putc('\n') moves the cursor down and left, regardless of system, and regardless of character set, and regardless of what code '\n' actually is. C library and compiler do any necessary conversions to make this work. There's no formal requirement that '\n' be ASCII LF - it could in theory be \xFF, even on an ASCII system.
#define LF 0x0a then serial_putc(LF) moves the cursor down only, if the serial port is attached to a conventional ASCII terminal. C library and compiler's definition of '\n' is not involved.
serial.putc('\n') moves the cursor down only if the C compiler's '\n' happens to be the LF code for your terminal, which it is in normal ASCII C implementation. But it's a slight abuse of the '\n' symbol, using it for something other than new-line.

I'm using VT100 syntax to control terminal,,

For you, I'm saying you should use stdout, with '\r' for carriage-return, '\n' for new-line, and if you ever did want to go down only, use ESC [ B, as that's probably got the best chance of working on any system/terminal combo. (Even if the system did output plain LF, the terminal itself could be configured to treat LF as new-line).
But until this PR goes in, you actually need to do "\r\n" for new-line, because the C library's plain "\n" is broken.

Added config option with original behaviour as default. Config option: MBED_CONF_CORE_STDIO_CONVERT_NEWLINES
Please rereview

Thanks @geky . Looks fine to me

Agree default value should be present. But it would better be boolean false, rather 0. If JSON booleans worked.
Got a bad feeling we might be busy baking in lots of slightly-off config options due to a (temporary?) JSON parser limitation.
(And I'm still voting for default true, at least in the next major system release if not this patch).

But it would better be boolean false, rather 0. If JSON booleans worked.

Ah, it can work. config.py can automatically change JSON true to 1 and JSON false to 0. It's a pretty trivial change. It does mean that after this change you won't be able to actually say that a variable has the value true, since it'll always be 1, but I think this is perfectly acceptable.

:+1:

@mbed-bot: TEST
HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL


Android fixes

Hey @ashok2004 thank you for opening those issues. Can you please try this branch with your app by replacing datadog_flutter in your pubspec with below:
datadog_flutter:
  git:
    url: git@github.com:greenbits/datadog_flutter.git
    ref: android-fixes

@tshedor after these changes, android side it is working fine. No compile error, no service name null issue, no warnings of android tracing disabled.

@ashok2004 I was waiting to see if I could reproduce what you're seeing in #26 but I couldn't, so after you respond I'll cut the next dev release.


Need to add CACHE_REDIS_URL to env variables for worker.tf

Need to add:
      CACHE_REDIS_URL        = var.cache_redis_url

https://github.com/dropseed/pullapprove-enterprise/blob/master/deploy/aws/worker.tf#L27-L28

@davegaeddert FYI

@erin-collins-dd I think it's not there because it is in an SSM param instead: https://github.com/dropseed/pullapprove-enterprise/blob/a9d15f9d2d4851ee8316d8702f8405ec9b127da1/deploy/aws/ssm.tf#L25-L29


Resolve #527 Add built-in converter for java.util.Currency type

Implement CurrencyConverter

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Mirko Luchi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Is this desirable? Afaik built-in converters take precedence over custom ones which may cause trouble if I just want to handle things differently. I already consider myslef lucky I use JSR-310 backport rather than Java 8 natives.
On the other side there's Moshi which throws an exception on any object that's not standard value type or array. You have to register converters manually.

consp1racy, I perfectly agree with you that people should be free to store a Currency into the database in whichever way they prefer. But built-in converters do not take precedence over the ones specified through annotations (see GenericMapping read/write method), therefore my proposed converter would just be the default one if no other one is specified.
IMHO, the easier is to configure an entity (with any field type) the better it is.
For what concerns Moshi, I don't get the connection with my PR. If you create an object with a Currency field, it's not naturally serializable using Moshi, but you can always plug a custom type adapter (see here: https://github.com/square/moshi#custom-type-adapters).

The way Moshi works is it requires explicitly registering the adapters. As in the adapters may be included in the library but not automatically used. This requires the consumer to carefully review and register adapters they actually need.
But you're right, this is more related to requery overall than this PR in particular.

I did the required changes.

Thanks


Google Maps not loading in debug mode

Issue Description
In debug mode while developing for Android, Google Maps is failing to load on the Maps tab and the Shuttle Stop view. The map renders as just a grey background with a Google logo in the bottom corner. Investigate and fix.
Additional Information

Environment: Debug
Platform(s) (iOS, Android, or both?): Android

Issue

Per the Image above, maps do not load on android.  This occurs on the android emulator and cell phones for both QAT and PROD builds that are not final release APKs. This problem is widely associated with invalid keys.  Checking for the validity of our map key revealed that our key was valid, however, it is restricted to only work on release builds (meaning final release APKs).
Solutions
Add Debug Hash
Within the key management portal we can add the key-store hash for the debug version of the app.  The debug key-store is different for every developer and every environment. This means for every environment a new hash will have to be generated and added to the list of  acceptable keys.
Create a new API key for Debug Instances
A new unrestricted map API key could be created and used for debug versions of the app.
@c3bryant @a6wu

Thanks @vishant101 - we will add developers to the existing key as needed for the time being


Cloud9 being phased out

As Cloud9 is being phased out I'd like to see an updated CloudFormation stack to address that.

Thank you for raising this. We will test an alternative to Cloud9 and then update the repo accordingly.

Thanks for acknowledging. If/when you have an idea whether this will be included in a new release and any timeline would be greatly appreciated. Just to mention, I adjusted the CloudFormation templates to exclude and Cloud9-related services being deployed and the stack succeeded in this way (implicitly I'm saying that the template as it is right now fails to execute completely due to the Cloud9 dependencies)

@mhavey code review done.

Submitted code change (remove Cloud9 from cfn) and doc change (README). If user does not have a build machine, we give instructions how to use the notebook instance for this purpose.

Closing


OGR in wheels not distributed with Arrow read/write driver

I was just curious to see the speed difference between pyarrow.parquet.read_table and pyogrio.raw.read_arrow to see how much overhead the read_arrow had. It appears that the default pyogrio isn't built with the Arrow driver, and I get
'file.parquet' not recognized as a supported file format.

I was surprised that Arrow isn't a driver because it still works to read into Arrow memory, but I guess that's because the C Data Interface is vendored?
Given that we can use pyarrow this isn't a huge deal and you can close if you wish.

Yes, the support for reading any format as an Arrow stream (via the C Data Interface) is implemented natively in GDAL without using any Arrow C++ libraries, and so this is always available once you have GDAL >= 3.6.
On the other hand the the Arrow and Parquet drivers to read actual arrow/parquet files use the Arrow C++ library, and so this needs to be explicitly enabled when GDAL is built, and then also vendored in the wheels in case of pyogrio.
And indeed, since for those two formats (from a geopandas perspective) you can already easily use pyarrow / geopandas.read_parquet, it was 1) not a priority to try to get the wheels building with Arrow, and 2) even a bit unclear if that is worth the increase in size of the wheel.

Yep that makes sense! I'll close this


Change labels GO:0034470 ncRNA processing & children

From yesterday's microRNA call

[ ] GO:0034470 ncRNA processing is defined as "Any process that results in the conversion of one or more primary non-coding RNA (ncRNA) transcripts into one or more mature ncRNA molecules."

-> change label to 'primary ncRNA maturation'
Same for

[ ] GO:0070918 primary sncRNA processing ->  change label to 'primary sncRNA maturation
[ ] 'GO:0010599 primary lsiRNA processing'  ->  change label to 'primary lsiRNA maturation
[ ] GO:0010267 primary ta-siRNA processing  ->  change label to 'primary ta-siRNA maturation

Thanks, Pascale

We decided to keep 'processing', and made sure that the definition was clear about the production of a mature product (and not just any modification.


Permission Denied Error

I've had this error occur on two occasions when getting a list of cards registered to a user:

Warning:  file_put_contents(mangotemp/MangoPaySdkStorage.tmp.php) [function.file-put-contents]: failed to open stream: Permission denied in /home/w293s11307/public_html/mangopay_api/Libraries/DefaultStorageStrategy.php on line 49

Fatal error:  Uncaught exception 'MangoPay\Libraries\Exception' with message 'Cannot put token to file' in /home/w293s11307/public_html/mangopay_api/Libraries/DefaultStorageStrategy.php:51
Stack trace:
#0 /home/w293s11307/public_html/mangopay_api/Libraries/AuthorizationTokenManager.php(46): MangoPay\Libraries\DefaultStorageStrategy->Store(Object(MangoPay\Libraries\OAuthToken))
#1 /home/w293s11307/public_html/mangopay_api/Libraries/AuthorizationTokenManager.php(33): MangoPay\Libraries\AuthorizationTokenManager->StoreToken(Object(MangoPay\Libraries\OAuthToken))
#2 /home/w293s11307/public_html/mangopay_api/Libraries/AuthenticationHelper.php(83): MangoPay\Libraries\AuthorizationTokenManager->GetToken('cdc79767f26f785...')
#3 /home/w293s11307/public_html/mangopay_api/Libraries/AuthenticationHelper.php(27): MangoPay\Libraries\AuthenticationHelper->GetHttpHeaderStrong()
#4 /home/w293s11307/public_html/mangopay_api/Libraries/RestTool.php(239): MangoPay\Libraries\AuthenticationHelper->GetHttpHeaderKey()
#5 /home/w293s11307/public_h in /home/w293s11307/public_html/mangopay_api/Libraries/DefaultStorageStrategy.php on line 51

If I delete the file "MangoPaySdkStorage.tmp.php" which is present in the temporary directory then the application continues to work fine.
The temporary directory has permissions 0777

Hi @jonnyleigh,
It seems you are talking about a known issue. As it is written on our documentation:

If you experience problems with authentification and/or the temporary token file following an SDK update (particuarly updating to v2.0 of the SDK), you may need to just delete your temporary file (that you specify with $api->Config->TemporaryFolder) - which allows it to be regenerated correctly the next time it's needed

Does this scenario fits with your issue ?

Hi @mickaelpois, no the issue I saw was not following an SDK update, but occured "randomly" (i.e. I haven't worked out yet what caused it).
I'll keep an eye on it and report back here if it happens again.  Our application is not yet in production use.
Thanks,

Hello @jonnyleigh !
Thanks a lot, feedbacks are very welcome !
It could happend when you're switching from one Mangopay client account to another one, but I guess you are working with only one sandbox account.

@mickaelpois it happened again today

Hello @jonnyleigh
Ok, thanks again for your feedback.
We will have a look at it very soon, we will keep you posted.
Mickaël

Thanks @mickaelpois.  It appears to me that the error occurs once a day, the first time I use the SDK in that day.  If I delete the file manually then I am able to use the SDK.  As a workaround I'm going to create a cron job which attempts to delete the temporary file on a daily basis.  Please do let me know if you make any progress on this issue though.

I suspect this error is specific to your setup since we're unable to reproduce it and others don't seem to be experiencing it. Since you've also moved to the memory storage approach, I suggest we close this issue :-)


Issue #119: Add option to set initial data storage level in ImagingDy…

Description
Closes #119
Adds option to set the initial data storage level in ImagingDynModel.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How should this pull request be reviewed?

[X] By commit
[ ] All changes at once

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Passes Tests

[X] Unit tests (General Environment only) pytest --cov bsk_rl/envs/general_satellite_tasking --cov-report term-missing tests/unittest
[X] Integrated tests (General Environment only) pytest --cov bsk_rl/envs/general_satellite_tasking --cov-report term-missing tests/integration
[X] Examples (General Environment only) pytest tests/examples

Test Configuration

Python: 3.11.6
Basilisk: 2.2.2
Platform:  MacOS Sonoma 14.3.1

Checklist:

[X] My code follows the style guidelines of this project (passes Black, ruff, and isort)
[X] I have performed a self-review of my code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] Commit messages are atomic, are in the form Issue #XXX: Message and have a useful message
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works

Could you add a unit test and integrated test to demonstrate that this works?

Sure! Added integrated tests for the storageInit. I believe these are better than unit tests for this case.


Hotkeys for conflict resolution

Description
Currently GitHub's conflict resolution feature is quite cumbersome to use, as the buttons/links are quite far apart. Hotkeys would help a lot to speed up the conflict resolution time.
Example for the UI:

The usual workflow is to click "Next" top right, then at the bottom of the text field have click "Accept incoming change", then "Next" again until all conflicts are resolved and one can click "Mark as resolved". After all files are resolved from conflicts, one can click "Commit merge" to commit the resolved files.
Example URLs
https://github.com/prisma/prisma/pull/18020/conflicts

Agreed! We should match VSCode's shortcuts, if any and not already in use.

Ha, I wasn't even aware part of that comes from Refined GitHub already! Neat.
https://github.com/refined-github/refined-github/blob/main/source/resolve-conflicts.ts


Hello, wo0>���p>0 is my output lol

Hello, wo0>���p>0 is my output lol
and an odd error from dmesg:
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=467527 end=467528) time 1289 us, min 1062, max 1079, scanline start 896, end 1122
Originally posted by @AlexGatz in https://github.com/s-matyukevich/raspberry-pi-os/issues/127#issuecomment-581097384

found other issue with similar problem


Create LICENSE

using MIT license for simplicity and due to this bit in the GPL license
The GNU General Public License does not permit incorporating your program
into proprietary programs

@QuartzShard @riina are we happy with this license?


Game crashes when entering space

crash-2023-07-30_19.15.31-client.txt

Always install Indium alongside Sodium, or else you'll break mods like this.

thx


Application - Edit or Update

User Story
As an Applicant
I want to be able to edit my application
So that it can have the most recent information for the Analyst
Research & Design
https://www.figma.com/file/nhOquOVmWD1P3BxEY0KIh5/CCBC-Intake?node-id=362%3A1091
Acceptance Criteria
Given that an applicant is in the dashboard
when they click on edit
then they will be redirected to the first page of the form (Organization profile)
and it will display all the fields filled in as they had them before
then they will be able to edit them

Hey team! Please add your planning poker estimate with ZenHub @marcellmueller @BryanGK

@elliottSlee acceptance criteria may change, noting this in a comment here. what the state is changed to (whether draft or complete, etc.) is to be finalized.

@elliottSlee can we edit the acceptance criteria for editing submitted application:
Given I am an Applicant
And the application has a "Submit" status (#92)
AND the intake is still open
When I click on edit
A modal appears on the dashboard saying "Edits made to submitted applications will be saved automatically. You will not need to submit this application again" with a "Edit application" button
Then I am redirected to the first page of the respective application
And I can edit all fields
The status remains as "Submitted"
The autosave message changes to "Changes submitted: [Time]

@zoeyli-46 just flagging this ticket is done and in review

@marcellmueller can we temporarily set the intake end date to tomorrow morning so that I can test the scenarios where the intake is closed?

@MarsRomer what are the scenarios you are looking to test in this card for after the intake has closed? I'm actually just worried we missed an acceptance criteria for what to do with submitted application after the form has closed. I assume it should show View and take them to review page?
As it currently is we are doing a check for the intake date for the first checkbox in this ticket. Though the behaviour is exactly the same as it always was, ie takes you to the first page of the form.
We aren't currently locking down the submitted pages after the intake closes as I think there is a ticket incoming about submitting attachments 30 days after the intake closes.

@MarsRomer I just spoke to Zoey and it sounds like this is incoming in another ticket. I'm not sure the best way to show you that the code for the intake being closed is working given that the behaviour is the same as normal (starting on the first form page) but I'm happy to jump on a call.

I am looking to see that when the intake closes that the submitted application is no longer showing an 'edit' button, instead it will have a 'view' button.  And when I click on it, it will take me someplace in the application (possibly the review page)
Also the draft applications will continue to show the edit button.


Student grade chart

Add command to show students' grades pie chart.
Format: show grade

Codecov Report
Base: 59.69% // Head: 58.74% // Decreases project coverage by -0.95% :warning:

Coverage data is based on head (9928557) compared to base (a49396f).
Patch coverage: 5.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #93      +/-   ##
============================================
- Coverage     59.69%   58.74%   -0.96%
  Complexity      608      608
============================================
  Files           127      129       +2
  Lines          2362     2402      +40
  Branches        285      288       +3
============================================
+ Hits           1410     1411       +1
- Misses          857      896      +39
  Partials         95       95

Impacted Files
Coverage Δ

...rc/main/java/seedu/address/logic/LogicManager.java
62.50% <0.00%> (-2.72%)
:arrow_down:

...dress/logic/commands/student/ShowGradeCommand.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
62.50% <0.00%> (-2.72%)
:arrow_down:

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
54.80% <0.00%> (-10.71%)
:arrow_down:

src/main/java/seedu/address/ui/GradeChart.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

...va/seedu/address/logic/commands/CommandResult.java
64.00% <25.00%> (-24.24%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fixed bugs and unit tests

PR for #114
Also wrote more unit tests for checks' execution in case of index commands

Coverage increased (+0.03%) to 85.102% when pulling e4fca7cbc0e28a51ae00225b8ae6ebe70f361120 on 114 into 383b1948e1403882adf49b5d4f18727be64818e0 on master.


Add layer name to message when SQL error occurs

This is more a wishlist request than a real issue, but when a tile fails to load due to an SQL error, etc. in one of the layers, it would be nice if the provider layer causing the error was printed out along with the error message.
For reference, I wrote this syntactically valid, but otherwise terrible SQL query for one of my provider layers.
SELECT ST_AsMVTGeom(geometry, !BBOX!) AS geometry, osm_id, name WHERE geometry && !BBOX!

Forgot to include the table name :face_in_clouds:
When I try to request a tile that loads data from this layer, of course I get an error.
2022-07-18 11:10:13 [ERROR] handle_map_layer_zxy.go:175: error marshalling tile: ERROR: column "geometry" does not exist (SQLSTATE 42703)

In this case, it would have been helpful if the error message was something like error marshalling tile for layer "my_layer_name":  ERROR: column "geometry" does not exist (SQLSTATE 42703).

@dwoznicki I agree that would be nice, but I'm not sure this is possible when using ST_AsMVT. The error you're seeing there is generated by the database. What version of PostGIS are you using? This request might need to be fulfilled by that team.

Right, I forgot about how the ST_AsMVTGeom query is formed. Hmm, it's possible this is something PostGIS could provide a better error message, but I'm not sure how they'd get access to the provider layer name.
Regardless, I think this can probably be accomplished in plpgsql using functions. Here's a proof of concept.
-- The exec_geoms_query function takes in the SQL to execute as text and the name of the provider layer,
-- and returns the result of the SQL query, or throws a custom exception if something goes wrong.
CREATE OR REPLACE FUNCTION exec_geoms_query(sql text, layer text)
RETURNS SETOF geometry
LANGUAGE plpgsql
AS
$$
DECLARE
    exception_message text;
BEGIN
    BEGIN
        RETURN QUERY EXECUTE sql;
    EXCEPTION WHEN OTHERS THEN
        GET STACKED DIAGNOSTICS exception_message = MESSAGE_TEXT;
        RAISE EXCEPTION 'caught exception in layer "%": %', layer, exception_message;
    END;
END;
$$;

I can now use this function as the input to ST_AsMVTGeom. For testing purposes, I just tried selecting from a nonexistent table.
SELECT ST_AsMVTGeom(exec_geoms_query('SELECT geometry FROM nonexistent_table LIMIT 1', 'my_layer'), ST_MakeEnvelope(-2.0663680475625e+07,-2.0663680475625e+07,2.0663680475625e+07,2.0663680475625e+07,3857));

When I execute this from a file with psql, I get the following error.
psql:test.sql:1: ERROR:  caught exception in layer "my_layer": relation "nonexistent_table" does not exist
CONTEXT:  PL/pgSQL function exec_geoms_query(text,text) line 9 at RAISE

Here are my thoughts on this implementation:

It makes debugging SQL errors a lot easier.
Executing strings is dangerous, though this should be okay if the end user has no control over the SQL tokens, or if the tokens are sanitized.
Even without the provider layer name in the error message, I've found that I can still debug these SQL errors. It's just more time consuming.
This adds a dependency on plpgsql.
The current implementation is not backwards compatible with PostgreSQL versions < 9.2 because of GET STACKED DIAGNOSTICS.

@dwoznicki sorry for the slow response. I really like this idea! Generally speaking I like using database functions over forming up complex SQL inside of tegola. I have found it's much easier to maintain. Typically I will create a function like
layer_water(!BBOX!, !ZOOM!)
And that will return a TABLE. I do this for every layer, and often have materialized views I'm leveraging based on the !ZOOM! token. Using this approach you could actually call exec_geoms_query() inside the "layer functions" and keep the tegola config very minimal.
I think your list of "thoughts on this implement" is very accurate. I honestly would consider this best practice in a lot of ways, particularly because you can push all string sanitization, prepared statements formed in plpgsql function.
Thanks for following up with this suggestion / solution.

I'm going to close this since, as you've pointed out, I can actually write custom functions (one per layer) to improve my own debug messages.


RFC: [theme] Add borderWidth to theme.shape

[x] I have followed (at least) the PR section of the contributing guide.

The simplest way to see it in use is to test it locally and change the value of borderWidth in styles/shape.js.

@mbrookes I have mixed feeling about the direction this change puts the library in.
It's interesting to look at Bootstrap. They have around 1000 variables. These variables can be very handy. A few of them even convert to CSS variables.
Now, one SASS variable has an overhead is at build time, one JavaScript variable has an overhead at runtime. Can we sustain 1000 variables without significantly slowing down the components and increasing the bundle size? If we can, it's awesome, we should move forward. If we don't, we need to consider what are the most important variables or revisit the style approach.

I don't envisage a significant number of additional variables - there are very few characteristics like this that are common to multiple components. And it isn't so much a a change in direction as a continuation of the existing one with borderRadius.
I hadn't considered the performance implication, and it does make a difference:

But at 63.5M ops /sec, I don't believe it's a meaningful one.
The other possible interesting consideration is CSS variables, with a ponyfill for IE11: https://github.com/jhildenbiddle/css-vars-ponyfill

@mbrookes Yeah, it won't make a difference for 1 variable, but it will with 1000. The bundle size is the only dimension we track, the only one we can notice a difference. The specification has a couple of themes pre-maid: https://material.io/design/material-studies/about-our-material-studies.html. None change the border width globally. I find it unlikely that people will use this theme option to change the border width globally. They might for a few of their components, but at that point, wrapping the components with withStyles is probably simpler.

This '1000 variables' stat doesn't make for a rational argument. It's one of a handful, not one of thousands.

I find it unlikely that people will use this theme option to change the border width globally.

Okay, shall I change the PR to remove borderRadius instead? 😜

Okay, shall I change the PR to remove borderRadius instead? 😜

Right on spot. I think that it all boils down to the usage of the theme values by people. themes.material-ui.com use border-radius 4px instead of 8px. We need more people feedback on this proposal. I have imperfect knowledge of reality. Can we have an 👍 of people that are in favor: @mui-org/core-contributors.

Let's play it safe. I think that we can truly move forward in this direction when we can move the overhead to built time (from runtime). The only overhead we know if is the bundle size of the default theme object.

Another proposal: https://github.com/mui-org/material-ui/pull/16034


Wavesurfer Support in Ionic capacitor

Hello,
Can i use the wavesurfer library in Ionic capacitor project? It will be an app for Web and Android. Looking forward for your response. Thanks

No idea. Ask in the Ionic capacitor project.


chore: pim-dam to 1.0.19

chore: Promote pim-dam to version 1.0.19

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

Needs approval from an approver in each of these files:

OWNERS

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


LogLevel is not applied when the test is run.

@RyuichiNamba-fj
All NF's PRs are merged. Please help update all NF submodule hashes.

@free5gc-org
Updated all NF submodule hashes. Please check.

@RyuichiNamba-fj
We just updated n3iwf.
Please help update the n3iwf hash to the latest.
Thanks.


Assertion 'lit_is_valid_cesu8_string (string_p, string_size)' failed at jerryscript/jerry-core/ecma/base/ecma-helpers-string.c(ecma_new_ecma_string_from_utf8):371.

JerryScript revision
Commit: a6ab5e9
Version: v3.0.0
Build platform
Ubuntu 18.04.5 LTS (Linux 4.19.128-microsoft-standard x86_64)
Ubuntu 18.04.5 LTS (Linux 5.4.0-44-generic x86_64)
Build steps
python ./tools/build.py --clean --debug --compile-flag=-fsanitize=address --compile-flag=-m32 --compile-flag=-g --strip=off --lto=off --logging=on --line-info=on --error-message=on --system-allocator=on --stack-limit=20

Test case
poc-as.txt
Execution steps & Output
$ ./jerryscript/build/bin/jerry poc.js

ICE: Assertion 'lit_is_valid_cesu8_string (string_p, string_size)' failed at jerryscript/jerry-core/ecma/base/ecma-helpers-string.c(ecma_new_ecma_string_from_utf8):371.
Error: ERR_FAILED_INTERNAL_ASSERTION
[1]    abort      jerry poc.js

@rerobika  I think it is not a bug, but a feature. "𞸋" is encoded in UTF-8 as  0xF09EB88B which is invaliid in CESU8.

The issue is not with the "𞸋" character, all non-BMP characters are converted to cesu8 encoding during parsing.
The problem is that the first character is in the basic multilingual plane and should be encoded using 3 bytes, however it is encoded using 4 bytes in the input. This messes up the conversion logic, which always expects the cesu8 equivalent to be 6 bytes long.

+info, a simple "/𝔽/" string fails with the same error if we build with tools/build.py --debug --function-to-string=on


SparkR dependencies in SparkApplication

Hello,
I'm trying to launch a SparkR application using the Spark Operator
apiVersion: sparkoperator.k8s.io/v1beta2
kind: SparkApplication
metadata:
  name: sparkr-test-app
spec:
  image: <my-spark-2.4.4-image>
  mainApplicationFile: 'https://artifactory-url/test-r/main.R'
  type: R
  mode: cluster
  sparkVersion: 2.4.4
  deps:
    files:
      - 'https://artifactory-url/test-r/dep.R'
  driver:
    cores: 1
    memory: 512m
    serviceAccount: spark-sa
  imagePullPolicy: IfNotPresent
  executor:
    cores: 1
    instances: 3
    memory: 512m`

Here the main.R and dep.R
main.R
library(SparkR)
sparkR.session(appName = "SparkR-DataFrame-example")
source("dep.R")
Sys.sleep(100)
sparkR.session.stop()

dep.R
localDF <- data.frame(name=c("John", "Smith", "Sarah"), age=c(19, 23, 18))
df <- createDataFrame(localDF)
printSchema(df)
head(df)
createOrReplaceTempView(df, "people")
teenagers <- sql("SELECT name FROM people WHERE age >= 13 AND age <= 19")
teenagersLocalDF <- collect(teenagers)
print(teenagersLocalDF)

When I launch the application I get this error:
Java ref type org.apache.spark.sql.SparkSession id 1
Error in file(filename, "r", encoding = encoding) :
  cannot open the connection
Calls: source -> file
In addition: Warning message:
In file(filename, "r", encoding = encoding) :
  cannot open file 'dep.R': No such file or directory
Execution halted

It seems the dependency is not downloaded/loaded
I continue to have the same problem also with the following options
sparkConf:
  spark.files: "https://artifactory-url/test-r/dep.R"
deps:
  files:
    - "https://artifactory-url/test-r/dep.R"
  filesDownloadDir: './'

How can I import dependency files in SparkApplications for R ?
Thank you
Alessio

Spark 2.4.x changed the way dependencies are downloaded. In Spark 2.3.x you could specify the directory where the files should be downloaded to. In Spark 2.4.x, dependencies are downloaded using the built-in mechanism and they are downloaded into a random directory under the working directory. I'm not sure how SparkR works in this case.


Importing ToastVariant causes @ns to be lost

Kept getting error messages like this:
6:57:34 AM [viteburner] Error: Failed to resolve import "@ns" from "src\support\FarmServer.ts". Does the file exist?
I included the working file as an upload. On line 30, I just used the value to get it working. If I swap it out for the ToastVariant enum and import ToastVariant, I'll get error messages and the file won't upload.
toasty.txt

duplicate of #17


ARROW-3002: [Python] Hash more parts of pyarrow.Field

Codecov Report

Merging #2385 into master will increase coverage by 2.16%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2385      +/-   ##
==========================================
+ Coverage   84.66%   86.82%   +2.16%
==========================================
  Files         293      237      -56
  Lines       45324    42558    -2766
==========================================
- Hits        38372    36952    -1420
+ Misses       6911     5606    -1305
+ Partials       41        0      -41

Impacted Files
Coverage Δ

python/pyarrow/types.pxi
57.31% <100%> (ø)
:arrow_up:

python/pyarrow/tests/test_types.py
100% <100%> (ø)
:arrow_up:

go/arrow/array/boolean.go

go/arrow/math/int64_amd64.go

rust/src/bitmap.rs

go/arrow/math/int64_avx2_amd64.go

rust/src/buffer.rs

go/arrow/math/int64_sse4_amd64.go

rust/src/memory_pool.rs

go/arrow/type_traits_boolean.go

... and 48 more

Continue to review full report at Codecov.

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

__reduce__ was missing for dictionary type, but it works now

Hmm, looks like the added test messes the test for total_allocated_bytes (see AppVeyor failure).

Does total_allocated_bytes test assume, that no arrow array has been allocated before that test case?
Perhaps because MANY_TYPES is a module level variable, whic holds a ref for an array.
I can create a parametrized datatype fixture instead of a global list, which would probably keep total_allocated_bytes as zero. Is that the desired behaviour?

I wonder where the memory allocation is happening. It's possible there is a memory leak somewhere or a dangling PyObject* that has not been gc'd yet (or has leaked)

I can create a parametrized datatype fixture instead of a global list,

Or you could simply write a helper function that returns that list.

But then We can't use it for parametrization.

As you prefer. I generally feel that parametrization is overrated, though it can give more informative errors.

I can admit it has its downsides.

I personally don't care for pytest.parametrize. Among other things, it can give a false sense of a test suite being much larger than it is (I've commented to @cpcloud about this several times). It's also a bit of a bummer that parametrize does not support fixtures as arguments

I like parametrize.
The body of a test IMO should contain the "kernel" of what's being tested and a loop that's iterating over a bunch test cases is not part of that kernel. I also want to be able to specify what specific value of a parameter I can test.
parametrize was pretty useful in writing a set of tests for ibis that run a subset of tests for across each backend.
i would've wasted a lot of time and the code would've been less readable IMO if i had to write the loops by hand, and in fact i would've just been rewriting machinery that already existed.
I see no reason not to make use of tool because someone else is able to convince themselves that they are being more productive by seeing more dots on a screen. The merit of a tool shouldn't be based on how others misuse it.
As far as passing fixtures to parametrize goes, I think that probably just needs a bit of old-fashioned open source TLC: https://github.com/pytest-dev/pytest/issues/349.

Actually that's possible with indirect.
Whatever, if We want to test that total_allocated_bytes == 0 We can't use parametrization, a ref would be stored unless we parametrize with lambdas - which we obviously don't want to :)
BTW I think test_array.py::test_total_bytes_allocated is too sensitive for side effects.

Though I'm happy to defer to the existing style in a codebase, I'm not a zealot :)

Ah, I forgot about indirect. It's definitely a bit brain-melting at first.

Ah, I forgot about indirect. It's definitely a bit brain-melting at first.
I can agree with that

i would've wasted a lot of time and the code would've been less readable IMO if i had to write the loops by hand, and in fact i would've just been rewriting machinery that already existed.

This is what I don't understand. Writing a loop isn't more costly than writing a decorator...
And the idea that we shouldn't use loops in tests while we use them all the time in regular code sounds a bit weird to me.

Writing a loop isn't more costly than writing a decorator...

What is the cost function here? What about when you want to parallelize your tests? This is much more tractable if the thing parallelizing your tests also controls the case iteration.
Ultimately this is a religious debate and probably counterproductive. Let's agree to disagree here.

Writing a loop isn't more costly than writing a decorator...

I'm of @pitrou's mindset on this aspect, but I'm not going to make anyone change any code. I would rather write loops and put the "kernel" of the test function in a helper function (like the _check_$THING functions I'm so fond of writing) if it helps readability or code reuse. Refactoring plain old Python is more pleasant (to me) than Python + some parameter injection magic from pytest.
In any case, I see no point to be dogmatic. I'm generally going to write loops in my tests over parametrize

The auto-parallelization point is well taken


Missing GitHub releases due to missing pinia@* tags

Steps to reproduce the bug
Go on https://github.com/vuejs/pinia/releases -- the last release is 2.2.6.
Go to https://github.com/vuejs/pinia/tags -- the last release is 2.3.0.
Expected behavior
2.2.7, 2.2.8, 2.3.0 should be listed in the releases page.
Actual behavior
2.2.7, 2.2.8, 2.3.0 are missing from the releases page.
Additional information
By looking at the workflow, it's triggered by commits tagged with pinia@*:
https://github.com/vuejs/pinia/blob/1d8f3411deae55cd7987785bd286005fe86566be/.github/workflows/release-tag.yml#L1-L4
In https://github.com/vuejs/pinia/tags the releases up to 2.2.6 were tagged as e.g<EMAIL_ADDRESS>and were triggering the workflow.  The following releases are tagged as e.g. v2.2.7.
If the changes in the tagging format was intentional, the GitHub workflow should be updated accordingly.  If not, the tags for 2.2.7, 2.2.8, 2.3.0 should be fixed and the pinia@* format should be used for new releases.
Note that because of this, dependabot release notes are stuck at 2.2.6.

Yes, you are right! Since you found the culprit, do you want to send a PR to fix the workflow?

If you are planning to use v* moving forward, I can make a PR to fix the workflow!


Public Value Metrics for CHAOSS Tools

In our work we'll have two types of Value Metrics:

"Public" - derived from public sources like GitHub repos
"Confidential" - company-proprietary data like costs and marketing reach

We want to make maximum use of CHAOSS software tools for Public Value Metrics: Augur, Bitergia, Grimore, Prospector, Cregit, Prospector, ...
This is a call for people to get involved with tooling for Public Value Metrics:

define a set of metrics
create an implementation plan with simple mockups
build

closing in favor of #21


Composer psr-4 autoloading

Heads up that v1.8 has deprecation notices on composer update.
tests/stubs/ServerStub

Duplicate of #116


improve: redirect log to right position

Currently:

all log from cli and cortex.cpp go to log file
log from engine go to terminal

Target:

Log from CLI go to terminal
Log from cortex.cpp server and engines go to log file

[x]  cortex llamacpp[x]  cortex tensorrt llm[ ]  cortex onnx

@nguyenhoangthuan99 Did we finish the log for ONNX?

for now we have  new logger logic. We need to update the logger for both 3 engines

[ ] cortex.llamacpp
[ ] cortex.tensorrt-llm
[ ] cortex.onnx


Windows 11 - System Tray icons on taskbars on all monitors

Description of the new feature / enhancement
In Windows 11 Enable the taskbars across all monitors to show the system tray icons.
Scenario when this would be used?
Windows 11 only allows the Sys Tray icons to be shown on the Task bar on the Default monitor.
This was possible in Windows 10, but not in 11. Perfect challenge for the PowerToys community.
Supporting information
https://answers.microsoft.com/en-us/windows/forum/all/is-there-an-option-to-have-the-tray-icons-on-all/1391359b-6c79-4fc8-a31b-df170e2eb5a2
https://www.reddit.com/r/Windows11/comments/u6c39f/system_tray_on_all_monitors/
https://www.elevenforum.com/t/how-to-display-all-tray-icons-on-all-monitors.15925/
https://forums.tomshardware.com/threads/display-system-tray-on-all-monitors.3738942/
https://linustechtips.com/topic/1481765-show-system-tray-icons-on-multiple-monitors/

/feedbackhub


pull request for e2e test at 01/30/2017 23:26:13

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


updating fzf disturbed the directory name view in the quickfixlist

Category

[ ] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[ ] Completion
[ ] Vim
[x] Neovim
[ ] Etc.

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Windows Subsystem for Linux
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

I just updated my neovim plugins today and when I used fzf after updaing it was creating a view like this everytime. FZF is opened but not visible and when I will start typing it will become visible.
Please help me in fixing this problem. I really love this plugin and I also wanted to thank all of you for creating an awesome plugin like this.

Can you reproduce the problem with the minimal configuration? (without any other plugins and settings)
You can test with this command:
nvim -Nu <(curl https://gist.githubusercontent.com/junegunn/6936bf79fedd3a079aeb1dd2f3c81ef5/raw)

Hi @lalitmee, any luck reproducing the issue?

@LuRst it was a long time ago. But now I don't have that problem. The problem I face now is that everytime I start neovim, I need to source init.vim to get fzf working. This problem doesn't seem to be there in Gvim.

What happens when you don't source init.vim in vim and try to run fzf?


Lazy init prop_exists func due to hit to startup time

Issue: https://github.com/iTwin/itwinjs-backlog/issues/704

Please explain what you observed to prompt this change and when it started. When will the "lazy" function now be hit?

Please explain what you observed to prompt this change and when it started. When will the "lazy" function now be hit?

This was reported by @nick4598 .  According to him it's added startup time to the backend and if it can be avoided. The code in question runs a query that results in the download of multiple 4Mb blocks for v2 a checkpoint. Which can be avoided so my change is regarding that. The query itself is not slow; the download blocks add time.

/azp run imodel-native


error while loading shared libraries: libopencv_gapi.so

Describe the bug
Running aitrack gives me the error of aitrack: error while loading shared libraries: libopencv_gapi.so.406: cannot open shared object file: No such file or directory, and doesn't open.
To Reproduce
Steps to reproduce the behavior:

Run aitrack

Expected behavior
The program should not error.
Environment

Operating system version: Arch Linux
Webcam model: not applicable
AITrack version: 0.7.1_1_alpha-1 (installed through provided PKGBUILD)

Additional context
The program was working fine before. Though, after I updated my system a little while ago, it can't open anymore.

Can you confirm if uninstalling and reinstalling aitrack solves the issue?

$ sudo pacman -Runs aitrack
$ cd /tmp
$ git clone https://github.com/mdk97/aitrack-linux
$ cd aitrack-linux
$ makepkg -si

After uninstalling and reinstalling it does in fact work! Probably because it recompiled. Thank you.


Handle API warnings

Currently, we handle API errors, but not warnings. We should do better (putting my money where my mouth is: https://phabricator.wikimedia.org/T295215#7489064).

For the record, I already have some local code for this, but I haven’t pushed it yet. I can probably do it soon, though.

Hm, I’m not yet sure how this should interact with combining requests. When two requests with the same warn option are combined into one, and the response has warnings, should warn() be called once or twice?
And does the answer to that change when we add additional context to errors and warnings, such as the parameters for the request? What does that look like for combined errors/warnings, anyways?

I think for now I’ll have warn() be called twice, as if the requests hadn’t been combined. (Though the warnings could only apply to some of the original requests, of course.)

Done in @12989709daccf17a5e8e29a0823b73835e7d252a. We can still tweak it before the 1.0.0 release.


New theme: Adam & Eve

Theme submission
Hello,
I'm happy to suggest a new theme called Adam & Eve. It's a wiki-like. I think it was missing in Hugo Theme repository.
I make it very simple, clean and responsive (as far as I know). I'm not a designer, that's why I make it so simple :sweat_smile:.
Here is the link to the repository: https://github.com/blankoworld/hugo_theme_adam_eve
I use it for 2 wiki I migrated from Dokuwiki to Hugo.
I made sure that...

[x] the repository contains a good README.md describing my theme
[x] an open source license has been added to LICENSE.md
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] the site's content is as neutral as possible (contains no ads etc.) and reflects the features of my theme

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

=> There is no "toCSS" or "PostCSS" in my theme.

Hello Olivier,
thank you for sharing this theme with the Hugo community. Your theme should be listed soon on the themes site.
Furthermore, I'll promote your theme on Hugo's official Twitter account.
Regards,
Digitalcraftsman


read_ccd_data_in_interval now uses partitioning for faster accessing

Improves performance for slow internet connections. See issue #138

if it looks ok now can you approve @skymandr ?

I cannot get this to work with l1b data..?

I cannot get this to work with l1b data..?

At a guess this is because the L1B-data in all current versions have a residual prefix in the form of the L1A-bucket from which it originates. This needs to be put in the path (or alternatively the prefix-attribute where applicable) explicitly. See the coverage script that I sent you for an example.

I cannot get this to work with l1b data..?

At a guess this is because the L1B-data in all current versions have a residual prefix in the form of the L1A-bucket from which it originates. This needs to be put in the path (or alternatively the prefix-attribute where applicable) explicitly. See the coverage script that I sent you for an example. Note that this prefix will be removed in future versions.

yes ill do a patch for this before we merge

I think that functionality might be better to have in Mats-utils than in this function to be fair.

I cannot get this to work with l1b data..?

At a guess this is because the L1B-data in all current versions have a residual prefix in the form of the L1A-bucket from which it originates. This needs to be put in the path (or alternatively the prefix-attribute where applicable) explicitly. See the coverage script that I sent you for an example. Note that this prefix will be removed in future versions.

yes ill do a patch for this before we merge

I think that functionality might be better to have in Mats-utils than in this function to be fair.

yes, agreed. I will add it there, just want to test it before mergning in this ;)


ebedtls数据无法抓取

Describe the bug
A clear and concise description of what the bug is.
ebedtls使用的类库与ecapture hook的相同，但是无法抓取。不知原因是什么。
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Linux Server/Android (please complete the following information):

Env: [run make env to get the environment variables]
OS: [e.g. Ubuntu 21.04]
Arch: [e.g. arm_aarch64]
Kernel Version: [e.g. 5.10]
Version: [e.g. 0.1.3-20220313-69c1e0]

Additional context
Add any other context about the problem here.

去 ebedtls 项目提交你的疑问更合适，另外建议提供详细的背景信息


support multiple roles in MakeCode

Can we make it easier to have multiple roles for the same service by generating more than one fixed instance per service.

fixed by adding 2 button roles


⚠ ClamAV has degraded performance

In 79820dc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 190 ms

Resolved: ClamAV performance has improved in 170d015 after 5 minutes.