Certificates are not injected anymore after master node migration

Subject of the issue
I have recently migrated master node from on-prem to EC2 by using old master's etcd snapshot following below tutorial on RKE2.

Restoring a Snapshot to New Nodes

Seems like the overall cluster information is migrated & restored properly however autocert certificates are not anymore injected to pods :(
I have deployed autocert through a helm chart initially and to fix this issue tried both autocert uninstall & helm chart Reinstall but everything seems running without errors except the certificates are not anymore injected....
Really appreciate your help
Many Thanks in advance!
Environment

Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.9+rke2r2", GitCommit:"6df4433e288edc9c40c2e344eb336f63fad45cd2", GitTreeState:"clean", BuildDate:"2022-04-28T19:11:38Z", GoVersion:"go1.16.15b7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.9+rke2r2", GitCommit:"6df4433e288edc9c40c2e344eb336f63fad45cd2", GitTreeState:"clean", BuildDate:"2022-04-28T19:11:38Z", GoVersion:"go1.16.15b7", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider or hardware configuration:
c5a.xlarge from AWS EC2
OS (e.g., from /etc/os-release):

NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Kernel (e.g., uname -a):
Linux ip-172-32-74-108 5.13.0-1023-aws #25~20.04.1-Ubuntu SMP Mon Apr 25 19:28:27 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Install tools:

Other:

Steps to reproduce
Install autocert via helm chart & migrate K8s master node

Could it be because of this change?  If so, what should I do to make it use admissionregistration.k8s.io/v1 instead of admissionregistration.k8s.io/v1beta1

@areed Can you confirm if this is still valid for new versions?
https://github.com/smallstep/helm-charts/blob/15d9779c17dafeffbc90010f124deb7d488d814c/autocert/templates/webhook.yaml

@areed Can you confirm if this is still valid for new versions? https://github.com/smallstep/helm-charts/blob/15d9779c17dafeffbc90010f124deb7d488d814c/autocert/templates/webhook.yaml

The only difference in the official helm chart is sideEffects: NoneOnDryRun. I've updated the yaml I posted above to match.

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
metadata:
  annotations:
    meta.helm.sh/release-name: autocert
    meta.helm.sh/release-namespace: akros-cert
  creationTimestamp: "2022-05-18T05:48:29Z"
  generation: 5
  labels:
    app.kubernetes.io/instance: autocert
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: autocert
    app.kubernetes.io/version: 0.16.0
    helm.sh/chart: autocert-1.16.3
  name: autocert-autocert-webhook-config
  resourceVersion: "27934799"
  uid: 130552ce-6aef-473d-a888-dcb76e4f3595
webhooks:
- admissionReviewVersions:
  - v1
  clientConfig:
    caBundle: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJ4RENDQVdxZ0F3SUJBZ0lSQUk1c1pTeFg1SXJzWmJUWWdJcmpJV2N3Q2dZSUtvWkl6ajBFQXdJd1FERWEKTUJnR0ExVUVDaE1SVTNSbGNDQkRaWEowYVdacFkyRjBaWE14SWpBZ0JnTlZCQU1UR1ZOMFpYQWdRMlZ5ZEdsbQphV05oZEdWeklGSnZiM1FnUTBFd0hoY05Nakl3TlRFNE1EVTBPRE01V2hjTk16SXdOVEUxTURVME9ETTVXakJBCk1Sb3dHQVlEVlFRS0V4RlRkR1Z3SUVObGNuUnBabWxqWVhSbGN6RWlNQ0FHQTFVRUF4TVpVM1JsY0NCRFpYSjAKYVdacFkyRjBaWE1nVW05dmRDQkRRVEJaTUJNR0J5cUdTTTQ5QWdFR0NDcUdTTTQ5QXdFSEEwSUFCSjJtRnYwVQppYmE1NFBsYmxQVjRtbzVROVBKVk9SVld1SXhvbkpsRnFPK2xmSklJQm1RSnpvVjVFOGsvS05KMWdPUFJVK3J2CnVEY3owNUcyc3diTGJWaWpSVEJETUE0R0ExVWREd0VCL3dRRUF3SUJCakFTQmdOVkhSTUJBZjhFQ0RBR0FRSC8KQWdFQk1CMEdBMVVkRGdRV0JCUTloVG5DUGxiUXdiYlZOUTBZbHU0MmhjdUhLREFLQmdncWhrak9QUVFEQWdOSQpBREJGQWlCWkx0RkdVSUVld0NQd3VNY29HaS9sVmdVeHpnQzRTVjZOME10VFczWUxvd0loQU4zT1lpMDBwRUd2CkhuWmc1MUJhNUl6cUI0Zy9JWm9BUWRpb2w4WEtCbXp4Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
    service:
      name: autocert
      namespace: akros-cert
      path: /mutate
      port: 443
  failurePolicy: Ignore
  matchPolicy: Equivalent
  name: autocert.step.sm
  namespaceSelector:
    matchLabels:
      autocert.step.sm: enabled
  objectSelector: {}
  reinvocationPolicy: Never
  rules:
  - apiGroups:
    - ""
    apiVersions:
    - v1
    operations:
    - CREATE
    resources:
    - pods
    scope: '*'
  sideEffects: NoneOnDryRun
  timeoutSeconds: 10

Above is my current MutatingWebhookConfiguration when I kubectl edit mutatingwebhookconfiguration/autocert-autocert-webhook-config

sideEffects is already NoneOnDryRun but still not working as expected :/

Also my kubeapi log shows autocert webhook error like below
W0519 00:56:09.206214       1 watcher.go:229] watch chan error: etcdserver: mvcc: required revision has been compacted
I0519 01:19:04.140341       1 trace.go:205] Trace[547299053]: "Call mutating webhook" configuration:autocert-autocert-webhook-config,webhook:autocert.step.sm,resource:/v1, Resource=pods,subresource:,operation:CREATE,UID:9f2425ce-c2d0-44fe-80af-9e7ee67a3118 (19-May-2022 01:18:54.140) (total time: 10000ms):
Trace[547299053]: [10.000217573s] [10.000217573s] END
W0519 01:19:04.140391       1 dispatcher.go:176] Failed calling webhook, failing open autocert.step.sm: failed calling webhook "autocert.step.sm": failed to call webhook: Post "https://autocert.akros-cert.svc:443/mutate?timeout=10s": context deadline exceeded
E0519 01:19:04.140409       1 dispatcher.go:180] failed calling webhook "autocert.step.sm": failed to call webhook: Post "https://autocert.akros-cert.svc:443/mutate?timeout=10s": context deadline exceeded
I0519 01:19:04.142797       1 trace.go:205] Trace[765278694]: "Create" url:/api/v1/namespaces/akros-research/pods,user-agent:kube-controller-manager/v1.22.9+rke2r2 (linux/amd64) kubernetes/6df4433/system:serviceaccount:kube-system:replicaset-controller,audit-id:caf6c471-3544-47a6-97ce-e99434848e17,client:<IP_ADDRESS>,accept:application/vnd.kubernetes.protobuf, */*,protocol:HTTP/2.0 (19-May-2022 01:18:54.135) (total time: 10007ms):
Trace[765278694]: ---"Object stored in database" 10007ms (01:19:04.142)
Trace[765278694]: [10.007754384s] [10.007754384s] END
I0519 01:20:57.026705       1 trace.go:205] Trace[1627148884]: "Call mutating webhook" configuration:autocert-autocert-webhook-config,webhook:autocert.step.sm,resource:/v1, Resource=pods,subresource:,operation:CREATE,UID:33e6e663-9142-4ac4-bb86-9d397293a707 (19-May-2022 01:20:47.026) (total time: 10000ms):
Trace[1627148884]: [10.000677498s] [10.000677498s] END
W0519 01:20:57.026760       1 dispatcher.go:176] Failed calling webhook, failing open autocert.step.sm: failed calling webhook "autocert.step.sm": failed to call webhook: Post "https://autocert.akros-cert.svc:443/mutate?timeout=10s": context deadline exceeded
E0519 01:20:57.026776       1 dispatcher.go:180] failed calling webhook "autocert.step.sm": failed to call webhook: Post "https://autocert.akros-cert.svc:443/mutate?timeout=10s": context deadline exceeded
I0519 01:20:57.029026       1 trace.go:205] Trace[189111566]: "Create" url:/api/v1/namespaces/akros-research/pods,user-agent:kube-controller-manager/v1.22.9+rke2r2 (linux/amd64) kubernetes/6df4433/system:serviceaccount:kube-system:replicaset-controller,audit-id:0b96d660-319e-49e9-b342-b04750a698b3,client:<IP_ADDRESS>,accept:application/vnd.kubernetes.protobuf, */*,protocol:HTTP/2.0 (19-May-2022 01:20:47.017) (total time: 10011ms):
Trace[189111566]: ---"Object stored in database" 10011ms (01:20:57.028)
Trace[189111566]: [10.011444304s] [10.011444304s] END
W0519 01:41:08.343449       1 watcher.go:229] watch chan error: etcdserver: mvcc: required revision has been compacted
I0519 04:39:06.372765       1 trace.go:205] Trace[615607443]: "List" url:/api/v1/secrets,user-agent:helm3/v0.0.0 (darwin/amd64) kubernetes/$Format,audit-id:f83d3271-419a-4283-9903-4d98f6fac6cb,client:<IP_ADDRESS>,accept:application/json, */*,protocol:HTTP/2.0 (19-May-2022 04:39:05.540) (total time: 831ms):
Trace[615607443]: ---"Writing http response done" count:25 819ms (04:39:06.372)
Trace[615607443]: [831.858074ms] [831.858074ms] END
E0519 05:42:59.682695       1 watch.go:251] unable to encode watch object *v1.WatchEvent: http2: stream closed (&streaming.encoder{writer:(*http2.responseWriter)(0xc016d43fe0), encoder:(*versioning.codec)(0xc0096a7cc0), buf:(*bytes.Buffer)(0xc00dcba6c0)})
I0519 06:45:25.118086       1 trace.go:205] Trace[1737294061]: "Call mutating webhook" configuration:autocert-autocert-webhook-config,webhook:autocert.step.sm,resource:/v1, Resource=pods,subresource:,operation:CREATE,UID:6b56e0a5-a57a-456e-a822-88c09b3ecf05 (19-May-2022 06:45:15.117) (total time: 10000ms):
Trace[1737294061]: [10.000783536s] [10.000783536s] END
W0519 06:45:25.118136       1 dispatcher.go:176] Failed calling webhook, failing open autocert.step.sm: failed calling webhook "autocert.step.sm": failed to call webhook: Post "https://autocert.akros-cert.svc:443/mutate?timeout=10s": context deadline exceeded
E0519 06:45:25.118150       1 dispatcher.go:180] failed calling webhook "autocert.step.sm": failed to call webhook: Post "https://autocert.akros-cert.svc:443/mutate?timeout=10s": context deadline exceeded
I0519 06:45:25.120072       1 trace.go:205] Trace[2097276046]: "Create" url:/api/v1/namespaces/akros-research/pods,user-agent:kube-controller-manager/v1.22.9+rke2r2 (linux/amd64) kubernetes/6df4433/system:serviceaccount:kube-system:replicaset-controller,audit-id:dc94c3f1-2efe-40c3-b9bc-d6385fa0c489,client:<IP_ADDRESS>,accept:application/vnd.kubernetes.protobuf, */*,protocol:HTTP/2.0 (19-May-2022 06:45:15.112) (total time: 10007ms):
Trace[2097276046]: ---"Object stored in database" 10007ms (06:45:25.120)
Trace[2097276046]: [10.007827998s] [10.007827998s] END
W0519 07:20:15.911496       1 watcher.go:229] watch chan error: etcdserver: mvcc: required revision has been compacted
W0519 07:58:10.839280       1 watcher.go:229] watch chan error: etcdserver: mvcc: required revision has been compacted
W0520 01:49:55.920022       1 watcher.go:229] watch chan error: etcdserver: mvcc: required revision has been compacted
W0520 01:49:55.920285       1 watcher.go:229] watch chan error: etcdserver: mvcc: required revision has been compacted
W0520 01:49:55.920479       1 watcher.go:229] watch chan error: etcdserver: mvcc: required revision has been compacted

You'll need to determine why the Kube API server cannot connect to autocert in the akros-cert namespace. Some things to try:

kubectl -n akros-cert get endpoints autocert
kubectl -n akros-cert logs deployment/autocert
kubectl -n akros-cert port-forward service/autocert 8443:443 then attempt to curl localhost:443

It was an issue of our master node being unable to communicate with other worker nodes.
While migrating we also set up an OpenVPN; by default, flannel was picking up the wrong interface.
Fixed it by setting flannel default iface to tun0.
Closing this issue, thank you for your support!


More detail required on the 'special environment' used to facilitate ATP Safe Attachments scanning.

Hello,
We are engaged with a very security focused customer who requires more detail regarding the 'special environment' before they will consider upgrading to ATP. Can we get a little more detail as to what this environment constitutes?
For example:
Is the 'special environment' isolated per customer?
How long are attachments retained for within the 'special environment'?
Are any engineers able to directly access the content that is sent to the 'special environment'?
What safeguards are in place to prevent engineers accessing content sent to the 'special environment'?
Thank you

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

ID: 7a177ba2-5cff-b0a0-6afa-717689db2884
Version Independent ID: 802f6c49-9a14-e76f-6cf3-67862b40f18d
Content: Office 365 Advanced Threat Protection - Office 365
Content Source: microsoft-365/security/office-365-security/office-365-atp.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

Hello @mtwelve ,
requires more detail regarding the 'special environment' - "special environment" here - is a dedicated VM where attachment is opened. After that, ATP checks whether anything was changed in the system of that VM.
Is the 'special environment' isolated per customer? - it is a black box isolated from everything
How long are attachments retained for within the 'special environment'? - until the check is completed
Are any engineers able to directly access the content that is sent to the 'special environment'? What safeguards are in place to prevent engineers accessing content sent to the 'special environment'? - this info is out of Microsoft docs scope, I would recommend to review trust center to collect information about Microsoft's approach to Security, Privacy and Compliance.
Thank you

@mtwelve - Thank you for submitting feedback.
From our understanding, the issue you raised has been answered by @MaratMussabekov so we will close this issue.
Thank you for your contribution to make the docs better! Much appreciated!

Thank you @MaratMussabekov for the explanation. This is really helpful information to have.


Improve instructions_by_address  function

Description

Close #200
Checklist

[ ] Targeted PR against correct branch.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #201   +/-   ##
=========================================
  Coverage          ?   64.52%
=========================================
  Files             ?       35
  Lines             ?     1477
  Branches          ?        0
=========================================
  Hits              ?      953
  Misses            ?      492
  Partials          ?       32

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 461cb90...4c9dc91. Read the comment docs.


A Dumb Thing

The color changing is pretty cool. It's mostly the flavor text that's dumb.
And the CSS implementation. Thank you emacs for making this possible.

Somebody who knows CSS tell me how stupid/genius/normal that CSS hack I put in for all the colors is.

I'm worried about how this will look on the other themes. We should weed out colors that won't stand out well against the backgrounds of Solarized Dark (hex #002b36) and Solarized Light (hex #fdf6e3.)
Solarized absolutely supports 8 colors that work on both backgrounds, list here under 'The values': https://ethanschoonover.com/solarized/ More than those will probably require serious testing on all 3 backgrounds that I don't think we have time for.
Our style https://github.com/lazerwalker/azure-mud/blob/main/style/style.css uses the Solarized-approved versions of green, pink, and blue (and then reasonably close variants for the default black background) to represent links (green), warning text (pink), and the thumbs up upvote (blue).
So what might be worth doing is defining --yellow, --orange, etc as CSS vars in the 3 sections of styles.css (root, .solarized-dark, and .solarized-light) and changing the function to grab the defined var.

+1, I think this is a really fun idea, but making sure it plays nicely with our color scheme seems like an important accessibility concern.

It should actually be really easy to support the themes, with how you set it up. Like Kawa said, in the :root, .solarized-dark, and .solarized-light, you can define more variables for colours, like --orange, and define it so that in each theme it's a visible colour. Those solarized colours Kawa linked save you some work because you can use the same value across light and dark, but there's nothing actually stopping you from adding a colour not on that list, you just need to make sure you pick a hex value for it in light that is visible on light, and a different hex value for the same general colour in dark that works for dark.
Then all you have to do is pair your ValidColors list down to just however many variables you've defined for colors, you can leave it the same where it's like Orange = 'Orange'.
Then your css just has
.name.Orange
{
color: --orange
}`

So, really I appreciate all the help on colors there, but I also have literally never used CSS before and have no idea what any of that means. It sounds like I'd have to test every color (?) manually to make sure it works with each theme, and then use --color: #hexvalue to something with enough contract on each theme to make it compatible? Which, if I'm understanding correctly, sounds like faaaaar too much work to be plausible.
Looking at the Solarized website it seems like if I just limited the valid colors to [yellow, orange, red, magenta, violet, blue, cyan green] it will just work out of the box? That's actually very easy, it's just deleting a lot of stuff.

...I thiiink I get it?

Coool, I suspect we'll eventually want to move this someplace other than Table A, but 👍 for now!
The merge conflict looks really simple, but GitHub's web UI isn't letting me do it, so I'll leave that to you to merge whenever :)

oh, lol, JK, I got a failure error message but the merge still went through


Create dotnet.yml

Category

[ ] Bug fix
[ ] New feature
[ ] New sample
[ ] Documentation update

Related Issues
fixes #X, mentioned in #Y
What's in this Pull Request?
Please describe the changes in this PR. Simple description or details around bugs which are being fixed.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please ensure you have updated any associated docs files based on your code changes

[!TIP]
@myHerbDev
Plant a Tree for Each Sponsor Donation!
Start slowly with $3 one-time payment


⚠ Bofrost.es has degraded performance

In 1b5417f, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1513 ms

Resolved: Bofrost.es performance has improved in 0a5ba56 after 9 minutes.


Sending mail from docker container to external server with the same domain name

Hello. I am using your docker image and everything works fine except one thing. I have a domain, mysite.com and i am using your docker image to send mail from this domain using my VDS. I also use an external mail service to receive mail to<EMAIL_ADDRESS> The service for receiving  mail is similar to google gsuite. Now, i want to send messages from my VDS to a mail service that is serving the same domain. When i send messages to<EMAIL_ADDRESS>from container the mail is not delivered. and i get following info in my docker logs

Jan 31 22:12:57 be599241f647 postfix/local[264]: A2157A0084<EMAIL_ADDRESS>relay=local, delay=0.12, delays=0.1/0.01/0/0.01, dsn=2.0.0, status=sent (delivered to maildir)

This means that the mail is sent using local relay and i need to make it sent to external server/service that service the same domain.
Please.help me. If you need any additional info - let me know.

Hi Muzset,
that sounds like a general problem you might be able to fix with some really fancy postfix configuration.
In general I'd say that your postfix does everything like he's supposed to do.
Imagine:

Your Postfix ist responsible for the Domain: mysite.com

<EMAIL_ADDRESS>belongs to mysite.com and is therefore under control of your postfix

Maybe you're able to add some forwarding rule like:
_forward all mails comming to<EMAIL_ADDRESS>to mailboxes@(mx ip addr of mysite.com)
I can't give you a good solution for such a odd szenario - but maybe you're able to find something in the postfix manual / configuration how to configure a postfix to only listen to a few specific mails and relay specific boxes of the same domain to a different mailserver


__display not defined

I get an error:
julia> sol = solve(ocp, :direct, :adnlp, :madnlp)

UndefVarError: `__display` not defined

This solve is the one from OptimalControl I assume.
Can you post the source code of the function here so that I can recheck the same case ?

https://github.com/control-toolbox/CTDirect.jl/blob/main/ext%2FCTSolveExtIpopt.jl#L16
Vs

Here an example:
using OptimalControl
using MadNLP

t0 = 0
tf = 1
x0 = [-1, 0]

ocp = @def begin

    t ∈ [ t0, tf ], time
    x = (q, v) ∈ R², state
    u ∈ R, control

    x(t0) == x0
    x(tf) == [ 0, 0 ]

    ẋ(t)  == [ v(t), u(t) ]

    ∫( 0.5u(t)^2 ) → min

end

solve(ocp, :direct, :adnlp, :madnlp)


Retrieve load balancer IP from kube_service_status_load_balancer_ingress

Previously, the LoadBalancerIP field was retrieved from kube_service_info.load_balancer_ip. This value, however, seems to be blank for the current ksm version.
This PR changes it to be retrieved from kube_service_status_load_balancer_ingress.ip, which seems to be working with the current version.
Temporary images images for testing are available:

roobre/infrastructure-k8s:load-balancer
roobre/infrastructure-k8s:load-balancer-unprivileged

Tasks

[ ] Investigate whether this is still needed/recommended in newer kube-state-metrics versions
[ ] Add a test case for this

Fixes #74

Made a few tests, and I can confirm the behavior of kube-state-metrics is the same on 1.9.7 and 1.9.8 (latest at the time of writing).

As reported upstream, kube_service_info.load_balancer_ip only reflects an IP if it is defined in the service spec directly. kube_service_status_load_balancer_ingress.ip should be used when this IP is not known at deployment-time.


Basic groups inside arrays support.

e.g.:
foo = (uint, text)
bar = [
  foos: [* foo],
]

which if you had n foos would be a 2 * n long CBOR array as there's no wrapping map/array around the basic group foo. This can be done in some CDDL specs as a space optimization.

For context, this was needed to generate the CIP-36 library for catalyst.

am i correct we couldn't generate this?

https://github.com/gitmachtl/CIPs/blob/914d0514fa90b821521a793f035e22b0f51f6009/CIP-0036/schema.cddl#L12
https://github.com/gitmachtl/CIPs/blob/914d0514fa90b821521a793f035e22b0f51f6009/CIP-0036/schema.cddl#L28

Yes, that was the part that we couldn't generate.


AttributeError: 'CostModelContactFrictionCone' object has no attribute 'frame'

Hi
Today I compiled a qudurpedal_gaits.py, and I got a error message "AttributeError: 'CostModelContactFrictionCone' object has no attribute 'frame'"
I am curious about this error message. Because it happens after updating robotpkg, and it also has a same error after I re-install the crocoddyl using robotpkg.
Is there a change on the crocoddyl library?

This issue is duplicate. See here for more details: https://github.com/loco-3d/crocoddyl/issues/752.


Fix test warnings

PR for #909.
Fix test warnings by passing required propTypes to the components.
Added babel-plugin-rewire to allow dependency mocking.
NOTE: the latest version of<EMAIL_ADDRESS>does not work with istanbul, but<EMAIL_ADDRESS>seems to work fine, see rewire issue or istanbul issue.

Coverage decreased (-0.02%) to 98.925% when pulling 0e0c68614db4f9e4c83824ccd055bee63f5a04cd on samit4me:fix-test-warnings into e1d054e82f6a1771b0af67980a9fbbd5b61d2f39 on mxstbr:dev.

I've been having the same issue lately and my stupid OCD is kicking in with my tests showing low coverage so I've been trying hard to get rewire to work in this boilerplate.
I've finally figured out that this issue has been fixed in the latest version of istanbul-lib-coverage (a dependency of istanbul-lib-instrument, which is a dependency of babel-plugin-istanbul) but because the old version is still being mentioned, we'll need to use a workaround.
I've done the hard work and forked both packages to use the newer version of istanbul-lib-coverage. For the time being, do the following ...
In your package.json file, use the following line for babel-plugin-istanbul:
"babel-plugin-istanbul": "git://github.com/bt/babel-plugin-istanbul.git#git-build",

or use:
$ npm install "git://github.com/bt/babel-plugin-istanbul.git#git-build" --save-dev

If we could please bring this to the attention of both packages, that'd be great. I've opened up PR/issues (istanbul-lib-instrument#20 and babel-plugin-istanbul#41) respectively.

Loving this, except the annoying rewire issue. So essentially we have to wait until they release a new version as per @bt's comment? (thanks for digging in!)

Thank you for the info and the work you have done @bt . I have updated to your babel-plugin-istanbul using the instructions 👍 and found the following:

It works with<EMAIL_ADDRESS>It does not work with<EMAIL_ADDRESS>as I get the same errors.

If there is something else I can try, I'd love to assist where possible, cheers.
@mxstbr This fix has certainly gone much deeper than I thought. As<EMAIL_ADDRESS>seems to work we could add rewire now and only update once the issue has been fixed, but in saying that I would totally understand if you wanted to wait until the issues have been resolved in the lastest versions.

Hey @samit4me, so what I've noticed is the fork that I made will fix an issue with rewire working with istanbul. It then gets into another issue which is to do with the istanbul HTML/LCOV reporting.
Can you do me a favour and try the following ...

In file internals/testing/karma.conf.js, comment out the HTML and LCOV reporters, and only leave the text-summary.

Your coverageReporting block should look like this:
    coverageReporter: {
      dir: path.join(process.cwd(), 'coverage'),
      reporters: [
        { type: 'lcov', subdir: 'lcov' },
        { type: 'html', subdir: 'html' },
        { type: 'text-summary' },
      ],
    },

... and then run another test and see if you still get the error (with the latest rewire).
If this is the case, I will put in yet another PR (this time to istanbul) to add a guard.

HI @bt you are correct about the reporters, commenting them out stops the error ERROR [coverage]: TypeError: Cannot read property 'start' of undefined, it seems lcov and html throw 1 error each.
I tried a few different combinations and below are my findings:
1) Using this PR "as is" - It Works!
package.json:
"babel": {
  "env": {
    "test": {
      "plugins": [
        "rewire",
        "istanbul"
      ]
    }
  }
},
"devDependencies": {
  "babel-plugin-istanbul": "2.0.0",
  "babel-plugin-rewire": "1.0.0-rc-4",
}

karma.conf.js:
coverageReporter: {
  dir: path.join(process.cwd(), 'coverage'),
  reporters: [
    { type: 'lcov', subdir: 'lcov' },
    { type: 'html', subdir: 'html' },
    { type: 'text-summary' },
  ],
},

2) After updating babel-plugin-rewire - It Fails! error log
package.json:
...
"devDependencies": {
  "babel-plugin-istanbul": "2.0.0",
  "babel-plugin-rewire": "1.0.0-rc-6",
}

karma.conf.js:
...

3) Switch babel plugin order - It Fails! error log
package.json
"babel": {
  "env": {
    "test": {
      "plugins": [
        "istanbul",
        "rewire"
      ]
    }
  }
},
"devDependencies": {
  "babel-plugin-istanbul": "2.0.0",
  "babel-plugin-rewire": "1.0.0-rc-6",
}

karma.conf.js:
...

4) Comment out lcov and html reporters - It Works!
package.json:
"babel": {
  "env": {
    "test": {
      "plugins": [
        "rewire",
        "istanbul"
      ]
    }
  }
},
"devDependencies": {
  "babel-plugin-istanbul": "2.0.0",
  "babel-plugin-rewire": "1.0.0-rc-6",
}

karma.conf.js:
coverageReporter: {
  dir: path.join(process.cwd(), 'coverage'),
  reporters: [
    // { type: 'lcov', subdir: 'lcov' },
    // { type: 'html', subdir: 'html' },
    { type: 'text-summary' },
  ],
},

5) Tried all of the above using "babel-plugin-istanbul": "git://github.com/bt/babel-plugin-istanbul.git#git-build" - Same results
6) Swapped out istanbul for babel-plugin-__coverage__ to test the plugin ordering and __coverage__ also failed if rewire was first.

I'd much rather wait until the rewire issue is properly solved, but I'm not that far into it – what do you think?

Agree, waiting feels like a better option. It looks like rewire is also waiting on istanbul to be fixed before updating the docs regarding  plugin ordering.

Coverage decreased (-0.02%) to 98.925% when pulling 4e61735b25843f14e449a2fcd71917449952b7e8 on samit4me:fix-test-warnings into 347ed436e86babb79849def968110557c021ed3d on mxstbr:dev.

Any updates here?

Hey @mxstbr,
So a number of PRs had been merged into istanbul that fixed an issue that was mentioned before, but now it is failing on another line, specifically the annotateBranches function. I'm not sure what the stance is for the istanbul community (ie. fixing it by putting a guard in istanbul or to fix it in rewire). I used a few days to do some debugging to understand why this was happening but I didn't get any real findings.
At this point, I've given up on using Karma as my test runner and have replaced the entire testing flow in my own private fork of this repository with ava, including the test generators. It works with rewire pretty much straight out of the box. The only major problem is that it doesn't have support for test grouping and I don't think the community there is interested at all in test grouping.
Maybe that's something you'd like to consider moving forward?

Coverage decreased (-0.02%) to 98.936% when pulling 2e76e61a83a4738e79a80070a0eb54567a3bdbfd on samit4me:fix-test-warnings into 2852c09b4d0851ce46eea3dc55517f67fd1ab80d on mxstbr:dev.

No updates @mxstbr, I tried using the latest versions, including<EMAIL_ADDRESS>and got the same issues 😞.
I was secretly hoping that Jest would resolve all of these issues, shame about the generators.
Maybe we could remove rewire? This would reduce the test errors, leaving only the following error.
ERROR: 'Warning: Failed prop type: Invalid prop srcof typeobjectsupplied toImg, expected string.     in Img'

@samit4me Could you handle that with something similar to:
  Img: React.PropTypes.oneOfType([
    React.PropTypes.object,
    React.PropTypes.string,

Your totally correct @gihrig, that certainly works, in fact, that is exactly what I did before using rewire. It was removed as it didn't feel right, the src attribute is expecting a URI.
Happy to use this PropType solution if others also agree?

Happy to use this PropType solution if others also agree?

Sure!

Coverage remained the same at 98.953% when pulling a8f9c8674c8ea0abf671de4fa6fc98a667d384fa on samit4me:fix-test-warnings into dfc822b1095cfe61780f65b032fe923c3c916cad on mxstbr:dev.

Rewire has been removed @mxstbr and the PropTypes solution recommended by @gihrig added, no more test warnings 🎉.

I can confirm: All tests pass no errors! 💯
Node 6.4.0
npm 3.10.6
Mac OS 10.11.6
Chrome 53.0.2785.116 (64-bit)

Awesome, let's 🚢


higher_percentiles & lower_percentiles  of type numpy.float64 are not recognized as float

If I submit values for higher_percentile or lower_percentile from a numpy array, these values are not seen as float (as they are indeed numpy.float64) -- hence they are never transformed into the 1-valued list (see line 361 in base.py).
A working solution could be to replace each line of the kind
if type(lower_percentiles) in [int, float]:

with:
if isinstance(lower_percentiles, (int, float)):

which would return True for both float and numpy.float64 types.

Hi,
Thanks for pointing this out; I have included a similar fix in the new release (0.2.0):
if isinstance(lower_percentiles, (int, float, np.integer, np.floating)):

(and similar for higher_percentiles)


correct the package name for Relaxed Factory

Should resolve issue 367

Good catch. Thanks for the PR.


C++: Support definition by reference in data flow library

The IR-based data flow library won't make it into 1.20, so I've added support for definition by reference to the current one. This PR doesn't support flow out of callers whose body assigns to a pointer parameter; that will still have to wait for the IR. What's supported now is flow through known library functions and manual specification of flow sources as DefinitionByReferenceNodes. I've hooked data flow up to the semmle.code.cpp.models.interfaces.DataFlow library, which immediately gives us flow through memcpy and related functions.
We need to find out whether this interface with DefinitionByReferenceNode is going to be forward-compatible with whatever is coming in the IR. We can always deprecate it, but it should at least allow feature parity between the current library and the IR-based one.
Before this PR, data flow around definition by reference was different depending on whether a variable was modelled in FlowVar.qll as SsaVar or BlockVar. It's supposed to be an implementation detail that variables can be modelled in these two different ways. Essentially, SsaVar-modelled variables would stop their data flow propagation at f(&x), while BlockVar-modelled variables wouldn't. I've changed BlockVar to do what SsaVar does.
The implementation was a bit tricky because it added cases to FlowVar where a control-flow node is simultaneously a definition and a use, similar to what I did in https://git.semmle.com/Semmle/code/pull/23501.

Looks promising.


Release 8.2.0

We should include https://github.com/theforeman/puppet-dhcp/pull/209 since I think it's now ready.


Push to openstack app collection

Towards https://github.com/giantswarm/giantswarm/issues/20430

Ok, but could we not add this push-to prefix everywhere please ? I find that it makes things less readable.

@TheoBrigitte I did this because we use this naming convention in basically all of our other CI pipelines and I think the consistency is important. I found it initially confusing when I looked at the file and the job name didn't contain push-to-. Maybe something to bring to SIG Releng?

Closing in favor of https://github.com/giantswarm/prometheus-rules/pull/214


A kubectl plugin for listing scaling events

Proposal
A simple kubectl plugin which will list the current scaling events under the deployed keda replicas.
Examples:
kubectl get scaling-events
Output:
NameOfScaler                           Scaling decision
couchdb-scaler                         no of rows greater than threshold
loki-scaler                            metric value greater than a threshold

What do you guys think?
I would be glad to pick this up as soon as this issue receives any positive feedback from the community.
Use-Case
Show the different scaling events of different scalers listed under the keda operator
Anything else?
No response

Do you think this use case is worth implementing?

Do you think this use case is worth implementing?

I think it is, in context that, suppose I would want to know as an user what scalers are available in my cluster currently, just using kubectl only

Do you think this use case is worth implementing?

I think it is, in context that, suppose I would want to know as an user what scalers are available in my cluster currently or the scaling events which are driving the auto scalers or scaling different resources, just using kubectl only

Since scalers are defined as part of ScaledJobs/ScaledObjects triggers, I think it will be worth it if we can list them, the trigger(s) that they are using, and the parameter config of the triggers.

Do you think this use case is worth implementing?

I think it is, in context that, suppose I would want to know as an user what scalers are available in my cluster currently or the scaling events which are driving the auto scalers or scaling different resources, just using kubectl only

Since scalers are defined as part of ScaledJobs/ScaledObjects triggers, I think it will be worth it if we can list them, the trigger(s) that they are using, and the parameter config of the triggers.

Agreed, that way it will be easier to view all the triggers @neelanjan00

Well yeah, but it is not so straighforward to query for this info from KEDA. You will need to manage all of that in the plugin seaprately (which si fine for the list of scalers, but might be a painful process when listing config options per scaler (it is a huge number)).

That will also be a long list, true @zroubalik , what do you suggest?

Well yeah, but it is not so straighforward to query for this info from KEDA. You will need to manage all of that in the plugin seaprately (which si fine for the list of scalers, but might be a painful process when listing config options per scaler (it is a huge number)).

That's a valid concern, I think. We can have a verbose flag for listing the config options maybe. Otherwise it might be done on a per ScaledJob/ScaledObject basis rather than for all of them at once.

I think writing them to our SO/SJ resources would be better: https://github.com/kedacore/keda/issues/3764

I think writing them to our SO/SJ resources would be better: #3764

I don't think I follow.

@26tanishabanik @neelanjan00 scalers are not defined on the ScaledObject/Job level, there are just metadata (map[string]string) that needs to be validated for each scaler. So it is not easy (possible) to programatically list all the options.
For example:
https://github.com/kedacore/keda/blob/41487693f172b53689e6b29b55185a4e2840233b/pkg/scalers/activemq_scaler.go#L77

Can't we just define a parameter in keda itself to define what the event is, and then fetch it? @zroubalik

I think writing them to our SO/SJ resources would be better: #3764

I don't think I follow.

https://github.com/kedacore/keda/issues/3764#issuecomment-1305301918 should clarify this, but basically give insights to how your SO/SJ is doing and when it has last scaled


Fixing NPE during ComposedModel validation in InheritanceChainPropertiesValidator

I had faced with NPE during validation Foo1 definition with InheritanceChainPropertiesValidator. composedModelWrapper.getChild().getProperties() throws NPE because composedModelWrapper.getChild() is null for Foo2 model
Model definitions to show inheritance hierarchy :
  Foo1:
    x-discriminator-value: value1
    allOf:
    - $ref: '#/definitions/Foo2'

  Foo2:
    allOf:
    - $ref: '#/definitions/Foo3'

  Foo3:
    allOf:
    - $ref: '#/definitions/Foo4'
    - type: object
      discriminator: prop1
      required:
      - prop1
      properties:
        prop1:
          $ref: '#/definitions/Foo3Type'

  Foo4:
    type: object
    properties:
      id:
        type: string

  Foo3Type:
    type: string
    enum:
    - value1
    - value2
    - value3

I already have fix for this issue. I'm going to create PR.

Hi @oyeli, could you please describe the use case to reproduce the error?

Please, look at my PR https://github.com/sylvainlaurent/swagger-validator-maven-plugin/pull/17.

Hi @oyeli, could you please describe the use case to reproduce the error?

Yes, sure. I'll update description.

Hi @giuliopulina.
Today we also faced this issue after updating our normalizer library. It is highly recommended to fix it. Thanks.

fixed by PR #17

@sylvainlaurent could you please put the new version of the plugin to mvnrepository.com

I deployed a 1.2.5 to maven central


Error: Command failed: /bin/sh -c make install

I am using this npm in my windows 10 system, it is running in local perfectly.
On my server, there is Ubuntu 18.04, I am unable to install this package. As it ends with below mentioned error. Do you have any idea ?
Response code 404 (Not Found)
⚠ gifsicle pre-build test failed
ℹ compiling from source
✖ Error: Command failed: /bin/sh -c make install
/bin/sh: 1: make: not found

Hello @1vipulp
I found a critical error on version 1.5.8. I fixed it. Check new version 1.6.0. But i not think than it related, but you checking.


Add test for smartmatch hash with Mu values.

Related to https://github.com/rakudo/rakudo/issues/1772

Thank you!


Display whether the snapshot is a stateful snapshot or not.

containerh1@containerh1:~$ lxc list first
+-------+---------+------------------+------+-----------+-----------+
| NAME  |  STATE  |       IPV4       | IPV6 | EPHEMERAL | SNAPSHOTS |
+-------+---------+------------------+------+-----------+-----------+
| first | RUNNING | <IP_ADDRESS> (eth0) |      | NO        |         1 |
+-------+---------+------------------+------+-----------+-----------+
Snapshots:
  /1.0/containers/first/snapshots/fresh

The snapshot list should display whether the snapshot is a stateful snapshot or not.

Yeah, I think the snapshot list should also be a table and show things like when it was created and whether it's stateful or not, a branch would be very welcome!


Fix yandex 400 error

Seems they changed something that broke things. probably url change for querying

are you still interested in this feature? I'm planning to remove yandex on it's entirety, or maybe rework google cog


[Question] Cannot create folder

How to create  new posts
hugo new posts/istpost
The above command create a file istpost.md in content/posts folder.
But the default posts are in this format posts/Folder/folder.md
My question is will we create folder manually?

Actually i am integrating Netlify CMS. I have integrated it to other hugo themes in the past.
But in this theme the post are saved in a folder like posts/POSTNAME/POSTNAME.md
How can I tell netlify to create a folder with same name as post title?
my netlify.toml is
backend:
  name: git-gateway
  branch: master # Branch to update (optional; defaults to master)

media_folder: static/images/uploads
public_folder: /images/uploads

collections:
  - name: "post"
    label: "Post"
    folder: "exampleSite/content/posts"
    create: true
    fields:
      - { label: "Title", name: "title", widget: "string" }
      #- { label: "Publish Date", name: "date", widget: "datetime" }
      - { label: "Description", name: "description", widget: "string" }
      # - { label: 'Side Image', name: 'image', widget: 'image' }
      - { label: "Body", name: "body", widget: "markdown" }
      # - { label: 'Libraries', name: 'libraries', widget: 'list' }
      #- { label: "Categories", name: "categories", widget: "list" }
      #- { label: "Tags", name: "tags", widget: "list" }
      #- { label: "Series", name: "series", widget: "list" }

How to create new posts

If you wanna write it on english translation in the Posts page
hugo new posts/yournamecontent/index.en.md

If you wanna write it without multilanguage in the Posts page
hugo new posts/yournamecontent.md

If you wanna create a special page for example About page
hugo new about.md or hugo new about/index.en.md

Source from Theme-Documentation

Yeah it is not necessary to have a folder for a post. The issue is considered solved now

@khusika

How to create new posts

1. If you wanna write it on english translation in the `Posts` page
   `hugo new posts/yournamecontent/index.en.md`

2. If you wanna write it without multilanguage in the `Posts` page
   `hugo new posts/yournamecontent.md`

3. If you wanna create a special page for example `About` page
   `hugo new about.md` or `hugo new about/index.en.md`

Source from Theme-Documentation

Is it also possible to have posts in their own folder for easy management and organization of assets? For example the image files included in the post.
So:
posts > postname1 > postname1.md
posts > postname1 > images.jpg
posts > postname1 > video.webm
Is it possible to create the post in its own folder for this workflow when telling hugo to make a new post?
Also, regarding the language translation, is it possible to disable multi-language so posts are just name.md instead of name.lang.md?

Is it also possible to have posts in their own folder for easy management and organization of assets?

Use CMS, read "Frontend Interfaces with Hugo" for more information

Is it possible to create the post in its own folder for this workflow when telling hugo to make a new post?

No, please read about hugo new documentation here

Also, regarding the language translation, is it possible to disable multi-language so posts are just name.md instead of name.lang.md?

Without multilanguage path
posts/postname/index.md; posts/postname.md; pagename/index.md; pagename.md

Is it also possible to have posts in their own folder for easy management and organization of assets?

Use CMS, read "Frontend Interfaces with Hugo" for more information

Doesn't something like Hokus or Netlify CMS need theme-specific setup to work properly?

Is it possible to create the post in its own folder for this workflow when telling hugo to make a new post?

Please read about hugo new documentation here

Yes, I did that, but nothing there talks about that. Does that mean you would have to manually name the folder for each post, is that correct?
Also, creating a new post.md does not include the theme's post options (just title, date and draft). Is it possible to make it include the options you built into the theme? then we could remove the options what we don't want to change, but don't have to remember all the option names and such.

Doesn't something like Hokus or Netlify CMS need theme-specific setup to work properly?

It's not "theme-specific setup" but "user-specific setup", and i wont (for the moment) support lot of 3rd party CMS-apps to be included in this theme.

Yes, I did that, but nothing there talks about that. Does that mean you would have to manually name the folder for each post, is that correct?

I don't understand what "manually" are you talking about, using hugo new is already automatic to generate a post in/out-side folder.

Also, creating a new post.md does not include the theme's post options in the front matter (just title, date and draft).

Every single post created using hugo new will include the default front-matter from archetypes
Please read Hugo Documentation for general question
and read FeelIt Documentation for specific question (e.g. extended-shortcode, UI, bugs, library, etc.)
Thread locked as it's already out of topic discussion from original post.
Feel free to create a new issues which is related to the theme bugs or feature request


fix(controller): retry transient error on agent pod creation

Fixes #13654
Motivation
When I use the HTTP template, I find it pending all the time.

Then I saw that the workflow status was error, and encountered a transient error.

error is : failed to create Agent pod. Reason: Operation cannot be fulfilled on resourcequotas "xxxx": the object has been modified; please apply your changes to the latest version and try again
Modifications
When the agent pod creation encounters transient errors, just retry.

Could anyone help to rerun it ?

@fyp711 That errors should hopefully be fixed with https://github.com/argoproj/argo-workflows/pull/13660. After that's merged, click the "Update branch" button at the bottom of the PR

@fyp711 That error should hopefully be fixed with #13660. After that's merged, click the "Update branch" button at the bottom of the PR

Updated thanks.

@agilgur5 @Joibel Could you help to review this pr ? If you have free time thanks.


Radial Annotator - Add 'Verification' section.

Includes the standard role picker we use elsewhere.  Creates the Verifier Role between the annotated object and the Person.
@jlpereira on 2285_georeference_metadata_updates.

This is a new slice? and for what kind of objects? Georeferences?

I would suggest to make it part of Confidence section.

New slice.  All objects.  I'm working out the refactor to permit it on the georeference branch.

I would suggest to make it part of Confidence section.

I thought about that.  It's conceptually different enough in meaning and code that I don't want to mix the two.  Remember we auto-create a lot of the annotation UI etc.  Merging would be a headache.


Springroll isn't compatible with the latest version of node or npm

When using node version 5 up and npm 3 up, when running npm install, npm throws many warnings and errors. Seems that a lot of modules are deprecated and need to be updated.
Springroll needs to be adjusted to be compatible with the latest version of node and npm.

This is a SpringRoll 1 issue, closing


macOS guest time becomes out of sync

guest time can desync from the host os. this issue is valid for a few versions back.

UTM Version: 4.1.0
macOS Version: host 12.5, guest 13.1
Mac Chip (Intel, M1, ...): m1

Could you please add more information about the issue? Especially need the guest configuration file:

right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible

How long after you turn on the VM does it take until the issue occurs? Are all of your macOS VMs affected or only a specific configuration? (please provide!)

config.plist.zip
I only have this VM. This happened to me a few times, and it seems to be fixing itself after a while. Definitely not an easy 1/1 repro, but it does happen and it was happening before 4.1.0.

Thanks. Config looks good to me. You could potentially test this further by turning off "Set date and time automatically" in the guest's System Settings. That would in theory prevent the guest time from fixing itself by using the internet time, and force it to rely on the time information it receives from the Apple virtualization backend.

Done. Monitoring the issue.

@conath since I wrote the above comment the time slipped 3 minutes today. So with the time sync set to off in the guest, it is continuously slipping.

Having the same issue here with macOS 13 host and guest.  I've noticed the VM time slips when the host is suspended due to no activity (i.e. "falls asleep").  An easy way to force the issue is pausing the VM for a few minutes.  When you resume, the time will be out of sync.

Seems like something we'll have to report to Apple.

Using latest release 4.1.5, it's also happening while actively using a MacOS guest VM.

I hit a similar issue, maybe the same issue. I'm a first-time UTM user as of a week ago on my new M2 laptop, using UTM 4.4.4 and MacOS Ventura 13.5.2. My guest VM's time fell days behind when not in use despite the Date & Time settings being configured to set the time automatically from the Apple time server.
I was able to reset the exact time with these steps:
(1) Manually set the time to a couple minutes in the future
(2) Reactivate "Set time and date automatically"
I wonder if automatic time sync to the Apple server fails if the time has desync'ed too far. For instance, web certificates started failing because the certificate timestamps were invalidly in the future, preventing me from loading websites in Firefox.

I observe the same issue, has been ongoing for about a year for me, currently with this config.

UTM Version: Version 4.4.4 (92)
macOS Version: 14.2.1 (23C71)
Mac Chip: M2

Guest system is Ubuntu 23.04 (lunar).
I can fix the time using the sequence of commands in bash below, but it just starts drifting again after a while and besides this is no solution just a workaround:
sudo service ntp stop
sudo ntpd -gq
sudo service ntp start

Fixed for Qemu, no APIs from Apple for Virtualization.framework

Found AppleVirtualPlaformRTCPlugin in Console.app logs when switching on and off the syncing to time.apple.com in Date & Time settings :

I checked the binary /System//Library/PrivateFrameworks/CoreTime.framework/TimeSources/AppleVirtualPlatformRTCPlugin.bundle/Contents/MacOS/AppleVirtualPlatformRTCPlugin which only uses IOKit to get notified about the change
 r0 = IONotificationPortCreate(*(int32_t *)*_kIOMainPortDefault);
[...]
    r0 = IOServiceNameMatching("AppleVirtualPlatformRTC");
    r0 = IOServiceGetMatchingService(r20, r0);
[...]
r0 = IOServiceAddInterestNotification(r0, r1, "IOGeneralInterest", 0x34bc, r19, r19 + 0x18);
[...]

with the 0x34bc method:
int sub_34bc(int arg0, int arg1, int arg2, int arg3) {
[...]
    r0 = os_log_type_enabled(r20, 0x0);
    if (arg2 == 0xe0000230) {
            if (r0 != 0x0) {
                    _os_log_impl(0x0, r20, 0x0, "Avp rtc state notification received", &var_30, 0x2);
            }
            if (r8 != 0x0) {
                    if (r8 == 0x1) {
                            r20 = *(r19 + 0x10);
                            if (os_log_type_enabled(r20, 0x0) != 0x0) {
                                    _os_log_impl(0x0, r20, 0x0, "Reset time", &var_40, 0x2);
                            }
                            sub_38c0();
                    }
            }
            else {
                    r20 = *(r19 + 0x10);
                    if (os_log_type_enabled(r20, 0x0) != 0x0) {
                            _os_log_impl(0x0, r20, 0x0, "Resync Time", &var_50, 0x2);
                    }
                    sub_38e0();
            }
    }
    else {
            if (r0 != 0x0) {
                    _os_log_impl(0x0, r20, 0x0, "Avp rtc unknown notification received", &var_60, 0x2);
            }
    }
    r0 = [r19 release];
    return r0;
}

No clue about how the host macOS send such an IOKit notification to the guest macOS

I do not know if my comment helps or not, but I noticed that the time drift certainly appears with Ubuntu guests (many versions tested) but does not seem to appear if the guest is openSUSE LEAP 15.5

Finally found a way to solve this, a macOS LaunchAgent with the swift code like the fix for QEMU, but to make the VM aware of the drift => a Wake On LAN magic packet (reading the UTM config.plist)
A launchd service on the VM listens to the WOL packet and run systemctl restart networking & systemctl restart ntp
My VM has network in bridge mode, so I lose network connectivity when closing my laptop, moving home, opening it. Hence the WakeOnLAN packet ^^

Microsoft solves this issue on their Hypervisor with a RTC device /dev/ptp_hyperv, and configuring chrony to use it, see https://learn.microsoft.com/en-us/azure/virtual-machines/linux/time-sync#chrony


test: clean up unused variable

Signed-off-by: kuochunghsu<EMAIL_ADDRESS>Risk Level: low
Testing: unit

/assign @ggreenway
PTAL - I think you were one of the authors? Just making sure this wasn't an indication of an intended test that wasn't fleshed out.


Error (active)E0070:	incomplete type is not allowed (IDFGH-475)

[x ] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[x ] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[x ] I have searched the issue tracker for a similar issue and not found a similar issue.

Environment

Development Kit:     ESP32-Wrover-Kit
Kit version (for WroverKit): [v1|v2|v3|v4]
Module or chip used:  [ESP32-WROOM-32]
IDF version (run git describe --tags to find it):
// v3.2-dev-1148-g96cd3b75c
Build System:         [Make|CMake]
Compiler version (run xtensa-esp32-elf-gcc --version to find it):
// 1.22.0-80-g6c4433a
Operating System:     [Windows]
Power Supply:         [USB]

Problem Description
I am using Visual Studio 2017 to build projects for ESP32, anyway it keeps me warning me about the following possible error :
STRUCT_AFIELD_A(char,1,XCHAL_CP1_SA_ALIGN,CS_SA_,cp1,XCHAL_CP1_SA_SIZE)
Error (active)	E0070	incomplete type is not allowed	Sketch2	c:\Users\Yordan\AppData\Local\arduino15\packages\esp32\hardware\esp32\1.0.0\tools\sdk\include\esp32\xtensa\xtruntime-core-state.h	166
and this reapeats for all of the follows :
STRUCT_AFIELD_A(char,1,XCHAL_CP0_SA_ALIGN,CS_SA_,cp0,XCHAL_CP0_SA_SIZE)
STRUCT_AFIELD_A(char,1,XCHAL_CP1_SA_ALIGN,CS_SA_,cp1,XCHAL_CP1_SA_SIZE)
STRUCT_AFIELD_A(char,1,XCHAL_CP2_SA_ALIGN,CS_SA_,cp2,XCHAL_CP2_SA_SIZE)
STRUCT_AFIELD_A(char,1,XCHAL_CP3_SA_ALIGN,CS_SA_,cp3,XCHAL_CP3_SA_SIZE)
STRUCT_AFIELD_A(char,1,XCHAL_CP4_SA_ALIGN,CS_SA_,cp4,XCHAL_CP4_SA_SIZE)
STRUCT_AFIELD_A(char,1,XCHAL_CP5_SA_ALIGN,CS_SA_,cp5,XCHAL_CP5_SA_SIZE)
STRUCT_AFIELD_A(char,1,XCHAL_CP6_SA_ALIGN,CS_SA_,cp6,XCHAL_CP6_SA_SIZE)
STRUCT_AFIELD_A(char,1,XCHAL_CP7_SA_ALIGN,CS_SA_,cp7,XCHAL_CP7_SA_SIZE)
The projects compile without problem, but this is sitting there all the time.
I am just posting it in just-in-case scenario.
Expected Behavior
unknown
Actual Behavior
unknown
Steps to repropduce

Install Arduino Studio.
Install Visual Studio 2017.
install "VisualMicro" plugin.
Try to build any project and check the Error list.

This seems more related to your Visual Studio configuration for C/C++ than anything else.
We do not officially support Visual Studio, so you should raise the question to the VisualMicro team instead, but if is any help here is how we configure C/C++ properties in our ESP-IDF Visual Studio Code extension

Hi, the Visual Studio intellisense is seperate to the build process for Arduino/ESP. The errors you have reported look like intellisense errors. It is possible to alter the combo box above the errors list to "Build Only". Then you will only see the more accurate build errors. Alternatively, above the "errors list" is another combo that can be set to Project Only, that will exclude the underlying sources from intellisense "errors list" reporting.
Why? Visual Studio intellisense is not 100% perfect, it caters for projects pre and post build so it is more flexible but less accurate than the build process.
tip: Visual Micro provides a "Verbose" output option on the "vMicro" menu gives the Arduino style build output that the Admins of this site will understand.
For any other questions about Arduino in Visual Studio or to see if we can help resolve intellisense errors, please join our forum at https://www.visualmicro.com.forums.
Thank you.

Thanks for reporting, feel free to reopen.


Distributed Digital Preservation with Samvera: the One-to-Many Grant

tom johnson
<EMAIL_ADDRESS>The One-to-Many (OtM) Grant, funded by the Mellon Foundation, is working to provide a model for how local repositories, like Hyrax, interact with Distributed Digital Preservation (DDP) services (i.e., Chronopolis, AP Trust, LOCKSS, etc).
This presentation will offer an overview of the grant's goals, an update on the specifications under development, and a call to action for implementation.

8/23 Confirmed


:package:  bump website dependency @cmfcmf/docusaurus-search-local

Description
Bump website dependency @cmfcmf/docusaurus-search-local to 1.1.0
Checklist

[ ] My changes follow the contributing guidelines of this project.
[ ] I have performed a self-review of my code.
[ ] I have made corresponding changes to the documentation.
[ ] I have added tests that prove my fix is effective or that my changes work.
[ ] New and existing unit tests pass locally with my changes.

coverage: 95.043%. remained the same when pulling 18d1ed22373aea3696e3a92dd2ab58c5cc4ed51d on chore/website-dep-maintenance into d72b5939b42292be97ea925ef6a2a9d9664f5b99 on main.


Add integration with UniversalHub French Toast Alert API

Slapped together in 30min. Doesn't handle HTTP errors.

I think you need to add requests to dependencies.txt


there was an error with mrujs.confirm

Expected Behaviour
Should show confirm dialog after clicked destroy button
Actual Behaviour
It shows an error on console
there was an error with mrujs.confirm

Steps to Reproduce

create new blogs
try to delete one of theme

After trying to call window.confirm("hello") on inspector console, It throws error Uncaught InternalError: too much recursion

Do you have a repo I could look at? This looks like something is overriding window.confirm.

The repo is here !!!
https://github.com/karn18/abc

@karn18 is this still an issue in the latest v0.8.3? Apologies for leaving you hanging this long.

@karn18 is this still an issue in the latest v0.8.3? Apologies for leaving you hanging this long.

@ParamagicDev Now it works well after update to latest version. Thank you.


[bug, minor] Easter Eggs :: Unavailable Video

The Digital Rights to a YouTube video link referenced in this Easter Egg are in dispute and the video clip is no longer offered.
13:34:37.580 [info]  Farmbot-5e34 is jamming out to https://www.youtube.com/watch?v=d4nbfPZa9Ws :musical_score:

Fixed in next release.


[Bug]: Duplicate query string added when using LinkColumn and Datatable link property together

Describe the bug
I've just updated to the latest version of Evidence after the cache/bandwidth issue was rectified and I've found an issue where if a user has specified both a row-level link (using the 'link' property in the Datatable parameters) and a column-level link (using the contentType='link' property in the Datatable Column parameters), two query strings will be added to the URL resulting in a 404. Previously if this was the case, both of the links would work correctly without duplicating the query string.
Steps to Reproduce

Add a row-level link (using 'link' property in Datatable) and a column-level link (using 'contentType='link'').
Click on the row and two query strings will be added to the URL (although the URL will show up normally when you hover over it before clicking).
User will be greeted with a page not found message.

Logs
No response
System Info
System:
    OS: Windows 10 10.0.20348
    CPU: (8) x64 Intel(R) Xeon(R) Gold 6226R CPU @ 2.90GHz
    Memory: 14.82 GB / 32.00 GB
  Binaries:
    Node: 20.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.6.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (119.0.2151.97)
  npmPackages:
    @evidence-dev/core-components: ^4.8.8 => 4.8.8
    @evidence-dev/csv: ^1.0.12 => 1.0.12
    @evidence-dev/duckdb: ^1.0.11 => 1.0.11
    @evidence-dev/evidence: ^39.1.12 => 39.1.12
    @evidence-dev/mssql: ^1.0.10 => 1.0.10
    @evidence-dev/sqlite: ^2.0.6 => 2.0.6
    @timhoward/evidence-connector-mssql: 1.0.1 => 1.0.1

Severity
annoyance
Additional Information, or Workarounds
I've worked around it for now by removing the column-level link, although this results in cosmetic issues as users do not realise the row is a link because the link text is now plain.


Include Java 9 classes into coverage report

This solves problem described in https://github.com/jacoco/jacoco/issues/965

Coverage increased (+0.02%) to 99.612% when pulling c54939d8865a53341a994daa046cbbcc75f1f933 on Godin:include_java_9_classes_into_coverage_report into 8deda29c5a55131e9fe8af960125ef61bf810936 on amaembo:master.

Wow! Thank you very much! I completely forgot that every Maven problem can be fixed with a bit of Ant :-) Really appreciate your PR.

Wow! Thank you very much!

@amaembo you're welcome! :heart:

I completely forgot that every Maven problem can be fixed with a bit of Ant :-)

so true 🤣 anyway I still have to answer on https://github.com/jacoco/jacoco/issues/965
And note BTW seems that Coveralls doesn't fully/properly support such layout for multirelease JARs - it displays only src/main/java/one/util/streamex/VerSpec.java but not src/main/java-mr/9/one/util/streamex/VerSpec.java , while now target/site/jacoco/index.html displays both because they are declared in two different <group>s , jacoco-maven-plugin:report unlike jacoco-maven-plugin:report-aggregate defines single group, so same source/class name within same module is also not supported.
BTW Have you thought about replacing Maven by Gradle? 😉

Really appreciate your PR.

Let's keep going - #204 , #205 :wink:

And note BTW seems that Coveralls doesn't fully/properly support such layout for multirelease JARs

In my case, I can live with this. I decided to keep a bare minimum of code in the classes with the same FQN, so it's always covered. Everything else should have different FQN.

BTW Have you thought about replacing Maven by Gradle? 😉

I'm a complete newbie in Gradle, so migration would take a considerable amount of time, especially taking into account that I do some non-trivial things in Maven, so unlikely I can just copy-paste some snippets from SO to make everything working. Currently, the benefit is not quite clear to me.

@amaembo makes sense,
however exactly what is not so trivial with Maven might become trivial,
but you're right this will require Gradle knowledge,
so consider maybe one day when you'll get tired of tricks for Maven :wink:

@Godin btw see https://habr.com/ru/post/472312/

@amaembo nice 👍
However don't know why you wrote

Я использую JaCoCo, и если ему ничего не сказать, то второй прогон просто затрёт результаты первого.

Because it is exactly opposite - by default agent appends to the existing file. See append parameter of agent and corresponding append parameter of jacoco-maven-plugin:prepare-agent.
So unless there is some other reason, you can get rid of multiple exec files - #206 :wink:

Here is proof that file target/jacoco.exec after execution of mvn clean package contains both versions of class one/util/streamex/VerSpec:
$ java -jar ./jacoco-0.8.5/lib/jacococli.jar classinfo target/classes/one/util/streamex/VerSpec.class
  INST   BRAN   LINE   METH   CXTY   ELEMENT
     5      0      1      1      1   class 0xeaf239c6ccdf4975 one/util/streamex/VerSpec

$ java -jar ./jacoco-0.8.5/lib/jacococli.jar classinfo target/classes-9/one/util/streamex/VerSpec.class
  INST   BRAN   LINE   METH   CXTY   ELEMENT
     5      0      1      1      1   class 0x1457506964186199 one/util/streamex/VerSpec

$ java -jar ./jacoco-0.8.5/lib/jacococli.jar execinfo target/jacoco.exec | grep VerSpec
1457506964186199    1 of   1   one/util/streamex/VerSpec
eaf239c6ccdf4975    1 of   1   one/util/streamex/VerSpec


Link to develop branch of zend-psr7bridge is wrong

…because the branch doesn't exists!

Where?

On the status page, but in the meantime the problem has been solved.


feat: EDV REST provider iterator method

Also fixed the formatStore's Iterator method which before this change wasn't unformatting the values received from the underlying store's iterator, which was not the intended behaviour.
Signed-off-by: Derek Trider<EMAIL_ADDRESS>closes #2309

@llorllale This PR has been updated per our discussions with the team earlier.
Some changes to note:

The multiple, redundant decryption is gone. The REST Provider once again no longer has any encryption/decryption ability.

The Formatter's ParseValue method has been changed to ParsePair to accommodate the new design.

Now that the FormatProvider can do that filter logic, it's possible to have redundant filtering if the underlying provider's Iterator() method also does it. I added a boolean to the FormatProvider to allow the filtering to be optional, so if the caller knows that the underlying provider will do the filtering then you don't have to waste cycles doing a redundant filter. I think that with the larger storage rework we were discussing I should be able to avoid having this weird boolean, so I left a TODO. Also, you'll see a bunch of tests I added to check that behaviour across an underlying mem store and REST provider. I wanted the REST provider tests specifically to make sure the behaviour of the filtering is consistent.

I moved the mock EDV server under a new package in the mock folder since I use it across two different testing files now.

I moved the EDV models to a separate folder nested under the EDV folder to avoid a circular dependency due to the above change.

I added a few more iterator tests to the mem iterator test file in order to help me better test consistency with the FormatProvider's Iterator filtering.


Set genesis block body root to ssz hash of the empty struct rather than empty hash

A block is not useful unless it has a way to point to its parent block, so that an importer knows how to import it. Although the spec does not define it, all block intrinsically has a block identifier. Currently our block identifier is defined by previous_block_root:
signing_root(BeaconBlockHeader {
  	slot: block.slot,
	previous_block_root: block.previous_block_root,
	state_root: self.0.state_root,
	block_body_root: if is_genesis {
		Default::default()
	} else {
		hash(&block.body)
	},
	..Default::default()
})

Notice the if statement just for genesis block. If, instead, we change genesis block_body_root to empty struct signing root, it can be avoided.

I agree that we want to minimise special cases. I'm not sure though what the best genesis design is. Changing genesis_block.parent_root to signing_root(BeaconBlock()) means having two beacon blocks with slot 0.


Dynamic Form - Render FileLeafRef

Category
[ ] Enhancement
[ ] Bug
[x] Question
Version
Please specify what version of the library you are using: [3.11.0]
Question
Is it possible to render and update FileLeafRef in the Dynamic Form component? I've tried with fieldOverrides but I can't seem to load it.
Thanks!

Hi @BarendDS,
After investigating source code, actually the "Name" field ("FileLeafRef" internal name) is not selected during the component mouting process (eg the API call dedicated to retrieve all the fields from the target list). Therefore, it's not possible to override its rendering.
But maybe this could be an improvment idea for the control 🙂.


The connection was lost with error [code:7]

Then I use client with client_id
        reconnect_interval = 5
        self._mqtt_consume_ran = True
        while self._mqtt_consume_ran:
            try:
                async with Client(hostname=settings.mqtt_host, port=settings.mqtt_port, client_id='blabla44') as client:
                    async with client.messages() as messages:
                        await client.subscribe(self._resolver.get_sub_mqtt_topics())
                        rate_limiter = Semaphore(150)
                        async for message in messages:
                            self._loop.create_task(self._handle_mqtt_msg(message=message, rate_limiter=rate_limiter))
            except MqttError as e:
                self._logger.error(e)
                await sleep(reconnect_interval)

I am getting this error every 5-10sec
Could not gracefully disconnect due to "[code:7] The connection was lost.". Forcing disconnection.

Checked again, it really works. Looks like I had a hard day at work, thanks


feat(orm): Provided module

Codecov Report
Attention: 9 lines in your changes are missing coverage. Please review.

Comparison is base (d43a58d) 97.21% compared to head (82451b3) 97.56%.

Files
Patch %
Lines

orm/plugin/trace.go
92.77%
4 Missing and 2 partials :warning:

orm/healthcheck/probe.go
86.95%
2 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
+ Coverage   97.21%   97.56%   +0.34%
==========================================
  Files          65       11      -54
  Lines        1651      369    -1282
==========================================
- Hits         1605      360    -1245
+ Misses         34        6      -28
+ Partials       12        3       -9

Flag
Coverage Δ

config
?

generate
?

healthcheck
?

httpclient
?

httpserver
?

log
?

orm
97.56% <96.13%> (?)

trace
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Clean Shutdown

Watch for signals
Call a Shutdown action when a signal is received

I thought this would be a nice addition. Gives you a chance to call server.Stop() or just os.Exit(0). Putting it in cli means writing less identical code even if it is just a channel and a call to Notify.

Hey! So, this traps all signals which is probably not what most users want (consider syscall.SIGWINCH e.g.). I could see maybe trapping just SIGTERM here, but I'm not sure we are gaining much over just having the user trap the signal in their own code if they desire to (especially since they will likely want to trap within each subcommand/command to do specific cleanup if they have subcommands).
Thank you for suggesting this though!


Replace local pointer-ing mechanism with the known k8s.io/utils/pointer

          there are other places in the codebase which can benefit to move to `k8s.io/utils/pointer`. I actually welcome this change. But it should be done all in once: the only thing I'm not fine with is having both the old clunky way I started (reinventing `k8s.io/utils/pointer` locally) and using `k8s.io/utils/pointer`.  Either you submit a PR to convert to `k8s.io/utils/pointer` everywhere and get that PR merged before to move on with this one (fine) or you use the old way in this new PR and convert to `k8s.io/utils/pointer` with a later PR

Originally posted by @ffromani in https://github.com/openshift-kni/numaresources-operator/pull/700#discussion_r1357781930

/assign @shajmakh

/unassign @shajmakh
/assign @ffromani


prisma:engine stdout Unknown error

Recently the prisma:engine logging is full with Unknown error message:
...
  prisma:engine stdout Fetched a connection from the pool +10ms
  prisma:engine stdout Unknown error +23ms
prisma:query BEGIN
  prisma:engine stdout Unknown error +61ms
prisma:query SELECT "public"."BuyerGroup"."id" FROM "public"."BuyerGroup" WHERE 1=1 OFFSET $1
  prisma:engine stdout Unknown error +63ms
prisma:query SELECT "public"."BuyerGroup"."id" FROM "public"."BuyerGroup" WHERE 1=1
  prisma:engine stdout Unknown error +22ms
prisma:query COMMIT
...

Logging can be achieved with DEBUG=* and
const prisma = new PrismaClient({
  log: ['query', 'info', `warn`, `error`],
})

@janpio any specifics that is required for a reproduction? I can't reproduce this on a simple local project.

Maybe NodeAPI flag @janpio?

That would be possible, no recollection after 4 weeks. Will observe if I see it again.

I will close it for now

@tehnorm Which version of prisma and @prisma/client are you using and could you share your Prisma Client query and schema maybe?
along with:

OS:
Database:
Node.js version:

It will help to reproduce this.

Hi @Jolg42 - here are those details:

OS: Mac OS - 10.15.1
Database: PostgreSQL 13
Node.js version: v15.0.1

Can you also share your npx prisma -v output @tehnorm please?

npx prisma -v
npx prisma -v
Environment variables loaded from .env
prisma               : 2.29.1
@prisma/client       : 2.29.1
Current platform     : darwin
Query Engine         : query-engine 1be4cd60b89afa04b192acb1ef47758a39810f3a (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 1be4cd60b89afa04b192acb1ef47758a39810f3a (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 1be4cd60b89afa04b192acb1ef47758a39810f3a (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 1be4cd60b89afa04b192acb1ef47758a39810f3a (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : 1be4cd60b89afa04b192acb1ef47758a39810f3a
Studio               : 0.419.0

Weird, that looks perfectly fine. Can you maybe create a small reproduction project with the minimal setup required to reproduce this? Would be really helpful for us.

This also popped up over here: https://github.com/prisma/prisma/discussions/9115

I haven't had time to recreate this but I can confirm it's happening somewhere in getBacktraceFromLog() https://i.imgur.com/jbVxih1.png

Here is a little more info: https://i.imgur.com/DcqnDEn.png - This is logging log4.

Thanks. That makes total sense, the problem is that we do not fully understand how this is happening. Can you maybe copy the text of your second screenshot and post it here? That might be useful. What kind of queries are you executing for this to happen?

Sorry for the ping @tehnorm but is this still relevant? We can close this otherwise.

I also got "Unknown error" logged from prisma:engine - https://github.com/prisma/prisma/discussions/16329

I tried reproducing and no luck.
The only instance of "Unknown error" in the code, in any of prisma and prisma-engines is imposible it is related to this problem as it a WASM specific code added very recently.
query-engine/driver-adapters/src/wasm/error.rs
11:        .unwrap_or_else(|| "Unknown error".to_string());

The history of commits that added or removed that expression "Unknown error" in both prisma or prisma-engines have been inspected and don't contain any smoking gun.
I'm going to close this as I can't reproduce anymore. And it's uncertain whether this is still an issue.


Try to bring back storage classes and add more numeric types

Removed storage classes as they clash with unions. e.g.
var a: <x: number | string> = <x: 1>

When inferring the type of the record literal, x is a number. However, as type stores x as a union. During type checking in isAssignableTo, the literals x is expanded to a union, so the literal can ve constructed and assigned accordingly.
The case above is easy, but there are other cases, where this becomes untractable, at least with the implementation I had. Of course I don't have any examples...
I'm convinced there's a way to make this work, so storage classes can be introduced again. With those, we can also add more primitive numeric types, like ints, or characters.


Segment Anything Version

Any thoughts on using Segment Anything? Seems like it might be a good fit to replace the Google models.

+1

Sounds interesting indeed. For now I don't fully understand the best way to provide Segment Anything with the class "person" or "body" that we'd like to segment. Needs a bit of investigation and experiment.

Grounded segment anything with "Human" as input seems to work pretty well.

But I do not really know much in Python universe so I don't know the struggle it would be to add this into the project

https://twitter.com/xenovacom/status/1650634015060156420
With Onnx getting WebGPU support and Segment Anything offering an Onyx model, should be possible starting with Chrome 113.
Also relevant: https://github.com/gaomingqi/Track-Anything


Bitbucket server with bearer tokens

Hi, 👋🏻
I'm testing PAC with Bitbucket Server.
With a personal access token (username/token) I can get it to work fine.
I'm trying to test with a project bearer token, which doesn't require a username.
I know the bearer token works with curl
BEARER='bear_token_here'
PROJECT="project_name"
REPO="repo_name"

curl  \
  --insecure \
    --header "Authorization: Bearer ${BEARER}" \
    https://bitbucket.mycorp/bitbucket/rest/api/latest/projects/${PROJECT}/repos/${REPO}/commits

But when I define the Repository resource, I receive an error if I leave the username out, as shown here
I thought I might get away with a placeholder username, but looks like basicAuth is the only option at present when I look here
Have I missed an option somewhere to setup Bitbucket server with a Bearer token?
Thanks.

I think it's something we will have to fix...

@chmouel Is there any plans to look into this? Would be great to use Pipelines as code with Bitbucket without depending on a personal user token.

I'd also like to request the possibility to use project and repo scoped access tokens instead of (or as well as) user scoped tokens.

cc @zakisk
we are going to restart the work on bitbucket server but this will take a bit of a while to get fix all the issues with the driver


[BUG] Kubernetes cluster unreachable: Get "http://localhost:8080/version": dial tcp <IP_ADDRESS>:8080: connect: connection refused

When I ran a bash script, as soon as it executed helm upgrade -i graphrag ./helm/graphrag -f, I encountered the following error
Error: Kubernetes cluster unreachable: Get "http://localhost:8080/version": dial tcp <IP_ADDRESS>:8080: connect: connection refused

local helmResult=1
true
set +x

I tried kubectl get pods, I got below result:
E0713 07:45:47.871185   24992 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused
E0713 07:45:47.871693   24992 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused
E0713 07:45:47.873291   24992 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused
E0713 07:45:47.873480   24992 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused
E0713 07:45:47.874953   24992 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?

I Installed  minikube on my machine and It automatically fixed my issue


BREAKING CHANGE changed attr property on elements to attributes

Coverage remained the same at 66.193% when pulling 2b472b171915b58afffe5a6890a9fcb3d7f4ab7f on feat/change-attr-to-attributes into 68ab07f6bd97a71f46e461fdee4fad358ed32820 on master.


Hex support

Hi! Could you be so kind to add cqerl to Hex. Guide is already there. Currently i am trying to publish another package that depends on cqerl and got this:
** (Mix) Stopping package build due to errors.
Dependencies excluded from the package (only Hex packages can be dependencies): cqerl

Got the same problem myself! Some of this package's dependencies aren't hex packages.
Well, let me try again now to see if they moved to hex.

Is anything changed so far? which are the dependencies that are still missing?

Just landed in https://github.com/matehat/cqerl/commit/839132cbe6c786cedb4400876c9006b26b6a662f


Implement carton bundle command

This command should invoke swift build (reusing the toolchain inference code that's already used by carton dev and carton sdk) in the directory for the only executable product, or a product specified with the --product option, similar to how carton dev infers a product to build. It should build the app in the release mode with swift build -c release, possibly passing -Osize flag to swiftc if it the release configuration doesn't do this by default already. After that, it should look for the presence of wasm-strip and wasm-opt on the system and apply size optimizations with those if present, otherwise suggesting to install corresponding WABT and binaryen packages (via Homebrew on macOS).
We also need a new bundle.js JavaScript entrypoint, similar to what we have with dev.js, but without the WebSocket bits, as the release bundle doesn't need hot reloads. This entrypoint should also by compiled by webpack in prod mode for size optimizations. The only question I don't have a clear answer to is, what the final bundle directory should be to which carton bundle writes the output? A few suggestions:

.build/bundle/wasm, means that the generated fails get ignored by Git most probably (since .build is in .gitignore most of the time)
Bundle, capitalized for consistency with Sources and Tests
CartonBundle, in case Bundle is used by other tools, but this one seems a bit verbose to me.

I have a slight preference towards the first option as these files are not supposed to be added to the repository in most of the cases, but the problem is that .build is not visible in Finder and other file managers by default, so I could see some beginner users not finding the final product on the file system. With directories like Bundle we'd need users to explicitly opt out of committing the final products to their repository (again, most of the time, unless they don't have .build in their .gitignore yet, which would make this point applicable to the .build option too).

If bundle.js is just an entry point, I would suggest just minify it when building Carton.
Personally I would prefer Bundle since different tools always seemed to use different default output directory. My frontend experience tells me it can often differs project to project. At the end I don't think it's necessary to "guess" what users' .gitignore may contains. (Actually none of my own projects, nor my user default includes .build in .gitignore.) I think mentioning the output directory and when the .gitignore does not includes Bundle, warn users to do so is enough.
Just my 2 cents, just tried SwiftWASM and it's good. Saw this wandering throughout repos so sorry for suddenly dropping a comment from nowhere. 😅

If bundle.js is just an entry point, I would suggest just minify it when building Carton.

Yes, this is exactly what we're doing already for dev.js. It's packaged in the static.zip archive attached to the release assets. This archive doesn't change much between releases (but obviously will change when bundle.js is included in it), so the latest 0.2.0 version still has a url for static.zip from 0.1.3 hardcoded in it. The archive is not committed to the git repository though, so we don't increases the size of the repository for no good reason. It's downloaded and unpacked automatically when carton detects that ~/.carton/static directory is missing, or when SHA256 hash of dev.js differs from the hash hardcoded in the carton binary itself.

I think mentioning the output directory and when the .gitignore does not includes Bundle, warn users to do so is enough.

Great point about warning users, this is definitely something I think it would be great to implement 👍

Just my 2 cents, just tried SwiftWASM and it's good. Saw this wandering throughout repos so sorry for suddenly dropping a comment from nowhere. 😅

Thanks for your feedback, and no problem at all. 🙂 I definitely do want people to feel free leaving their feedback. It's all still at an early stage, but the more feedback we have, the better we can become. All feedback and contributions are very welcome where you have it, that's why all the development is open and I hope is as transparent as possible.


Repositories::Updater#recreate spec is flakey

🙎  The Repositories::Updater#recreate spec does not run predictably. An example of a recent failure follows:
Failures:

  1) Repositories::Updater#recreate resets and forces a run
     Failure/Error: expect(Snapshots::EventCount.find_by_id(last_updated_event.id)).to be_blank
       expected `#<Snapshots::EventCount id: 2, snapshot_name: "global_event_pointer", event_id: 3>.blank?` to return true, got false
     # ./spec/models/repositories/updater_spec.rb:134:in `block (3 levels) in <top (required)>'

Happened again.
Failures:

  1) Repositories::Updater#recreate resets and forces a run
     Failure/Error: expect(Snapshots::EventCount.find_by_id(last_updated_event.id)).to be_blank
       expected `#<Snapshots::EventCount id: 2, snapshot_name: "global_event_pointer", event_id: 2>.blank?` to return true, got false
     # ./spec/models/repositories/updater_spec.rb:134:in `block (3 levels) in <top (required)>'

Finished in 17.54 seconds (files took 7.05 seconds to load)
686 examples, 1 failure

Failed examples:

rspec ./spec/models/repositories/updater_spec.rb:120 # Repositories::Updater#recreate resets and forces a run

https://circleci.com/gh/FundingCircle/shipment_tracker/2365


Allow outside clicks always, except when modal is in the loading state

There's an interesting question on SO: https://stackoverflow.com/q/47925036/1331425
After some thinking I would like to propose the non-breaking change:
Convert the allowOutsideClick from boolean to:
allowOutsideClick?: 'always' | 'when-not-loading' | false;

'when-not-loading' looks ugly for me though, I would like to come up with the nicer parameter. Ideas are welcome.
@angrykoala will this solution be acceptable for you?
Opinions from collaborators and the community are welcome!

There are likely cases where someone is passing allowOutsideClick: true, for example (1) to override the defaults set with swal.setDefaults, or (2) because true is the result of an expression. So if we are to go the proposed route, I might suggest changing the type to something like allowOutsideClick?: true | 'when-not-loading' | false;. This would make the change fully backwards compatible; no need for a warning or an eventual breaking change (when the next major is released), and it wouldn't immediately break type-checking in projects that have it. We could think of a simple true as an unqualified affirmative, a.k.a. "always".

Another route we could go, which would eliminate the ugliness of 'when-not-loading' and could serve a broader use-case:

For allowOutsideClick, accept a boolean or a function with no args that returns a boolean (I think the type would look something like allowOutsideClick?: boolean | () => boolean)
Add a getter method to expose the "loading" state, i.e. swal.isLoading()
Possibly add more getter methods, exposing other bits of state, particularly swal.isValidating() since it's pretty similar.

This way for @angrykoala's use-case we would simply pass allowOutsideClick: () => !swal.isLoading(). Or for basically the same case, but when we also have an async inputValidator, allowOutsideClick: () => !swal.isValidating && !swal.isLoading().

I can make the PR if we go the allowOutsideClick-as-a-function route

why not a method to change the allowOutsideClick to be set? similar to showValidationError in the example?
would that be feasible?, if not I feel the second idea from @zenflow would be better than using string
thanks for your help

For allowOutsideClick, accept a boolean or a function with no args that returns a boolean (I think the type would look something like allowOutsideClick?: boolean | () => boolean)
Add a getter method to expose the "loading" state, i.e. swal.isLoading()
Possibly add more getter methods, exposing other bits of state, particularly swal.isValidating() since it's pretty similar.

Perfect! :+1: :+1: :+1:

why not a method to change the allowOutsideClick to be set? similar to showValidationError in the example?

It's not possible to change params after popup initialization.

if not I feel the second idea from @zenflow would be better than using string

Yeah, I like it more as well. It'll provide a flexibility for future needs.
@zenflow please go ahead with the PR :rocket: Many thanks, you're making this plugin better!
Happy holidays everyone! :gift: :gift: :gift:

https://jsfiddle.net/limon/k6vm7y5o/ :tada:


Have a global setting for notifications

An env var to select a default enabled notification (by name or some other identifier) please.

Having to select this per notification is tedious. Thanks!!

Merged PR: https://github.com/louislam/uptime-kuma/pull/340
You can check it in current master branch


Syntax highlighting doesn't work for Python cells with magic

If I have a cell in a Python 3 notebook that says e.g.
%%time
# some python code

then when rendered with nbsphinx, the # some python code looses its syntax highlighting. Could it be made so that the syntax highlighting is kept, the same way it does in Jupyter notebook itself?
Some info about my setup incase its just a bug:
nbsphinx==0.2.9
Sphinx==1.4.6
ipython==5.1.0
jupyter-client==4.3.0
jupyter-core==4.1.1

The Jupyter Notebook and nbconvert seem to handle that differently. nbsphinx is normally closer to nbconvert, since it uses a lot of code from there. I think the highlighting in the Jupyter Notebook is done with client-side JavaScript, which cannot be re-used in nbsphinx.
I just enabled processing of cell magics in #60. However, the %%time magic still has no syntax highlighting, same as in nbconvert.
The ipython3 lexer seems to disable syntax highlighting when a cell magic is present.
I just saw that this was already reported to nbconvert (https://github.com/jupyter/nbconvert/issues/105) and ipython (https://github.com/ipython/ipython/issues/9099). Once this is resolved, it should automatically work in nbsphinx, too.

Thats great, thanks for that. Will wait on the IPython fix then!

Any updates here ? Still does not work with %%file.

You should ask over there: https://github.com/ipython/ipython/issues/9099

It mostly works now, the missing %%file stuff should be fixed in https://github.com/ipython/ipython/pull/11384.

My PR has been merged, so I think this should be fine now.
If there is still some highlighting missing, please leave a comment!

Hello @mgeier, I'm commenting this because I have the same issue, on a custom magic.
The syntax highlighting within the Jupyter document works fine:

But, when renderer using nbsphinx, it does not work:

Any idea on how to fix that?

What does nbconvert do?
See https://github.com/spatialaudio/nbsphinx/issues/59#issuecomment-243383017.

@mgeier nbconvert also fails: should I report that to them?
(Within the notebook viewer)

(When exported as HTML)

nbconvert also fails: should I report that to them?

Yes, or maybe even to IPython, see e.g. https://github.com/ipython/ipython/issues/9099 and https://github.com/ipython/ipython/pull/11137.

@mgeier done :-)


Big lag spikes with parallax on terrain since 3.9

I noticed a significant loss in fps count since 3.9 when I activated parallax on terrain.
In a scene where I got 60fps (with V-sync) it drops down as low as 30fps sometimes, especially when turning around quickly or zooming to somewhere, resulting in a clearly noticeable lag.
Turning off V-sync helps a bit, but there are still significant lag spikes.
In my latest stable build which is based on 3.8 there is no noticeable lag spike when parallax on terrain is on, the fps stay at a stable 60fps with V-sync as it is supposed to be.
This is weird since 3.9 runs overall faster, but when activating parallax on terrain it is overall much slower. I'm aware that parallax is very heavy, but it never used up that much performance, maybe 10-20% at max before and without lag spikes, but now it eats up to 50% performance with heavy lag spikes.

hmmm not sure if is parallax, but I ran the profiler a few weeks ago and I see a huge FPS drop since 3.5 to 3.9 just using a plain Empty Terrain (sand level).

I just told you, that it happens with parallax on. I know what buttons I switch.
And the default templates all have no parallax textures at all, so you need to add some proper parallax ready terrain textures and paint them on a terrain to test this.

So I found out that this happens only on my biggest map that is 1km squared, since the other maps are significantly smaller and the fps drop is not that noticeable.
Second condition is, the map must have parallax terrain textures, the amount of parallax textured ground does not seem to play a big role.
Third condition is there must be V-sync on, V-sync gives significantly higher fps drops.
And Fourth condition is zooming.
So when I zoom in on a distand area the fps drop with V-sync on from 60fps to roughly 30fps, but when I have V-sync off, it drops from roughly 65 fps to roughly 58 fps and the lag is almost not noticeable in compared to it being very noticeable with V-sync on.
I added this PR for the test: https://github.com/GarageGames/Torque3D/pull/1838 it re enables face culling which solved the lags in most places in my level, now there is only significant lag when I zoom in on a distant area and there is some parallax textures in the view field and V-sync is on.


:construction_worker: fix: Fix git shas

Description
Fix git shas which were uncommented
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #214   👈

PR #211

PR #212

PR #213

This comment was auto-generated by Graphite.


Added auto login for teachers when previewing an activity

@scytacki I changed the code to test for all non-anonymous users and changed the query parser/building code to use Rack::Utils.

👍


Merge command line tools

This pull request combines the three legacy command line tools into a new pyocd tool with subcommands for the existing functionality. The tool is implemented as the pyocd.__main__ module, so pyOCD can now be invoked by running python -mpyocd.
Usage:
usage: pyocd [-h] [-V] [--help-options]  ...

PyOCD debug tools for Arm Cortex devices

optional arguments:
  -h, --help      show this help message and exit
  -V, --version   show program's version number and exit
  --help-options  Display available session options.

subcommands:

    commander     Interactive command console.
    cmd           Alias for 'commander'.
    erase         Erase entire device flash or specified sectors.
    flash         Program an image to device flash.
    gdbserver     Run the gdb remote server(s).
    gdb           Alias for 'gdbserver'.
    json          Output information as JSON.
    list          List information about probes, targets, or boards.

Command line arguments have been normalized across tools. They are generally compatible with legacy tools, but there are some changes. Also, some of the more esoteric options have had their command line arguments dropped in favour of the generic method of setting session options.
The biggest argument change is that --board no longer selects the debug probe. That is now handled by --uid, with --board reserved for future selection of board name (like --target, but for boards).
The erase functionality previously in pyocd-flashtool has been extracted into the erase subcommand.
Features that were previously implemented directly as part of the legacy tools has been refactored into reusable modules: programming bin, hex, or elf files into flash, chip and sector erasing, hex dumps, and generating dictionaries for JSON output.
The three legacy tools now output a warning that they are deprecated.
As part of this change, pyOCD will look for and load a pyocd.yaml or pyocd.yml config file in the working directory.
Fixes #448.
Closes #395.

/morph test

/morph test

@arekzaluski Fyi, this PR include the board listing functionality in #395.

cc @MaureenHelm

fixes #448

/morph test

Rebased and squashed.

/morph test

Looks really good. I've done quick testing and I enjoy being able to run all commands using single tool. I haven't yet looked at the code. I'm only missing reset command that we are using from pyocd-tool.

Thanks for taking it for a test drive.
You actually helped me discover a bug! You should should be able to reset the target by running pyocd cmd -c reset. Similar for any other of the interactive commands. However, it was not correctly splitting commands provided this way: pyocd cmd -c 'rw 0 8' did not work.

/morph test


Bug where searching displays all results on respective page

When searching for a class or professor, the respective pages displays all professor/class descriptions when it shouldnt

Also made it where the class reviews also were displaying correctly. after some change didn't work anymore


Update to owlready0.45

With owlready2==0.45 python names are added as triplets, whcih changes how the ontology is.
Description

Type of change

[ ] Bug fix.
[ ] New feature.
[ ] Documentation update.
[ ] Test update.

Checklist

This checklist can be used as a help for the reviewer.

[ ] Is the code easy to read and understand?
[ ] Are comments for humans to read, not computers to disregard?
[ ] Does a new feature has an accompanying new test (in the CI or unit testing schemes)?
[ ] Has the documentation been updated as necessary?
[ ] Does this close the issue?
[ ] Is the change limited to the issue?
[ ] Are errors handled for all outcomes?
[ ] Does the new feature provide new restrictions on dependencies, and if so is this documented?

Comments

Closed wiht #795