Pod has unbound PersistentVolumeClaims (repeated 7 times)

Rancher versions:
rancher/rancher:master
rancher/rancher-agent:master
Infrastructure Stack versions:
rancher/hyperkube:v1.10.1-rancher2
Docker version: (docker version,docker info preferred)
18.3.1-ce
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Boot2Docker 18.3.1-ce
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
vSphere
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher, internal DB
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Kubernates
Steps to Reproduce:
-Configure Storage class to provisioner Ceph RBD
-Configure Workload (new or edit)
--Enter "name"
--Add a new persistente volume (Claim)
--Select ceph class
--Define Button
--Enter "mount Point"
--Launch or Upgrade button.
Results:
The POD status is "Scheduling" and show error "Pod has unbound PersistentVolumeClaims (repeated 7 times)"

Me too

I have been running Rancher 2.0 in my Linode mahcine. None of the Catalog Apps are working and always giving this error. Please how to fix it? I have tried many way to deploy and kubectl works fine, but catalog is not working.
Thanks,
Love Rancher btw :)

It's working for me with the nfs-provisioner in catalog.

Olá @MichelDiz . Não achei seu contato no seu perfil. Estou testando várias soluções para volumes persistenstes. Como você configurou o NFS? você usa vários compartilhamentos NFS ou um apenas para todos os namespaces? Tentei usar storage class para o NFS mas não achei na listagem do rancher.

Hi.
Thank you. Will this work without nfs? Like just from local disk?
On Sat, May 12, 2018, 5:45 PM Willian Itiho Amano<EMAIL_ADDRESS>wrote:

Olá @MichelDiz https://github.com/MichelDiz . Não achei seu contato no
seu perfil. Estou testando várias soluções para volumes persistenstes. Como
você configurou o NFS? você usa vários compartilhamentos NFS ou um apenas
para todos os namespaces? Tentei usar storage class para o NFS mas não
achei na listagem do rancher.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rancher/rancher/issues/13442#issuecomment-388585274,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUQ4CURqYJV0Jjs6RIPSpaPtUPaHdezlks5tx1fmgaJpZM4T70tg
.

@kaushikCanada Not sure if will work without the NFS server. Go to Catalog and run the "nfs-provisioner" before run any app.
@Itiho Eu ainda estou explorando o Rancher 2.0, eu acabei de sair do Rancher 1.X - Funcionou como eu disse, apaguei o Wordpress que levantei para teste. Rodei o nfs-provisioner, e levantei novamente o Wordpress e Voilà tudo funcionando. Só tenho problemas agora com IP, como estou usando um virtualbox com Photon WMware. Eu tenho de ver o que fazer quanto a isso. Mas que apareceu tudo funcionando, apareceu. Os volumes funcionaram.

@kaushikCanada In that case open a new issue in the github from that app you're using.
but first, pick up an app from the catalog and see if it works.
If it works, it is not related to that issue. It seems to me an application problem. If neither of the catalog app works, then open a more detailed Issue here on the Rancher.

I have been trying to launch mysql containera fr a while and it is giving
this output. I will keep trying. One thing is that the nfs provisioner
worked and is active.. but other apps are not working. Let me see.
On Sat, May 12, 2018, 7:53 PM Michel Conrado<EMAIL_ADDRESS>wrote:

@kaushikCanada https://github.com/kaushikCanada In that case open a new
issue in the github from that app you're using.
but first, pick up an app from the catalog and see if it works.
If it works, it is not related to that issue. It seems to me an
application problem. If neither of the catalog app works, then open a more
detailed Issue here on the Rancher.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rancher/rancher/issues/13442#issuecomment-388591154,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUQ4Cb06ajHmoSVAGhcmb7cVSeFeCGxQks5tx3XzgaJpZM4T70tg
.

same here with Rancer 2.0.4 and Mongodb-replicaset (catalog library version)

Same with Rancher 2.0.5 and postgresql (helm library version)

same here with anything.
Rancher 2.0.5  Azure Disk Storage class
To add some value:
Volumes are apparently being created, but when viewed are marked Pending. Similar to described here: https://github.com/rancher/rancher/issues/13305

I am having the same issue with AES EBS. I can not even attach an existing claimed volume !!
I have watched all the Rancher Training videos on Youtube :D but none of them shows live dynamic EBS volume provisioning , All the demo includes NFS Provisioning.
However NFS Provisioning works perfect !!

#update
The Problem with AWS EBS solved by changing the cluster cloud provider settings to Amazon. I think its necessary for Dynamic Provisioning of Storage, but its not written in 2.0 docs ..

@sh0umik if you change it, does it still respect the auth values from the template to build out the VMs? I found that the radio options seem reversed. It seems like if you select Azure or AWS (depending on) all of those fields from what amount to be settings in the host templates show.. it's very odd to me.

@CRuppert no it seems fine.. however the template should change the default user from ubuntu to rancher

2.0.8 - none of the apps are working

How are people going to production with rancher if nothing is going to work.
On Wed, Oct 3, 2018, 4:49 AM geruetzel<EMAIL_ADDRESS>wrote:

2.0.8 - none of the apps are working
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rancher/rancher/issues/13442#issuecomment-426559121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUQ4CYOohR4vFxjCqZeO1tvtFrbxxukOks5uhHo2gaJpZM4T70tg
.

Same here trying to deploy cockroachdb (or anything, really), using Gluster

Thanks for your report!
We will investigate it soon

I have faced this before while deployng rancher.
On Mon, Oct 8, 2018, 7:48 PM Logan<EMAIL_ADDRESS>wrote:

Thanks for your report!
We will investigate it soon
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rancher/rancher/issues/13442#issuecomment-428014069,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUQ4CQQ0ryrJx2NBbK3p1jliPY474V4Uks5ui-QygaJpZM4T70tg
.

our problem was that we didn't have a storage class defined, once that was done it started working

Can u give a screenshot maybe pls
On Mon, Oct 8, 2018, 8:19 PM Greg Keys<EMAIL_ADDRESS>wrote:

our problem was that we didn't have a storage class defined, once that was
done it started working
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rancher/rancher/issues/13442#issuecomment-428019281,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUQ4Cd_jJT8HKN0S8Ldfw4QL5osLHv0xks5ui-umgaJpZM4T70tg
.

Hi, all.
It will be very easy for the charts from Library catalog as Rancher will maintain them. What you need is just making sure there is a storage class in your cluster.
But for Helm Incubator, sometimes you might meet some problems.
First, make sure you have a storage class installed and make sure there is a default storage class. If you don't have one, an easy way is deploying nfs-provisioner in Library catalog.

Second, for instance, if you want to deploy Patroni from Helm Incubator. cc @daya

Deploy Patroni in catalog without any answers and just click Launch
In workload detail page of patroni, you can see a pod failed when scheduling.

Now you can click the pod and go to the pod detail page to see the Events section to find out why k8s can not schedule the pod.

As it says pod has unbound PersistentVolumeClaims (repeated 2 times), so it must be something wrong with PVC. So go to the PVC list page now. And you can find a PVC is in Pending state. So there is something wrong with it.

Click the pending pvc, it will take you to the pvc detail page. Click Events and you can find out what is going on.

As it says no persistent volumes available for this claim and no storage class is set,  so I guess there is something wrong in the YAML of the PVC. So I clicked the View YAML to check it out.

Yes, I find the storageClass is empty. So K8S can not provision the PV for you automatically.  Why it is empty? I guess I missed some required filed for the app. So I removed the app and try to deploy it again. Check the Detailed Description of this App. And I found there is a answer we might need to set.

Add the answer to try if it will help and click Launch.  (there is some bug in the charts with etcd mode. Etcd has fixed that issue https://github.com/helm/charts/pull/2864/files. But patroni doesn't update etcd yet https://github.com/helm/charts/blob/master/incubator/patroni/requirements.yaml. So we need to turn off etcd and use zookeeper)

Wait a bit and everything just works well!

Please let us know in a comment if you can still reproduce the issue, and we'll reopen it

I have the exact same issue trying elasticsearch helm chart on bare-metal (RHEL 7.6) 3 node cluster
the message I get is
Pod has unbound PersistentVolumeClaims (repeated 3 times)

fresh install, i am deploying nfs provision-er app and i am getting same error as before. any suggestions

fresh install 2.2.3, just for testing I deployed nfs-provisioner so it can create storage class, but rancher is even complaining about that.

you need to have PV for nfs-provisioer


disable bitcode on try builders

bitcode makes builds take up to 10x longer.  We don't need it on try builders.
I also regenerated the config file from the main.star
@christopherfujino  - is it ok to bump xcode for the one that was missing?
@LongCatIsLooong - did you intentionally or manually edit that one?
@iskakaushik - does this look ok to you (give fuchsia ctl to all builders as a property?)
@godofredoc  - we may want to add some CI to this repo to make sure main.star can successfully run.

I simply relanded @chinmaygarde 's PR.

I'm going to land this since it should speed up try jobs immensely.  Happy to address further feedback in a subsequent CL.
I also want to land it so I can add a CI check that main.start is valid :)


Add Flagsmith python provider

This PR
Adds the information for the Flagsmith python provider.
Related Issues
N/a
Notes
N/a
Follow-up Tasks
N/a
How to test
While running the dev server, browse here.

Hi @matthewelwell, could you please expand the readme to include installation and information on basic usage?

https://github.com/Flagsmith/flagsmith-openfeature-provider-python/pull/4

@beeme1mr thanks for the review and apologies for the terrible readme 🤦
I've updated that now (as per the PR you linked) and resolved the conflicts. Please let me know if you're happy to merge this now.


Bump grpc to v1.50.1

Bumps grpc to v1.50.1
Bumps protobuf to v1.28.1
Bumps genproto to v0.0.0-20221107162902-2d387536bcdd

I have a PR open in kubernetes to bump grpc there too https://github.com/kubernetes/kubernetes/pull/113707

/retest

/retest

/retest

https://github.com/grpc/grpc-go/pull/5782 it seems that we can wait for 1.51 😅 if the CI is still unhappy 😞

/retest


not working at user signup

When not filling the captcha
error: invalid input syntax for type boolean: ""
    at Parser.parseErrorMessage (/usr/local/lib/node_modules/@saltcorn/cli/node_modules/pg-protocol/src/parser.ts:369:69)
    at Parser.handlePacket (/usr/local/lib/node_modules/@saltcorn/cli/node_modules/pg-protocol/src/parser.ts:188:21)
    at Parser.parse (/usr/local/lib/node_modules/@saltcorn/cli/node_modules/pg-protocol/src/parser.ts:103:30)
    at Socket.<anonymous> (/usr/local/lib/node_modules/@saltcorn/cli/node_modules/pg-protocol/src/index.ts:7:48)
    at Socket.emit (node:events:390:28)
    at Socket.emit (node:domain:475:12)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:199:23)
    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)

When filling the captcha
error: invalid input syntax for type boolean: "hjp6"
    at Parser.parseErrorMessage (/usr/local/lib/node_modules/@saltcorn/cli/node_modules/pg-protocol/src/parser.ts:369:69)
    at Parser.handlePacket (/usr/local/lib/node_modules/@saltcorn/cli/node_modules/pg-protocol/src/parser.ts:188:21)
    at Parser.parse (/usr/local/lib/node_modules/@saltcorn/cli/node_modules/pg-protocol/src/parser.ts:103:30)
    at Socket.<anonymous> (/usr/local/lib/node_modules/@saltcorn/cli/node_modules/pg-protocol/src/index.ts:7:48)
    at Socket.emit (node:events:390:28)
    at Socket.emit (node:domain:475:12)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:199:23)
    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)

in my custom form:

Thanks, I was hoping someone would test with sign up. This may be related to the other issue you saw, I will look at both

Looks like I'm a bug magnet. Usually at my first try I'm already at an edge case :sweat_smile:

fixed in https://github.com/saltcorn/saltcorn/pull/1508. Make sure you upgrade the captcha plugin to latest version

Great! Thanks @glutamate


buildbot: 3.1.1 -> 3.2.0

Motivation for this change
Updates buildbot to the latest version. Upstream just merged a patch to fix compatibility with SQLAlchemy 1.4, which allows this package to build again.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 132186 at b4ce66c0 run on aarch64-linux 1

20 packages built successfully:

buildbot (python39Packages.buildbot)
buildbot-full (python39Packages.buildbot-full)
buildbot-ui (python39Packages.buildbot-ui)
buildbot-worker (python39Packages.buildbot-worker)
python38Packages.buildbot
python38Packages.buildbot-full
python38Packages.buildbot-pkg
python38Packages.buildbot-plugins.console-view
python38Packages.buildbot-plugins.grid-view
python38Packages.buildbot-plugins.waterfall-view
python38Packages.buildbot-plugins.wsgi-dashboards
python38Packages.buildbot-plugins.www
python38Packages.buildbot-ui
python38Packages.buildbot-worker
python39Packages.buildbot-pkg
python39Packages.buildbot-plugins.console-view
python39Packages.buildbot-plugins.grid-view
python39Packages.buildbot-plugins.waterfall-view
python39Packages.buildbot-plugins.wsgi-dashboards
python39Packages.buildbot-plugins.www

14 suggestions:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/buildbot/default.nix:118:0:
    |
118 |       description = "An open-source continuous integration framework for automating software build, test, and release processes";
    | ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/buildbot/plugins.nix:27:7:
   |
27 |       license = licenses.gpl2;
   |       ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/buildbot/worker.nix:30:5:
   |
30 |     license = licenses.gpl2;
   |     ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/buildbot/plugins.nix:91:0:
   |
91 |       description = "Buildbot Grid View Plugin";
   | ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/buildbot/plugins.nix:113:0:
    |
113 |       description = "Buildbot WSGI dashboards Plugin";
    | ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/buildbot/plugins.nix:93:7:
   |
93 |       license = licenses.gpl2;
   |       ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/buildbot/plugins.nix:69:0:
   |
69 |       description = "Buildbot Waterfall View Plugin";
   | ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/buildbot/default.nix:120:7:
    |
120 |       license = licenses.gpl2;
    |       ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/buildbot/plugins.nix:71:7:
   |
71 |       license = licenses.gpl2;
   |       ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/buildbot/plugins.nix:49:7:
   |
49 |       license = licenses.gpl2;
   |       ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/buildbot/plugins.nix:25:0:
   |
25 |       description = "Buildbot UI";
   | ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/buildbot/plugins.nix:115:7:
    |
115 |       license = licenses.gpl2;
    |       ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/buildbot/pkg.nix:29:5:
   |
29 |     license = licenses.gpl2;
   |     ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/buildbot/plugins.nix:47:0:
   |
47 |       description = "Buildbot Console View Plugin";
   | ^


api.get.current_page returns wrong value

Hi
I'm working on an extension that migrates e-mail messages to a google group, using api.get.selected_emails_data method. I've noticed that it uses a faulty URL to get the id's when not in inbox, because  api.get.current_page() returns only 'label', and not 'label/'.
Quick fix could be
page = hash.join("/");
in stead of current
if($.inArray(hash[0], pages) > -1) {
page = hash[0];
}
Thanx for the good work! We had a company developing a gmail extension, but I wanted to add some features myself, so I'm integrating it with this great library

Hi @WimRoose could you clarify this a bit further? The goal of the current page is to return the type of the given view. In that context, label is the group, instead of label/. I would be interested in knowing how this affects your usecase

@KartikTalwar
For instance: select a label in inbox, check some e-mails, and then trying to get ID's of selected ones:
api.helper.get.visible_emails_pre() {
var page = api.get.current_page();
.....
if(page.indexOf('label/') == 0) {
url += '&cat=' + page.split('/')[1] +'&search=cat';
.....
}
Problem is that current_page returns only type ("label" in this case), while api.helper.get.visible_emails_pre() is expecting "label/", to build a correct URL
api.get.current_page()  {
....
if($.inArray(hash[0], pages) > -1) {
page = hash[0];   // comment by me: hash[1] contains , but isn't returned
}
}
....
Does this makes sense?


fix recaptcha action not getting passed correctly

Just thought it would be a good idea to not have it be a magic value in case it needs to be changed in multiple places in the future.


Have folders per service

With the addition of other Azure services, I believe a per service folder containing the samples for this service would enable users to easily find the samples that they want.
As for multi service actions it could be in a special folder.

Sure, we now have a folder structure for all templates. Thanks for the suggestion.


[Wildcard Variables] Feature Specification

Issue for tracking that the feature spec is in progress or is complete.
The working spec is located here: https://github.com/dart-lang/language/blob/main/working/wildcards/feature-specification.md
@eernstg @munificent Can we confirm that the spec is basically complete? Is there anything else we need to discuss or decide on?

I just checked, and the icky thing I disagree with is disallowing super._.
We should allow it.
If it breaks the current desugaring specification of super parameters, then define super._ as introducing a fresh name instead of no name.

I added the rule that super._ is an error because the desugaring will turn it into code that doesn't work (or code that does something completely different! - if _ in super(..., _, ...) will now denote a static or top-level declaration).
We could try to enable super._ by introducing an implicit renaming step that makes it possible for the superinitializer to denote this parameter. However, I think that would be an anomaly, and it is yet another exception to remember while coding.
So I'd prefer that we keep super._ as an error. Developers may then do the rename themselves. First case, it's in the same library:
// Current code. Breaks because `super._` will be an error.

class A {
  final int _;
  A(this._);
}

class B extends A {
  B(super._);
}

// Migrated code. No problem, no rename lints, no code outside this library can know.

class A {
  final int __;
  A(this.__);
}

class B extends A {
  B(super.__);
}

In the other case, where A and B are declared in two distinct libraries, we would get a rename lint anyway because _ isn't the same name in two different libraries.
class OtherB extends A {
  // ignore: matching_super_parameters
  OtherB(super._);
}

class OtherB extends A {
  // ignore: matching_super_parameters
  OtherB(super.__);
}

In general, we will continue to allow developers to use _ as the name of some declarations. But I do not think we should bend over backwards to make it convenient to do so, at the expense of the consistency and comprehensibility of the language as a whole.

I think we should allow super._ because I don't expect users to expect an exception, so it not working is a surprising exception to them.
If the author doesn't use the name of a positional super.x parameter, it's reasonable to assume that changing it to super._ is fine. After all, they can change it to super.y or super._arglebargle without any problem.
The reasoning that the specification uses the name is meaningless to the user. Can't it just not do that? (Yes, yes it can. It's an accident of specification that the name is used, not anything inherent to the feature. It used to be a safe assumption that the name given to the parameter would still be in scope and refer to the same value at the point of the super constructor invocation, so the specification chose to specify the meaning as a desugaring to an invocation that references the parameter variable. That's no longer safe if we allow super._, but that shouldn't break the wildcard feature by disallowing a meaningful use, it just means that the specification of super parameters shouldn't make that assumption any more, and should be rewritten to work anyway.
We can make it work. How we do that is up to us, it shouldn't matter to the user that we wrote a specification for super parameters that wasn't forward compatible. That's our problem, and we should solve it, and allow super._.

Another thought: Maybe we should treat all of __, ___ etc. as non-binding declarations too. It's not necessary, but I'm not sure I'd want someone to write __ as a name, just to not have it be non-binding, and still not give the thing a real name.
It's a little iffy, because then they should probably work the same in patterns too. And that's an unrelated breaking change.
(Still think it would be prettier.)

Another thought: Maybe we should treat all of __, ___ etc. as non-binding declarations too. It's not necessary, but I'm not sure I'd want someone to write __ as a name, just to not have it be non-binding, and still not give the thing a real name.

I considered that when I was first writing the proposal. You're point about it being inconsistent with patterns is, I think, a good one.
Also, we ultimately want to get to a world where people don't use __, ___, etc. So I think scoping wildcards to only be a single _ helps us go in that direction.

Moved all discussions to their own issues. Easier to keep track :)

https://github.com/dart-lang/language/issues/3792
https://github.com/dart-lang/language/issues/3793


Switching presets once user starts typing

Description

Is there a way without impacting performance to dynamically switch presets inside TypesenseInstantSearchAdapter? I would like to switch presets when a user starts typing for instance.

You could use the updateConfiguration() method of the adapter.


Enable users to configure their monospace font specifically

This replaces the overly-verbose radio-button font setting (which only allows embedded or autodetected from system) with a simple combobox providing both existing options as well as a custom option to allow the user to select any font of their choice/style.

a follow-up can be to use the selected font wherever monospace fonts are used such as the console.

A separate configuration for that may make sense , but yes, this makes it much simpler to do that. Figured it would be a bit too much for this PR though :)

Concept ACK
This should allow users to select a dyslexic font as well (if they have it installed) - which can be helpful when dealing with numbers.

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts
Reviewers, this pull request conflicts with the following ones:

#440 (Do not require restart if overridden option is modified by hebasto)
#435 (Move third-party tx URL setting from Display to Wallet options tab by jarolrod)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

@luke-jr still working on this?

@hebasto Yes, but I don't understand the review comment.

Concept ACK
https://github.com/RandyMcMillan/gui/runs/6019248786

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

@luke-jr  Rebase?

Rebased

Approach ACK. Tested on Windows 11. Observing kind of jittering of the vertical position of the "Font in the Overview tab:" label when choosing different fonts. Could it be avoided?

I'm guessing it's the preview font changing? How would you suggest avoiding it?

🐙 This pull request conflicts with the target branch and needs rebase.

There hasn't been much activity lately and the patch still needs rebase. What is the status here?

Is it still relevant? ➡ Please solve the conflicts to make it ready for review and to ensure the CI passes.
Is it no longer relevant? ➡ Please close.
Did the author lose interest or time to work on this? ➡ Please close it and mark it 'Up for grabs' with the label, so that it can be picked up in the future.

Closing this due to lack of activity. Feel free to reopen.

Rebased

🤔 There hasn't been much activity lately and the CI seems to be failing.
If no one reviewed the current pull request by commit hash, a rebase can be considered. While the CI failure may be a false positive, the CI hasn't been running for some time, so there may be a real issue hiding as well. A rebase triggers the latest CI and makes sure that no silent merge conflicts have snuck in.


LESQ-216 feat(quizzes): put quizzes inside new lesson item container

Description
put quizzes inside lesson item container
Issue(s)
Fixes #
How to test

Go to https://deploy-preview-1792--oak-web-application.netlify.thenational.academy/beta/teachers/programmes/french-primary-ks2/units/je-decris-un-monstre-8348/lessons/describing-parts-of-the-head-and-face-with-colours-and-sizes-6gv3jd
Click on starter and exit quiz
You should see new styled quizzes

Screenshots
How it used to look (delete if n/a):
{screenshots}
How it should now look:
{screenshots}
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner

:tada: This PR is included in version 1.220.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add network test vectors

The purpose of this PR is to ensure that our ReqResp code behaves exactly the same from version to version. Current unit tests only assert that the current encoder works with the current decoder, but doesn't guarantee correctness. This PR leverages the fact that our current code has been widely tested and interop-ed so it's treated as correct. I'm adding this now to safely incorporate my upcoming ReqResp code re-org.
Tests are structured resembling the eth2 spec tests, but are generated with our own code. Include three directories

network/spec-test/format: write test vectors to FS, parse FS to test vectors logic
network/spec-test/generate: create test vectors and store to FS. Should be run rarely run, i.e. when the spec changes and we are confident our code interops
network/spec-test/run: read test vectors from FS and run them
network/spec-test/vectors: test vectors

Currently this PR only includes tests for decoding a response given a stream of bytes. I will extend to response encoding, request encoding / decoding and errors if this structure is good with other repo mantainers

Superseded by https://github.com/ChainSafe/lodestar/pull/1930
Above PR includes serialized payloads for Ping, Status and SignedBeaconBlock for ssz_snappy, captured in current master.

Superseded by https://github.com/ChainSafe/lodestar/pull/1930
Above PR includes serialized payloads for Ping, Status and SignedBeaconBlock for ssz_snappy, captured in current master.


Issue with speech api

Hi team,
We are using require('@google-cloud/speech').v1p1beta1 to convert our audio file.
But we are getting errors frequently on calling client.recognize().
Below are the errors we are getting.

Timeout error
Sync input too long. For audio longer than 1 min use LongRunningRecognize with a 'uri' parameter

In the first case if we try again with the same voice file it will work.
Can some one pls let us know why it returns timeout error so frequently.
Below are the config we are using.
const config1 = {
encoding: 'FLAC',
sampleRateHertz: 16000,
languageCode: 'en-GB',
alternativeLanguageCodes: ['ar-AE', 'ar-SA', 'th-TH'],
};

👋 @anjaly there's been a known issue with grpc that causes users to see an increase in timeouts, I suspect you may be seeing that. Could you verify what version of @grpc/grpc-js is installed in your project?
For an immediate workaround I would suggest trying one of the following

Manually updating to 0.6.9$ npm i<EMAIL_ADDRESS>--save

Using the C++ extension$ npm i grpc --save

Then you can require the installed package and pass it directly to the speech constructor.
const grpc = require('grpc'); // or @grpc/grpc-js
const client = new speech.SpeechClient({grpc});

Hi @callmehiphop, can u please help me in finding grpc in my code. Below is what we are having in our code now.
const speech = require('@google-cloud/speech').v1p1beta1;
const client = new speech.SpeechClient({
projectId: config.api.PROECT_ID,
keyFilename: config.api.FILENAME
});
How should we modify this?

@amtdevops let me know if the following helps
const grpc = require('grpc');
const speech = require('@google-cloud/speech').v1p1beta1;
const client = new speech.SpeechClient({
  projectId: config.api.PROECT_ID,
  keyFilename: config.api.FILENAME,
  grpc: grpc
});

Checking in -- it seems like this response from @callmehiphop  answered the question, so I'm going to go ahead and close this. Please reopen if needed. Thanks!


[DATE]: OSCSA/MOOCs landing page

@BatoolMM @alswajiab i would be working on the landing page of the MOOC in this issue, the landing page would consist of

navigation bar
hero section
testimonial section
recommended videos section
recommended learning material section
benefits of the platform
footer

ALl these would be built with Vue.js and bootstrap

@jesutobi   We decided to use React and plain CSS for the App

@jesutobi We decided to use React and plain CSS for the App

The intro into this task by the mentors didnt state a particular framework

@jesutobi We decided to use React and plain CSS for the App

did the mentors mandate this

@jesutobi
we formed a team to work on it and we have decided to use React.
If you decide to work with the Team (dev_team2) then you'll have to use React.
If you want to build the App alone or maybe form another team then you are free to use whichever technology you like.
Let me know if you need more clarification

@jesutobi we formed a team to work on it and we have decided to use React. If you decide to work with the Team (dev_team2) then you'll have to use React.
If you want to build the App alone or maybe form another team then you are free to use whichever technology you like.
Let me know if you need more clarification

okay , thanks

@jesutobi alright

@okerekechinweotito I know how to use react, I'd like to join the team

@adetyaz  Welcome ! Pick a task from #10  and make a PR.

@okerekechinweotito thanks


Replace ConfVars.HIVE_SERVER2_WEBUI_PORT with its equivalent string

Fixes #11

Coverage remained the same at 88.82% when pulling 6989e608ccf05b0b6178e58b30f3d05af0780270 on issue-11 into bda20bed01c9331f5795e69182b29a5d5ffdd3f1 on master.

Update changelog please

Coverage remained the same at 88.82% when pulling 2f2e0b44917d7449129d8b5175c2bfcf1cbeb122 on issue-11 into bda20bed01c9331f5795e69182b29a5d5ffdd3f1 on master.


ADO Data Loss during Service Outage/ failover?

Hi
The Page explains all the details about the data availability and data redundancy, etc. But there is no explicit mention about the data loss in case of service outage.
There is a statement on the page about ensuring the data availability, but the data loss during the failover scenarios are not answered explicitly
"Azure DevOps uses many Azure Storage features to ensure data availability if there's a hardware failure, service disruption, or region disaster. "
There are questions raised from customers about data loss during the service outage/ failover. Is it possible to include that information on the page to clarify the data loss scenarios?
Thanks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 52eb9f91-b952-afb6-6d17-d7092f46440d
Version Independent ID: bb9113a5-8b8b-b20b-9c6f-09a57f53ba7c
Content: Data protection overview - Azure DevOps Services
Content Source: docs/organizations/security/data-protection.md
Product: devops
Technology: devops-security
GitHub Login: @chcomley
Microsoft Alias: chcomley

@vijayanand-msft -- thank you for feedback and questions.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@chcomley -- please look into this issue.

Hi @vijayanand-msft, per our email conversation, closing this issue, as you confirmed that you have the answers you need. The documentation won't be updated, as its purpose is high-level.  Thank you!


Updating rubocop

Rubocop recently reached the first stable version 1.0 and they have
assured the community they'll follow semantic versioning from now on.
As of today, v1.2 has been released. This PR introduces support via the
gemspec up to that version and enables all new cops by default when
using the edge configuration.

Looking good!


✨ [Feature Request / Suggestion]:  Adding Additional Video Stock Footage API's

Suggestion / Feature Request
Adding Additional Video Stock Footage API's
Pixabay
https://pixabay.com/service/about/api/
VideoEvo
https://www.videvo.net/a/videvo-api/
Videovo
https://www.videvo.net/stock-video-footage/apis/
Coverr
https://coverr.co/developers
These are all free API access etc.
Why would this be useful?
If one stock footage site doesn't provide correct content, we can select another
Screenshots/Assets/Relevant links
No response

Added to the task list:
https://github.com/users/RayVentura/projects/1/views/1

@Peteinoz Good luck finding stock footage that's not people walking around or food. It's so simple just use YouTube and Clip2


Errors when trying to run simplest possible project

I've made the simplest possible test project using Love2D:
function love.draw()
    love.graphics.setColor(1, 0, 0, 1)
    love.graphics.rectangle('fill', 20, 20, 30, 30)
end

This (obviously) works with a standalone player, but it's not working at all when I try to run it with love-js. The build process works just fine. The script (main.lua) is in a folder by itself, called love-test. I run the command like this:
love-js love-test love-test-game

and then serve it like this:
cd love-test-game
python -m http.server 8000

and the page loads with the Love2d logo and everything, but the game doesn't load at all -- there's just a message box that says "An error occurred before the game window could be initialised. Please check the console!"
These are the errors in the console:

Other things I've tried, in various combinations, only to have the exact same error:

Building in compatibility mode
Building from a .love archive instead of the folder itself
Building the spec tests from this repo, instead of my simple test

... and the same thing always happens.
Any ideas what I'm doing wrong here? Or maybe you could point me in the right direction for how to begin debugging, or at least providing more information?

That also doesn't work. I've tried that with zipping it up both from the Windows default zip mechanism from windows explorer, and with 7-zip, and same error every time.
However! When I use the Linux Subsystem for Windows to both zip up the LOVE archive and call love.js, it works!

That also doesn't work. I've tried that with zipping it up both from the Windows default zip mechanism from windows explorer, and with 7-zip, and same error every time.
However! When I use the Linux Subsystem for Windows to both zip up the LOVE archive and call love.js, it works!

But, then I get the same error when trying to build an actual game rather than just a super simple example. I'm guessing there's some logging we should have that isn't happening. I'll try building from source myself and see if I can figure out what's wrong here

But, then I get the same error when trying to build an actual game rather than just a super simple example. I'm guessing there's some logging we should have that isn't happening. I'll try building from source myself and see if I can figure out what's wrong here


typo: Double word "in"

Docs Build status updates of commit 4c67447:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/patterns/category/management-monitoring.md
:white_check_mark:Succeeded
View

docs/patterns/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Microsoft.PowerToys version 0.29.3

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate <manifest>, where <manifest> is the name of the manifest you're submitting?
[ ] Have you tested your manifest locally with winget install -m <manifest>?

Microsoft Reviewers: Open in CodeFlow

This can be deleted.  This was a test

This can be deleted.  This was a test


Why custom validation errors are embedded in a HTTPError ?

I have a custom validator that parses the JSON response and tries to build an Error struct.
If it builds the error successfully, my validator will return with a .failChain(responseError), but in my catch at the call site, the error is still embedded into a HTTPError, which makes the catch a bit convoluted:
import RealHTTP
import MyService

do {
  let result = try await service.callSomeEndpoint()
} catch let httpError as HTTPError {
  if let responseError = httpError.error as? ResponseError {
    // handle my custom response error here
  } else {
    // handle the http error?
  }
} catch {
  //
}

Question: what's your rationale behind automatically nesting the validator custom errors in a HTTPError ?
I would probably prefer to have 2 dedicated catches:
} catch let responseError as ResponseError {
  ...
} catch let httpError as HTTPError {
  ...
}

So I can ignore the HTTPError and fallback to a generic catch if I'd like to.. and I could also avoid leaking the RealHTTP implementation/imports in all my services ;)

Hi, I agree with your point. Would you make a PR to support this enhancement

@malcommac ok, I'll try to find the time for that in a near future


Running Airflow locally with DataHub, init fail

Describe the bug
initialize airflow fail
To Reproduce
Steps to reproduce the behavior:
https://datahubproject.io/docs/docker/airflow/local_airflow
Expected behavior
airflow-init_1       | Admin user airflow created
airflow-init_1       | 2.1.3
airflow_install_airflow-init_1 exited with code 0

Hi，Is there a solution

Can you please share details of your system where you are running? Have you made any changes in the docker compose files? Have you given sufficient memory to Docker as per prerequisites?

Hi @zsdyx
Is this still an issue? if not, will close it after a few days of inactivity.


Include the version number within the library

It would be nice to know which version of the toolbar is currently installed, exactly as in Flask..
Just include the __version__ = '0.8.0' in the __init__.py for the stable releases and use something like __version__ = '0.9.0-dev'for the master branch!
It would be also good idea to include that number inside the VersionDebugPanel so you will know which version of the toolbar is currently running.

Pull requests welcome

Having looked at this deeper, I would prefer to access the version using pkg_resources.get_distribution('Flask-DebugToolbar').version. I would prefer to avoid adding a __version__ inside of __init__.py as so far I haven't seen a compelling reason to add the additional complexity.
It does seem like a good idea to expose in the UI which version of the toolbar is currently running.

it won't work on Google App Engine.. can't find right now another library that went this way and then switched back to the hardcoded version.. :/

What won't work inside of Google App Engine?
Accessing pkg_resources or not having a __version__ inside of init.py?
Are there GAE docs explaining this?

Use `importlib.metadata.version("package-name") to get the version in a standard way for any installed package.


Allure Reports for Bamboo - Cannot allocate memory

Hi,
We have a problem with generating allure reports. Sometimes reports are generated and sometimes the same reports are not generated because of out of memory problem.
It’s always the same error:
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000600000000,<PHONE_NUMBER>, 0) failed; error='Cannot allocate memory' (errno=12)
It’s strange because available free memory is often about 2GB and one time reports are generated with success and another time without success. Error shows that needed about 5GB memory.
If we increase RAM, the problem will disappear, or not? We can’t increasing RAM with every Allure error about memory.
What we can do? How much RAM should be reserved for allure reports plugin?
Please support.
Regards,
Wiola

@wiolken44 when is this happening? Where exactly do you see the OOM error?

Hi,
OOM error is in Allure Report tab:

Reports are generated mainly with success, but sometimes the same report does not generate and is with an OOM error, but we do not know why.

Increase RAM on server solved our same problem.
We waas change RAM from 24 to 32 GB

We're running into this same issue as well. Although our Bamboo instance size already pretty large at a c5.9xlarge (36 CPU & 72 GB Memory). We can't really go up any higher.
Caused by: org.buildobjects.process.ExternalProcessFailureException: External process '/bin/bash /v*********n/allure generate -o /var/vcap/packages/atlassian-bamboo/atlassian-bamboo-standalone/temp/1569865667710-1/report /v*********o/atlassian-bamboo-standalone/temp/1569865667710-0/31dbf336-d8e8-4f0e-9047-6d049f4c5f5f' returned 1 after 235ms
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000080000000,<PHONE_NUMBER>0, 0) failed; error='Cannot allocate memory' (errno=12)

Hello, we are facing the same issue on the Bamboo.
Our Bamboo team has tried several options, but that didn't help:
"We already have maxed out settings with the build agents resource and JVM settings wise and this is due to a bug on the vendor side with a plugin that appears to have been abandoned."
"Just to clarify, the memory issue is not with Bamboo itself, and instead relates to the Allure-developed plugin.  This is the challenge because Bamboo issues would be something our team could theoretically take action on - but because this is a plugin developed by an external vendor, we are limited in terms of what we are able to do here. "
Could you please take a look?

I know this issue is super old, but I just hit it today. The problem is that the Allure plug-in re-uses the jvm options set in Bamboo's setenv.sh. So unless you have enough un-allocated memory equal to your app, you'll get this error when the report tries to generate.

closed as stale


Add YangMingShan to UI category

Project URL

https://github.com/yahoo/YangMingShan
Description

YangMingShan is a collection of iOS UI components that we created while building Yahoo apps. The reason we open source it is to share useful and common components with the community.
Checklist

[x] Only one project is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Travis CI pass
[x] Supports iOS 7 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Thank you for contributing to awesome-ios 😄


particular json secret failing to parse

We are attempting to migrate our github ci from using https://github.com/marketplace/actions/aws-secrets-manager-action to this action.
However we are finding for a particular secret it is failing to parse and we are unsure why.
env:
  CI: true
  ACTIONS_RUNNER_DEBUG: true

...

    - name: Configure AWS Credentials
      uses: aws-actions/configure-aws-credentials@v2
      with:
        aws-region: us-east-2
    - name: Read AWS Secret Manager
      uses: aws-actions/aws-secretsmanager-get-secrets@v1
      with:
        secret-ids: |
          prod-elastic
          prod-rds
        parse-json-secrets: true
...

    - name: deploy
      working-directory: example-lambda
      run: |
        npm i -g serverless
        npm install
        serverless config credentials --provider aws --key $AWS_ACCESS_KEY_ID --secret $AWS_SECRET_ACCESS_KEY
        sls deploy --stage production
      env:
        DATABASE_HOST: ${{ env.PROD_RDS_MASTER_HOST }}
        DATABASE_USERNAME: ${{ env.PROD_RDS_MYSQL_USERNAME }}
        DATABASE_PASSWORD: ${{ env.PROD_RDS_MYSQL_PASSWORD }}
        DATABASE_NAME: ${{ env.PROD_RDS_DATABASE_NAME }}
        FUNCTIONBEAT_SUBSCRIPTION_STREAM: ${{ env.PROD_ELASTIC_FUNCTIONBEAT_SUBSCRIPTION_STREAM }}
        FUNCTIONBEAT_SUBSCRIPTION_ROLE: ${{ env.PROD_ELASTIC_FUNCTIONBEAT_SUBSCRIPTION_ROLE }}

prod-rds successfully parses.
however prod-elastic fails to parse. Why is this happening
content of secret:

note: the previous action we have been using successfully parses this secret (prod-elastic)
Attempted to enable debugging ACTIONS_RUNNER_DEBUG however we don't see any extra information displayed in the step.

@kaykhan What was your solution here?

@kaykhan What was your solution here?

Hey can't remember specifically what the problem was here but we do have this working. Here is an example
env:
  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
  AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
  AWS_REGION: us-east-2

  deploy:
    needs: unit-test
    name: deploy
    if: startsWith(github.ref, 'refs/tags/')
    environment: production
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@master
      - uses: actions/setup-node@v3
        with:
          node-version: "16.x"
      - name: Configure AWS Credentials
        uses: aws-actions/configure-aws-credentials@v2
        with:
          aws-region: us-east-2
      - name: Read AWS Secret Manager
        uses: aws-actions/aws-secretsmanager-get-secrets@v1
        with:
          secret-ids: |
            prod-rds
            prod-elastic
          parse-json-secrets: true
      - name: deploy
        run: |
          npm i -g serverless
          npm install
          serverless config credentials --provider aws --key $AWS_ACCESS_KEY_ID --secret $AWS_SECRET_ACCESS_KEY
          sls deploy --stage production
        env:
          DATABASE_HOST: ${{ env.PROD_RDS_MASTER_HOST }}
          DATABASE_USERNAME: ${{ env.PROD_RDS_MYSQL_SOME_USERNAME }}
          DATABASE_PASSWORD: ${{ env.PROD_RDS_MYSQL_SOME_PASSWORD }}
          DATABASE_NAME: ${{ env.PROD_RDS_DATABASE_NAME }}

I think in the past we had some issues with this env var/val CI: true if you have that try removing it. Other than that i dont know.


Throttle Probe Tool Calculations

Description
Adding more than ~5 probes makes the canvas unresponsive.
This does not happen when adding more than 20 freehand object (containing more than 100 points).
Steps to Reproduce

Add 5 probe points.
Panning and zooming becomes slow.

Expected behavior:
Have a smooth experience.
Actual behavior:
Slow and sluggish canvas tool.
Codepen With Reproduction of Issue:
cornerstone.enable(element);
cornerstoneTools.mouseInput.enable(element);
cornerstone.loadImage(imageId).then(function(image) {
cornerstone.displayImage(element, image);
cornerstoneTools.probe.activate(element, 1);
cornerstoneTools.probe.enable(element);
}

This is likely do to how the tool determines when it should recalculate values. Newer methods throttle the calculation, and/or only update the value if the previous value becomes invalid.
More than happy to review a PR for this fix. The vNext branch would likely need it as well

@dannyrb Could you review #698?

@hsahin , I believe this is a common problem for any tool that looks at pixel values. I've updated the issue and added labels to address the core issue here. While I will look at a fix for the master branch, I would prefer to see the work done in vNext to reduce the effort required to port changes.

@evren217 was this addressed in your recent changes? I think we're throttling all annotation tool recalculations now.

That is correct. We can close this issue.


fix(config): fix the config template

Config template must use the actual redis settings

Coverage remained the same at 93.785% when pulling 39999aacfaf2a5dc9439dd70bcdfda293fbde461 on thetutlage-patch-1 into 17959ccec2d96283b741404cd6826f8f50bb6bd7 on develop.

Coverage remained the same at 93.785% when pulling 39999aacfaf2a5dc9439dd70bcdfda293fbde461 on thetutlage-patch-1 into 17959ccec2d96283b741404cd6826f8f50bb6bd7 on develop.


Swedish translation

This PR is to add Swedish as a language option, as requested in Issue #60.
There's one thing that needs to be fixed though, and one to be discussed:

The letters Ä, Å and å can't be displayed, they only result in a white space. I've added these to resources/fonts/full/subset_characters.txt, but the issue persists, so I'm not sure what the cause is. Is there a certain order in which they need to be placed? Because now, I've put them in arbitrary locations in subset_characters.txt.
I started out by creating a 4th column for Swedish in the language selection page, but it became a bit cramped with 4 columns, so I went with adding it to the 1st column. Does this, and the placement, seem alright with you?

I've also made (what seems to me to be) some small corrections of other texts.

Hi @vcrn thank you very much.
For point 1): don't worry, I'll fix it personally. (It's also necessary to include those letters in the font file but I use a program to do it, so don't worry of doing it yourself).
For point 2): I'll fix it as well!

Update:

added missing characters to the font files
restructured language selection page
renamed Swedish language code to SV (SE is the code for Sweden, the country)

If you confirm everything looks good to you as well, I'll proceed merging

Great, I'll check it out today or tomorrow!

The library I use for the GUI has a very basic text handling as of today so I don't think it supports a similar feature.
After having played a bit with the relative widths of the filter columns I have come up with sizes that correctly display all the columns title in one line without cuts, in all the currently available languages.
Thank you very much for having pointed out the problem (I noticed it happened for Korean as well).
Confirm everything's good when you can.
PS: you didn't forget the Å actually, I removed it by edited that file by grepping all the used characters in the src folder.

Great, now it looks good in full-screen on both laptop screens!

@all-contributors please add @vcrn for translation.

@all-contributors please add @vcrn for translation.

Thanks, appreciate it!
I'll see if there's something else I can help out with. Right now I'm looking into what makes one of my laptops running Manjaro able to display the flag-icons using wgpu, while my laptop that runs Arch can only do it using glow. Will see if it's due to hardware or some missing dependency

Thanks, appreciate it!
I'll see if there's something else I can help out with. Right now I'm looking into what makes one of my laptops running Manjaro able to display the flag-icons using wgpu, while my laptop that runs Arch can only do it using glow. Will see if it's due to hardware or some missing dependency

I must be thanking you man!
I think that problem is "normal", Iced documented it a lot and suggests to use glow in case of problems.
However, they are introducing a new software renderer that should be "universal" (but someone already reported on their Discord that in some cases this bug happens as well)

I must be thanking you man! I think that problem is "normal", Iced documented it a lot and suggests to use glow in case of problems. However, they are introducing a new software renderer that should be "universal" (but someone already reported on their Discord that in some cases this bug happens as well)

Cool, I'll check it out!
In case it's of any interest, my laptop that could display the icons while running Manjaro can still display them after a fresh install of Arch, so it seems like it's something on the hardware level that is making my other Arch laptop unable to display them.

Yep, absolutely.
I forgot to mention that this problem usually has to do with the graphical card / adapter of the machine.


skopeo should be able to return be the catalog from a docker-distribution based registry.

A User want to build tooling to keep multiple container registries in sync using skopeo.
In order to script this he needs to have a list of all container images at the source registry.  This is stored as a catalog and should be able to be retrieved using skope catalog command.
Add a new command catalog, which will bring back the entire registry catalog file in json format.
skopeo catalog docker:registry.access.redhat.com
Should output the catalog to stdout.

/cc @mtrmac

This is necessary but not sufficient for full sync because it only lists repositories, not images in these repositories.  We would also need https://github.com/projectatomic/skopeo/issues/276 to list tags, and I don’t think there is any way to list untagged images (which are still accessible using the @digest notation).

If this is supposed to be a generic command, we need to think about what the transport-independent semantics is (e.g. “what should skopeo catalog dir:/usr output?”). Perhaps we can avoid that and make a docker-specific hack for now, skopeo docker-datalog $hostname or something like that.

back to
curl -su $DOCKER_USERNAME:$DOCKER_PASSWORD https://$DOCKER_REGISTRY/v2/_catalog | jq .
curl -su $DOCKER_USERNAME:$DOCKER_PASSWORD https://$DOCKER_REGISTRY/v2/$IMAGE_NAME/tags/list | jq .

or in a single line (generate array of all images with their tags) using curl,xargs and jq:
curl -su $DOCKER_USERNAME:$DOCKER_PASSWORD https://$DOCKER_REGISTRY/v2/_catalog | jq -r .repositories[] | xargs -I'{}' curl -su $DOCKER_USERNAME:$DOCKER_PASSWORD https://$DOCKER_REGISTRY/v2/{}/tags/list | jq --slurp .

@mtrmac @vrothberg Is this something we should pursue?  Should we look at interns working on this?  Do you think it is important?

I am taking a shot and close it in favor of the skopeo-sync PR https://github.com/containers/skopeo/pull/524.

skopeo sync won’t use the catalog to list all repositories.
The existing podman search can be used for this, e.g. podman search registry.fedoraproject.org/ (but that registry reasonably limits the number of results, so it is only marginally useful.)
Considering that a sane registry server rarely support returning the full catalog, and that none of this can deal with untagged images, yes, let’s close.


Typed throws

Parsing of typed throw specifiers. See https://github.com/apple/swift/pull/68629 for more information.

All of this should be behind an experimental language feature.

Great point, and it was super-easy to do. Thanks!

https://github.com/apple/swift/pull/68629
@swift-ci please test

https://github.com/apple/swift/pull/68629
@swift-ci please test

https://github.com/apple/swift/pull/68629
@swift-ci please test Windows

https://github.com/apple/swift/pull/68629
@swift-ci please test

https://github.com/apple/swift/pull/68629
@swift-ci please test

https://github.com/apple/swift/pull/68629
@swift-ci please test

https://github.com/apple/swift/pull/68629
@swift-ci please test Windows

https://github.com/apple/swift/pull/68629
@swift-ci please test

https://github.com/apple/swift/pull/68629
@swift-ci please test Windows

https://github.com/apple/swift/pull/68629
@swift-ci please test Linux

I’ve got a couple more comments in-line. On a higher level, the following still needs to be done.

The following should be SPI

The ThrownTypeClauseSyntax type
SyntaxAnyVisitor.visit(ThrownTypeClauseSyntax)
SyntaxAnyVisitor.visitPost(ThrownTypeClauseSyntax)
SyntaxEnum.thrownTypeClause
SyntaxKind.thrownTypeClause
SyntaxRewriter.visit(ThrownTypeClauseSyntax)
SyntaxVisitor.visit(ThrownTypeClauseSyntax)
SyntaxVisitor.visitPost(ThrownTypeClauseSyntax)
The initializers of AccessorEffectSpecifiersSyntax etc. that take ThrownTypeClauseSyntax
unexpectedBetweenThrowsSpecifierAndThrownError and unexpectedAfterThrownError

Provide unexpectedAfterThrowsSpecifier that concatenates unexpectedBetweenThrowsSpecifierAndThrownError, thrownError, and unexpectedAfterThrownError
Ensure that all the expression tests like [() try(MyError) async -> Void]() don’t parse once #2255 is fixed

We just discussed the design of the syntax tree and I think the tree should be structured as follows:

The effect specifier nodes contain a throwsClasue: ThrowsClauseSyntax child, instead of throwsSpecifier and thrownType
The ThrowsClauseSyntax has 4 children

throwsSpecifier: TokenSyntax (which can be either throws or rethrows)
leftParent: TokenSyntax?
thrownType: TypeSyntax?
rightParen: TokenSyntax?


[RouterConfigControllerTest] use alternative method withValueFromSecret

Type of change

Bugfix

Description
Fixes odd compile error appearing on some CI environments.
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@kornys I don't understand why this issue appears on the Jenkins CI environment only.   I was unable to find the root cause.   This test code is equivalent.


Bump types-python-dateutil from <IP_ADDRESS> to <IP_ADDRESS> (#5656)

Pull request opened by the merge tool on behalf of #5656

Merged in 7d4de17f07985a8d75e63fbb2be3f28f13c3d150