pipelines-api, oidc-gatekeeper, and dex-auth in CrashBackoffLoop after deploy

This is with juju 2.8.5, deploying version 9af36dc8d1b3ee5d090cb36fea2f797c52858816 of this repo on microk8s v1.19.2.
ubuntu@rufflet:~$ microk8s.kubectl get pods --all-namespaces
NAMESPACE          NAME                                           READY   STATUS             RESTARTS   AGE
kube-system        calico-kube-controllers-847c8c99d-pjdbd        1/1     Running            0          20h
kube-system        coredns-86f78bb79c-lx89z                       1/1     Running            0          20h
kube-system        calico-node-9frzm                              1/1     Running            0          20h
kube-system        metrics-server-8bbfb4bdb-cvswm                 1/1     Running            0          20h
kube-system        kubernetes-dashboard-7ffd448895-rd8d7          1/1     Running            0          20h
kube-system        dashboard-metrics-scraper-6c4568dc68-5psvm     1/1     Running            0          20h
kube-system        hostpath-provisioner-5c65fbdb4f-xrmpw          1/1     Running            0          20h
controller-micro   controller-0                                   2/2     Running            2          20h
controller-micro   modeloperator-5d9fd66694-zp69j                 1/1     Running            0          20h
metallb-system     speaker-lljfj                                  1/1     Running            0          19h
metallb-system     controller-559b68bfd8-55hxn                    1/1     Running            0          19h
kubeflow           modeloperator-66d8cd69c6-84srb                 1/1     Running            0          76m
kubeflow           ambassador-operator-0                          1/1     Running            0          75m
kubeflow           argo-controller-operator-0                     1/1     Running            0          75m
kubeflow           argo-ui-operator-0                             1/1     Running            0          74m
kubeflow           argo-ui-54d5cfcf67-8gg62                       1/1     Running            0          74m
kubeflow           katib-ui-operator-0                            1/1     Running            0          74m
kubeflow           dex-auth-operator-0                            1/1     Running            0          74m
kubeflow           jupyter-controller-operator-0                  1/1     Running            0          74m
kubeflow           jupyter-web-operator-0                         1/1     Running            0          73m
kubeflow           katib-controller-operator-0                    1/1     Running            0          73m
kubeflow           ambassador-8bb997fbc-4vvhh                     1/1     Running            0          75m
kubeflow           katib-ui-566d5b6d9d-zcm5m                      1/1     Running            0          73m
kubeflow           katib-db-operator-0                            1/1     Running            0          73m
kubeflow           katib-db-manager-operator-0                    1/1     Running            0          73m
kubeflow           jupyter-controller-6bf6576545-z2h4s            1/1     Running            0          73m
kubeflow           katib-controller-75fc7c4677-rl5j6              1/1     Running            0          73m
kubeflow           katib-db-0                                     1/1     Running            0          73m
kubeflow           metadata-ui-operator-0                         1/1     Running            0          72m
kubeflow           pipelines-db-operator-0                        1/1     Running            0          72m
kubeflow           katib-db-manager-6478487499-stkl7              1/1     Running            0          73m
kubeflow           pipelines-persistence-operator-0               1/1     Running            0          72m
kubeflow           pipelines-visualization-operator-0             1/1     Running            0          72m
kubeflow           pytorch-operator-operator-0                    1/1     Running            0          72m
kubeflow           metadata-db-operator-0                         1/1     Running            0          72m
kubeflow           metadata-api-operator-0                        1/1     Running            0          72m
kubeflow           pipelines-visualization-5df6fc7f9b-4qct6       1/1     Running            0          72m
kubeflow           pytorch-operator-7b7fd58bcb-tktl8              1/1     Running            0          72m
kubeflow           minio-operator-0                               1/1     Running            0          72m
kubeflow           pipelines-db-0                                 1/1     Running            0          72m
kubeflow           pipelines-api-operator-0                       1/1     Running            0          71m
kubeflow           pipelines-viewer-operator-0                    1/1     Running            0          71m
kubeflow           kubeflow-profiles-operator-0                   1/1     Running            0          71m
kubeflow           metadata-db-0                                  1/1     Running            0          72m
kubeflow           minio-0                                        1/1     Running            0          71m
kubeflow           argo-controller-558457b4f5-mfl2b               1/1     Running            0          71m
kubeflow           metadata-envoy-operator-0                      1/1     Running            0          71m
kubeflow           pipelines-viewer-78f6989fc-2f26g               1/1     Running            0          71m
kubeflow           metadata-api-7558d4c879-9wc5b                  1/1     Running            1          71m
kubeflow           metadata-grpc-operator-0                       1/1     Running            0          71m
kubeflow           oidc-gatekeeper-operator-0                     1/1     Running            0          70m
kubeflow           jupyter-web-6b44f59cfb-ppfh8                   1/1     Running            0          71m
kubeflow           pipelines-scheduledworkflow-operator-0         1/1     Running            0          70m
kubeflow           metadata-ui-d496d9c8c-tg4h9                    1/1     Running            0          70m
kubeflow           metadata-grpc-657b88cb95-6ck9t                 1/1     Running            0          70m
kubeflow           metadata-envoy-9d9679df8-7ds55                 1/1     Running            0          70m
kubeflow           metacontroller-operator-0                      1/1     Running            0          70m
kubeflow           pipelines-ui-operator-0                        1/1     Running            0          70m
kubeflow           pipelines-scheduledworkflow-76ffdfbd68-j8rt4   1/1     Running            0          70m
kubeflow           seldon-core-operator-0                         1/1     Running            0          69m
kubeflow           metacontroller-cc67694b7-grqbp                 1/1     Running            0          69m
kubeflow           tf-job-operator-operator-0                     1/1     Running            0          69m
kubeflow           kubeflow-dashboard-operator-0                  1/1     Running            0          69m
kubeflow           pipelines-ui-78dd896755-kznvn                  1/1     Running            0          69m
kubeflow           seldon-core-ddcbdf6c9-vr4dj                    1/1     Running            0          69m
kubeflow           tf-job-operator-66bd5b9997-44qtp               1/1     Running            0          69m
kubeflow           kubeflow-dashboard-689ddb8844-7j9h6            1/1     Running            0          69m
kubeflow           kubeflow-profiles-7d5f66cff8-ww647             2/2     Running            5          71m
kubeflow           oidc-gatekeeper-5c54d7b849-kqjhw               0/1     CrashLoopBackOff   18         70m
kubeflow           pipelines-api-9c77b9b65-qnt8r                  0/1     CrashLoopBackOff   15         71m
kubeflow           dex-auth-6d567f8cf7-6b4zn                      0/1     CrashLoopBackOff   18         70m
kubeflow           pipelines-persistence-76944457d4-wcnsv         1/1     Running            13         71m

ubuntu@rufflet:~$ microk8s.kubectl logs oidc-gatekeeper-5c54d7b849-kqjhw -nkubeflow
time="2020-10-27T17:14:07Z" level=info msg="Starting readiness probe at 8081"
time="2020-10-27T17:14:07Z" level=fatal msg="Env variable CLIENT_SECRET missing, exiting."
ubuntu@rufflet:~$ microk8s.kubectl logs pipelines-api-9c77b9b65-qnt8r -nkubeflow
I1027 17:14:16.709378       1 client_manager.go:135] Initializing client manager
I1027 17:14:16.709513       1 config.go:46] Config DBConfig.ExtraParams not specified, skipping
F1027 17:15:16.784068       1 client_manager.go:351] Failed to create Minio bucket. Error: Access Denied.
ubuntu@rufflet:~$ date
Tue Oct 27 17:16:58 UTC 2020
ubuntu@rufflet:~$ microk8s.kubectl logs dex-auth-6d567f8cf7-6b4zn -nkubeflow
time="2020-10-27T17:15:01Z" level=info msg="config using log level: debug"
time="2020-10-27T17:15:01Z" level=info msg="config issuer: /dex"
time="2020-10-27T17:15:01Z" level=info msg="kubernetes client apiVersion = dex.coreos.com/v1"
time="2020-10-27T17:15:01Z" level=info msg="creating custom Kubernetes resources"
time="2020-10-27T17:15:01Z" level=info msg="checking if custom resource authcodes.dex.coreos.com has been created already..."
time="2020-10-27T17:15:01Z" level=info msg="The custom resource authcodes.dex.coreos.com already available, skipping create"
time="2020-10-27T17:15:01Z" level=info msg="checking if custom resource authrequests.dex.coreos.com has been created already..."
time="2020-10-27T17:15:01Z" level=info msg="The custom resource authrequests.dex.coreos.com already available, skipping create"
time="2020-10-27T17:15:01Z" level=info msg="checking if custom resource oauth2clients.dex.coreos.com has been created already..."
time="2020-10-27T17:15:01Z" level=info msg="The custom resource oauth2clients.dex.coreos.com already available, skipping create"
time="2020-10-27T17:15:01Z" level=info msg="checking if custom resource signingkeies.dex.coreos.com has been created already..."
time="2020-10-27T17:15:01Z" level=info msg="The custom resource signingkeies.dex.coreos.com already available, skipping create"
time="2020-10-27T17:15:01Z" level=info msg="checking if custom resource refreshtokens.dex.coreos.com has been created already..."
time="2020-10-27T17:15:01Z" level=info msg="The custom resource refreshtokens.dex.coreos.com already available, skipping create"
time="2020-10-27T17:15:01Z" level=info msg="checking if custom resource passwords.dex.coreos.com has been created already..."
time="2020-10-27T17:15:01Z" level=info msg="The custom resource passwords.dex.coreos.com already available, skipping create"
time="2020-10-27T17:15:01Z" level=info msg="checking if custom resource offlinesessionses.dex.coreos.com has been created already..."
time="2020-10-27T17:15:01Z" level=info msg="The custom resource offlinesessionses.dex.coreos.com already available, skipping create"
time="2020-10-27T17:15:01Z" level=info msg="checking if custom resource connectors.dex.coreos.com has been created already..."
time="2020-10-27T17:15:01Z" level=info msg="The custom resource connectors.dex.coreos.com already available, skipping create"
time="2020-10-27T17:15:01Z" level=info msg="config storage: kubernetes"
time="2020-10-27T17:15:01Z" level=info msg="config static client: Ambassador Auth OIDC"
time="2020-10-27T17:15:01Z" level=info msg="config skipping approval screen"
failed to initialize server: server: no connectors specified

http://paste.ubuntu.com/p/t5khN6bchC/ same/similar issue with the bundle from the charm store

This seemed to have been an issue of the specific bundle and juju version mentioned in the issue. With this not ocurring in the latest bundle and juju version we will procede to close this issue.


Helm chart

Is there any reason why the chart was removed back in April? Is there a better chart available somewhere else?

Is there any reason why the chart was removed back in April? Is there a better chart available somewhere else?

Hello, thank for issue. All charts was moved to this repo: https://github.com/CRASH-Tech/charts


Force UTC dates

Can one force UTC dates? I know we can set locales, but (correct me if I'm wrong) there's no UTC locale.
The idea is that all users see the same UTC time, whatever their locale. Currently it seems like default timezones are being used, so even though I'm passing an object with a UTC date time, it shifts the boxes in the weekview according to my timezone.

You are correct, there is no UTC locale. Locales are for languages, while UTC is a timezone.
Working with timezones is still a bit rough in this library, since the WeekView component always shows the dates with the timezone in the user's phone.
I have had a similar issue, my current workaround (without any additional library) is to manually create a date with the UTC values before passing it to events:
  const date = new Date(2022, 2, 1, 15) // any date in your timezone
  const utcDate = new Date(
    date.getUTCFullYear(),
    date.getUTCMonth(),
    date.getUTCDate(),
    date.getUTCHours(),
    date.getUTCMinutes(),
    date.getUTCSeconds(),
    date.getUTCMilliseconds(),
  );
  return utcDate;

In the future we could support timezones, suggestions are welcomed :rocket:

That works, thank you @pdpino!


NTLM authentication New Extension Request:

Describe the feature
test API call that we need to have NTLM authentication
Environment

Version: 0.4.0
Engine: webkit
EngineVs: 537.36
Supporter: chrome
SupporterVs: <IP_ADDRESS>
System: windows
SystemVs: 10
Platform: Web

@evilevilevil110 Get it.
In fact, our plug-in can be extended, and only need to write some conversion code to inject authentication logic.
like：https://github.com/Postcatlab/postcat-extensions/tree/main/packages/postcat-basic-auth


FileNoteFoundError: imagenet_1k/train

When I ran (imagenet_test_ood_mds.sh),
python main.py \
--config configs/datasets/imagenet/imagenet.yml \
configs/datasets/imagenet/imagenet_ood.yml \
configs/networks/resnet50.yml \
configs/pipelines/test/test_ood.yml \
configs/preprocessors/base_preprocessor.yml \
configs/postprocessors/mds.yml \
--num_workers 4 \
--ood_dataset.image_size 256 \
--dataset.test.batch_size 256 \
--dataset.val.batch_size 256 \
--network.pretrained True \
--network.checkpoint 'results/checkpoints/imagenet_res50_acc76.10.pth' \
--merge_option merge

I received an error saying that
FileNotFoundError: [Errno 2] No such file or directory: './data/images_largescale/imagenet_1k/train/n02113978/n02113978_2340.JPEG'

I assume that I need to download the train set. If so, could you provide a link for me to download it?
Thanks.

Thank you for your question. We do not provide ImageNet training set since it is too big. You might need to download from their official website or mirror.


X-fapi-financial-id header should be optional starting with v3.1.2

The x-fapi-financial-id header has to be removed from all APIs and Controllers in RS as it is no longer required starting with v3.1.2 according to https://openbankinguk.github.io/knowledge-base-pub/standards/read-write.html#what-error-code-should-an-aspsp-send-back-to-a-tpp-if-a-wrong-x-fapi-financial-id-was-sent-in-the-request.

Remove all use of this header across all versions. Later we will remove access to any versions prior to 3.1.4 where signing headers changed. b64 etc...


Issue with /docs/concepts/configuration/assign-pod-node/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
In the document, it mentiond:
In principle, the topologyKey can be any legal label value. However, for performance reasons, only a limited set of topology keys are allowed. By default the allowed topology keys are:
kubernetes.io/hostname
failure-domain.beta.kubernetes.io/zone
failure-domain.beta.kubernetes.io/region
but we can still create a pod with unsupported topologyKey like this
apiVersion: v1
kind: Pod
metadata:
  name: pod-affinity
spec:
  affinity:
    podAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
      - labelSelector:
          matchExpressions:
          - key: security
            operator: In
            values:
            - S1
        topologyKey: poor-topo
  containers:
  - name: with-pod-affinity
    image: gcr.io/google_containers/pause:2.0

Proposed Solution:
change allowed into recommended ?
Page to Update:
http://kubernetes.io/...

Please feel free to send a PR if you have time.


Questions for what colums to consider tracking zkVM

Currently we have 5 columns that we tracking - but we'd like to extend and represent in more sophisticated manner

privacy support : does zkvm allows to write program contain private value and/or computation

proving backend: how specifically do we wanna show backend side (  does it just layout as prover library? how specifically mention proving scheme? )

ISA specific: actually not all "RISC-V" is just same. Some are slightly make their own variance, and to be specific there can be riscv32/64 variance etc. How much do we wanna show all and how detail should we track on

Assembly: For now I put it as "Proving Frontend" as technically people can write with assembly directly but e.g PIL is different from Rust. Do we need to divide this lower/higher level language for tracking?

specify what precompiles that zkVM are supporting e.g RSA/keccak/ECDSA/Pairings and BLS12-38

continuation vs recursion need to split

Having a formal verification column would be cool! This still left-out the question of what is verified, how (a model or the code or the code itself), and for which properties. Maybe there are ways to link a cell to a footnote or something to justify the formal verification level with links to relevant materials.

One possible addition: EVM support; that is, is there a repository (e.g., zeth, sp1-reth) or public benchmarks (ethproofs, ...) that demonstrate you can run an EVM on that zkVM.


Timetable is fetched every time the browser window gets focus

this image is after alt-tabbing a few times

https://tanstack.com/query/v4/docs/framework/react/guides/window-focus-refetching


chore(main): release homestar 2.2.0

:robot: I have created a release beep boop
2.2.0 (2024-03-08)
Features

Wasmify supports custom wit folder, world name, debug mode and wasm cache (1dafc13), closes #168

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fission-codes/stack/releases/tag/homestar-v2.2.0 :sunflower:


ZWAVE?

Hey
Do you think this will also work with the ZWAVE Version of the Spirit?
Thanks
R

Hey Ralph,
as far as I know the implementation of the firmware between the zigbee and zwave models is quit different. So I can't answer it easily.
If the heating setpoint is changed in the same attribute and if the same HVAC models are supported it could work also with the zwave implementation. You could give it a try with one of your zwave models and report back. The thermostat implementation itself is based on the generic_thermostat from HA and is mostly independent from the used protocols and subsystems (like ZHA, deconz or Zwave).


Release 1.9

@rultor release, tag=1.9

@rultor release, tag=1.9

@uklimaschewski OK, I will release it now. Please check the progress here

@rultor release, tag=1.9

@uklimaschewski Done! FYI, the full log is here (took me 3min)


waitForSelector fails with timeout error when puppeteer reconnects to a browser.

Steps to reproduce
Tell us about your environment:

Puppeteer version: 5.3.1
Platform / OS version: Mac OS X 10.15.6
URLs (if applicable): -
Node.js version: 14.7.0

What steps will reproduce the problem?
Please include code that reproduces the issue.

Launch browser (or connect to already running one).
Open a new page, navigate to any url (or use already opened one if exists)
Disconnect browser.
Connect to the same browser and find the same page (from step 2).
Reload/navigate this page.
Await waitForSelector.
Bug. TimeoutError: waiting for selector "div.test-reconnect" failed: timeout 5000ms exceeded

Example below:
const {createServer} = require('http');
const puppeteer = require('puppeteer');

const httpPort = 8909;
const waitOptions = {timeout: 5 * 1000};
const testUrl = `http://localhost:${httpPort}/`;

const testServer = createServer(({}, response) => {
  response.write('
Test Reconnect
');
  response.end();
});

(async () => {
  await new Promise((resolve, reject) => {
    testServer.on('listening', resolve);
    testServer.on('error', reject);
    testServer.listen(httpPort);
  });

  let browserWSEndpoint;

  {
    const browser = await puppeteer.launch({
      headless: false
    });
    browserWSEndpoint = browser.wsEndpoint();

    const page = await browser.newPage();
    await page.goto(testUrl);

    await page.reload();

    const element = await page.waitForSelector('div.test-reconnect', waitOptions);
    await element.dispose();

    // Reloading/navigating page before reconnection fixes the issue becuase the old
    // utility world gets destroyed on page reload.
    // So when puppeteer connects again it creates a new one and `waitForSelector` works fine.

    // await page.evaluate(() => setTimeout(() => location.reload(), 1000)); // <-- uncomment to make it work

    browser.disconnect();

    await new Promise((resolve) => setTimeout(resolve, 2000));
  }

  {
    console.log('reconnect');
    const browser = await puppeteer.connect({
      browserWSEndpoint
    });

    const page = (await browser.pages())
      .find((page) => page.url() === testUrl);

    // If page is not reloaded/navigated the old utility world is not yet destroyed
    // and `waitForSelector` works.
    await page.reload(); // <-- comment to make it work

    console.log('after reload');
    const element = await page.waitForSelector('div.test-reconnect', waitOptions);
    await element.dispose();

    await new Promise((resolve) => setTimeout(resolve, 1000));

    await browser.close();
  }
})()
.catch(console.error)
.finally(() => {
  testServer.close();
  process.exit();
});

What is the expected result?
waitForSelector works for a reconnected browser.
What happens instead?
waitForSelector fails with timeout error.

So what's happening here is that isolated utility world is being destroyed after browser is disconnected, but only when page is reloaded/navigated after that.
A new utility world is not created if there's already existing one:
https://github.com/puppeteer/puppeteer/blob/c756fb495be31041a6017f2afa1dcfa9af440c3c/src/common/FrameManager.ts#L320
So the old one is being used.
But after page is reloaded it gets destroyed and a new one is not created either.
As a result the context for the secondary world is never set.


New option like --preview but with no variables expand

Is your feature request related to a problem? Please describe.
The actual result of the --preview option is not compatible with the GitLab internal ci/lint API route
which validates if a CI config is valid or not. As it's not the purpose of this option, I propose to add a new option doing the same job (merging the chole CI configuration) but without variable expansion. Something like the result of the "Full configuration" tool of GitLab's internal CI editor: https://docs.gitlab.com/ee/ci/pipeline_editor/#view-full-configuration.
Final purpose
The final goal is to be able to validate a complete local development of CI, with all the concerned includes, sending
the result as the ci/lint API route content parameter to be able to validate a full CI local development:
jq --null-input --arg yaml "$(gitlab-ci-local --<OPTION>)" '.content=$yaml' \
| curl "https://scm.clubmed.com/api/v4/projects/${GITLAB_PROJECT_ID}/ci/lint?include_merged_yaml=true" \
  --header "Authorization: Bearer ${GITLAB_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data @- \
| jq '.valid'
# should always be 'true'

This could be a great feature for CI automation, like a pre-commit hook for instance.
Minimal .gitlab-ci.yml illustrating the need
I haven't tested all the combinations of all keywords but I've identify at least the following case which is failing:
# .gitlab-ci.yml
---

.anchored_vars: &anchored_vars
  MY_VAR: 'my var'

my_job:
  rules:
    - if: $CI_COMMIT_REF_NAME
      variables:
        <<: *anchored_vars
  script:
    - echo "$MY_VAR"
  environment:
    name: $MY_VAR

Below is the result of the --preview option:
$ gitlab-ci-local --preview

---
stages:
  - .pre
  - build
  - test
  - deploy
  - .post
my_job:
  rules:
    - if: $CI_COMMIT_REF_NAME
      variables:
        MY_VAR: my var
  script:
    - echo "$MY_VAR"
  environment:
    name: ''

Passing this to the API will fail:
$ jq --null-input --arg yaml "$(gitlab-ci-local --preview)" '.content=$yaml' \
  | curl "https://scm.clubmed.com/api/v4/projects/${GITLAB_PROJECT_ID}/ci/lint?include_merged_yaml=true" \
    --header "Authorization: Bearer ${GITLAB_TOKEN}" \
    --header 'Content-Type: application/json' \
    --data @- \
  | jq

{
  "valid": false,
  "errors": [
    "jobs:my_job:environment name can't be blank",
    "jobs:my_job:environment name can contain only letters, digits, '-', '_', '/', '$', '{', '}', '.', and spaces, but it cannot start or end with '/'"
  ],
  "warnings": [],
  "merged_yaml": "---\nstages:\n- \".pre\"\n- build\n- test\n- deploy\n- \".post\"\nmy_job:\n  rules:\n  - if: \"$CI_COMMIT_REF_NAME\"\n    variables:\n      MY_VAR: my var\n  script:\n  - echo \"$MY_VAR\"\n  environment:\n    name: ''\n",
  "includes": []
}

Expected behavior
In that particular case, the enviroment name and url should not be replaced by the variable value (which is empty as it can not be guessed outside of a tag).
In deed, if we change the payload like the following:
# .gitlab-ci-validated.yml

---
stages:
  - .pre
  - build
  - test
  - deploy
  - .post
my_job:
  rules:
    - if: $CI_COMMIT_REF_NAME
      variables:
        MY_VAR: my var
  script:
    - echo "$MY_VAR"
  environment:
    name: '$MY_VAR'

We have a validated result:
$ jq --null-input --arg gitlabci "$(<.gitlab-ci-validated.yml)" '.content=$gitlabci' \
  | curl "https://scm.clubmed.com/api/v4/projects/${GITLAB_PROJECT_ID}/ci/lint?include_merged_yaml=true" \
    --header "Authorization: Bearer ${GITLAB_TOKEN}" \
    --header 'Content-Type: application/json' \
    --data @- \
  | jq

{
  "valid": true,
  "errors": [],
  "warnings": [],
  "merged_yaml": "---\nstages:\n- \".pre\"\n- build\n- test\n- deploy\n- \".post\"\nmy_job:\n  rules:\n  - if: \"$CI_COMMIT_REF_NAME\"\n    variables:\n      MY_VAR: my var\n  script:\n  - echo \"$MY_VAR\"\n  environment:\n    name: \"$MY_VAR\"\n",
  "includes": []
}

Host information

tested with gitlab-ci-local 4.46.1

This is quite an undertaking, and wasn't the initial purpose of --preview

It was my point thinking about my request. The original purpose of the --preview was not to validate the rendering but mostly to visualize the whole CI right ?
So the idea of a new option maybe better no ?
I can create a Discussion about that if you want...

@e-picas The purpose was to extrapolate extends and !reference, not variables.
Go for it, no need to make a Discussion


[BUG] plugins.security.ssl.transport.enforce_hostname_verification marked as deprecated without documentation

What is the bug?
Starting the OpenSearch (2.17.1) prints following message:

"[plugins.security.ssl.transport.enforce_hostname_verification] setting was deprecated in OpenSearch and will be removed in a future release! See the breaking changes documentation for the next major version."

I found questions about this issue on forum and it seems it was not resolved (both of them are 2.14.0):
https://forum.opensearch.org/t/query-regarding-warning-message-in-os-version-2-14/20194
https://forum.opensearch.org/t/deprecation-of-some-security-configuration-settings/20324
This change is not mentioned neither in configuring security documentation nor in breaking changes
How can one reproduce the bug?
Start OpenSearch
What is the expected behavior?
Replacement for this setting is documented and described or deprecated message is removed.
What is your host/environment?

Version: 2.17.1

[Triage] Thank you for filing this issue @patrykmatys. Since this setting was marked as deprecated it can be removed on the main branch to prevent this from being logged in 3.0.0.

@patrykmatys From https://github.com/opensearch-project/security/pull/4119/files I believe that
# deprecated
plugins.security.ssl.transport.enforce_hostname_verification: false
plugins.security.ssl.transport.resolve_hostname: false

Now it's:
# new
transport.ssl.enforce_hostname_verification: false
transport.ssl.resolve_hostname: false

But indeed it would be nice to add it either as a clearer log message or in the docs because these settings are not updated yet: https://opensearch.org/docs/latest/install-and-configure/configuring-opensearch/network-settings/ and there is no single mention in https://opensearch.org/docs/latest/security/configuration/tls/#advanced-hostname-verification-and-dns-lookup that the settings are deprecated :(


Scope issue in Standalone Patient App - Full Access

Why below highlighted scopes are NOT automatically getting requested in the suite? There are tests related to these resources but are not getting requested during Standalone Patient App - Full Access test.
patient/ServiceRequest.rs patient/Coverage.rs patient/MedicationDispense.rs patient/RelatedPerson.rs

Hello @VighneshAlevoorP
When you don't use any Preset from the left side, the configuration is set to default for all US Core versions.
A solution is that you can save your server's setting as a JSON file and reuse by upload or copy/paste. To save your own settings, click the "JSON" or "YAML" tab at the bottom

Then click either "Download File" or the "Copy/Paste" button.
The next time you run test against your server, you can click "Upload File" button to update values.


javascript as the repository language

While creating a new repository, gogs asks for the language to setup the gitignore file. However, javascript is not among them.

Also missing HTML, CSS, JS, jQuery, MySQL, Perl, Bash, etc

Objective-C++ anyone?

https://github.com/github/gitignore
This is basically what you want.

I just use http://gitignore.io/

@zoozalp : if you create a folder at the path gogs\custom\conf\gitignore, you can drop gitignore files within it (simply name them the language.  IE for Java, the file would simply be named Java.
Restart the gogs binary and you'll find them in the dropdown list.

Added a big list to Gogs on master branch. :tada:


Prefix is missing for abstract ThisType in denotation.signature

The following tests is failing with Classifier != Foo.this.Classifier
  targeted(
    """
      |package ah
      |
      |trait EventBus {
      |  type Classifier
      |}
      |trait Foo { this: EventBus =>
      |  val <<x>>: Classifier
      |}
      |""".stripMargin, { (db, x) =>
      val sig = db.symbols.find(_.symbol == x).get.denotation.signature
      assertNoDiff(sig, "Foo.this.Classifier")
    }
  )

This bug is the root cause of existing ExplicitResultTypes bugs in scalafix https://github.com/scalacenter/scalafix/issues/324

@olafurpg Is this still relevant now that we're moving full steam ahead towards https://github.com/scalameta/scalameta/issues/1221?

This was already fixed in a PR actually


[BUG]: Scrutinizer Fixes

Scrutinizer reports several issues that need addressing.
https://scrutinizer-ci.com/g/niden/phalcon/inspections/9f633ca6-e6d9-4669-9854-99165df3a917/issues/?status=all

Resolved in https://github.com/phalcon/phalcon/pull/267


Bugfix: Return Frightful Aspect's Polymorph tag

not sure if this was changed in an owlcat patch or caused when you tried to fix master shapeshifter but the spell lost it's polymorph tag(which it should have according to TT)
seems to be messing with stacking rules too due to the missing descriptor

Frightful Aspect has the polymorph descriptor and master shapeshifter does apply to it. Admittedly the spell's tooltip does not show any descriptors, but that's certainly not my fault.

weird i could swear in-game it used to have the descriptor in the tooltip in the past(i.e pre last patch) which allowed it to 'stack' with specific things(like legendary proportions), weird if owlcat themselves removed it
like my Cam has both effects on at the same time cause she had it pre patch but anyone else trying to do the same now has FA overwrite LP completely(i.e no FA for the aura while benefiting from LP's size bonuses to ability scores and AC instead)


fix(Optional): use std::optional

BREAKING CHANGE: absl::optional has been replaced by std::optional

:tada: This PR is included in version 7.0.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Can not install yaml~0.2.5. Too many errors in conv.py.

The program said that it couldn't install yaml~0.2.5 when I tried to pip install -r requirements.txt.
Besides, when I ran main_video.py, it said that some errors happened in conv.py

You can try different version of yaml. It usually error when you set up the
latesst vers
On Mon, Dec 19, 2022, 16:06 Zero @.***> wrote:

The program said that it couldn't install yaml~0.2.5 when I tried to pip
install -r requirements.txt.
Besides, when I ran main_video.py, it said that some errors happened in
conv.py
—
Reply to this email directly, view it on GitHub
https://github.com/mrzaizai2k/License-Plate-Recognition-YOLOv7-and-CNN/issues/2,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJYP3L4SWE3U2TUIZPXR4GLWOAQP3ANCNFSM6AAAAAATDDWTF4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


Remove forgotten comma in BusServiceProvider

I've notice the error when I visit _ignition/health-check page.

Laravel 8 requires PHP 7.3 as its minimum version, and PHP 7.3 or higher allows a trailing comma in a function call.
There are multiple closed PRs trying to "fix" this, but this is not a bug if you are using a supported PHP version.

use php >= 7.3

Upgrading to composer 2.0 will warn you of this kind of error too.

We need to reopen this issue again,
I'm using docker php:7.4.11-apache-buster
Both cli and fpm versions are 7.4.11
My CLI
www-data@616eceb11dc8:/var/www/html$ php -v
PHP 7.4.11 (cli) (built: Oct 13 2020 10:01:40) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies

My FPM

I know PHP 7.4 is more tolerant
www-data@616eceb11dc8:/var/www/html$ php -l vendor/laravel/framework/src/Illuminate/Bus/BusServiceProvider.php
No syntax errors detected in vendor/laravel/framework/src/Illuminate/Bus/BusServiceProvider.php

Ran a composer du
When I let php artisan queue:work running it throws this after a while
[2020-10-23 11:24:29] local.ERROR: syntax error, unexpected ')' {"exception":"[object] (ParseError(code: 0): syntax error, unexpected ')' at vendor/laravel/framework/src/Illuminate/Bus/BusServiceProvider.php:51)

What's the deal with the leading comma anyways? Why can't we just remove it?

@thureos you're definitely not using PHP 7.4 if you stumble over this.

What's the deal with the leading comma anyways? Why can't we just remove it?

It's a PHP 7.3 language feature.

didn't you readme?

@thureos you're definitely not using PHP 7.4 if you stumble over this.

What's the deal with the leading comma anyways? Why can't we just remove it?

It's a PHP 7.3 language feature.

didn't you readme ?

I'm using docker and php 7.4.9. All is OK

Replicate this: Create a dummy job and schedule:run then run queue:work for about 2 minutes.
if this works for you then I'm crazy and I need to downgrade from 7.4.11 to 7.4.9

I told you guys even a syntax check (php -l) on the file runs fine, but given the conditions I mentioned before the error shows up, please read my detailed explanation.

try use in Docker
php:7.4.11-fpm

Works fine:

Thanks @driesvints , WIll try what @vladislavtkachenko  suggested. Last thing, could you leave it running for a little while while tailing the log?
Thanks again,

This is running 7.4.11 FPM

magic :)

@thureos I'm sorry but I think it's best that you try a support channel now:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

magic :)

It didn't work @vladislavtkachenko , I just showed that php by itself doesn't complaing about the file syntax.
@driesvints I'm going to downgrade a little bit more but, is it cool to have that leading comma just "because PHP now supports it"?
Thanks anyway guys, Happy 2020!

For the record: PHP 7.4.9 Doesn't help either.

Decided to just resend the PR: https://github.com/laravel/framework/pull/34945

Thanks @driesvints!


DeveloperError in new Picking example

@bagnell can you look at this for 1.10?
From this horizon view:

Grabbing the model to zoom towards it moves the camera too quickly like it picked through the model.  Did this break recently?
Grabbing the model (or sky) can result in a DeveloperError:

This is with the left mouse button, not the right, which is probably what I was testing before.  Models should work just like grabbing the globe.

When you look up at the model like that and move towards it, the camera would go under the terrain. The collision detection prevents that so it appears to move faster.
The developer error occurs because for one frame the depth read back for each frustum is 0. I'm not sure why that happens, but I can add a check for undefined.

#2769 fixes this:

Grabbing the model (or sky) can result in a DeveloperError:

Leaving this issue open for:

Grabbing the model to zoom towards it moves the camera too quickly like it picked through the model. Did this break recently?

which is a priority post 1.10

Could not reproduce this


Rename tag 1.0 to v1.0 in order to use gopkg.in

As the title says, it would be nice to let users use stable release with go get and the easiest way is to use gopkg.in.
With the current tag name 1.0 the service is unable to access 1.0 release.
GitHub repository at https://github.com/gernest/utron has no branch or tag "v1", "v1.N" or "v1.N.M"

@Slacki thanks, doing that right now

@Slacki can you try again? I just fchanged it to v1.0

It works now. I am gonna make a PR later with changes to README and wiki to let users know about this.

thanks, I am closing this issue for now.


Enable sage backend by default only if SAGE_ROOT is set

It's possible to install the Sage system as a normal Python package, as
e.g. in Fedora/Debian. In this case, presence of sage.all is not an
indicator whether the user is running Sage, and checking for 'SAGE_ROOT'
is more reliable.
There are some behavior differences in mpmath with the Sage backend,
(e.g. mpmath.ker(0, 0) is 0 on sage but inf on gmpy), but a larger reason
for this change could be that the Sage backend probably makes sense mostly
when using Sage.

Seems OK.
The mpmath.ker(0, 0) discrepancy would be worth looking into, because results are meant to be identical.

That was fairly silly as reasoning. System sage like sage-on-gentoo use system mpmath in their system sage. This change breaks the use of mpmath in a system install of sage. I'll admit that automated back end choice is a bit of an issue. But this change leads to this kind of stuff in sage-on-gentoo
fbissey@moonloop ~ $ sage -t --long --random-seed=0 /usr/lib/python3.9/site-packages/sage/calculus/calculus.py
too many failed tests, not using stored timings
Running doctests with ID 2021-03-18-13-14-48-fb25a05d.
Using --optional=dochtml,memlimit,pip,sage
Doctesting 1 file.
sage -t --long --random-seed=0 /usr/lib/python3.9/site-packages/sage/calculus/calculus.py
**********************************************************************
File "/usr/lib/python3.9/site-packages/sage/calculus/calculus.py", line 372, in sage.calculus.calculus
Failed example:
    [f[0].n() for f in _.coefficients()]  # numerical coefficients to make comparison easier; Maple 12 gives same answer
Exception raised:
    Traceback (most recent call last):
      File "sage/symbolic/expression.pyx", line 6186, in sage.symbolic.expression.Expression.numerical_approx (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/symbolic/expression.cpp:37043)
        x = x._convert(kwds)
      File "sage/symbolic/expression.pyx", line 1495, in sage.symbolic.expression.Expression._convert (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/symbolic/expression.cpp:10451)
        cdef GEx res = self._gobj.evalf(0, kwds)
      File "sage/libs/pynac/pynac.pyx", line 2139, in sage.libs.pynac.pynac.py_psi2 (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/libs/pynac/pynac.cpp:25306)
        return mpmath_utils.call(mpmath.psi, n, x, prec=prec)
      File "sage/libs/mpmath/utils.pyx", line 439, in sage.libs.mpmath.utils.call (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/libs/mpmath/utils.c:7129)
        y = mpmath_to_sage(y, prec)
      File "sage/libs/mpmath/utils.pyx", line 272, in sage.libs.mpmath.utils.mpmath_to_sage (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/libs/mpmath/utils.c:5518)
        mpfr_from_mpfval(y.value, x._mpf_)
      File "sage/libs/mpmath/utils.pyx", line 167, in sage.libs.mpmath.utils.mpfr_from_mpfval (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/libs/mpmath/utils.c:4702)
        sign, man, exp, bc = x
    TypeError: Cannot convert mpz to sage.rings.integer.Integer

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/usr/lib/python3.9/site-packages/sage/doctest/forker.py", line 714, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/lib/python3.9/site-packages/sage/doctest/forker.py", line 1133, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.calculus.calculus[101]>", line 1, in <module>
        [f[Integer(0)].n() for f in _.coefficients()]  # numerical coefficients to make comparison easier; Maple 12 gives same answer
      File "<doctest sage.calculus.calculus[101]>", line 1, in <listcomp>
        [f[Integer(0)].n() for f in _.coefficients()]  # numerical coefficients to make comparison easier; Maple 12 gives same answer
      File "sage/structure/element.pyx", line 885, in sage.structure.element.Element.n (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/structure/element.c:8385)
        return self.numerical_approx(prec, digits, algorithm)
      File "sage/symbolic/expression.pyx", line 6190, in sage.symbolic.expression.Expression.numerical_approx (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/symbolic/expression.cpp:37116)
        x = x._convert(kwds)
      File "sage/symbolic/expression.pyx", line 1495, in sage.symbolic.expression.Expression._convert (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/symbolic/expression.cpp:10451)
        cdef GEx res = self._gobj.evalf(0, kwds)
      File "sage/libs/pynac/pynac.pyx", line 2139, in sage.libs.pynac.pynac.py_psi2 (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/libs/pynac/pynac.cpp:25306)
        return mpmath_utils.call(mpmath.psi, n, x, prec=prec)
      File "sage/libs/mpmath/utils.pyx", line 439, in sage.libs.mpmath.utils.call (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/libs/mpmath/utils.c:7129)
        y = mpmath_to_sage(y, prec)
      File "sage/libs/mpmath/utils.pyx", line 272, in sage.libs.mpmath.utils.mpmath_to_sage (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/libs/mpmath/utils.c:5518)
        mpfr_from_mpfval(y.value, x._mpf_)
      File "sage/libs/mpmath/utils.pyx", line 167, in sage.libs.mpmath.utils.mpfr_from_mpfval (/dev/shm/portage/sci-mathematics/sage-9999/work/sage-9999/src-python3_9/build/cythonized/sage/libs/mpmath/utils.c:4702)
        sign, man, exp, bc = x
    TypeError: Cannot convert mpz to sage.rings.integer.Integer
**********************************************************************
1 item had failures:
   1 of 113 in sage.calculus.calculus
    [429 tests, 1 failure, 9.93 s]
----------------------------------------------------------------------
sage -t --long --random-seed=0 /usr/lib/python3.9/site-packages/sage/calculus/calculus.py  # 1 doctest failed
----------------------------------------------------------------------
Total time for all tests: 10.0 seconds
    cpu time: 10.6 seconds
    cumulative wall time: 9.9 seconds
fbissey@moonloop ~ $ SAGE_ROOT=1 sage -t --long --random-seed=0 /usr/lib/python3.9/site-packages/sage/calculus/calculus.py
too many failed tests, not using stored timings
Running doctests with ID 2021-03-18-13-18-15-7c4bcb36.
Using --optional=dochtml,memlimit,pip,sage
Doctesting 1 file.
sage -t --long --random-seed=0 /usr/lib/python3.9/site-packages/sage/calculus/calculus.py
    [429 tests, 9.94 s]
----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
Total time for all tests: 10.0 seconds
    cpu time: 10.7 seconds
    cumulative wall time: 9.9 seconds

Is there a related upstream issue as reference?

If by upstream you mean sagemath, then no. We have just stumbled across this in sage-on-gentoo yesterday https://github.com/cschwan/sage-on-gentoo/issues/628. I think this change assumed that a system sage like the one shipped with fedora or debian is bringing a private copy of mpmath. This is not the case for Gentoo and I assume arch.

It looks like I can get away with it by setting MPMATH_SAGE=1 rather then SAGE_ROOT. May be we should have some change in sage upstream to make sure MPMATH_SAGE is set when calling mpmath. While I want to make sure you are aware that the SAGE_ROOT assumption was simplistic, something probably needs to be done inside sage as well.

I agree with this change in principle. Sage itself should be responsible for "enabling" sage mode when it imports mpmath (only I don't know if an environment variable is the right way to go about that, which is why I say "in principle"). It is also possible to install Sage using conda-forge, and the exact same problem exists there. If you install Sage into a conda environment, a ton of SymPy tests start failing, because they do not work properly when mpmath uses the Sage backend (I haven't investigated these tests so I can't say if they are legitimate bugs or just small numerical differences). Here is the upstream issue https://trac.sagemath.org/ticket/25445 (see also https://github.com/sympy/sympy/pull/14703).
Ideally, mpmath could use both backends at the same time, by switching out a context at runtime, so that Sage can use its Sage backend and SymPy can use the normal backend(s) in the same process. I don't know if this use case is important enough to add this complexity to mpmath, however.
You could argue this is sort of a Sage issue. There are a lot of bad things that can happen if you import Sage in a normal Python environment (e.g., IIRC unless this has changed, it also hooks the interpreter in some ways that makes exceptions print differently). Installing Sage into the same Python environment you plan to use for non-Sage things is a bad idea. If gentoo is doing that, it should reconsider. But the fact that mpmath just imports sage when it can find it exacerbates this problem. That means that, prior to this fix, simply doing conda install sage will break SymPy in that environment.

I acknowledge that the situation sympy/mpmath/sage has been ongoing for some time. sage in sage-on-gentoo has been a normal python package that you can import from python since about sage-5.0. Recent sympy have not exhibited problems in sage-on-gentoo but for a while I had some environment variable specifically set for it.
In effect this is the first time in a couple of years since I had an issue of this kind. But the fact that once sage is installed you have to explicitly tell mpmath not to use it is something I understand you find less than ideal. I am currently trying a simple fix in upstream sage but I don't know if it will catch enough things.

I don't know if this still the case, but Sage used to have pretty stringent pinning of some dependencies, which was another reason to prefer using a separate environment for conda. @isuruf would need to comment on whether that is still the case. Also as I mentioned, I noticed back in 2018 that Sage was hooking the interpreter in some ways when it was imported. I don't know if this is still relevant. I don't follow Sage development at all, though, so it is very possible that these are no longer significant issues. It definitely was the case then that Sage was not at all designed to be installed as a library alongside a normal Python environment. That's obviously an even bigger issue when something like mpmath eagerly imports sage if it sees that it is installed. Importing Sage also is slow. import mpmath takes over a second with MPMATH_SAGE=1 and about 0.1 seconds without.

Still does need some stringent pinning of some dependencies (singular, pari...). This is unfortunate but also the result of the fact that most of those packages have APIs that are not very stable. Separate environment and other containment strategies are obviously a good way to have a handle on those issues from the user perspective, not so much from the regular packager perspective.

For conda environments are trivial, so it isn't a big deal. The main issue really is messaging to users that Sage is very much a package that you want to have in a separate environment, rather than your "main" environment. I understand that no all package managers have straightforward environments like conda does, including most Linux system package managers, so it's a harder problem there.

Nod in agreement. The ticket you opened years ago is getting renewed interest https://trac.sagemath.org/ticket/25445. I think the fact sage is not working properly if you are not using the sage backend is a sage bug. It shouldn't matter, beside possible numerical noise, and the fact it does means the internal of mpmath are abused.


remove the explode parameter

LGTM - it's just a stylistic change in the chart, so that a slice isn't "exploded" out from the center.


Implement error message wraping/encryption and decryption

Issue
Within the network, it's important that when an HTLC forwarding failure occurs, the recipient is notified in a timely manner in order to ensure that errors are graceful and not unknown. However, we also want to ensure the privacy of the onion routing scheme, meaning that the intermediate hops don't know the exact location of the initiating sender. Therefore, nodes need to use the existing circuit to report the error with a message traveling backwards from the point of error to the original sender.
Within the current spec draft the handling of the scenario described above is detailed in sufficiently in the returning messages section.
This error wrapping and decryption at the sender is currently unimplemented.
Steps to Completion

[x] The ProcessPacket method should also return an object which encapsulates the derived shared secret, and provides a method/function to create a wrapped error messages.

[x] Similarly, the NewOnionPacket function should return a similar object which encapsulates the derived shared secret, and the encoded route. The object should provide a method/function to perform trial decryption (O(N^2) work, since we don't know which node in the route send the message).

Will take this one.

Closed by #8.


[Bug]: connectivity_plus doesn't have support for iOS in latest version. Had to revert to the previous one

Platform
iOS
Plugin
connectivity_plus
Version
5.0.0
Flutter SDK
3.13.7
Steps to reproduce
run flutter build ios
Code Sample
No response
Logs
N/A

Flutter Doctor
Not relevant

Checklist before submitting a bug

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

After upgrading to the latest version of the plugin (5.0.0) I cannot build for iOS any longer. After reverting back to the older version, all is good

Current bug report is invalid without logs and information what exactly is wrong. Provide information properly.

The app just doesn't build for iOS with the latest (5.0.0) version, that is the only thing. There is no other information that I can provide.
After reverting to the previous version (4.0.2) of the plugin, the app builds for iOS as expected.

If you can't provide even logs from build fails there is no way to help you.
Thus, I am closing the bug report as invalid.


Modify: IObit.AdvancedSystemCare version <IP_ADDRESS>3

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?
Resolves #167160

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @KarbitsCode,
This manifest adds Apps and Features entries that aren't present in previous PR versions. These entries should be added to the previous versions, or removed from this version.
(Automated response - build 887.)


Wrong Sidekiq serialization for object/nested types

Hello!
When I'm trying to index #my_cities through sidekiq, those are being identified by Chewy as objects and the adapter chosen is Chewy::Type::Adapter::Object.
Sidekiq serialization will inevitably fail because the adapter returns objects instead of the expected array of ids.
Is there any way to force Chewy to use a specific adapter (Chewy::Type::Adapter::ActiveRecord) on object/nested types? maybe on definition?
Thank you!
ENV:
Rails 5.2.1
chewy 5.0.0
ruby 2.4.4p296 (2018-03-28 revision 63013)

Models:
class Country
  update_index('countries#country') { self }
  has_many :cities

  def my_cities
     #some method that returns an AR collection of cities
  end
  ...

class City
  belongs_to :country
  ...

Type definition:
define_type Country.includes(:cities) do
  field :id
  field :name
  field :my_cities do
    field :id
    field :name
  end
end

Chewy request strategy:
Chewy.request_strategy = :sidekiq

I don't think there is a way to do it. Try to propose a patch maybe?

This turned out to be a non issue by the way.


Add ability to refresh/rerender a document manually

Add an action that allows for the user to explicitly request a re-rendering of a certain document/page from the CMS.
For example, in the document list overview we could have a actions menu on each list item like this

This would require implementation of a callable cloud function or implementation of task service in CMS to create entries into the task queue.

Create a task service that writes to the RTDB as follows

firebase.database()
  .ref('tanam')
  .child(siteId)
  .child('/tasks/cache/update')
  .push('/blog/foobar-testing-with-the-change');


Skip scaling if image is smaller than requested

If original image has width/height smaller than requested and no upscaling then skip resizing.

sorry it took me so long to get this merged.  But thanks for the contribution, this looks great!


Broken link

Link to MSDN blog is broken:
For more information, see "Performance pattern 1: Identifying lock contention" in Hazim Shafi's Parallel performance tools for Windows blog on the MSDN blog Web site.
URL returns page not found
https://blogs.msdn.microsoft.com/hshafi

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

ID: 84100a50-c4c1-7369-12e1-3489487d6f58
Version Independent ID: d5ab85d8-7456-78df-8aec-5dac0ad1a710
Content: Common Patterns for Poorly-Behaved Multithreaded Applications - Visual Studio
Content Source: docs/profiling/common-patterns-for-poorly-behaved-multithreaded-applications.md
Product: visual-studio-windows
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@gmanvel Thanks, I'll take a look at that.

@gmanvel Looks like the blog post was decomissioned. Similar content referencing Hazim Shafi's post is available here:
https://msdn.microsoft.com/en-us/magazine/ff714587.aspx
I can update the link


Updated styles for contact form and made it attractive and modern

Updated styles for contact form, including border radius, box shadow and colors, added labels to form fields, and modified navbar and section title styles.

Thank you @abhishekraoas


Error account have sr25519 key, it must have ed25519 key

When deploying caprover through terraform, I get the error
mycaprover$ terraform apply -parallelism=1
╷
│ Error: the account associated with the given mnemonics have sr25519 key, it must have ed25519 key
│
│   with provider["registry.terraform.io/threefoldtech/grid"],
│   on caprover.tf line 9, in provider "grid":
│    9: provider "grid" {
│
╵

I know conversion was ongoing to sr keys, issue to be kept informed about when correction is available

Judging from the error message, you are using 0.1.13 or an older version. In 0.1.14, you can specify key_type to be ed25519 or sr25519. The sr25519 as of now won't work on testnet as it's not yet updated with this zos update.


[v1.3]Pin a person

added
pin person
unpin person
listpin
changed
Ui of bluebird

Coverage decreased (-1.8%) to 88.087% when pulling 954edfae78dfed7015612d8dc1def0ce096977f2 on ALim95:v1.3_PinPerson into d85490d39ad70e547c9c96db4b0bc0c45377459f on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.002%) to 89.902% when pulling fbf38376ff46b958786f75f2cd9dcae8ad3c3e44 on ALim95:v1.3_PinPerson into d85490d39ad70e547c9c96db4b0bc0c45377459f on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.1%) to 90.005% when pulling 1beca7a2e089c67cbba42e7a3291b5d3816bcc59 on ALim95:v1.3_PinPerson into d85490d39ad70e547c9c96db4b0bc0c45377459f on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.1%) to 90.005% when pulling 83ad108ca9c0775ef8005eaf23df13de60939a49 on ALim95:v1.3_PinPerson into d85490d39ad70e547c9c96db4b0bc0c45377459f on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.1%) to 90.005% when pulling 83ad108ca9c0775ef8005eaf23df13de60939a49 on ALim95:v1.3_PinPerson into d85490d39ad70e547c9c96db4b0bc0c45377459f on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.1%) to 90.005% when pulling c814a025150dc194eb7be48940c5d7a59eb8a90a on ALim95:v1.3_PinPerson into d85490d39ad70e547c9c96db4b0bc0c45377459f on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.1%) to 90.005% when pulling e28704defdb0b900b06d2b5ebb6cb2c69ef31cf7 on ALim95:v1.3_PinPerson into d85490d39ad70e547c9c96db4b0bc0c45377459f on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.09%) to 90.005% when pulling 040c71168161c29ec86bc69a4092f4efc1ccea14 on ALim95:v1.3_PinPerson into d1fc69b1cdb443e950f2d5915c6de3fe1188f0b6 on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.09%) to 90.005% when pulling 5bcd23f00afd53588fa92188b7f3036305b5756f on ALim95:v1.3_PinPerson into d1fc69b1cdb443e950f2d5915c6de3fe1188f0b6 on CS2103AUG2017-T15-B4:master.

Coverage increased (+0.2%) to 88.338% when pulling 6d74f45f2f1f8e4361ee8f5def883cb025c45f95 on ALim95:v1.3_PinPerson into a72bfb0df5f3795f311a2fc42390c0f71fbc868e on CS2103AUG2017-T15-B4:master.


[BUG]: Parameter "--fs" does work properly

Describe the bug
The behavior of parameter --fs does work as described in Evaluation README. The README states that it is optional, but if I do not fill in it, it gives out error. Also, no matter I fill in it will int type value (aka 24000) or string type value (aka '24000'), it gives out error.
How To Reproduce
Config/File changes: No changes.
BUG 1: --fs is not actually optional.
Run
$ bash egs/metrics/run.sh --reference_folder compare/ref_dir --generated_folder compare/gen_dir --dump_folder compare/dump_dir --metrics "fpc"

Get error
usage: calc_metrics.py [-h] [--ref_dir REF_DIR] [--deg_dir DEG_DIR] [--dump_dir DUMP_DIR]
                       [--metrics METRICS [METRICS ...]] [--fs FS]
calc_metrics.py: error: argument --fs: expected one argument

BUG 2: We fill in the --fs, no matter we fill 24000 (int type) or "24000" (string type), it still does not work properly.
If we use "24000"
$ bash egs/metrics/run.sh --reference_folder compare/ref_dir --generated_folder compare/gen_dir --dump_folder compare/dump_dir --metrics "fpc" --fs "24000"

Get error
  0%|                                                                     | 0/3 [00:00<?, ?it/s]
  0%|                                                                     | 0/1 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "/mnt/c/users/lukec/pycharmprojects/Amphion/bins/calc_metrics.py", line 155, in <module>
    calc_metric(args.ref_dir, args.deg_dir, args.dump_dir, args.metrics, args.fs)
  File "/mnt/c/users/lukec/pycharmprojects/Amphion/bins/calc_metrics.py", line 110, in calc_metric
    score = METRIC_FUNC[metric](
  File "/mnt/c/users/lukec/pycharmprojects/Amphion/evaluation/metrics/f0/f0_pearson_coefficients.py", line 49, in extract_fpc
    audio_ref, _ = librosa.load(audio_ref, sr=fs)
  File "/home/luke/.conda/envs/Amphion/lib/python3.10/site-packages/librosa/core/audio.py", line 192, in load
    y = resample(y, orig_sr=sr_native, target_sr=sr, res_type=res_type)
  File "/home/luke/.conda/envs/Amphion/lib/python3.10/site-packages/librosa/core/audio.py", line 668, in resample
    y_hat = np.apply_along_axis(
  File "<__array_function__ internals>", line 180, in apply_along_axis
  File "/home/luke/.conda/envs/Amphion/lib/python3.10/site-packages/numpy/lib/shape_base.py", line 379, in apply_along_axis
    res = asanyarray(func1d(inarr_view[ind0], *args, **kwargs))
  File "/home/luke/.conda/envs/Amphion/lib/python3.10/site-packages/soxr/__init__.py", line 145, in resample
    if in_rate <= 0 or out_rate <= 0:
TypeError: '<=' not supported between instances of 'str' and 'int'

If we use 24000
$ bash egs/metrics/run.sh --reference_folder compare/ref_dir --generated_folder compare/gen_dir --dump_folder compare/dump_dir --metrics "fpc" --fs 24000

  0%|                                                                     | 0/3 [00:00<?, ?it/s]
  0%|                                                                     | 0/1 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "/mnt/c/users/lukec/pycharmprojects/Amphion/bins/calc_metrics.py", line 155, in <module>
    calc_metric(args.ref_dir, args.deg_dir, args.dump_dir, args.metrics, args.fs)
  File "/mnt/c/users/lukec/pycharmprojects/Amphion/bins/calc_metrics.py", line 110, in calc_metric
    score = METRIC_FUNC[metric](
  File "/mnt/c/users/lukec/pycharmprojects/Amphion/evaluation/metrics/f0/f0_pearson_coefficients.py", line 49, in extract_fpc
    audio_ref, _ = librosa.load(audio_ref, sr=fs)
  File "/home/luke/.conda/envs/Amphion/lib/python3.10/site-packages/librosa/core/audio.py", line 192, in load
    y = resample(y, orig_sr=sr_native, target_sr=sr, res_type=res_type)
  File "/home/luke/.conda/envs/Amphion/lib/python3.10/site-packages/librosa/core/audio.py", line 668, in resample
    y_hat = np.apply_along_axis(
  File "<__array_function__ internals>", line 180, in apply_along_axis
  File "/home/luke/.conda/envs/Amphion/lib/python3.10/site-packages/numpy/lib/shape_base.py", line 379, in apply_along_axis
    res = asanyarray(func1d(inarr_view[ind0], *args, **kwargs))
  File "/home/luke/.conda/envs/Amphion/lib/python3.10/site-packages/soxr/__init__.py", line 145, in resample
    if in_rate <= 0 or out_rate <= 0:
TypeError: '<=' not supported between instances of 'str' and 'int'

Expected behavior
Execute without error and dump results.
Screenshots
See Reproduce part.
Environment Information

Operating System: Debian 12
Python Version: Python 3.10.13
Driver & CUDA Version: NVIDIA-SMI 545.36, Driver Version: 546.33, CUDA Version: 12.3
Error Messages and Logs: See Reproduce part.

Thanks for your BUG report! I think there are some configuration mismatches. I will refactor this part to solve the problems this week.


Start migration of old scripts over into new ETL

[x] Fatal OD
[ ] 311
[x] Blotter
[x] Jail Census
[ ] Kane Census
[x] PLI

I'm going to take a look at this as well.

@saylorsd please take a look at 13d88ed, and let me know what you think, especially of the change in the CSVExtractor. I explained the logic in the commit message.

Also, what is the Kane Census?

:+1:
Though in the job tests, the jail and police blotter pipelines are registered as fatal od. Could end up being a problem if we start doing some integration testing?
Re: the Kane census
It's a census for what I believe are County Health Department nursing homes.  They were working out providing data to me on a timely matter.  I haven't gotten any official word on it, but It looks like they're publishing it weekly now. I can push a sample to this branch if it's up to date with your work.

@bsmithgall I finally got some time to get to the police blotter pipeline.  I was able to get it to pretty much work, and in doing so, realized some issues that are worth discussing. You can see the current changes here: a2ed761dcfd6e9dbc2e249583b1610b33cac1444 (note: this is a WIP)

the current fields for the police blotter are all capitalized which is might require a little bit of reworking for our schema .

I'll need to add some more flexibility to the loader class.  This mainly comprises of implementing more features of the CKAN datastore api, standardizing the methods for said calls, and passing back more response information.

That damn BOM is showing up on the blotter file and causing issues where the first header item pulled from the data starts with those 3 chars.

We'll need to work out how to deal with some higher-level issues with pushing the data.

how to track when a resource(in CKAN it's essentially one file) already exists within a package (dataset). Currently, when running the police blotter, it just creates a new file, because it is run with resource_id=''.  We'll need to store the resource id's somewhere.
Some situations will involve creating a new resource within the package after a certain period of time (e.g the Jail Census data)  However, this seems like just a waste of space as each month the same data is added to two different files - so maybe it won't be an issue.

Feel free to take a look at the commit and create any issues if you see fit, I'll do the same.

Nice work! If you take a look at the port-other-pipelines branch, there's a little bit in there that lets you pass an encoding kwarg, which fixes the BOM issue so long as you know the encoding ahead of time (which you should be able to know when you create a pipeline).
For fields, I think that you should be able to get them out of extractor.headers and/or extractor.schema_headers. As for the types, it might make sense to write a method that does some sort of dumb conversion based on the schema field types. I think that would be a lot better than having to do all the hard coding.

Nice! I can't see an issue where we won't know ahead of time unless the publisher changes their process without giving us a heads up.
Totally agree on the fields thing.  I just copy and pasted these for the time being so I could see it work.  I think a simple conversion like that is all we'll need since, once again, we should know all this stuff ahead of time, it can all be part of the hard-coded schema.

:+1: I think that for resource_ids it should be something similar -- can't you create the resource ahead of time and get the resource id? Then it could live in the pipeline's instantiation. It doesn't seem like something that you need to configure at runtime.
Thoughts?

Hmm... I'll have to think about it.  I'm leaning towards not, since manually creating a resource requires actually uploading a file.  I'd also like to leave open the option to automatically generate resources.
I think for the cases we have now and in the foreseeable future, we can call CKAN's 'package_show' and see if a resource with the same human-readable resource_name exists instead checking against the resource_id. And then just grab the resource_id attached to the resource_name.  This is something we'll know from the start and it shouldn't change.
I'll have to think more about if we'll need to automatically generate new resources entirely as I mentioned about with the Jail Census.  It might be a bridge we won't need to cross.

:+1:
Isn't there an existing CKANUpsertLoader method that checks for an existing resource?

I think there's one that pulls the names of ones in a package, but I'll make one that takes a name as an argument and returns an id.

Oh great that's good too. You can dump that into the generic method run at the beginning of all CKANLoaders as well. Looking up by name is probably the best bet for consistency going forward.

So I forgot about resource_exists() which returns a boolean but does exactly the same work I'm looking to do.  Is it bad practice to modify it to return the resource_id or None, but leave alone any implementations that evaluate its truth value? As far as I understand, they should still behave the same way.

I would rewrite the implementations to handle a NoneType instead because None and False behave differently and explicit is better than implicit.

Any progress on this @saylorsd ? Did you get it to upload successfully? I'm very excited.

Only a little -- been a bit busy.  I added a get_resource_id() method and changed resource_exists() to call resource_id = get_resource_id and return resource_id is not None.
I'm currently adding some more tests for  loaders and then I'll make a commit so you can see what's going on.

:+1: :+1:
Is there anything else that can be worked on in the meantime?

Hmm.. I don't know for sure.  I'll try and get this out real soon so we can go from there.  Does it look like it will be easy to merge your changes in port-other-pipeline with this branch if all I've really changed is loaders and test_loader?

Nah it'll probably be ok to just ditch that branch and move the changes into a new branch. Don't delete it yet though because we'll be able to recycle some of the pipelines.

Sounds good.  I think I'm just gonna get started on these tests and commit, since I can see this turning into quite a few new tests.  That way I can better show where I'm looking to go with the loader methods.

@bsmithgall Check out 1643a784110ebe5dfcb88ab9a55d57683cc7423b.
I renamed the CKANUpsertLoader Class to CKANDatastoreLoader to reflect the CKAN extension it uses as well as remove any ambiguity as we implement both insert and upsert methods within that class.
My todo in the TestCKANDatastoreLoader() class reflects my biggest question.  How should we go about testing these two different ways of using the datastore loader?  Does it make sense to keep the same tests, but run one using insert and the other using uspert?

You should be able to write unit tests for each method, mocking different HTTP responses as appropriate. I think the last two things we need to do are:

[ ] do something smart with the schema to autogenerate fields for the loader
[ ] do some sort of too-soon protection against re-running too aggressively in the pipeline's pre_run method.

Are the all-caps names requirements?

For CKAN I mean.

Also, are there only the three types in the police blotter (text, timestamp, numeric) or are there more?

Hey @saylorsd check out a64d337, I've implemented a little method on the BaseSchema class that converts to the CKAN-style fields. If there are more fields needed/types, I figure we can just extend the FIELD_TO_CKAN_TYPE_MAPPING dictionary. Let me know if that works for the staging environment.

The all caps thing is only for the police blotter. I just don't want to change the way it already is since it might break someones app or site if they're currently pulling that data. From a glance, it seems to be a very popular dataset.
Those are the only types for the blotter.
Re: fields: Sounds great! I'll take a look when I get back from class.

I've also added a bit to handle the duplicate file checking, along with a test. It's in 49c3ca6 if you want to take a look. Let's get this stuff merged soon!

I added the Asbestos Permit dataset to the list.  Since we currently don't' have a ETL process set up for this set, this should be the highest priority.  It will use the SFTP connector to pull and update it.  There will also be a series of pdfs (copies of the actual permits), each relating to a record in the xls.  I'll have the SFTP connector ready to merge today and hopefully I'll have something (#29) for the pdfs annd xls (#34) ready as well.

Are you storing both the PDF (binary file transfer I suppose) and the Excel on the CKAN? Or do the PDFs live on some other resource?

They will be elsewhere, so that will also involve another loader.

No I mean like can you construct regular URLs to them? Or do you have to load them yourselves?

Well the plan was to do both, in a sense.  I was thinking of having a @post_load method in the schema to build the urls since the pdfs will be named consistently. The urls would point to a location where I store the pdfs, unless I can get the county to store them online, then they'd be to that location.
The plan isn't to load them into CKAN either way since they might muck up the view with 10's of permits.

You should try to get the county to do it :stuck_out_tongue: but that sounds like the right way to do it :+1:

Maybe an S3 loader with boto?

For example: https://boto3.readthedocs.org/en/latest/guide/migrations3.html#storing-data


Retrofit 0.7 legacy classification improvements to 0.6.24

I didn't just copy and paste the code. I adapted it to mimic existing code and then tested it.


Improve X509CA disk implementation

Pull request check list

[X] Proper tests/regressions included?
[X] Documentation updated?

Description of change
This pull request enhances the X509CA "disk" implementation by introducing a new configuration option called bundle_file_path and enabling the use of intermediate CA certificates. The bundle_file_path parameter is now required when the specified cert_file_path does not contain a self-signed (root) CA. It allows Galadriel to issue certificates based on an external chain of trust. The bundle file should contain one or more intermediate CA certificates and/or root CA certificates, forming the trust chain up to the root CA. This update ensures more flexibility in managing CA certificates and provides better support for complex trust relationships.
This PR also updates the Galadriel server to utilize the entire certificate chain issued by the X509CA as the TLS certificate for the TLS connections with the Harvesters.
In summary, the changes include:
X509CA "disk" Implementation:

Added a new configuration option bundle_file_path to support external chains of trust.
Updated the X509CA documentation to reflect the new configuration option.
Modified the X509CA test cases to cover the new functionality.

Galadriel Server:

Updated the server code to utilize the entire certificate chain issued by the X509CA as the TLS certificate for the TLS connections with the Harvesters.

These changes provide a more robust and flexible X509CA "disk" implementation, enabling Galadriel to handle a broader range of trust scenarios.
Which issue this pull requests fixes

Thanks, I'll address your comments. There's something else I've just realized that I'm fixing: when there are certs in the ca.trustBundle, all certs are appended to the cert chain, even if they are root CAs, which is not the common practice.

Update: The last commits modify the trust bundle's handling to enhance the certificate chain creation process. Initially, the trust bundle is used to validate that the CA certificate can chain back to a trusted CA certificate. Following this verification, root CAs are filtered out from the trust bundle. The remaining trust bundle, set in ca.trustBundle, solely contains any necessary intermediate CAs. These intermediate CAs are then appended to the certificate chain during the issuance of new certificates. This approach ensures a streamlined and efficient creation of the certificate chain.