sidebar generation does not work as expected when nbs are in folders 3 or more levels deep

Provide a minimally reproducible example

start a new project with the nbdev_new template
add new notebooks in the nbs folder 3 or more levels deep

This is what a project of mine look like

Upon running nbdev_preview, the sidebar is generated but it created a different section of a nb in the same category

The generated sidebar looks like this,
website:
  sidebar:
    contents:
      - index.ipynb
      - section: exp
        contents:
          - section: camvid
            contents:
              - exp/camvid/4 labels.ipynb
      - section: exp
        contents:
          - section: camvid
            contents:
              - exp/camvid/Untitled0.ipynb
      - section: exp
        contents:
          - section: camvid
            contents:
              - exp/camvid/camvid.ipynb
      - section: exp
        contents:
          - section: camvid
            contents:
              - exp/camvid/skimage save camvid labels.ipynb

It should ideally look like this
website:
  sidebar:
    contents:
      - index.ipynb
      - section: exp
        contents:
          - section: camvid
            contents:
              - exp/camvid/4 labels.ipynb
              - exp/camvid/Untitled0.ipynb
              - exp/camvid/camvid.ipynb
              - exp/camvid/skimage save camvid labels.ipynb

@hamelsmu do you think this is expected behavior or is it a bug?

Seems like a bug - won't have time to look at this for a long time though :/
If you are up for please feel free to send a PR and I'll happily review

Fixed in #1307. @hamelsmu can you please close this issue? this is now fixed.


[Bug]: Hits not displaying and getting error message on console

Version of the software
0.2.5
Operating system
Windows 10
Browser / Native
Chrome 123
What happened?
Am getting error "System.InvalidOperationException: The property 'HitEntity.Id' has a temporary value while attempting to change the entity's state to 'Unchanged'. Either set a permanent value explicitly, or ensure that the database is configured to generate values for this property." in console. Cannot see hits so have changed my config to save to file instead.
Relevant LoliCode if needed
No response

Are you using the web or native client? Do you have a way to reliably reproduce this?


system_advanced_firewall display State Timeouts section

A few little code style bits
Make the State Timeouts section actually appear (add the section to the form)
The State Timeouts section was trying to do groups of fields, which spread themselves horizontally. That did not fit across a reasonable screen nicely, specially for the 6 different TCP timeouts. So the groups thing is removed and each field is its own input in the section, all vertically below each other.
Fixed various cut-and-paste bugs in the variable naming of the timeouts code.
Added logic to be able to generate the key name (like tcpfinwaittimeout) from the screen displayed text (like "FIN Wait"). Previously the "FIN Wait" case would not work with the simple strtolower($name)
This works now. If someone wants to mess with grouping the TCP, UDP, ICMP and Other in some way, then great.

The state timeouts seem fine in rows of their own, although the help text is completely pointless. If the section heading said: “State timeouts in seconds. (Leave blank for default)” it could all be removed.
Steve
Stephen Beaver | +1<PHONE_NUMBER>;239 |<EMAIL_ADDRESS>| www.netgate.com

On Dec 15, 2015, at 12:03 PM, Phil Davis<EMAIL_ADDRESS>wrote:
A few little code style bits
Make the State Timeouts section actually appear (add the section to the form)
The State Timeouts section was trying to do groups of fields, which spread themselves horizontally. That did not fit across a reasonable screen nicely, specially for the 6 different TCP timeouts. So the groups thing is removed and each field is its own input in the section, all vertically below each other.
Fixed various cut-and-paste bugs in the variable naming of the timeouts code.
Added logic to be able to generate the key name (like tcpfinwaittimeout) from the screen displayed text (like "FIN Wait"). Previously the "FIN Wait" case would not work with the simple strtolower($name)
This works now. If someone wants to mess with grouping the TCP, UDP, ICMP and Other in some way, then great.
You can view, comment on, or merge this pull request online at:
https://github.com/pfsense/pfsense/pull/2239 https://github.com/pfsense/pfsense/pull/2239
Commit Summary
Update system_advanced_firewall.php
File Changes
M src/usr/local/www/system_advanced_firewall.php https://github.com/pfsense/pfsense/pull/2239/files#diff-0 (92)
Patch Links:
https://github.com/pfsense/pfsense/pull/2239.patch https://github.com/pfsense/pfsense/pull/2239.patch
https://github.com/pfsense/pfsense/pull/2239.diff https://github.com/pfsense/pfsense/pull/2239.diff
—
Reply to this email directly or view it on GitHub https://github.com/pfsense/pfsense/pull/2239.

Yes, but I guess at least it has replicated the functionality and text from 2.2.* - if someone wants to reduce the mindless repetitive help text, then great.
I will keep going with code style, because while scanning through for code style I am finding all sorts of odd bits of stuff to fix.

Thank you Phil :)

I see you already removed the help text duplication in a later commit - good stuff.


Why does the 1.11 version require forge?

First I apologize if this is in the wrong section, I'm new here and have no idea how this works, my apologies
I thought the other versions didnt require forge. While this isnt a big deal for singleplayer, it is extremely limiting for multiplayer as you need to have forge on the server to play. I really hope you can release a stand alone version
Thanks

I haven't tried forge for minecraft 1.11 yet but unless they removed the ability of a forge client to connect to a vanilla server you should be able to use the pixelcam on a server.

There isn't even a 1.11 version on the plugin

The 1.10 version may be compatible with 1.11, though I'm not sure. Every version of the PixelCamMod so far has needed Forge, and that won't change. It's perfectly possible to join any Minecraft server with Forge clients.

Oh, I see.
I apologize for my extreme stupidity and lack of information here. It's been a while since I played modded-multiplayer and it appears I've forgotten all my info.
Apologies for the inconvenience.
Thanks to all of you for replying. This is great news


feat: Improve controller Dockerfile caching

There's no reason to continually do things like fetching eBPF compilation dependencies, rebuild eBPF, fetch Go dependencies, etc. over and over.  Most of these things will not change frequently, so deserve to be aggressively cached by Docker layers. The things that are more likely to change can then have a much faster build process.
This entailed reducing some of the intermediate image sprawl into a single "bins" image so that cache layers could be reused.

@timraymond can you resolve the merge conflict so we can get this in?

@nddq Thanks for the heads up. I wish the merge queue would ping when there's actionable problems for the author to fix.

@timraymond THis would be very useful to everyone - can you resolve the conflict and merge?

Ack. Will prioritize

github says these commits are from a timposter

@rbtr argh, good catch. New environment and didn't have commit.gpgSign set in the fresh clone. Done.

RCA of build failures found. Just need an equivalent for windows.

@timraymond can you attach the before and after build time?

Before (luke-warm cache): make retina-image BUILDX_ACTION=--load 3.04s user 1.30s system 2% cpu 2:34.11 total
Before (hot cache): make retina-image BUILDX_ACTION=--load 3.05s user 1.44s system 3% cpu 2:12.67 total
After (luke-warm cache): make retina-image BUILDX_ACTION=--load 2.70s user 0.95s system 8% cpu 45.541 total
After (hot cache): make retina-image BUILDX_ACTION=--load 2.69s user 1.16s system 51% cpu 7.474 total

Building the retina agent image takes 60s for (another 60s for operator) - are you really seeing 2s? :O

@rectified95 That's the output from time, so total wall clock is all the way to the right. It's about 45s if you need to fetch Go modules. For example, if I change some log messages around (i.e. just the Go logic), rebuild time is about ~10s.


Fix strict/es5+ octal literal 2x error #46810

Signed-off-by: Jay Clark<EMAIL_ADDRESS>Partially fixes #46810
Fixes the conditional in the binder to only issue an error for octal literals in strict mode if the target is before es5. (If es5 or after, this error becomes redundant.)
Please verify that:

[X] There is an associated issue in the Backlog milestone (required)
[X] Code is up-to-date with the main branch
[ ] You've successfully run gulp runtests locally
[ ] There are new or updated unit tests validating the change

(Waiting for feedback on comment in issue thread before addressing testing.)

Great, thanks so much for the quick feedback! The testing is a bit harder for me (I’m still very junior), so I just wanted to check my fix wasn’t completely off base before I dove into it. :)

Lost a few days being under the weather from getting my COVID booster, but I think I've finally got the tests sorted. I also updated the logic in tsserver.js so that there would be consistency there, but I see the PR has been flagged because of that. It doesn't seem like tsserver.js is a file to which the warning applies (and unless the logic is changed in it, tsserver.js will continue throwing two errors for octal literals in strict mode in ES5+).

Sure thing, sorry for the oversight!

This is a good fix. Do you mind if I finish it by adding a test + accepting baselines? If you want to finish it yourself in a few months that's fine too.

@sandersn That would be fine. I meant that I'd try my hand at solving a different issue. I'm stuck on creating the TS test and need to learn the language, repo, and test strategy better before I'd be able to complete it (which realistically I wouldn't be able to spend time on until I'm done with my coursework in January.)

@sandersn Thank you so much for your help in closing this out. The added test may have only been a few lines of code, but I really could not wrap my head around how the test suite works in this repo (I've only really worked with jest) and would probably not have gotten there for quite some time.
Just so I understand it correctly for the next time I take a stab at an issue here, when adding a TS test all that's needed is to write the code snippet that will be evaluated. When I run the tests, the testing suite will create a .txt file of the errors that are thrown. Presumably these errors will differ from the baselines because something in the Typescript code has been changed/corrected. If the errors look correct, I then run the command to accept the new baselines.
TLDR: There is no need to code any assertions into the test regarding what errors are expected (this is where I kept getting hung up), instead the code throws & records the errors in the testing process and the developer evaluates that the errors are correct and adds them to the baselines.

You got it exactly right. Our system is quite different from unit tests since the assertions are implicit in the baseline output. That means there are a lot of assertions — even ones that the author didn't intentionally put there.


bug(sink): panic on should not receive any data after pause

Describe the bug
The only compute node panicked on panicked at src/stream/src/executor/sink.rs:277:21:\nShould not receive any data after pause.
The user was creating multiple sink into table at the time.
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
v2.0.2
Additional context
No response

IIUC this failed assertion is only in the code path of SINK that writes into external system. It cannot be reached for SINK INTO TABLE.
However, there is no SINK that writes into external system in the case.

I think the panic is due to this no-op pause&resume for sink that is decoupled.

I believe this is caused hash agg can emit data chunk on window close on receiving a barrier, even when the stream graph is already paused.
@stdrc


feat(assets): file upload extension validation

this PR adds:

file extension validation
filter between uploaded file extensions
file upload button to access dropdown

but there is no token validation for adding extension(so there is still a security issue), is it a good idea to add a token? param to updateOptions RPC ?
https://github.com/nuxt/devtools/assets/38922203/919a0899-99d5-4281-8e3b-1beef0e21a00

Why do we need to valid the extension of uploads?

@antfu to be more safe, for example when accessing from a public network, we make sure that nothing harmful(e.g. an .exe file) can't be uploaded unless the user wants to.

In that case, I think we should make it in the module options (nuxt.config.ts) that are not updatable from the client, and do the verification on the server side,

@antfu sure! that cross my mind too. thanks

Could you help resolve the conflicts? Thanks!

Could you help resolve the conflicts? Thanks!

Sure! I'll try to do it today. thanks


RetDec.flare v<IP_ADDRESS> Installation Error

RetDec.flare v<IP_ADDRESS>
retdec.flare package files upgrade completed. Performing other installation steps.
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
Error - hashes do not match. Actual value was '718524FA09414DEBD95058CE4E92FAC542177A1E0BAA7FC12B82395DCBE916D6'.
Downloading retdec
from 'https://github.com/avast/retdec/releases/download/v3.3/retdec-v3.3-windows-64b.zip'
Downloading retdec
from 'https://github.com/avast/retdec/releases/download/v3.3/retdec-v3.3-windows-64b.zip'
Progress: 1% - Saving 4.81 MB of 248.39 MB                                                                                ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://github.com/avast/retdec/releases/download/v3.3/retdec-v3.3-windows-64b.zip'. Exception calling "Read" with "3" argument(s): "Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."
The upgrade of retdec.flare was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\RetDec.flare\tools\chocolateyinstall.ps1'.
See log for details.
Chocolatey upgraded 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures

retdec.flare (exited 404) - Error while running 'C:\ProgramData\chocolatey\lib\RetDec.flare\tools\chocolateyinstall.ps1'.
See log for details.
Chocolatey reported an unsuccessful exit code of 404. See C:\Users\Vedanth\AppData\Local\Boxstarter\boxstarter.log for details.

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM has just been released and will make the project more open and maintainable.
Please check out our blog post at https://www.mandiant.com/resources/blog/flarevm-open-to-public and give the new installation a try.
If this problem still persists with the new installation, please report:

new tools or tool-related issues at https://github.com/mandiant/VM-Packages/issues
ideas and issues related to the installer script and configuration at https://github.com/mandiant/flare-vm/issues

Please note that we use this message to close all legacy issues in this repository. We look forward to your feedback and support for the next generation of FLARE VM.


Now, Jade has been renamed to Pug

VSCode Version: 1.0.0
OS Version: Windows 10

Steps to Reproduce:

Open any pug file without syntax highlighting

Unfortunately, Jade has been renamed to Pug (ref: https://github.com/pugjs/pug/issues/2184).
We should change jade to pug on all documents, extensions and supports...
Do you have any plans?

P.S. I left a solution regarding syntax highlighting on this issue for all vscode and pug user.
Add your User settings (Command Palette -> Preferences: Open User Settings -> edit settings.json) such as:
"files.associations": {
  "*.pug": "jade"
}

@gregvanl can you update the doc accordingly.
@aeschli I suggest we support both the .pug and .jade file associations.

Definitely keep supporting the now-legacy .jade associations, there is a lot of code floating around still including the old jade.

added the '.pug' file association
once the new name is established and e.g. the pug-lang.com website is up and ready, we can also rename the extension, the label and the language id.

Um, so what about do the same here?
https://github.com/Microsoft/vscode/blob/2f76c44632b0d47ba97f66fbc158c763628e30b3/extensions/jade/syntaxes/Jade.json#L5
Change it to "name": "Pug" or something

Also renamed extension and label. Kept languageID for backward compatibility. See #18219


Unable to access server

I/flutter (30573): --- Package Error ---
I/flutter (30573): Unable to access server. 😑
I/flutter (30573): --- End Package Error ---
Am I having this error cause I don't have remote server?

Hi @Abhis2004, The package has been updated. And the test server will be only up from tomorrow. And also the test server will have a mailing limit of 30 / per day. So to setup a production server, Kindly check this link
https://saran-surya.github.io/email-auth-node/ : This will guide you through the detailed steps of setting up a production server.

I/flutter (30573): --- Package Error ---
I/flutter (30573): Unable to access server. 😑
I/flutter (30573): --- End Package Error ---
Am I having this error cause I don't have remote server?

The Error is because the test server is not available. It will be working from tomorrow.

Thanks for the update
On Tue, Aug 31, 2021, 21:58 SARAN SURYA RAVICHANDRAN <
@.***> wrote:

Hi @Abhis2004 https://github.com/Abhis2004, The package has been
updated. And the test server will be only up from tomorrow. And also the
test server will have a mailing limit of 30 / per day. So to setup a
production server, Kindly check this link
https://saran-surya.github.io/email-auth-node/ : This will guide you
through the detailed steps of setting up a production server.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/saran-surya/email_auth/issues/21#issuecomment-909392154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARNKRH3HB2Q7VN7DFEJONVDT7T7LBANCNFSM5DEKI5PQ
.


ngAria should check for interactive child elements before binding role=button and tabindex=0

I've seen this bug in the wild on a large web application using ngAria: ng-click tries to help accessibility by binding role="button" and tabindex="0", unless opted out. The problem is if that DIV with an ng-click wraps another interactive element such as <button> or <a>, the extra tabindex and role cause problems.

Here is a Plunker showing the wrapping interactive elements, prompted from #14665: https://plnkr.co/edit/SPxQ0X2RQvvfvAmDVTNA?p=preview
What is the expected behavior?
If we can do it fast enough, ngAria should test an ng-click target's child elements against the nodeBlacklist and return false on the first instance, leaving off tabindex="0" and role="button". The DIV with ng-click will then stay a mouse-only element to prevent degrading accessibility in the rest of that DOM subtree.
What is the motivation / use case for changing the behavior?
ngAria currently causes more problems than it solves with "fixes" like the one ng-click tried to solve. Addressing this problem would improve the utility of the library.
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
Visible in the latest version.

One problem I see is that this won't work for dynamically loaded content (templateUrl, ngInclude), but also for content that changes dynamically, like ngIf.
The other option would be to to look up in the DOM from interactive elements and then remove tabindex from them when they have been found. But this could incur a big performance penalty.

The other option would be to to look up in the DOM from interactive elements and then remove tabindex from them when they have been found.

That would also break usecase, where the tabindex/role are intended in the parent elements (for whatever reason).
--
Indeed, taking dynamic elements into account, I feel that this would be too much magic to implement - and it wouldn't be possible to cover all usecases either.
Better alternatives might be:

Document this as a known issue and let the developers explicitly prevent the addition of tabindex/role (by supplying their own).

Provide a way (e.g. via a new attribute) to opt out of ngAria for specific elements. (This has been brought up in #14602.)

Those are really great points, thanks for the feedback. I agree that going up the DOM tree from interactive elements would be too costly. It would also be tough to know which attributes were added intentionally without keeping track of everything...again, a huge cost for a click handler.
I like the idea of an attribute for opting out of ngAria on specific elements. I still think there will be a lot of ng-click abuse, but at least if we had a better hook it would be easier to do the right thing. Paired with additional documentation, that would set developers up a lot better than the current situation.


Kube-Vip Not Working on Kubernetes from 1.29 to Latest

Describe the bug
In Kubernetes versions 1.30.4 and 1.29.x, Kube-Vip fails to properly start and manage the VIP, resulting in the kubelet failing to register nodes due to a "no route to host" error when trying to communicate with the API server via the VIP. This behavior works as expected on Kubernetes version 1.28.13 but not on newer versions. The kubelet continues to attempt to connect to the VIP (<IP_ADDRESS>), even when localAPIEndpoint is configured with the real control plane node's IP.
Logs from the kubelet show repeated attempts to connect to the VIP with errors like dial tcp: no route to host, and the Kube-Vip container fails to bind the VIP because it cannot access the API server.
Steps to reproduce the behavior:
Deploy Kubernetes version 1.29.x or 1.30.4 with Kube-Vip configured for the API server VIP.
Specify localAPIEndpoint in the kubeadm configuration with the control plane node’s real IP.
Check the kubelet logs and observe that the kubelet is still trying to connect to the VIP (<IP_ADDRESS>) and not the local API endpoint.
Attempt to bring up the Kube-Vip service, which will fail to perform leader election due to API server unavailability.
Expected behavior
The kubelet should connect to the real control plane IP as defined in localAPIEndpoint when the VIP is not available. Kube-Vip should be able to perform leader election and manage the VIP without causing a deadlock between the kubelet and API server.
Logs from Kubelet
Logs showing the kubelet failing to connect to the API server via the VIP:
Sep 08 11:15:20 master0 kubelet[86403]: E0908 11:15:20.016412   86403 kubelet_node_status.go:96] "Unable to register node with API server" err="Post \"https://<IP_ADDRESS>:6443/api/v1/nodes\": dial tcp <IP_ADDRESS>:6443: connect: no route to host"
Sep 08 11:15:20 master0 kubelet[86403]: E0908 11:15:20.016423   86403 controller.go:145] "Failed to ensure lease exists, will retry" err="Get \"https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/master0\": dial tcp <IP_ADDRESS>:6443: connect: no route to host"
Sep 08 11:15:20 master0 kubelet[86403]: E0908 11:15:20.960610   86403 eviction_manager.go:282] "Eviction manager: failed to get summary stats" err="failed to get node info: node \"master0\" not found"

Logs from Kube-Vip Container (via crictl)
E0908 14:27:37.076396       1 leaderelection.go:332] error retrieving resource lock kube-system/plndr-svcs-lock: leases.coordination.k8s.io "plndr-svcs-lock" is forbidden: User "kubernetes-admin" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-system"
Environment:
OS/Distro: Ubuntu 24.04
Kubernetes Version: 1.30.4 (and 1.29.x)
Kube-vip Version: v0.8.2
Kubeadm-config.yaml:
apiVersion: kubeadm.k8s.io/v1beta3
kind: InitConfiguration
nodeRegistration:
  kubeletExtraArgs: {}
localAPIEndpoint:
  advertiseAddress: <IP_ADDRESS>
  bindPort: 6443
---

apiVersion: kubeadm.k8s.io/v1beta3
kind: ClusterConfiguration
networking:
  podSubnet: <IP_ADDRESS>/16
kubeProxyArgs: ["--ipvs-exclude-cidrs=<IP_ADDRESS>/24"] ###### cidr of node network #######
controlPlaneEndpoint: <IP_ADDRESS>:6443
apiServer:
  certSANs:
  - "kubevip-api-server"
  - "<IP_ADDRESS>"
  - "<IP_ADDRESS>"

  extraArgs:
    enable-admission-plugins: DefaultTolerationSeconds
    default-not-ready-toleration-seconds: "120"
    default-unreachable-toleration-seconds: "120"

Kube-Vip Configuration:
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  name: kube-vip
  namespace: kube-system
spec:
  containers:
  - args:
    - manager
    env:
    - name: vip_arp
      value: "true"
    - name: port
      value: "6443"
    - name: vip_nodename
      valueFrom:
        fieldRef:
          fieldPath: spec.nodeName
    - name: vip_interface
      value: eth0
    - name: vip_cidr
      value: "24"
    - name: dns_mode
      value: first
    - name: cp_enable
      value: "true"
    - name: cp_namespace
      value: kube-system
    - name: svc_enable
      value: "true"
    - name: svc_leasename
      value: plndr-svcs-lock
    - name: vip_leaderelection
      value: "true"
    - name: vip_leasename
      value: plndr-cp-lock
    - name: vip_leaseduration
      value: "5"
    - name: vip_renewdeadline
      value: "3"
    - name: vip_retryperiod
      value: "1"
    - name: address
      value: <IP_ADDRESS>
    - name: prometheus_server
      value: :2112
    image: ghcr.io/kube-vip/kube-vip:v0.8.2
    imagePullPolicy: IfNotPresent
    name: kube-vip
    resources: {}
    securityContext:
      capabilities:
        add:
        - NET_ADMIN
        - NET_RAW
    volumeMounts:
    - mountPath: /etc/kubernetes/admin.conf
      name: kubeconfig
  hostAliases:
  - hostnames:
    - kubernetes
    ip: <IP_ADDRESS>
  hostNetwork: true
  volumes:
  - hostPath:
      path: /etc/kubernetes/admin.conf
    name: kubeconfig
status: {}

Additional context
This issue only occurs in Kubernetes versions 1.29.x and above. In Kubernetes 1.28.13, the kubelet correctly uses the local API endpoint, and Kube-Vip functions as expected. The lack of a fallback to the real control plane IP when the VIP is unavailable seems to cause this circular dependency, leading to a deadlock where Kube-Vip can't function, and the kubelet can't register with the API server.
I believe it won't work on Kubernetes 1.31.0 as well.

The same problem is occurring to me as well. During the upgrade to a newer version of Kubernetes, I encountered a problem where the other masters were unable to connect to the VIP address that I defined in the configuration. When I upgraded my cluster to 1.30 , I encountered this problem for the first time

k8s 1.29 creates a seperate super-admin.conf, https://github.com/kubernetes/kubernetes/pull/121305

Can you get the kube-vip logs? I'm going to update the docs to cover all of these issues shortly.

k8s 1.29 creates a seperate super-admin.conf, kubernetes/kubernetes#121305

👆 this
also make sure to use at least 1.29.7 - because they had some issue with hostAlias in static-pods (this problem also was in some certain 1.28 and 1.30 version afaik - unfortunately I cannot find the kubernetes issues anymore where the fix was discussed and merged.
For our internal wiki-system I noted down this

Starting with Kubernetes v1.29 you have to mount the super-admin.conf instead of the admin.conf for the first master-node initialization.
From the kube-vip static-pod manifest
...
   volumeMounts:
  - mountPath: /etc/kubernetes/admin.conf
    name: kubeconfig
hostAliases:
- hostnames:
  - kubernetes
  ip: <IP_ADDRESS>
hostNetwork: true
volumes:
- hostPath:
    path: /etc/kubernetes/super-admin.conf
  name: kubeconfig
...

(warning)  This is only needed on the first node (the super-admin.conf is also only generated on the first node!) you can later change it back to the normal admin.conf after your cluster is up and running.
(warning)  Also make sure that you use the latest v1.29 available (2024-08-07 this was v1.29.7) because up to some earlier version there was an issue with the hostAliases-part and it was ignored for some reason.

also see https://github.com/kube-vip/kube-vip/issues/684

@BBQigniter @linsite Thanks! It worked!
I have a few additional questions to fully understand the implications of this change:
Why was this separation introduced?
What was the reason behind separating the super-admin.conf from the standard admin.conf? Are there specific use cases or scenarios that required this change?
Can you clarify the differences in privileges between super-admin.conf and admin.conf? Is admin.conf on the rest of the master nodes configured with fewer permissions than super-admin.conf on the first master?
Impact on Cluster Management:
Could the use of super-admin.conf only on the first master node affect how privileges are escalated across the control plane? Is there any risk of limited functionality or inconsistency in cluster management if the other masters use admin.conf instead of super-admin.conf?
In addition I opened a ticket about kubevip not working on an openstack environments (same versions).
Can you maybe take a look?
https://github.com/kube-vip/kube-vip/issues/931

@devopsInterviews as far as I understood the change to use the super-admin.conf for the initialization is a security enhancement. Using the super-admin.conf gives you now some high-privileged permissions. Here is a nice blog describing some things https://rodrigtech.com/kubernetes-1-29-0-security-enhancements/
hmm, and about the mentioned ticket - no clue what that could be. just turned up my 3-node lab-cluster (v1.29.8, all nodes are control-plane, etcd and worker-nodes) and have no issues. But my setup is a little bit different - I use the kube-vip static-pods only for control-plane nodes and a daemonset kube-vip workload for service-loadbalancing giving me more control where the service VIPs should be assigned via my kube-vip-watcher daemon.

This appears to be another duplicate of #684


condition request, glucose starvation and recovery

I'm using
"glucose starvation and timing" which exists. No def. Is this a typo?
v

I don't see "glucose starvation" in PECO at all, with or without "and timing". There's "grouping starvation and timing" (PECO:0000239), which looks like it ought to be flagged as a grouping term not for direct use (I can fix that in a minute).
(holler if you need the new condition before Antonia is back up to scratch, and I'll add it)

may as well add it (glucose starvation and recovery) or this session will hang around

OK, I'm going to do some FYPO tomorrow, so I'll do this then too.

added
[Term]
id: PECO:0000310
name: glucose starvation and recovery
def: "Cells are first grown in minimal medium lacking glucose and are then allowed to recover in rich medium." [PomBase:mah]
is_a: PECO:0000094 ! grouping sequential growth conditions


Cube slice iterator and merger

As an IMPROVER developer I want repeated patterns of slicing, merging, and dimensions checking to be centralised so that my code is more reliable and maintainable.
Acceptance criteria:

Ensure there is a utility that: slices a cube (over given coordinate(s)), applies an operation on each slice, and then recombines the slices to form a cube with the dimensions of the output cube identical to the original.
The utility should build upon existing code where possible.
Ensure there are associated unit tests, and that they capture the existing use cases (for an example, see description).
Update the existing code to use the generic functionality wherever possible (if this is not possible, note on the ticket)
If appropriate, comment on if this functionality could be ported to Iris.

Ideas from User Story splitting meeting:
The first 3 of the acceptance criteria might be done in one PR, with the updating of the existing use cases being a second PR.
Description:
An example use case of slicing a cube, applying an operation, then recombining it (requiring the original dimensions) is: https://github.com/metoppv/improver/blob/05ebd97/bin/improver-wind-downscaling#L120-L136

Not sure we have a generic use case for this functionality any more or that there is a lot to gain for a generalised utility.


01.02.01

As a claimant, I want to list all my expense claims, showing for each claim: the starting date of travel, the destination(s) of travel, the claim status, tags, and total currency amounts.

Previously done

As a claimant, I want to list all my expense claims, showing for each claim: the starting date of travel, the destination(s) of travel, the claim status, tags, and total currency amounts.

Basic Flow:

Claimant makes/edits a claim
Claimant presses on add Travel destination button
Claimant enters travel destination and description
Claimant presses Add button

Exceptions:

Duplicate entry 2. Blank Travel Destination 3. Blank Description

Not quite done. Needs more tests.

Hey James. I Was looking through this one.. I think you have this one mixed up.
US01.02.01
As a claimant, I want an expense claim to record one or more destinations of travel and an associated reason for travel to each destination.

I think you used this one
US02.01.01
As a claimant, I want to list all my expense claims, showing for each claim: the starting date of travel, the destination(s) of travel, the claim status, tags, and total currency amounts.

oh yeah, nice catch will fix

Finished test

Done. All JUnit tests pass


Update AUTHORS with recent contributors

No issue associated with this PR.

@wesleimp - this could be reviewed too when you have time. :smile:

Thank you, @wesleimp !


When using UI Templates, prompt to run npm install

Is your feature request related to a problem? Please describe.
When running the nhost and selecting Y to install a UI template, automatically run npm install
Describe the solution you'd like
This is minor but prompting or automatically running npm install for the web folder.

We had carefully taken a decision to not run any third-party commands (like NPM) on behalf of users from our CLI. Both because of security, and to avoid altering/modifying user's app's configuration unintentionally.
I'm closing this issue.


removed legacy xu dtsi files

removes XU series dtsi files from tree

please fold the 4 commits into a single one


owncloud: Add version <IP_ADDRESS>40

Created an app manifest for the ownCloud desktop client. Since the clients are still very similar, I used the manifest of Nextcloud as blueprint.
Closes #13229

[x] I have read the Contributing Guide.

/verify


2 add codecov integration

Codecov Report

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

@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   86.11%
=========================================
  Files             ?       11
  Lines             ?      144
  Branches          ?        0
=========================================
  Hits              ?      124
  Misses            ?       20
  Partials          ?        0

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 1cd6bf2...f2f233d. Read the comment docs.


[FEATURE] Add a TablePrompt

Feature description
A TablePrompt should allow the user to input values into a table.

Added with #11


Dash in URL breaks hyperlink parsing

Gitea version (or commit ref): 3b89ee5
Example: https://try.gitea.io/svarlamov/foobar-issues-example/issues/1

Description
When posting an issue by cut-n-pasting a URL like https://example.com/something/my-link the URL parsing works and I get a pretty hyperlink after posting. However, this url https://sample.example.com/:i:/p/foobar/helloworld-foo?abc=123 breaks. Ie., the link is only the https://sample.example.com/:i:/p/foobar/helloworld part, whereas -foo?abc=123 just looks like normal text and when I click on the part that got recognized as a link, it directs me without the -foo?abc=123 part -- which is not where I wanted to go!
I have this problem quite often when posting links to screenshots in Gitea (because the image upload is very painful, ref #3032)... But even now that I'm posting URLs, it's still not happy... 😢
Screenshots

Since #3354 merged, I'll close this one. Please feel free to reopen it.


Modify Step to accept optional id property

We currently have two "Step-ish" types in the front end: Step and  TransferStep.
TransferStep is like Stepbut adds an optional id property we use in Xpollinate and Lifi. In both Apps we need it to store and identify Routes.
We could simplify the frontend and reduce confusion by adding an optional id to Step and removing TransferStep.

Integrated in #3


Parameterize Scylla Repo Options

This will make sure that future upgrades can be done without making significant changes to this module. Now each Scylla Cluster could maintain its separate version; hence would reduce upgrade complexity.

do NOT mege


multiple selection not work in swift

Hi, thanks for your work.
I am using Swift 4, and try to use multiple selection.
However, [self.delegate respondsToSelector:@selector(czpickerView:didConfirmWithItemsAtRows:)] is always false and cannot call function "func czpickerView(pickerView: CZPickerView!, didConfirmWithItemsAtRows rows: [AnyObject]!)"
Do you know why?
Thanks.

Can you post a sample code here? I used this control yesterday in swift project and it turned out fine.

Thanks for your message.
I have noticed that
func czpickerView(pickerView: CZPickerView!, didConfirmWithItemsAtRows rows: [AnyObject]!) {
}
does not work, but
func czpickerView(_ pickerView: CZPickerView!, didConfirmWithItemsAtRows rows: [Any]!) {
}
works.
Anyway thank you for your support.

@ryamashita then looks like it's method signature doesn't match, this library is written in Obj-C so have to be careful :D


Possible incompatibility with iperf 3.x (opensuse)

I 've installed mininet and all dependecies in opensuse manually by following the install script. After running mininet with no arguments and options, I had tested ping and connectivity  and h1 can ping h2 and vise versa, but when trying to test the performance , "iperf h1 h2" and got this response repeatedly : "Waiting for iperf to start up..." and nothing happens until pressing CNTR+C.
I have used diffrent switches like ovsk,ivs,ovs and no diffrence.
I have tested iperf manualy by opening xterm of two hosts and checking iperf by using one in server mode and another in client mode and it works like a charm!
Does anybody know what's wrong and why iperf doesn't work in Mininet shell ?

So, this is going a bit outside the average use case since you're using it on a platform that isn't Ubuntu or Fedora, but here are some questions for you to see if you can debug it a bit:

Are you sure that you've installed telnet as well as iperf, as is done in the install script?

Since you're using OpenSuse, do telnet and iperf produce the same output that they do on Ubuntu?

When you run Mininet with mn -v debug, what are the results you are seeing?

Incidentally, you are welcome to make a pull request to add OpenSuse support to install.sh.

Telnet and iperf are installed before and worked correctly independently. Both of the outputs are similar to each other.
Here is output of mn -v debug :
*** Setting resource limits
*** Creating network
*** Adding controller
*** c0 : ('stty -echo',)
mnexec -p stty -echo
*** c0 : ('set +m',)
*** c0 : ('echo A | telnet -e A <IP_ADDRESS> 6633',)
Telnet escape character is 'A'.
Trying <IP_ADDRESS>...
telnet: Unable to connect to remote host: Connection refused
*** Adding hosts:
*** h1 : ('stty -echo',)
mnexec -p stty -echo
*** h1 : ('set +m',)
h1 *** h2 : ('stty -echo',)
mnexec -p stty -echo
*** h2 : ('set +m',)
h2
*** Adding switches:
*** s1 : ('stty -echo',)
stty -echo
*** s1 : ('set +m',)
added intf lo (0) to node s1
*** s1 : ('ifconfig', 'lo', 'up')
s1
*** Adding links:
added intf h1-eth0 (0) to node h1
moving h1-eth0 into namespace for h1
*** h1 : ('ifconfig', 'h1-eth0', 'up')
added intf s1-eth1 (1) to node s1
*** s1 : ('ifconfig', 's1-eth1', 'up')
(h1, s1)
added intf h2-eth0 (0) to node h2
moving h2-eth0 into namespace for h2
*** h2 : ('ifconfig', 'h2-eth0', 'up')
added intf s1-eth2 (2) to node s1
*** s1 : ('ifconfig', 's1-eth2', 'up')
(h2, s1)
*** Configuring hosts
h1 *** h1 : ('ifconfig', 'h1-eth0', '<IP_ADDRESS>/8', 'up')
*** h1 : ('ifconfig lo up',)
h2 *** h2 : ('ifconfig', 'h2-eth0', '<IP_ADDRESS>/8', 'up')
*** h2 : ('ifconfig lo up',)
*** Starting controller
c0 *** c0 : ('controller -v ptcp:6633 1>/tmp/c0.log 2>/tmp/c0.log &',)
[1] 2726
*** Starting 1 switches
s1 *** s1 : ('ovs-vsctl del-br', <OVSSwitch s1: lo:<IP_ADDRESS>,s1-eth1:None,s1-eth2:None pid=2616> )
ovs-vsctl: no bridge named s1
*** s1 : ('ovs-vsctl -- get Bridge', <OVSSwitch s1: lo:<IP_ADDRESS>,s1-eth1:None,s1-eth2:None pid=2616> , 'Controller')
ovs-vsctl: no row "s1" in table Bridge
*** s1 : ('ovs-vsctl add-br s1 -- set Bridge s1 other_config:datapath-id=0000000000000001 -- set-fail-mode s1 secure -- add-port s1 s1-eth1 -- set Interface s1-eth1 ofport_request=1  -- add-port s1 s1-eth2 -- set Interface s1-eth2 ofport_request=2 -- set-controller s1 tcp:<IP_ADDRESS>:6633 ptcp:6634 -- set bridge s1 other-config:disable-in-band=true ',)

Opensuse :*** Setting resource limits
*** Creating network
*** Adding controller
*** c0 : ('stty -echo',)
mnexec -p stty -echo
*** c0 : ('set +m',)
*** c0 : ('echo A | telnet -e A <IP_ADDRESS> 6633',)
Telnet escape character is 'A'.
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection refused
*** Adding hosts:
*** h1 : ('stty -echo',)
mnexec -p stty -echo
*** h1 : ('set +m',)
h1 *** h2 : ('stty -echo',)
mnexec -p stty -echo
*** h2 : ('set +m',)
h2
*** Adding switches:
*** s1 : ('stty -echo',)
stty -echo
*** s1 : ('set +m',)
added intf lo (0) to node s1
*** s1 : ('ifconfig', 'lo', 'up')
s1
*** Adding links:
*** h1 : ('ip link add name h1-eth0 address d2:14:7c:ff:f9:f8 type veth peer name s1-eth1 address 96:62:a8:a1:19:9d netns 6814',)
added intf h1-eth0 (0) to node h1
moving h1-eth0 into namespace for h1
*** h1 : ('ifconfig', 'h1-eth0', 'up')
added intf s1-eth1 (1) to node s1
*** s1 : ('ifconfig', 's1-eth1', 'up')
(h1, s1) *** h2 : ('ip link add name h2-eth0 address da:f8:80:1b:90:aa type veth peer name s1-eth2 address 82:33:90:b6:a9:af netns 6814',)
added intf h2-eth0 (0) to node h2
moving h2-eth0 into namespace for h2
*** h2 : ('ifconfig', 'h2-eth0', 'up')
added intf s1-eth2 (2) to node s1
*** s1 : ('ifconfig', 's1-eth2', 'up')
(h2, s1)
*** Configuring hosts
h1 *** h1 : ('ifconfig', 'h1-eth0', '<IP_ADDRESS>/8', 'up')
*** h1 : ('ifconfig lo up',)
h2 *** h2 : ('ifconfig', 'h2-eth0', '<IP_ADDRESS>/8', 'up')
*** h2 : ('ifconfig lo up',)
*** Starting controller
c0 *** c0 : ('controller -v ptcp:6633 1>/tmp/c0.log 2>/tmp/c0.log &',)
*** Starting 1 switches
s1 *** s1 : ('ovs-vsctl --if-exists del-br s1 -- add-br s1 -- set Bridge s1 other_config:datapath-id=0000000000000001 -- set-fail-mode s1 secure -- add-port s1 s1-eth1 -- set Interface s1-eth1 ofport_request=1  -- add-port s1 s1-eth2 -- set Interface s1-eth2 ofport_request=2 -- set-controller s1 tcp:<IP_ADDRESS>:6633 ptcp:6634 -- set bridge s1 other-config:disable-in-band=true ',)
*** s1 : ('ovs-vsctl -- get Bridge', <OVSSwitch s1: lo:<IP_ADDRESS>,s1-eth1:None,s1-eth2:None pid=6814> , 'Controller')
[20ba4b80-4f50-411d-be11-8ea3077b0d6f, 5d6dfed8-fd7c-43a0-9ece-e2e0932b12c8]
*** s1 : ('ovs-vsctl', '-- set Controller 20ba4b80-4f50-411d-be11-8ea3077b0d6f max_backoff=1000', '-- set Controller 5d6dfed8-fd7c-43a0-9ece-e2e0932b12c8 max_backoff=1000')

I found the problem. It's because of iperf version.
in opensuse it's 3.0.10 after installing version 2.0.5 it works again in mininet shell.
I had installed V3. it makes iperf3 executable but after I had linked an iperf link with iperf3 it didn't worked yet.
any solution or workaround for version 3?

I don't have a solution offhand - if you come up with one, feel free to submit a pull request.
Also your output doesn't include the results from running iperf, e.g. sudo mn -v debug --test iperf

I found that there are some differences with iperf2 and iperf3.
The first is in the listening port for server. Iperf2 use port 5001 and iperf3 use port 5201.
The second is the output difference to parse. Iperf2 calculate the bandwidth only once without any argument, but iperf3 calculate it about ten times, print them and in the end it outputs the average.
In the "net.py" file port is mentioned statically in iperf function : 'sh -c "echo A | telnet -e A %s 5001"'. I don't think it's necessary and it is the cause of problem. I 'm not a master in python and could not manipulate "net.py" so well to handle iperf3 and iperf2 outputs for printing them in mininet shell.
And dear lantz, about your pull request for opensuse , it was somehow difficult, because of some outdated dependencies that are bind to old libraries that are not present anymore in newest opensuse repositories (opensuse 13.1 , 13.2,...) like old swig and bison (swig 1.3 ,bison 2.5) or some errors for compilations of old codes so need to add some flags in compilations, or do adding some "include...." in the codes and so on.
It took me about 7-8 hours to installing mininet and all dependecies but then it worked like a charm , without any problem, with the newest libraries and builds.
I can interpret the install script so well but don't have a good skill in writing scripts to do all that do manually to make the script compatible with opensuse .
But I can present you my virtual machine or anybody who wants mininet in opensuse. (It's about 3.6 GB, a bit large, because of desktop managers like KDE and GNOME).

Hmm.... well if you want to tackle updating for an OpenSuse install, that would be helpful.
Otherwise, maybe someone else will be able to figure it out.
I have slightly modified iperf() in b2fe0778dc21ccc772292e5337f388446c4ce8f4 to explicitly supply a port argument. However, if the output format is different for iperf 3, then additional modifications may be required.


6 tests failed

Hello, I have completed full installation,  but 6 tests still aren't passing. Is it critical? Will I be able to functionally work with EOS, interact with blockchain and deploy smart contracts? What can I do to fix these errors?
The following tests FAILED: 	 30 - nodeos_run_test (Failed) 	 32 - distributed-transactions-test (Failed) 	 33 - restart-scenarios-test-resync (Failed) 	 34 - restart-scenarios-test-hard_replay (Failed) 	 35 - restart-scenarios-test-none (Failed) 	 36 - validate_dirty_db_test (Failed) Errors while running CTest make: *** [test] Error 8
OS: macOS High Sierra V 10.13.5

@JustinZal , have you solved this? Just update to 1.1.3, and you should be fine.

Yes, I have resolved it. Thanks for the answer


Add support for MT inheritance models

Inherited maternally
Transferred to all offspring
Paternal MT DNA is not propagated to offspring
All affected should carry variation

Ok so it is like AD, right?

Yes, but the variant can only be inherited on the maternal side.
Skickat från min iPhone

8 nov. 2015 kl. 22:47 skrev Måns Magnusson<EMAIL_ADDRESS>Ok so it is like AD, right?
—
Reply to this email directly or view it on GitHub.

Mitochondria-linked Dominant (MD): Lika AD except

Only on MT
Mother affected and “1"
All offspring is affected and “1”

Mitochondria-linked (M):

Only on MT
Offspring can be either “0” or “1” i.e. reduced penetrance due to the bottleneck between generations (i.e. Mother to child transmission of MT subpopulation) or novel mutation in offspring
Mother unaffected and “0” or affected and “1"
Affected offspring is “1”
Unaffected offspring is “0"


Adding Embarrassingly Parallel Algorithms in NetworkX to nx-parallel

Embarrassingly parallel algorithms
Embarrassingly parallel algorithms are those that can be easily and efficiently divided into smaller, independent tasks that can be executed concurrently across multiple processing units, such as CPUs, GPUs, or nodes, without requiring significant communication or synchronisation between them. This type of parallelism is often referred to as “embarrassingly parallel” because it’s so straightforward and easy to implement. Refer this to see how to implement embarrassingly parallel algorithms using joblib.
Characteristics of Embarrassingly Parallel Problems(Algorithms):

Independent tasks: Each task can be executed independently, without relying on the output of other tasks.
No communication: Tasks do not require frequent or significant communication with each other.
No data dependencies: Tasks do not rely on shared data or intermediate results from other tasks.
Easy to divide: The problem can be easily split into smaller, parallelizable tasks.

Adding a new algorithm to nx-parallel
Step 1 : Find a NetworkX algorithm that is embarrassingly parallel

You can find such an algorithm from the NetworkX's references - https://networkx.org/documentation/latest/reference/index.html
Make sure there is a _dispatchable decorator(in the networkx's codebase) on the algorithm you have selected to parallelise.

Step 2 : Complete the checklist in Contributor's guide
This checklist in Contributor's guide for adding a new algorithm to the package.
Some references:
It would be better to look at currently existing algorithms than previous PRs that add parallel algorithms(like https://github.com/networkx/nx-parallel/pull/60 , https://github.com/networkx/nx-parallel/pull/37 , https://github.com/networkx/nx-parallel/pull/45 and many more) because we have changed a few things.
Feel free to ask questions if you get stuck anywhere or if anything is not clear or if you want something to be explained in a bit more detail here.
Thank you :)

Hey , i would like to work on this issue

Hi @RohitP2005 , let us know if you have any questions :)
Also, writing parallel versions of functions that return a non-generator(i.e. functions that return and not yield) would be easier to begin with.

Thank you @Schefflera-Arboricola  , I will reach out to you if i need anything

Shall i add this algorithm to the nx_parallel

@Schefflera-Arboricola i have made a pull request traversal
algorithm added

hey @Schefflera-Arboricola  can u clarify that am i supposed to add a alogrithmfrom in networkx that is embarissingly parallel to the nxparallel algorithms
If yes i also need a suggestion of such algorithm


OCPBUGS-29020: reduce external-dns route53 call volume

Ideally, we would not need to backport this.  However, release-4.15 across the org currently use the HO built from the release-4.15 branch and it is not trivial to change this.  release-4.15 jobs are still creating route53 throttling situation so let's backport this fix.
Contains https://github.com/openshift/hypershift/pull/3394 and follow up fix https://github.com/openshift/hypershift/pull/3408

/jira refresh

/test e2e-aws

/test e2e-aws

/lgtm

The console pod is crashlooping with:

F0206 04:36:25.448889       1 authoptions.go:286] Error initializing authenticator: failed to construct OAuth endpoint cache: failed to setup an async cache - caching func returned error: request to OAuth issuer endpoint https://oauth-example-l74kt.service.ci.hypershift.devcluster.openshift.com:443/oauth/token failed: Head "https://oauth-example-l74kt.service.ci.hypershift.devcluster.openshift.com:443": dial tcp: lookup oauth-example-l74kt.service.ci.hypershift.devcluster.openshift.com on <IP_ADDRESS>:53: no such host

@sjenning I see why the above is failing. In the case of a private cluster, we create a Service of type ExternalName so oauth is accessible with the external name but points to the vpce:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_hypershift/3521/pull-ci-openshift-hypershift-release-4.15-e2e-aws/1754707041789677568/artifacts/e2e-aws/run-e2e/artifacts/TestCreateClusterPrivate/namespaces/e2e-clusters-slsvs-example-l74kt/core/services/oauth-private-external.yaml
You are now filtering out this type of service:  https://github.com/openshift/hypershift/pull/3521/files#diff-ab3302b00ae0805370a599255a6ccd796179116937ed66a7d32932950594924fR427
I wonder why we didn't catch this before 🤔

Removing the filter and giving it a try.  If it does work, will forward-port to main to keep everything together.

/test e2e-aws
flake on CCO in leader elect code with concurrent map read/write

/test e2e-kubevirt-aws-ovn

/lgtm


[Registry] Add GenerateID func for all entity interface.

Description
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

@Jougan-0 if you're able to fix this so that we can move forward, please do.

Re-running for failed lint checks...

Re-running for failed lint checks...

Yes.


Add a note about comparison to Tekton to the docs

What would you like to be added:
Comparison page should mention how we differ from Tekton. This was one of the questions raised during the webinar.
Why is this needed:

the comparison component of the site was overhauled during docathon week...
@alenkacz is there a reason to compare to tekton specifically?   It seems like a different domain and more comparable to dispatch.   Closing for now... please reopen if desired.


Fixed a typo in the background_fetch plugin section

What it says on the box, fixes a typo

[approve ci]

Cherry-picked to 8.0.x


Add Project to the repository

There is no existing project in the repository.
Create new Branch and Create the PR with the Project.

Please Add a directory and then place your Application Code there.

Please assign me this issue.


how to test influxdb-relay working or not on multinode…?

how to test influxdb-relay working or not on multinode…?
server1: I install influxdb and influxdb-relay and both running
server2: I install influxdb and influxdb-relay and both running
so what next … I want exact steps to test influxdb-relay working or not

server 1:- influxdb-realy.conf file
-- toml --
InfluxDB && Prometheus
[[http]]
name = "example-http-influxdb"
bind-addr = "<IP_ADDRESS>:9096"
Timeout for /health route
After this time, the host may be considered down
health-timeout-ms = 10000
Request limiting (Applied to all backend)
rate-limit = 5
burst-limit = 10
Ping response code, default is 204
default-ping-response = 200
Enable HTTPS requests.
ssl-combined-pem = "/etc/ssl/certs/localhost.crt"
[[http.output]]
name = "local-influxdb01"
location = "http://<IP_ADDRESS>:8086/"
endpoints = {write="/write", write_prom="/api/v1/prom/write", ping="/ping", query="/query"}
timeout = "10s"
[[http.output]]
name = "local-influxdb02"
location = "http://<IP_ADDRESS>:8086/"
endpoints = {write="/write", write_prom="/api/v1/prom/write", ping="/ping", query="/query"}
timeout = "10s"
[[udp]]
name = "example-udp"
bind-addr = "<IP_ADDRESS>:9096"
read-buffer = 0 # default
Precision to use for timestamps
precision = "n" # Can be n, u, ms, s, m, h
[[udp.output]]
name = "local-influxdb01"
location = "<IP_ADDRESS>:8089"
mtu = 512
[[udp.output]]
name = "local-influxdb02"
location = "<IP_ADDRESS>:7089"
mtu = 1024
EOF

server2:- influxdb-relay.conf file
influxDB && Prometheus
[[http]]
name = "example-http-influxdb"
bind-addr = "<IP_ADDRESS>:9096"
Timeout for /health route
After this time, the host may be considered down
health-timeout-ms = 10000
Request limiting (Applied to all backend)
rate-limit = 5
burst-limit = 10
Ping response code, default is 204
default-ping-response = 200
Enable HTTPS requests.
ssl-combined-pem = "/etc/ssl/certs/localhost.crt"
[[http.output]]
name = "local-influxdb01"
location = "http://<IP_ADDRESS>:8086/"
endpoints = {write="/write", write_prom="/api/v1/prom/write", ping="/ping", query="/query"}
timeout = "10s"
[[http.output]]
name = "local-influxdb02"
location = "http://<IP_ADDRESS>:8086/"
endpoints = {write="/write", write_prom="/api/v1/prom/write", ping="/ping", query="/query"}
timeout = "10s"
[[udp]]
name = "example-udp"
bind-addr = "<IP_ADDRESS>:9096"
read-buffer = 0 # default
Precision to use for timestamps
precision = "n" # Can be n, u, ms, s, m, h
[[udp.output]]
name = "local-influxdb01"
location = "<IP_ADDRESS>:8089"
mtu = 512
[[udp.output]]
name = "local-influxdb02"
location = "<IP_ADDRESS>:7089"
mtu = 1024
EOF

I to also want to know how the relay is writing the data and we are mentioning the connection between the instance and relay and how do we mention the writing data from Prometheus to relay

I to also want to know how the relay is writing the data and we are mentioning the connection between the instance and relay and how do we mention the writing data from Prometheus to relay


Remove unintended SpiceDB connection test from constructor

PR Template:
Describe your changes

I had added a minimal version of #109 locally to help repro #112 and seemingly accidentally pushed it. This PR is intended to revert it.

Ticket reference (if applicable)
Fixes #
Checklist

[ ] Are the agreed upon acceptance criteria fulfilled?

[ ] Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

[ ] Do your changes have passing automated tests and sufficient observability?

[ ] Are the work steps you introduced repeatable by others, either through automation or documentation?

[ ] If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
[ ] An SOP (Standard Operating Procedure) was created

[ ] The Changes were automatically built, tested, and  - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

[ ] Are the agreed upon coding/architectural practices applied?

[ ] Are security needs fullfilled? (e.g. no internal URL)

[ ] Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

[ ] For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

/lgtm


SMS notifications client, some refactoring that affects email client

Implementing the SMS notification client, and some refactoring
Description

Implemented SMS client
Moved related code into Notifications/ folder and namespace
Shared telemetry class to centralize the config
Made implementation classes internal
Made injection of TelemetryClient optional as it may not exist in the container if no instrumentation key or connection string is configured (which might be the case when running locally)
Made exception constructors internal and to string building there based on HTTP info
Additional test and edge case for RequestedSendTime. Removed AddMinutes(1) from the email notification timestamp as the Notifications API accounts for that
Added ILogger-logging for errors

[x] Implement SMS support in localtest - https://github.com/Altinn/app-localtest/pull/94

Related Issue(s)

#493

Verification

[ ] Your code builds clean without any errors or warnings
[ ] Manual testing done (required)
[ ] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Documentation

[x] https://github.com/Altinn/altinn-studio-docs/pull/1498

@ivarne I've changed things now so they follow the standard conventions like discussed yesterday


Bug: Sprint issues are not filtered out

Expected Behavior
When I select board and and an active sprint I just want to see issues for this active sprint and all other issues are filtered out.
Actual Behavior
Issues from older sprints and also closed issues are shown.
Steps to Reproduce the Problem

Select board
Select sprint
Look at the issues

Specifications

Chronos-timetracker version: 2.6.2
OS: macOS HighSierra 10.13.2

@Kondamon  check v2.6.4 please

@VladimirPal it's working thank you for the quick fix!


Remove ConstExpr in favor of a limited Expr

This regresses default-features all-in build times by about 0.1-0.3s on my laptop from ~7.4-7.6s (current master) to ~7.76s (mystor/constexpr - the new times seem more consistent?). In the past when I measured the regression it seemed more significant. I think this added overhead is mostly due to our now-correct precedence handling when parsing binary constant expressions. I figure this isn't too big of a build time regression but would like @dtolnay's opinion.
The advantage of this patch set is that it simplifies the interface to consistently use the same expression everywhere, and enables code re-use for the expression parser, by eliminating the chance that the Expr and ConstExpr parsers get out of sync.

That seems fine. The Expr / ConstExpr split is not worth it to save 0.1-0.3 seconds.


Pattern for data binding

Not an issue, but just wanted to post this to help with others using data binding. If it proves to be useful, it could also be added as another submodule.
The general contents are here, but the idea is that with data binding, we can get the view ids from the layout id, and we no longer need to make a custom ViewHolder. This also avoids the need for non generic adapters.
ViewHolders however are useful for cases like event hooks, where we need to distinguish between the types. This binding pattern uses a companion object to keep track of that layout res instead.
Usage example:
class PlaceholderVhBinding(@StringRes override val data: Int) :
    BindingItem<ViewPlaceholderBinding>(data),
    BindingLayout<ViewPlaceholderBinding> by Companion {

    override fun ViewPlaceholderBinding.bindView(holder: ViewHolder, payloads: MutableList<Any>) {
        placeholderText.setText(data)
    }

    override fun ViewPlaceholderBinding.unbindView(holder: ViewHolder) {
        placeholderText.text = null
    }

    companion object : BindingLayout<ViewPlaceholderBinding> {

        override val layoutRes: Int
            get() = R.layout.view_placeholder

    }
}

Binding and unbinding signatures extend the data binding, so view access is easy, and the model can be accessed from data. So long as it is a data class, equality and hash are also defined, so diffs work out of the box.
Id type defaults to layout res, though that is a person design decision.

@AllanWang have you had a look at ViewBinding as it may make this obsolete too?

This pattern is actually pretty generic, so long as there is a way to get the binding from the layout res. I probably won't be looking at ViewBinding until it makes it to AS Beta, but there is a chance it will still work. If all they expose is the inflate method, I would be pretty disappointed

This can probably be closed, as it's really here in case people search for it and want information.
I'm testing integration with ViewBinding here:
https://github.com/AllanWang/KAU/blob/viewbinding/fastadapter-viewbinding/src/main/kotlin/ca/allanwang/fastadapter/viewbinding/BindingItem.kt
Essentially, it seems like we can get the view information from the binding instead of a custom viewholder, and if we implement equality through the use of data classes for models, we get diffs out of the box too. All that is left is to use a single IItem model. It is annoying that you have to provide the binding yourself, whereas with data binding there is a generic loader that can take in the layoutRes you provide.
In this case, the layoutRes is a bit redundant, but is still used to validate event hooks.

Perhaps you would be interested in doing a sample activity in the sample app to showcase this?
if we somehow can do that more generic or so and pack it, then we could also set-up a new additional extension :)

I'm in the process of testing now. It could be even more generic by supporting any class with a getView function, but I think at a certain point it defeats the purpose

Please have a look at the new data binding module :) perhaps this suites all the needs


Fix and cleanup rotationMatrixToEulerAngle

I am sorry I made mistakes during testing and thought that the Y rotation needed "compensation". In fact, all xyz rotations returned by the routine are correct and accurate. The YZX routine is clean and fine alone without further modification. Technically speaking the result is identical to the so-called full routine (matrix => quaternion => euler). I think this rotation matrix => euler is actually an elegant solution.

In fact if you don't want to return the rotation matrix, I think it's fine to just return pitch/yaw/roll. Technically speaking it should be possible to reconstruct the matrix/quaternion with values computed using this method, if the user really needs it.

I'll copy&paste those changes directly to my code as PR is in conflict with my latest merge, so don't worry about rejection.


Indentation in raw string literals

Hi @dominikh, big thank you for your work! Not sure if this is OK to ask questions here, but I didn't find anything about that in README. My question is if indentation of the raw string literal in snippets like this
func f() {
  s := `my
    long
    string
`
}

can be controlled? The problem is that currently its using spaces which is somewhat inconsistent with the rest of the tab based indents in the Go source.

go-mode isn't doing any kind of indentation in raw strings. Indentation in raw strings is significant as it becomes part of the actual value, and whether tabs, spaces or neither should be used depends on what you actually need in the string. go-mode will not touch the indentation in raw strings at all, and new lines will start in the first column.

Reasonable, thanks!


Add annotation for return value of Rule::getOptions()

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
225

test


README Examples respond http404

You may need to update the README Examples and/or point to the documentation itselft and/or add a visible redirect from the versionless routes to the v1 ones.

Thanks @borisschapira!  I updated the README for v1!


Add score for variable stars

gatspy computes internally a score (model.score(period)). Not sure how this can be translated into a chi^2/dof.
Not that we are using
https://github.com/astroML/gatspy/blob/a8f94082a3f27dfe9cb58165707b883bf28d9223/gatspy/periodic/lomb_scargle_multiband.py#L205-L209
def _score(self, periods):
    # Total score is the sum of powers weighted by chi2-normalization
    powers = np.array([model.score(periods) for model in self.models_])
    chi2_0 = np.array([np.sum(model.yw_ ** 2) for model in self.models_])
    return np.dot(chi2_0 / chi2_0.sum(), powers)

so we can easily derive the chi2 using np.sum(model.yw_ ** 2). It remains the number of ddof to determine (nterm_base + nterm_band + period?)

#137


bug(mdc-icon-button): adding border to mat-icon-button causes icon to become misaligned

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When using the basic implementation of mat-icon-button the icon inside the button is properly aligned as expected within the button. It is centered both vertically and horizontally.
When a border is added to the mat-icon-button it shifts the icon down and to the right by the size of the border.
For instance a CSS border like so:
border: 1px solid black
would cause the icon to move down by 1px and right 1px, this causes the icon to now be misaligned.
This is almost unnoticeable on small borders, but is increasingly obvious as the border gets bigger.
Reproduction
StackBlitz link: https://stackblitz.com/edit/components-issue-8mcihf?file=src%2Fapp%2Fexample-component.html
You should be able to see once loaded that the icons are not centered within their border/parent element(button).
Expected Behavior
Expect the icon within a mat-icon-button to be centered with or without border, and no matter what size the border is.
Actual Behavior
The border width affects the position of the icon within the mat-icon-button causing it to not be centered.
Environment

Angular: v16.2.0
CDK/Material: v16.2.0

Hi, changing the border of the icon button like this is not something the library supports as it is outside of the material design spec


maven-cache

Noticed we're not caching maven dependencies, also, according to https://docs.travis-ci.com/user/caching/, npm should be cached this way instead of node_modules

will we need to clear the existing cache after this is merged in?

@britneywright don't believe so, we can validate after with the next pr since we can check their logs and if they needed maven dependencies when using masters cache

nuking the cache is a pain though so we should wait to see, remembering that builds took upwards of 40 minutes when we've done it in the past


fix(download-file.js): Writing files just with 200 code

We were writing on disk files without checking the http status code causing empty file for cases
where the request failed.

As adding tests to this file is a PITA. I'd say LGTM. :shipit:

Current coverage is 86.84% (diff: 100%)

Merging #43 into develop will decrease coverage by 0.82%

@@            develop        #43   diff @@
==========================================
  Files             4          4
  Lines            73         76     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits             64         66     +2
- Misses            9         10     +1
  Partials          0          0

Powered by Codecov. Last update 6d33b71...401ade9


Enabling background theories and python external functions in the same program

I would like to use background theories and python external computation at the same time in the same program.
My use case does not combine the two. That is, I have programs with rules for theory atoms which don't use external computation and rules which use external computation which do not use theory atoms.
For a toy example, I was expecting the following to work
#script (python)
from clingo.symbol import Number
def exp(n, m):
    return Number(n.number ** m.number)
#end.

two(2).
three(3).
eight(@exp(A,B)) :- two(A),three(B).
&sum{ C*four } = 24 :- C = A * B,two(A),three(B).

For all the background theories I am interested in using, Clingo[DL], Clingo[LP] and ClingoLPX, I get a stack trace and the following: error: python support not available. As python support is just fine for my normal Clingo install (e.g. I can run the above without the last rule just fine with clingo), I was expecting this to just work.
For an example which combines external computation and theory atoms, just add the following rule to the above program:
&sum{ C*one } = 8 :- C = @exp(A,B),two(A),three(B).

How much effort would it be to fix this, at least for the first use case?

The following is a workaround that should work for my first use case:

Separate program P's rules into two separate programs: Pex and Pth, the first only making use of external computation and the second only making use of background theories.
Call clingo --text on Pex to obtain a program Pex-text which already has the python computation performed/the textual substitution applied to.
Union Pex-text and Pth to obtain the intended program P, that background theory-enriched clingos can deal with.

It should work, if you enable python script execution: https://potassco.org/clingo/python-api/5.5/clingo/script.html#clingo.script.enable_python.

Adding from clingo import script; script.enable_python() to the appropriate app.py/__main__.py file of the background theory projects do indeed make the above examples work.
Thanks Roland.


fix: Make the dropdown to have at least one selected value

Description
Makes the dropdown have at least one selected value so that clicking the selected item again doesn't unselect it and make the dropdown empty
Fixes #11484
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Manually
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=c5654a6

Closing this in favour of #11495


discogs: Handle socket errors

Apply, More candidates, Skip, Use as-is, as Tracks, Group albums,
Enter search, enter Id, aBort? a
Traceback (most recent call last):
  File "C:\Python27\Scripts\beet-script.py", line 9, in <module>
    load_entry_point('beets==1.3.11', 'console_scripts', 'beet')()
  File "c:\users\100557855\src\beets\beets\ui\__init__.py", line 953, in main
    _raw_main(args)
  File "c:\users\100557855\src\beets\beets\ui\__init__.py", line 943, in _raw_m
in
    subcommand.func(lib, suboptions, subargs)
  File "c:\users\100557855\src\beets\beets\ui\commands.py", line 870, in import
func
    import_files(lib, paths, query)
  File "c:\users\100557855\src\beets\beets\ui\commands.py", line 847, in import
files
    session.run()
  File "c:\users\100557855\src\beets\beets\importer.py", line 316, in run
    pl.run_parallel(QUEUE_SIZE)
  File "c:\users\100557855\src\beets\beets\util\pipeline.py", line 301, in run
    out = self.coro.send(msg)
  File "c:\users\100557855\src\beets\beets\util\pipeline.py", line 183, in coro
    func(*(args + (task,)))
  File "c:\users\100557855\src\beets\beets\importer.py", line 1227, in lookup_c
ndidates
    task.lookup_candidates()
  File "c:\users\100557855\src\beets\beets\importer.py", line 558, in lookup_ca
didates
    autotag.tag_album(self.items)
  File "c:\users\100557855\src\beets\beets\autotag\match.py", line 433, in tag_
lbum
    search_album, va_likely)
  File "c:\users\100557855\src\beets\beets\autotag\hooks.py", line 563, in albu
_candidates
    out.extend(plugins.candidates(items, artist, album, va_likely))
  File "c:\users\100557855\src\beets\beets\plugins.py", line 360, in candidates
    out.extend(plugin.candidates(items, artist, album, va_likely))
  File "c:\users\100557855\src\beets\beetsplug\discogs.py", line 121, in candid
tes
    return self.get_albums(query)
  File "c:\users\100557855\src\beets\beetsplug\discogs.py", line 173, in get_al
ums
    return [self.get_album_info(release) for release in releases[:5]]
  File "c:\users\100557855\src\beets\beetsplug\discogs.py", line 178, in get_al
um_info
    artist, artist_id = self.get_artist([a.data for a in result.artists])
  File "C:\Python27\lib\site-packages\discogs_client\models.py", line 96, in __
et__
    return [wrapper_class(instance.client, d) for d in instance.fetch(self.name
 [])]
  File "C:\Python27\lib\site-packages\discogs_client\models.py", line 237, in f
tch
    self.refresh()
  File "C:\Python27\lib\site-packages\discogs_client\models.py", line 203, in r
fresh
    data = self.client._get(self.data['resource_url'])
  File "C:\Python27\lib\site-packages\discogs_client\client.py", line 110, in _
et
    return self._request('GET', url)
  File "C:\Python27\lib\site-packages\discogs_client\client.py", line 97, in _r
quest
    content, status_code = self._fetcher.fetch(self, method, url, data=data, he
ders=headers)
  File "C:\Python27\lib\site-packages\discogs_client\fetchers.py", line 73, in
etch
    resp, content = self.oauth_client.request(url, method, headers=headers)
  File "C:\Python27\lib\site-packages\oauth2\__init__.py", line 682, in request
    connection_type=connection_type)
  File "C:\Python27\lib\site-packages\httplib2\__init__.py", line 1593, in requ
st
    (response, content) = self._request(conn, authority, uri, request_uri, meth
d, body, headers, redirections, cachekey)
  File "C:\Python27\lib\site-packages\httplib2\__init__.py", line 1335, in _req
est
    (response, content) = self._conn_request(conn, request_uri, method, body, h
aders)
  File "C:\Python27\lib\site-packages\httplib2\__init__.py", line 1291, in _con
_request
    response = conn.getresponse()
  File "C:\Python27\lib\httplib.py", line 1074, in getresponse
    response.begin()
  File "C:\Python27\lib\httplib.py", line 415, in begin
    version, status, reason = self._read_status()
  File "C:\Python27\lib\httplib.py", line 371, in _read_status
    line = self.fp.readline(_MAXLINE + 1)
  File "C:\Python27\lib\socket.py", line 476, in readline
    data = self._sock.recv(self._rbufsize)
socket.error: [Errno 10054] An existing connection was forcibly closed by the r
mote host

I get this error during a regular import and the only plugin currently being used is discogs. I removed the discogs plugin and started the import again and it worked fine.

Thanks for the report. These errors should now be caught and logged instead of crashing.


Default to Runner v2 for Python Streaming jobs.

This will take effect from release 2.32 on.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @angoenka


formatter read from stdin and print to stdout

Specific Demand
I'm using helix editor which require formatter to read the source file from stdin and print the result to stdout
My discussion on Helix Editor

That was added in https://github.com/DioxusLabs/dioxus/pull/1529. You can use dx fmt -f - to format code from stdin

@ealmloff log will be printed to stdout, how to disable it ?


Resolve #29 [Assert] All-in Hamcrest

org.whaka.asserts.builder package is removed
AssertBuilder is moved into org.whaka.asserts
All "assert performers" and "instant asserts" are removed
AssertBuilder provides now 3 main methods:

#checkThat(Object, Matcher)
#checkThat(Object, Matcher, String)
#checkThat(Object, Matcher, String, Throwable)

Assert provides now 3 main methods:

#assertThat(Object, Matcher)
#assertThat(Object, Matcher, String)
#assertThat(Object, Matcher, String, Throwable)

Note: any custom matchers will be implemented under separate issues.

Maybe it's better to return some AssertError.EMPTY instead of null?

Should this EMPTY error than be also throwable?

What is the point of an "error of the assertion" without any assertion (messages/results)?
How then method "#performAssert" should behave in case of empty builder? Should it still throw this EMPTY error?

If error shouldn't be fully functional and throwable, then:

How?
What is the point of it?

It was decided to return null in this case, for it seems to be the only proper way to indicate the lack or error.
Also note, that AssertError cannot be empty, this is treated as construction exception.

To avoid null value, it's better to return special case of expected class. Potential NPE will be eliminated.
#performAssert will look like: if(!error.isEmpty()) throw error.

To avoid null value, it's better to return special case of expected class. Potential NPE will be eliminated.

It sounds good, as everything dogmatic for no reason. But tells nothing, on the subject of how should it work in this particular case.
Does it really pay off to have a system-wide empty instance of an error - which doesn't have a point without some proper message in it - exactly the thing I was trying to avoid with exceptions in the error constructor, only to avoid a single possibility of an NPE? Especially taking to note the fact that #build method is created mostly for consistency matters, and will be actually used less then never.
Trying to fix this "neverhappen" problem will literally introduce more additional complexity than the occasional null-check (if method ever will be used, which I doubt).
And still, if we introduce an empty instance we have to mind additional usecase of the:
throw AssertError.EMPTY;

Which is unacceptable.

Method might return Optional<AssertResult>

Add assertFail(Consumer consumer) (without message)
Done

"Optional" looks better.
P.S.
You don't have to write tons of sarcasm in comment. "null" from the "build" method looks weird.

"Optional" looks better.

Fixed

You don't have to write tons of sarcasm in comment. "null" from the "build" method looks weird.

Noted. Actually, only part about "dogmatic" was a sarcasm =)
Otherwise I do always appreciate a discussion of a proposed code, but just am doing it weird.
Haven't thought about optional from the beginning at all.


 But is there anyway from within duckdb to get the CRS data from the .prj file in the shx I'm parsing with ST_READ?
I see that the extension integrates with PROJ which makes me suspect what I'm asking is possible (though I do see from the documentation that the geometry itself can't contain SRID information yet)
I see two approaches to handle this, we probably want both.

Implement something like a st_describe to output the GDAL metadata from a dataset
Output the CRS of the dataset as an additional columns when calling st_read, we just have to be careful to deduplicate the column names, or maybe even allow specifying the column name with a parameter.

I like the st_describe option, as it's simple, and an example could be provided in the documentation showing how to do a select from st_read that also selects the relevant columns from st_describe to achieve the same results as your second option. Leaving the complexity of deduplication to the user (who can do so in the simplest way that suits their data set)

Yeah I agree that CRS should not be stored per value, so far Ive tried to tell people to store it as a column instead, which makes much more sense from a db perspective.
Generally I feel like kernels should be agnostic to the CRS though? The only thing I can see mattering is whether the geom is planar or spherical, but I think thats better solved with a GEOGRAPHY type.

Generally I feel like kernels should be agnostic to the CRS though

Totally! I think what I had in mind was if you do something like st_intersects you can error if x and y do not have identical CRS. In Acero that would happen at kernel selection time (not sure where what happens in DuckDB).

Right now It doesnt 😅, but I agree it, absolutely should error.


Document Terraform and Terraform provider versions that are known to work.

When a Terraform provider is updated, variables used by the provider might be updated.
E.g.
Error: Unsupported argument

  on modules/k8s_csi_driver_azure/main.tf line 3, in provider "helm":
   3:         load_config_file       = false

An argument named "load_config_file" is not expected here

This is a bit of headache when you cannot simply run tf plan anymore without updating the code.
Maybe Terraform provides a way to lock the dependencies (e.g. in script source) and/or provides a mechanism to output current versions of all dependencies. It might be good to store this output with the code in repo.

This seems to be addresses by Terraform 0.14 which bring support for lock files.
https://www.hashicorp.com/blog/terraform-0-14-introduces-a-dependency-lock-file-for-providers
Seems that JouHouFin already did some of the initial work: https://github.com/smaddis/smad-terraform-azure/commit/2a92344009af2e37807a51e553cc183f90ec8d54#diff-ad2c33b49112c808ea24699b01e9e020735e894c9438ace109477b3e6098cc43

Let's discuss IRL what is proper way (basically when to fetch dependency updates) to update the lock file.


encoding/json: Proposal - Flexible omitempty

Questions unrelated.
I run into the issue where I wanted to omitempty a non-pointer struct. I couldn't make it happen properly so I think about a solution. So this is the code running I guess when there is the omitempty tag on the field. What if it would check for an extra interface implementation where we can flexibly determine when we consider a non-pointer struct as empty?
So use-case in this playground. It seems that the empty struct marshalled into the JSON. But if the Go has an interface like below I can implement this and the linked source can look for that implementation. If no any implementation than go with the default.
type Something interface {
  IsEmpty() bool
}

Dup of #32675, see discussion at #11939.


NodeJS Client builds empty

What version of gRPC and what language are you using?
1.4.1
What operating system (Linux, Windows, …) and version?
Various(Mac OS, Ubuntu, Centos)
What runtime / compiler are you using (e.g. python version or version of gcc)
Node.JS
What did you do?
Updated from Node.js 1.3.9 to 1.4.1.
Buffers were previous creating clients.
Now they aren't, and they are doing so without bugs.
What did you expect to see?
A Working Client
What did you see instead?
An Empty Client
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment?

You haven't provided any of the information relevant to understanding, reproducing, or solving the problem.  What did you expect the code to do? What did it do instead?

Instantiation and Generation of clients(With any buffers) is returning an empty object in Node.
For example:
const address = 'SOMESERVER';
const creds = grpc.credentials.createInsecure();
const client = new someBuffer.TEST(address, creds);

This will return an empty object. No channels, nothing.

What is someBuffer?

A loaded buffer, gotten via grpc.load

When you say that you got an "empty object", do you specifically mean that it has no "own properties", or that it generally fails to provide the functionality you expect from a client object?
Can you provide a complete reproduction case? We have a number of tests that follow that general pattern, so you must be encountering a scenario we haven't considered.

The Object has no properties.
I'll check with engineering to see if we can clear some of the code for the public. Baring that, I'll write up an example of the fail case and post it(I can fail it fairy regularly now).

To be clear, you are looking at an instance of a class, which is part of a prototype chain. Some fields and methods may be properties of the prototype, or the prototype's prototype. Fields on the prototype will not be printed if you stringify the object, for example, but that doesn't mean that they don't exist.

Due to lack of further comments by the reporter, I think this question has been resolved.


Updated protobuf dependency and fixed type clash

Description:
The following PR fixes protobuf name clashes, due to lack of namepsacing for ecdsa and eddsa messages.
As a side effect it also fixes issue: https://github.com/binance-chain/tss-lib/issues/106
Work done:

Removed deprecated github.com/golang/protobuf dependency
Added namepsacing to ecdsa and eddsa message types, to avoid name clash
Updated Go version to 1.16

Requested reviewers:
@ackratos, @omershlo , @notatestuser
(tagging like that, since I don't seem to be allowed to request review the normal way)

@PlamenHristov We have update the master branch. It still has deprecated package usage. Would you like to do a rebase to your PR?

Hey @yycen,
Merged from master and resolved conflicts.

The file signature.pb.go has not been regenerated and still references github.com/golang/protobuf/proto. Would you update signature.proto file with go_package = "./common" and regenerate to pb file?

Ah apologies. Was doing the update in a rush and missed it.
Should be good now.


[QUESTION] Can PIT ID change across search requests?

Hi!
I was wondering about the tests in ElasticsearchIntegrationTests.java regarding PIT. In this test, the PIT ID is reused across multiple requests, without using the one that is returned in the response of the search requests (if I understand the code correctly).
I want to make sure I understand the documentation correctly. In the ElasticSearch docs, they explicitly say that the PIT ID can change across requests:

The open point in time request and each subsequent search request can return different id; thus always use the most recently received id for the next search request.

Since OpenSearch was a fork of ElasticSearch, I'm wondering if there is a similar constraint for OpenSearch? Or can I be certain that the PIT ID never changes?
Thanks!

Since OpenSearch was a fork of ElasticSearch, I'm wondering if there is a similar constraint for OpenSearch? Or can I be certain that the PIT ID never changes?

Hi @matheisco , no sure I understood your question correctly, there could be many PITs open and you could run search request against any of those by providing the respective PIT ID. Does it make sense?

Hi @reta, I understand that part, what I'm unsure of is the PIT ID that OpenSearch returns in the response of a search request:
{
    "pit_id": "XYZ",
    "took": 180,
    "timed_out": false,
    "_shards": {
...

According to the ElasticSearch docs, subsequent search requests can return different PIT IDs, so I can't keep using the one from the initial PIT creation request.
Not sure if the same is true for OpenSearch...

According to the ElasticSearch docs, subsequent search requests can return different PIT IDs, so I can't keep using the one from the initial PIT creation request.

Oh I see, thank you @matheisco , so I would say this: at the moment, the pit_id of the response should much the pit_id of the request, but I strongly believe that this may change in the future (since there are some unimplemented flows internally), so I think the general answer would be - yes, it could change.

Ok, thanks for the clarification @reta!


feat: edit profile's education part to fit the mockup

Changes

Changed the education_item.dart to fit the mockup.
Changed the images in the codebase to fit the mockup.

UI

Also a side tip, you can make the image in your description smaller by using the <img src="..." width="350px" />

Also, the fields, when focused, should have the inner icon in the teal colour as well!

Were you able to address this comment?

Also, the fields, when focused, should have the inner icon in the teal colour as well!

Were you able to address this comment?

I think I need explanation for that due to the limit understanding for this comment


add new bool flag use-exec to ssh command

This new flag add possibility to choose between exec or terminal during ssh command.
This is needed, because when KUBEVIRT_PROVIDER is set to oc-3.11.0 and terminal is available,
then it requires upgraded connection to attach to container. If call is changed to upgraded, then
ssh gets stuck on iopodman.GetAttachSockets().Call function and will never end.
But if communication is done over exec, then everything works as expected.
//cc @fromanirh I am not sure if this is correct fix. Can you advise me if it is correct place?
Signed-off-by: Karel Šimon<EMAIL_ADDRESS>

the Terminal function was born as blind port of what the original gocli tool did with the docker API.
Is actually very possible we don't need it entirely, and we can build everything we need on top of Exec.
So, if you succesfully tested Exec works already, I'd actually suggest to get rid of it entirely and always use Exec. No new option needed.

ok, so i will check all providers, if any need Terminal function

It could be that the provisioning step, which is currently out of scope, needs it. If so, we should do a better analysis about how to port it to podman, and add it later.
Hopefully is not needed for phase 1 (just run the images)

Closing this in favour of https://github.com/fromanirh/pack8s/pull/31


Dotted lines

Replace the gray block outline with dotted lines.

This PR fails because of a test bug that was fixed in remember-socket-floating. Submitting small changes directly to floating-assembly and merging remember-socket-floating.


fly execute randomly can no longer properly relatively resolve inputs

I have been using fly execute successfully all morning and then all of a sudden this error starts happening 100% of the time when using relative paths.
➜  Desktop fly --target ci execute --config `./pipeline/ci/tasks/task_deploy_stack.yaml` --input pipeline-scripts=../../../scripts
executing build 41 at https://XXXXXX/builds/41
initializing
failed to upload input 'pipeline-scripts': Put https://XXXXX/api/v1/builds/41/plan/5b058e31/input: tar compress failed (exit status 1). output: "tar: ci/tasks/deploy_environment.yaml: Cannot stat: No such file or directory\ntar: Error exit delayed from previous epipeline-scripts: 12.42 MiB/s 0s
Put /volumes/065afdce-adf9-4529-59af-516c96a4db9e/stream-in?path=.: unexpected EOF
errored

When I rename the config file to be ./pipeline/ci/tasks/deploy_environment.yaml it starts working again.
I guess the issue is. What must I do to rename the config file?

Today I faced the same thing, and I found out that uploading inputs was always failing on removed and not commited files. So it turns out that fly execute is getting list of files to upload from git state instead of real files.

@antonu17 your point is correct, it works after staging the changes
It's weird that this is required, as fly execute's main purpose was to test the task config locally without commiting under-development changes to source control

Hey,
Looking at the code (see https://github.com/concourse/fly/blob/9a2f2ebde1136119a17d53057b1b4f273385f3e4/commands/internal/executehelpers/uploads.go#L21-L28), it seems to me that with the --include-ignored flag you can get around that, right?
--include-ignored             Including .gitignored paths. Disregards .gitignore entries and uploads everything

thx!

Yes, It looks like --include-ignored includes not only ignored, but simply all files that are available in current dir, without looking into git stage. :+1:
Nice catch, @cirocosta :wink: !


Add support for NOXPYTHON, NOXEXTRAPYTHON and NOXFORCEPYTHON

Closes #672

I think all the feedback's been addressed. Feel free to merge 😄


FormatFilter overrides content type set explicitly by the developer

If the user sent a request with url like api/values.json and the developer set a content-type as application/xml on ObjectResult, I would have expected the one set by the developer to picked as he is explicitly setting the content-type.
Expected: application/xml
Actual: application/json
@rynowak

Please confirm with @rynowak that this is a bug, but it certainly sounds broken to me.

7a955bcbc09d34a4096ba20ca4248eebdc0b9df3


Need to List Groupie Version in the Mini-Map Menu Title and Bulletin Board Title

This will help diagnose errors.
"Groupie - 1.41"

Also in ToC. https://github.com/Gogo1951/Groupie/issues/178


[NEW ALGORITHM] GRADIENT DESCENT IN C

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
GRADIENT DESCENT
About:
Gradient descent is the most important algorithms in deep learning and I would like to add the implementations of the naive version as well as more advanced versions once this pr is closed in C language.
Labels:
new algorithm, gssoc-ext, hacktoberfest, level3

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

@karandevhub please stop spamming as the issue is opened by me and I have clearly mentioned I wanna work on it.

@anishka25  oh ! sorry for that i was testing my Extension

@pankaj-bind why was this closed? may I know the reason?


Fix/UI - Grid SC

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Fixed issues (PRs without this will not be accepted)

Fixes #210

Changes

grid to styled-components.

PR Checklist

[x] Grid to styled-components

I don't see this component being used anywhere. Do we need it @tristanMatthias or it's a legacy component?


Wrong description when multiple custom-data-modal are defined

Dear IGV team,
Thank you very much for your awesome work. I have been toying recently with the IGV webapp and I think I have found a minor bug.
I am using the latest prebuilt package (https://igv.org/app-archive/igv-webapp.2.13.3.zip) and adding a custom-data-modal to the track will use the "Description" from the first custom-data-modal defined in the trackRegistry.
If I add my own custom-data-modal after the 4DN, I get the 4DN Description for both custom-data-modal, while I get my own Description if I put my own custom-data-modal first in the trackRegistry.

Sounds like a bug.  Could you post your custom data modal configuration?

{
  "label": "Neoenhancer Positive Controls",
  "type": "custom-data-modal",
  "description": "All files related to neoenhancer positive control samples. Can be used to select a subset of files to explore the results.",
  "columns":
  [
    "name",
    "format",
    "donor_id"
  ],
  "delimiter": "\t",
  "data": "resources/tables/neoenhancer_positive_controls.tsv"
}

And this description is applied to the 4DN tracks if its json is loaded after in the trackRegistry.json:
  "hg38": [
    "resources/tracks/hg38_annotations.json",
    "resources/tracks/hg38_encode.json",
    "resources/tracks/hg38_neoenhancer_positive_controls.json",
    "resources/tracks/hg38_4dn.json"
  ],

This is fixed with commit 55c53fdd2cd362099419780c5a75039620ff1942