Monarch Projection Step for rectangular blocks and where the number of blocks != sqrt(input dimension)

Hi, I had a question regarding the projection step from dense -> monarch butterfly matrices, in the general case, where we have rectangular or nblocks != sqrt(m) of the matrix, as I'm having trouble finding the code for this and extending existing implementations for this case.
I found multiple projection files/functions: blockdiag_butterfly_projection.py and blockdiag_butterfly_einsum.py.
As an example, if I use code roughly as follows:
from src.models.layers.blockdiag_butterfly_multiply import blockdiag_butterfly_multiply

x = np.eye(8)
nblocks = 2
bfly_dim = 4

w1_bfly = np.random.normal((nblocks, bfly_dim, bfly_dim))
w2_bfly = np.random.normal((nblocks, bfly_dim, bfly_dim))

bfly_matrix = blockdiag_butterfly_multiply(x, w1_bfly, w2_bfly)

print(bfly_matrix.shape)

The resulting shape of the output will be 8x8, which is essentially the full matrix used for transformation.
However, if I use the projection function (which is meant for square matrices) from blockdiag_butterfly_projection.py to try and recover the butterfly matrices from this matrix, I run into the issue that it expects the matrix to decompose as follows M_permuted_batched = rearrange(M, '(p k) (r s) -> k r p s', k=sizes[1], r=sizes[0]), while in our case: r = 4 and s = 4, making it incompatible with the matrix dimensions.
Meanwhile, the einsum functions in blockdiag_butterfly_einsum.py gave different results from the original blockdiag_butterfly_multiply (comparing the forward multiplication step not the projection step).  (see this colab)
In the paper, I did see the original derivation for algorithm 1:
 but I was unclear on how to actually perform the decomposition step when we can't decompose the tensor into an m x m x m x m shape.

Maybe the function you're looking for is block_diag_butterfly_project_einsum_rank.
(you can see our tests here that the projection recovers the original factors) https://github.com/HazyResearch/fly/blob/cd624cffeffa7d1579336d26a776405bf0867f36/tests/ops/test_blockdiag_butterfly_einsum.py#L112

Thanks! just to make sure, the forward function called in monarch_linear.py:
https://github.com/HazyResearch/fly/blob/cd624cffeffa7d1579336d26a776405bf0867f36/src/models/layers/blockdiag_butterfly_multiply.py#L63
is then equivalent to
https://github.com/HazyResearch/fly/blob/cd624cffeffa7d1579336d26a776405bf0867f36/src/ops/blockdiag_butterfly_einsum.py#L89
and we can just use the block_diag_butterfly_project_einsum_rank function for the projection step? I compared the two forward functions on a number of inputs, and they seemed equivalent to me, but just wanted to double check.

Another related question, I'm seeing relatively high projection error for arbitrary weight matrices.
ie. if I generate a standard normal matrix M, with dimensions 1024 x 4096, project this into two monarch matrices with the function you suggested, then compute the overall projected matrix \tilde{M}, I get a max element-wise difference of ~4. Is this expected? I'm finding that fine-tuning dense -> sparse fine-tuning is not performing well due to this projection error.
I'm wondering whether I'm using the function suggested correctly.
I've shown this in the colab here: https://colab.research.google.com/drive/18uQy0nWP-oH0bXcViwipzxsA-5MpfMpk?usp=sharing


task: Front End Registration

References #37
Definition of Done:

[x] Front end page is built with stepper for registration
[x] Validation is handled on the front end
[x] Able to make create call to backend to register users

[t:180]
Added page for registration, created stepper and fields for a user to register, wrote validation for each field, started creating fields for error messages to display based on validation result

[t:60]
Added validation on all form fields, including error messages based on entries

[t:90]
Added call to backend to create account and a check to make sure username, phone and email are all unique


Need to add /airr/v1/receptor_reactivity endpoint

There is currently a /receptor endpoint but we have not added a /receptor_reactivity endpoint to go along with the ReceptorReactivity object.

The object is cell_reactivity, not receptor_reactivty as per discussion in #705


--poll option does not work with libraries

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Repro steps
--poll option does not work with library.
ng build --watch --poll=1000 works but ng build some-library --watch --poll=1000 does not.
The log given by the failure
CHZRHMAC048:design-system cenkm$ ng build design-system-generic
Building Angular Package
Building entry point 'design-system-generic'
Compiling TypeScript sources through ngc
Bundling to FESM2015
Bundling to FESM5
Bundling to UMD
Minifying UMD bundle
Copying declaration files
Writing package metadata
Removing scripts section in package.json as it's considered a potential security vulnerability.
Built design-system-generic
Built Angular Package!
 - from: /Users/cenkm/workspace/design-system/projects/design-system-generic
 - to:   /Users/cenkm/workspace/design-system/dist/design-system-generic
CHZRHMAC048:design-system cenkm$ ng build design-system-generic --watch --poll=1000
Unknown option: '--poll'

Desired functionality
--poll option also works with libraries. It works fine if [project] is not provided.

This will require work to be done at upstream, as we are using ng-packagr to build libraries and this feature is not currently supported from their end either.


Add DeviceIoControl

Multiple files were also move from the desktop project to the shared one
as file functions are present in both (CreateFile isn't but CreateFile2
is for example)

LGTM. Thanks.


deprecation

The "Symfony\Component\HttpKernel\DependencyInjection\Extension" class is considered internal since Symfony 7.1, to be deprecated in 8.1; use Symfony\Component\DependencyInjection\Extension\Extension instead. It may change without further notice. You should not use it from "jonasarts\Bundle\TCPDFBundle\DependencyInjection\TCPDFExtension".

Will look into it and upgrade to use future class.

Resolved


Move from master to control plane

A set of changes that fixes #17880

/assign @rajakavitha1

This is ready for approval.

This PR changes “master” (lower case) to “Control Plane” (initial caps).
@Fale can you comment on why the change of letter case? I'd expect to see “master” change to “control plane”.

@sftim In https://kubernetes.io/docs/concepts/overview/components/ we kept "Control Plane" as capitalized

I've noted that in that page there is not much consistency around this. Is there an official way to write it so we can standardize it everywhere (titles, text, etc)

Have a look at https://kubernetes.io/docs/concepts/overview/components/ @Fale
The first (perhaps also most prominent) mention of “control plane” write the term in lower case.

I don't mind the "control plane" version, but if this is the rule, I'm going to fix the other page as well

+:ok_hand:

@sftim  Isn't it the opposite you were suggesting in https://github.com/kubernetes/website/pull/20265#discussion_r409662561 ?

@sftim Isn't it the opposite you were suggesting in #20265 (comment) ?

In page titles, it's OK to capitalize words that are normally lower case.

@sftim Isn't it the opposite you were suggesting in #20265 (comment) ?

In page titles, it's OK to capitalize words that are normally lower case.

I think that is confusing if we have different rules for title and text

@Fale, page titles are written in initial caps on this website. (This is common in English writing for the web).

Ok, I see now the rationality of it

Are sub-titles following the same rule of titles, right?

/lgtm


[Remote Store] Add cluster settings to enforce index creation with Remote storage.

Is your feature request related to a problem? Please describe.
Today the user has a choice to create a remote store backed index in a cluster by providing certain settings during index creation. We should introduce cluster settings to allow user to create remote store backed indices without specifying remote store settings for each index during creation. If cluster settings is enabled all indices by default would be remote store backed
Describe the solution you'd like
Introduce new cluster settings to enable remote store cluster wide and another settings to specify the default repo to be used. Whenever a new index would be created it would be remote store backed
Describe alternatives you've considered
NA
Additional context
NA

@sachinpkale is this in your radar?

Yes @anasalkouz this for Durability and under @sachinpkale 's  radar


Crash on launch

I'm unable to launch this software due to "Fatal error occured on initialisation" message with window title "INVALID TITLE WITH QUOTES"
Windows 10 Enterprise Version 21H1 (OS Build 19043.1110)

Hi, thanks for the report, the error window you got is quite confusing given the title, but I think I may have found the source. There's a good chance that it's caused by the Analog SDK not being installed, I'll have to do a bit more digging as to why it gives such an unhelpful message, but if you follow the Analog SDK install guide here it should hopefully get you going

Hi, thanks for the reply, and for the solution! I did not have SDK installed, and now it works wonders (=

@Beeque Great to hear! Next update I push out will have a fixed error dialog so hopefully no-one else will run into that issue :)


Add python programming in repo

@GlazeDonuts add python programming resource in programming-languages readme

#59

Issue here


Hi does regsync work with workload identity ?

Does regsync work with gke workload identity to sync to Google Artifact Registry ?
I am trying with regclient/regsync:alpine

@sudo-bmitch
I tried with the config in the initial image of the Question after uncommenting credHelper.
But without mounting service account token I cannot get regsync to authenticate to GAR ( Google Artifact Registry )
What works though is the below :

Create the pod with command: ["/bin/sh"] and args: ["-c", "while true; do date; echo sleeping for 600s; sleep 600; done"]
Create a service account key of the GCP IAM service account in GCP console
Mount the sa key inside the pod at home/appuser/.config/gcloud/application_default_credentials.json
Execute docker-credential-gcr configure-docker --registries=europe-docker.pkg.dev in the pod
Execute regsync once -c /etc/regsync/regsync.yml -v debug

docker-credential-gcr configure-docker --registries=europe-docker.pkg.dev is not executed by the command regsync once -c /etc/regsync/resync.yml -v debug
Did you manage to get it working previously using GKE workload identity ( without having to create a key for GCP service account ) ?

The readme on docker-credential-gcr seems to indicate they require a service account, which would need to be associated with the container. If it has access, you should be able to run the following to get a token:
echo "europe-docker.pkg.dev" | docker-credential-gcr get

I don't have access to GKE myself, so best I can do it refer you to guides for the credential helper:

https://cloud.google.com/artifact-registry/docs/docker/authentication#standalone-helper
https://cloud.google.com/docs/authentication#service-accounts
https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity

If those don't work and the credential helper still isn't returning a working token, then either the GKE or the credential helper maintainers would probably be a better resource. Once you have a working token from the helper running in the container, if that doesn't work with regsync, I can try to assist further.

@sudo-bmitch :
Okay so workload identity support is not yet possible for regsync to connect to GAR ( workload identity is a secure way to connect to GCP instead of using service account keys which pose a security risk ). So if you could add the support to workload identity as a feature to regsync it would help those who use GAR as their container registry.
However there is still a concern with regsync by using service account key.

Mount service account in the pod at home/appuser/.config/gcloud/application_default_credentials.json and run it in GKE
Execute regsync once -c /etc/regsync/regsync.yml -v debug

The above 2 steps do not succeed.
Have to add an additional manual step to configure credHelper.

Mount service account in the pod at home/appuser/.config/gcloud/application_default_credentials.json and run it in GKE
Execute docker-credential-gcr configure-docker --registries=europe-docker.pkg.dev
Execute regsync once -c /etc/regsync/regsync.yml -v debug

With these 3 steps ( additional step to configure credHelper ), regsync works.
When credHelper: docker-credential-gcr is set in /etc/regsync/regsync.yml the manual execution of configuring credential helper should not be required right ?
credHelper: docker-credential-gcr is supposed to configure credential helper right ?

For issues with docker-credential-gcr, please report those in their own GitHub repo: https://github.com/GoogleCloudPlatform/docker-credential-gcr
regclient calls credential helpers using their predefined spec, which is to run $helper get and pass the hostname to stdin. It does not implement any of the helper logic itself, it only includes two of the more popular ones in the alpine images for convenience.

The configure-docker command is used to setup a config.json file used by docker logins, and regsync will fallback to that if the credentials are not setup correctly in the yml file. The screenshot is difficult to read and apparently not the one you are using, but make sure you have configured the registry option on the entry with the credential helper, and skip setting the hostname value (the uses for that are rare).

@sudo-bmitch okay now with registry instead of hostname I can have regsync do the work without having to explicitly execute docker-credential-gcr configure-docker --registries=europe-docker.pkg.dev
We can conclude this issue/thread
Ending notes :

regsync does not work with GKE workload identity
regsync works syncing to GAR with gcp service account credentials mounted in the pod


Merge pull request #23 from IntelSoftware/praveenkk123-patch-3

Update README.md

All changes were made to the repo in a separate PR. No need to merge this one.


CLI login not working

Bug description
When running grabber from the command line, I sometimes get the warning:
[Warning] [JavaScript] 2 image(s) without URL found, login to view them

However, if I provide my username and password:
C:\[redacted]\Grabber_v7.10.1_x64> grabber-cli -f "C:\[redacted]\imgbrd-grabber\%artist%\%md5%.%ext%" -m 10000000 -t "[redacted]" -s "e621.net" -u "[redacted]" -w "[redacted]" --download

it seems to have no effect.
Steps to reproduce
Run grabber-cli with -s "e621.net" and using a tag that has images that are blocked unless you login.
System information

OS: Windows 11
Grabber version: v7.10.1

Yes, seems like the CLI parameters for login aren't mapped properly. Note that login does work when just going through the UI, which might be better in some cases since a source might have multiple login methods and more than two fields.
I'll make sure that the user/login config is mapped properly when passed, though.

My point was that if you go through the UI, setup your login information, then go back to the CLI, you don't need to pass any login parameters. Definitely not great but you'd only need to use it to setup login.

My point was that if you go through the UI, setup your login information, then go back to the CLI, you don't need to pass any login parameters. Definitely not great but you'd only need to use it to setup login.

Oh, I see. That's a good tip! The login must be cached somewhere then... I'll give it a try until the fix can get in. Thanks!

Yes, login information is stored in each site's config files.


Add generic int16_t fields to radio packet data structure

[x] Add 3 generic int16_1 fields to the radio packet structure to support e.g. current temp, max and min
[x]  Adding 4th to handle e.g. light sensor and / or motion sensor in same transmission.

https://github.com/jgc/falco_photon/issues/1

typedef struct {
uint8_t node;
uint8_t tran;
int16_t batt;     // battery voltage in millivolts
int16_t value1; // Generic e.g. Current temperature in dec * 100
int16_t value2; // Generic e.g. Minimum temperature in dec * 100
int16_t value3; // Generic e.g. Maximum temperature in dec * 100
int16_t value4; // Generic
} Payload;
Payload theData;


sizing guide for premetheus operator components

we have k8s cluster with high load of pods (3000-10000 pods) ,we are using Prometheus operator to monitor the system. lately we encounter several of issue especially with the runC issue and upgrade the operator to the latest version 0.29 which solved some of the issue, thanks!
Now when we increasing the load even further we see that the operator is not stable, node-exporter issues and kube-state-metrics etc... before we coming into conclusion that this is just bugs... is there any sizing guide which cpu & memory its better to use on high load system ? how to scale the components etc to fits high loads requirements. most of the issue doesn't appear regularly, just on high load...
Please advice

Could you be more precise in your information? What do you mean by "not stable"? What issues are you seeing with node-exporter/kube-state-metrics? We did some capacity planning documentation for OpenShift in regards to planning the Prometheus server's resources approximately: https://docs.openshift.com/container-platform/3.11/scaling_performance/scaling_cluster_monitoring.html#cluster-monitoring-capacity-planning
For what it's worth, we remove all limits from our components on openshift, and only set resource requests for monitoring components.

@brancz  - we see that the statfulSet - prometheus-prometheus is getting the following message in the k8s-dashboard , "Readiness probe failed: HTTP probe failed with statuscode: 503
Back-off restarting failed container" ,
also for pod - prometheus-prometheus-0 with the same error
please let me know which commands do you want to me to run in kubectl do get maybe more precise details

What do the logs say?

when I use this command for the running container
kubectl logs prometheus-operator-366578bfbf-w8j90 -n monitoring
I get logs which look ok:
level=info ts=2019-03-04T10:52:28.807183621Z caller=operator.go:970 component=prometheusoperator msg="sync prometheus" key=monitoring/prometheus
level=info ts=2019-03-04T10:52:36.31179327Z caller=operator.go:970 component=prometheusoperator msg="sync prometheus" key=monitoring/prometheus
level=info ts=2019-03-04T10:52:43.817785031Z caller=operator.go:970 component=prometheusoperator msg="sync prometheus" key=monitoring/prometheus

when I run this:
kubectl logs prometheus-prometheus-0 -n monitoring
im getting error since this pod state is crashLoopBack
Error from server (BadRequest): a container name must be specified for pod prometheus-prometheus-0, choose one of: [prometheus prometheus-config-reloader rules-configmap-reloader]

please advice how to proceed .

for the second one you need to specify the container you want logs for
kubectl logs prometheus-prometheus-0 -n monitoring -c prometheus

@brancz  -done see my update

Could you share the whole pod object of that Prometheus pod?

@brancz - what do you mean ? how can I achieve this ?

kubectl get pod prometheus-prometheus-0 -n monitoring -oyaml

@brancz  - can I send you this via email please?  maybe we have there secure data which I dont want to share...

@brancz  - please see:
apiVersion: v1
kind: Pod
metadata:
  annotations:
    cni.projectcalico.org/podIP: <IP_ADDRESS>/32
    kubernetes.io/psp: mbrer.privileged
  creationTimestamp: "2019-03-03T19:03:20Z"
  generateName: prometheus-prometheus-
  labels:
    app: prometheus
    controller-revision-hash: prometheus-prometheus-8b7db6
    prometheus: prometheus
    statefulset.kubernetes.io/pod-name: prometheus-prometheus-0
  name: prometheus-prometheus-0
  namespace: monitoring
  ownerReferences:
    - apiVersion: apps/v1
      blockOwnerDeletion: true
      controller: true
      kind: StatefulSet
      name: prometheus-prometheus
      uid: ed55555125-3dca-11eeq-9c26-16555510066
  resourceVersion: "104139"
  selfLink: /api/v1/namespaces/monitoring/pods/prometheus-prometheus-0
  uid: 0b9a3-e7-11e9-9c26-1646
spec:
  containers:
    - args:
        - --web.console.templates=/etc/prometheus/consoles
        - --web.console.libraries=/etc/prometheus/console_libraries
        - --config.file=/etc/prometheus/config_out/prometheus.env.yaml
        - --storage.tsdb.path=/prometheus
        - --storage.tsdb.retention=24h
        - --web.enable-lifecycle
        - --storage.tsdb.no-lockfile
        - --web.route-prefix=/
      image: quay.io/prometheus/prometheus:v2.7.1
      imagePullPolicy: IfNotPresent
      livenessProbe:
        failureThreshold: 6
        httpGet:
          path: /-/healthy
          port: web
          scheme: HTTP
        periodSeconds: 5
        successThreshold: 1
        timeoutSeconds: 3
      name: prometheus
      ports:
        - containerPort: 9090
          name: web
          protocol: TCP
      readinessProbe:
        failureThreshold: 120
        httpGet:
          path: /-/ready
          port: web
          scheme: HTTP
        periodSeconds: 5
        successThreshold: 1
        timeoutSeconds: 3
      resources:
        limits:
          cpu: 160m
          memory: 1000Mi
        requests:
          cpu: 100m
          memory: 400Mi
      terminationMessagePath: /dev/termination-log
      terminationMessagePolicy: File
      volumeMounts:
        - mountPath: /etc/prometheus/config_out
          name: config-out
          readOnly: true
        - mountPath: /prometheus
          name: prometheus-prometheus-db
        - mountPath: /etc/prometheus/rules/prometheus-prometheus-rulefiles-0
          name: prometheus-prometheus-rulefiles-0
        - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
          name: prometheus-token-538zf
          readOnly: true
    - args:
        - --log-format=logfmt
        - --reload-url=http://localhost:9090/-/reload
        - --config-file=/etc/prometheus/config/prometheus.yaml.gz
        - --config-envsubst-file=/etc/prometheus/config_out/prometheus.env.yaml
      command:
        - /bin/prometheus-config-reloader
      env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
      image: quay.io/coreos/prometheus-config-reloader:v0.29.0
      imagePullPolicy: IfNotPresent
      name: prometheus-config-reloader
      resources:
        limits:
          cpu: 50m
          memory: 50Mi
        requests:
          cpu: 50m
          memory: 50Mi
      terminationMessagePath: /dev/termination-log
      terminationMessagePolicy: File
      volumeMounts:
        - mountPath: /etc/prometheus/config
          name: config
        - mountPath: /etc/prometheus/config_out
          name: config-out
        - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
          name: prometheus-token-558zf
          readOnly: true
    - args:
        - --webhook-url=http://localhost:9090/-/reload
        - --volume-dir=/etc/prometheus/rules/prometheus-prometheus-rulefiles-0
      image: quay.io/coreos/configmap-reload:v0.0.1
      imagePullPolicy: IfNotPresent
      name: rules-configmap-reloader
      resources:
        limits:
          cpu: 100m
          memory: 25Mi
        requests:
          cpu: 100m
          memory: 25Mi
      terminationMessagePath: /dev/termination-log
      terminationMessagePolicy: File
      volumeMounts:
        - mountPath: /etc/prometheus/rules/prometheus-prometheus-rulefiles-0
          name: prometheus-prometheus-rulefiles-0
        - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
          name: prometheus-token-558zf
          readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  hostname: prometheus-prometheus-0
  nodeName: ip-11-350-28-33.al-1.comp.internal
  nodeSelector:
    worker.mbr.awscloud.io/group: operator
  priority: 20000
  priorityClassName: operator-critical
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: prometheus
  serviceAccountName: prometheus
  subdomain: prometheus-operated
  terminationGracePeriodSeconds: 600
  tolerations:
    - effect: NoSchedule
      key: WorkGroup
      operator: Equal
      value: operator
    - effect: NoExecute
      key: WorkGroup
      operator: Equal
      value: operator
    - effect: NoExecute
      key: node.kubernetes.io/not-ready
      operator: Exists
      tolerationSeconds: 300
    - effect: NoExecute
      key: node.kubernetes.io/unreachable
      operator: Exists
      tolerationSeconds: 300
  volumes:
    - name: config
      secret:
        defaultMode: 420
        secretName: prometheus-prometheus
    - emptyDir: {}
      name: config-out
    - configMap:
        defaultMode: 420
        name: prometheus-prometheus-rulefiles-0
      name: prometheus-prometheus-rulefiles-0
    - emptyDir: {}
      name: prometheus-prometheus-db
    - name: prometheus-token-558zf
      secret:
        defaultMode: 420
        secretName: prometheus-token-558zf
status:
  conditions:
    - lastProbeTime: null
      lastTransitionTime: "2019-03-04T07:18:15Z"
      status: "True"
      type: Initialized
    - lastProbeTime: null
      lastTransitionTime: "2019-03-04T11:17:41Z"
      message: 'containers with unready status: [prometheus]'
      reason: ContainersNotReady
      status: "False"
      type: Ready
    - lastProbeTime: null
      lastTransitionTime: "2019-03-04T11:17:41Z"
      message: 'containers with unready status: [prometheus]'
      reason: ContainersNotReady
      status: "False"
      type: ContainersReady
    - lastProbeTime: null
      lastTransitionTime: "2019-03-04T07:18:15Z"
      status: "True"
      type: PodScheduled
  containerStatuses:
    - containerID: docker://f02cb05f3ae422b8edeaa99d266b5c539fbdfb
      image: quay.io/prometheus/prometheus:v2.7.1
      imageID: docker-pullable://quay.io/prometheus/prometheus@sha256:f21aa9225a1ba630e9bbb6525c56703ed317ae9226
      lastState:
        terminated:
          containerID: docker://f02wr9d266b5ce792936fe82578a8b5c539fbdfb
          exitCode: 137
          finishedAt: "2019-03-04T11:17:40Z"
          reason: OOMKilled
          startedAt: "2019-03-04T11:15:57Z"
      name: prometheus
      ready: false
      restartCount: 24
      state:
        waiting:
          message: Back-off 5m0s restarting failed container=prometheus pod=prometheus-prometheus-0_monitoring(03-3de7-11e9-9c26-164066)
          reason: CrashLoopBackOff
    - containerID: docker://8feed0b292280ba171d1c4b4a444de5791ddc1cd7c0
      image: quay.io/coreos/prometheus-config-reloader:v0.29.0
      imageID: docker-pullable://quay.io/coreos/prometheus-config-reloader@sha256:d40935baa38d8ca61ac927069f30f02e8757f0eae9ee335be23
      lastState: {}
      name: prometheus-config-reloader
      ready: true
      restartCount: 0
      state:
        running:
          startedAt: "2019-03-04T07:19:08Z"
    - containerID: docker://873f0ac2aaagdcvwraa783e8bf00e25bbfacf75ea509b9d5
      image: quay.io/coreos/configmap-reload:v0.0.1
      imageID: docker-pullable://quay.io/coreos/configmap-reload@sha256:e24rwwe7deba907833e8ca53f0047c42c5a057
      lastState: {}
      name: rules-configmap-reloader
      ready: true
      restartCount: 0
      state:
        running:
          startedAt: "2019-03-04T07:19:29Z"
  hostIP: <IP_ADDRESS>
  phase: Running
  podIP: <IP_ADDRESS>
  qosClass: Burstable
  startTime: "2019-03-04T07:18:15Z"
  ~ 

@brancz  - does it helps to figure out this problem ?

Ah yes, that looks like your Prometheus Pod has too low memory limits, as the source of the crashloop is the OOMKill, not the readiness probe (the readiness probe takes ~75 seconds to be ready, but that works as expected as it reads the write ahead log into memory). I would recommend removing the limits and see where memory usage ends up.

@brancz  - thanks !
two questions :)

How did you see that the memory is not sufficient ?  which line ?/
I think (please correct me if im wrong) that limits is a best practice , after I will remove them how you suggest to identify  how much mem & cpu I should use, via top ? or other tool?

      lastState:
        terminated:
          containerID: docker://f02wr9d266b5ce792936fe82578a8b5c539fbdfb
          exitCode: 137
          finishedAt: "2019-03-04T11:17:40Z"
          reason: OOMKilled
          startedAt: "2019-03-04T11:15:57Z"
      name: prometheus
      ready: false
      restartCount: 24
      state:
        waiting:
          message: Back-off 5m0s restarting failed container=prometheus pod=prometheus-prometheus-0_monitoring(03-3de7-11e9-9c26-164066)
          reason: CrashLoopBackOff

I think (please correct me if im wrong) that limits is a best practice , after I will remove them how you suggest to identify how much mem & cpu I should use, via top ? or other tool?

This depends. Monitoring is so important that we prefer it to take whatever it needs rather than be killed. However, if you are concerned, you can of course set limits. I suggest to look at the usage over time, using Prometheus itself :slightly_smiling_face: .

@brancz  - thank you, will follow your guide and will update. hopefully this is the issue. Thanks a lot!

@brancz  - just to verify ( we build new cluster for high-load)  should I remove the limits only from here ?  or there is other places which I should adjust ?
kind: Deployment
metadata:
  labels:
    k8s-app: prometheus-operator
  name: prometheus-operator
  namespace: monitoring
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: prometheus-operator
  template:
    metadata:
      labels:
        k8s-app: prometheus-operator
    spec:
      priorityClassName: "operator-critical"
      tolerations:
        - key: "WorkGroup"
          operator: "Equal"
          value: "operator"
          effect: "NoSchedule"
        - key: "WorkGroup"
          operator: "Equal"
          value: "operator"
          effect: "NoExecute"
      containers:
        - args:
            - --kubelet-service=kube-system/kubelet
            - --logtostderr=true
            - --config-reloader-image=quay.io/coreos/configmap-reload:v0.0.1
            - --prometheus-config-reloader=quay.io/coreos/prometheus-config-reloader:v0.29.0
          image: quay.io/coreos/prometheus-operator:v0.29.0
          name: prometheus-operator
          ports:
            - containerPort: 8080
              name: http
#          resources:
#            limits:
#              cpu: 200m
#              memory: 200Mi
#            requests:
#              cpu: 100m
#              memory: 100Mi

You should remove the limits from the Prometheus object.

@brancz  - thank you so much!


Unified builder plugin system

While the hooks we have are complete in providing the ability to have loader plugins in the browser, and to alter the loader hooks as well, an "official" plugin system enables third-party ecosystems to properly grow. At the moment we're really only growing these ecosystems around module loader plugins, but there is scope to have loader hook plugins.
For example this would enable ecosystem plugins for things like code coverage, alternative minification and code optimization etc etc. And it's really important to have such an ecosystem.
By focusing first on the builder, it may be as simple as simply providing a plugin API as a sugar shortcut to the hooks and documenting it.
Something like:
var builder = new Builder();

builder.config({
  plugins: ['x']
});

Where the plugin is itself loaded as a module and then simply provides implementations for the loader hooks, as if we had done:
builder.config({
  fetch: customFetch,
  translate: customTranslate
});

etc etc. It's effectively very similar to what Rollup did here too.

This issue could equally be called "make SystemJS builder like webpack"...


Joh/fix74925

This is for https://github.com/microsoft/vscode/issues/74924

Works lovely -> approved


[WIP] Bump Docsy to 0.7.x

This PR upgrades to a newer version of Docsy: 0.7.2 (preview)
In the testing I've done, I haven't found any different look or behavior that still needs fixing. The top nav doesn't look right, though.
Relevant to issue https://github.com/kubernetes/website/issues/44002
/area web-development
This PR incorporates the commits from PRs:

#48721
#48722
#48723
#48724

Ah, this needs a fix!

This also needs more work on working well for mobile / narrow viewports.
/retitle [WIP] Bump Docsy to 0.7.x
See https://github.com/kubernetes/website/pull/48724 for a PR that may be better to merge.

Hmm, I think this needs a new approach.
/close
I hope to get time to revisit it.


Icons in the download list

It would be great if, beside the video title in the download list, there was an icon that shows the current status of the download (downloading, post-processing, completed, etc).
Like this :

The status will therefore be more visible by a fast glimpse.
Thanks in advance!

I guess we could add them (even though its a pain with wxListCtrl) if this gets some thumbs up.


Push this repo to songcamp

References:

https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
https://vercel.com/docs/concepts/git/vercel-for-github#changing-the-github-repository-of-a-project

Done


Can not convergence to my mouse dataset

Hi! That's great work! But it doesn't work on my video. After 100 epochs, the images in the sample folder and my parameter config file are shown below. I try to use the pre-train model to finetune but it doesn't work either. What can I do to improve the keypoint discovery performance on my dataset? (train file contains 40,000 images)
dataset: custom_dataset
data: data/mice
workers: 4
epochs: 300
start_epoch: 0
schedule: 30
batch_size: 16
lr: 0.001
momentum: 0.9
weight_decay: 0.0001
print_freq: 10
pretrained: False
gpu: 0
val_schedule: 20
curriculum: 4
checkpoint: checkpoint/custom_dataset
nkpts: 15
image_size: 256
frame_gap: 15
bounding_box: False  # Only False allowed for the custom dataset
perc_weight: [100.0, 1.6, 2.3, 1.8, 2.8, 100.0]
resume: checkpoint/CalMS21/checkpoint.pth.tar
evaluate: False

Hi & thanks for your interest in our project! The current release of our code doesn't support multiple identical agents noted below (as you have 3 black mice in your example (the pre-trained model is on 1 black mouse & 1 white mouse)):

We are still working on open-sourcing the version of our code that would address multiple identical agents, but we have an internal version of our code that handles this. If you'd like us to help run the multi-agent version of our code on your videos, feel free to share your videos here! https://forms.gle/k5gwNxws8xMEEzUe6
Otherwise, we can update when the multi-agent version is open-sourced!

Thank you


ocamlPackages.cairo2: 0.6.2 -> 0.6.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ocaml4.14.0-cairo2/versions.
meta.description for ocamlPackages.cairo2 is: "Binding to Cairo, a 2D Vector Graphics Library"
meta.homepage for ocamlPackages.cairo2 is: "https://github.com/Chris00/ocaml-cairo"
meta.changelog for ocamlPackages.cairo2 is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 0.6.4 with grep in /nix/store/mybvw7lpnpf9wncsh2dfrgzvgdw4q07r-ocaml4.14.0-cairo2-0.6.4
found 0.6.4 in filename of file in /nix/store/mybvw7lpnpf9wncsh2dfrgzvgdw4q07r-ocaml4.14.0-cairo2-0.6.4

Rebuild report (if merged into master) (click to expand)

11 total rebuild path(s)

11 package rebuild(s)

First fifty rebuilds by attrpath
acgtk
coqPackages.coqide
coq_8_10
coq_8_11
coq_8_12
coq_8_13
easycrypt
framac
ocaml-top
spark2014
why3

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mybvw7lpnpf9wncsh2dfrgzvgdw4q07r-ocaml4.14.0-cairo2-0.6.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.cairo2 https://github.com/r-ryantm/nixpkgs/archive/7cec36f3551c27f8270da00ecba696fd5533fa7e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mybvw7lpnpf9wncsh2dfrgzvgdw4q07r-ocaml4.14.0-cairo2-0.6.4
ls -la /nix/store/mybvw7lpnpf9wncsh2dfrgzvgdw4q07r-ocaml4.14.0-cairo2-0.6.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

16 packages built:

acgtk
coqPackages.coqide
coq_8_10
coq_8_11
coq_8_12
coq_8_13
easycrypt
framac
ocaml-top
ocamlPackages.cairo2
ocamlPackages.lablgtk3
ocamlPackages.lablgtk3-gtkspell3
ocamlPackages.lablgtk3-sourceview3
ocamlPackages.lambdapi
spark2014
why3

Maintainer pings
cc @jirkamarsik @vbgl for testing.

@ofborg build spark2014 coq_8_12 coq_8_13 why3 coq_8_10 coq_8_11 easycrypt framac ocaml-top acgtk coqPackages.coqide


Investigate how IPv6 is exposed

Whilst fixing #239 it turns out that the properties weren't available for a device that only had IPv6 addresses.  Have a look at if these are already available in the library end make available if need be.

Hopefully fixed with #242


Using node lib that imports files with fs.readFileSync throws error

First I think this issue may maybe belong somewhere else. But I am not sure where and clueless in how to solve it.
I am trying to use node library conekta-node but when using it I get the following error:
{
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/Users/ben/Workspace/myserver/.esbuild/.build/cert/ca_bundle.crt'
}

and the reason is because these lines in code in node_modules
const certPath = path.join(path.dirname(__dirname), '/cert/ca_bundle.crt')
...
ca: fs.readFileSync(certPath),

https://github.com/conekta/conekta-node/blob/master/lib/Requestor.js#L35
I tried
custom:
  esbuild:
    external:
      - conekta

but it leads to other problems about other modules not being available.
I also tried
custom:
  esbuild:
    packagerOptions:
      scripts:
        - mkdir -p .esbuild/.build/cert
        - cp node_modules/conekta/cert/ca_bundle.crt .esbuild/.build/cert/ca_bundle.crt

but does not seem to copy ca_bundle.crt file
I searched everywhere for a solution but can't find any.
Any hints?

Have you tried adding your file as part of the package options on serverless.yml?
So something like:
	 package:   patterns:     - 'node_modules/conekta/cert/ca_bundle.crt'
I usually use this to add external files to the build.

Thanks for the advice that did almost work.
Since esbuild bundles the code it cannot be included in node_modules folder
Was easily solved with esbuild-plugin-copy like this
/* eslint-disable @typescript-eslint/no-var-requires */
const { copy } = require('esbuild-plugin-copy');

module.exports = (serverless) => {
    return {
        minify: true,
        exclude: ['@aws/sdk'],
        bundle: true,
        sourcemap: true,
        keepNames: true,
        plugins: [
            copy({
                resolveFrom: 'cwd',
                assets: [
                    {
                        from: ['node_modules/conekta/cert/ca_bundle.crt'],
                        to: '.esbuild/.build/cert/ca_bundle.crt',
                    },
                ],
            }),
        ],
    };
};


feat(es-7-migration): Update script and migration docs and add a simple Dockerfile

The script requires ssl configuration even if we disable ssl. Update the script to take optional disable-ssl params for source and destination.
Add simple Dockerfile to run a docker container that runs the script.
Update migration doc with recommendations on how to migrate to es7.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

@shirshanka @jplaisted Please take a look! Let me know if the migration plan needs more details.

I'm fine with whatever name for the branch. Naming is hard, bikeshedding probably not worth it :p
@shirshanka did you want to cut a release before ES7? Maybe a 0.6.2 the immediately a 0.7.0? Up to you, I'm not sure if there are other breaking changes other than ES, if not then this would let people upgrade as far as possible without going to ES7.

+1 to having two releases. If we decide on the version numbers, I can add that into the readme as well.

I think if there's no other major breaking changes other than ES7 then 0.6.2 and 0.7 will work. Otherwise 0.7 and 0.8 (where 0.8 is ES7, ironically). If its too hard to tell we can just do 0.7 and 0.8.


meaning of visibility

Can you clarify these scenarios? What is a user with no visibility? I completely lost you there.
First time I'm reading this, starting from the top, getting to:
https://github.com/cloudfoundry/cc-api-v3-style-guide#responses-collection

We are archiving this repo in favor of colocating the information in the ccng repo, any issues or PRs are welcome in its new location. Thanks!


Adding support for ISY.

This adds support for Universal Devices ISY controller which communicates with an array of Insteon and Z-Wave devices. Initial commit is tested working for controlling Light Bulb (dimming), Switch, and Ceiling Fan devices. It uses the published REST API available at http://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface

Awesome, sounds great!

I saw a lot of issues in this code. As mentioned here, the onRead was apparently not being called right.
here:
 onRead: function() {
   return this.query();
}

The function isn't defined right. The function has a callback, and you're supposed to return the value with the callback, not a return.
 onRead: function(callback) {
   callback(this.query());
}

though, query() wasn't defined to use a callback either, which it probably should. to keep things from blocking, (or even working correctly at all right?)
From what I can tell just by breezing over this pull though, its not exactly working.

I changed it as suggested to utilize the callback. However, I simply put a console.log in there
onRead: function(callback) {
    console.log("Query");
    callback(this.query());
}

I do not see the log of 'Query' ever showing up. I also log out in my query() code and it does not run either. I guess what I am asking is - when is this supposed to be executed? I never see it getting called.

It gets called when homekit queries the current state of your device.
For example, ask Siri which light are on. It will get called.
As for the logs, I'm not sure you can log via that way, I've seen them not show up like that. Check the logging pattern used in the other Accessory shims.
Do this, instead, just return a value instead of running the query (which isn't working anyways because it doesn't support a callback).
So just use callback(true). In the logs you should then see it.

On Jun 27, 2015, at 12:33 AM, rayzorben<EMAIL_ADDRESS>wrote:
I changed it as suggested to utilize the callback. However, I simply put a console.log in there
onRead: function(callback) {
console.log("Query");
callback(this.query());
}
I do not see the log of 'Query' ever showing up. I also log out in my query() code and it does not run either. I guess what I am asking is - when is this supposed to be executed? I never see it getting called.
—
Reply to this email directly or view it on GitHub.

If onRead is not being called, then that is the first thing to investigate. From your code it does look like it's defined in the right place. This may be a silly question but did you make sure to update git submodules to get the latest version of HAP-NodeJS?

Really appreciate your help. Still not seeing what I think I should be seeing. Looking at the code:
console.log("Characteristics.js:valueForUpdate(): called, Siri has asked for the accessory's status");

if (this.onRead) {
    console.log("Characteristics.js:valueForUpdate(): invoking callback");

My log is showing the first message, but it is not showing the second message (invoking callback). I have simplified it as you recommended. I have verified that the version of HAP-NodeJS is correct and what is in Characteristic.js matches what is in your commit.

Ignore me - I pulled the latest HAP-NodeJS, but not the latest HomeBridge as I was in the middle of a commit and didn't pull it back down after. So I missed the update for the onRead to HomeBridge which copies it across. It is calling the callback now.

:+1:


Add Markdown Underline Style to Get Texts Underlined (Maybe Not In Markdown)

Some language syntax extensions, like rust-analyzer, may use "markup.underline" to distinguish terms. Just add the following code copied from the default theme:
		{
			"scope": "markup.underline",
			"settings": {
				"fontStyle": "underline"
			}
		},

Duplicated #139 due to GitHub 500 Server error. Closed.


Rules to prevent slowloris are not working

I want modsec to detect some possible slowloris attacks,but none worked
apache 2.4.23 loaded reqtimeout_module module:
RequestReadTimeout header=10 body=20
latest mod_security 2.9.1:
SecRule RESPONSE_STATUS "@streq 408" "phase:3,id:1,log,pass"
SecRule RESPONSE_STATUS "@streq 408" "phase:4,id:2,log,pass"
SecRule RESPONSE_STATUS "@streq 408" "phase:5,id:3,log,pass"
SecDebugLog /var/log/modsec_debug.log
SecDebugLogLevel 9
I've made requests by burp suite,replaced \r\n\r\n with \r\n between request headers and request body.
Apache returned 408 as expected.
As to modsec,nothing,no debug log and no audit log

By the way.
SecConnReadStateLimit and SecConnWriteStateLimit don't work as well

Hi @fuckingbaidu,
Do you have SecConnEngine set to On?
https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#secconnengine

Can confirm this, 408 errors are not being received by mod_security2 so there is no way to capture or parse them

Can confirm this, 408 errors are not being received by mod_security2 so there is no way to capture or parse them. I'm guessing mod_reqtimeout module doesn't bubble the error to mod_security?

5 years later... Any movement about this problem?

Hello @ShaiMagal ,
This item is long closed -- in fact, so long closed that I have never seen it before. So, no, it has received no attention whatsoever.
The combined commentary in this old item is confusing at best.
The title 'Rules to prevent ...' implies that ModSecurity functionality is to perform the rejection of the transaction. I believe the relevant functionality in ModSecurity v2 does indeed work. (There is no such functionality in ModSecurity v3 because it does not have the necessary access to nginx's TCP stack.)
However, other wording seems to refer to other Apache functionality and the complaint was merely that ModSecurity v2 was not reporting the rejection. If that was the case, then the possibility mentioned back in 2018 is reasonably likely.

Hi @martinhsv ,
we are facing totally same issue in 2023 on all our servers difference distributions:

Ubuntu 20 TLS (Ubuntu 16 and 18 same problem)
Apache/2.4.58 (Ubuntu) + mod_reqtimeout (lower Apache 2.4.x versions same problem)
libapache2-mod-security2 2.9.3-1ubuntu0.1

Apache correctly gave 408 error to access.log, but mod_security do nothing.
Our rule looks:
 SecRule RESPONSE_STATUS "@streq 408" "id:20,phase:5,t:none,nolog,pass,setvar:ip.slow_dos_counter=+1,expirevar:ip.slow_dos_counter=60,ctl:ruleEngine=On"
SecRule IP:SLOW_DOS_COUNTER "@gt 5" "id:21,phase:1,t:none,log,deny,status:403,msg:'SlowlorisAttack',ctl:ruleEngine=On"

If we try to change "@streq 408" to "@streq 200" (for TEST only) - it works well and block and log.
But 408 isn't detected. (in apache log is correctly written)
ALL other rules works well. (we have more than 100 modsec rules without problems)

@ShaiMagal ,
If you would like to bring this to the attention of the community, please create a new issue (and use the issue template 'Bug report for version 2.x')

@martinhsv
OK, when I will have time, I will do this.

@martinhsv Opened here:
https://github.com/SpiderLabs/ModSecurity/issues/3007[](url)


Fixed some spelling an grammar in the readme

Proposed Changes

[X] I've read the CODE OF CONDUCT and abide to it.
[X] I've read the CONTRIBUTING.md
[X] I've forked the repository.
[X] I've created a branch and made my changes in it.
[X] I understand opening a PULL REQUEST doesn't mean it will be merged for sure.

as per https://github.com/blockspacer/CXXCTP/issues/68

Thanks!


Add blob manager

What is the purpose of the change
Add blob manager
Brief change log
(for example:)

Add blob manager

Verifying this change
(Please pick either of the following options)
This change added tests.

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@45faf27). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev     #325   +/-   ##
======================================
  Coverage       ?   21.19%
======================================
  Files          ?      148
  Lines          ?    13419
  Branches       ?     1785
======================================
  Hits           ?     2844
  Misses         ?    10414
  Partials       ?      161

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 45faf27...5c03a55. Read the comment docs.


Add initial type definitions for ProtoBuf.js

This is an initial type definition file for the ProtoBuf.js project. Added a few core functions and types and tests for them.
This was requested in https://github.com/borisyankov/DefinitelyTyped/issues/2754

Finally the PR builds and is ready for merging.

@panuhorsmalahti thank you your contributions. please rename protobuf to protobufjs.
definitelytyped.org/guides/contributing.html#naming-the-file
https://www.npmjs.com/package/protobufjs

Renamed to protobufjs.

@panuhorsmalahti thanks mate!

Wanted to let you know that I'm going to be working on completing protobuf.d.ts over the course of the next week. Hopefully, will have it done by Monday.
For this though, it would be really nice to be able to include PR - #4569 in the definitions.

I've tackled most of protobufjs. I still have one more library to go through and I need to add tests.
You can check out my progress here though:
https://github.com/ttowncompiled/DefinitelyTyped/tree/protobufjs

I have 90%, if not more, of protobufjs. I'm going to write the tests, and then submit the PR.

Finished the tests for protobuf.d.ts. Check it out here:
https://github.com/ttowncompiled/DefinitelyTyped/tree/protobufjs


Added tournament URL to signup embed

Absolutely teeny quality of life thing

Also all the other commits from the main branch which dev doesn't have :tf:

thats a few commits

Github dot com forced my hand
Also did you notice what I did with the colour? :tf:


Licensing requirement needs clarification

Hello,
This statement seems to imply that a license is required on both the source and target tenants: "All users in both the source and target organizations must be licensed with the appropriate Exchange Online subscriptions. Also, make sure to apply Cross Tenant User Data Migration licenses to all users that will be migrated to the target side."
Through https://o365exchange.visualstudio.com/o365 core/_queries/edit/3667656/?triage=true, the license requirement is such that it is required on either the target or source tenant, but not both.  Clarifying this would be helpful for customers moving forward.

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

ID: c61c960c-f5c3-76f7-ac18-dfeaf30230e4
Version Independent ID: 3dc607b2-869e-976f-80da-d73cfb1210e5
Content: Cross-tenant mailbox migration - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/cross-tenant-mailbox-migration.md
Service: microsoft-365-enterprise
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

Closing, found clarification in the documentation.


Buffering changes for remaining funcs & fix face detection

This is a follow-up to #2 ; this covers the other 6 functions. It also fixes the direct path use of the image detection XML files.

Per Discord convo, I also added a fix for the face detection. Two more models are used, and it attempts to use the best one to indicate faces. It's still missing on vaguer faces, but actually detects a fair amount of cartoon faces now too.


MyVaillant Heating Boiler energy entities missing after update

Hello, since update from v0.8.17 to v0.8.22, I am missing my Heating Boiler entities related to energy. Everything was available and running fine before. Is there anything I can do to return it? I tried downgrade back to v0.8.17 but it says this entity is not included in mypyllant integration.
Thank you for checking and answer in advance! :)

Same here.

Same problem

same here

same problem

same here

Same here

Unitower Sensors are unavailable.

Same problem here. None of the energy consumption sensors are available anymore. It says that the entity is not part of mypyllant any more.

no solution?

Now the difference comparing to the previous occasions, the same function is working in the MyVaillant app but not from HA. I suppose Vaillant has changed something again...

Same for me.
My "Vaillant aroTHERM plus heatpump + sensoCOMFORT VRC 720 + sensoNET VR 921" was reporting beautifully up to the update.

works again, for whatever reason

I downgraded since I've had that issue, and the downgraded version sometimes works, sometimes doesn't.
I currently assume there is at least a problem at vaillant.

After checking a bit more, for some non-obvious reason the entities are renamed, so the data is there I just need to query another entity....
potala_device_0_vu_25cs_1_5_n_int2_ecotec_plus_consumed_electrical_energy_heating potala_device_0_vu_25cs_1_5_n_int2_ecotec_plus_consumed_primary_energy_heating_2

What is the situation with you? I am still not getting any data

I doublechecked the entities as @Vladx71 wrote. I did find them. Everything works fine so far.
I do have:

myVAILLANT v0.8.22 with configuration see picture below (currently I am testing with Fetch Energy Management Data and 3600 seconds between energy data updates)
Vaillant VU 10CS/1-5 (N-INT2) ecoTEC plus
Vaillant VR 940f Wi-Fi Gateway
Vaillant sensoROOM VRT 51f

With the 0.8.22 I see 5 entities as unavailable:
sensor.XXX_device_0_arotherm_consumed_electrical_energy_cooling
sensor.XXX_device_0_arotherm_consumed_electrical_energy_domestic_hot_water
sensor.XXX_device_0_arotherm_consumed_electrical_energy_heating
sensor.XXX_device_1_unitower_consumed_electrical_energy_domestic_hot_water
sensor.XXX_device_1_unitower_consumed_electrical_energy_heating
I can't find any order energy entities.

Everything is working fine again ! I guess the problems had been due to Vaillant. But even in the app they give an hint that data update can take a while.

After I deleted the whole thing in hacs and reinstalled it, it now works again

Deleting or reactivating HA  really not help. there is no update of Vailant, only update on HA. Do we can expect any bug fix soon?

After I deleted the whole thing in hacs and reinstalled it, it now works again

I had no luck with that. Energy entities are still missing after reinstalling the plugin.

I had the same problem and got it working again with following settings. Let's see how long it will last

same problem here
With the 0.8.22 I see 5 entities as unavailable:
sensor.XXX_device_0_arotherm_consumed_electrical_energy_cooling
sensor.XXX_device_0_arotherm_consumed_electrical_energy_domestic_hot_water
sensor.XXX_device_0_arotherm_consumed_electrical_energy_heating
sensor.XXX_device_1_unitower_consumed_electrical_energy_domestic_hot_water
sensor.XXX_device_1_unitower_consumed_electrical_energy_heating
when can we expect a response?

did you check quota messages in the logs. vaillant seems to be limiting access to this data. if you see those errors in the logs try to contact them and ask to be excluded from query limits.


ENYO-4772: TooltipDecorator add tooltipHidden prop

Issue Resolved / Feature Added
Tooltip is not removed when VideoPlayer control panel is hidden
Resolution
Tooltip visibility is based on its wrapped component DOM events. In the case that wrapped component is both disabled, un-focusable, and hidden by its parent, there is no way TooltipDecorator knows when to hide tooltip... because there is no DOM event that TooltipDecorator can receive. Adding the prop tooltipHidden allows for control over hiding tooltip. When tooltipHidden = false, tooltip will show and hide as normal.
Additional Considerations
We could also guard DOM eventlisteners with tooltipHidden
Links
ENYO-4772
Enact-DCO-1.0-Signed-off-by: Teck Liew<EMAIL_ADDRESS>

closing out as the jira associated with this is closed.


PATCH params sent as payload

Hi.
I was trying to make a PATCH request to my endpoint users{/id}, but found out that the data in case of POST/PUT/PATCH is always send as the payload, and not replaced in the url.
My API endpoint expects the PATCH to be something like /users/7 when I'm updating the data for user number 7.
I know the "problem" is in resources.js but I don't know if you consider this a problem or not.
Edit: This only happens when using the resource this.$resource. Using this.$http with method PATCH, works perfeclty
Thanks

Add this setting Vue.http.options.emulateJSON = true

Hi @Nandiin
Thanks for the reply, but after all the mistake was mine.
I was doing resource.save({id: 1, item: 'a'}) instead of resource.save({id: 1}, {item: 'a'})
Sorry for the confusion


suggestion

maybe try to develop something that the script check  the futbin(live price update every 10-40 min) prices when u search the players and caculate the sell price... it will be crazy!

Will be tracked as part of #72


Escrever texto para a seção "Transcriptional analyses"

Sugestões:

Falar do artigo do Clóvis

Transcriptional analysis is an indispensable tool for understanding the pattern and regulation of gene expression in triggering biological processes. This field has been marked by notable advances in molecular biology techniques over the years and, consequently, in the amount of data generated. The Dalmolin group has been researching this area since 2009, analyzing data from Microarray, Bulk RNA-seq, and, more recently, single-cell RNA-seq (scRNA-seq).
One of the first transcriptional analysis projects undertaken by the group resulted in the development of a computational method that assesses gene expression variation and identifies functional modules consisting of strongly interacting genes. Initially, this method was applied to differentiate stages of Saccharomyces cerevisiae fermentation (10.1093/nar/gkq1269), and subsequently, it was used to assess early and late-induced global transcriptional changes caused by lead (https://doi.org/10.3389/fgene.2019.00791). This approach resulted in the Bioconductor/R package called Transcriptogramer (10.1093/bioinformatics/btz007) and can be used for both Microarray and RNA-seq data, enabling genome-wide visualization of the alterations in the gene expression in the most numerous conditions or diseases.
The group also conducts studies focusing on the transcriptional analysis applied to diseases, studying the gene expression pattern related to the regulation of metastasis development in cancer and major depressive disorder development.


Add Meagan to team page

Added a TOML for myself

@meagancojocar can you add an img of yourself too?


Add initial demo-driven design demos

Previous discussion: https://github.com/hlandau/openssl-ddd/pull/1
See also #17939.
For discussion of the "demo-driven design" demos and permanent inclusion of these demos into the OpenSSL tree for future reference.
This comment will be updated to link to the blogpost when it's published.

Updated:

Added notes on scope to README.
Added clean target.
Warnings.
Added note about SSL_CERT_DIR to README.
Used www.openssl.org:443 as endpoint.
Remove unnecessary buffering in nonblocking RX code.
Handle EOF in ddd-05.

Unclear to me how one is supposed to avoid long lines in Markdown tables. I've exempted it from the mdl config.

@mattcaswell Saw your notes on SSL_set_connect_state. It is interesting that removing SSL_set_connect_state worked for you. Is there some kind of undefined state we have here we should be explicitly checking for?

It is interesting that removing SSL_set_connect_state worked for you.

This was (partly) user error. Removing it didn't actually report any errors, but it didn't come back with a response either. At the time I hadn't set SSL_CERT_DIR so I think that might have also masked things.

My personal proposed diffs against demos 1 through 4 are now available for viewing here: https://github.com/hlandau/openssl/compare/ddd-diff-base...hlandau:ddd-diff
Feedback welcomed, and since I expect this to be quite a collaborative process, if other people have very different ideas for what the diffs should look like, I'd be interested to see.

The proposed diff for demo 5 is now available here:
https://github.com/hlandau/openssl/compare/ddd-diff-base...hlandau:ddd-diff
Each demo has a Markdown file discussing the design issues and resultant changes. You can read these discussions inline in the above diffs, or here:
https://github.com/hlandau/openssl/tree/ddd-diff/ddd

I've added a demo 6, which demonstrates use of a memory BIO with libuv, the asynchronous I/O library. I believe this captures valuable design information that is not necessarily obvious in demo 5.

Demo 2 has been chosen to exemplify use of BIO_f_buffer. Diffs and the discussion have been updated.

The proposed diff for demo 5 is now available here: hlandau/openssl@ddd-diff-base...hlandau:ddd-diff
Each demo has a Markdown file discussing the design issues and resultant changes. You can read these discussions inline in the above diffs, or here:
https://github.com/hlandau/openssl/tree/ddd-diff/ddd

Could you create a pull request on your own fork at least so I can add comments to the diff? I have some questions and concerns with some of the diffs.

@t8m Done. https://github.com/hlandau/openssl/pull/1

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 61 days ago

Also approved if the directories are moved somewhere a little better (e.g. doc/design)

Also approved if the directories are moved somewhere a little better (e.g. doc/design)

Yeah, please move it there -> doc/design/ddd

Moved.

Assuming @paulidale is ok with the move.

This pull request is ready to merge

Merged to master branch. Thank you.


Error response from daemon: Get "https://registry-1.docker.io/v2/"

Describe the bug
1.I'm in china, cannot connect "registry-1.docker.io" when without VPN network
2.It's fine when in VPN network, but vpn network is not free
3. not use registry-mirrors, i want use china's registry-mirrors
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

docker.json
{
"registry-mirrors" : [
"https://dockerproxy.com",
"https://docker.mirrors.ustc.edu.cn",
"https://docker.nju.edu.cn"
]
}
docker info

To Reproduce
No response
Expected behavior
No response
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.8.2
Commit: 44cf8269710cd29802bfee176a7cec65b55cc822 (v1.8.2)
System info:
macOS: 15.1 (24B2082)
CPU: arm64, 14 cores
CPU model: Apple M4 Pro
Model: Mac16,7
Memory: 24 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-11-30T14-42-51.379785Z.zip

Screenshots and additional context (optional)
No response

none of the mirrors are working

Where can I see the logs?

Duplicate of #1305


Cannot replace data in window 10

I ran this function on window 10.
local ENV working fine but when I packaged and run it as application. I saw this message: " Can't find end of central directory : is this a zip file ?"
can anyone help me out?

Please provide a way for us to reproduce your issue. This is not enough information.

oh sorry. the problem is about my code. fs.writefileSync in nodejs not override in window. I thought that message is error but it is not. Thank for kindly response.

Good to hear that you found a solution! Thanks for the update.