Retry on errors when reconciling the root policy

Before this, the controller would be stuck in an infinite loop in the
event something failed when reconciling the root policy. This is not
likely in most cases except for a bad template string. This enables
proper error handling of template strings rather than just ignoring
them.
This ended up refactoring a lot of the handleRootPolicy method in order
to make it easier to read with the addition of retry logic.
Resolves https://github.com/open-cluster-management/backlog/issues/15438

@ckandag I couldn't think of a nice way to add a stable e2e test for retries since it'd all be subject to timing that we have little control over. I worried that if I did add one, it would be unstable based on how fast the system executing the e2e tests are or it'd be quite hacky.

@mprahl  : You are fearless with your refactoring !
Gathering  and Setting the statuses of Failed Clusters/decisions on the root Policy  looks  good.
On the  Retrying part , I imagined  that reconcile-request would be re-queued   to the back of the queue for a certain number of times.
But it looks  like, each method that throws an error is being retried individually and immediately.
Which is ok  and harmless I suppose but   in some places I dont know that its really necessary  or has-value.
e.g reading the policy list r.client.List , would a retry change the result ?  similarly on other r.client operations.
The particular scenario I had in mind when considering Re-tries was -  if there is a timing issue with setting up the policies vs resources referenced in the templates they could be resolved on a retry like when a cluster shows in the placement decisions before the config-map is updated with params for this new cluster .   Far edge team enquired about this , so thought retry may provide a little help there. But  I am no sure anymore about this if we do an immediate retry.
Just because of the  amount of changes, probably best if  Gus reviewed it too @gparvin

@mprahl : You are fearless with your refactoring !
Gathering and Setting the statuses of Failed Clusters/decisions on the root Policy looks good.
On the Retrying part , I imagined that reconcile-request would be re-queued to the back of the queue for a certain number of times.
But it looks like, each method that throws an error is being retried individually and immediately.
Which is ok and harmless I suppose but in some places I dont know that its really necessary or has-value.
e.g reading the policy list r.client.List , would a retry change the result ? similarly on other r.client operations.
The particular scenario I had in mind when considering Re-tries was - if there is a timing issue with setting up the policies vs resources referenced in the templates they could be resolved on a retry like when a cluster shows in the placement decisions before the config-map is updated with params for this new cluster . Far edge team enquired about this , so thought retry may provide a little help there. But I am no sure anymore about this if we do an immediate retry.
Just because of the amount of changes, probably best if Gus reviewed it too @gparvin

@ckandag the reason why I retried each individual function that calls an error is for efficiency and to prevent race conditions.
For example, if the first try on handleRootDecision 5 managed clusters fail out of 10. The intuitive thing would be to rerun handleRootDecision again only for the 5 that failed. What if the placement status changed between the first and second attempt? The policies would be partially propagated based on the old placement status and partially on the new placement status. Granted, the next reconcile request would fix this, but it'd be in an awkward state until then.
Retrying on each step that can fail removes this risk of a race condition. Additionally, each step is retried a maximum amount of times rather than just the whole method.
In terms of your question on if it's valuable for the API calls to be retried, I imagine so in the event of a temporary infrastructure "blip" (i.e. DNS issue, network infra issue, etc.) or we are waiting on some process to complete. Then we could not retry on the failed subset clusters if we requeue on those errors.
In terms of your concern about it not really being helpful for the event where a template resolution fails due to a dependent resource not being available, I disagree. This retry mechanism waits 1 second before trying again at first, but then this wait grows after each consecutive failure with a maximum of 5 seconds. I can make this longer if you think it'd be helpful. Anything beyond that should be handled by a separate process which periodically reprocesses all the templates.

Thanks for the review @gparvin! I responded to your comments and here's the diff from your last review:
https://github.com/open-cluster-management/governance-policy-propagator/compare/e0553f385157dcbb91100175a8301dbe7249ca2c..16454a6c8517a382edd168596b763d2090dccacf


Problem with numpy/openblas in staged-recipes

Quoting @jochym ...

Several (phonopy, elastic, pyhmc) staged-build PRs got broken by the numpy/openblas problems on osx and linux for py3k. I had to block builds for py3k on these platforms. At the same time the feedstocks with similar code and setup (e.g. spglib) build fine. I'll be happy to provide any additional info to help with this.

Appears this problem does not occur with conda-build-all version 1.0.0, but it does occur with conda-build-all version 1.0.1. This points to an issue with PR ( https://github.com/SciTools/conda-build-all/pull/68 ), but it is not clear to me yet what it is. Any ideas @mwcraig ?

It seems really odd that #68 would cause this kind of issue. What version of conda build and conda are being used?
If i had to guess, this maybe has to do with the fact that #68 left in place a small difference in how the built package path is determined (beyond the fact that one uses the appropriate API call and one does not): In the call to bldpkg_path at https://github.com/SciTools/conda-build-all/blob/master/conda_build_all/build.py#L43 the config is passed in, but in the call to get_output_file_path at https://github.com/SciTools/conda-build-all/blob/master/conda_build_all/builder.py#L43 the config is not passed in.
This is pure speculation, though...

Some mixture of conda-build 1.21.14 and 2.0.x it seems as I guess we changed conda-build version while tracking down this bug too. I'm guessing @scopatz theory with bldpkg_path is correct.
xref: https://github.com/SciTools/conda-build-all/commit/323db66848d02180dbcf6a02bf4fc24fd08dca6e

This was already solved right? If so, we should be able to switch back to python 3 in staged-recipes' conversion step.

Closing this out. Looks like the issue was resolved, though I don't have a xref to prove it...


Feature4119

initial commit of friction test - functions added for support of friction test between realtimerobottask3.py and systemmanager.py

looks good, thanks. I'll move some functions to derived class later.


Inference garph

Hello,
I just wanted to know where you are saving the .pbtxt file? I noticed your code creates this graph file but I am not able to locate the code snippet for creating it.
Thanks in advance

Hi @ramrahu, if I remember correctly, I didn't use the proto buff export because it was incompatible with the py_func  function used to convert and feed the audio files to the network. Depending on which graph you need, you could just try to export it.

Hmm... but I see a .pbtxt file created in the checkpoint directory. There must have been some code to create that file. I didn't add anything to export it.

Hi, sorry for the late response. I would assume that the tf.estimator.Estimator does write those. In that case it's probably configurable somewhere within the tf.estimator.RunConfig; however I don't know where exactly.

Hmm ok thank you
Do you have any paper on this work which I could cite for my work?

If you could cite:
@thesis{Dangschat2018,
  author = {Dangschat, Marc},
  title = {End-to-End Speech Recognition Using Connectionist Temporal Classification},
  type = {Master Thesis},
  institution = {Münster University of Applied Sciences},
  date = {2018-11-21},
  url = {https://github.com/mdangschat/ctc-asr},
}

that would be great. Could you drop me a line when your work is finished? It would be interesting to dabble a bit into TensorFlow on Android.

Yeah sure. Will let you know when my work is finished. Thank you for your help.

Hi,
I have a question. I see most speech recognition applications use 16 kHz audio files for training. And from my understanding of your work, I guess even you have done the same. I was wondering why isn't 44.1 kHz and 48 kHz considered for training as they may have more important frequencies that may be lost in 16 kHz?

Hey, some of the reasons why I used 16 kHz training material were:

The number of samples per second of recording. An increased SR contains more datapoints, therefore a RNN would require additional unrolls.
To be comparable with other models, which mostly use 16 kHz.
I merged several smaller datasets into a larger one, and didn't want to upsample. So I stayed with the lowest SR.

Does the number of samples per second affect feature extraction? I read somewhere that it might. Like for example, for 44.1 kHz, if we use a 25 ms frame to extract MFCC like its generally done, the number of samples we get isn't a whole number. That may affect MFCC extraction. Not sure in what way it affects though.

I'm not sure how an increased sampling rate affects windowed features like MELSCALE/MFCC. I would assume that is would allow for more precise discrete datapoints. Which could maybe help if you would also use more of them. For example increasing the 80 coefficients (NUM_FEATURES) that I use. The window size (and step) should be tuned to fit common speech features like e.g. phonemes.
The increase in computation I mentioned was more in reference of raw data input or a misuse of the librosa API; which I used initially while prototyping this project.

OK thanks. One last question. I didn't understand what you mean my datapoints?

Raw speech data or extracted features (e.g. MFCC) are time series data, which contains a datapoint at every recorded time step.


Retrieve Customer Segments

Sorry for asking this isn't really a troubleshooting issue. I am trying to find a way to get segment data for specific customers. I cannot see anything in the package, does the package include a method to do this or will I need to call the API following these guides?
https://documentation.bloomreach.com/engagement/reference/segmentations-2
https://documentation.bloomreach.com/engagement/reference/customer-segmentations-test
Thanks

Hi @LarssK-TS Flutter SDK has no API for Segmentations data yet. It is planned to bring support in future. I'm not able to tell ETA but please ask your CMS or contact support for more informations.


[CI] Deprecated all CI workflows related to the manylinux2014 target

Hello, I am a code review agent on flows.network using model gpt-4o.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

Hello, I am a code review agent on flows.network using model claude-3-5-sonnet-20240620.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!


Add diff/ediff faces.

I have added this for mocha theme:
  ;; ediff
  (ediff-even-diff-A                    (:background mantle))
  (ediff-even-diff-B                    (:background mantle))
  (ediff-even-diff-C                    (:background mantle))
  (ediff-odd-diff-A                     (:inherit 'ediff-odd-diff-A))
  (ediff-odd-diff-B                     (:inherit 'ediff-odd-diff-B))
  (ediff-odd-diff-C                     (:inherit 'ediff-odd-diff-C))

I have also fixed the indentation in the catppuccin-mocha.el (the tabs and spaces were mixed together randomly and lots of lines were misaligned).
I will pr this when I will have time.


testvm - scheduling - failed

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What happened:
Installed Kubevirt and then deployed testvm.  testvm is toggling between 'scheduling' and 'failed' states.  The pod, virt-launcher-testvm-xxxx is transitioning from Init to Terminating and restarting.  Hence virtctl console testvm, timed out as well.
I am unable to look into the Pod Logs of virt-launcher-testvm-xxxx as well, since it is getting recreated freshly.
kubectl get vmis
NAME     AGE   PHASE        IP    NODENAME
testvm   6s    Scheduling

kubectl get vmis
NAME     AGE   PHASE    IP    NODENAME
testvm   19s   Failed         kf-w-1

kubectl get pods --all-namespaces
NAMESPACE     NAME                               READY   STATUS      RESTARTS   AGE
default       centos                             0/1     Completed   0          16h
default       virt-launcher-testvm-78bsj         0/2     Init:1/2    0          1s
kube-system   coredns-6955765f44-52lt4           1/1     Running     0          16h
kube-system   coredns-6955765f44-8c7h6           1/1     Running     0          16h
kube-system   etcd-kf-m                          1/1     Running     0          16h
kube-system   kube-apiserver-kf-m                1/1     Running     0          16h
kube-system   kube-controller-manager-kf-m       1/1     Running     0          16h
kube-system   kube-flannel-ds-b8jl2              1/1     Running     0          16h
kube-system   kube-flannel-ds-nx5rg              1/1     Running     0          16h
kube-system   kube-proxy-h4cbz                   1/1     Running     0          16h
kube-system   kube-proxy-mk8fh                   1/1     Running     0          16h
kube-system   kube-scheduler-kf-m                1/1     Running     0          16h
kubevirt      virt-api-86c54597b4-5hbll          1/1     Running     0          16h
kubevirt      virt-api-86c54597b4-bfvff          1/1     Running     0          16h
kubevirt      virt-controller-65444f859c-rrlwh   1/1     Running     0          16h
kubevirt      virt-controller-65444f859c-xcrzm   1/1     Running     0          16h
kubevirt      virt-handler-kj7d5                 1/1     Running     0          16h
kubevirt      virt-operator-5f79869f79-dmxc4     1/1     Running     0          16h
kubevirt      virt-operator-5f79869f79-wp8kz     1/1     Running     0          16h

What you expected to happen:
Was expecting to connect to the testvm console using virtctl console testvm
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version): v0.39.0
Kubernetes version (use kubectl version): v1.17.17
VM or VMI specifications:
Cloud provider or hardware configuration: Baremetal
OS (e.g. from /etc/os-release): "CentOS Linux"  "7 (Core)"
Kernel (e.g. uname -a): Linux kf-m 3.10.0-1160.24.1.el7.x86_64 #1 SMP
Install tools:
Others:

@bhkamath could you please describe testvm

This is the test VM provided on kubevirt.io page.
wget https://raw.githubusercontent.com/kubevirt/kubevirt.github.io/master/labs/manifests/vm.yaml
kubectl apply -f https://raw.githubusercontent.com/kubevirt/kubevirt.github.io/master/labs/manifests/vm.yaml

@bhkamath Thank you for the response
Could you please run  kubectl describe virtualmachine.kubevirt.io/testvm and let me know the output

kubectl describe virtualmachine.kubevirt.io/testvm
Name:         testvm
Namespace:    default
Labels:       <none>
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"kubevirt.io/v1alpha3","kind":"VirtualMachine","metadata":{"annotations":{},"name":"testvm","namespace":"default"},"spec":{"...
              kubevirt.io/latest-observed-api-version: v1
              kubevirt.io/storage-observed-api-version: v1alpha3
API Version:  kubevirt.io/v1
Kind:         VirtualMachine
Metadata:
  Creation Timestamp:  2021-04-18T12:30:45Z
  Generation:          4
  Resource Version:    1725019
  Self Link:           /apis/kubevirt.io/v1/namespaces/default/virtualmachines/testvm
  UID:                 fcac5458-daeb-4974-9a0a-f695301ad624
Spec:
  Running:  true
  Template:
    Metadata:
      Creation Timestamp:  <nil>
      Labels:
        kubevirt.io/domain:  testvm
        kubevirt.io/size:    small
    Spec:
      Domain:
        Devices:
          Disks:
            Disk:
              Bus:  virtio
            Name:   containerdisk
            Disk:
              Bus:  virtio
            Name:   cloudinitdisk
          Interfaces:
            Bridge:
            Name:  default
        Machine:
          Type:  q35
        Resources:
          Requests:
            Memory:  64M
      Networks:
        Name:  default
        Pod:
      Volumes:
        Container Disk:
          Image:  quay.io/kubevirt/cirros-container-disk-demo
        Name:     containerdisk
        Cloud Init No Cloud:
          userDataBase64:  SGkuXG4=
        Name:              cloudinitdisk
Status:
  Created:  true
  Volume Snapshot Statuses:
    Enabled:  false
    Name:     containerdisk
    Reason:   Volume type does not suport snapshots
    Enabled:  false
    Name:     cloudinitdisk
    Reason:   Volume type does not suport snapshots
Events:       <none>

@bhkamath could you please run virtctl start testvm
I want to see the events after running testvm currents its none
also events of virt-launcher if created kubectl describe pod/virt-launcher-testvm-xxxxx

virtctl start testvm
Error starting VirtualMachine Operation cannot be fulfilled on virtualmachine.kubevirt.io "testvm": Always does not support manual start requests

kubectl get pods
NAME                         READY   STATUS        RESTARTS   AGE
centos                       0/1     Completed     0          3d16h
hello36-755bd85b5f-7b4rf     1/1     Running       0          28h
virt-launcher-testvm-lgqxq   1/2     Terminating   0          3h59m

kubectl describe pod/virt-launcher-testvm-lgqxq
Name:                      virt-launcher-testvm-lgqxq
Namespace:                 default
Priority:                  0
Node:                      kf-w-1/<IP_ADDRESS>
Start Time:                Thu, 22 Apr 2021 06:48:26 +0530
Labels:                    kubevirt.io=virt-launcher
                           kubevirt.io/created-by=3a124d43-5b30-4099-b794-ccdbbe6e913a
                           kubevirt.io/domain=testvm
                           kubevirt.io/size=small
Annotations:               kubevirt.io/domain: testvm
Status:                    Terminating (lasts 3h58m)
Termination Grace Period:  60s
IP:                        <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  VirtualMachineInstance/testvm
Init Containers:
  container-disk-binary:
    Container ID:  docker://90217d230df7edd2f01069d5a42d0944484f71278aca9df79fc8d10aafc73745
    Image:         quay.io/kubevirt/virt-launcher@sha256:15d8acc10977d4bcc14deb76da3d38252b5455dff9284a80231347b19a5d73a9
    Image ID:      docker-pullable://quay.io/kubevirt/virt-launcher@sha256:15d8acc10977d4bcc14deb76da3d38252b5455dff9284a80231347b19a5d73a9
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/cp
      /usr/bin/container-disk
      /init/usr/bin/container-disk
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Thu, 22 Apr 2021 06:48:28 +0530
      Finished:     Thu, 22 Apr 2021 06:48:28 +0530
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     100m
      memory:  40M
    Requests:
      cpu:        10m
      memory:     1M
    Environment:  <none>
    Mounts:
      /init/usr/bin from virt-bin-share-dir (rw)
  volumecontainerdisk-init:
    Container ID:  docker://24c022dc961e46b935919af4c4415aff162dd9dfbe70cb6ad515aceeecb25059
    Image:         quay.io/kubevirt/cirros-container-disk-demo
    Image ID:      docker-pullable://quay.io/kubevirt/cirros-container-disk-demo@sha256:0e5ac38b20abcc7752293425b239a147868facd62cd5030dede6da6f2fc526a1
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/container-disk
    Args:
      --no-op
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Thu, 22 Apr 2021 06:48:32 +0530
      Finished:     Thu, 22 Apr 2021 06:48:32 +0530
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     100m
      memory:  40M
    Requests:
      cpu:        10m
      memory:     1M
    Environment:  <none>
    Mounts:
      /usr/bin from virt-bin-share-dir (rw)
      /var/run/kubevirt-ephemeral-disks/container-disk-data/3a124d43-5b30-4099-b794-ccdbbe6e913a from container-disks (rw)
Containers:
  compute:
    Container ID:  docker://223e683855841e08bc416549f7ea61491e81dee65756f2d04f9e437f311544fa
    Image:         quay.io/kubevirt/virt-launcher@sha256:15d8acc10977d4bcc14deb76da3d38252b5455dff9284a80231347b19a5d73a9
    Image ID:      docker-pullable://quay.io/kubevirt/virt-launcher@sha256:15d8acc10977d4bcc14deb76da3d38252b5455dff9284a80231347b19a5d73a9
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/virt-launcher
      --qemu-timeout
      5m
      --name
      testvm
      --uid
      3a124d43-5b30-4099-b794-ccdbbe6e913a
      --namespace
      default
      --kubevirt-share-dir
      /var/run/kubevirt
      --ephemeral-disk-dir
      /var/run/kubevirt-ephemeral-disks
      --container-disk-dir
      /var/run/kubevirt/container-disks
      --grace-period-seconds
      45
      --hook-sidecars
      0
      --less-pvc-space-toleration
      10
      --ovmf-path
      /usr/share/OVMF
      --use-emulation
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Thu, 22 Apr 2021 06:48:32 +0530
      Finished:     Thu, 22 Apr 2021 06:48:45 +0530
    Ready:          False
    Restart Count:  0
    Limits:
      devices.kubevirt.io/tun:  1
    Requests:
      cpu:                      100m
      devices.kubevirt.io/tun:  1
      memory:                   242382920
    Environment:                <none>
    Mounts:
      /var/run/kubevirt-ephemeral-disks from ephemeral-disks (rw)
      /var/run/kubevirt/container-disks from container-disks (rw)
      /var/run/kubevirt/hotplug-disks from hotplug-disks (rw)
      /var/run/kubevirt/sockets from sockets (rw)
      /var/run/libvirt from libvirt-runtime (rw)
  volumecontainerdisk:
    Container ID:  docker://8f0043b86a5ed93dbeb659d46168419568304c3aa9b0aa6729eb918678d9299e
    Image:         quay.io/kubevirt/cirros-container-disk-demo
    Image ID:      docker-pullable://quay.io/kubevirt/cirros-container-disk-demo@sha256:0e5ac38b20abcc7752293425b239a147868facd62cd5030dede6da6f2fc526a1
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/container-disk
    Args:
      --copy-path
      /var/run/kubevirt-ephemeral-disks/container-disk-data/3a124d43-5b30-4099-b794-ccdbbe6e913a/disk_0
    State:          Running
      Started:      Thu, 22 Apr 2021 06:48:36 +0530
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     100m
      memory:  40M
    Requests:
      cpu:        10m
      memory:     1M
    Environment:  <none>
    Mounts:
      /usr/bin from virt-bin-share-dir (rw)
      /var/run/kubevirt-ephemeral-disks/container-disk-data/3a124d43-5b30-4099-b794-ccdbbe6e913a from container-disks (rw)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  sockets:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  virt-bin-share-dir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  libvirt-runtime:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  ephemeral-disks:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  container-disks:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  hotplug-disks:
    Type:        EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:   <unset>
QoS Class:       Burstable
Node-Selectors:  kubevirt.io/schedulable=true
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason   Age                      From             Message
  ----    ------   ----                     ----             -------
  Normal  Killing  3m46s (x103 over 3h59m)  kubelet, kf-w-1  Stopping container volumecontainerdisk

It seems similar to https://github.com/kubevirt/kubevirt/issues/5220 issue
would you mind upgrading to the latest version  v0.40.0

Shall update to v0.40.0 version

On upgrading to v0.40.0 version, I am able to create testvm and login to console successfully.
Thanks a lot.


Don't build fuzz tests target on Travis

This XCode target started failing on Travis for no clear reason. This isn't reproducible locally; remove the target to unblock development.

Is it mergeable?

Yes. It fixes part of the problem, though I still had to rerun two of the build steps (one was timing out and the other hasn't been producing output for 10 minutes).


Could it delete old files when using DateRollingFileStream?

I find it is easy to use RollingFileStream to keep numBackups files. But how can I keep certain number files when using DateRollingFileStream? The most idealized method is to delete files by passing a certain time range, for example pass a number to keep this number latest days files.
Could log4js support this? Or could you give some advise?

After searching source code, I found there is a option daysToKeep to implement this. It's my fault without reading source code.

This isn't your fault - it should be in the documentation. I'm going to keep this issue open, so that I remember to update the docs to include the daysToKeep option.


In-Statement properties need to also show those where the entity is the prop's source node

In-statement properties under entity Detail only show the uses of that entity as proptype or propvalue. We also need to show those where the entity is the source node. E.g., if we attach somewhere the in-statement prop P Alberic - has - C order - C Dominican order, we need to see this in-statement prop under the entity Alberic. Very important even for our Hackathon 3 coding.
My view is that we should even sort the uses: first list the uses where the entity is the source node, then when it is proptype, and then when it is propvalue. To be considered whether to even create subtitles for those 3 kinds of uses.

If I understand correctly, P:Alberic is, in your example, an actant, and therefore, you can find the link under Used In - Statements section

In-statement Classifications and In-statement Properties are more important, they need to be more visible than just giving a link to the statement in which there is a mention of them. I.e., on the basis of your statement screenshot, @adammertel, we need to see more visibly in Detail that Bernard has mother P XYZ and brother G ZYX.
I think this was decided - that we will create special sections:
Classification
Meta classification
In-statement classification
Properties
Meta properties [editable from Detail]
In-statement properties [non-editable from Detail, click icon available to open the relevant statement]
@rljshaw to cross-check this design proposal.

A hotfix was deployed, which append cases when the entity was an origin into the list of UsedInProps.


WIP added medical centers form

#2

What is left to do (consider)

Date picket in ETH date
The note section (I think that is a common component)
Language picker (Common component)
Validation - what are the required fields?


Group Rails Project: set up kanban board

List of Pair members

@Tekhlay
@EmekaEmmanuel

We are a pair of two members 🤟

Hi Team 👍🏼
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that doesn't has a link to the project Kanban board. Kindly add this
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


[FR] Simple API endpoint to change own user metadata

Fixes #3979

@SchrodingersGat experiencing some ... interesting test behaviour here - any idea why a test fails if all tests are run but succeeds if only the specific file is run (only on pgsql)?

Nope, that's a new one for me. Something being set in the test environment by a prior test?

Maybe, not really sure. Let's see if it now works.

Have you worked out the CI issues here?

@SchrodingersGat no, now I know why it was commented out originally

@matmair is there any intent in this PR to replace the front-end forms with this API driven approach? Or would you like to see this merged separately "as is"

@SchrodingersGat no, this is more to get in line with the expectations OIDC / OAuth2 connector have regarding user info endpoints


Stage types are lost when using TypeScript and Dynamic Import in Next.js.

First of all, thank you for maintaining this amazing library!
Description
No problem when importing as usual.

In Next.js, needs to use Dynamic Import to prevent SSR.
Doing so will result in a Stage type loss and a type error.

Steps to reproduce
See in codesandbox.
https://codesandbox.io/s/sharp-snow-u2xev?file=/pages/index.tsx

Install dependencies.
Dynamic import Stage from @inlet/react-pixi.
Add attributes to Stage.

Additional info

@inlet/react-pixi version: 6.0.9
React version: 17.0.1
ReactDOM version: 17.0.1
PIXI version: 5.3.7

Thanks @eai04191
The problem is that next's dynamic import doesn't preserve typings. What you could do is wrap it in a separate component, here's an example: https://codesandbox.io/s/next-js-react-pixi-jcmt1


NOISSUE - Add comparing docs in CI

Signed-off-by: 0x6f736f646f<EMAIL_ADDRESS>What does this do?
It add CI pipeline to check if the docs are in sync or not
Which issue(s) does this PR fix/relate to?
No
List any changes that modify/break current functionality
No
Have you included tests for your changes?
No
Did you document any new/modified functionality?
Done here
Notes
With reference to #36

Let's check it after reviewing #35

@0x6f736f646f CI is failing

@dusanb94 I am using lazydocs and it isn't available for python version 3.5 as indicated by the test errors here
We have two options:

Do away with lazydocs and remain with the initial docs generator
Use lazydocs and drop support for python version 3.5

Keep in mind lazydocs is able to do Source Code Linking as indicated here

@dusanb94 I am using lazydocs and it isn't available for python version 3.5 as indicated by the test errors here
We have two options:

Do away with lazydocs and remain with the initial docs generator
Use lazydocs and drop support for python version 3.5

Keep in mind lazydocs is able to do Source Code Linking as indicated here

@0x6f736f646f Is it possible to check docs in a separate job, not for each test env? We only need it to keep docs up to date, so we don't have to generate docs for each OS and Python version, really.

@dusanb94 I am using lazydocs and it isn't available for python version 3.5 as indicated by the test errors here
We have two options:

Do away with lazydocs and remain with the initial docs generator
Use lazydocs and drop support for python version 3.5

Keep in mind lazydocs is able to do Source Code Linking as indicated here

@0x6f736f646f Is it possible to check docs in a separate job, not for each test env? We only need it to keep docs up to date, so we don't have to generate docs for each OS and Python version, really.

Yes it is possible

Resolves #37


Remove clip content to prevent outlining cut.

Checking "clip_content" to false fix this "bug".

Confirmed, its a good change. Merging it in


[Release] v0.11.0 release schedule

In order to continue with our agreed release cycle as per discussion in RFC#67 , I'd like to propose a schedule for our next TVM release: v0.11.0.
This schedule is tentative and may change as we progress through the process. In case dates change, this thread will be kept updated.
The proposed schedule is:

[x] ~12~ 13 December 2022 - a branch v0.11.0 to be created from main

Done in https://github.com/apache/tvm/tree/v0.11.0

[x] ~12~ 13 December 2022 - a tag v0.12.dev0 to be created, marking the beginning of the next development cycle

v0.12.0 points to 12311dcdefd7f2213ce5ce78f2c5904
https://github.com/apache/tvm/tree/v0.12.dev0

[x] 16 December 2022 - cherry-picking soft deadline

during this time any reasonable change can be merged, comment on this issue with the commit you would like added to the release branch

[x] ~04~ 06 January 2023 - cherry-picking hard deadline

during this time only critical changes will be merged, comment on this issue with the commit you would like added to the release branch as well as the reasoning for adding it

[x] ~1 February 2023 - Draft release notes published -  https://github.com/apache/tvm/issues/13899
[ ] 2 February 2023 - RC package uploaded
[ ] ~2 February 2023 - release voting opens
[ ] ~13 February 2023 - release date

Note: for this specific release, given we'll have the end of the year period, I've extended the cherry-picking hard deadline in 1 week, so that we some more time to consider patches to be included.
Call for release managers: in case you want to be involved in upcoming releases, please manifest your interest in this thread and we'll try to organise.
See also:

Release steps
TVM release process docs.

cc @apache/tvm-committers @driazati @areusch @Mousius @tqchen @AndrewZhaoLuo

@apache/tvm-committers Just a reminder that today is the last day to have fixes and PRs ported to the v0.11.0 branch. Let me know.

we discussed the release in the community meeting this morning. here are notes:

release is running late. @leandron will update the schedule
branch created, current status is past the hard deadline for cherry-picks. can still get a few last commits in given we are behind (but speak up soon).
still need to put the release notes together, we have a script but it may need some edits (it can be tough to get prose from various parties to summarize the changes).
note: tests/scripts/release script has mostly been tested on mac.
if you want to try out the 0.11 prerelease wheel, it's built on pypi and you can try it with pip install --pre apache-tvm~=0.11. we will also upload the prerelease tarball before opening a vote thread.

I'm picking this up and facing an issue with protected branches when trying to cherry-pick #13624 into v0.11.0 - any idea how to solve that?
$ git push -f upstream v0.11.0
Enumerating objects: 42, done.
Counting objects: 100% (42/42), done.
Delta compression using up to 8 threads
Compressing objects: 100% (19/19), done.
Writing objects: 100% (23/23), 3.97 KiB | 1.32 MiB/s, done.
Total 23 (delta 18), reused 5 (delta 4), pack-reused 0
remote: Resolving deltas: 100% (18/18), completed with 18 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/v0.11.0.
remote: error: At least 1 approving review is required by reviewers with write access. Commits must have valid signatures.
To github.com:apache/tvm.git
 ! [remote rejected]     v0.11.0 -> v0.11.0 (protected branch hook declined)
error: failed to push some refs to 'github.com:apache/tvm.git'

$ git push --delete upstream v0.11.0
remote: error: GH006: Protected branch update failed for refs/heads/v0.11.0.
remote: error: Cannot delete this protected branch
To github.com:apache/tvm.git
 ! [remote rejected]     v0.11.0 (protected branch hook declined)
error: failed to push some refs to 'github.com:apache/tvm.git'

cc @driazati

The release branches are protected from force pushes / deletes by GitHub, but cherry-picking shouldn't require rewriting history right? Are you doing something like this?
git fetch origin
git checkout v0.11.0
git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e
git push origin

Can we ensure a date that this release will be completed? So the downstream organization can decide whether sync this release to our internal or not, thanks.

Can we ensure a date that this release will be completed? So the downstream organization can decide whether sync this release to our internal or not, thanks.

I'm working on this at the moment, and will update here as soon as it's ready for review/vote. thanks.

The release branches are protected from force pushes / deletes by GitHub, but cherry-picking shouldn't require rewriting history right? Are you doing something like this?
git fetch origin
git checkout v0.11.0
git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e
git push origin

I was just trying to produce the tarball with the actual v0.11.0 with that cherry-picked commit, but I'm probably missing something:
% git remote -v
origin	git@github.com:leandron/tvm.git (fetch)
origin	git@github.com:leandron/tvm.git (push)
upstream	git@github.com:apache/tvm.git (fetch)
upstream	git@github.com:apache/tvm.git (push)

% git fetch upstream
% git checkout upstream/v0.11.0

% git reset --hard upstream/v0.11.0
HEAD is now at 1d9863470 [TIR] Fix PlanAndUpdateBufferAllocationLocation not visiting constant buffer (#13605)

% git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e
[v0.11.0 2f999d62e] [BugFix][UMA] Protect target registration (#13624)
 Author: Balint Cristian<EMAIL_ADDRESS> Date: Fri Dec 16 15:23:26 2022 +0200
 4 files changed, 42 insertions(+), 16 deletions(-)

% git push upstream v0.11.0
Enumerating objects: 42, done.
Counting objects: 100% (42/42), done.
Delta compression using up to 8 threads
Compressing objects: 100% (19/19), done.
Writing objects: 100% (23/23), 3.93 KiB | 3.93 MiB/s, done.
Total 23 (delta 18), reused 5 (delta 4), pack-reused 0
remote: Resolving deltas: 100% (18/18), completed with 18 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/v0.11.0.
remote: error: At least 1 approving review is required by reviewers with write access. Commits must have valid signatures.
To github.com:apache/tvm.git
 ! [remote rejected]     v0.11.0 -> v0.11.0 (protected branch hook declined)
error: failed to push some refs to 'github.com:apache/tvm.git'
%

i have asked asf-infra whether perhaps gitbox has misconfigured our branch protection. i'm not able to view that natively in the GH UI, i believe, so i'm left to deduce what i can from the asf.yaml and associated docs.

okay, traced this down with the help of asf infra. it appears we tried to configure this in .asf.yaml last Oct, but GH API didn't support configuring branch patterns. @driazati filed a ticket about this and they manually configured it for us. there do exist some .asf.yaml in fix_typo and alter/fix_gpu_other_build branches with the pattern indicated, but this is a red herring as according to asf infra, branch protection is only configured from canonical branches - that means:

master
main
your default branch

it seems like the problem here is most likely the requirement of code review on those branches. shall we ask ASF infra to remove that requirement and see if that allows us to cherry-pick existing commits? we would need to probably add something about only pushing reviewed commits in that case; also need to address how to verify CI as well, but likely that's not much change from present as you'd want to look at the post-merge build.

Looks like the GH branch protection is kicking in , kind of like : https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging
Alternatively, you could do a PR to the branch (and merge it)?

This should work for what we need to do and avoid the branch protection issues, has this been tried yet? We should keep the release branches protected IMO so they don't get updated without anyone knowing

Delay again

@leandron so...

Any updates?

Hi. I'm sorry, this is a bit frustrating... you can still checkout the v0.11.0 branch to checkout the contents of the release. I'm working through some issues to be able to do the release, as you can see in the discussions above.
I'll update here when I'm able to push on v0.11.0 branch and the proceed with the release vote. In this meantime, I've shared the Release Notes, you can have a look. Is there anything specific you that is blocking you @HLearning?

Seems like we can still do cherrypick PR and merge that to v0.11.0 instead of directly push. Happy to help on this and drive the release in case that is a blocker

https://github.com/apache/tvm/pull/14057 is now merged with cherry pick.

#14057 is now merged with cherry pick.

Can you share the list of commands you ran to merge this? Perhaps we should adjust the Release guideline with that? You can see the commands I was running above, when I'm describing the issue I'm facing that.

I just do git rebase to pick the commits onto top
git checkout [the-commit]
git rebase --onto [branch] HEAD~1

There might be other commands to cherry pick as well. In future perhaps we could try a staging branch before we finalize and put  things under the release branch. Let us still if there are still blockers atm

Hi. I'm sorry, this is a bit frustrating... you can still checkout the v0.11.0 branch to checkout the contents of the release. I'm working through some issues to be able to do the release, as you can see in the discussions above.
I'll update here when I'm able to push on v0.11.0 branch and the proceed with the release vote. In this meantime, I've shared the Release Notes, you can have a look. Is there anything specific you that is blocking you @HLearning?

I need a recent packaged version

The vote has opened for the release candidate: https://github.com/apache/tvm/issues/14129

I've just published v0.11.0 as latest release here in GitHub, and at this moment I'm dealing with announcing it at Apache and getting some help to update the website.
Here is the link for the GitHub releases: https://github.com/apache/tvm/releases

Unfortunately I encountered a problem when trying to publish the wheels for v0.11.0:
$ venv/bin/python3
Python 3.8.10 (default, Nov 14 2022, 12:59:47)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tvm
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/__init__.py", line 79, in <module>
    from . import micro
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/micro/__init__.py", line 23, in <module>
    from .model_library_format import (
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/micro/model_library_format.py", line 34, in <module>
    from ..relay.backend import executor_factory
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/relay/__init__.py", line 29, in <module>
    from . import prelude
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/relay/prelude.py", line 21, in <module>
    from tvm.relay.transform import ToANormalFormExpr
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/relay/transform/__init__.py", line 20, in <module>
    from .transform import *
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/relay/transform/transform.py", line 30, in <module>
    from ..backend.utils import mangle_module_name
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/relay/backend/__init__.py", line 18, in <module>
    from . import te_compiler
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/relay/backend/te_compiler.py", line 27, in <module>
    from tvm.meta_schedule import is_meta_schedule_enabled
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/meta_schedule/__init__.py", line 18, in <module>
    from . import (
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/meta_schedule/builder/__init__.py", line 22, in <module>
    from .builder import Builder, BuilderInput, BuilderResult, PyBuilder, create
  File "/home/areusch/ws/tlcpack/venv/lib/python3.8/site-packages/tvm/meta_schedule/builder/builder.py", line 21, in <module>
    from typing_extensions import Literal
ModuleNotFoundError: No module named 'typing_extensions'

This is a hole in our CI testing/release process we should plug. We'll need to make a slight tweak to the python install_requires and release a v0.11.1. There aren't any functionality changes expected other than fixing the missing typing_extensions package, so folks don't need to block on this unless they depend on pip3 install apache-tvm.
#14244 fixes this in the release branch.


Check 1: User Guide

First check for user guide.
Important things to note:

I have changed the naming for the different parts of our GUI to be in accordance with our class names
Constraints have been changed to Rules to make it simpler
Figure numbers are not updated
Line breaks have yet to be added
Added @@author tags accordingly

Should we use "rule" or "constraints"? "Rule" doesnt sound specific enough.

Should we use "rule" or "constraints"? "Rule" doesnt sound specific enough.

I chose rule because it sounds simpler, from the CS2101 feedback someone said constraints a bit complicated. I don't mind changing back to constraints if you guys think it's better. @potty10

We can discuss it later. LGTM!


0.7-beta Resource isnt updated with source signal

Describe the bug
Resource isnt updated with source signal
async fn create_list(i: usize) -> Vec<String> {
    if i % 2 == 0 {
        log!("create even list");
        vec![
            String::from("Hello,"),
            String::from("Dave"),
            String::from("and"),
            String::from("the"),
            String::from("green"),
            String::from("World"),
        ]
    } else {
        log!("create uneven list");
        vec![String::from("Ehm")]
    }
}

#[component]
pub fn App() -> impl IntoView {
    let (counter, mut_counter) = signal(0);

    let list = Resource::new(move || counter.get(), create_list);

    Effect::new(move |_| {
        log!("{:?}", list.get());
    });

    Effect::new(move |_| {
        log!("{:?}", counter.get());
    });

    view! {

            {move || counter.get()}
            <button on:click=move |_| {
                log!("click");
                mut_counter.update(|counter| {
                    *counter += 1;
                });
            }>"Click here!"</button>

            {move || list.get()}

    }
}

Leptos Dependencies
leptos = { git = "https://github.com/leptos-rs/leptos.git", branch = "leptos_0.7" }
leptos_axum = { git = "https://github.com/leptos-rs/leptos.git", branch = "leptos_0.7" }
leptos_meta = { git = "https://github.com/leptos-rs/leptos.git", branch = "leptos_0.7" }
leptos_router = { git = "https://github.com/leptos-rs/leptos.git", branch = "leptos_0.7" }

at the time of commit 4bc999ead36ab9eeb2b80e13ef945b343e9e3393
To Reproduce
Click the button. The list doesnt change.
On the first click the fetcher refires, but the counter passed into the fetcher is not incremented, yet.
All subsequent clicks it doesnt refetch.
Expected behavior
When clicking the button, it should toggle between "Ehm" and "Hello,DaveandthegreenWorld"
Additional Context
Take a look at the console logs

I think a better example is
#[server]
pub async fn create_server_list(i: usize) -> Result<Vec<String>, ServerFnError> {
    if i % 2 == 0 {
        log!("create even list");
        Ok(vec![
            String::from("Hello,"),
            String::from("Dave"),
            String::from("and"),
            String::from("the"),
            String::from("green"),
            String::from("World"),
        ])
    } else {
        log!("create uneven list");
        Ok(vec![String::from("Ehm")])
    }
}

#[component]
pub fn App() -> impl IntoView {
    let (counter, mut_counter) = signal(0);

    //let list = Resource::new(move || counter.get(), create_server_list);
    let list = LocalResource::new(move || async move { create_server_list(counter.get()).await });

    Effect::new(move |_| {
        log!("{:?}", list.get());
    });

    Effect::new(move |_| {
        log!("{:?}", counter.get());
    });

    view! {

            {move || counter.get()}
            <button on:click=move |_| {
                log!("click");
                mut_counter.update(|counter| {
                    *counter += 1;
                });
            }>"Click here!"</button>

            <Suspense>
                {move || list.get()}
            </Suspense>

    }
}

Where LocalResource works, but Resource doesnt

Thanks, this is a good issue to find. I've been investigating it today and it's a bit tricky, but I'll figure it out. Strangely, the source signals for examples like the todo_app_sqlite ones do work. It looks like the effect is triggering twice per change, which may be part of it. (I think the same issue may drive #2721 but we'll see.)

I believe this should be fixed by 5d09cd1, but I don't think #2721 is fixed yet.


requirements: add initial document

Adding initial kata requirements list, based off of discussion from
kata-containers/runtime issue #31.
Signed-off-by: Eric Ernst<EMAIL_ADDRESS>

@sameo @klynnrif @gnawux @jessfraz @tallclair  - FYI.

@egernst How about change the title to "design principles" or something else?

@gnawux I ended up changing the heading to Design requirements (was mandatory requirements) and removed the empty optional section.  This okay with you (you mentioned design principles before)?
I think that requirements are required; mandatory and optional is a bit odd there, and given that we didn't have any optional ones, it shouldn't be too controversial.

@jodh-intel -- I didn't add the TLA dictionary addendum; let me know if you think this is still necessary and if you want to add such a section as an example :)

@egernst I am ok with the name change, good job.

@klynnrif - PTAL?

lgtm


fix(deps): add upper-bound google-auth dependency

For consistency with google-api-core, which specifies
google-auth >= 1.21.1, < 2.0dev as a dependency.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #1179 🦕

@googlebot I signed it!

@busunkim96 do you know why this failed the build? There's a unit test failure on tests/test__auth.py:92 but admittedly I am not familiar with this project, and don't know why this change would cause such a failure.

The build failure is unrelated to this PR. The build fails with pip install google-auth==1.25.0 or greater.
With google-auth==1.25.0, the following test fails.
tests/test__auth.py::TestAuthWithGoogleAuth::test_with_scopes_scoped FAILED

With google-auth==1.24.0 , the same test passes.
tests/test__auth.py::TestAuthWithGoogleAuth::test_with_scopes_scoped PASSED

I've created issue #1198 to track the unittest failure since it's unrelated to this PR.

There was no Kokoro build this time, does that have to be started manually?
Thanks for fixing the other issue and merging the fix in here, appreciate it.

There was no Kokoro build this time, does that need to be started manually?
Thanks for fixing the other issue and for merging it in here, appreciate it.


[AppBar] Scrolls off the page

Hi there,
According to your description of AppBar: "App bars are a collection of components placed as a static header for an application", I was thinking that the AppBar wouldn't scroll off the page when you put a long list below it, let's say.  But it does.  See this example if you'd like: http://www.donwoodlock.com/TextDon/index.html
Is there a property I should set to keep it fixed on top?  Or a particular wrapper I should use for everything else to create a designated scrolling area?
Please advise.  Thx.
Don

This, and for tabs too.

@dwoodlock although that should not have happened, before we look into it, one possible workaround might be to put style={{position: 'fixed'}} as an attribute to your AppBar component.
Let me know how that works!

That works a little bit. When you do a fixed position element as you know, the browser doesn't leave room for it.  So since I have:

the first item on the my list is hidden under the AppBar.  I'm sure I can do something that I'd rather not do like query the DOM to figure out the height of that AppBar and put a box underneath it to accommodate.  Let me know if you think that might be best - otherwise I'll await your investigation on this.
Don

@dwoodlock I think that's what you might have to do. You could apply the position: 'fixed' style conditionally (only when you have scrolled past the appbar) like so: http://www.hongkiat.com/blog/css-sticky-position/
I'll leave this to @oliviertassinari and @hai-cea if they have a better suggestion.

I'm using the approach you describe: a position fixed and a paddingTop. Works fine for me. I can't find a better one.

Thanks.  I'll either do the sticky positioning techniques from your article or the fixed positioning with the paddingTop like Olivier suggests.  @oliviertassinari - I'm assuming what you are doing is checking the height of the AppBar after it has been mounted and then adding paddingTop of that height to the component right below it?  I was hoping not to query the DOM but that's my interpretation of that solution - is that correct?

@dwoodlock I'm not computing the height of the AppBar. I'm using a static value. So It was simpler for me to just use fixed position.
If the height of your AppBar change. I suggest you you to try flex box. It should be working (this is what I should be doing too).

OK - I have enough to go on and build a workaround.  Ideally it would be great if someone more talented than me could change AppBar to actually match this description: "App bars are a collection of components placed as a static header for an application" and not have it scroll off the page.  I'm not sure I could make that change reliably to this library.  But I appreciate everyone's tips: I ended up writing a FixedAppBar component that renders an AppBar in a fixed div and renders a box underneath it with the same height as the AppBar. That worked for me.

Haha I hear you @dwoodlock! I'm re-writing AppBar these days, and I'll see if I can include some logic to accomplish that. Feel free to close this issue if your problem has been solved :-)

@dwoodlock @oliviertassinari this is a good package: https://www.npmjs.com/package/react-sticky
I'll probably end up using this in the AppBar code too.

I think that react-sticky doesn't resolve the content overflow.
The question is, do we want MUI to have layout? I would say no, than having simple component as AppBar that just render correctly in his available space sound fine for me.

@oliviertassinari I'm fine either way.  I was just thinking based on the documentation that the AppBar would stay at the top and not scroll.  But like I said I was able to write a FixedAppBar component that does that by leveraging the real AppBar, making it fixed position, and drawing a box of the same height next (basically underneath it) so my FixedAppBar would take up space in the flow.

@dwoodlock Can you please share your FixedAppBar solution as a gist or something?

@prashaantt checkout that comment https://github.com/callemall/material-ui/pull/1321#issuecomment-174108805

            Hi Prashant,
            Here’s the gist for what I did.  It is no fancy, elegant, or generic.  But in short:

     I did not make any changes to the material-ui Toolbar component.

     I created a mainAppToolbar.js component for my app – that code is in the gist.  There is a bunch of code in there that pertains to my app – so it’s not a generic component.

     In the styles (near the top), I made the toolbar ‘position: fixed’ at the top.

     In the render, I added a <div> right after the toolbar with a height the same as the toolbar.  Because the toolbar is fixed position, it’s taken out of the flow, so this box also ‘appears’ at the top of the page underneath the toolbar.  That means the next element (the first visible element) appears below the toolbar which is what I wanted.

     So the solution:

o   Keeps the toolbar on the top of the page – because of fixed positioning.
o   Has the content below the toolbar (because of the box) so it’s all visible and everything scrolls beneath the toolbar.
The only problem I haven’t solved with this is when you start the app on an iOS device when another app has taken some space on the top of the phone (like you are in a phone call), then the webview gets painted a little lower on the phone if the user starts your app.  Then when you hang up the phone, it doesn’t properly move everything up.  It’s not the most popular use case for me, but at some point I may figure out a fix.
Hope that helps.
Don
https://gist.github.com/dwoodlock/060546b94b1db6b7d723
From: Prashant Tiwari<EMAIL_ADDRESS>Sent: Thursday, February 18, 2016 2:07 AM
To: callemall/material-ui
Cc: Woodlock, Don (GE Healthcare)
Subject: Re: [material-ui] AppBar scrolls off the page (#1792)
@dwoodlockhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dwoodlock&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=bQuLCd7b2ehAXCAD1aeNrx49BkqReEHGd3hsO2qFScQ&m=55xK2oOD6q684JdvSZqRkIirdc5rzP-aLhhGWI1ciHA&s=74fp5T3RPTumJT2ZZLou5VvHBE2cMilq72Td9NEE6KY&e= Can you please share your FixedAppBar solution as a gist or something?
—
Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_callemall_material-2Dui_issues_1792-23issuecomment-2D185588699&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=bQuLCd7b2ehAXCAD1aeNrx49BkqReEHGd3hsO2qFScQ&m=55xK2oOD6q684JdvSZqRkIirdc5rzP-aLhhGWI1ciHA&s=M5V0i7VJh_pJjGGa20p_mIBC4YMIN6k6ibEwjeLxO1g&e=.

For info, the docs site for this material-ui project has a static app bar and content and a left nav that start after the app bar, rather than underneath it, so that code might provide some inspiration.  The code for the docs site is here: https://github.com/callemall/material-ui/tree/master/docs.

This is still happening with the latest version as of now.

I would love to see some official docs describing the best way to implement this, seems like a pretty common behaviour to me, no?

@mismith Yes, it's. Notice that we are not focusing on the layout with this lib. We need a strong component base first, which we haven't yet 😁 .

Ahh, gotcha. Well can I help with this layout somehow? Is there anything out there already started for what your implementation is going to look like for layouts like this? I'd be happy to throw something together but I don't want to duplicate any existing work (in progress).

There is not work I'm aware of regarding the layouting. We are focusing on the core components. I don't that that we should work on this before the next branch is completed. Just to stay focused.

How is this issue being solved currently? I am also facing the the issue if i set the appbar position as fixed the children content renders underneath the appBar. Calculating the appbar height dynamically  might solve the issue.

@jasan-s To put is simply, I know two ways to solve this issue:

With the positioning approach. You would have to add a position: fixed on the AppBar component
With the flex layouting approach. You would have to build a <ScrollView /> component like.

Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.

That works to the browser platform too.
(I'm using option 2.)

Hey, guys for this issue are there any updates or a better fix ?

Any ideas on the best way to listen to changes in AppBar height? This way the dummy div marginTop can also be responsive.


Add spsmb to list

Link to school website: https://www.spsmb.cz/

@RadekPelikan First stage of verification passed, official domain for Střední průmyslová škola Mladá Boleslav is spsmb.cz as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@RadekPelikan Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.

@philipto thank you very much!


include exception details in tool exit displayed when adb call fails

Fixes #125971
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

In #125971, @DanTup proposes (as an example) including the stack trace, but I feel like this would be pretty noisy to include in a tool exit message. Perhaps we could include the stack trace in a printTrace call, but I am not sure that would appear in the flutter daemon log output surfaced by VS Code. @DanTup, do you know if printTrace output would appear in these logs (i.e. does Dart-Code invoke flutter daemon with the -v flag)?

i.e. does Dart-Code invoke flutter daemon with the -v flag?

It doesn't currently. We could change it, but it does mean there would generally be a lot more output (in normal operation when there are no errors) being sent over to the IDEs to be read/ignored.
Is there a way we could include the stack trace info in the call to throwToolExit that could be handled by the daemon mode and always printed? (flutter daemon is only intended for IDEs, so having error messages be verbose even without -v could be helpful).

i.e. does Dart-Code invoke flutter daemon with the -v flag?

It doesn't currently. We could change it, but it does mean there would generally be a lot more output (in normal operation when there are no errors) being sent over to the IDEs to be read/ignored.

Makes sense.

Is there a way we could include the stack trace info in the call to throwToolExit that could be handled by the daemon mode and always printed? (flutter daemon is only intended for IDEs, so having error messages be verbose even without -v could be helpful).

I think we could augment this conditional (excerpted from the code that handles ToolExits) https://github.com/flutter/flutter/blob/be0eb721d5a0668a32878a16da7a699a8998b7c4/packages/flutter_tools/lib/runner.dart#L176-L178
We could change if (verbose) to if (verbose || args.first == 'daemon') (in an actual implementation, I would try avoid the hard-coded dependency on the name of the command, but I'm keeping this simple). I'm pretty neutral on this since it's not clear how often this will be useful, but I'm down to implement this while I'm here. Any disagreement here, @christopherfujino?

I'm pretty neutral on this since it's not clear how often this will be useful, but I'm down to implement this while I'm here. Any disagreement here, @christopherfujino?

@christopherfujino 😛

I'm pretty neutral on this since it's not clear how often this will be useful, but I'm down to implement this while I'm here. Any disagreement here, @christopherfujino?

@christopherfujino 😛

I'm also fine to just merge this as is since this isn't high priority. If you agree, feel free to reapprove


closes #1186 - removed go generate

this is initial attempt, let me know what you think, if you are happy with the change, I will update the templates that changed recently

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1188   +/-   ##
=======================================
  Coverage   36.22%   36.22%
=======================================
  Files          63       63
  Lines        3821     3821
=======================================
  Hits         1384     1384
  Misses       2223     2223
  Partials      214      214

Impacted Files
Coverage Δ

core/nodepool/config/config.go
28.12% <ø> (ø)
:arrow_up:

core/controlplane/config/config.go
62.13% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e61fae4...5f27899. Read the comment docs.

ok, up to date with master, all tests are passing


after installing the react-native-my-sql-connection i am getting this error. And not able to find any solution

resolved?


Add support for using PETSc preconditioners and solvers

This PR extends the MFEM PETSc wrappers to allow PETSc solvers to be used interchangeably with the existing MFEM solvers with minimal conversion of matrix types (at most once per Newton step). Most importantly, this allows the use of PETSc's geometric algebraic multigrid with a properly set near null space for elasticity and PETSc's hierarchical multigrid which uses GAMG on each of the components of a multi-component PDE.
Additionally, this allows for using the nonlinear and linear solvers available in PETSc alongside existing MFEM solvers and preconditioners.

Just to be clear after making several comments. I only care about consistency in the capitalization of PETSc. I would be fine to have one that matches MFEM's use and then have comments and strings be the correct one, or swapping over to the correct one entirely. If anyone else has strong opinions please say so now.

Just to be clear after making several comments. I only care about consistency in the capitalization of PETSc. I would be fine to have one that matches MFEM's use and then have comments and strings be the correct one, or swapping over to the correct one entirely. If anyone else has strong opinions please say so now.

PETSc typically uses the correct capitalization (PETSc) in documentation and comments, while using Petsc in function names for clarity.


anypoint code builder improvements

some anypoint code builder improvements you can think about:

invest in webview 2.0 not webview.
decouple the app and the vscode extension. You have to create a local sever (connector) that interacts with vscode apis. The server gets requests from the app and send them to vscode. With this approach the builder can be opened in "window mode" using a browser or an electron app.

add a new config prop called "window mode" so that people can use this feature only if they want it.

I think you will be able to do window mode soon with native vscode apis. The latest version allow users to create floating windows by just dragging certain editor tabs to another window or desktop.


How to share the group call directly to Youtube Stream?

I have tried to follow this example. But sadly it is telling nothing about exact instruction for Youtube stream.
I also tried to implement some of this methods on client but getting error. Not working at all.
Can anyone give me any straight forward exmple to pass the group call stream directly to Youtube stream?

@kamal-hossain you can follow these steps:
let LiveTranscoding = {} // you need to create the transcoding config
client.setLiveTranscoding(LiveTranscoding); // set the config
client.startLiveStreaming("rtmp://a.rtmp.youtube.com/livexxxxxxxxxxxxxxxx", true) // add your rtmp url for YouTube
// your stream should appear on youtube in a couple seconds if your config is correct

// when you want to update the transcoding config
client.setLiveTranscoding(newConfig);
// when you want to stop
client.stopLiveStreaming("your RTMP URL")

For an example config you can view the doc. Make sure your remote UIDs are correct.
If you need more help, please join our community slack.


Add balance to account

As bank accound provider
I want bank accounts to have a balance
so customers can transfer money
Hints:

use a domain object "money" as balance type (wrapping a BigDecimal)
don't care about currency for now

Pull Request: https://github.com/holixon/cqrs-meets-hexagonal/pull/27/files


Add tricky expression on object expression

except object key interpolation if property value is member expression
const ObjectInterpolationMember = p => {
  const theme = useTheme()
  const color = 'red'

  return (
    <p
      css={{
        color: theme.colors[color],
      }}
    >
      H
    </p>
  )
}

@probablyup 👀


Policy Report PDF Generation

The policy reporter can already generate a programmatic view, and/or a UI view for the policy statuses, but as a feature request I'd really love to see some level of PDF generation (or similar exec-friendly file type) to be able to easily generate "pretty pictures" of the policy reports through the clusters.

Thanks for your request, what be an HTML report / representation also work for you? Like the HTML templates for the email reports?
What kind of information you would like to see?

Okay,I understand the basic idea but it's not that easy of me to understand what kind of structure of the data would achieve your needs.
Example:
Shows the current E-Mail Report with the basic information about policy reports but if I understand your requirements right, you would need a more fine grained structure per App / Namespace / Policy ?

Honestly that looks great. But yeah I'd want to generate on a per namespace, and per policy basis. So that I can get a report for validations of a single policy across the entire cluster, single policy in a single namespace, all policies in a single namespace, and all policies in the entire cluster.
I don't know if I care about an "app", I think having just namespaced structures would be quite acceptable.

Sorry for the late response. I think I got your requirements. I will work on prototype in the next week, as soon as I find some time. Would you like to have an API with different parameters to configure the report, (select namespaces, policies, grouped-by, etc) and/or an integration in the UI with the configuration and an "download" action?

Current state of the reports

Summary for results per Policy / Namespace / Rule
Details about the status of each resources per namespace

The new HTML Reports are released with Helm Version v2.14.0


Microsoft Azure VM Backup - File Recovery OsName not recognized if your os

Background, we had a power user take a linux vm and generalize it, turn it into an image. A process that is irreversible. Then he deleted that image.
So now I'm doing a file recovery from the VM as we had daily Azure Backups running. Every backup since that time has been Crash-Consistent.
So I decided to do a File Recovery starting with the latest File-Consistent backup. The first time I downloaded and ran the python script on a Linux vm in the same subnet, it ran fine.
Now every subsequent time I've tried to do a File Recovery from another backup it fails and I get an error
Microsoft Azure VM Backup - File Recovery
______________________________________________
OsName not recognized if your os is in the list 'Ubuntu', 'Debian', 'CentOS', 'RHEL', 'SLES', 'OpenSUSE', 'Oracle'.
 Please enter OsName as they appear in the list
Enter you os name:

I searched for this but could not fine any mention or resolutions of this issue. Any help is greatly appreciated. I even tried to update the python azure libraries such as pip install azure-mgmt-compute but no luck.
Thank you.
-rw-r-----. 1 localadmin localadmin 67406 Jul 11 00:02 ulapala001_cus_583553472800346609_615550966878_1608fc7097104a14805cc130dd5059c455f37dd7a0c987.py
[root@ulapapp002 tmp]# python ulapala001_cus_583553472800346609_615550966878_1608fc7097104a14805cc130dd5059c455f37dd7a0c987.py
Microsoft Azure VM Backup - File Recovery
______________________________________________
OsName not recognized if your os is in the list 'Ubuntu', 'Debian', 'CentOS', 'RHEL', 'SLES', 'OpenSUSE', 'Oracle'.
 Please enter OsName as they appear in the list
Enter you os name: RHEL
The script requires 'iscsi-initiator-utils' to run
Do you want us to install 'iscsi-initiator-utils' on this machine?
Please press 'Y' to continue with installation, 'N' to abort the operation. : Y
Loaded plugins: langpacks, product-id, search-disabled-repos
Fiserv-Hardening                                                                                | 2.9 kB  00:00:00
rhui-microsoft-azure-rhel7                                                                                | 2.1 kB  00:00:00
rhui-rhel-7-server-dotnet-rhui-rpms                                                                                | 4.2 kB  00:00:00
rhui-rhel-7-server-rhui-extras-rpms                                                                                | 2.0 kB  00:00:00
rhui-rhel-7-server-rhui-rh-common-rpms                                                                                | 2.1 kB  00:00:00
rhui-rhel-7-server-rhui-rpms                                                                                | 2.0 kB  00:00:00
rhui-rhel-7-server-rhui-supplementary-rpms                                                                                | 2.0 kB  00:00:00
rhui-rhel-server-rhui-rhscl-7-rpms                                                                                | 2.0 kB  00:00:00
Resolving Dependencies
--> Running transaction check
---> Package iscsi-initiator-utils.x86_64 0:<IP_ADDRESS>4-20.el7_9 will be installed
--> Processing Dependency: iscsi-initiator-utils-iscsiuio >= <IP_ADDRESS>4-20.el7_9 for package: iscsi-initiator-utils-<IP_ADDRESS>4-20.el7_9.x86_64
--> Running transaction check
---> Package iscsi-initiator-utils-iscsiuio.x86_64 0:<IP_ADDRESS>4-20.el7_9 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================================================================================================================================
 Package                                                Arch                           Version                                    Repository                                            Size
=============================================================================================================================================================================================
Installing:
 iscsi-initiator-utils                                  x86_64                         <IP_ADDRESS>4-20.el7_9                         rhui-rhel-7-server-rhui-rpms                         423 k
Installing for dependencies:
 iscsi-initiator-utils-iscsiuio                         x86_64                         <IP_ADDRESS>4-20.el7_9                         rhui-rhel-7-server-rhui-rpms                          94 k

Transaction Summary
=============================================================================================================================================================================================
Install  1 Package (+1 Dependent package)

Total download size: 517 k
Installed size: 2.5 M
Downloading packages:
(1/2): iscsi-initiator-utils-<IP_ADDRESS>4-20.el7_9.x86_64.rpm                                                                                | 423 kB  00:00:00
(2/2): iscsi-initiator-utils-iscsiuio-<IP_ADDRESS>4-20.el7_9.x86_64.rpm                                                                                |  94 kB  00:00:00
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                839 kB/s | 517 kB  00:00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : iscsi-initiator-utils-<IP_ADDRESS>4-20.el7_9.x86_64                                                                                1/2
  Installing : iscsi-initiator-utils-iscsiuio-<IP_ADDRESS>4-20.el7_9.x86_64                                                                                2/2
  Verifying  : iscsi-initiator-utils-iscsiuio-<IP_ADDRESS>4-20.el7_9.x86_64                                                                                1/2
  Verifying  : iscsi-initiator-utils-<IP_ADDRESS>4-20.el7_9.x86_64                                                                                2/2

Installed:
  iscsi-initiator-utils.x86_64 0:<IP_ADDRESS>4-20.el7_9

Dependency Installed:
  iscsi-initiator-utils-iscsiuio.x86_64 0:<IP_ADDRESS>4-20.el7_9

Complete!
Traceback (most recent call last):
  File "ulapala001_cus_583553472800346609_615550966878_1608fc7097104a14805cc130dd5059c455f37dd7a0c987.py", line 1352, in <module>
    main(sys.argv[1:])
  File "ulapala001_cus_583553472800346609_615550966878_1608fc7097104a14805cc130dd5059c455f37dd7a0c987.py", line 1314, in main
    "OsNameVersion" : OsName + ";" + Version + ";",
UnboundLocalError: local variable 'Version' referenced before assignment

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

@aakashrami -  Thank you for your question.
Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

@aakashrami - Thank you for your question.
Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

@aakashrami - Since we have not heard back from you we will now proceed to close this thread.
However if you can share additional information regarding the documentation you are referring and circle back on this thread , we will gladly reopen the issue and continue the discussion. Thank you.


6-fold CV on S3DIS.

Hello! I want to know how to carry 6-fold CV on S3DIS?
Thank you very much!

hi @zhangguanghui1, you need to train/test 6 models in total, i.e.,  (1) train on Area23456, test on Area1, ...,  (6) train on Area12345, test on Area6. The final results are the unweighted average of the 6 testing splits.


Doesn't seem to work with distributed.

I tried some basic stuff with a dask_kubernetes on ocean.pangeo.io. No luck.
I created a cluster and connected to it, created a gdrivefs, and the tried to read / write via xarray. I immediately get a KilledWorker.
Sorry for not providing a reproducible example. The only example I know how to make is probably too complicated. I figured you would know how to do a proper test of distributed instead of whatever hack I come up with.

I haven't tried, but I assume you would need to copy the pickled token file to all workers.
On November 16, 2019 12:10:30 AM EST, Ryan Abernathey<EMAIL_ADDRESS>wrote:

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/intake/gdrivefs/issues/8

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

The following worked for me:
import fsspec
from gdrivefs import core
fsspec.registry['gdrive'] = core.GoogleDriveFileSystem

import dask.bag as db
from dask.distributed import Client
c = Client()
b = db.read_text('gdrive://*.md', storage_options={'token': 'cache'})
b.compute()

(in my case this was two files, and resulted in text output, as expected)


how do in middleware use app_data?

when i want read cookie and from redis read it time

Hi @Zheby!
Could you clarify, what framework do you use? actix-web?
If so, extractor interface  is async fn extract(req: &ServiceRequest) -> Result<HashSet<String>, Error>
Thus, ServiceRequest has a method app_data (documentation ref), does it work for you?
Probably I misunderstood something, in that case could you provide some MRE(pseudo-code) of what you want to achieve?
Thanks for using/trying the crate!

ep i use
 let redis_url = format!("redis://{}:{}",
            std::env::var("REDIS_HOST").unwrap(),
            std::env::var("REDIS_PORT").unwrap()
        );
        let client = rustis::client::Client::connect(redis_url).await.unwrap();

when i add client in route
 let auth = GrantsMiddleware::with_extractor(Middleware::extract);
 App::new()
            .app_data(web::Data::new(client.clone()))
           .wrap(auth)

Then, how should I access redis inside

You can access it with app_data (take a look at HttpRequest::app_data as well), right.
Something like that should work for you:
async fn extract(req: &ServiceRequest) -> Result<HashSet<String>, Error> {
  let client: &web::Data<rustis::client::Client> = req.app_data().expect("redis client must present in app_data"); // you can handle `Option` how you wish
  // ... you logic here
}

It's more about actix-web interface rather that extractor itself though.
Let me know if it doesn't work for you

Oh my god, I seem to have found a problem. This needs to be included with web::Data. I'm sorry to bother you, but your create is very good and can make it easier for us to manage permissions.

No worries, glad to help!

your crate is very good and can make it easier for us to manage permissions.
Thank you! Don't hesitate to reach out with any questions


Added WithBuildArgument method to ImageFromDockerfileBuilder

Some images requires arguments for build process. This PR enable to use this option with the framework.

I don't know how to test it. Remember that these kind of variables are present only during build time.


Add user manual examples of some Errors and Warnings

Links for more information on errors or warnings don't actually link to more information. They just redirect to the Umple home page.
I think errors are being sent to the wrong location. For example, when looking at "More Information (1006)" it's trying to redirect to http://umple.org/W1006StateMachineNotParsed.html instead of something along the lines of http://cruise.eecs.uottawa.ca/.

Attached is a spreadsheet showing the status of pages that need updates, mostly to error and warnings pages
ErrorInventory.xlsx


@State templateUrl properties doesn't work any more

Since the refactor, it's not possible to define a templateUrl in the State annotation.
I pointed the change:
https://github.com/pbastowski/angular2-now/commit/9982e46071cf8b28b66f49c0581bffd5ddb5ec53#diff-3e972fd2dbab9f5b4c0af1f0c2447076R127
@State({
  name: "foo",
  url: "/foo",
  controllerAs: "foo",
  templateUrl: "foo.html",
})

after update I get <div ui-view>foo.html<div> instead of the content of foo.html

We must wait for @pbastowski now, he has The Force to publish new version :)

thx, I didn't notice those conditions.


Got some issue while running twitter_streaming.oy

import _ssl             # if we can't import it, let the error propagate
ImportError: DLL load failed: The specified module could not be found.
I got this issue can anyone help here?

Can you provide the full traceback along with any relevant code?
As well as the Tweepy version you're using and information about your environment (Python version, etc.).

I am using Andaconda here with these versions below
Microsoft Windows [Version 10.0.17134.706]

path_val.txt

Thanks for following up.
Based on a quick search of the issue, it seems like this is a known issue with PyCharm, which you seem to be using. According to the issue, it was fixed in version 2019.1.
Alternatively, you can try the steps here: https://stackoverflow.com/a/54240362/6191255
Regardless, this isn't an issue with Tweepy.
GitHub issues for this repository should be used to report issues with this library.
They are not a medium for requesting help with Python, Anaconda, or PyCharm.

Thanks Harmon . I followed the above link and updated Anaconda .
It is working now.


Also export succeed and fail

I have the same trouble at the beginning, but later I guess one reason that fail is not exported by mk.rkt is because libraries like rackunit they already exported a name call fail. In this case, there would be an error if the user imports rackunit and mk.rkt in the same time.


Refactoring storyCleaner and nameCleaner

[ ] Get all the functions and put it in a folder called utilsCleaner in utils. File name should be index.js
[ ] Make all the functions export const ....
[ ] Fix any of the affected files that uses them
[ ] Fix nameCleaner so it's compatible previous versions of node ie node 14.x; for example
To something like .replace(/'/gim, "'")

Hey I could also work this issue! Just to corroborate, the fix for nameCleaner should be implementing a regex search? I looked up what /gim meant and I found out that they are Regex modifiers g(lobal) i(nsensitive) m(ulti-line). I am correct in this assumption? 😅

Hey I could also work this issue! Just to corroborate, the fix for nameCleaner should be implementing a regex search? I looked up what /gim meant and I found out that they are Regex modifiers g(lobal) i(nsensitive) m(ulti-line). I am correct in this assumption? 😅

yea id assume so


Allows exporting to kappa when rules refer to only one compartment

Hello everyone,
I did a workaround for models with one compartment or many but with rules only referring to one compartment. For instance, I took the model MODEL1608100000 from Biomodels. It has two compartments, but the 4 rules refer to only one. The export to kappa isn't allowed because of the model.compartments is non-empty.
The model has no expressions, so I copy the attribute (model.compartments = model.expressions, and because deletion isn't allowed by the exporter). The resulting model in kappa language has @compartment and @compartment: statements, but removing them makes the model executable by KaSim (and also repairing an agent mismatch in rule R3).
It would be useful for the user to declare an option allowing the conversion.
Thanks for your time and best regards.

Thanks for the report. It's possible to manually strip out compartments from a model, see the example code below, which you could use like this: new_model = remove_compartments(model).
Not sure how useful this would be as a helper function in PySB, since it will break model functionality in general. Perhaps @jmuhlich or @lh64 have thoughts on whether something along these lines is worth adding to PySB?
from pysb.core import ComponentSet
import copy

def _remove_compartment_complex_pattern(cp):
    cp.compartment = None
    for mp in cp.monomer_patterns:
        mp.compartment = None

def remove_compartments(model):
    """ Return a new copy of the model with compartments removed """
    model = copy.deepcopy(model)

    for rule in model.rules:
        for cp in rule.reactant_pattern.complex_patterns:
            _remove_compartment_complex_pattern(cp)
        for cp in rule.product_pattern.complex_patterns:
            _remove_compartment_complex_pattern(cp)

    for obs in model.observables:
        for cp in obs.reaction_pattern:
            _remove_compartment_complex_pattern(cp)

    model.compartments = ComponentSet()

    return model


Refactor transaction weight

Followup from https://github.com/rust-bitcoin/rust-bitcoin/pull/1835.  Call predict_weight from weight instead of scaled_size() https://github.com/rust-bitcoin/rust-bitcoin/pull/1835#issuecomment-1543687210.  I think we could also deprecate scaled_size() and strippedsize() in a future refactor.

Also removed checked_weight since seemingly the only purpose was to check that weight was the same as predict_weight which will now always will be true since weight now calls checked_weight.

Can you justify these changes in each commit log please. It is hard to review a PR that says "refactor" when the changes look much more invasive that a refactor.

@tcharding I think this is actually a pure refactor. If you diff both commits at once you can see that it's essentially moving the "manual" predict_weight-based weight function out of a test harness and into weight.
The result is that weight and predict_weight both use the same codepaths, so we can be assured that they're in sync. Though it may make weight a tiny bit slower, I suppose.
It looks like there are a bunch of unit tests, none of which were changed (other than the removal of the check_weight function which just asserted that the old and new code were the same), so I'm reasonably confident that there is no change here.

Cheers


Auto deploy dist as release

Current coverage is 88.04% (diff: 100%)

Merging #141 into develop will increase coverage by 1.51%

@@            develop       #141   diff @@
==========================================
  Files           116        116
  Lines          1960       2308   +348
  Methods          58         64     +6
  Messages          0          0
  Branches        149        194    +45
==========================================
+ Hits           1696       2032   +336
- Misses          206        215     +9
- Partials         58         61     +3

Powered by Codecov. Last update d76a861...c88a8a7


Add device_map={'':0} and ipynb file like colab

1.Changed gradio.Slide's 'minimum=1' which named 'Beam'. ( By transformers, when I tune the 'beam' property to 0, errors happened,  which must equal or bigger than num_beam_groups: Optional[int] = 1)
2.All from_pretrained function added device_map={'':0} to avoid AttributeError: 'NoneType' object has no attribute 'device'.
3.Add 'alpaca_lora.ipynb' to let users run it with jupyter notebook ( Added 'device_map={'':0}' and changed the colab code ).

device_map={'':0} worked well for me for loading int8 models


Ignore commit messages that do not adhere to the format

I am getting an "undefined" printed in the changelog, cause the commit message was and old one not following the format required by generate-changelog
##### Bug Fixes

* **undefined:** remove reference...

That was generated from "Fix: remove reference..."
So it was missing the category capture group.
So https://github.com/lob/generate-changelog/blob/master/lib/git.js#L50 should look like this:
commit.category = parsed[3] || "";
Why do you capture a 3rd capture group that includes the catagory in braces (category). Its not used anywhere.
How about this match pattern?
https://regex101.com/r/tB8sV4/2
It captures 3/2 groups: type/[category]/subject

Hey @pke! Thanks for creating an issue!
The reason that third capture group exists isn't to use it later, but to make the (category) part of the commit message optional. That's why it matches Fix: test. We could use the match pattern that you have in the regex101.com link, but then category will have the parenthesis in it, which isn't desired. We could do an additional commit.category = parsed[3].replace(/[\(\)]/g, '');, but we thought it was a bit cleaner to do it all using capture groups.
As for the undefined category, I agree, it shouldn't be printing * **undefined:**. But instead of defaulting to the empty string, I think the change should go in the writing logic. We can't just use the empty string because that would output * **:** remove reference... when it should just output * remove reference....
Feel free to put up a PR to fix this issue, but if you can't, we'll try to tackle it as soon as we can!

Ok, how about this regex?
https://regex101.com/r/tB8sV4/9
No additional group, relaxed spacing fixes and strict start-words.


Unable to view x grid outside the x domain

When charting something progressing towards a goal, it'd be nice to put an x grid line to pin-point the goal.  Typically that goal exists later (when the x-axis is time) than what is visible in the chart.
For instance, on this demo:  http://c3js.org/samples/grid_x_lines.html
Change any of the x grid value's to something greater than 5 and the line will no longer be visible.

FWIW, I worked around the issue by doing the following:
chart.axis.max({x: max});
chart.internal.config.axis_x_tick_values = chart.internal.x.domain();

The second problem is that the ticks dont render either.

I think you can use flow api because it changes x domain and then the grids will be visible. Can you try it? Example is here: http://c3js.org/samples/api_flow.html
And this seems not a bug, so please let me close and could you ask in GoogleGroup first? https://groups.google.com/forum/#!forum/c3js Thanks.


train and test

hi.thank your code.but i have some question.
your test code only test sigle image and thet train have no psnr or model.vel（）？

There may be some typos in your question, I do not understand what you mean.
I guess you need a test.py to obtain PSNR results.
It's a trivial work, try it yourself.


Unable to Install on Windows

Doesn't matter if I use pip or git clone to install elastalert, when I get to the step python install setup.py I'm getting this error
Installed c:\users\A\appdata\local\programs\python\python36-32\lib\site-packages\elastalert-0.1.14-py3.6.egg
Processing dependencies for elastalert==0.1.14
Searching for blist>=1.3.6
Reading https://pypi.python.org/simple/blist/
Downloading https://pypi.python.org/packages/6b/a8/dca5224abe81ccf8db81f8a2ca3d63e7a5fa7a86adc198d4e268c67ce884/blist-1.
3.6.tar.gz#md5=a538f1a24b9191e3c40252e9397408a9
Best match: blist 1.3.6
Processing blist-1.3.6.tar.gz
Writing C:\Users\A\AppData\Local\Temp\easy_install-fhxg31rk\blist-1.3.6\setup.cfg
Running blist-1.3.6\setup.py -q bdist_egg --dist-dir C:\Users\A\AppData\Local\Temp\easy_install-fhxg31rk\blist-1.3.
6\egg-dist-tmp-jidn1gs_
warning: no files found matching 'blist.rst'
_blist.c
blist/_blist.c(5994): error C2121: '#': invalid character: possibly the result of a macro expansion
blist/_blist.c(5994): error C2065: 'endif': undeclared identifier
blist/_blist.c(5994): warning C4047: 'function': 'Py_ssize_t *' differs in levels of indirection from 'Py_ssize_t'
blist/_blist.c(5994): warning C4024: 'PySlice_Unpack': different types for formal and actual parameter 2
blist/_blist.c(5994): warning C4024: 'PySlice_AdjustIndices': different types for formal and actual parameter 2
blist/_blist.c(6963): error C2121: '#': invalid character: possibly the result of a macro expansion
blist/_blist.c(6963): error C2065: 'endif': undeclared identifier
blist/_blist.c(6963): warning C4047: 'function': 'Py_ssize_t *' differs in levels of indirection from 'Py_ssize_t'
blist/_blist.c(6963): warning C4024: 'PySlice_Unpack': different types for formal and actual parameter 2
blist/_blist.c(6963): warning C4024: 'PySlice_AdjustIndices': different types for formal and actual parameter 2
blist/_blist.c(7743): fatal error C1070: mismatched #if/#endif pair in file 'c:\users\A\appdata\local\temp\easy_ins
tall-fhxg31rk\blist-1.3.6\blist\_blist.c'
error: Setup script exited with error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\cl.exe'
failed with exit status 2

Is there something wrong with the blist file it installs? Not too sure why it involves my Visual Studio.
Thanks.

blist contains C extensions. C extensions need to be compiled. Pre-compiled wheels for blist are available here http://www.lfd.uci.edu/~gohlke/pythonlibs/#blist


How can i send repetition_penalty to my own llm server with openai-go sdk

Hello, i use lmdeploy serve internvl llm model, and i want to use this sdk to send request, and i found there are no repetition_penalty in openai.ChatCompletionNewParams, how can i send repetition_penalty param to my service?

There is no repetition_penalty param because the OpenAI doesn't support it. To send undocumented request params you can use option.WithJSONSet()
https://github.com/openai/openai-go?tab=readme-ov-file#requestoptions