Collect pods in CrashLoopBack

Context
Deployment of BMRA in virtual environment.
Symptoms
Collectd pods are in crashloop after deployment.
Root cause is that a conditional flag in the collectd daemonset present in BMRA 21.09 has been removed in BMRA 22.01 (the git blame doesn't show this change). https://github.com/intel/container-experience-kits/blob/65af34f72496b53ba1d64cf7feefbbdcee1062e9/roles/collectd_install/templates/daemonset.yml#L41
Fix
Live-fixed by manual editing of the running collectd daemonset  and removing the mount, deployment-fix by restoring the flag https://github.com/intel/container-experience-kits/blob/3a27e8ad7c9ca0424192460e427cefb235d767a2/roles/collectd_install/templates/daemonset.yml#L41
and set it to false in group_vars/all.yml

@calinghe  I have tested with Profile: full_nfv, OS: Ubuntu 21.04, Machines: ICX but Deployment of BMRA in K8s mode not on VMs...
Collectd Pod is Up and Running... So on K8s mode profile We are good need to verify VMs mode to reproduce the issue on our side to properly fix it...

root@aq09-30-bc:~# kubectl get pods --all-namespaces
NAMESPACE                NAME                                                     READY   STATUS    RESTARTS      AGE
cert-manager             cert-manager-56b686b465-5lwpv                            1/1     Running   0             16m
cert-manager             cert-manager-cainjector-75c94654d-7qttl                  1/1     Running   0             16m
cert-manager             cert-manager-webhook-69bd5c9d75-gvfb8                    1/1     Running   0             16m
istio-system             istio-ingressgateway-755d6cb48f-fbrzw                    1/1     Running   0             2m9s
istio-system             istiod-cddd697cf-pxtck                                   1/1     Running   0             2m33s
kube-system              bypass-tcpip-m99df                                       1/1     Running   0             2m44s
kube-system              bypass-tcpip-pd27b                                       1/1     Running   0             2m45s
kube-system              calico-kube-controllers-684bcfdc59-fwff9                 1/1     Running   4 (17m ago)   18m
kube-system              calico-node-96rlp                                        1/1     Running   1 (17m ago)   19m
kube-system              calico-node-wkbvp                                        1/1     Running   2 (17m ago)   19m
kube-system              container-registry-dc6d78798-hs646                       2/2     Running   0             15m
kube-system              coredns-8474476ff8-qg7gk                                 1/1     Running   1 (17m ago)   18m
kube-system              coredns-8474476ff8-xt4lg                                 1/1     Running   1 (17m ago)   18m
kube-system              dns-autoscaler-5ffdc7f89d-m5nq4                          1/1     Running   1 (17m ago)   18m
kube-system              intel-qat-plugin-2wrrl                                   1/1     Running   0             9m28s
kube-system              intel-sgx-aesmd-hkgb5                                    1/1     Running   0             9m37s
kube-system              intel-sgx-plugin-j95zf                                   1/1     Running   0             9m43s
kube-system              inteldeviceplugins-controller-manager-6475d97999-v6cbk   2/2     Running   0             12m
kube-system              kube-apiserver-aq09-30-bc                                1/1     Running   0             14m
kube-system              kube-controller-manager-aq09-30-bc                       1/1     Running   3 (17m ago)   20m
kube-system              kube-multus-ds-amd64-22zfl                               1/1     Running   1 (17m ago)   18m
kube-system              kube-multus-ds-amd64-qsqbs                               1/1     Running   1 (17m ago)   18m
kube-system              kube-proxy-69bxw                                         1/1     Running   1 (17m ago)   19m
kube-system              kube-proxy-zb95q                                         1/1     Running   1 (17m ago)   19m
kube-system              kube-scheduler-aq09-30-bc                                1/1     Running   0             3m47s
kube-system              kubernetes-dashboard-548847967d-ssl29                    1/1     Running   1 (17m ago)   18m
kube-system              kubernetes-metrics-scraper-6d49f96c97-f6j7q              1/1     Running   1 (17m ago)   18m
kube-system              nginx-proxy-ar09-09-cyp                                  1/1     Running   2 (17m ago)   20m
kube-system              node-feature-discovery-controller-5bb85dfdbb-znz7v       1/1     Running   0             13m
kube-system              node-feature-discovery-worker-w5cl4                      1/1     Running   0             13m
kube-system              tas-telemetry-aware-scheduling-747664c96d-fnnf4          1/1     Running   0             3m58s
minio-operator           console-6c9557b87d-r8rzt                                 1/1     Running   0             97s
minio-operator           minio-operator-7885bb8d4-mrgqd                           1/1     Running   0             97s
minio-tenant             minio-tenant-ss-0-0                                      1/1     Running   0             49s
monitoring               collectd-l4sss                                           3/3     Running   0             2m51s
monitoring               node-exporter-7dq8s                                      2/2     Running   0             5m35s
monitoring               node-exporter-tgccv                                      2/2     Running   0             5m35s
monitoring               prometheus-k8s-0                                         4/4     Running   0             5m32s
monitoring               prometheus-operator-bf54b8f56-gfwjd                      2/2     Running   0             5m38s
sriov-network-operator   sriov-device-plugin-nsrbv                                1/1     Running   0             7m47s
sriov-network-operator   sriov-network-config-daemon-29685                        3/3     Running   0             12m
sriov-network-operator   sriov-network-operator-98db5fcbf-kg2zv                   1/1     Running   0             13m

root@aq09-30-bc:~# kubectl get node ar09-09-cyp -o json | jq '.status.allocatable'
{
  "cpu": "125",
  "ephemeral-storage": "636985485487",
  "hugepages-1Gi": "4Gi",
  "hugepages-2Mi": "256Mi",
  "intel.com/ar09_09_cyp_ens801f0_intelnics_1": "1",
  "intel.com/ar09_09_cyp_ens801f0_intelnics_2": "4",
  "intel.com/ar09_09_cyp_ens801f0_intelnics_3": "1",
  "intel.com/ar09_09_cyp_ens801f1_intelnics_1": "4",
  "memory": "518556492Ki",
  "pods": "110",
  "qat.intel.com/generic": "32",
  "sgx.intel.com/enclave": "20",
  "sgx.intel.com/epc": "4261412864",
  "sgx.intel.com/provision": "20"
}

root@aq09-30-bc:~# kubectl describe pods collectd-l4sss -n monitoring
Name:         collectd-l4sss
Namespace:    monitoring
Priority:     0
Node:         ar09-09-cyp/<IP_ADDRESS>
Start Time:   Wed, 02 Mar 2022 04:46:05 -0800
Labels:       app=collectd
              controller-revision-hash=788c5d94b4
              pod-template-generation=1
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  DaemonSet/collectd
Containers:
  collectd:
    Container ID:  docker://0236a8742f06fd7680b7f921650967e50e1bad98c799bf3045ed04e5672105e3
    Image:         opnfv/barometer-collectd@sha256:a7cea43d9d2f67c38fbf0407786edbe660ee9072945f7bb272b55fd255e8eaca
    Image ID:      docker-pullable://opnfv/barometer-collectd@sha256:a7cea43d9d2f67c38fbf0407786edbe660ee9072945f7bb272b55fd255e8eaca
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/bash
      -c
    Args:
      yum -y remove kernel-devel kernel-headers ; /run_collectd.sh
    State:          Running
      Started:      Wed, 02 Mar 2022 04:46:36 -0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /mnt/proc from proc (ro)
      /opt/collectd/etc/ from files (ro)
      /sys/devices/system/cpu from cpufreq (ro)
      /sys/devices/virtual/powercap/intel-rapl/ from pkgpower (ro)
      /sys/kernel/mm/hugepages from hugepages (ro)
      /var/run/.client from clientsocketpath (rw)
      /var/run/collectd/ from unixsocksocket (rw)
      /var/run/dpdk/rte/telemetry from dpdksocketpath (rw)
      /var/run/openvswitch/ from ovs (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-j787p (ro)
  collectd-exporter:
    Container ID:  docker://6dbc55b97c76f116dc2990e124783ee63e31b596e4b942a3e5027dc1c8f159f4
    Image:         prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654
    Image ID:      docker-pullable://prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654
    Port:          9103/TCP
    Host Port:     9103/TCP
    Args:
      --web.listen-address=<IP_ADDRESS>:9103
      --collectd.listen-address=<IP_ADDRESS>:25826
    State:          Running
      Started:      Wed, 02 Mar 2022 04:46:43 -0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-j787p (ro)
  rbac-proxy:
    Container ID:  docker://3a4e9d3ff30cd9fe6e2135c4feecac9caaf1f4a146ecb39b58812deda87e8f10
    Image:         quay.io/coreos/kube-rbac-proxy:v0.5.0
    Image ID:      docker-pullable://gcr.io/kubebuilder/kube-rbac-proxy@sha256:e10d1d982dd653db74ca87a1d1ad017bc5ef1aeb651bdea089debf16485b080b
    Port:          9104/TCP
    Host Port:     9104/TCP
    Args:
      --tls-cert-file=/etc/ssl/rbac-proxy/rbac-proxy-ssl.cert
      --tls-private-key-file=/etc/ssl/rbac-proxy/rbac-proxy-ssl.key
      --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
      --secure-listen-address=<IP_ADDRESS>:9104
      --upstream=http://<IP_ADDRESS>:9103/
    State:          Running
      Started:      Wed, 02 Mar 2022 04:46:44 -0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /etc/ssl/rbac-proxy/ from ssl (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-j787p (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  ssl:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  rbac-proxy-ssl
    Optional:    false
  files:
    Type:          HostPath (bare host directory volume)
    Path:          /opt/collect.d
    HostPathType:
  proc:
    Type:          HostPath (bare host directory volume)
    Path:          /proc
    HostPathType:
  ovs:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/local/var/run/openvswitch/
    HostPathType:
  clientsocketpath:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/.client
    HostPathType:
  dpdksocketpath:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/dpdk/rte/telemetry
    HostPathType:
  pkgpower:
    Type:          HostPath (bare host directory volume)
    Path:          /sys/devices/virtual/powercap/intel-rapl/
    HostPathType:
  hugepages:
    Type:          HostPath (bare host directory volume)
    Path:          /sys/kernel/mm/hugepages
    HostPathType:
  cpufreq:
    Type:          HostPath (bare host directory volume)
    Path:          /sys/devices/system/cpu
    HostPathType:
  unixsocksocket:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/collectd/
    HostPathType:
  kube-api-access-j787p:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Scheduled  7m56s  default-scheduler  Successfully assigned monitoring/collectd-l4sss to ar09-09-cyp
  Normal  Pulling    7m55s  kubelet            Pulling image "opnfv/barometer-collectd@sha256:a7cea43d9d2f67c38fbf0407786edbe660ee9072945f7bb272b55fd255e8eaca"
  Normal  Pulled     7m26s  kubelet            Successfully pulled image "opnfv/barometer-collectd@sha256:a7cea43d9d2f67c38fbf0407786edbe660ee9072945f7bb272b55fd255e8eaca" in 29.110409864s
  Normal  Created    7m25s  kubelet            Created container collectd
  Normal  Started    7m25s  kubelet            Started container collectd
  Normal  Pulling    7m25s  kubelet            Pulling image "prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654"
  Normal  Pulled     7m18s  kubelet            Successfully pulled image "prom/collectd-exporter@sha256:73fbda4d24421bff3b741c27efc36f1b6fbe7c57c378d56d4ff78101cd556654" in 6.638644283s
  Normal  Created    7m18s  kubelet            Created container collectd-exporter
  Normal  Started    7m18s  kubelet            Started container collectd-exporter
  Normal  Pulling    7m18s  kubelet            Pulling image "quay.io/coreos/kube-rbac-proxy:v0.5.0"
  Normal  Pulled     7m17s  kubelet            Successfully pulled image "quay.io/coreos/kube-rbac-proxy:v0.5.0" in 745.286868ms
  Normal  Created    7m17s  kubelet            Created container rbac-proxy
  Normal  Started    7m17s  kubelet            Started container rbac-proxy

In fact the initial deployment is done on VMs in Openstack (not the libvirt VMs on Intel BareMetal), so our nodes don't have Intel drivers activated that's why we need to disable Collectd specific plug-ins with the flag that existed in 21.09.


FIX issue #198: wrong linker used

according to https://stackoverflow.com/questions/52646860 the -gcc-toolchain
flag is now required starting with ndk-r18

Closing this pull request as it was fixed by #223.

Closing this pull request as it was fixed by #223.


"Pull request commented on" service hook event not documented

The event for "Pull request commented on" is not documented.

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

ID: 6033d681-9093-547c-20fd-b31183c2bb33
Version Independent ID: 0d92e3f0-7fb4-57e5-d913-f305a055a819
Content: Service hooks event reference - Azure DevOps
Content Source: docs/service-hooks/events.md
Product: devops
Technology: devops-collab
GitHub Login: @aaronhallberg
Microsoft Alias: aaronha

Any chance someone will document this service hook? It's been a very long time without documentation to be found anywhere.

We've moved this issue to our internal tracking system as we transition to a new feedback system.


Marquee not respecting custom.css

I was messing with the useMarquee option, and changing this css class:
.CX3 .event .headline .title.marquee .marqueeText {
  display: inline-block;
  white-space: nowrap;
  overflow: unset;
  animation: marquee calc(var(--marqueeLength) / 10) linear 2s infinite;
  min-width: 0;
}

Specifically, changing the duration of the animation property calc(var(--marqueeLength) / 10), does not appear to work in custom.css. Making the same change directly in MMM-CalendarExt3.css does work.
Changing the keyframes in custom.css does work.

Well, in my test, it works. Exactly what do you want to do with that changing? Please describe more details, such as AS-IS and TO-BE.
I added this rule in the custom.css.
.CX3 .event .headline .title.marquee .marqueeText {
  text-decoration: underline; /* To check whether this rule applied */
  animation: marquee calc(var(--marqueeLength) / 100) linear 2s infinite; /* Changed from 10 to 100 */
}

This code makes the animation 10x faster. (and underlines)

You're right, it's working. My code was wrong. My fault, not a bug. The part where you turn off everything else to isolate the issue... I was not careful enough.
If you're curious, I'm doing a constant infinite scroll thing like a news crawler, with a duplicated copy of the content so that the beginning of the entry can already be scrolling in as the end is still scrolling out.


How to shorten controller instantiation time?

There is such a description in the manual:
The application creates a controller instance to handle the request.
According to my understanding, these repeated steps are executed for every request.
Can these be avoided?
I tried to join the cache, but failed.Is there any solution?

This is how PHP works. What is that you are trying to achieve exactly?

https://github.com/charlesportwoodii/yii2-app-basic-psr7


invalid data source name and Undefined variable dsn

Hi,
I just update to the latest version and got a pdo error : invalid data source name
and a Undefined variable: dsn on line 134
I'm using mysql  5.6
do you know what's wrong ?
Thanks

Same issue, any help ?


mcast was removed by mistake. restoring it back.

mcast was already approved: https://github.com/JetBrains/swot/blob/064ea0dfb4bc7e52fe5aa1d937e753f6d75153e8/lib/domains/mt/edu/mcast.txt but was removed in this commit: https://github.com/JetBrains/swot/commit/9aec568d53b8b5d43e3e40d4da049009ee1f574b

@roderickvella I am sorry, the domain mcast.edu.mt is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Pack at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).

@philipto Thanks for your quick reply. I am a lecturer at MCAST IICT. I don't know who abused this domain, but what I can say is that we have several students that use this service, example with Unreal and Unity.
We are a legitimate institution, as you can see here: https://iict.mcast.edu.mt/
Thanks for your consideration.


[2.7] Support CATTLE_WHITELIST_ENVVARS in RKE2 provisioning code

This allows passing down environment variables to rancher machine during provisioning.
Issue: #39377
Problem

This is an alternative solution to #39375 because there were concerns regarding security. We need to be able to enable debug logging in RKE2.
Solution

Instead of passing the --debug flag to rancher machine, we allow RKE2 provisioning to pass down to rancher machine whitelisted environments variables, one of which can be MACHINE_DEBUG, which solves the needs of the original issue reporter.
Testing

Engineering Testing
Manual Testing

Start rancher with MACHINE_DEBUG=true and CATTLE_WHITELIST_ENVVARS=NO_PROXY,HTTP_PROXY,HTTPS_PROXY,MACHINE_DEBUG env vars.
Create an RKE2 cluster
Make sure rancher machine debug logs are displayed

Automated Testing

QA Testing Considerations

Regressions Considerations

@sbstp Can you also handle the update on the Doc side?
Yeah I'd like to. I'll ask for some pointers tomorrow to do it.

I pushed a new commit that tries to have more code re-use, let me know what you think


Flatten class generation

The issue: with nested class generation approach the nested class name can be too long, for example
UpdateCheckoutShippingAddressQuery.Data.CheckoutShippingAddressUpdate.Checkout.LineItemConnection.LineItemEdge.LineItem.Variant
Proposal: change the way how classes to be generated, so instead of fully nested classes make the structure more flat, for example:
class UpdateCheckoutShippingAddressQuery.Data {
  class CheckoutShippingAddressUpdate {...}
  class Checkout {...}
  class LineItemConnection {...}
  class LineItemEdge {...}
  class LineItem {...}
  class Variant {...}
}

This will reduce the nested levels in class names:
UpdateCheckoutShippingAddressQuery.Data.CheckoutShippingAddressUpdate
UpdateCheckoutShippingAddressQuery.Data.Checkout
UpdateCheckoutShippingAddressQuery.Data.LineItemConnection
UpdateCheckoutShippingAddressQuery.Data.LineItemEdge
UpdateCheckoutShippingAddressQuery.Data.LineItem
UpdateCheckoutShippingAddressQuery.Data.Variant

@BenSchwab  @marwanad @digitalbuddha any comments here?


Home: Reorder Groups

As a user, I would like to re-order my home page from that home screen without needing to go into settings.

done


Upgrade Python code to Python 3

Apply most of the suggestions of pyupgrade.
The Python code is documented to  support Python >= 3.7 in README.rst:

pyEDFlib can be used with Python >=3.7.

looking good, thanks!
could you merge the changes I made in #206 (now in master) and check if the test suit then runs?

thanks!


Replace EGI with EOSC marketplace for DIRAC

Summary

Related issue :

Actually, https://docs.egi.eu/users/compute/orchestration/workload-manager/#the-egi-workload-manager-web-portal also needs updating. Not sure where to start :)

For the access request, shouldn't we align with, or redirect to, https://docs.egi.eu/users/getting-started/#pilot-your-application ?
Or do we have a specific interest in going via the EOSC Marketplace? Like maybe liaising with the Workload Manager team to have them configure the access?

I believe that's the case since I was member of vo.access.egi.eu and I had to open a GGUS ticket to get my access configured. So either the EOSC Marketplace is a trigger (which would also help us accounting interest for the service) or we need another trigger to configure access to DIRAC after enrolling into vo.access.egi.eu.


Remove Boto Dependency

Remove boto3 dependency. Downloading through Python requests library instead. The download first streams the model into a .part file so that it doesn't have to be stored in memory.
Checklist

[x] pytest passes

This has been merged in the GitLab repo and synced to this repo


Implement a drag and drop team builder interface for AGS

The current rewrite of AutoGen studio has focused on representing teams declaratively in JSON.
It would be great to add a flexible GUI to let users modify team configurations. A team is made of up compontents - agents (models, tools, etc), termination conditions etc.

[ ] Visualize team config (what are the agents, what are the tools, models etc)
[ ] Add/remove components (agents, teams, models) either directly in JSON or via UI
[ ] Validate / test components .

Component Serialization Decisions

The team (which defines the main workflow/orchestration behaviors) is the primary component in AGS.
There are two potential approaches for storing declarative team (and other component) specifications in the same internal ags database:
Fully Linked Components
In this approach, each component (model, agent, team, memory etc) maintains relationships at the database level. For example, an Agent table row would have foreign keys to its models and tools. Fetching a team's complete configuration requires traversing these relationships to assemble the full picture.
Pros:

Components stay synchronized - when a model or tool is updated, all agents using it automatically see the change
Referential integrity is enforced by the database
Storage efficiency since components are stored once and referenced many times

Cons:

Complex fetching logic requiring multiple joins to assemble full configurations
Updates must cascade through relationships
Schema changes needed to support new component types (a deployment challenge each time AGS users update their app)
Harder to version control since components can change underneath a team
More complex deployment as schema updates needed for new features

Independent Components
This approach serializes the complete configuration of each component. Rather than maintaining relationships, a team's configuration includes the full definition of all its agents, including their tools, models, and other settings. When you store a team using the weather_api tool, that tool's entire configuration is part of the team definition.
Pros:

Configurations are self-contained and portable
Simple updates - just modify a single record, test it and reuse elsewhere (helps with trust)
Easy versioning since each team captures a complete snapshot
Schema flexibility - new component types don't require database changes
Simpler deployment with less database coordination

Cons:

Storage duplication when components are reused across teams (not really an issue, configurations are very light).
No automatic propagation of component updates (we can mitigate this by providing UX that helps users easily validate/test all components to build trust)
UX needs to clearly communicate the independence of configurations
Potential confusion if users expect linked behavior (UX can help here)

Key Decision Factors
The choice depends heavily on use case. For experimentation and reproducibility, Independent Components shines - each team captures a precise snapshot of its configuration at a point in time. For production systems prioritizing consistency, Fully Linked Components ensures changes propagate automatically.
A hybrid approach storing both relationships and snapshots is possible but adds complexity. The benefits of Independent Components - reproducibility, schema flexibility, and configuration portability - likely outweigh the storage overhead from duplication for most use cases.
Happy to get thoughts here.
@husseinmozannar , @ekzhu , @JingyaChen

Thanks @victordibia for the analysis.
Thoughts:

Storage cost decreases faster than compute, so storage overhead is not an issue.
Important to associate class version number (e.g., a hash code) with each serialized component, and ability to retrieve the provider for each version. When an irreversible breaking change in the underlying agent/tool/team class happens in the future we can use the version number to resolve or migrate the stored component to the latest version.
A provider class maps (serialized component, version) -> (component). On store, always migrate to the latest version.
Independent component with loose, un-linked, key-value like schema is good to start. Otherwise, the overhead of schema migration will be burdensome when code changes frequently.

I think we also want to separate these two concepts for component:

Component definition: a JSON serialized config that can be used to create a new component instance.
Component state: a JSON serialized state that can be used to bring a component back to an existing state.

Separating these two allows us to ease the breaking changes: if a change impacts just the definition, we don't need to worry about also updating the state, and vice versa. This also allows us to run analytics on the state without the analytic code to reconstruct the components, as some components can be heavy and doing so consumes a lot of compute.

More regarding the state.
I think in the beginning we might want to consider supporting only "ephemeral" components: that is their states exists in memory only. We still store their definitions. So, user can retrieve their designed components, but every time they do the components are all new.
We can just have an export function to export all the state in JSON, if user want to see. But no import to start.

Good ideas and points @ekzhu

Agreed that we should start with independent components each with a version number. Current spec has version numbers
Agree that state is different from definition/spec. The current work in AGS has focused on definition/spec. #4222 will look at how best to persist exchanged messages. If we do this right, the structure of state should not be far from the actual messages exchanged. This should allow us some lattitude to "restore" agent state by loading messages they sent previously?


Adding new section in documentation for troubleshooting permissions

This patch is inspired by keycastr/keycastr#222 documentation around
troubleshooting KeyCastr when it doesn't seem to be working.
I modified it a little bit to fit the writing style of the rest of the
documentation. I hope this helps folks troubleshoot issues that are unrelated
to bugs that arise in KeyCastr.

Thanks again!


Flagwaver is laggy and barely works.

That flag disappears and is laggy.

Thanks for your feedback. I'd need some more information to know if there is anything that can be done about it, like what browser and device are you using, and what kind of images are you using?


upgrade jpeg-js dependency

What's Changing and Why
This PR relates to the new release of jpeg-js (more info here). Some jpeg files were not properly handled by jpeg-js therefore are refused by jimp. Objective is to upgrade the library so that these files are accepted on jimp.
What else might be affected
Yarn lockfile seemed to be out-of-date, so adding this dependency updated the lockfile for all missing packages. It should not be a problem. All tests pass.
Tasks

[ ] Add tests Unnecessary
[ ] Update Documentation Unnecessary
[ ] Update jimp.d.ts Unnecessary
[ ] Add SemVer Label

:rocket: PR was released in v0.16.1 :rocket:


[BUG] Fallback to documentation homepage when clicking the breadcrumb in documentation.

The bug is found on the documentation page of breadcrumbs, all the sub-topics display the same behavior. It takes the user back to the homepage when clicking on any breadcrumb there. The issue is happening on all the breadcrumbs of "Limit the number of breadcrumbs", "Truncate each breadcrumb" and "Responsive".
To Reproduce
Steps to reproduce the behavior:

Go to limit the number of breadcrumbs.
Click on any breadcrumb.
It will take you back to the homepage.

Host/Environment:

OS: Windows 11, Ubuntu 22.04
Chrome, Firefox Browser - 110

@abhirajshourya - this behavior actually reflects what is intended with the breadcrumb (that the breadcrumbs would point to different URLs, including the homepage of the documentation). As we are currently making many changes to this forked doc site, we have simple generic URLs right now to demonstrate that the breadcrumbs are clickable. While we work through continued edits to the documentation, the content and the URLs may become more specific.
TLDR; Closing as this is expected behavior.


Adopt bitbucket-branch-source-plugin

Link to GitHub repository
https://github.com/jenkinsci/bitbucket-branch-source-plugin
When modifying release permission
List the GitHub usernames of the users who should have commit permissions below:

@abayer
@amuniz
@bitwiseman
@carroll
@dnusbaum
@rsandell
@jtaboada
@lifeofguenter
@nfalco79

This is needed in order to cut releases of the plugin or component.
If you are modifying the release permission of your plugin or component, fill out the following checklist:

### Release permission checklist (for submitters)
- [x] The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to [accounts.jenkins.io](https://accounts.jenkins.io/).
- [x] All users added have logged in to [Artifactory](https://repo.jenkins-ci.org/) and [Jira](https://issues.jenkins.io/) once.
- [x] I have mentioned an [existing team member](https://github.com/orgs/jenkinsci/teams) of the plugin or component team to approve this request.

When enabling automated releases (cd: true)
Follow the documentation to ensure, your pull request is set up properly. Don't merge it yet.
In case of changes requested by the hosting team, an open PR facilitates future reviews, without derailing work across multiple PRs.
Link to the PR enabling CD in your plugin

### CD checklist (for submitters)
- [ ] I have provided a link to the pull request in my plugin, which enables CD according to the documentation.

### Reviewer checklist
- [ ] Check that the `$pluginId Developers` team has `Admin` permissions while granting the access.
- [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
- [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently `@Wadeck`) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it.

See https://groups.google.com/g/jenkinsci-dev/c/OPcbarV9qoQ/m/dOfnWgHrAgAJ
Thanks for the adoption request, welcome aboard!

Thank you for helping with maintaining the plugin!


Why is it still "Preview"?

I'm new to VS Code and OmniSharp. I saw there is a red "Preview" tag in VS Code and the description "Welcome to the C# extension for Visual Studio Code! This preview provides the following features inside VS Code:" ...
May I ask a dummy question: if the version is already 1.14, why is it still preview?
Regards.

Sorry for the delay in responding. We talked about this internally and we decided that there is no reason this extension should still be considered a "preview". For our next release (1.15), we will remove the preview branding.


[backport/v1.19] repo: Dev 1.19.5

set VERSION -> dev
cp current.rst -> v1.19.4.rst
merge v1.19.2.rst -> v1.19.3.rst (due to failed build)

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

checking that the merge 1.19.2 -> 1.19.3 is correct - afaict yes - 25dbd02cddb95673de48312616391d14c883fd65
ill update envoy main with the missing changelog

/docs

/retest

This PR essentially again opens the release/v1.19 branch up to backporting.
It will also allow us to test the branch (as a dev branch)


[Q&A] Need a help for match two above url with one Route

Sorry, my english is not good enough.
Version
4.1.1
I want to match two url with one route and one component.
just like below:

http://host:port/test/orders/id-1
http://host:port/test/products/id-1

How can I write the path for Route?

Thanks.

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux. Thanks!


[RESOLVED] High ICMP ping response time

Problem started at 02:10:29 on 2023.08.14
Problem name: High ICMP ping response time
Host: HP_iLO
Severity: Warning
Operational data: Value: 182ms
Original problem ID: 36116
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23268&eventid=36116

Problem has been resolved in 1m 0s at 02:11:29 on 2023.08.14
Problem name: High ICMP ping response time
Host: HP_iLO
Severity: Warning
Original problem ID: 36116


Add CrossQ

Description

Implementing https://openreview.net/forum?id=PczQtTsTIX
on top of #21
Discussion in #36
perf report:
https://wandb.ai/openrlbenchmark/sbx/reports/CrossQ-SBX-Perf-Report--Vmlldzo3MzQxOTAw
Motivation and Context

[ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)

Checklist:

[ ] I've read the CONTRIBUTION guide (required)
[ ] I have updated the changelog accordingly (required).
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly (required for a bug fix or a new feature).
[ ] I have updated the documentation accordingly.
[ ] I have reformatted the code using make format (required)
[ ] I have checked the codestyle using make check-codestyle and make lint (required)
[ ] I have ensured make pytest and make type both pass. (required)
[ ] I have checked that the documentation builds using make doc (required)

Note: You can run most of the checks using make commit-checks.
Note: we are using a maximum length of 127 characters per line

@danielpalen after reading the paper, I'm wondering if you have the learning curves for relu6?
or is it similar to SAC - TN + tanh?

@danielpalen Some early results of DroQ + CrossQ (only 2 random seeds on 3 pybullet envs, need more runs): https://wandb.ai/openrlbenchmark/sbx/reports/DroQ-CrossQ-SBX-Perf-Report--Vmlldzo3MzcxNDUy
I also quickly checked the warmup steps and could see an impact on AntBulletEnv-v0 only when it was too small.

@danielpalen after reading the paper, I'm wondering if you have the learning curves for relu6? or is it similar to SAC - TN + tanh?

I quickly checked and it looked pretty similar.

I have also played around with REDQ/DroQ + CrossQ on MuJoCo but from what I remember, the results were not really consistent, sometimes better, sometimes worse.

So far, it always improved the results in my case (need more seeds to confirm, I have tried on different pybullet and mujoco envs), or at least to quickly get "good enough" solution (using up to 2x less samples than CrossQ).
One last point in case you missed it (because from https://github.com/araffin/sbx/pull/36#issuecomment-2027392759):
@danielpalen  would you be interested in providing a PyTorch implementation for SB3 contrib? (https://github.com/Stable-Baselines-Team/stable-baselines3-contrib)

One last point in case you missed it (because from #36 (comment)): @danielpalen would you be interested in providing a PyTorch implementation for SB3 contrib? (https://github.com/Stable-Baselines-Team/stable-baselines3-contrib)

Yes, absolutely :) I put it on my todo. But I think I won't be able to get on that right away at the moment.


add option to disable inline code block copying. Set to enabled by default

this seems to be working well, the only thing I couldnt figure out how to do so far is to fire the observers when they are first created. But as soon as you click on any node in the graph they will fire and update. I can't seem to find good documentation on how the observers work or how to solve this problem. I tried firing a change event, but that didn't seem to do it.
It looks like my editor has also changed some code styles - semicolons, reformatting, etc. If you want me to match your code style exactly we could work on getting a prettier config in that will format things the way you like.

This looks great, I had trouble getting the observer to fire without selecting a node as well so no worries.


I18n command fails on WordPress.org GlotPress

Describe the bug
When running composer -- pup i18n it build the URL incorrectly for WP.org glotpress.
To Reproduce
https://github.com/bordoni/fakerpress/actions/runs/8857143849/job/24324261209#step:6:16
Expected behavior
Used this i18n configuration:
    "i18n": {
        "path": "languages",
        "formats": ["mo"],
        "slug": "fakerpress",
        "textdomain": "fakerpress",
        "url": "https://translate.wordpress.org/api/projects/wp-plugins/fakerpress/stable"
    },

Additional context
Here is where I think the problem currently is:
https://github.com/stellarwp/pup/blob/main/src/Commands/I18n.php#L90

With a diff configuration we can get the correct URL to be requested, but it still throws a 403.
Configuration that yield the correct results:
    "i18n": {
        "path": "languages",
        "formats": ["mo"],
        "slug": "wp-plugins/fakerpress/stable",
        "textdomain": "fakerpress",
        "url": "https://translate.wordpress.org"
    },

Fetching language files for fakerpress from https://translate.wordpress.org
Client error: `GET https://translate.wordpress.org/api/projects/wp-plugins/fakerpress/stable` resulted in a `403 Forbidden` response:

<title>403 Forbidden</title>

403 Forbidden

nginx</c (truncated...)


Connections Not Closed when No Client Passed to civis.ml.ModelPipeline

I've got some code like:
for i in range(500):
    model = civis.ml.ModelPipeline(clf)
    model.train()

Running this on my system eventually results in errors due to running out of file handles (my system's default limit is 1024.)
Each call to model.train() results in three connections to the civis platform which are never closed, consuming file handles (you can observe this using lsof -i and strace on linux.)
This similar bit of code results in connections being closed and no file handle leaks:
for i in range(500):
    client = civis.APIClient()
    model = civis.ml.ModelPipeline(clf, client=client)
    model.train()

I have vague suspicions about the first case creating its own APIClient object since one was not supplied, and its getting garbage-collected somehow prevents connections from being closed.

@waltaskew , there's another potential cause. If the ModelPipeline creates its own APIClient object, it uses the resources="all" parameter. This lets it subscribe to PubNub notifications, which are still in internal beta. Every time you call model.train, you subscribe to another notifications channel. I would expect that this opens at least one file handle.
The code samples you provide aren't runnable as they are -- in your actual code, are you storing the output of model.train anywhere? If the CivisFuture goes out of scope, ideally it would be garbage collected and the PubNub connection closed. Maybe that's not happening.

@waltaskew , there's another potential cause. If the ModelPipeline creates its own APIClient object, it uses the resources="all" parameter. This lets it subscribe to PubNub notifications, which are still in internal beta. Every time you call model.train, you subscribe to another notifications channel. I would expect that this opens at least one file handle.

I was seeing three separate network connections for each model.train, which I imagine included the connections for creating and running the custom script.

The code samples you provide aren't runnable as they are -- in your actual code, are you storing the output of model.train anywhere? If the CivisFuture goes out of scope, ideally it would be garbage collected and the PubNub connection closed. Maybe that's not happening.

I'm holding onto the output of model.train but don't need to try and get the result of the future to see file handle leeks.
Here's a full example:
import os
import subprocess
import string

import civis.ml
import numpy
import pandas
import sklearn.linear_model

data = pandas.DataFrame(
    numpy.random.rand(400, 12),
    columns=list(string.ascii_letters[:12]),
)
file_id = civis.ml._model._stash_local_dataframe(data)

lsof_cmd = ('lsof', '-i', '-a', '-p', '%d' % os.getpid())

def print_open_connections():
    try:
        out = subprocess.check_output(lsof_cmd)
        print(out.decode('ascii'))
    except subprocess.CalledProcessError as err:
        if err.returncode == 1:
            print('no open connections')
        else:
            raise

trainings = []
for i in range(5):
    model = civis.ml.ModelPipeline(
        model=sklearn.linear_model.LogisticRegression(),
        dependent_variable=data.columns[-1],
    )
    print('about to train model %d' % i)
    print_open_connections()
    print('')

    trainings.append(model.train(file_id=file_id))

    print('started training model %d' % i)
    print_open_connections()
    print('')

with output on my linux box like:
about to train model 0
no open connections

started training model 0
COMMAND  PID      USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python3 7624 waltaskew    4u  IPv4 265214      0t0  UDP <IP_ADDRESS>:49861-><IP_ADDRESS>:domain
python3 7624 waltaskew    5u  IPv4 266158      0t0  TCP <IP_ADDRESS>:53856->ec2-34-231-234-145.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    6u  IPv4 265215      0t0  UDP <IP_ADDRESS>:47403-><IP_ADDRESS>:domain

about to train model 1
COMMAND  PID      USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python3 7624 waltaskew    4u  IPv4 266253      0t0  TCP <IP_ADDRESS>:60050->ec2-54-241-191-234.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    5u  IPv4 266158      0t0  TCP <IP_ADDRESS>:53856->ec2-34-231-234-145.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    6u  IPv4 266256      0t0  TCP <IP_ADDRESS>:33790->ec2-54-241-191-243.us-west-1.compute.amazonaws.com:https (ESTABLISHED)

started training model 1
COMMAND  PID      USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python3 7624 waltaskew    4u  IPv4 266253      0t0  TCP <IP_ADDRESS>:60050->ec2-54-241-191-234.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    5u  IPv4 266158      0t0  TCP <IP_ADDRESS>:53856->ec2-34-231-234-145.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    6u  IPv4 266256      0t0  TCP <IP_ADDRESS>:33790->ec2-54-241-191-243.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    7u  IPv4 266362      0t0  UDP <IP_ADDRESS>:43976-><IP_ADDRESS>:domain
python3 7624 waltaskew    8u  IPv4 266210      0t0  TCP <IP_ADDRESS>:48754->ec2-52-70-212-109.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    9u  IPv4 266363      0t0  UDP <IP_ADDRESS>:40100-><IP_ADDRESS>:domain

about to train model 2
COMMAND  PID      USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python3 7624 waltaskew    4u  IPv4 266253      0t0  TCP <IP_ADDRESS>:60050->ec2-54-241-191-234.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    5u  IPv4 266158      0t0  TCP <IP_ADDRESS>:53856->ec2-34-231-234-145.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    6u  IPv4 266256      0t0  TCP <IP_ADDRESS>:33790->ec2-54-241-191-243.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    7u  IPv4 266380      0t0  TCP <IP_ADDRESS>:48226->ec2-52-9-63-129.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    8u  IPv4 266210      0t0  TCP <IP_ADDRESS>:48754->ec2-52-70-212-109.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    9u  IPv4 266383      0t0  TCP <IP_ADDRESS>:35204->ec2-54-241-191-232.us-west-1.compute.amazonaws.com:https (ESTABLISHED)

started training model 2
COMMAND  PID      USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python3 7624 waltaskew    4u  IPv4 266253      0t0  TCP <IP_ADDRESS>:60050->ec2-54-241-191-234.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    5u  IPv4 266158      0t0  TCP <IP_ADDRESS>:53856->ec2-34-231-234-145.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    6u  IPv4 266256      0t0  TCP <IP_ADDRESS>:33790->ec2-54-241-191-243.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    7u  IPv4 266380      0t0  TCP <IP_ADDRESS>:48226->ec2-52-9-63-129.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    8u  IPv4 266210      0t0  TCP <IP_ADDRESS>:48754->ec2-52-70-212-109.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    9u  IPv4 266383      0t0  TCP <IP_ADDRESS>:35204->ec2-54-241-191-232.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   10u  IPv4 266419      0t0  UDP <IP_ADDRESS>:46760-><IP_ADDRESS>:domain
python3 7624 waltaskew   11u  IPv4 267421      0t0  TCP <IP_ADDRESS>:49036->ec2-34-206-6-184.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   12u  IPv4 266420      0t0  UDP <IP_ADDRESS>:50333-><IP_ADDRESS>:domain

about to train model 3
COMMAND  PID      USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python3 7624 waltaskew    4u  IPv4 266253      0t0  TCP <IP_ADDRESS>:60050->ec2-54-241-191-234.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    5u  IPv4 266158      0t0  TCP <IP_ADDRESS>:53856->ec2-34-231-234-145.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    6u  IPv4 266256      0t0  TCP <IP_ADDRESS>:33790->ec2-54-241-191-243.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    7u  IPv4 266380      0t0  TCP <IP_ADDRESS>:48226->ec2-52-9-63-129.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    8u  IPv4 266210      0t0  TCP <IP_ADDRESS>:48754->ec2-52-70-212-109.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    9u  IPv4 266383      0t0  TCP <IP_ADDRESS>:35204->ec2-54-241-191-232.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   10u  IPv4 266443      0t0  TCP <IP_ADDRESS>:52028->ec2-52-9-63-131.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   11u  IPv4 267421      0t0  TCP <IP_ADDRESS>:49036->ec2-34-206-6-184.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   12u  IPv4 266440      0t0  TCP <IP_ADDRESS>:59806->ec2-54-219-189-245.us-west-1.compute.amazonaws.com:https (ESTABLISHED)

/home/waltaskew/src/gfk_multi_output/venv/lib/python3.6/site-packages/sklearn/base.py:311: UserWarning: Trying to unpickle estimator LogisticRegression from version 0.18.1 when using version 0.19.1. This might lead to breaking code or invalid results. Use at your own risk.
   This might lead to breaking code or invalid results. Use at your own risk.
  UserWarning)
started training model 4
COMMAND  PID      USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python3 7624 waltaskew    4u  IPv4 266253      0t0  TCP <IP_ADDRESS>:60050->ec2-54-241-191-234.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    5u  IPv4 266158      0t0  TCP <IP_ADDRESS>:53856->ec2-34-231-234-145.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    6u  IPv4 266256      0t0  TCP <IP_ADDRESS>:33790->ec2-54-241-191-243.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    7u  IPv4 266380      0t0  TCP <IP_ADDRESS>:48226->ec2-52-9-63-129.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    8u  IPv4 266210      0t0  TCP <IP_ADDRESS>:48754->ec2-52-70-212-109.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew    9u  IPv4 266383      0t0  TCP <IP_ADDRESS>:35204->ec2-54-241-191-232.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   10u  IPv4 266443      0t0  TCP <IP_ADDRESS>:52028->ec2-52-9-63-131.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   11u  IPv4 267421      0t0  TCP <IP_ADDRESS>:49036->ec2-34-206-6-184.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   12u  IPv4 266440      0t0  TCP <IP_ADDRESS>:59806->ec2-54-219-189-245.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   13u  IPv4 266492      0t0  TCP <IP_ADDRESS>:59822->ec2-54-219-189-245.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   14u  IPv4 267515      0t0  TCP <IP_ADDRESS>:52044->ec2-52-9-63-131.us-west-1.compute.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   15u  IPv4 266520      0t0  UDP <IP_ADDRESS>:50313-><IP_ADDRESS>:domain
python3 7624 waltaskew   16u  IPv4 267486      0t0  TCP <IP_ADDRESS>:53884->ec2-34-231-234-145.compute-1.amazonaws.com:https (ESTABLISHED)
python3 7624 waltaskew   17u  IPv4 266521      0t0  UDP <IP_ADDRESS>:59484-><IP_ADDRESS>:domain
python3 7624 waltaskew   19u  IPv4 267559      0t0  TCP <IP_ADDRESS>:49064->ec2-34-206-6-184.compute-1.amazonaws.com:https (ESTABLISHED)

Eventually the connections fall into CLOSE_WAIT status indicating that the server has hung up the connection, but even after long amounts of time the client doesn't appear to attempt to close the connections to reap the file handle of the CLOSE_WAIT connections.

I wouldn't expect that you'd need to request the result of the model training to see an open connection. We subscribe to the PubNub channel immediately, so that we don't miss a completion message.
But it's also true that every new APIClient opens its own requests.Session and never explicitly closes it. You're keeping the reference to those client objects around when you store the output of model.train. I'm not sure why we need 3 open files. I'm also surprised that all of them are pointing to EC2. Shouldn't there be one per model which connects to PubNub?
Is there a reason to keep the Session to the Civis API permanently open? We could instead re-open it every time we want to make a request.

I've verified that I see an increase of 3 open file handles with each new model in the above code. If I pass a pre-constructed client object with resources="base", there's no increase in open file handles. If I pass a pre-constructed client object with resources="all", I see an increase of 2 open file handles for each new model. So it looks like our PubNub connection uses 2 file handles.


When selecting a bucket from the list and clicking on the (+) to upload a file, set the same bucket in the Upload new file menu!

Done in branch develop :)

ok cool!, closing.


discourse: 2.9.0.beta4 -> 2.9.0.beta8

Description of changes
Update Discourse to the latest beta and update all plugins.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

I tried upgrading one of my servers to this and the page shows a constant loading animation with these errors in the browser console:

Here's a probably relevant post: https://meta.discourse.org/t/regression-on-could-not-find-module-handlebars-imported-from-discourse-common-lib-raw-handlebars/225572

Looks like we were working on the update simultaneosly. Your PR is cleaner but I found the reason for the handlebars error Ryan mentioned :) The problem is indeed the missing dist directory which is used by Discourse code to find the dependency "chunks" that have to be included in the page. Unfortunately, the "file not found" exception gets ignored and nothing is rendered, which leads to the missing handlebars module.

Here's the fix: https://github.com/dpausp/nixpkgs/commit/7cf064e1ef594d5c016c73c0801d7439b2de9f91 @ryantm @talyz

Seems to be working well for me with @dpausp's patch on top.

Oh, great! Maybe we should just include the whole javascripts folder to be on the safe side? That way we catch any future generated artifacts as well. I'll push a fix-up that does this, which seems to work just fine to me.

Your updates work for me @talyz. Meanwhile they're now on 2.9.0.beta9.

Okay, I've updated to 2.9.0.beta9 and squashed the change now.

The latest thing still works for me!


docs(kong.conf.default): ssl_ciphers description (#6035)

Summary
The description of ssl_ciphers was confusing if you were using DHE ciphers because you'd also have to use another parameter. This fixes the description.
This is a cherry-pick of Kong/kong-ee#6035
Checklist

[ ] The Pull Request has tests
[ ] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

kong.conf.default update

@locao could you please open the PR in OSS first and then cherry-pick it to EE in the future? Doing it in the reversed order will cause issues for the CE2EE merge. Thanks


Mutual TLS with bun router

💡 Adding Mutual TLS to router.
📄  In microservices environment we are communicating with Mutual TLS between two services. And this is right now a cumbersome process doing it with http server. If there is a better way to do this with bun router that would be great.
🚀 A way to do Mutual TLS
    // Create a CA certificate pool and add cert.pem to it
    //root_ca.crt  server.crt  server.key
    caCert, err := ioutil.ReadFile(cfg.RootCert)
    if err != nil {
            log.Fatal(err)
    }
    caCertPool := x509.NewCertPool()
    caCertPool.AppendCertsFromPEM(caCert)

    // Create the TLS Config with the CA pool and enable Client certificate validation
    tlsConfig := &tls.Config{
            ClientCAs:  caCertPool,
            ClientAuth: tls.RequireAndVerifyClientCert,
    }
    tlsConfig.BuildNameToCertificate()

    // Create a Server instance to listen on port 8443 with the TLS config
    server := &http.Server{
            Addr:      ":8443",
            TLSConfig: tlsConfig,
    }

    // Listen to HTTPS connections with the server certificate and wait
    log.Fatal(server.ListenAndServeTLS(cfg.MyCert, cfg.MyKey))

How this can be done with bun router

This is how i am doing it in the http.Server
// Create a CA certificate pool and add cert.pem to it
//root_ca.crt  server.crt  server.key
caCert, err := ioutil.ReadFile(cfg.RootCert)
if err != nil {
log.Fatal(err)
}
caCertPool := x509.NewCertPool()
caCertPool.AppendCertsFromPEM(caCert)
    // Create the TLS Config with the CA pool and enable Client certificate validation
    tlsConfig := &tls.Config{
            ClientCAs:  caCertPool,
            ClientAuth: tls.RequireAndVerifyClientCert,
    }
    tlsConfig.BuildNameToCertificate()

    // Create a Server instance to listen on port 8443 with the TLS config
    server := &http.Server{
            Addr:      ":8443",
            TLSConfig: tlsConfig,
    }

    // Listen to HTTPS connections with the server certificate and wait
    log.Fatal(server.ListenAndServeTLS(cfg.MyCert, cfg.MyKey))

How can this be done with bun router

The same, just set the handler to Bun router:
    server := &http.Server{
            Addr:      ":8443",
            TLSConfig: tlsConfig,
            Handler: router,
    }


[ios] Update UI Thread image and fix typo

Whoops! This was PR'ed against live. It should be to master.


[DRAFT] modify  QuantizeParams and QBuffer to implement quant/dequant op along with unit test

add groupSize member in struct QuantizeParams for group wise quantization
revert src/fastertransfomer/kernels/quantization_tensor.h/cu to commit 8c993e73b6b8d3aa29d0d548ca92e5e76e60394e
move rocm quant related kernels into src/fastertransfomer/kenrels/rocm folder
add int4x2 quant/dequant unit test
fix rocm gpu mem allocate bug

Qwen2-7B-Instruct-GPTQ-Int4 test result:
["Hello! I'm Qwen, a state-of-the-art language model developed by Alibaba Cloud. My main purpose is to generate human-like text and assist with various types of questions and tasks. How can I assist you today?"]
{
    "id": "chat-",
    "object": "chat.completion",
    "created":<PHONE_NUMBER>,
    "model": "AsyncModel",
    "choices": [
        {
            "index": 0,
            "message": {
                "role": "assistant",
                "content": "我是阿里云开发的一款超大规模语言模型，我叫通义千问。作为一个助手，我的目标是帮助用户获得准确、有用的信息，解决他们的问题或完成任务。我可以回答各种问题、提供代码实现、构思创作、甚至是进行闲聊。如果你有任何需要帮助的地方，尽管告诉我，我会尽力提供支持。",
                "function_call": null,
                "tool_calls": null
            },
            "finish_reason": "stop"
        }
    ],
    "usage": {
        "prompt_tokens": 22,
        "total_tokens": 91,
        "completion_tokens": 69
    },
    "debug_info": null,
    "aux_info": null
}
[FT][WARNING][RANK 0][139788025853504][24-08-07 11:06:30] max_top_k: 1, max_top_p: 1.000000
[FT][WARNING][RANK 0][139788025853504][24-08-07 11:06:30] topk_ws_size: 608320, topp_ws_size: 2433280
[FT][WARNING][RANK 0][139788025853504][24-08-07 11:06:30] max_top_k: 1, max_top_p: 1.000000
[FT][WARNING][RANK 0][139788025853504][24-08-07 11:06:30] topk_ws_size: 608320, topp_ws_size: 2433280
[FT][INFO][RANK 0][139830970417600][24-08-07 11:06:30] destory normal engine
[FT][INFO][RANK 0][139830970417600][24-08-07 11:06:30] stop normal engine
[FT][INFO][RANK 0][139830970417600][24-08-07 11:06:30] stop FIFOScheduler
[FT][INFO][RANK 0][139830970417600][24-08-07 11:06:30] stop FIFOScheduler
[FT][INFO][RANK 0][139830970417600][24-08-07 11:06:30] destory FIFOScheduler
2024-08-07 11:06:31.766029 INFO kmonitor.MetricsSystem : remove source name [_1_reporter], current source size [1]
2024-08-07 11:06:31.766129 INFO kmonitor.KMonitor : release kmonitor [_1_reporter].
================================================================================
Target //example:test up-to-date:
  bazel-bin/example/test
INFO: Elapsed time: 64.608s, Critical Path: 63.52s
INFO: 2 processes: 2 local.
INFO: Build completed successfully, 2 total actions
//example:test

rocm gemm_op_test result:
[----------] Global test environment tear-down
[==========] 6 tests from 1 test suite ran. (8194 ms total)
[  PASSED  ] 6 tests.
================================================================================
Target //src/fastertransformer/devices/rocm_impl/test:gemm_op_test up-to-date:
  bazel-bin/src/fastertransformer/devices/rocm_impl/test/gemm_op_test
INFO: Elapsed time: 67.519s, Critical Path: 66.29s
INFO: 12 processes: 5 internal, 7 local.
INFO: Build completed successfully, 12 total actions
//src/fastertransformer/devices/rocm_impl/test:gemm_op_test              PASSED in 20.1s

Executed 1 out of 1 test: 1 test passes.


phpstorm

Hi, I used to use atom and used this theme for a long time. I'd like to use it on PhpStorm, would you be willing to port it?
Thanks.

@hilyin Appreciate the kind words. I'm not using / familiar enough with PhpStorm, but if anyone in the community wants to attempt a port I'd be honoured :)


Where is the open project that is claimed in your paper?

As the title.

Source code has been released!


Fixed #40

I made the basic fixes, but it looks like now the docker environment is not starting the frontend environment.
In the future, if the project is stable, it can be further optimized. Now the docker image file will be larger.

Superseded by other PRs


How to run binoc ?

Hello,
I'm trying to run binoc directly on a local shpc registry from the command-line, but I can't find how to control the path to that registry. I'm trying something like this, as in README.md
$ BINOC_REPO_PATH=$PWD BINOC_PARSERS_LOADED=shpc BINOC_GIT_TOKEN=rEdAcTeD ./binoc

 ____  _
| __ )(_)_ __   ___   ___
|  _ \| | '_ \ / _ \ / __|
| |_) | | | | | (_) | (__
|____/|_|_| |_|\___/ \___|
Application Version: develop

[Parsing Container Blueprints]
[Checking Containers for Updates]

[Scan Results]
0     Packages Parsed
0     Packages Updated
0     Packages Skipped

But, as you can see it cannot find any update.
The registry is a copy of https://github.com/singularityhub/singularity-hpc/tree/main/registry to $PWD/registry, where I have downgraded redis:
diff --git a/registry/redis/container.yaml b/registry/redis/container.yaml
index bbbb234..ddcd24e 100644
--- a/registry/redis/container.yaml
+++ b/registry/redis/container.yaml
@@ -4,14 +4,12 @@ maintainer: '@vsoch'
 description: Redis is an open-source, networked, in-memory, key-value data store with
   optional durability.
 latest:
-  7.0-rc: sha256:939f6b81ae093c4c58c3913d1c8b4d3e53910b7da6bd96e67a10136e037ad985
+  6.2.5: sha256:c98f0230b5f1831f4f5dd764c4ea8ef11d3e3a1a3593278eb952373d97c82b27
 tags:
   6.2.3-alpine: sha256:f8f0e809a4281714c33edf86f6da6cc2d4058c8549e44d8c83303c28b3123072
   6.2.4-alpine: sha256:0039796b887fd30e460353f14e46ba1004152aa97f5f59094cc21eac445fc89b
   6.2.5: sha256:c98f0230b5f1831f4f5dd764c4ea8ef11d3e3a1a3593278eb952373d97c82b27
-  6.2.6: sha256:0d9c9aed1eb385336db0bc9b976b6b49774aee3d2b9c2788a0d0d9e239986cb3
-  7.0-rc: sha256:939f6b81ae093c4c58c3913d1c8b4d3e53910b7da6bd96e67a10136e037ad985
-  latest: sha256:0d9c9aed1eb385336db0bc9b976b6b49774aee3d2b9c2788a0d0d9e239986cb3
+  latest: sha256:c98f0230b5f1831f4f5dd764c4ea8ef11d3e3a1a3593278eb952373d97c82b27
 aliases:
   redis-benchmark: /usr/local/bin/redis-benchmark
   redis-check-aof: /usr/local/bin/redis-check-aof

I've tried a few things for BINOC_REPO_PATH:

omitting it: very quickly exits with no update found
setting it to /: fails with Error. repository does not exist
setting it to $PWD: runs for a while, then exits with no update found
setting it to $PWD/registry: fails with Error. repository does not exist

Any tip would be appreciated 🙏🏼
Regards,
Matthieu

OK, I think I'm getting there. It looks like binoc only works 1) if the current branch is named main, and 2) on container.yaml files that are present in the last commit, excluding the ones that have been locally deleted.

Hey @muffato! Do you have a copy of binoc in your SHPC repository? I'd try running it with something like this from the Binoc repository. It's admittedly been a couple of months since I've dived into this code but I'll check this out on a local shpc repository later today after a couple of meetings and see if I run into a similar error.
$ BINOC_REPO_PATH=/path/to/shpc BINOC_PARSERS_LOADED=shpc BINOC_GIT_TOKEN=rEdAcTeD go run binoc.go

Hi @alecbcs . Right: I had copied the registry to a local checkout of binoc, so that I could debug binoc at the same time. As far as I can see, go run binoc.go works the same as ./binoc, and the constraints are on the repo:

BINOC_REPO_PATH must be a git repository. I guess that's because binoc is meant to be creating a pull-request.
the git repository has to be on the main branch, otherwise binoc fails with "reference not found"

In one occasion, binoc failed with "worktree contains unstaged changes", but I haven't been able to reproduce that.
Once I comply with those rules, I can run binoc fine.

We should fix this. Although Binoc was originally developed as a GitHub action if you're not generating a pull request with it we shouldn't require BINOC_REPO_PATH to be a git repository.

I managed to run binoc, so I'll close this issue, and open a new open about binoc requiring the directory to be a git checkout


SnippetTest.java:69-71: Enable PlaceTest and UnplaceTest...

The puzzle 526-1315d399 from #526 has to be resolved:
https://github.com/cqfn/eo/blob/b2b8dac2c97071920f068a74aba30ff575bf7f23/eo-maven-plugin/src/test/java/org/eolang/maven/SnippetTest.java#L69-L71
The puzzle was created by @baudoliver7 on 28-Dec-21.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@yegor256 please, assign


community[minor]: Add support for Tencent Hunyuan Chat Model and Embeddings

Tencent provides its Hunyuan Chat model and Embeddings through Tencent cloud.
Langchain-python has implemented it, as described in doc.
This PR adds support in langchain-js for the Hunyuan Chat Model (doc), and Embedding (doc).

Looks solid overall, see comments about crypto usage.

Thank you!


Need Help on resolving the error - Storage account name and account key are mandatory when not using development storage

while i was trying to store the user utterances in a table(app insights azure), i am getting the below error. I have followed the below links for implementation.
https://docs.microsoft.com/en-us/azure/bot-service/nodejs/bot-builder-nodejs-state-azure-table-storage?view=azure-bot-service-3.0
https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-tutorial-function-appinsights
Here is my code snippet and error screen shot.

Settings for the storage account are also given in App Settings.

Please help me resolving this error. Thanks in advance!

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

ID: bebdde16-1bbd-541e-6c65-58ca3f3f71e6
Version Independent ID: 8a82d32a-382a-6325-062f-19cb96208c10
Content: Add LUIS data to Application Insights using Node.js - Azure
Content Source: articles/cognitive-services/LUIS/luis-tutorial-function-appinsights.md
Service: cognitive-services
GitHub Login: @v-geberr
Microsoft Alias: v-geberr

@AdityaJasti Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@AdityaJasti It looks like you are missing the third parameter on the call to create a new AzureTableClient. Please check that all 3 parameters are in your code.

#please-close


Update sdran helm chart version

LGTM. Needs to updated in aether-onramp repo too (vars/main-sdran.yml).


Pie chart initial animation with 0 value in series

Codepen
https://codepen.io/anon/pen/oKzJgR
Explanation
When the series includes the value 0, the animation will run for about 1/5th of its duration, then snap to its finished state.
The animation works fine if the series does not include any 0s, and I expect it to work the same even if it does include 0s.

Just bumped into this as well… @AlexanderArvidsson Do you perhaps have any workarounds until this is fixed?

@mikerockett My only workaround is using another graphing package at the moment 🤷

@AlexanderArvidsson I see – well I've landed up turning off animations for these charts, not the end of the world for now. 🙂

Fixed it.
The next minor release will be released soon with this fix.


The JSONEncoder encode Dictionary to Array?

struct Name: RawRepresentable, Codable, Hashable {
    typealias RawValue = String
    var rawValue: String
    init(rawValue: String) {
        self.rawValue = rawValue
    }
    var hashValue: Int {
        return rawValue.hashValue
    }
    init(from decoder: Decoder) throws {
        let container = try decoder.singleValueContainer()
        let rawValue = try container.decode(String.self)
        self.init(rawValue: rawValue)
    }

    func encode(to encoder: Encoder) throws {
        var container = encoder.singleValueContainer()
        try container.encode(rawValue)
    }
}

let value0 = Name.init(rawValue: "Name")
let encoder0 = JSONEncoder()
if let data = try? encoder0.encode(value0) {
    if let string = String(data: data, encoding: .utf8) {
        print(string) // ✅ prints: "Name"
    }
}

let value1 = [Name.init(rawValue: "Name"): "John"]
let encoder1 = JSONEncoder()
if let data = try? encoder1.encode(value1) {
    if let string = String(data: data, encoding: .utf8) {
        print(string) // ❌ prints: ["Name","John"]
    }
}

let value2 = ["Name": Name.init(rawValue: "John")]
let encoder2 = JSONEncoder()
if let data = try? encoder2.encode(value2) {
    if let string = String(data: data, encoding: .utf8) {
        print(string) // ✅ prints: {"Name":"John"}
    }
}

Environment

Swift compiler version info
Xcode version info Xcode 14.2 Build version 14C18 -->
Deployment target: iOS
swift-driver version: 1.62.15 Apple Swift version 5.7.2 (swiftlang-<IP_ADDRESS>.5 clang-14<IP_ADDRESS>)

cc @parkera

We don’t have enough info when encoding the ”bad” example to know that Name will be encoded as a single value container with just a String and therefore is suitable for use as a key in a JSON dictionary (which is of course required to be a String). Therefore Dictionary goes into the fallback path of encoding itself as an Array instead.

If a dictionary's key type was defined in OC like this:
typedef NSString *SomeKeyName NS_EXTENSIBLE_STRING_ENUM;

In swift, the key type was converted to struct, which lead to the JSONEncoder doesn't work as expected.
The JSONSerialization may work, but it needs all the value types implemented NSCoding protocol at first.
Is there any way to resolve this problem without changing many codes.
@parkera

I had the same problem, my goal was to use a string enum as a key so that I could better process the results, but failed due to the lack of this feature. I believe When the Decoder thinks it's a Dictionary, it should be able to get the target type, and instead of decoding the key with String, it should decode it with Dictionary.Key, like the Dictionary.Value

Isn't this a duplicate of SR-7788?
I think SE-0320 is a workaround for this.

@YOCKOW I just fixed this in swift-foundation(FoundationPreview), but it looks like I should move it to swift-corelibs-foundation?

SE-0320 is the workaround, adding CodingKeyRepresentable is working for me.


Test our error handling results in CI errors

Our perf tests were throwing errors, but the CI returned pass/green statuses. Verify a Write-Error produces a CI failure.

Well, this simple script returned 1 and caused the GitHub actions step to fail. Very strange.


Remove synonym "Gus deficiency" from mucopolysaccharidosis type 7 (MONDO_0009662)

@bioportal_agent requests:

remove synonym "Gus deficiency" from MONDO_0009662, comments: I don't think this is correct

This request comes from BioPortal user: jvendetti

remove synonym "Gus deficiency" from MONDO:0009662
Comments: I don't think this is correct

This change request comes from BioPortal user: palexander
Issue auto-generated by @kgcl-change-request

remove synonym "Gus deficiency" from MONDO:0009662
Comment: I don't think this is correct!
This request comes from BioPortal user: Sansa Stark


Create a PR test that actually runs jupyter

To prevent stuff like this from happening: #11035, we should make at least one of our functional tests run with real jupyter.
Some of the simpler ones should be robust enough to run on every submission.

Plan is to enable Smoke tests as mandatory job in PR pipeline.
Will do this after release.

Linux Smoke is now required on PRs. Validated.


Add created_at typings to Application resource

Change-type: minor
Signed-off-by: Stevche Radevski<EMAIL_ADDRESS>
Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

@balena-ci retest

@balena-ci retest


Typo - Update neuralnetworktutorial.md

Typo - changed "on" to "one" in "(MLP) with on or more"

Thanks @eddiepierce


No way to create BCEdDSAPublicKey from raw key data

If you only have the public key value and curve name which is the case when using https://tools.ietf.org/html/rfc8037 it is unclear to me how to proceed.  None of the "spec" methods seem to fit and the BC tests do not include such transformations either.
{
  "kty":"OKP",
  "crv":"Ed25519",
  "x":"11qYAYKxCrfVS_7TyWQHOg7hcvPapiMlrwIaaPcHURo"
}

Try this:
private static X509EncodedKeySpec createEdDSAPublicKeySpec(byte[] rawPoint)
throws IOException
{
AlgorithmIdentifier algId;
if (rawPoint.length == 32)
{
algId = new AlgorithmIdentifier(EdECObjectIdentifiers.id_Ed25519);
}
else
{
algId = new AlgorithmIdentifier(EdECObjectIdentifiers.id_Ed448);
}
    return new X509EncodedKeySpec(new SubjectPublicKeyInfo(algId, rawPoint).getEncoded());
}

Thanx!


Add ts-jest and a couple base tests

relates https://github.com/oleeskild/obsidian-digital-garden/issues/289
Adds jest and a couple sanity tests, which hopefully document some utils and allow fixing functionality safely.
Hopefully the addition of testing (and example of unit tests) will make future testing easier :)
PS: I figured it would be better to make a tiny contained PR instead of going to fix the issue in the same one, correct me if you prefer bigger PRs!

Once this is in I have a PR which will close a couple issues relating to rewrite rules https://github.com/julesvirallinen/obsidian-digital-garden/pull/1

I've had a todo item saying "Add unit tests to digital garden" in todoist for well over a year now, and never got around to do it, so this is a very welcome PR 😅
Thanks a lot for taking the time to setup the scaffolding for writing tests. As you mention, this should make it more frictionless to add tests going forward.
I agree with you on the way you split up the PR. Sorry for the slow response, I haven't been able to prioritize this project in the last weeks/months. If everything goes according to plan I should have more time available for maintaining it going forward. 🤞


Updated Tempo2 gps corrections to be compatible with recent versions of tempo2

The GPS correction in tempo2 was a bit strange, and recent (since about start of 2024) tempo2 has used a new system derived from this repository, but made compatible with tempo2.
gps2utc.clk used to be a correction that did not have a consistent definition of GPS time. This is because BIPM published two different corrections between their realisation of UTC and GPS, labeled as C0 and C0' in CircularT. Furthermore, gps2utc.clk was produced from old circularT files that had an error that was later corrected by BIPM.
The difference is that there is GPS time as directly read from the satellites (which I call GPST) and a time derived from this which better approximates UTC(UNSO), which I call (GPS(UNSO)).
Previously the IPTA clock repo tried to recreate the gps2utc.clk by switching between C0 and C0' at an arbitrary epoch. However, this is not extremely satisfactory.
Instead tempo2 has abandoned gps2utc.clk and instead we have two clock files:
gpst2utc.clk (which used C0 to go from GPST to UTC) and gps_unso2utc.clk (which uses C0' to go from GPS(UNSO) to UTC)
Note here, UTC means UTC as defined by BIPM, because that's what tempo2 implies right now.
For backwards compatibility there are two additional clock files, gps2gpst.clk and gps2gps_unso.clk, which have zero correction and fixed date ranges that basically replicate the old gps2utc behavior.
Ideally clock correction files from obervatories will change to specify which GPS time they really mean. Likely this is GPS(UNSO), but it may depend on exactly what is measured by the GPS reciever.
There is also a minor 'compatibility' fix - bipm.py previously produced duplicated entries a the start and end of circularT blocks. I think this can cause problems in tempo2, so I have updated it to avoid duplicated date entries.
If this change is merged, then tempo2 and the IPTA clock repo should agree and we can make tempo2 copy the files in from this repo (currently they are generated by a modified version of this code), and eliminate one duplication.

I can't merge this, but I'll look anyway.  Probably we don't need to include the updated log files in the PR?


Trigger update

Hi,
How can I subscribe just to the trigger order updates on the websocket? I found the enum but I can't see where is implemented a part from submitting a new trigger order.
Like socket.SubscribeToOrderUpdatesAsync()
But with trigger orders only.
Or if the same can retrieve also a property that if it's a trigger order the trigger order type is evaluated.
Thank you

Well sure, but the API doesn't offer that, so I can't provide that in the library


Validating Certificate

Hello and thanks for the client.
I'm writing to ask how you can validate the asics archive or the token once after creating it on windows.
In particular I use www.freetsa.org.
Thank you in advance,
Pier

ASiC-S container can be validated for example by our online service ZEP.DISIG.SK. However TSA at freetsa.org does not seem to be qualified service operated under the terms of eIDAS regulation so the validation result for its certificate will most likely be "indeterminate".


CrossFacebookClient.Current.Logout() is not working.

Bug Information
Version Number of Plugin: 2.2.1
Tested On: Xiaomi Redmi Mi 9T
Version of VS: VS 2019
Version of Xamarin: 4
Steps to reproduce the Behavior

Log in using any login method
Logout using CrossFacebookClient.Current.Logout() method.

Expected Behavior
The logged Facebook account will be logged out and I will be able to log in again - the Facebook dialog will pop-up and I can confirm - if I want to "Continue as" .
Actual Behavior
The logged Facebook account remained and logging in won't open the Facebook login dialog, it will automatically login to the supposed-to-be-logged-out account.

Any news ion this issue? Is there a workarround or bug fix coming?

I've been looking at this for some days now but I can't find the problem. Somebody has shown any progress?

Any news about this bug? I'm also facing the same issue :(

I have the same, any updates when it will be resolved? @rdelrosario

Hi any news on this issue?


Sort out 10Gbps/m4 compatibility

Appears that when instances launch on 10Gbps-enabled nodes, networking isn't getting properly set up. Fix for EL6 doesn't seem to translate to EL7

Issue was in AMI setting. Fixed.


Testlinter

Remove testlinter/whitelist.go and introduce a whitelist comment pattern which could be used to opt out lint rules for a test.

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

Needs approval from an approver in each of these files:

tests/OWNERS

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

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4f22e3db25197df83a8eabb4bd93c7321e83e3c3
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4f22e3db25197df83a8eabb4bd93c7321e83e3c3
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
4f22e3db25197df83a8eabb4bd93c7321e83e3c3
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

This PR is WIP, and it is close to review. I will send it out for another round of review this week.


Bluetooth:RFCOMM: Fix length errors when payload exceeds 127

hdr->length is the length of the payload, it should be
buf->len - sizeof(*hdr) - 1 or buf->len - (sizeof(*hdr) + 1)
Signed-off-by: ZhongYao Luo<EMAIL_ADDRESS>PS:  When using zephry to implement the iap2 protocol, when iOS sends RequestAuthenticationCertificate, zephry responds to AuthenticationCertificate, iOS will no longer send new data, and AuthenticationCertificate exceeds 127. After using this patch, it works fine.

Fix looks ok, but could you please fix the typo in the commit message. It's RFCOMM and not RFOCOMM 😄

Also (minor): there should be a space character after Bluetooth:

Is this a fix for https://github.com/zephyrproject-rtos/zephyr/issues/18386?

@LuoZhongYao I see you've fixed the PR title, but you also have to fix the commit message

@LuoZhongYao I see you've fixed the PR title, but you also have to fix the commit message

sorry, Was using a non-work computer

Is this a fix for #18386?

I did n’t verify it because your project testing is really slow

I did n’t verify it because your project testing is really slow

You mean coverity? We can leave that issue open. Johan mentioned that he saw several things that looked suspicious. So if you are familiar with the RFCOMM spec you might want to have a look for more issues, as there is not really anybody maintaining the BR/EDR part of zephyr at the moment.

I did n’t verify it because your project testing is really slow

You mean coverity? We can leave that issue open. Johan mentioned that he saw several things that looked suspicious. So if you are familiar with the RFCOMM spec you might want to have a look for more issues, as there is not really anybody maintaining the BR/EDR part of zephyr at the moment.

OK


[Rest Server] Infer TaskStatus after App completed  #2635

#2635

Coverage decreased (-0.002%) to 53.317% when pulling e85705a831c8b8650483cdf461f2d56e2cc1aa98 on qinsu/errorspec/taskstate into eaab2906c52e1e94904bd614bd4b2da22aa338db on errorspec.


Support %(app_label)s and %(class)s in related_name

I am trying to add TaggableManager to an Abstract model.  I've added a related name like related_name='%(app_label)s_%(class)s_tags'.  This gives an error like The name '%(app_label)s_%(class)s_tags' is invalid related_name for field with HINT: Related name must be a valid Python identifier or end with a '+'
Per the Django docs, this is a valid form of related_name.
Shouldn't TaggableManager be performing the string format operation?  At a glance this seems like it would work just fine with generic object tagging

OK so I narrowed this down to the fact that TaggableManager is using a totally custom contribute_to_class. In Django's RelatedField.contribute_to_class method we have
            if related_name:
                related_name = related_name % {
                    'class': cls.__name__.lower(),
                    'model_name': cls._meta.model_name.lower(),
                    'app_label': cls._meta.app_label.lower()
                }
                self.remote_field.related_name = related_name

Ideally I would like for us to just find a way to use contribute_to_class directly, but even a patch that would just copy over this behavior could be pulled into the project.

Labelling a bug since we are a RelatedField sublcass, so should behave as such when possible.

Haven't used this past an initial investigation but it does seem to be the solution:
class AbstractTaggableManager(TaggableManager):
    def contribute_to_class(self, cls, name):
        self.opts = cls._meta

        if not cls._meta.abstract:
            if self.remote_field.related_name:
                related_name = self.remote_field.related_name
            else:
                related_name = self.opts.default_related_name
            if related_name:
                related_name = related_name % {
                    "class": cls.__name__.lower(),
                    "model_name": cls._meta.model_name.lower(),
                    "app_label": cls._meta.app_label.lower(),
                }
                self.remote_field.related_name = related_name

        super().contribute_to_class(cls, name)

As far as testing goes - would it be good enough to simply define an abstract and concrete implementation in the models?  System checks seem to throw an error with a related name like related_name="%(app_label)s_%(model_name)s_%(class)s_tags" without this quickfix

@thenewguy if you want to take this on, I think the straightforward way would be to just edit one of the existing test models with a related name like what you are discussing, then we can add a quick test/modify an existing one to check that the related name accessor works.
For example one of the models in this file, and editing a test.
And of course for actually getting the bug fixed, just reworking the TaggableManager contribute_to_class function!
Would you be interested in making a PR with your changes? Even just having that as a starting point would be helpful. And if you're not interested, I can look at making a PR instead. But I think you understand the problem well


Auto import not working

Auto import seems to not be working
To reproduce
Use a variable/function from another module, select auto-import from the dropdown menu.
Expected behavior
The selected symbol should be added to the current module's imports
Screenshots

Environment
Nova version: 10.6
Extension version: 2.5.0
macOS version: 13.1
NodeJS information:
    node version: 18.12.0
    npm version: 8.19.2
    installation method: nvm

I verified this is working today. If you can find more details, let me know.

Not working for me either.

@franzwarning I tested this with a project without baseUrl and it doesn't work either


Setting the maximum comment column width

I opened a feature request issue for this but decided to implement it.
I've added a command line and config file argument for to set the maximum column width for submission comments. By default this is set to 80.
This makes reading comments much smoother when using a full screen terminal.
It's only my second contribution to someone else's code, so feedback on code quality is welcome :)

Hi Michael,
Implemented those changes! I hope it's all good.
Thanks for rtv by the way, now I can reddit at work ;)

Glad you're using it, if you find any other issue feel free to post them!


Clearing RS.Event_MouseTerrainHit is not qualified by event type [Unity 5.6.1xf1]

I'm using Unity 5.6.1xf1.
OnSceneGUI() sets RS.Editor_MouseTerrainHit based on control or shift being pressed while the current event is MouseMove or MouseDrag.
if (current.control && (Event.current.type == EventType.MouseMove || Event.current.type == EventType.MouseDrag)) {
	Ray worldRay = HandleUtility.GUIPointToWorldRay (Event.current.mousePosition);
	RaycastHit hitInfo;
	if (Physics.Raycast (worldRay, out hitInfo)) {
		if (hitInfo.collider.transform.GetComponent<Terrain> () != null || hitInfo.collider.transform.name.ToLower ().Contains ("terrain")) {
			RS.Editor_MousePos = hitInfo.point;
			RS.Editor_MouseTerrainHit = true;

Then the following code block clears RS.Editor_MouseTerrainHit if neither control nor shift are pressed without be qualified against the event type. When layout and repaint events occur, RS.Editor_MouseTerrainHit is cleared and it is impossible to place nodes as a result.
The following change allows me to place nodes:
- if(!current.control && !current.shift){
+ if (!current.control && !current.shift && (Event.current.type == EventType.MouseMove || Event.current.type == EventType.MouseDrag)) {

#17 Merged in.