missing port in address and opentelemetry-operator-webhook-service errors

Hello,
I've been playing around with the Adot implementation for the past several months and everything was working fine. I've started to revisit this as i'm looking to do do some eventbridge and PagerDuty in 2024.
I've had it deployed across all my eks clusters for while but now seeing this error:
eks: v1.25
Adot Operator = v0.82.0-eksbuild.1
The Operator installs fine into the opentelemetry-operator-system NS:
pod/opentelemetry-operator-75b5b48d57-4xnlr   2/2     Running   0          25m

NAME                                     TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
service/opentelemetry-operator           ClusterIP   <IP_ADDRESS>   <none>        8443/TCP,8080/TCP   25m
service/opentelemetry-operator-webhook   ClusterIP   <IP_ADDRESS>   <none>        443/TCP             25m

NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/opentelemetry-operator   1/1     1            1           25m

NAME                                                DESIRED   CURRENT   READY   AGE
replicaset.apps/opentelemetry-operator-75b5b48d57   1         1         1       25m

I've then installed the following collector into a NS called: opentelemetry, which hasn't changed in the several months and was working fine.
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: collector-xray
spec:
  mode: deployment
  resources:
    requests:
      cpu: "1"
    limits:
      cpu: "1"
  serviceAccount: adot-collector
  env:
    - name: CLUSTER_NAME
      value: eksdev
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    processors:
      batch/traces:
        timeout: 1s
        send_batch_size: 50
      resourcedetection/eks:
        detectors: [env, eks]
        timeout: 2s
        override: false

    exporters:
      awsxray:
        region: eu-west-1
        index_all_attributes: true

      logging:
        loglevel: debug
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [resourcedetection/eks, batch/traces]
          exporters: [awsxray,logging]

      telemetry:
        logs:
          level: debug

I'm trying to deploy the following:
https://aws-otel.github.io/docs/getting-started/adot-eks-add-on/config-auto-instrumentation#configuring-the-auto-instrumentation
I'm see this seeing this error in the operator logs:

{"level":"info","ts":"2023-12-18T15:28:07Z","logger":"controllers.OpenTelemetryCollector","msg":"couldn't determine metrics port from configuration, using 8888 default value","opentelemetrycollector":{"name":"collector-xray","namespace":"opentelemetry"},"error":"missing port in address"}
{"level":"error","ts":"2023-12-18T15:28:07Z","logger":"controllers.OpenTelemetryCollector","msg":"Cannot create liveness probe.","opentelemetrycollector":{"name":"collector-xray","namespace":"opentelemetry"},"error":"service property in the configuration doesn't contain extensions","stacktrace":"github.com/open-telemetry/opentelemetry-operator/internal/manifests/collector.Container\n\t/workspace/internal/manifests/collector/container.go:127\ngithub.com/open-telemetry/opentelemetry-operator/internal/manifests/collector.Deployment\n\t/workspace/internal/manifests/collector/deployment.go:56\ngithub.com/open-telemetry/opentelemetry-operator/pkg/collector/reconcile.Deployments\n\t/workspace/pkg/collector/reconcile/deployment.go:40\ngithub.com/open-telemetry/opentelemetry-operator/controllers.(*OpenTelemetryCollectorReconciler).RunTasks\n\t/workspace/controllers/opentelemetrycollector_controller.go:237\ngithub.com/open-telemetry/opentelemetry-operator/controllers.(*OpenTelemetryCollectorReconciler).Reconcile\n\t/workspace/controllers/opentelemetrycollector_controller.go:225\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.1/pkg/internal/controller/controller.go:118\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.1/pkg/internal/controller/controller.go:314\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.1/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.1/pkg/internal/controller/controller.go:226"}

But also see this in Argo for the Sample java app i've deployed.

Sync operation to 7277bf3b0ec3e1545fe05c4474645c771126661e failed: one or more objects failed to apply, reason: Internal error occurred: failed calling webhook "vinstrumentationcreateupdate.kb.io": failed to call webhook: Post "https://opentelemetry-operator-webhook-service.opentelemetry-operator-system.svc:443/validate-opentelemetry-io-v1alpha1-instrumentation?timeout=10s": service "opentelemetry-operator-webhook-service" not found

I see this within Argo for the app i've added the instrumentation to.

Resource not found in cluster: opentelemetry.io/v1alpha1/Instrumentation:my-instrumentation (edited)
Note: I was also half way through migrating to 0.88 but gave up on this due to incomplete info on the migration guide and not introducing extra variables (i.e creating the new IAM role and setting advanced add on config etc).

Hi @bryan-aguilar,
Thanks for the reply:

I believe the collector does deploy successfully - and I am able to see traces in x-ray for another app that had the aws-otel-java bundled in the dockerfile.

k describe deployments.apps -n opentelemetry
Name:                   collector-xray-collector
Namespace:              opentelemetry
CreationTimestamp:      Mon, 18 Dec 2023 13:35:07 +0000
Labels:                 app.kubernetes.io/component=opentelemetry-collector
                        app.kubernetes.io/instance=opentelemetry.collector-xray
                        app.kubernetes.io/managed-by=opentelemetry-operator
                        app.kubernetes.io/name=collector-xray-collector
                        app.kubernetes.io/part-of=opentelemetry
                        app.kubernetes.io/version=latest
Annotations:            deployment.kubernetes.io/revision: 1
                        opentelemetry-operator-config/sha256:<PHONE_NUMBER>c8db39b085205e5d76c4ef07cde0112d12128b81021bc7f567bc21
                        prometheus.io/path: /metrics
                        prometheus.io/port: 8888
                        prometheus.io/scrape: true
Selector:               app.kubernetes.io/component=opentelemetry-collector,app.kubernetes.io/instance=opentelemetry.collector-xray,app.kubernetes.io/managed-by=opentelemetry-operator,app.kubernetes.io/part-of=opentelemetry
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:           app.kubernetes.io/component=opentelemetry-collector
                    app.kubernetes.io/instance=opentelemetry.collector-xray
                    app.kubernetes.io/managed-by=opentelemetry-operator
                    app.kubernetes.io/name=collector-xray-collector
                    app.kubernetes.io/part-of=opentelemetry
                    app.kubernetes.io/version=latest
  Annotations:      opentelemetry-operator-config/sha256:<PHONE_NUMBER>c8db39b085205e5d76c4ef07cde0112d12128b81021bc7f567bc21
                    prometheus.io/path: /metrics
                    prometheus.io/port: 8888
                    prometheus.io/scrape: true
  Service Account:  adot-collector
  Containers:
   otc-container:
``
    Image:       public.ecr.aws/aws-observability/aws-otel-collector:v0.32.0
    Ports:       8888/TCP, 4317/TCP, 4318/TCP
    Host Ports:  0/TCP, 0/TCP, 0/TCP
    Args:
      --config=/conf/collector.yaml
    Limits:
      cpu:  1
    Requests:
      cpu:  1
    Environment:
      CLUSTER_NAME:  eksdev
      POD_NAME:       (v1:metadata.name)
    Mounts:
      /conf from otc-internal (rw)
  Volumes:
   otc-internal:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      collector-xray-collector
    Optional:  false
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   collector-xray-collector-75899f9dcc (1/1 replicas created)
Events:          <none>

The instrumentation manifest is based on the docs

Here's the snippets:
---
apiVersion: apps/v1
kind: Deployment
metadata:
  # namespace: nextjs
  name: inws-java
spec:
  replicas: 0
  selector:
    matchLabels:
      app.kubernetes.io/name: inws-java
  template:
    metadata:
      labels:
        app.kubernetes.io/name: inws-java
      annotations:
        instrumentation.opentelemetry.io/inject-java: "true"
    spec:
      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:

apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: my-instrumentation
spec:
  exporter:
    endpoint: http://collector-xray-collector.opentelemetry:4317
  java:
    image: public.ecr.aws/aws-observability/adot-autoinstrumentation-java:v1.28.0

kubectl get customresourcedefinitions
NAME                                         CREATED AT
applications.argoproj.io                     2021-04-26T14:13:08Z
applicationsets.argoproj.io                  2022-04-05T08:09:31Z
appprojects.argoproj.io                      2021-04-26T14:13:08Z
awsnodetemplates.karpenter.k8s.aws           2023-08-21T11:09:37Z
certificaterequests.cert-manager.io          2022-02-01T16:25:46Z
certificates.cert-manager.io                 2022-02-01T16:25:46Z
challenges.acme.cert-manager.io              2022-02-01T16:25:46Z
clusterissuers.cert-manager.io               2022-02-01T16:25:46Z
clusterworkflowtemplates.argoproj.io         2021-06-08T15:41:39Z
cninodes.vpcresources.k8s.aws                2023-08-14T21:25:31Z
cronworkflows.argoproj.io                    2021-06-08T15:41:39Z
eniconfigs.crd.k8s.amazonaws.com             2021-04-26T10:27:29Z
extensions.dashboard.tekton.dev              2021-06-02T12:54:15Z
ingressclassparams.elbv2.k8s.aws             2022-02-16T11:17:43Z
instrumentations.opentelemetry.io            2023-12-18T11:34:50Z
issuers.cert-manager.io                      2022-02-01T16:25:46Z
machines.karpenter.sh                        2023-08-21T11:09:37Z
opentelemetrycollectors.opentelemetry.io     2023-12-18T11:34:49Z
orders.acme.cert-manager.io                  2022-02-01T16:25:46Z
policyendpoints.networking.k8s.aws           2023-10-18T08:34:37Z
provisioners.karpenter.sh                    2023-08-21T11:09:37Z
sealedsecrets.bitnami.com                    2021-04-26T14:50:59Z
securitygrouppolicies.vpcresources.k8s.aws   2021-04-26T10:27:32Z
targetgroupbindings.elbv2.k8s.aws            2021-04-26T14:06:11Z
workfloweventbindings.argoproj.io            2021-06-08T15:41:39Z
workflows.argoproj.io                        2021-06-08T15:41:39Z
workflowtemplates.argoproj.io                2021-06-08T15:41:39Z

Interesting I haven't touched the live cluster yet
But the output of 4) has got two extra services...
kubectl get services -n opentelemetry-operator-system
NAME                                                        TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
opentelemetry-operator                                      ClusterIP   <IP_ADDRESS>     <none>        8443/TCP,8080/TCP   118d
**opentelemetry-operator-controller-manager-metrics-service   ClusterIP   <IP_ADDRESS>    <none>        8443/TCP,8080/TCP   140d**
opentelemetry-operator-webhook                              ClusterIP   <IP_ADDRESS>   <none>        443/TCP             118d
**opentelemetry-operator-webhook-service                      ClusterIP   <IP_ADDRESS>    <none>        443/TCP             140d**

If it's any help here are some recent logs from Cert Manager cert-manager-cainjector pod
I1218 16:31:13.762847       1 reconciler.go:142] "cert-manager: Updated object" kind="mutatingwebhookconfiguration" kind="mutatingwebhookconfiguration" name="cert-manager-webhook"I1218 16:31:13.763122       1 reconciler.go:142] "cert-manager: Updated object" kind="validatingwebhookconfiguration" kind="validatingwebhookconfiguration" name="opentelemetry-operator-validation"I1218 16:31:13.768505       1 reconciler.go:142] "cert-manager: Updated object" kind="validatingwebhookconfiguration" kind="validatingwebhookconfiguration" name="aws-load-balancer-webhook"I1218 16:31:13.768834       1 reconciler.go:142] "cert-manager: Updated object" kind="mutatingwebhookconfiguration" kind="mutatingwebhookconfiguration" name="opentelemetry-operator-mutation"I1218 16:31:13.773718       1 reconciler.go:142] "cert-manager: Updated object" kind="validatingwebhookconfiguration" kind="validatingwebhookconfiguration" name="cert-manager-webhook"I1218 16:31:13.774599       1 reconciler.go:142] "cert-manager: Updated object" kind="mutatingwebhookconfiguration" kind="mutatingwebhookconfiguration" name="aws-load-balancer-webhook"I1218 16:31:13.778965       1 reconciler.go:142] "cert-manager: Updated object" kind="validatingwebhookconfiguration" kind="validatingwebhookconfiguration" name="opentelemetry-operator-validating-webhook-configuration"

Did someone previously try to install the operator using kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml? Because that's where those service names would come from.
I tested this on a dev cluster and here are my results.
Install with kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml
kubectl get services -n opentelemetry-operator-system
NAME                                                        TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
opentelemetry-operator-controller-manager-metrics-service   ClusterIP   <IP_ADDRESS>   <none>        8443/TCP   4s
opentelemetry-operator-webhook-service                      ClusterIP   <IP_ADDRESS>   <none>        443/TCP    4s

Install adot v0.82.0:
kubectl get services -n opentelemetry-operator-system
NAME                             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
opentelemetry-operator           ClusterIP   <IP_ADDRESS>   <none>        8443/TCP,8080/TCP   14s
opentelemetry-operator-webhook   ClusterIP   <IP_ADDRESS>   <none>        443/TCP             13s

I was also half way through migrating to 0.88 but gave up on this due to incomplete info on the migration guide and not introducing extra variables (i.e creating the new IAM role and setting advanced add on config etc).

Can you provide more information for this? Re the migration guide: If you are not using the add-on advanced configuration then there are no breaking changes for you.
If you have an advanced configuration that you need to migrate, and the guide is not clear, please share it here and we can provide guidance. Please verify that any info sensitive info is redacted from the advanced configuration first.

So I embarked on the migration and created the new IAM role that only has x-ray permissions but then it wasn't clear to me if I was supposed to add the ARN of the IAM role to the operator or the collector
I think with fresh eyes it's the collector
I gave up as I didn't think it was going to fix my initial issue which trying to get auto-instrumentation to work with the other error in the logs (couldn't determine metrics port from configuration, using 8888) is an additional thing expecting to come across.
to recap the latest state of play is:
A fresh install of Adot 0.82 has been installed on the cluster, with a brand new IAM role and SA (adot-collector). The collector hasn't changed at all and that's deployed in the namespace opentelementy and I am able to see traces in x-ray for another app that had the aws-otel-java bundled in the dockerfile.
I'm now trying to resolve the instrumentation issue.
Not sure if someone's run this before (it's likely)

kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml

Is this required for Instumentation?

If I run

kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml

Then my instrumentation works.

work with the other error in the logs (couldn't determine metrics port from configuration, using 8888) is an additional thing expecting to come across.

In your case you can effectively ignore this and the other error in the operator logs. In plain terms this error is saying "We cannot detect a user configured prometheus metrics port configured in service:telemetry for emmitting collector self telemetry. Assuming the default".  I also believe the second error regarding the liveness probe is because you do not have the health check extension configured. It is not a requirement but the operator tries to create a liveness probe if it exists, and produces an error if it cannot.
Do not run

kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml

while also having the ADOT EKS add-on installs. This effectively creates dual resources of the opentelemetry operator and will create undefined behavior. My suggestion is to just choose one method of installing and managing the operator. Since you have ran both on the cluster recently you will want to ensure that any dangling resources from the other installation are cleaned up. Uninstall one, do a cleanup of opentelemetry-operator-system namespace. Also check cluster level resources like CRDs and cluster roles/bindings to make sure they were deleted. Then proceed.

So I embarked on the migration and created the new IAM role that only has x-ray permissions but then it wasn't clear to me if I was supposed to add the ARN of the IAM role to the operator or the collector

Are you using the advanced configuration to deploy the otlp ingest collector? Or are you self managing an OpenTelemetry collector custom resource. Can you share your add-on advanced configuration?

Hi Brain, you da man!
v0.82 is running well (baring the the errors in the logs we've already discussed).
I ran the following:

kubectl delete -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml
Deleted the Adot add-on
Reinstalled the Adot add-on (v0.82)
Deleted and redeployed my inws-java app that has auto-instrumentation. (for extra assurances this wasn't a fluke)

I am seeing this error:
{"level":"info","ts":"2023-12-19T15:24:21Z","logger":"instrumentation-resource","msg":"default","name":"my-instrumentation"} {"level":"info","ts":"2023-12-19T15:24:21Z","logger":"instrumentation-resource","msg":"validate update","name":"my-instrumentation"} {"level":"error","ts":"2023-12-19T15:24:23Z","msg":"failed to select an OpenTelemetry Instrumentation instance for this pod","namespace":"inws","name":"inws-java-76b4b5d596-vdngf","error":"no OpenTelemetry Instrumentation instances available","stacktrace":"github.com/open-telemetry/opentelemetry-operator/pkg/instrumentation.
Where is the most appropriate place (namespace) to deploy the collector, previously I've been installing it in a NS I created called opentelemetry.

Where is the most appropriate place (namespace) to deploy the collector, previously I've been installing it in a NS I created called opentelemetry.

It depends™. This is all up to you and the design choices that you make. I would suggest keeping them out of opentelemetry-operator-system as that is managed by other (outside) services (add-on service). Ultimately, your choice on how you best want to namespace your observability solution.

Also regarding your latest error. I believe this is because you are missing an instrumentation object in the applications namespace. Refer to documentation here to set that up. https://aws-otel.github.io/docs/getting-started/adot-eks-add-on/config-auto-instrumentation#configuring-the-auto-instrumentation

brilliant, thanks for all your help on this.
The collector has been installed in the opentelemetry NS. This is successfully receiving traces from two different services deployed in two different namespaces. Once via a the bundled aws-java in the Dockerfile and the other via auto-instrumentation.
Re: v0.88
While I've got a stable working solution. I'll go away over Xmas and re-review the docs for the migration. I think the problem was the existing  opentelemetry-operator.yaml resources causing me red herring flags.
Thanks again Brian. Hope you have a great Christmas.

Ty, closing this for now. Please feel free to open a new issue if you run into roadblocks with the v0.88.0 migration.


Worker constructor does not accept URL

TypeScript Version:  3.2.0-dev.201xxxxx

Search Terms: worker new url, worker constructor
Code
new Worker(new URL(""))

Expected behavior: Compiles fine, as it is valid per the spec
Actual behavior:

[ts] Argument of type 'URL' is not assignable to parameter of type 'string'.

Playground Link: http://www.typescriptlang.org/play/#src=new Worker(new URL(""))%3B
Related Issues: #15338, #15246 and was recently updated in #28136 as well

PRs welcomed. You can find more information about contributing lib.d.ts fixes at https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md#contributing-libdts-fixes.

PR is up at https://github.com/Microsoft/TSJS-lib-generator/pull/600


cargo-ebuild-0.4.0: Error: Failed to fetch security advisory database

Hi,
I have a problem with cargo ebuild 0.4.0.
Whenever i try to create a ebuild from a rust project i'll get a error as follows:
Error: Failed to fetch security advisory database

Caused by:
    git operation failed: invalid version 0 on git_proxy_options; class=Invalid (3)

This happens in every project. The same problem appears on a different machine too. With version 0.3.3 I don't have this problem which is why i had to downgrade now to version 0.3.3.

Could you please give more details about the crates you are trying to generate ebuilds for?
You can also use version 0.4.0 with --noaudit flag, it should not try to fetch the database.

This happens with any repository, even with this one. (even tried with different tags from the cargo-ebuild repository)
--noaudit does work, thank you, at least this way i can use the latest version now.

This seems to be a problem with the rustsec library (https://github.com/rustsec/rustsec/issues/431). Until we have a fix, please keep using --noaudit useflag.


Why is dschf defined in function scope?

To enable DeepSpeed Zero Stage 3, you need to create and configure an persist instance of HfDeepSpeedConfig.
https://huggingface.co/docs/transformers/main_classes/deepspeed#non-trainer-deepspeed-integration
However, it appears that the current code dares to define it within the function scope.
https://github.com/OpenLLMAI/OpenRLHF/blob/fad3227afd3124ad41505974b49a24b953eba7ed/openrlhf/models/actor.py#L53-L56
Could you please explain the reason for this?

Internally, HfDeepSpeedConfig set a special weakref global object which may affect all transformers behavior. We only want HfDeepSpeedConfig take effects(enable deep.zero.Init) when initializing model with AutoModelForCausalLM.from_pretrained, so we define it locally and let gc collect it when the function return.
https://github.com/huggingface/transformers/blob/main/src/transformers/integrations/deepspeed.py#L75
def set_hf_deepspeed_config(hf_deepspeed_config_obj):
    # this is a special weakref global object to allow us to get to Deepspeed config from APIs
    # that don't have an easy way to get to the Deepspeed config outside of the Trainer domain.
    global _hf_deepspeed_config_weak_ref
    # will go away automatically when HfDeepSpeedConfig is destroyed (when TrainingArguments is destroyed)
    _hf_deepspeed_config_weak_ref = weakref.ref(hf_deepspeed_config_obj)


Revert the azure-spring-boot commits, as current Ci cannot parse these

@chenrujun As the starter packages are not able to process by doc Ci. We decided to revert the changes for now in order to unblock all other changes to master. Let me know if you have any further questions.
FYI, @scbedd

Docs Build status updates of commit 96bccaa:
:clock10: Full build: the average full build time is 345 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

@chenrujun  Got a wrong revert commits. Revert my changes here. Will do another PR for the right starter packages.
azure-servicebus-jms-spring-boot-starter-2.3.6-beta.

Docs Build status updates of commit 96bccaa:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because branch remove_starter has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/remove_starter

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Merge TypeScript and JavaScript Webpack Skeletons

After npm installing the Webpack skeleton, there's now a prompt question asking you to choose the desired language.

SWEET!


Add delete icon

Please add this icon called 'clear' to the dress-code.
clear icon
Usage
After doing a search via search text field, this icon should show up in the search input field instead of the magnifying glass.

The behavior (changing when text is entered) is not possible to have without javascript. But we can create a class for it and simulate the demo for the demo.


(tournaments) user stories for displaying tournaments

This issue should resolve the creation of multiple, descriptive, user stories which depict how tournaments get displayed from the perspective of the user.
Key Points:

Purpose: To establish clear and concise user stories that detail how users will interact with the tournament display feature.
Benefit: User stories will help developers understand the desired functionality and user experience from the perspective of the end-users.
Scope: This will likely cover various scenarios such as viewing an individual tournament, browsing a list of tournaments, interacting with tournament details, etc.

Possible Related Areas to Consider:

Filters or search functionalities for finding specific tournaments.
Displaying relevant information like tournament dates, participants, and status.
User interactions like registering for a tournament, viewing results, or sharing the tournament details.

@rqueiroz20
Do you want to add a "General" section to your user stories to outline features which apply to both the spectator and player?
Here's a potential template:
User Stories for Displaying Tournaments
Spectator Stories:

As a spectator, I want to view the schedule and progress of tournaments, so I can know when matches are taking place and follow the results in real-time.

As a spectator, I want to see the leaderboard and player statistics, so I can track players' performances and make predictions.

As a spectator, I want to watch live streams and view match highlights, so I can engage with the action and catch up on any missed content.

As a spectator, I want to participate in tournament chat rooms, so I can discuss matches and interact with other viewers.

Player Stories:

As a player, I want to view the tournament bracket and schedule, so I can see my opponents and match timings.

As a player, I want to track my progress in the tournament, so I can see how far I've advanced and what's next.

As a player, I want to access the tournament rules, prize pool, and relevant social feeds, so I'm informed and motivated.

General Stories:

As a user, I want to use filters or search functionalities, so I can easily find specific tournaments.

As a user, I want to see relevant tournament information like dates, participants, and status at a glance.

As a user, I want to register for tournaments, view results, and share tournament details with others.

The user stories you grouped together for spectators and participants don't really apply to spectators, since I would assume a user becomes a spectator after they join a tournament that is already in progress. We could talk to the team working on User Management to create an attribute related to a user's status as a participant or spectator. If you want to talk about it more, we can. I was thinking of modifying some of these anyway and we could come to a more unified approach.

That sounds good to me. Feel free to close the issue if those user stories are comprehensive enough for what we currently have modeled out.

For now, the user stories we have for displaying tournaments lines up well with those in #33. I'll close this issue for now, but once we speak to the User Management team, we can revisit our approach.

I am thinking about adding this part to the user stories to "general":

Justin can see the profile of each player in the tournament, including their past winning rate, past strategies (if possible, e.g., in a card game), and opponents, so he can decide what strategy to use later. (This feature is highly dependent on the user profile and matches group)

@MikeChen012345 The user story is a good one and we should take it into account eventually, but I'm more concerned about getting a working prototype done first, then we can add it on at a later date. Perhaps this could be another issue put into the backlog?

Issue Score: Satisfactory
Comments:
User stories look good. It doesn't really affect your user stories, but maybe adjust them to single elimination since you guys have decided to go with that route instead of double elimination. I took off points from this issue because there was no closing statement that explained what you guys did. Also, please do not leave unnecessary comments on the issue. If you need to discuss the issue, that should be done on Slack. Instead, the comments are a space for periodic updates on what work has been done.


Allow multiselect comparisons between Git timeline entries

Refs: #116361
We should be able to multi-select timeline entries and compare the 2 ends of the selection

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


"Automatic checkpoints" missing and/or not addressed

Automatic checkpoints have been available since at least Version 10  but the checkbox is not shown in the graphics above nor is the specific function addressed in this article as I believe it should be.

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

ID: 4dd8cc6b-2dba-951b-03bc-98180d8b8a9e
Version Independent ID: 6549b0bd-8ea2-d5d3-ab61-e9bc5b2c3505
Content: Using checkpoints
Content Source: virtualization/hyper-v-on-windows/user-guide/checkpoints.md
Product: windows-10-hyperv
GitHub Login: @scooley
Microsoft Alias: scooley

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Docs website cant access

https://simulatedgreg.gitbooks.io/electron-vue/content/

For me it works...

It work agian... only happen at saturday, thank you


Permissions in Android  incomplete

no  'android.permission.REQUEST_INSTALL_PACKAGES'  in PermissionsAndroid.js, so that i cant check this Permssions on android

react-native 0.61.5
react-native 0.63.3

To install packages from RN you need to implement custom native module, and it might be best to implement permission request there. But you can still create a PR to add missing permissions.

To install packages from RN you need to implement custom native module, and it might be best to implement permission request there. But you can still create a PR to add missing permissions.


feat: LSP highlight groups support

Support for neovim LSP highlight groups.
See: https://neovim.io/doc/user/lsp.html#lsp-highlight

ps: Thanks for this colorscheme! (:

❤ ❤ ❤

Thanks for the contribution @pyrho 🔥


Import path does not give reproducible results

Hi Matt and co.,
I've come across something that I don't understand. I noticed that the same paths (Mg_O201) from two different feff calculations gave different results with the same parameters, so I checked if this is also the case if the same path is imported from the same feff calculation and it seems so. Furthermore, it seems not to be random, but follow a pattern.
The paths were added in order as they are listed in the legend and every time I do this the shapes of the curves are exactly the same. The second is slightly different from the first and from the third on there is a significant difference. Note that this is without fitting, but simply giving each path the same parameters and using the values listed in the screenshot below.

The issue is that when I perform a fit using the different versions of the path, I get (slightly) different results. The fit for each version of this path is reproducible.
I've separately mailed the data and cif file to Matt, as I can't add a data file here.
Is this an expected result?
Siebe
PS Due to partial occupancy of the M site (Mg, Al) there is another thing to watch out for. Each time feff/Larix computes the atomic positions it seems to randomly select the Mg/Al distribution of the 6 Mg_M paths. Given the elemental composition, this should be 3/3.

@SiebevanderVeer  it looks like maybe those two paths have distances that are almost identical bur not quite exact to 4 decimal places.  Does that seem right to you?
I recommend picking one of these paths.  From the Session File you sent, it looks like maybe you imported 5 slightly different paths and set them all to have a coordination number of 6 -- adding to 30 total neighbors, if I am reading that correctly.

@newville, sorry for the confusion. The issue occurs when I import the same path several times. The final comment on the partial occupancy I've added because I am not sure that this first Mg-O path will remain identical in each of the different atomic configurations, where the 6 nearest metal neighbours to Mg are a combination of Mg and Al.
For a bit more background on how I came across this. I did data fitting using a certain version of a cif file of a layered structure, but I came to the conclusion that the interlayer atoms and their paths do not significantly contribute to the EXAFS so I made another version of the cif file, where the interlayer atoms were removed. This I wanted to do to get a clearer overview of which paths within the octahedral sheets were available and explore which of these contribute to the EXAFS. Then when I did a first shell fit of the new cif file, the fit was significantly different from the one obtained with the previous cif file. I wondered how that could be, so I imported the Mg-O path of both files and they were different while having the same variables. After some more exploration I came to the conclusion that when I import a path multiple times, it is different. As mentioned in the original post, this behaviour seems to be reproducible.
Hope this clarifies the issue a bit.

@newville, sorry to bother you on this, but do you have any further feedback on this issue, based on the clarification above?

@SiebevanderVeer I guess I don't.  I'm not 100% sure I know what you are seeing that is a problem.  Having a slightly distorted structure will give paths that are very similar but not identical.  Is that what you are seeing?
Having partial occupancy will cause randomly selected scattering atoms.  Is that what you are seeing?
It definitely helps if you can provide a reproducible script that demonstrates what the problem is.

Hi Matt, ok. I'll think a bit on how better to explain the issue. I'll get back on it early next week.

@newville, let's try this again. When you are talking about a script, do you mean the sequence of actions that I take?
I am using the cif file I sent to you for the feff calculation with Mg as the absorbing atom. When I import the first shell Mg-O path multiple times, I repeatedly see the same issue, as shown in the image in the original post. I am not importing degenerate, or slightly different paths, but the same one multiple times and it gives different results.

@SiebevanderVeer By script I mean either the Larix Session File or the Command Script from the Larch buffer.  This will show the exact sequence you took.
You say that you import "the first shell Mg-O path" multiple times.   What does that mean to you?  Like, if you are reading the same FeffNNNN.dat file, then the results have to be identical.   For a single Feff run, there might be several fefffNNN.dat files that would represent a "first shell".   The fefffNNNN.dat files represent "paths" which are one set of atoms with one geometry and one set of atomic potentials.   But a "shell" is sort of a vague concept --  for your case, there could be 6 different paths in the first shell.  Those would not be identical, but they are all "first shell".
If you are running Feff multiple times on the same input file, you will get identical results.  But if you re-make the input file from the CIF file -- especially in the case of partial occupancy -- then the Feff file might have different arrangements of atoms, and indeed different atom types at each partially occupied position.  That would give different results - probably only slightly different.  But, the path files would NOT be "the same".  They might be named the same, but Feff names files "feff0001.dat", "feff0002.dat", ...., so not all "feff0001.dat" files are the same.

Hi Matt, thanks for the further explanations; the point on the differences between the re-makes of the input file is clear. With regards to further information, I will send you the session file, the history saved as a script, as well as the feff file with which I observe this behaviour.
I see now that my phrasing is unclear, apologies. What I did is I imported the same FeffNNNN.dat (feff0001.dat) file from the same feff calculation multiple times, see Mg_O201 to Mg_O201d in the image in the original post. If I repeat this process, by removing the paths and loading them again, I see the same behaviour.

@SiebevanderVeer When I look at your project files, some of those "Mg-O at 2.01 Ang" paths are, in fact, identical, while others are not precisely identical.   I think "Mg_O201_c" and "Mg_O201_d" are identical.  The path labeled "Mg_O201" is clearly from a different calculation.  The path labeled "Mg_O201_a" also appears to be from a different calculation (several of the parameters in the Feff.dat file are just different), though it is a little less clear how that came to be.
Again (and apologies if this is already clear to you) if you run feff with a different input file (or a different set of atomic positions)  then the results may be slightly different.

@SiebevanderVeer I think you have understood what was your initial error, then this issue is not relevant anymore.


impl a sale history trigger

if the business wants to create a sale history for the customer after making an order, what is the SQL query equivalent for doing that!
Note: the history record may contain customer firstname  and lastname, order products names, quantity, and the total order amount of money.

After a lot of work and search I couldn't get the right answer for this issue, so I got help from ChatGpt:
link of chatbot solution: https://chat.openai.com/share/fc8f13b5-3df3-48bb-a851-32f528e9d022


Update readme/docs

Todo

Codesandbox Demo
Features: Mention support for prettier
Different flows: Generation, Scaffolding, Bootstrapping
Explain the relationship between GraphQL types, resolvers and models
Benefits of type-safety:

Map GraphQL schema to resolver implementation
Type-safe data flow inside of resolvers (resolver return value <> parent value)
Auto-completion & error-catching on args, return & parent values

Common usage flows

Adding a GraphQL field/type
Resolver scaffolding: copy&pasting
Initial setup
Adding a database

Config file overview

GraphQL type <> model mapping
Scaffolding layouts

Contributors
Credits: gqlgen

Please also add a note that Flow + Reason are not yet supported in graphqlgen.


Update Wave.toml

Previous PR:
https://github.com/anoma/namada-testnets/pull/494
https://github.com/anoma/namada-testnets/pull/1156
https://github.com/anoma/namada-testnets/pull/1731
Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

Successfully validated transactions.toml file for commit hash 9e5fd88


Possibility to correct or remove an entry in the contact diary for persons or places

Feature description
Possibility to correct or remove an entry in the contact diary for persons or places if the entry was not assigned

Problem and motivation

If you make a mistake while entering it or if an entry is no longer required, it cannot be removed
Is this something you're interested in working on
Yes

Hey @BFallert
It is possible to remove entries from the contact diary!
Please see https://www.coronawarn.app/en/blog/2020-12-28-corona-warn-app-version-1-10/ for a How-To.
If you're happy with this answer, please close this issue.

Thanks for this advice! That solves my problem. The menu would of course also be helpful for the people or places.

@BFallert Thanks for contributing here!
@Ein-Tim Many thanks for answering.
Best wishes, DS

Corona-Warn-App Open Source Team


Update IntelliJ IDEA 2016.3.6 EAP to build 163.15188.5

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Verified locally.


Number of SRAM reads for ofmap for input stationary dataflow is unrealistically small

The problem here is that number of reads for SRAM in ofmap for input stationary dataflow is unrealistically small. Upon inspection of the code, it seems that during the simulation the number of reads is not added to each other in each iteration of the output matrix. So instead the number of reads are overwriting each other so the final number of output reads becomes the number of reads of the last iteration. Hope this is clear.

Thanks @boukhary123 , I missed this issue here. Replicated the listing with more info in #44 .
Closing this by marking it as duplicate.


Element not catching 'cloudinarydone' trigger

I have a file upload that sends the file just fine, but it isn't registering the trigger afterward:
form
  .append($.cloudinary.unsigned_upload_tag 'cloudinary_transform', {
      cloud_name: 'mysite',
      tags: 'mytag'
    }).bind('cloudinarydone', () -> console.log 'finished')

I have also tried variations of
form
  .append($.cloudinary.unsigned_upload_tag 'cloudinary_transform', {
      cloud_name: 'mysite',
      tags: 'mytag'
    }).on('cloudinarydone', () -> console.log 'finished')

The image uploads just fine, and I see the data response in the console, but I'm not able to register the trigger (i.e. finished is never logged).
Has this been changed recently, or is there some other obvious problem?

Your syntax is not well formed. Try the following:
$('body').append($.cloudinary.unsigned_upload_tag('cloudinary_transform', {
      cloud_name: 'mysite',
      tags: 'mytag'
    })).bind('cloudinarydone', function() {console.log("finished")});

Thanks for your answer.  Sorry for not mentioning, but it is coffeescript and is equivalent to what you have written:
form.append($.cloudinary.unsigned_upload_tag('cloudinary_transform', {
    cloud_name: 'mysite',
    tags: 'mytag'
})).bind('cloudinarydone', function() {
    return console.log('finished');
});

See here for reference
Any other ideas as to what could be the issue?

append will return the form and not the upload tag, so the binding is done on the wrong element.
Try:
$.cloudinary.unsigned_upload_tag('cloudinary_transform', {
    cloud_name: 'mysite',
    tags: 'mytag'
}).appendTo(form).bind('cloudinarydone', function() {
    return console.log('finished');
});

Great, this solved it for me -- thanks!
Solution below (with function inputs) for future reference by others:
$.cloudinary.unsigned_upload_tag('cloudinary_transform', {
    cloud_name: 'mysite',
    tags: 'mytag'
}).appendTo(form).bind('cloudinarydone', function(e, data) {
    return console.log('finished', e, data);
});


3rd party connectors are not displayed from the connection manager

Bug Description
A description of what the bug is.
Steps to Reproduce
note: make sure to add a view 3rd party connectors

from the home page click privacy requests
click connection manager
from the drop down select any of the added 3rd party connectors

Expected behavior
after step two the the 3rd party connectors should be listed.
after step three the selected connector is not displayed
Screenshots

Environment

Version:
OS:
Python Version:
Docker Version:

Additional context
Add any other context about the problem here.

FYI @rsilvery

completed, moving to done.


FEATURE REQUEST: Query user before defaulting to hello world page

I recently lost my content due to my own ineptness while doing a new browser installation. I'm not really sure how, but it proves that it is possible. To avoid this in the future, it would be awesome to ask the user at installation time if they already have content on the same browser somewhere else. After that, either attempt to sync, prompt them to log onto the browser, or let them paste in their content - whatever the best option might be.

I have added the Vivaldi config folder to my backups. Closing issue.


Conditional tests should use the value of test when their containing suite is called.

Some tests conditionally disable groups of tests by capturing either test or test.skip from the top-level scope before the tests are run and later calling the captured function instead of test:
https://github.com/Polymer/lit-html/blob/1d0549426df5fc420285812f634970d92a027905/src/test/lib/render_test.ts#L22-L34
However, this can potentially prevent the test runner from associating them with the correct suite, which might be a problem if they are meant to be part of a suite with (e.g.) a setup function.

Yeah, it's pretty strange. I found this while trying to do https://github.com/Polymer/lit-html/pull/937, where the render tests were being run twice: the tests that were using a captured test would run outside of all suites and those that depended on setup / teardown hooks would break.


Shared Nextflow environment not available.

The shared Nextflow environment referred to in:
analyses/01_assembly-workflow_initial-run_rackham/run_nextflow.sh
is no longer available.
Do we need to point it somewhere else or simply just create a new environment?

What happened to the allocation?
Either:
Make a new environment and make a PR to the correct the path in the template.
Or:
Comment out the environment setup in the run_nextflow.sh and load Nextflow from your own conda environment or from modules.
We should make an envs folder with the conda definition of the environment.


Using the object's hashcode avoid duplication of rendering

var previousModelJSONStr = JSON.stringify(model)
model = merge(model, result)
var nowModelJSONStr = JSON.stringify(model)
if (hashCode(previousModelJSONStr) !== hashCode(nowModelJSONStr)) {
    render(model, view, name)
}

@jbucaran
For the model, If the each change is same, render function will be repeated calls, although the virtual dom very fast, but it will waste performance, whether it is feasible to do so?

@crixusshen Nice. The real question is, which one is is faster: JSON.stringify or render(model)?
😄

@dodekeract What do you think?

@jbucaran I have 3 issues with this:

JSON.stringify is not guaranteed to be deterministic. If it is, that's an implementation detail - not a standard.
To "not update" we should just look if the action returned a model change. If it did it's reasonable to assume that the model is actually different.
JSON.stringify isn't able to stringify everything. For example Maps, Sets, etc.. I think that's makes it the wrong tool for the job.

So all in all I'd just suggest to look at what the action returns to determine if a render should happen.

@jbucaran Now the route module, if the browser is frequent forward and backward, will appear such problems, but the model did not change.In the immutable.js,the principle of immutable. Is() and hashcode are similar, have optimized space? （My English level is very poor, please understand ^_^）

@dodekeract There's also circular reference errors. 🤔

JSON.stringify will crawl. you're better off delegating to userland sCU or an immutable data store (and auto-sCU). i personally like https://github.com/arqex/freezer

@crixusshen To optimize the render pipeline, we should look into requestAnimationFrame first.
How often an action that is supposed to update the model doesn't actually update anything?

@jbucaran If you introduce requestAnimationFrame I desperately need a way to hook into the next update. I currently have to measure dimensions of an element in my code that may change its size when the model gets updated.

@dodekeract Nothing yet, so no worries.

Don't think I am going to use JSON.stringify in the near future so closing. Thanks @crixusshen 👋.


androidPath should use PathBuilder as receiver instead of argument

This would bring it in parity with the Path { lambda.

Not so much solved as rendered obsolete by #157


KYLIN-3526 Add check for hybrid name with special character

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Bugfix/641 make cmdstan manual

Submisison Checklist

[ ] Run tests: ./runCmdStanTests.py src/test
[x] Declare copyright holder and open-source license: see below

Summary:
command make manual works on fresh install of cmdstan, stan.  Stan PR https://github.com/stan-dev/stan/pull/2694 fixed stan/make/manual so that directory doc is created for module's documentation suite.  this PR adds more cleanup to makefile.
Intended Effect:
make target make manual should build documentation suite
How to Verify:
run make
Side Effects:
none
Documentation:
none
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Columbia University
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

@seantalts or @syclik - how long does it take for merges to github to be picked up by circleci?  this fix depends on file stan/make/manual, but the circleci log looks like it's not seeing the changes.  retest later?

Ah, merges to Stan? Hmm, let me try to manually re-run it... I'm not really sure, actually. We may also want to get rid of the circleci part if the book has been moved out...

The user's guide has been moved out, but not the functions reference and not the reference manual.

@seantalts
I'm looking at the circleci logs and task: git submodule update --init --recursive is checking out this stan submodule:
Submodule path 'stan': checked out 'dc01681e6e578ae539da82710dcf6eceb2b5de07'

why isn't it checking out latest develop:  7ea40259c64a5fd90bd8b867e25afd6788ff22cc?

I guess it's testing the exact code in this PR, instead of the result of merging this PR with develop :( Would you mind merging in develop and pushing and seeing if that fixes it?

Would you mind merging in develop and pushing and seeing if that fixes it?

what is the git incantation to do this? trying to understand what's here: https://git-scm.com/book/en/v1/Git-Tools-Subtree-Merging , but like the unix man pages, you can only understand it once you already understand it.   Sweet.

finally!!!!

$ git pull origin develop
will merge the current state of develop into your branch.  I think you need to wait for the CI to push up the changes to the downstream repos.

@seantalts could you please approve PR on manual?


'make start' in project root does not work, it starts only the backend

make start is currently broken in the project root.
start:  ## Start
        @echo "Starting application"
        $(MAKE) start-backend
        $(MAKE) start-frontend

This will only start the backend and when it is cancelled/stopped, the frontend will run :-O
We could fix this by doing something like: start:  start-frontend start-backend in the Makefile but then you need invoke make with make -j2 start
I found at https://stackoverflow.com/questions/19521438/how-to-access-make-options-in-makefile
that this should check for make being called with -j :
PARALLEL = $(findstring j,$(firstword -$(MAKEFLAGS)))$(filter -j,$(MAKEFLAGS))
Makefile gurus: would it be possible to check for -j2 and print a warning and abort if one doesn't start the stack with '-j 2'
Otherwise I suggest we just remove this and print a message "Please do a 'make start-frontend' and 'make start-backend' in separate terminals" .

Should we just remove the make start command? It is not mentioned in the readme, and it seems like it would give you a fairly unusable jumble of output from both commands.


add seconds for DateTimerPicker

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

Examples 🌈

Motivation 🔦

#1961


Update docs for v1

Closes #647
@rannn505, I need your help with:

Updating the Configu Flow Diagram in docs/introduction/workflow.mdx to reflect the ConfigSchema structure. I don't have the source image.
INPUT: I want to detail the context each ConfigExpression has depending on the relevant feature. I'm having some trouble deciding where to detail the context of all the CLI features that use expressions. The only place that makes sense is in the ref.mdx file but it's currently auto-generated. Should we maybe include the context details as part of the descriptions of each flag?
I couldn't identify any tool to generate docs for clipanion similar to oclif readme. How should we proceed?

Notes:

Also fixed some broken links in CONTRIBUTING.md and other files that still reference the old @configu/ts pacakge.
Also fixed a broken link in packages/integrations/stores/aws-secrets-manager/README.md
Also fixed a mistake in packages/integrations/stores/toml-file/README.md
The entire Configu section of the docs shouldn't be updated until the platform has upgraded to v1. First, because the docs won't reflect reality until then. Second, the new screenshots can't be produced until the platform is updated.

closing to reopen so we can trigger mintilfy preview


Not able to embed permanent live url link in youtube

Be sure to search for your issue before opening a new one.
Current Behavior

Not able to use permanent live url from youtube i.e https://www.youtube-nocookie.com/embed/live_stream?channel=UC6K7yzj2kV3v3sASdaYCY0Q although i am able to embed the same with iframe
Expected Behavior

I should be able to use permanent live embed
Steps to Reproduce

Just put https://www.youtube-nocookie.com/embed/live_stream?channel=UC6K7yzj2kV3v3sASdaYCY0Q  in mediaurl and it will not work but with iframe this works
Environment

URL attempting to play: https://www.youtube-nocookie.com/embed/live_stream?channel=UC6K7yzj2kV3v3sASdaYCY0Q
Browser: Chrome
Operating system: Mac
jsFiddle example: https://jsfiddle.net/sv5x3ug1

Other Information

No

using the permanent live URL results in playing a weird playlist
I entered this URL:
https://www.youtube.com/embed/live_stream?channel=UCLA_DiR1FfKNvjuUpBHmylQ
but the iframe I got had src= https://www.youtube.com/embed/null?autoplay=0&mute=0&controls=0&origin=http%3A%2F%2Flocalhost%3A8000&playsinline=1&listType=playlist&list=UUIYVU7fPs_n6gJIBso3ryeg&showinfo=0&rel=0&iv_load_policy=3&modestbranding=1&enablejsapi=1&widgetid=1
any idea what is going on here?

Not sure if this is related, but I do get an old version of the stream when I enter such URL. It loads fine but displays something different (from the past) than what I would get if I open the url in the browser directly.

I've removed the list_type, added live_stream instead of null and changed list to channel (not replacing UC with UU in the URL) which seems to work:
https://www.youtube.com/embed/live_stream?autoplay=0&mute=0&controls=0&origin=http%3A%2F%2Flocalhost%3A8000&playsinline=1&channel=UCLA_DiR1FfKNvjuUpBHmylQ&showinfo=0&rel=0&iv_load_policy=3&modestbranding=1&enablejsapi=1&widgetid=1

Seems like the JS API does not support these methods. The only solution I found online is from this stackoverflow thread (2017) that suggests creating an iframe with the constructed url and passing that to the YT instance instance instead of an empty div:
https://stackoverflow.com/questions/47241553/youtube-iframe-api-for-live-videos
<iframe id="player" src="https://www.youtube.com/embed/live_stream?channel=CHANNEL_ID?enablejsapi=1"></iframe>

var player = new YT.Player('player', {});


silence warning about if guard

gcc 6.1.1 has this warning at Fedora 24.
I'm not quite sure how to fix this right, now patch does fixes the warning and it should do as previously. So this should be just style without functional change.
In file included from src/sregex/sre_vm_thompson_jit.c:16:0:
./dynasm/dasm_x86.h: In function 'dasm_put':
./dynasm/dasm_x86.h:207:2: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
  if (*p++ == 1 && *p == DASM_DISP) mrm = n; continue;
  ^~
./dynasm/dasm_x86.h:207:45: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if'
  if (*p++ == 1 && *p == DASM_DISP) mrm = n; continue;
                                             ^~~~~~~~

@maage Maybe we should update the upstream dynasm instead? We simply copied over the dynasm directory of the luajit-2.0 git repository BTW.


Adding Minimum Risk Training with OpenNMT

Hi,
Any plans of adding MRT with OpenNMT?

Hi,
Still no plans for it unfortunately. Here is the forum post that references this feature request:
http://forum.opennmt.net/t/minimum-risk-training-for-nmt/347


Proximal Policy Optimization example

This is a draft PR for reinforcement learning example using the Proximal Policy Optimization algorithm. It's a work in progress.

Codecov Report

Merging #470 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #470   +/-   ##
=======================================
  Coverage   74.29%   74.29%
=======================================
  Files          55       55
  Lines        3976     3976
=======================================
  Hits         2954     2954
  Misses       1022     1022

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 a420315...399e9b2. Read the comment docs.


Race condition on creating a deployment PR

There was a race condition observed:
precondition: deployment branch deploy/name and PR exists
a new gitops workflow run that include update to the deployment
prer in the run fetches the repo with deploy/* branches and start rendering manifests
original PR 1 merged and branch automatically deleted
prer in the run pushes the updated deployment branch and creates a new PR
As a result, the newly created branch and PR includes exact copy of the commits history from the original branch which causes a merge conflict since changes are already present in the target branch (main)

We have discussed this issue offline. Looks like the window when such race condition may occur may be reduced. The race condition occurs only when existing deploy branch is updated and force pushed as a new one. prer should only use git push --force when no previous deployment branch exists and if such push fails the whole prer run should be reexecuted starting from git fetch
This does not solve the problem completely since small time window between pushing the branch and creating a PR still exist.


Remove top-tabs when side-tabs are enabled

See subject. Side-tabs make merely sense when top-tabs can be switched-off.

Chrome doesn't allow hiding the horizontal bar at the top, so extensions can't support it yet.


Return instances of Model/Collection.

This is a great plugin, but I would like that the returned values be actual Model or Collection instances, instead of simple objects with just a toJSON method.
https://github.com/strapi/bookshelf-cache-redis/blob/master/src/index.js#L88-L90
We're missing out on all the APIs provided by Model or Collection.

Hi @avaly sorry for delay. Actually we are focus on Strapi v3 and don't support this module. Please submit a PR if you want any update for this repo. Thank you


Make AABB change trigger bounding box update

closes #42388
Changing AABB (e.g., by modifying mesh) will now trigger a redraw of the bounding box.

Works for me on 3.2 branch :+1:

Thanks!

Cherry-picked for 3.2.4.


Cache the dependencies

Fixes #295

Awesome, thanks so much for all your work on this, @zoo868e! At least based on how the jobs ran on this PR, I expect this is going to almost entirely fix the issue (perhaps with the exception of cases where populating the cache itself fails, which should presumably be much less common than at least one of 149 jobs failing for the same reason).


preserveUnknownFields is removed from CRDs by operator-sdk generate bundle

Bug Report
We need to explicitly set preserveUnknownFields: false to support upgrades between v1beta1 CRDs and v1 CRDs. In the past, we've used YAML post-processing on the CRD files to set this property explicitly. I'm working on upgrading our project to Operator SDK v1.3.2, and so now we can leverage kustomize for some of this "post-processing" of CRDs.
I've configured kustomize patches, for example:
$ cat config/crd/patches/pruning_in_datapowerservices.yaml
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: datapowerservices.datapower.ibm.com
spec:
  preserveUnknownFields: false

I have validated those are outputting correctly for our two CRDs:
$ kustomize build config/manifests | grep preserveUnknownFields
  preserveUnknownFields: false
  preserveUnknownFields: false

Our bundle make target looks like this:
# Generate bundle manifests and metadata.
bundle: manifests kustomize
        operator-sdk generate kustomize manifests
        cd config/manager && $(KUSTOMIZE) edit set image controller=$(IMG)
        $(KUSTOMIZE) build config/manifests | operator-sdk generate bundle $(BUNDLE_METADATA_OPTS)

As the kustomize build config/manifests is the input to operator-sdk generate bundle, and I know the properties exist in that input, it narrows the point of omission to the operator-sdk copying of these files to the bundle/manifests output directory.
What did you do?
make bundle
What did you expect to see?
CRDs output in bundle/manifests should retain preserveUnknownFields: false.
CRDs output in bundle/manifests should match the output from kustomize build config/manifests.
What did you see instead? Under which circumstances?
The preserveUnknownFields property is stripped from the CRDs when placed into bundle/manifests.
$ grep -R -c preserveUnknownFields bundle/manifests
...
bundle/manifests/datapower.ibm.com_datapowermonitors.yaml:0
bundle/manifests/datapower.ibm.com_datapowerservices.yaml:0
...

Environment
Operator type:

/language go

Kubernetes cluster type:
OCP 4.6 / 4.7
$ operator-sdk version
operator-sdk version: "v1.3.2", commit: "5dd883dc90085da6a6e75bb05443b4d491a39143", kubernetes version: "1.19.4", go version: "go1.15.5", GOOS: "linux", GOARCH: "amd64"

$ go version (if language is Go)
go version go1.15.8 linux/amd64

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.5", GitCommit:"e6503f8d8f769ace2f338794c914a96fc335df0f", GitTreeState:"clean", BuildDate:"2020-06-26T03:47:41Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0+d670f74", GitCommit:"d670f744c7507b1afebfa72ef3f79bf924ad5467", GitTreeState:"clean", BuildDate:"2021-05-21T13:35:23Z", GoVersion:"go1.15.7", Compiler:"gc", Platform:"linux/amd64"}

Possible Solution

Additional context

@aharbis One more way could be to set this in controller-gen options. Can you try setting this in Makefile (similar to this): https://github.com/operator-framework/operator-sdk/blob/6351af55dd38c88ca19114d0c165eadec5c82143/testdata/go/v3/memcached-operator/Makefile#L41

@varshaprasad96 Yes, except that's broken for v1 CRDs: https://github.com/kubernetes-sigs/controller-tools/issues/476

If this happens soonish we can backport it to a patch release for 1.12.0, but otherwise we think this is fine for 1.13.0.

We investigated the issue, and found that the kustomize generates the yaml fields by taking inputs from the patch/ dir, while generating bundle we Marshal the crd to bytes so that it is written to a file. While marshalling, as the preserveUnknownFields has the omitempty tag on it, its default value is false and hence its not explicitly written. This brings us to the same problem as faced in controller-gen which is mentioned in here.
The only option we found it to write it explicitly into yaml file using script.
Script is:
function generate_preserveUnknownFieldsdata() {
    for j in config/crd/patches/*.yaml ; do
        if grep -qF "preserveUnknownFields" "$j";then
            variable=`awk '/metadata/{flag=1} flag && /name:/{print $NF;flag=""}' "$j"`
            for k in config/crd/bases/*.yaml ; do
                if grep -qF "$variable" "$j";then
                    filename=`awk 'END{ var=FILENAME; split (var,a,/\//); print a[4]}' "$k"`
                    awk '/^spec:/{print;print "  preserveUnknownFields: false";next}1' "bundle/manifests/$filename" > testfile.tmp && mv testfile.tmp "bundle/manifests/$filename"
                fi
            done
        fi
    done
}

generate_preserveUnknownFieldsdata

Also, modified the make bundle in Makefile as shown in below:
.PHONY: bundle
bundle: manifests kustomize ## Generate bundle manifests and metadata, then validate generated files.
	operator-sdk generate kustomize manifests -q
	cd config/manager && $(KUSTOMIZE) edit set image controller=$(IMG)
	$(KUSTOMIZE) build config/manifests | operator-sdk generate bundle -q --overwrite --version $(VERSION) $(BUNDLE_METADATA_OPTS)
	operator-sdk bundle validate ./bundle | ./preserve_script.sh

We are planning to document these as a FAQ to the docs section.

We investigated the issue, and found that the kustomize generates the yaml fields by taking inputs from the patch/ dir, while generating bundle we Marshal the crd to bytes so that it is written to a file. While marshalling, as the preserveUnknownFields has the omitempty tag on it, its default value is false and hence its not explicitly written. This brings us to the same problem as faced in controller-gen which is mentioned in here.
The only option we found it to write it explicitly into yaml file using script.
Script is:
function generate_preserveUnknownFieldsdata() {
    for j in config/crd/patches/*.yaml ; do
        if grep -qF "preserveUnknownFields" "$j";then
            variable=`awk '/metadata/{flag=1} flag && /name:/{print $NF;flag=""}' "$j"`
            for k in config/crd/bases/*.yaml ; do
                if grep -qF "$variable" "$j";then
                    filename=`awk 'END{ var=FILENAME; split (var,a,/\//); print a[4]}' "$k"`
                    awk '/^spec:/{print;print "  preserveUnknownFields: false";next}1' "bundle/manifests/$filename" > testfile.tmp && mv testfile.tmp "bundle/manifests/$filename"
                fi
            done
        fi
    done
}

generate_preserveUnknownFieldsdata

Also, modified the make bundle in Makefile as shown in below:
.PHONY: bundle
bundle: manifests kustomize ## Generate bundle manifests and metadata, then validate generated files.
	operator-sdk generate kustomize manifests -q
	cd config/manager && $(KUSTOMIZE) edit set image controller=$(IMG)
	$(KUSTOMIZE) build config/manifests | operator-sdk generate bundle -q --overwrite --version $(VERSION) $(BUNDLE_METADATA_OPTS)
	operator-sdk bundle validate ./bundle | ./preserve_script.sh

We are planning to document these as a FAQ to the docs section.


End beta version by uninstalling

This uninstalls the extension from all clients.
Previously I was doing a custom thing each time to force uninstall. This adds a specific new uninstallation event page.

@meacer consider this a TBR -- I'm just gonna push it (since I need to uninstall), but if you have comments I can take them into account later :)

Lgtm just in case


Add support for all cultures corresponding to localizations we have

I looked into this and it appears that, since we must explicitly enumerate the cultures we support, we can simply enable support for all cultures that we have language translations for.
For some cultures, we localize into a specific locale - ie, pt-BR, but some are a language code - ie, fr. We can enumerate through all cultures in CultureInfo and filter out cultures whose language code we support.
Example (showing en-GB and en):

(en)

(en-GB)
Hopefully, this solves #4884 once and for all
Microsoft Reviewers: Open in CodeFlow

cc @samsp-msft @kvenkatrajan

Nice - out of curiosity, what does the full list end up being when it runs on your machine?

/azp run

Nice - out of curiosity, what does the full list end up being when it runs on your machine?

It's several hundred cultures 😄

This works on my Windows computer but is there a chance it breaks in the docker container? Maybe create an issue to test it there once the chances reach the nightly docker container.

This works on my Windows computer but is there a chance it breaks in the docker container? Maybe create an issue to test it there once the chances reach the nightly docker container.

We can create an issue, but I would not expect any break in the docker container, especially considering this works on my Mac computer as well.


Identify URL:s uniquely

When two different URL:s point to the same content, the URL:s should be considered the same.
This is so that features such as avoiding getting duplicate links and calculating statistic for links can be supported.
How can the URL be stored on the back-end in unique and identifying way?

The suggested solution is to make use of:

URL normalization
Canonical URL

Canonical URL
Two ways have been found for websites to provide the canonical URL:
Canoncial
<link rel="canonical" href="https://www.linkedin.com/?trk=">
Open Graph
Resources:

Canonical URL - RESTful API for obtain the Canonical URL for a given URL
agavish/parse-canonical-url: Parse canonical url of cross device supported web sites
canonical-url.js
The Open Graph protocol


Allow shot collision

Allow two shots to collide. This would be configurable so that for example bazooka shots will be able to collide with other shots but pistol bullets won't.

Implemented in 7dfb93f7d871369a463862b446ad618a4ef98106

Uuuu, tak to musim zkusit!:D
On Sunday, 19 June 2016, Ondřej Daněk<EMAIL_ADDRESS>wrote:

Implemented in 7dfb93f
https://github.com/odanek/duel6r/commit/7dfb93f7d871369a463862b446ad618a4ef98106
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/odanek/duel6r/issues/38#issuecomment-227012527, or mute
the thread
https://github.com/notifications/unsubscribe/AFDp3uszNYE-Xnj87zIdpykQtAYFPzp0ks5qNYoKgaJpZM4EOsk5
.

--
http://honza.kotrs.cz


Still having issues with the env vars memory leak

Hi, I read this issue which was supposedly closed by implementing a new allocator in the reactor component. Currently still even the most basic example with jco crashes:
❯ npx jco types world.wit -n gateway -o types
unreachable executed at adapter line 214: out of memory

(jco types) RuntimeError: unreachable
    at wasm://wasm/0001823a:wasm-function[39]:0xffb
    at wasm://wasm/0001823a:wasm-function[38]:0xb55
    at utf8Encode (file:///home/pimeys/code/grafbase/demo-component/ts-demo/node_modules/@bytecodealliance/jco/obj/js-component-bindgen-component.js:120:11)
    at trampoline31 (file:///home/pimeys/code/grafbase/demo-component/ts-demo/node_modules/@bytecodealliance/jco/obj/js-component-bindgen-component.js:3393:16)
    at wasm://wasm/df4ce642:wasm-function[20]:0x27c
    at wasm://wasm/0001823a:wasm-function[43]:0x1648
    at wasm://wasm/0001823a:wasm-function[44]:0x184c
    at wasm://wasm/df4ce642:wasm-function[32]:0x328
    at wasm://wasm/00826e82:wasm-function[4992]:0x1bfce0
    at wasm://wasm/00826e82:wasm-function[5005]:0x1c00f1

Now, I solved this with Rust and cargo-component by defining a custom reactor:
[package.metadata.component]
adapter = "./wasi_snapshot_preview1.reactor.wasm"

Where the reactor is downloaded from here:
https://github.com/bytecodealliance/wasmtime/releases
I'm asking is there a way to define custom adapters for jco? I can see the adapters in node_modules, but manually replacing them there feels wrong.

This should be working in the latest Jco now, please let me know if you're still having any issues at all.


Multiple "Query execution failed, ES index does not exists" errors

I'm using the provided docker-compose.yml and the trackit-ui.
I've successfully completed the setup a few days ago and AWS is creating its cost file to an S3 bucket.
Now some parts of the UI are (partialy) working, others don't work at all with errors like:

No event available (Data not available yet. Please check again in few hours.)
No data available for this timerange
Error while getting data (Data not available yet. Please check again in few hours.)
No reports available (Reports bucket not configured)

The API outputs errors like:
{"level":"error","time":"2022-01-27T10:41:42.3852915Z","message":"Failed to wrap one of the bill repositories","data":{"error":"sql: no rows in result set"}}
{"level":"warning","time":"2022-01-27T09:37:28.1269098Z","message":"Query execution failed, ES index does not exists","data":{"error":"elastic: Error 404 (Not Found): no such index [type=index_not_found_exception]","index":"000001-elasticache-reports"},"context":{"requestId":"bddc05cb-7f54-11ec-9c68-02420a135405"}}
{"level":"warning","time":"2022-01-27T09:37:28.1171287Z","message":"Query execution failed, ES index does not exists","data":{"error":"elastic: Error 404 (Not Found): no such index [type=index_not_found_exception]","index":"000001-rds-reports"},"context":{"requestId":"bddb883f-7f54-11ec-9c68-02420a135405"}}
{"level":"warning","time":"2022-01-27T09:37:28.1219073Z","message":"Query execution failed, ES index does not exists","data":{"error":"elastic: Error 404 (Not Found): no such index [type=index_not_found_exception]","index":"000001-lambda-reports"},"context":{"requestId":"bddc044e-7f54-11ec-9c68-02420a135405"}}
{"level":"warning","time":"2022-01-27T09:37:28.1232164Z","message":"Query execution failed, ES index does not exists","data":{"error":"elastic: Error 404 (Not Found): no such index [type=index_not_found_exception]","index":"000001-es-reports"},"context":{"requestId":"bddb8920-7f54-11ec-9c68-02420a135405"}}
Did i miss something during setup?
Thank you in advance
Thomas

Same problem here.
Looking at elasticsearch it looks like the indexes are not being created, but there is a request for them.
Does anyone have an idea about this?


Collect metrics on clicks to about and faq on goat counter

Add a goat counter action that can be counted for clicking the faq link and clicking the about link

#512

@paloeka metrics on who opens the faq or about page should now be available


Exposing connection information to the application.

Certain applications require knowledge of the connection and not just the HTTP message that was sent. For example inspecting a client ssl certificate or blacklisting particular ip addresses.
Adding this to the request is not desirable because:

it conflates the transport information with the HTTP protocol
The request struct sent by the client should be identical to the request struct handled by the server. Assuming both client and server use Raxx.
It is also possible to have HTTP without a connection. Posting Requests and Responses would work if anyone wanted to do that.

Option 1
Ace could have an entry in the process dictionary of the worker. The ace module could the expose several reader functions that work only in the context of a worker.
defmodule MyApp do
  def handle_request(_request, _state) do
    peer_ip = Ace.peer_ip()

    response(:ok)
  end
end

Somewhat ugly to use the process dictionary, however as all exposed functions are for derived properties the cannot be used to cause side effects.
Option 2
handle_request/2 (and all other callbacks) can have a handle_request/3 partner that takes request, channel, state with the default behaviour to fallback to the arity 2 implementation.
The downside of this approach is raxx is understanding both HTTP and some concept of the transport layer. e.g. would the channel object be an Ace.Connection or a Raxx.Connection.
Option 3
A server specific callback for connecting. e.g.
defmodule MyApp do
  use Ace.HTTP.Service, [port: 8080]

  @impl Ace.HTTP.Server
  def connect(channel, config) do # 1.
    Logger.metadata(client_ip: channel.ip)
    {:ok, config}
  end

  @impl Raxx.Server
  def handle_request(_request, _state) do
    response(:ok)
  end
end

Advantages this gives people an answer to what does init look like, it's replaced with connect.
There is a choice at 1. do we pass a connection or channel object. if channel then no error case should stop the complete connection, but the callback is executed in the same process as the handle_*. If connection then its only executed once for potentially many requests. but it would be possible to use it to stop the connection. i.e. blacklisted ips

This has been partially tackled by #96
It is not at least possible to access the socket and with that access as anything about peer ip etc

Just adding a workaround that I use in the meantime, for anyone else that might stumble upon this issue report:
  def get_ace_ip() do
    with info <- Process.get(Ace.HTTP.Channel),
         {:tcp, socket} <- info.socket,
         {:ok, {ip, _}} <- :inet.peername(socket) do
      ip
    else
      _ -> nil
    end
  end

You can run that in a request handler and you'll get either the requesting IP or nil as a result.


iPass Open Mobile crashes on macOS 10.12.5

Description of issue
After installing ipass-open-mobile the app crashes right on startup with the following error in the Application.log.
[DEBUG] [2017-06-04 16:13:58:173] : RTNSetting.xml file not present
[INFO] [2017-06-04 16:13:58:175] : UIConfig XML path got is /Applications/iPass Open Mobile.app/Contents/Frameworks/iPassCommon.framework/Resources/Directory/UIConfig.Xml
[INFO] [2017-06-04 16:13:58:175] : No UIConfig.xml Present, nothing to Parse. Branding Feature is not Enabled for this client
[DEBUG] [2017-06-04 16:13:58:177] : Check for isOMClientActivated looking for dir file at path : /Applications/iPass Open Mobile.app/Contents/Frameworks/iPassCommon.framework/Resources/Directory/
[DEBUG] [2017-06-04 16:13:58:177] : checking for email activation build.
[DEBUG] [2017-06-04 16:13:58:178] : UtilityFunctions::isEmailActivationbuild returned yes .Directory xml files are not present. So OM client is unactivated state.
[ERROR] [2017-06-04 16:13:58:178] : OM Client is not yet activated.
[DEBUG] [2017-06-04 16:13:58:184] : disableSIMPinMenuItems: Called.
[INFO] [2017-06-04 16:13:58:187] : Starting up iPass Open Mobile [Version - 2.3.1(183)]
[INFO] [2017-06-04 16:13:58:187] : OS Name: Mac OS X OS Version: Mac OS X 10.12.5
[INFO] [2017-06-04 16:13:58:188] : awakeFromNib call : wasLaunchedAsLoginItem :0
[DEBUG] [2017-06-04 16:13:58:777] : UIState Description

The app downloaded and installed from the official website works as expected after successful activation.

Both this and the newer version available from www.ipass.com crash during install.
https://github.com/caskroom/homebrew-cask/pull/35330


Scripts are currently broken

The main script in Automatic1111 repo https://github.com/AUTOMATIC1111/stable-diffusion-webui/blob/master/scripts/prompts_from_file.py is broken, and so are these scripts. Fix is in the #5

Thanks @racinmat for the PR
Sorry for the delay responding, I've been busy with other items.


Added API Reference and Glossary

Just a reference to jargon and used APIs

Wonderful!!! This is a great idea. Very useful!
Il giovedì 26 novembre 2015, Maurizio Mangione<EMAIL_ADDRESS>ha scritto:

Merged #3 https://github.com/js-girls/awesome-tasks/pull/3.
—
Reply to this email directly or view it on GitHub
https://github.com/js-girls/awesome-tasks/pull/3#event-475479359.


Support of old version Oracle

Hello @floyd871
It is good ulility for Oracle DB monitoring. But I have Oracle 11.2 and can not use this tool for monitoring. How I can rebuild your exporter to support old version of Oracle?

Install 11.2 Oracle client. And build it.
Refer to: https://golang.org/pkg/go/build/


feat: add option quietResLogger to supress response data from res.log entries

closes #235
I didn't succeeded on making the npm t running with no errors, even in the fresh new cloned repo :thinking:

I have been playing and have it successfully passing tests and blocking the response log.
however i am getting this error

actually the misunderstood the the ticket, I wanted a way to disable the request complete log. have a PR here https://github.com/pinojs/pino-http/pull/259


Remove brief description

Description of the problem
In the current doxygen documentation we see the brief description of each function in the "Public Member Functions" tab.
Description of the solution
The corresponding option in the doxygen tab is fixed, so that we only see the list and if more recommendation required one can go to the "Member Function Documentation" section.  Just like in deal.ii.

@acdaigneault This PR fixes what you pointed out earlier.


Question: How to update non-running containers?

I have volume container with data and it non-running. wathtower does't listing updates for it

Another use-case: an ephemeral container for running migrations

with the next release, you'll be able to update these using --include-stopped


Fix RPM package release and version files expansion

What
While trying to migrate from version 0.9.1 to 0.10.0 I stumbled across following error:
Traceback (most recent call last):
        File "/home/tomasz.wojno/code/rules_pkg/pkg/rpm_pfg.bzl", line 352, column 47, in _pkg_rpm_impl
                content = substitute_package_variables(ctx, "\n".join(preamble_pieces)),
        File "/home/tomasz.wojno/code/rules_pkg/pkg/private/util.bzl", line 95, column 34, in substitute_package_variables
                return attribute_value.format(**vars)
Error in format: Missing argument 'VERSION_FROM_FILE'

In #787 a helper function for expanding RPM preamble with user-defined variables was introduced. The function uses Starlark format expression to replace {var} occurrences with defined variables. However, this does not work when we pass release or version file to the build target. The rpm_pfg.bzl appends Release: ${RELEASE_FROM_FILE} and Version: ${VERSION_FROM_FILE} to preamble, which are later expanded by make_rpm.py script. Thus, those variables are failed to be expanded as they are not defined.
Changes
This pull request introduces following changes:

Avoid expanding RELEASE_FROM_FILE and VERSION_FROM_FILE by wrapping them in double curly braces. This way ${{RELEASE_FROM_FILE}} becomes expanded to ${RELEASE_FROM_FILE}, so it can be processed later by make_rpm.py
Add tests that uses version_file and release_file attributes
Fix passing changelog file to OutputGroupInfo

@aiuto Do you want to review or can I merge this PR?


Linear saturation and plotting

Lots of plotting functionality and bug fixes for phase. Examples cleaned up.

Good additions to the functionality for plotting. I have two questions:

I assume the problem with get_misfit was the square brackets making a single-element array of arrays, therefore breaking the residual'*residual calculation later in the function?
The GMR manual specifies that the phase fields are in radians (so the "data" phases are radians), and my function in ProcessingTools.jl also provides phases in radians (they just aren't restricted to the interval [-π, π) because of the unwrapping that occurs in the estimation before doing the least-squares fit). Based on this I don't think we need the deg2rad that you've added, unless there's something I've missed?

Oooh ... but the phases have a spread of a hundred degrees then!!! somewhere around -198

Yep, that's what is so "interesting" about the actual dataset


fix(kafka_and_hooks): add set async reference

:tada: This PR is included in version 1.29.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ADD a search for keyword

Description
Currently, in the Search Files extension, users can search in a specific folder by using in keyword.

But it is not that convenient with this syntax, I suggest using ~/Desktop for name, as we can search a specific folder, and use tab to go inside the folder, then type for ... for searching files in a specific folder.
Who will benefit from this feature?
Everyone
Anything else?
Or any better way to search in a specific folder.

This issue is not related to the API or extensions. Could you please use the Send Feedback command inside Raycast or use the #help or #bugs channel in our Slack Community 😊


Help to get a list of file ids from a volume

Hey. How can we get the FID(File Id) list from volumes?
We running server via:
weed server -metrics.address=pushgateway:9091 -master.dir=/tmp -volume.index=leveldb -volume.max=666 -dir=/data -garbageThreshold=0.1 -ip 'hostname -i'
Version: SeaweedFS 30GB 1.36
We assume that we have lost some of the file ids. How can we get a list of file ids exist in the volumes for compare with what we store in our database?

You can see the code of volume.fsck in weed shell. There is a gRPC API to fetch fetch file ids except the cookie part. It should be enough for you to find lost file ids.


Confusion on what should be dumped

I've been migrating my own install scripts to take advantage of brew bundle, and noticed that brew bundle dump lists more packages than brew leaves --installed-on-request.
Is this the expected behavior, and is there an option I should be using to only install the packages described by brew leaves --installed-on-request?

This is expected. You can either use brew mark to mark things you do not wish to be installed on request.


An error occurred while attempting to add additional data to the stream.

An error occurred while attempting to add additional data to the stream.
Error: expected client.AuthMode.CRAM_MD5, found null
src/client.zig:419:9: 0x1059f219d in test.client: helo (test)
try t.expectEqual(.CRAM_MD5, client.ext_auth);

Example Code:
var stream = t.Stream.init();
        stream.add("220\r\n250-\r\n250 AUTH PLAIN LOGIN CRAM-MD5\r\n");
        var client = TestClient.init(stream, config);
        defer client.deinit();

        try client.hello();
        try t.expectEqual(false, client.ext_smtp_utf8);
        try t.expectEqual(false, client.ext_8_bit_mine);
        try t.expectEqual(.CRAM_MD5, client.ext_auth);

Not sure I understand the issue.
It looks like you're trying to run the tests, and getting a failure. But I can't reproduce it. What version of Zig?
Do you have any more data?

I executed with the following command.
zig build test --summary all
OS: 20.5.0 Darwin Kernel Version 20.5.0
I think it is the issue with the test_runner.zig file. No error when I remove the main function from test_runner.zig.

If you remove main from test_runner.zig, then no tests are being run.
If you're running the tests, then this ought to be something you can debug. The trick would be to figure out if (a) findSupportedAuth is being called and, if so (b) why it's retuning null.
You can run just that test by doing:
TEST_FILTER="client: helo" zig build test

I checked "findSupportedAuth" function. But data is not utf8.
On Sun, 11 Aug 2024, 5:42 pm Karl Seguin, @.***> wrote:

If you remove main from test_runner.zig, then no tests are being run.
If you're running the tests, then this ought to be something you can
debug. The trick would be to figure out if (a) findSupportedAuth is being
called and, if so (b) why it's retuning null.
You can run just that test by doing:
TEST_FILTER="client: helo" zig build test
—
Reply to this email directly, view it on GitHub
https://github.com/karlseguin/smtp_client.zig/issues/5#issuecomment-2282739234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABT5Y5PSTKRYLTI7PJRAPBDZQ5ILDAVCNFSM6AAAAABMKIWRYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSG4ZTSMRTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I tested in Linux server. Then I can see the same error.
On Sun, 11 Aug 2024, 5:45 pm Muhammed Arshid KV, @.***>
wrote:

I checked "findSupportedAuth" function. But data is not utf8.
On Sun, 11 Aug 2024, 5:42 pm Karl Seguin, @.***>
wrote:

If you remove main from test_runner.zig, then no tests are being run.
If you're running the tests, then this ought to be something you can
debug. The trick would be to figure out if (a) findSupportedAuth is
being called and, if so (b) why it's retuning null.
You can run just that test by doing:
TEST_FILTER="client: helo" zig build test
—
Reply to this email directly, view it on GitHub
https://github.com/karlseguin/smtp_client.zig/issues/5#issuecomment-2282739234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABT5Y5PSTKRYLTI7PJRAPBDZQ5ILDAVCNFSM6AAAAABMKIWRYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSG4ZTSMRTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, I can reproduce this sometimes, looking into it

I believe this is fixed on master.

Thank you

I just noticed that you're using 0.13. It's fixed in the zig-0.13 branch too.


Added ability to write response stats to a CSV file.

This adds the -out filename flag to the slapper command. The response stats will be written to a CSV file if it is provided.
The file will have the format response code, response time in ms. E.g.
200, 5
200, 10
...
404, 5

This file can be post-processed to get response time histograms per code, percentiles, etc.
I have tested the performance of writing to a file. Writing to a file does not impede performance even at 25000 QPS agains a local lighweight server. The QPS remains approximately the same with and without -out option.

@ikruglov Would you please have a look at these changes? We use them for some time and it seems to work well. Thanks in advance!

@ikruglov I can rename -out to -output. This will make it closer to vegeta.
vegeta and slapper operate differently and it's hard to make complete 1-to-1 similarity.
Would you suggest something else on top?


collate.js missing logic to insert open and close brackets

collate.js missing logic to insert open and close brackets

Fixed!


bug: input types loose out on provided graphQL documentation

Documentation isn't copied into the blueprint for input types from configurations. For eg:
"""
Some Documentation
"""
input Foo {
  id: Int!
}

While using a configuration with an input type like the above, documentation isn't copied in the final schema.
Technical Requirements

Copy the documentation into the blueprint
Ensure integration tests are added

/bounty 10$

/attempt

cancelling my attempt.. I am busy with some other work to do.
For anyone who wants to attempt:
in from_document.rs
convert:
TypeKind::InputObject(input_object_type) => {
                to_input_object(input_object_type, &type_definition.node.directives).some()
}

to
TypeKind::InputObject(input_object_type) => {
                to_input_object(input_object_type, &type_definition.node.description, &type_definition.node.directives)
}

and the new function should look like:
fn to_input_object(
    input_object_type: InputObjectType,
    description: &Option<Positioned<String>>,
    directives: &[Positioned<ConstDirective>],
) -> Valid<config::Type, String> {
    to_input_object_fields(&input_object_type.fields)
        .fuse(Protected::from_directives(directives.iter()))
        .map(|(fields, protected)| {
            let doc = description.to_owned().map(|pos| pos.node);
            config::Type { fields, protected, doc, ..Default::default() }
        })
}

now you just need to make sure it's passed to blueprint and write the tests as described in issue.

/attempt

/attempt #1625

@tusharmath I made the PR based on the suggestions above: https://github.com/tailcallhq/tailcall/issues/1625#issuecomment-2031426868.

/attempt #1625