Add rvm .ruby-env equivalent for rbenv (.rbenv-vars) to .gitignore

For those of us who prefer the rbenv way!

@anthonylebrun the env file is auto generated via: https://github.com/on-site/StockAid/blob/master/lib/environment_setup.rb
Do you want to update that script to generate the rbenv file as well, or are you fine just managing the file yourself?

I don't think this is going to affect very many people at this point, so I'm happy to manage that file myself.


[wip] try sleeping until echo is ready

Hint to save some time: You can create a draft PR and manually run only the integration tests


How to add a page count at the bottom of Page

Hi, I was trying to add a page count at the bottom of the page, as the other implementation of fpdf works, by using pdf.SetY(-15) and therefore adding a cell.
But a new page is added and the {nb} is not interpolated.
package main

import (
	"fmt"

	"github.com/go-pdf/fpdf"
)

func main() {
	pdf := fpdf.New("P", "mm", "A4", "")
	tr := pdf.UnicodeTranslatorFromDescriptor("")
	pdf.AddPage()
	pdf.SetFont("Arial", "B", 16)
	pdf.Cell(40, 10, tr("Olá, mundo"))
	pdf.SetY(-15)
	pdf.SetFont("Arial", "I", 8)
	pageNum := fmt.Sprintf("%d/{nb}", pdf.PageNo())
	pdf.CellFormat(0, 10, pageNum, "", 0, "C", false, 0, "")
	err := pdf.OutputFileAndClose("hello.pdf")
	if err != nil {
		panic(err.Error())
	}
}

To interpolate {nb} had to force by using pdf.AliasNbPages("{nb}"), but even though another page was added.

See the example of AddPage that uses SetFooterFunc :
https://pkg.go.dev/github.com/go-pdf/fpdf#example-Fpdf.AddPage
(feel free to reopen if that didn't help)


54 cap policy exclusions

Updated AAD Policies 2.1, 2.2, 2.3, 2.4, 2.9, & 2.10 to check for conditional access policy exclusions to users and groups.  Roles will not allow exclusions at this time.
🗣 Description
If the conditional access policies contain user or group exclusions, the baseline policy will fail.  This change is the first step towards adding the capability for users to define allowable exclusions to these policies. Most agencies will want to include some exclusions  to these policies. Therefore, the automation script should be enhanced to allow for these exclusions.

💭 Motivation and context
AzureAD uses conditional access policies to evaluate access requests. These policies may include references to existing users, groups, and roles with both an inclusion and exclusion condition. Currently, the conditional access policies assume that all users, groups, and roles should  to meet the policy baselines.

🧪 Testing
I tested the changes using the AAD Rego unit tests. Reviewers can run the AAD unit tests for each policy baseline statement. Some issues I ran into included not having all the necessary Rego policies defined in the AADConfig.rego, e.g.,
"All" in Cap.Conditions.Users.IncludeGroups
"All" in Cap.Conditions.Users.IncludeRoles
The changes include an update to how the Orchestrator processes the configuration file to include it in the provider export as well as changes to the AAD Rego provider code and unit tests.  Test using variations of the new sample aad-config.yaml test file to ensure proper results for AAD 2.1, 2.2.1, 2.3, 2.4.1, 2.9, & 2.10 with variations of exclusions, both user and group, with and without exemptions in the configuration file.  The most common execution scheme will be running Invoke-Scuba -ConfigFilePath sample-config-files\aad-config.yaml while changing the configuration file to elicit the expected results.  Careful when making changes to tenant conditional access policies in testing as it is possible to lock yourself and others out when changing block rules.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] Tests have been added and/or modified to cover the changes in this PR.
[x] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Add a tag or create a release.

merge tests passed (note that there are additional policy failures on a given tenant but these new fails are consistent with implemented cap exclusions) -> merging into the main.


Upgrade to cats 2.0.0 and monix 3.0.0

I have not been able to fully figure out how the build process works, but here is my first stab at this.
Is .settings(commonJvmJsSettings) the right set of settings?

Looks good, thanks! :)

Yeah the build can be confusing, but that's what you end up with supporting a mixture of jvm/js/native and 2.11/2.12/2.13 :)
As monix now supports 2.13, it's enough to just drop that line


Add protocol to URLs embedded in help text

Having recognizable URLs inside the help text helps humans and terminal (auto-highlighting) tooling alike
Signed-off-by: Stefan Hoffmeister<EMAIL_ADDRESS>

Before this patch, I was actually thinking that there were stray pixels in the help text.


Why do we need to use the ALB for any load balancer?

In all the diagrams for internal or external LB, I see the Azure LB. I'm working with a customer that wants all ALB out of their solution. Is this possible if they are going to use NGinx etc.?

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

ID: a38439d0-0125-3445-1c0a-a03b940e315d
Version Independent ID: c6436a35-94b9-6396-3b13-9291f0a17b21
Content: Restrict egress traffic in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/limit-egress-traffic.md
Service: container-service
GitHub Login: @palma21
Microsoft Alias: jpalma

@larrywa Thank you for sharing your query! We are currently investigating and will get back to you shortly on this.

They are using nginx where? inside of the cluster?
if yes how are they expose nginx outside of the cluster?
If no, can you clarify?

They are using Nginx inside the cluster, they are not exposing it outside the cluster, all ILB.
Any routing to do TO the internet, they want to do it own their own.
My point was it seems that every concept that Microsoft has, includes access from the internet, when in fact, a private cluster should be completely private from the outside.
Thanks!
larrywa
From: Jorge Palma<EMAIL_ADDRESS>Sent: Friday, August 28, 2020 2:06 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Larry Wall (AZURE DEV<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Why do we need to use the ALB for any load balancer? (#61637)
They are using nginx where? inside of the cluster?
if yes how are they expose nginx outside of the cluster?
If no, can you clarify?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F61637%23issuecomment-682344064&data=02|01|Larry.Wall%40microsoft.com|fa8bf1fb95814b97db4e08d84b187567|72f988bf86f141af91ab2d7cd011db47|1|0|637341915770079819&sdata=zzZ%2BpRry8oGiaGcx7uZ7DFIb3Z8BQLkvW8HtsYjfruk%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA27FWXLEV7DIIEFZVTAOK3SC5CNDANCNFSM4QNBTY5A&data=02|01|Larry.Wall%40microsoft.com|fa8bf1fb95814b97db4e08d84b187567|72f988bf86f141af91ab2d7cd011db47|1|0|637341915770089817&sdata=WdUWu%2FP%2FUN2pailYG6qMHKOo5mPQDEG6FVFA10vBQSs%3D&reserved=0.

@larrywa As per our discussion I will now go ahead and close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.
Thanks


Fix new issue/pull request btn margin when it is next to sort

Close #23627
Added margin left to the button when it is next to the svg, which has a margin-right of -0.5rem
And here it might be better if white-space: nowrap; is added because otherwise it might look like below on pull requests page on smaller screen

After:

Pull Request on smaller screen

ping lg-tm


Xinting voting

Implemented

cli: qnode-score (feature: qnode_score)
cli: feature-voting

Also, for any new command, please add the relevant entry in the REAME.md.
And pull requests go into the development branch

need to rebase on dev branch :(

need to rebase on dev branch :(

no, just pull from usc-isi-i2:development and create a new pull request

Hey @saggu I think Ke-Thia's changes (external_embedding) is not in development which my work (voting) relies on. I can cherry pick my changes on top of dev but that won't be too useful without the embedding computation code 😔


Implement benchmark for Apply()/ReadRow() latency.

This fixes #189. Implements a benchmark to measure the latency
of Table::Apply() and Table::ReadRow() using either production
Cloud Bigtable, the Cloud Bigtable Emulator, or an embedded server.

Ping.  Can somebody review please?

Thanks, do you mind clicking on the "approve" button?


Add OLM deployment CI coverage

Add CI for deploying Submariner via submariner-operator via OLM. This would replicate the experience of a user finding Submariner on OperatorHub, or the community-operators CI.
https://dev.operatorhub.io/operator/submariner
https://github.com/operator-framework/community-operators/pull/1677/checks?check_run_id=648885925

Maybe this is actually how to get at the idea: https://github.com/operator-framework/community-operators/blob/master/docs/using-scripts.md

That’s what I’d based my patch to install OLM on.

https://github.com/submariner-io/submariner/pull/134

submariner-io/submariner#134

Ah, nice, I had forgotten about that one! You're a few steps ahead of me as always. :wink: So it seems we need to do something like what you have there in Shipyard now?

There are two parts to the issue:

deploying OLM & co in our test K8s clusters (this is what submariner-io/submariner/#134 does, and what needs to be replicated in Shipyard)
using OLM to deploy Submariner

The latter should IMO be done in subctl (because the goal is to use OLM when deploying on OpenShift, in all cases), but whether done directly in CI or in subctl, there are some subtleties involved. We can’t use the operator CSV from OperatorHub because we want to deploy the Submariner components that CI needs to test, not those available on Quay and referred to by the current OperatorHub CSV.

There are two parts to the issue:

deploying OLM & co in our test K8s clusters (this is what submariner-io/submariner/#134 does, and what needs to be replicated in Shipyard)
using OLM to deploy Submariner

The latter should IMO be done in subctl (because the goal is to use OLM when deploying on OpenShift, in all cases), but whether done directly in CI or in subctl, there are some subtleties involved. We can’t use the operator CSV from OperatorHub because we want to deploy the Submariner components that CI needs to test, not those available on Quay and referred to by the current OperatorHub CSV.

Makes sense, I stumble into this the other day:
https://github.com/che-incubator/chectl#chectl-serverstart
I don't mean we need to take the chectl things as a reference, I have't analyzed them in terms of usability, but .. they do support operator or olm... (even helm). I think we should "auto" by default, and use olm with priority if that's available.

@skitt @mangelajo do either of you guys have a suggestion for how to properly depend on the released CRDs/other resources that comprise OLM? I'm messing with a patch to subctl, but I'm a bit stuck trying to figure out the right way to do pull in their artifacts that can be easily maintained/updated in Go.
I'd basically like to do:
kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.14.1/crds.yaml --validate=false

using utils.CreateOrUpdateCRD
and
kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.14.1/olm.yaml

without duplicating all of those definitions in Go, ie not paralleling https://github.com/submariner-io/submariner-operator/blob/master/pkg/subctl/operator/submarinerop/serviceaccount/ensure.go.

@dfarrell07 why do you want to deploy OLM from subctl?

@skitt I saw your point about OLM via Shipyard, but it seemed like it should be pretty straightforward from subctl, for a released version at least. Just parallel CRD/resource creations to what we already do. And it seemed like it would make sense from a UX sandpoint, to have the ability to install OLM and then the operator via OLM all via subctl.
But I guess this shows it's not as easy as I imagined and it should just be deployed via Shipyard.

@dfarrell07 what I mean is that OLM is a means to an end, not an end to itself. I think subctl should be able to use OLM to install the operator, if OLM is already present. I don’t think subctl should install OLM itself to install the operator.

@skitt the first part of this seems to be almost ready via https://github.com/submariner-io/submariner/pull/134. For the second part, does it make sense to you to deploy a custom OLM catalog/registry to enable OLM deploys with non-released Submariner versions? https://github.com/operator-framework/operator-registry#building-an-index-of-operators-using-opm

@dfarrell07 what I mean is that OLM is a means to an end, not an end to itself. I think subctl should be able to use OLM to install the operator, if OLM is already present. I don’t think subctl should install OLM itself to install the operator.

Agreed

@skitt the first part of this seems to be almost ready via submariner-io/shipyard#175. For the second part, does it make sense to you to deploy a custom OLM catalog/registry to enable OLM deploys with non-released Submariner versions? https://github.com/operator-framework/operator-registry#building-an-index-of-operators-using-opm

There used to be a way to add a local catalog entry without pushing a custom catalog, I don’t know if that’s still possible but it would be much easier than the whole custom catalog thing. I’ll look into it once I’ve finished Libreswan.

@skitt @mangelajo If you get a chance, am I on the right track with https://github.com/submariner-io/submariner-operator/pull/432? There are still TODOs stubbed out (and tests failing because of them), but wanted to get feedback before pushing on too far.


Remove invalid calls to "bin/apply-config-from-env.py conf/bkenv.sh"

this is obsolete after apache/pulsar#6579, apache/pulsar#4105 and apache/pulsar#5892
changes.

apply-config-from-env.py doesn't properly handle replacements for shell scripts and it's not necessary to use it.

We missed this change while working on #110


[New Feature]: Home page should appear attractive.

🎮 feature Request
The homepage should be colorful, and we can add a navbar where we can include some icons using CSS. We can also add a demo video showing how the game is played.
Point down the features
feature points
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

please assign me I can do this

Kindly assign me this issue , I will do this .

If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created separate channels for all projects...
Thank you :)


Smi's static _positiveBase10Length function calls operator< dynamically

Pretty sure the fix is simple (change var to int). I guess it's a left over from Dart 1.0 days, noticed it when debugging some AOT issues.
I guess TFA doesn't tell the VM that the smi argument is always an integer (or better, an Smi).
https://github.com/dart-lang/sdk/blob/895cb7720db4bcaef1f0c8f6b947e6b6d4b8b868/runtime/lib/integers.dart#L573

/cc @alexmarkov


Opkg update test

Verify that opkg can download list of packages.
Signed-off-by: Michal Hrusecky<EMAIL_ADDRESS>

Looks great @miska, I'll merge it now!


some countries are not present (Ivary coast), West Africa

Just checked and this is the case indeed. It will be added in an upcoming version. If you are able to submit a PR, that would speed things up as well.

Sure

@kizitonwose Check the PR - https://github.com/kizitonwose/CountryPickerView/pull/128

Closing this as #128 is closed.


create $approve and $reject methods for Annex81

@SmalsJulien

Result can be checked here: https://build.fhir.org/ig/hl7-be/referral/branches/issue-339

Hello,
Thank you for the modification.
Maybe for the rejection, is it possible to put the description "Reject an Annex 81 proposal" instead of "Creates an rejection from an Annex81 proposal" because we are not always creating a resource in this case.
As discussed, the body is given like that:
{ 	"resourceType": "Parameter", 	"parameter": [{ 		"name": "note" 		"valueMarkdown": "my note" 	}] }
And the response will be like that:
{ 	"resourceType": "Parameter", 	"parameter": [{ 		"name": "location" 		"valueId": "refID" 	}] }


ES5 on CentOS 7 fails due to 'max number of threads is too low'

Elasticsearch 5.4 is failing to start on a freshly installed CentOS 7 VM with the following error:

max number of threads [1861] for user [elasticsearch] is too low, increase to at least [2048]

It appears that Systemd ignores the values specified in 'limits.conf', so need to add LimitNPROC to systemd unit file.
PR incoming to implement.

Implemented in #837, will go out with next release.


cfr: 0_101 -> 0_125

Motivation for this change
Version update

@GrahamcOfBorg build cfr

No attempt on aarch64-linux
The following builds were skipped because they don't evaluate on aarch64-linux: cfr
No log is available.

Success on x86_64-linux (full log)
Attempted: cfr
Partial log (click to expand)
  /nix/store/8c35w6whyp0mdygj8n1qpwvci6jq4njn-cfr_0_125.jar.drv
  /nix/store/ya9cvw7j75qh3rjsjd1ifcc18grnacms-cfr-0_125.drv
building '/nix/store/8c35w6whyp0mdygj8n1qpwvci6jq4njn-cfr_0_125.jar.drv'...

trying http://www.benf.org/other/cfr/cfr_0_125.jar
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1529k  100 1529k    0     0  1640k      0 --:--:-- --:--:-- --:--:-- 1640k
building '/nix/store/ya9cvw7j75qh3rjsjd1ifcc18grnacms-cfr-0_125.drv'...
/nix/store/llvw6k2dbabp16i2l2db0v48pyi6z7if-cfr-0_125


Error resolving references within extended objects

Glossary
An "extended object" is a JSON object that has other properties in addition to $ref.  For example:
{
    "name": "additional name property",
    "$ref": "#/some/reference"
}

Note: that extended objects are not allowed by the JSON Schema or JSON Reference specs.  The json-schema-ref-parser library only supports them for backward-compatibility, and it's possible that this support will be removed at some point in the future to bring this library inline with the official spec.

Issue Description
There is currently a bug in the dereference() method when an extended object contains both an external file reference and an internal reference.  The internal reference gets broken, because the dereference() method attempts to resolve it in the external file instead.
Issue Reproduction
Here is sample code that reproduces this issue:  https://runkit.com/bigstickcarpet/swagger-cli-issue-19

Any updates on this? Im having the same issue ... I tried using a custom resolver, but this error occurs before my custom resolver can intercept and handle the #/some/reference

No update on this yet.  It's lower on my priority list than other issues, since it only occurs for schemas that are technically invalid (see my note above)

Thanks ... will keep eyes on this issue to see what is done going forward ... Hoping it gets in, but understand the bring this library inline with the official spec statement .... any chance of a fork?

My plan is for the core library to be spec-compliant and to move the non-spec-compliant functionality to a companion library or a plugin.


After update to version 0.8.0 (0.8.1 too) Eufy Addon is not working wit error "No stations found" and "No devices found"

Version
0.8.0 and 0.8.1
Node version
that came with Homeassistant OS installed at Rasberry PI
Operating System type
Linux
Operating system version
Home Assistant OS 2022.2.3
Describe the bug
After update to version 0.8.0 the Addon is not working and is possible to see following in the logs:
2022-02-07 08:47:02.847  INFO  Eufy Security server listening on host <IP_ADDRESS>, port 3000
2022-02-07 08:47:05.308  INFO  No stations found.
2022-02-07 08:47:05.555  INFO  No devices found.
2022-02-07 08:47:06.132  INFO  Push notification connection successfully established
Then I updated to version 0.8.1 with the same problem.
With version 0.7.0 there was not problems
I tried to uninstall the addon, update homeassistant to latest version 2022.2.3, checked code country, but non of my tests worked.
I also tried to login to Eufy cameras webpage to double check my account was not locked and it was working fine.
To reproduce
In my case, the update from version 0.7.0 to version 0.8.0 and latter 0.8.1 was enough to see the problem
Screenshots & Logfiles
No response
Additional context
No response

+1
Country: CH
Core 2022.2.3
Eufy Security 0.8.1

+1
I think this is related to / a duplicate of https://github.com/bropat/eufy-security-ws/issues/81

New version released 0.8.2

I just updated to version 0.8.2 and reboot HA but unfortunatelly with no luck :(

I have news. Today the Android version for Eufy was updated to version 4 and then, Eufy for homeassistant started to work so I think it was something related with Eufy webpage.
Note: Was necesary to reboot homeassistant
Thank you very much for your time and help


overlay backend allows rmi on in-use layers

We switched to overlay yesterday and are already seeing non-deterministic problem with the filesystem backend, across multiple containers and teams. Linux 4.0.2, docker 1.6.0, ext4 filesystem.  I initially thought this might be #11012, but since that was reported against XFS originally I decided to open my own issue.
We run Docker containers for our CI builds.  Immediately after we migrated to the overlay storage driver, we started to see problems:
++ cut -d . -f 1
./../otpl-deploy-scripts/bin/otpl-deploy: line 218: cut: command not found

[Step 2/5] jetbrains.buildServer.agent.runner.CannotBuildCommandLineException: Unable to find java executable at: /usr/lib/jvm/java-8-openjdk-amd64/bin/java
    at jetbrains.buildServer.agent.runner.JavaCommandLineBuilder.buildPath2Java(JavaCommandLineBuilder.java:155)
    at jetbrains.buildServer.agent.runner.JavaCommandLineBuilder.build(JavaCommandLineBuilder.java:107)

Trying to enter the container, something is clearly fucked:
root@mesos-slave8-qa-uswest2:~# docker exec -it 0adffe3c5da6 /bin/bash
bash-4.3# ls
bash: ls: command not found
bash-4.3# echo *
*
bash-4.3# pwd
/
bash-4.3# /bin/ls
bash: /bin/ls: No such file or directory
bash-4.3# /bin/*
bash: /bin/*: No such file or directory
bash-4.3# find .
.
bash-4.3# bash  # NOTE HOW THIS SUCCEEDS
bash-4.3# exit
bash-4.3# ps
bash-4.3# find /bin/bash
/bin/bash
bash-4.3# find /bin
/bin

Looking from the outside in:
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay# cd 0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# ls
lower-id  merged  upper  work
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# ls merged/
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# ls upper/
dev  etc  home  mnt  run  tmp  var
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# find work
work
work/work
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# find merged
merged
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# find merged/
merged/
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# ls merged/
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# find upper
upper
upper/.dockerenv
upper/.dockerinit
upper/etc
upper/etc/hosts
upper/etc/mtab
...
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# ls -lh merged/bin/bash
-rwxr-xr-x 0 root root 998K Oct  7  2014 merged/bin/bash
root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# ls -lh merged/bin/
total 0

I looked at the mapping, and wonder if it's something related to the absence of a root directory:
root@mesos-slave8-qa-uswest2:~# cat /proc/mounts  | grep 0adf
overlay /mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83/merged overlay rw,relatime,lowerdir=/mnt/docker/overlay/914daaa4ae3ecae1966c92ef38c62835f5f81fd75ae544409d099345e958c93a/root,upperdir=/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83/upper,workdir=/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83/work 0 0

root@mesos-slave8-qa-uswest2:/mnt/docker/overlay/0adffe3c5da6dca485194ed26135361ee6ea46fbec841ef6a1750997a5673d83# ls
lower-id  merged  upper  work

root@mesos-slave8-qa-uswest2:/# docker version
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 4749651
OS/Arch (client): linux/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 4749651
OS/Arch (server): linux/amd64

root@mesos-slave8-qa-uswest2:/# docker info
Containers: 40
Images: 360
Storage Driver: overlay
 Backing Filesystem: extfs
Execution Driver: native-0.2
Kernel Version: 4.0.2
Operating System: Ubuntu 14.04.2 LTS
CPUs: 8
Total Memory: 29.45 GiB
Name: mesos-slave8-qa-uswest2
ID: NMLO:YQYU:3N53:LTCK:CBGB:LYIH:GHTZ:Y5ME:UIUZ:4IKD:VUWQ:BN2L
WARNING: No swap limit support

root@mesos-slave8-qa-uswest2:~# uname -a
Linux mesos-slave8-qa-uswest2 4.0.2 #1 SMP Tue May 12 23:29:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Hi!
If you are reporting a new issue, PLEASE make sure that does not have any duplicates already open.
We would like to take this time to remind you of the information we need to debug the problem you are seeing. This is an automated response so if this ticket is not about a bug, do not fret.
If you fail to provide this information within 7 days, we will close this because we cannot debug your issue. We can reopen whenever the information is provided.
Thank you.
Please see:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
Description of problem:

`docker version`:

`docker info`:

`uname -a`:

Environment details (AWS, VirtualBox, physical, etc.):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Additional info:

#ENEEDMOREINFO

I wish I had reproduction steps, believe me...

Thanks for reporting
/cc. @jfrazelle @crosbymichael might want to have a quick look for overlay.

pinng @vbatts we may want to add this to our list of thinngs to fix before overlay is no. 1 :)

I now strongly suspect this is related to a missing root directory.  It happened again:
root@mesos-slave1-qa-uswest2:/mnt/docker/overlay/ee164b56ee9a99c663e4711f9efe615c8969d0935aacd39f297a3b7f9dc81171# cat /proc/mounts | grep ee164b56ee9a
overlay /mnt/docker/overlay/ee164b56ee9a99c663e4711f9efe615c8969d0935aacd39f297a3b7f9dc81171/merged overlay rw,relatime,lowerdir=/mnt/docker/overlay/24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d/root,upperdir=/mnt/docker/overlay/ee164b56ee9a99c663e4711f9efe615c8969d0935aacd39f297a3b7f9dc81171/upper,workdir=/mnt/docker/overlay/ee164b56ee9a99c663e4711f9efe615c8969d0935aacd39f297a3b7f9dc81171/work 0 0
root@mesos-slave1-qa-uswest2:/mnt/docker/overlay/ee164b56ee9a99c663e4711f9efe615c8969d0935aacd39f297a3b7f9dc81171# ls /mnt/docker/overlay/24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d/root
ls: cannot access /mnt/docker/overlay/24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d/root: No such file or directory
root@mesos-slave1-qa-uswest2:/mnt/docker/overlay/ee164b56ee9a99c663e4711f9efe615c8969d0935aacd39f297a3b7f9dc81171# cd ../
root@mesos-slave1-qa-uswest2:/mnt/docker/overlay# cd 24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d
-su: cd: 24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d: No such file or directory

And a smoking gun: our cleanup script is deleting the layer out from under the container!
Untagged: docker-pp-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209
Deleted: 24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d

That the Docker daemon allows you to delete an in-use layer is a huge problem.

Woah wat. This doesn't seem right or is a regression.
On May 20, 2015 16:48, "Steven Schlansker"<EMAIL_ADDRESS>wrote:

And a smoking gun: our cleanup script is deleting the layer out from under
the container!
Untagged: docker-pp-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209
Deleted: 24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d
That the Docker daemon allows you to delete an in-use layer is a huge
problem.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/13261#issuecomment-104033225.

Indeed, I can now do this, which did not work before on the btrfs or devicemapper backends:
root@mesos-slave1-qa-uswest2:/mnt/docker/overlay# docker ps | grep feature
354eb80340af        docker-pp-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209                                        "node fm-server.js"    21 hours ago        Up 21 hours                                   mesos-626b5438-d9db-4d53-a7b0-251f1b7f1679
ee164b56ee9a        docker-ci-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209                                        "node fm-server.js"    21 hours ago        Up 21 hours                                   mesos-b24dd8b2-9a05-4520-a8a3-78e754b49a4f
root@mesos-slave1-qa-uswest2:/mnt/docker/overlay# docker rmi -f docker-pp-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209
Untagged: docker-pp-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209
root@mesos-slave1-qa-uswest2:/mnt/docker/overlay# docker rmi -f docker-ci-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209
Untagged: docker-ci-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209
Deleted: 24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d
Deleted: 845054e95a2e16f6a55f67fde52550b7756ec609f8e0de44dc531fc651a8da86
Deleted: b86b04419bb464fb8d824e15375b704277832318570a564b3e78d55ef88f923d
Deleted: 3523eaa06072ccbb60337270c288e70000f73bea629d280d6e593a0f867b3e4e
Deleted: 3ed5bc67cec0a6db953334ef08b46ee116d1bb148426a31145b033a977e83b5d
Deleted: 9e2e6341c4f7db48919c7e29e19ed6dfeb3029f78f302c5607b3ea85430a3df2
Deleted: a0988a11a88009da80f69f60a69779d9409b5b18024095adc8b7f3bfc8206baa
root@mesos-slave1-qa-uswest2:/mnt/docker/overlay# docker ps | grep feature
354eb80340af        docker-pp-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209                                        "node fm-server.js"    21 hours ago        Up 21 hours                                   mesos-626b5438-d9db-4d53-a7b0-251f1b7f1679
ee164b56ee9a        docker-ci-uswest2.otenv.com/gc-featuremanager:gc-featuremanager-209                                        "node fm-server.js"    21 hours ago        Up 21 hours                                   mesos-b24dd8b2-9a05-4520-a8a3-78e754b49a4f

This is a serious issue for people trying to reclaim disk space.  It really highlights the lack of the proposed docker clean command to reclaim disk space.  I bet a lot of the homegrown hacks out there will start to exhibit similar problems...
We are now back to square zero with regards to our nodes filling up their disks endlessly with CI-built images.

Isn't the purpose of the -f flag here to force the removal of the image regardless if a container i using it if the container using it is stopped?

I'm not seeing the same behavior

vbatts@noyee ~ (master) $ docker info
Containers: 12
Images: 172
Storage Driver: overlay
 Backing Filesystem: extfs
Execution Driver: native-0.2
Kernel Version: 4.0.3-300.fc22.x86_64
Operating System: Fedora 22 (Twenty Two)
CPUs: 4
Total Memory: 7.234 GiB
Name: noyee.usersys.redhat.com
ID: VG6V:7CTR:AU4V:JIWF:4WDU:Y2WP:XHMQ:4KZG:7YIU:CBPY:3LSG:DMF6
Debug mode (server): true
Debug mode (client): false
Fds: 22
Goroutines: 44
System Time: Thu May 21 11:07:39 EDT 2015
EventsListeners: 0
Init SHA1: 61b17d8393b7181419cbc5b3fc83ad452d0a82cc
Init Path: /usr/libexec/docker/dockerinit
Docker Root Dir: /var/lib/docker
Username: vbatts
Registry: [https://index.docker.io/v1/]
vbatts@noyee ~ (master) $ docker version
Client version: 1.6.1
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 97cd073
OS/Arch (client): linux/amd64
Server version: 1.6.1
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 97cd073
OS/Arch (server): linux/amd64
vbatts@noyee ~ (master) $ docker run -t -d busybox top
a8a5aa91aeaceb48a566c8d29abe319ffc606ee1a5ea0fc29f09ecb76283bb38
vbatts@noyee ~ (master) $ docker ps
CONTAINER ID        IMAGE                    COMMAND             CREATED             STATUS              PORTS               NAMES
a8a5aa91aeac        busybox:latest           "top"               2 seconds ago       Up 2 seconds                            sick_babbage
vbatts@noyee ~ (master) $ docker rmi busybox
Error response from daemon: Conflict, cannot delete 4986bf8c1536 because the running container a8a5aa91aeac is using it, stop it and use -f to force
FATA[0000] Error: failed to remove one or more images
vbatts@noyee ~ (master) $ docker rmi -f busybox
Error response from daemon: Conflict, cannot force delete 4986bf8c1536 because the running container a8a5aa91aeac is using it, stop it and retry
FATA[0000] Error: failed to remove one or more images

even -f fails due to the container using it...

Indeed for me, -f fails if the container is running, it allows the removal if the container is not running.

We are forced to use -f because of the following error message:
Error response from daemon: Conflict, cannot delete image 34f0138c2fbd because it is tagged in multiple repositories, use -f to force

Since we use regional mirrors, and docker still has no client side registry mirror fallback (https://github.com/docker/docker/pull/9161), we must tag all our images in each region we wish to pull from.  We are a global org and constantly pulling images from California to London seriously taxes our WAN links.
So all our images are tagged in multiple repositories.  So nothing will ever get deleted if we do not use -f :(

I upgraded to 1.6.2:
root@mesos-slave1-qa-uswest2:~# docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64

and retried:
root@mesos-slave1-qa-uswest2:~# docker rmi -f docker-ci-uswest2.otenv.com/shardkeygenerator-server:shardkeygenerator-server_teamcity_37
Error response from daemon: Conflict, cannot force delete 3e17baa2fbb1 because the running container 03322bdee759 is using it, stop it and retry

So it seems this affects 1.6.0 but not 1.6.2

so this is a non-issue now?
On Thu, May 21, 2015 at 2:29 PM, Steven Schlansker<EMAIL_ADDRESS>
wrote:

I upgraded to 1.6.2:
root@mesos-slave1-qa-uswest2:~# docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64
and retried:
root@mesos-slave1-qa-uswest2:~# docker rmi -f docker-ci-uswest2.otenv.com/shardkeygenerator-server:shardkeygenerator-server_teamcity_37
Error response from daemon: Conflict, cannot force delete 3e17baa2fbb1 because the running container 03322bdee759 is using it, stop it and retry
So it seems this affects 1.6.0 but not 1.6.2
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/13261#issuecomment-104379245.

Seems so.  But anyone who uses 1.6.0 is in for a surprise...

fair. thanks.
On Thu, May 21, 2015 at 3:02 PM, Steven Schlansker<EMAIL_ADDRESS>
wrote:

Seems so. But anyone who uses 1.6.0 is in for a surprise...
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/13261#issuecomment-104389965.

Okay, we are now reproducing the same issue on docker 1.6.2:
root@mesos-slave1-qa-uswest2:~# docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64

root@mesos-slave1-qa-uswest2:~# docker exec -it fe654fe63fb9 /bin/bash
exec: "/bin/bash": stat /bin/bash: no such file or directory
Cannot run exec command bee0e7367908ea56b2287540840ce4351bcd68aa966ec81966687c5524124e43 in container fe654fe63fb947d7b41fbb9a7be5a3f654b8bcca79bc08979dd4eca373c6fb3a: [8] System error: exec: "/bin/bash": stat /bin/bash: no such file or directory

root@mesos-slave1-qa-uswest2:/mnt/docker/overlay/fe654fe63fb947d7b41fbb9a7be5a3f654b8bcca79bc08979dd4eca373c6fb3a# cat /proc/mounts | grep fe654fe63fb9
overlay /mnt/docker/overlay/fe654fe63fb947d7b41fbb9a7be5a3f654b8bcca79bc08979dd4eca373c6fb3a/merged overlay rw,relatime,lowerdir=/mnt/docker/overlay/24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d/root,upperdir=/mnt/docker/overlay/fe654fe63fb947d7b41fbb9a7be5a3f654b8bcca79bc08979dd4eca373c6fb3a/upper,workdir=/mnt/docker/overlay/fe654fe63fb947d7b41fbb9a7be5a3f654b8bcca79bc08979dd4eca373c6fb3a/work 0 0

root@mesos-slave1-qa-uswest2:/mnt/docker/overlay/fe654fe63fb947d7b41fbb9a7be5a3f654b8bcca79bc08979dd4eca373c6fb3a# ls /mnt/docker/overlay/24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d
ls: cannot access /mnt/docker/overlay/24ac989500e74c921b46ab49b2b092c96878a058100caa28072e32990c89791d: No such file or directory

It's probably a bug of the rmi API. I submitted a PR #14578
I can reproduce this problem consitently with the following script:
#!/bin/bash
# Build 2 images for testing.
echo -e "FROM busybox\nRUN echo a"|docker build -t test1 -
echo -e "FROM busybox\nRUN echo b"|docker build -t test2 -

# First let's start a long-running container.
docker run -d test1 sleep 300

# Create another container and force remove its image.
docker run --name=TEST2 test2 true
docker rmi -f test2

# At this point the images of any running containers that were created
# before TEST2 can be removed regardless of the -f flag.
docker rmi test1


Does not function when using the "Pop-out chat" function.

What the title says, if you use the "Pop-out chat" function then the extension doesn't seem to detect it and no filtering is done.
It might never have been your intention to have it work with the pop-out chat but just in-case you were unaware.
I guess this can double as a feature request since if it isn't too annoying to add that function, it would be nice to have.
Thanks in advance.

Fixed in v0.0.8


Use numeric_limits::lowest instead of numeric_limits::min

From https://en.cppreference.com/w/cpp/types/numeric_limits/min:
"For floating-point types with denormalization, min returns the minimum positive normalized value. Note that this behavior may be unexpected, especially when compared to the behavior of min for integral types. To find the value that has no values less than it, use numeric_limits::lowest."
Depending on the values one can get on the track, using min might be okay, buy by using lowest we remove all doubt.

Thanks for the quick review!

From https://en.cppreference.com/w/cpp/types/numeric_limits/min:
"For floating-point types with denormalization, min returns the minimum positive normalized value. Note that this behavior may be unexpected, especially when compared to the behavior of min for integral types. To find the value that has no values less than it, use numeric_limits::lowest."
Depending on the values one can get on the track, using min might be okay, buy by using lowest we remove all doubt.

In the future please add PR description to the commit message as well.

In the future please add PR description to the commit message as well.

I'm actually not sure what you mean. Add the entire PR description to the commit message? I'm probably misunderstanding what you are saying.

Yes - I meant the PR description

Ah, yes, thanks @ronaldfw  :-)


Rename the Primary Branch from Master to Main

Enter an issue title
Rename the Primary Branch from master to main
Summary
In support of Proposal to Rename the Primary Branch on all Cloud Foundry repos, we would like to move away from Master branch to Main.
Here is an example of a script that helps with the migration or we can use Git 2.28 for an easier workflow
Questions

[ ] Can this change break old releases? We've used master branch in gitmodules, so will older tags still work?
[ ] Most pipelines and go modules that pull diego-release components will break. What sort of communication should we have for this change? (e.g. https://pkg.go.dev/code.cloudfoundry.org/bytefmt?tab=importedby)

Diego repo
All of the Diego repo's in cloudfoundry and cloudfoundry-incubator

[ ] https://github.com/cloudfoundry/diego-release
[ ] https://github.com/cloudfoundry/archiver
[ ] https://github.com/cloudfoundry/auction
[ ] https://github.com/cloudfoundry/auctioneer
[ ] https://github.com/cloudfoundry/bbs
[ ] https://github.com/cloudfoundry/benchmarkbbs
[ ] https://github.com/cloudfoundry/bytefmt
[ ] https://github.com/cloudfoundry/cacheddownloader
[ ] https://github.com/cloudfoundry/certsplitter
[ ] https://github.com/cloudfoundry/cfdot
[ ] https://github.com/cloudfoundry/clock
[ ] https://github.com/cloudfoundry/consuladapter
[ ] https://github.com/cloudfoundry/debugserver
[ ] https://github.com/cloudfoundry/diego-dockerfiles
[ ] https://github.com/cloudfoundry/diego-logging-client
[ ] https://github.com/cloudfoundry/diego-upgrade-stability-tests
[ ] https://github.com/cloudfoundry/dockerdriver
[ ] https://github.com/cloudfoundry/durationjson
[ ] https://github.com/cloudfoundry/ecrhelper
[ ] https://github.com/cloudfoundry/eventhub
[ ] https://github.com/cloudfoundry/executor
[ ] https://github.com/cloudfoundry/fileserver
[ ] https://github.com/cloudfoundry/healthcheck
[ ] https://github.com/cloudfoundry/inigo
[ ] https://github.com/cloudfoundry/localdriver
[ ] https://github.com/cloudfoundry/localip
[ ] https://github.com/cloudfoundry/locket
[ ] https://github.com/cloudfoundry/operationq
[ ] https://github.com/cloudfoundry/rep
[ ] https://github.com/cloudfoundry/route-emitter
[ ] https://github.com/cloudfoundry/systemcerts
[ ] https://github.com/cloudfoundry/tlsconfig
[ ] https://github.com/cloudfoundry/vizzini
[ ] https://github.com/cloudfoundry/volman
[ ] https://github.com/cloudfoundry/workpool

There seems to be more tooling coming from Github that will help with the migration.
go.mod imports will break. I found the following documentation that suggests using branches in go.mod is not a recommended pattern. Since CF mailing list had already proposed this change, we don't need any other communication for this change.
Given the number of repositories we have, I propose we wait until the new tooling is introduced in Github.


#402 - Secret key should be stored as a byte[]

https://docs.oracle.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec.html#PBEEx
However, here's the caveat: Objects of type String are immutable, i.e., there are no methods defined that allow you to change (overwrite) or zero out the contents of a String after usage. This feature makes String objects unsuitable for storing security sensitive information such as user passwords.

But you will never need to override this credential, it is meant to be used consistently so the system this application is going to be used has to be secure. Also, this change will break the existing code.

Even though it is not being overwritten just keeping it in memory is a security risk, the JVM can be inspected for the string value.
There is no real need to store a secret ket as a String as Binance just needs the byte[] to create the SecretKeySpec.  Added to this, a lot of developers will store their private key in a java keystore and when the key is loaded from the keystore it will be in a byte[].  So the the ideal scenario is to load the key as byte[] from the keystore and pass to binance to create the SecretKeySpec from the byte[].  In this flow the secret key never needs to be stored as a String for the lifetime of the application.
I dont think this change will break existing code, I have kept the old String methods for backward compatibility.
Although for this change it might be better to allow a breaking change so developers have the opportunity to fix their code so that they never need to load the secret key as a String.

For example, this is how I instantiate Binance in my app using my binance fork
char[] keystorePassword;  // ="xxxxx";
KeyStore keystore =  KeyStore.getInstance("JCEKS");
keystore.load(new FileInputStream(ATH), password);
Key k = keystore.getKey("BinanceSecretKey", password);
SecretKeySpec secret = new SecretKeySpec(k.getEncoded(),"AES");
BinanceApiClientFactory factory = BinanceApiClientFactory.newInstance(apiKey, secret.getEncoded());
This means I never need to store the secret key as a string in memory


Update metadata.py

I added my email address

Coverage remained the same at 69.503% when pulling 206dd7846ff29e0ba22f051b3fffe4bf60d2020d on marcorosa:patch-1 into 4d209d0ddc3ac05a42be4e973223b2a17f3daea8 on Storj:develop.


Add  support to Korean Language

some commas and whitespace has changed automatically by vscode.
thank you

merge another updates


Add key command to go back in browser

Ideally we want to be able to use an onscreen back button or trackpad swipe to go back, but for now at least wire up a key command to let you go back

Added in https://github.com/ashokfernandez/kiste/pull/13


Remove the 'replace with your text' placeholder

This PR fixes...
This PR removed the default text from dictionary entries which do not have any info.
What I did...
Did find and replace on the markdown files that had the default text
How to test...

Go to /dictionary
Ctrl+F to search for "replace with your own definition." See that nothing comes up.

I learned...
I need some sleeeeep. 😪

Zero results returned


Corrupted layout in QR code creation screen on iPhone SE first generation

Avoid duplicates

[ ] Bug is not mentioned in the FAQ
[ ] Bug is specific for iOS only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[ ] Bug is not already reported in another issue

Technical details

Device name: iPhone SE (first generation) / tested on simulator
iOS version: iOS 15 / tested on simulator (Xcode 13.0)
App version: newest developer branch (release/2.14.x as of 03 Nov)

Describe the bug

The QR code creation form has a corrupted layout with overlapping text on iPhone SE first generation.
Steps to reproduce the issue

from 'Status' tab scroll to 'Planning an event' and press button 'Create QR code'
see screen 'My QR codes' and again press button 'Create QR code'
select a location type and get the QR code creation form
Note: on this screen size, only a single field is visible above the keyboard
(optional) fill the first field of the form
press 'Next' to get the next field of the form
the form scrolls up to reveal the next field. The location type overlays with the title. See screenshot.

Expected behaviour

No overlay of the two texts.
Either the location type should push the title up into the navigation bar, or it should hide below the navigation bar (and at least be 'blurred' in that case).
Possible Fix

check the layout constraints, especially those for the safe area ...
Additional context

Internal Tracking ID: EXPOSUREAPP-10544
Internal Tracking ID: EXPOSUREAPP-10545

@jucktnich IIRC you own such a device.
Could you please test if this layout corruption is already present in the current released version?
Thanks!

It's reproducible on a real world device

@jucktnich oh - but thanks for the confirmation.
Could you please add more details on your configuration? (iOS version and cwa version).

iOS 15.1 cwa 2.13.1 (0)

Initial analysis:

the view controller is TraceLocationConfigurationViewController
the layout constraints for this view controller are specified in an interface builder file (TraceLocationConfigurationViewController.xib)

The following screenshot shows the view hierarchy

the two text fields (description and address) are laid out and grouped, using a stack view and a text field container view
this container view is laid out and grouped with a label (the location type), using a stack view and a view
and all this is embedded in a scroll view

Initial analysis, continued. Now we look at the layout constraints.

the scroll view specifies the available full size - this is ok.
Note: we have a translucent navigation bar, and the scroll view is supposed to slide under the bar.
the top-level content view specifies the full size of its superview (except its height may be smaller)
this is not ok - with a translucent navigation bar the content view must take the safe area into account.
the top-level stack view specifies insets of 16 resp. 10 - this again is ok.

Unfortunately, the top-level content view has no @IBOutlet definition.

The behaviour resembles very much what was observed in #2699.
The layout respects the safe area of the large title only as long as there is enough vertical space.
As soon as vertical space becomes tight, it moves up, and overlaps with the large title.
The upwards force seems too weak to push the title back into the navigation bar.
Only when it starts to touch the bottom position of the "normal" navigation bar ( = with normal title size) - at this moment it succeeds to push the title up and into the bar.

I have just checked the linked Jira issue.
Jira Ticket is flagged as:
Resolution: Wont Fix
Status: Obsolete
Unfortunately, no additional information was added to this Jira ticket.

@ndegendogo Dev team's feedback is, that this issue cannot be reproduced anymore. Are you still able to reproduce? Thanks.

Internal Tracking ID: EXPOSUREAPP-10545

@dsarkar Maybe re-open this issue until clarified?

can still be reproduced

PR fixing this:

https://github.com/corona-warn-app/cwa-app-ios/pull/5147

Closing as suggested


kubectl gs 5 chars cluster name validation

Copying the Slack conversation:
Accorgin to https://github.com/giantswarm/roadmap/issues/1017 we decided we want to support 10 characters in the cluster name in CAPI.
Currently there is a validation happening in kubectl gs
Error: Invalid flag: --name must only contain alphanumeric characters, start with a letter, and be no longer than 5 characters in length

Digging into the code reveals that there is another flag that we can pass to extend the length of the name to 10 chars: https://github.com/giantswarm/kubectl-gs/blob/5e272a9c4377fe39336ddf7d0e5a2d3f9d9a69ee/internal/key/key.go#L57
the flag should be --enable-long-names  according to this https://github.com/giantswarm/kubectl-gs/blob/main/cmd/template/cluster/flag.go#L20
However I don't see that flag being used/documented in the current version of kubectl-gs  (2.23.0) because it's marked as hidden.
Passing that flag: --enable-long-names true allows to bypass the validation and generate a YAML template with the longer name.
So this is what I believe could to be done to conform to ISSUE 1017:

[ ] Remove the hidden flag (unless used for other purposes as well)
[ ] Use the 10 chars validation by default
[ ] Remove the 5 chars validation altogether

@alex-dabija Can hydra take a look into this please?

@alex-dabija Can hydra take a look into this please?

@alex-dabija Can hydra take a look into this please?

Unfortunately, not at this moment in time. We are strictly focused on the deliverables for private clusters. I'm adding it to our backlog for now.

When a fix is implemented, ask Hydra to review the PR.

The --enable-long-names flag is used in 3 places/comands:

template cluster
template networkpool
template nodepool

Should we remove it from all 3 commands? Or only from template cluster command?

Note from planning - we should keep things consistent and apply the change to all relevant resources.

Removing the --enable-long-names may be a breaking change in kgs. Question is if anyone even uses it since it's marked as hidden, but it might be safer if we mark the flag as deprecated first and remove it later. What do you think?


Add Clone to JsonRpcExtractor

Add clone derive for avoid re-parsing a request

@esemeniuc do you need release for axum 0.6 or 0.7?

We're using 0.7 branch

Release would be appreciated :)

@esemeniuc done


Use Send-MailMessage instead of SmtpClient / General Cleanup

Per issue #43 , Send-MailMessage is used instead of SmtpClient to enable sending emails through Office 365.
Other changes include:

The addition of an EmailPort parameter to provide to Send-MailMessage
Get-Credential is called at the top of the Begin region so that credentials can be passed to Send-MailMessage
General cleanup and formatting of the overall script (only dealing with fixing style inconsistencies, not changing actual functionality)

Thanks @JaimeStill ! Appreciated!
Other than the Email Edit, I see a lot of changes.
If you submit another PR please keep the changes focus on one particular aspect, easier to review :sweat_smile:
I agree with most of your changes except for:

All the semi-colon which are not necessary in PowerShell (looks like you have a developer background c# ? :smile: )
Way you handle credentials, it should not prompt if the user use the current account.
Date format of the report, I should actually update it to use something like get-date -format o which includes the timezone.

No worries! Apologies for how chaotic the commit was, I'd just pushed up the whole revision I'd made not thinking you may want a PR for it.
Definitely more acquainted with C# / full stack dev than PowerShell, but it's something I enjoy and find fascinating. I've done some really cool stuff building web apps centered around calling PS stuff via Web API. If you'd be interested in anything like that, feel free to shoot me an email (on my profile)!


cube: Fix incremental present on swapchain recreate

When swapchain is recreated the entire surface should be redrawn

CI Vulkan-Tools build queued with queue ID 180439.

CI Vulkan-Tools build queued with queue ID 180448.

CI Vulkan-Tools build queued with queue ID 180448.

CI Vulkan-Tools build # 1439 running.

CI Vulkan-Tools build # 1439 passed.


Fixing version comparisons from strings to semver

See #3002 for more detail

/lgtm
/approve
Thanks!


[suggestion]About make laser more friendly for other players on server

Issue description:
Hi~ Mekanism was a nice mod that bring us joy, but also has troubles which caused by lasers.
I have setup a server to play mekanism with my friends, and we also welcome strangers to join us, but there were some player use laser unfriendly, such as digging around other's house, which broken was unable to prevent by plugins(Sponge plugins, such as griefrevention which could only cancel break event caused by players).
but mek's laser was so cool ( active nuclear generator and transport RF) that we don't want to set it unavailable, so I'm here to request a suggestion:
How about to give more configurable node to laser or other blocks which would be used by someone unfriendly to break other's homes? and if we could config it to disable laser to damage player would much better. even if there were no such friendly laser in real life 😅
Thanks for checking out. ;)
Version :
Minecraft Forge: <IP_ADDRESS>11
Mekanism-1.12.2-<IP_ADDRESS>0
Other relevant version:

It seems like the laser can already by stopped by canceling the BlockEvent.BreakEvent that it fires: https://github.com/aidancbrady/Mekanism/blob/07aab3bd2052209b41020e83f5251ea3690b2170/src/main/java/mekanism/common/LaserManager.java#L90-L96

There also appears to be a setting just above that to turn block breaking off completely
if(!general.aestheticWorldDamage)
{
	return null;
}

So Enhancement is for turning off player damage.


disable word wrap.

Activate or Deactivate Word Wrap via configuration.  JSON with:
"wordWrap": false,
in my Versión: 1.19.10821.0 do not works, for any terminal configuration, "simbolo del sistema" or default.

Proposed technical implementation details (optional)

That's not a setting that's supported by the terminal. There's nowhere in the JSON you could add that which would turn off word wrap. You're probably looking for /dup #1860. Or more correctly, I'd recommend using a pager like less that supports horizontal scrolling.


Run Travis cron jobs as part of the main test suite

This PR integrates the slow-running tests for Travis nightly ('cron') CI with the overall message_ix test suite. The tools used to prepare, upload, and retrieve the test databases are moved to message_ix.testing.nightly and made available through the CLI.
Closes #252.
Partially addresses #244 by adding docs for a new MESSAGE_MACRO.GAMS_min_version attribute.
Supersedes #253. The secure environment variables added by this PR are only available in builds from within the main (iiasa/message_ix) repo, per Travis security restrictions. (The other PR was from my fork.)
PR checklist:

[x] Tests added.
[x] Documentation added.
[x] Release notes updated.

@gidden @zikolach I'd value your thoughts at this point. As of now, the long-running tests pass on Travis/Linux; but consistently run into Java heap space issues. See the most recent build logs on this PR. Two questions:

Is there an easy way to resolve this? I've tried giving jvmargs=['-Xmx4G'], but no change.
Is it even important to do so? These nightly tests are not really to test that the global model can be run in some/all environments, just that it gives correct results when run. So is it sufficient to run them only on Linux?

@khaeru referring to https://docs.travis-ci.com/user/reference/overview/ we should probably not set max heap size to 4g as travis vm (osx) has only 4g ram.
How big is the dataset to be written to gdx? We should probably have some reproducible test case and do some optimizations.

travis vm (osx) has only 4g ram

I also noticed this. I'd like to test with different values, but this is a clean PR so far and I'd like to avoid larding it up with dozens of CI debugging commits. So maybe that means I should merge with macOS tests disabled and then use a new PR for that debugging.

How big is the dataset to be written to gdx?

They are the ones defined here: https://github.com/iiasa/message_ix/blob/99e6b6e5527ca076a928a10bc40b42dce5b38199/tests/data/scenarios.yaml#L1-L23

We should probably have some reproducible test case and do some optimizations.

Agreed, we should.

Is it even important to do so? These nightly tests are not really to test that the global model can be run in some/all environments, just that it gives correct results when run. So is it sufficient to run them only on Linux?

Per discussion on Slack with @gidden—yes, it is sufficient. The nightly runs are a “smoke” test, i.e. an indicator that something might be wrong and should be investigated; this indication will be given by a failing test on any one platform.
I have tried one final tactic in d14375f45c45eaf87951a2b469d66f29237e1f46 to avoid the heap space issue on macOS. If that doesn't work, we will merge this with the macOS tests disabled.

I have tried one final tactic in d14375f to avoid the heap space issue on macOS. If that doesn't work, we will merge this with the macOS tests disabled.

It didn't work :upside_down_face:

Okay, Travis build # 1196 is our confirmation that this works.
I will now disable this temporary setting that was just for this PR: https://github.com/iiasa/message_ix/blob/0b9fb46f3f2afbbe24e28fa14c25955a52cb1070/tests/test_nightly.py#L15-L25
The tests should again pass, but without the nightly tests being run.


Complete registration flow

Use inquirer

Completed with https://github.com/siddharthkp/cronduty-cli/pull/4


Support zsh when creating a react-native application

Description
If you paste the example into zsh without quoting the version you get:
npx react-native init foobar --template<EMAIL_ADDRESS>zsh: no matches found<EMAIL_ADDRESS>
Why
You support more shells from the docs.
Screenshots

Microsoft Reviewers: Open in CodeFlow
Microsoft Reviewers: Open in CodeFlow

We'd be happy to accept a PR that fixes up any of the arguments for zsh as long as it doesn't break the standard shells we expect (PowerShell, cmd, sometimes bash).

/azp run


Throw at startup time instead of run time in case of wrong parameters

What is the issue about:
early throw in case of wrong parameters
What happened:
if I defined a handler function of type:
func(ctx context.Context, first int, after string)

while using definitions as
Parameters: []definition.Parameter{
					{
						Source: definition.Query,
						Name:   "after",
						Type:   reflect.TypeOf(""),
					},
					{
						Source:  definition.Query,
						Name:    "first",
						Type:    reflect.TypeOf(0),
						Default: 10,
					},
				},

then there's only an error thrown during request time.
But in fact, this check can be done at startup time.
What you expected to happen:
Anything else we need to know:

There are some explanation on the field.
	// Type is used to override function parameter type.
	// If you want to override the type in function parameter, you can specify it here.
	// When the type is same as function parameter type, the field can be ignored.
	// If the type is not compatible with function parameter type, you must add
	// a operator to convert it or it will panic.
	Type reflect.Type

It only works in request time. The pipeline is:
request field(string) --> Parameter.Type --> Operators(Must convert type) --> function parameter type


Clean-up.

Changed all 'reasonArgs' parameters to be named 'becauseArgs'.
Fixed some XML-Doc comments.
It is an additional fir for commit 688184bf8e917756e434708b20cf8005d9c7b501.

It also makes sense to rename corresponding fields in IAssertionContext, AssertionContext, IEquivalencyValidationContext files.
What do you think?

Thanks for cleaning this up. What's with those interfaces?
PS. build failed.

About interfaces.
All them have Reason and ReasonArgs properties.
https://github.com/dennisdoomen/FluentAssertions/blob/master/Src/Core/Equivalency/IEquivalencyValidationContext.cs#L13-L22
https://github.com/dennisdoomen/FluentAssertions/blob/master/Src/Core/Equivalency/AssertionContext.cs#L20-L21
https://github.com/dennisdoomen/FluentAssertions/blob/master/Src/Core/Equivalency/IAssertionContext.cs#L25-L34
And such code looks a bit discomfortable for me:
public static void ShouldAllBeEquivalentTo<T>(this IEnumerable<T> subject, IEnumerable expectation,
    Func<EquivalencyAssertionOptions<T>, EquivalencyAssertionOptions<T>> config, string because = "",
    params object[] becauseArgs)
{
    EquivalencyAssertionOptions<IEnumerable<T>> source = config(AssertionOptions.CloneDefaults<T>()).AsCollection();

    var context = new EquivalencyValidationContext
    {
        Subject = subject,
        Expectation = expectation,
        RootIsCollection = true,
        CompileTimeType = typeof (IEnumerable<T>),
        // This one
        **Reason** = because,
        **ReasonArgs** = becauseArgs
    };

    new EquivalencyValidator(source).AssertEquality(context);
}```

About the build.
If I understand the AppVeyor output correctly, it says the problem is with publishing the package.
Can I fix it myself?

Everything is Ok
##teamcity[blockClosed name='Zipping up the binaries']
Executing BuildPackage at 03/02/2016 13:19:45
##teamcity[blockOpened name='Building NuGet Package']
Attempting to build package from '.nuspec'.
Successfully created package 'C:\projects\fluentassertions\Artifacts\FluentAssertions.4.2.2.nupkg'.
##teamcity[blockClosed name='Building NuGet Package']
Executing PublishToMyget at 03/02/2016 13:19:48
##teamcity[blockOpened name='Publishing NuGet Package to Myget']
Pushing   to 'https://www.myget.org/F/fluentassertions_ci/'...
Error: 3/2/2016 1:19:51 PM:
At C:\projects\fluentassertions\build\default.ps1:154 char:4 +             & $Nuget push $package.FullName $NuGetApiKey -Source "$NuGetPushSource" +             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Command exited with code

Ah yes, my publishing API key was changed. Fixed it for you. And yes, go ahead and rename those internal properties.

Thanks.
OK, I will do it.

Just to have proper references: #28 #91

@GDoronin you're still on this?

@dennisdoomen Yes I am. Please wait a few more days. We just had a 4-days national holidays :)

No worries.

@dennisdoomen It's done.
However, one more question if you don't mind..
In the file Core\Collections\StringCollectionAssertions.cs, what's the purpose of becauseArg = null parameter?
There is params object[] becauseArgs parameter, so the previous one seems redundant.
Also, all other methods of this class simply call the base-class implementations, but not this.
public AndConstraint<StringCollectionAssertions> Contain(IEnumerable<string> expected, string because = null,
    object becauseArg = null,
    params object[] becauseArgs)
{
    var args = new List<object> {becauseArg};
    args.AddRange(becauseArgs);
    return base.Contain(expected, because, args.ToArray());
}

I've noticed this because it doesn't have matching XML param tag:
      Src\Core\Collections\StringCollectionAssertions.cs:113 Parameter 'becauseArg' has no matching param tag in the XML comment for FluentAssertions.Collections.StringCollectionAssertions.Contain (but other parameters do)

Aich, that looks like a merge issue. Somebody recently renamed all parameters named reasonArgs to becauseArgs.

Actually it was there before my renaming.. :)
Check for example this revision from AUG 2015:
https://github.com/dennisdoomen/FluentAssertions/blob/6f0164317df98f43c5b00583d1a9b8124c286792/Src/Core/Collections/StringCollectionAssertions.cs

Ah, that was you ;-)

Hmm, it seems that you need to rebase your changes. If you can ensure your PR ends-up as a single commit, then I can merge it right away.

Hm, it seems the recent PR introduced few merge conflicts in two files:

Src\Core\Collections\CollectionAssertions.cs
Src\Core\Collections\SelfReferencingCollectionAssertions.cs

I'll rebase and resolve the conflicts tomorrow.
Just to clarify.

If you can ensure your PR ends-up as a single commit, then I can merge it right away.

Do you want me to squash my commits, right?

Do you want me to squash my commits, right?

Yes!

@dennisdoomen Done.


KAFKA-4269 extracted code updating topics when regex pattern specifie…

…d out of topicGroups method. The topicGroups method only called from StreamPartitionAssignor when KafkaStreams object  is the leader, needs to be executed for clients.

@guozhangwang  @mjsax @dguy
Please review when you have a chance.
The previous change for multiple consumers missed extracting a block of code in the topicGroups() method only called for the leader KafkaStreams instance.

@dguy
Added unit test for method

A few minor comments otherwise LGTM. @bbejeck could you rebase?

@guozhangwang
rebased and updated per comments

Merged to trunk.

@bbejeck Could you file a follow-up PR for 0.10.1 branch just in case we have a bug-fix release later?

@guozhangwang - Sure thing.  I attempted opening the PR against the 0.10.1 branch but it looked like there were a lot of conflicts, is there another approach ?

You can try 1) checkout 0.10.1 first and checkout a new branch from there, and 2) use git cherry-pick to pull in that commit from trunk, 3) upon showing conflicts, fixing them forward, 3) git commit to create a new PR.


fix: add typing

Coverage remained the same at 98.23% when pulling 0ec870f728ebfe8cb6d4419c98ae263400931e06 on typed-logger into e754c7af80a7aa1a9fd1836a2a0ab353df86d4fb on master.

Coverage remained the same at 98.23% when pulling 0ec870f728ebfe8cb6d4419c98ae263400931e06 on typed-logger into e754c7af80a7aa1a9fd1836a2a0ab353df86d4fb on master.

Coverage remained the same at 98.23% when pulling 0ec870f728ebfe8cb6d4419c98ae263400931e06 on typed-logger into e754c7af80a7aa1a9fd1836a2a0ab353df86d4fb on master.


Memorize filtering and sorting

Hello. Is there an option similar to memorize_per_page, so that it can remember my previous filters and sorting order when I come back on the listing page?

This was already requested in #26


Private Clocks

Added ability for GMs to create private clocks that can not be viewed by players.

There is a checkbox on the edit dialog to make a clock private.
An eye slash icon will appear next to the name of a clock to inform the GM that it is private.

Thanks for doing this. This seems against the spirit of clocks, but it can't hurt.
Can you change how visibility is set using a hidden css class? Something like {{#if (and clock.private @root.editable)}}hidden{{/if}}. If that doesn't mess with sortable then it would be much preferred as a solution.

Not a problem. That's actually the first way I did it. I was just slightly concerned a skilled player would be able to unhide the private clock. However the css class approach is much simpler code. I was unfortunatly unable to figure out how to do an 'and' with handlebarjs and could not find any documentation.  So I settled on an 'unless' nessed in an 'if'. I hope this will suffice.
Sorting works fine with this approach. The only noticable diffrence is there is not animation when hiding or unhiding a clock. But in reality I don't think that will happen very often.
My GM likes to use clocks for various things like tracking if an encounter is close to happening. So hopefully other GMs will find uses for private clocks.

Awesome! Thank you! It looks like that is working.

Thank you. I wont' release this immediately, but it'll be in there when I finally get to finishing the clock theming stuff.


Rename FunctionExecutionContext -> FunctionContext

This context is meant to be similar to HttpContext. And since ExecutionContext already has another meaning, the current name seems confusing. We think that FunctionContext makes the most sense.

And there's also FunctionInvocation, which also seems to be related to the execution.


Allow CosmWasm contracts to mint new custom sdk.Coin denoms

Currently CosmWasm-enabled chains have two token standards existing in tandem, CW20 and sdk.Coins.  While CosmWasm contracts currently have an easy mechanism for interacting with sdk.Coins denoms that already exist on the chain, there's not an easy plug and play solution for contracts to mint new sdk.Coins denoms (instead, they tend to use CW20s).
Such a mechanism would be useful for many chains and applications that want to use the CosmWasm framework for writing logic in, but would prefer to only support a single token standard (sdk.Coins) for their asset layer, due to increased integration costs of multiple standards.
For example, in Osmosis, we would like to add a permissioned CosmWasm module to allow developers to build DeFi contracts on top, but if these protocols need to mint a new token, would like them to mint native sdk.Coins rather than CW20.  This is because our AMM mechanism, which is written as a native Cosmos SDK module, is built to only support sdk.Coins, and would prefer to avoid the complexity of supporting both standards right now.
In order to make this minting process "permissionless", we would need to namespace minted denoms so that any contract can mint new denoms.  Because CosmWasm contracts have unique address, we could just have the generated denoms be cw/{minting_contract_address}.  However, because a single contract may want to mint multiple tokens, we should also have an additional namespace per contract.  So minted denoms should be cw/{minting_contract_address}/nonce.  This nonce can be chosen by the contract when minting new denoms (or just use increasing sequence numbers if that is preferred).
One solution that was proposed was to consider using the cw-ics20 contract with a loopback ibc channel.  However, according to the ibc-go README, it seems that loopback ibc channels are not yet fully implemented.

This is a very nice idea.
I think cw20 is valuable and there are many cases for full cw20 token support that are not available in native tokens (rebasing, whitelisting, transfer taxes, snapshots, etc). However I believe 80%+ of cw20 tokens are just cw20 base more or less. In these cases, being able to use a native token is a great path to interop.
You could even have a reverse-wrapper contract that takes cw20 tokens and "unwraps" them into custom native denoms that could serve as a generic bridge on eg. Osmosis to bring unmodified contracts that run on other chains and bridge them to your DEX.

One large piece is missing for usability however, and that is the metadata.
CW20 defines a symbol, name, and decimals.
Native tokens have a symbol and there are some standard about decimals (eg. if it starts with u it is 10^-6)
ibctransfer provides a custom denom as a hash, but maintains some metadata in the "denom_trace", minimally the remote denom as a string
I think we need a solution for this to make this usable in real products. And I would generally lean to something like "denom_trace" (which you would have gotten for free if we could use ibctransfer over loopback). But since we would have to build this ourselves, maybe define a custom coin metadata struct based on your experience on Osmosis. Let's design this with the end user in mind.

The Cosmos SDK bank module has a type called DenomMetadata that contains that metadata.
https://github.com/cosmos/cosmos-sdk/blob/master/proto/cosmos/bank/v1beta1/bank.proto#L78
This can be registered and stored in the bank module.
Just to confirm, you don't guarantee name collision resistance for CW20 tokens on a chain rn, right?  Two CW20 tokens could have the same name or symbol?

Yes, the cw20 name is not unique, and the only real identifier is the contract address. However, it makes it nicer to show some Metadata.
Terraswap has some whitelists to deal with fake eg. mGoog tokens. I assume any app would have that, but even an unverified name is a nice first step.

I was very happy to see this feature request 👏 . I had spiked this more than a year ago (#262) but there was no demand from the community. Minting natural coin types can be very powerful but also dangerous when abused to spam the system with random coins, like UX/ performance issues.
Do you have something concrete in mind to limit this to a subset of contracts or should this be a new message type available to all contracts?

It looks like evmos Intrarelayer ERC20 <-> sdk.Coin

Thanks for the link.
Yes, it is a very similar concept we are trying to achieve.
I think there are open questions about allowing multiple native denoms per cw-contract.
Also, making this controlled by the contract, not by an external module. There are some tokens (eg. with rebase, transfer tax, etc) that do not map to a native coin and will not want to allow such mapping, or will want to have some control on it.
But this is a great starting point to look at for a cosmwasm-specific design. Thank you for the contribution.

I've created a tokenfactory module, that achieves the functionality I outlined above, essentially allowing any cosmos sdk address (including a cosmwasm contract) to mint new denoms namespaced by their address and a nonce.  The creator of the denom, is set as the admin of the coin, allowing them to mint, burn, and forceTransfer coins at will.  They can also transfer ownership of the admin privileges.  An account can use either CosmWasm or authz to perform more complex delegation of authorities.
https://github.com/osmosis-labs/osmosis/pull/584
I think if we create a CosmWasm Module, or just use CustomMsgs, with this sdk module, this should allow us to create the functionality we want.

I think if we create a CosmWasm Module, or just use CustomMsgs, with this sdk module, this should allow us to create the functionality we want.

A custom msg and handler would be a quick solution to implement this feature without touching wasmvm messages and play with it today. I had added extension points to make this extension very easy.
The authZ of contracts can then be handled as you like in your handle and/or by calling your "tokenfactory" module.
I want to highlight that when your MsgCreateDenom handling is not restricted then this may cause unwanted side effects for clients reading this data.
evmos intrarelayer relies on a gov process to enable minting for contracts. That addresses the spam risk.
Beside the quick custom msg/handler solution, let's add more ideas how "minting" can be integrated proper into wasmd.

I was considering that we might want to add some sort of governance permissioning or fees to the MsgCreateDenom action, but then realized that technically we already do have a non-spam resistant way of creating denoms... ibc
I suppose that's not a good reason to not fix the spam problem here though.  One thing was, I wonder if we might want to only allow CosmWasm modules to use the module, not normal SDK addresses.  In Osmosis specifically, CosmWasm will be permissioned anyways, so the spam resistance is already happening upstream.  Is there a way for the tokenfactory module to know whether the address calling it is a CosmWasm contract or not?

In Osmosis specifically, CosmWasm will be permissioned anyways

👌

Is there a way for the tokenfactory module to know whether the address calling it is a CosmWasm contract or not?

You can use the HasContractInfo() method to identify if the address belongs to a contract

I hadn't seen this before, and think that this would simplify many things.


Update @yamada-ui/carousel accessibility

Description
This issue aims to address accessibility deficiencies in our carousel component as per W3C guidelines.
The component currently does not meet the accessibility standards outlined in the W3C documentation.
The goal is to ensure the component is accessible to all users, including those using assistive technologies.
Ensure that all unchecked items in this checklist should be addressed.
General Requirements

Visible Labels:

[ ] Carousel container has an accessible label using aria-labelledby or aria-label.
[x] Label does not include the word "carousel".

Roles and Descriptions:

[ ] Carousel container has role="region" or role="group".
[ ] aria-roledescription="carousel" is set on the carousel container.
[ ] Each slide container has role="group" with aria-roledescription="slide".

Rotation Control

Rotation Control Button:

[x] Exists as a native button element or implements the button pattern.
[ ] Accessible label provided by aria-label or inner text.
[ ] Label changes based on action (e.g., "Stop slide rotation" or "Start slide rotation").
[x] Button does not use aria-pressed.

Slide Navigation

Next and Previous Slide Controls:

[x] Exist as native button elements or implement the button pattern.
[x] Styled as arrows.
[ ] Do not move focus when activated.

Slide Picker Controls (if present):

[x] Group of elements, often styled as small dots or tabs.
[x] Each control is a native button element or implements the button pattern.
[ ] Accessible name indicates the slide it will display.
[ ] Current slide control has aria-disabled="true".

Keyboard Interaction

Tab and Shift + Tab Navigation:

[x] Moves focus through carousel interactive elements.

Automatic Slide Rotation:

[ ] Stops when any carousel element receives keyboard focus.
[ ] Does not resume unless the user activates the rotation control.
[x] Stops when the mouse hovers over the carousel.

WAI-ARIA Implementation

Basic Carousel Elements:

[ ] Carousel container includes all components, with role="region" or role="group".
[ ] Rotation, next slide, and previous slide controls are native button elements or implement the button pattern.
[ ] Each slide container has role="group" with aria-roledescription="slide".
[ ] Each slide has an accessible name using aria-labelledby or aria-label.
[ ] Wrapper element for slides has aria-atomic="false" and aria-live="off" if rotating, aria-live="polite" if not.

Tabbed Carousel Elements:

[ ] Slide containers have role="tabpanel" instead of role="group".
[ ] Slide picker controls follow the Tabs Pattern.
[ ] Each control is a tab element, displaying the associated slide when activated.
[ ] Accessible name of each tab indicates the slide it will display.
[ ] Controls are grouped in a tablist element with an accessible name.

Grouped Carousel Elements:

[ ] Slide picker controls are in an element with role="group".
[ ] Group containing picker controls has an accessible label.
[ ] Each picker control is a native button element or implements the button pattern.
[ ] Accessible name of each picker button matches the slide it displays.
[ ] Current slide picker button has aria-disabled="true".

Problem Statement/Justification
none
Proposed Solution or API
No response
Alternatives
No response
Are you willing to participate in implementing this feature and create a pull request include the implementation?
None
Additional Information
No response
References
https://www.w3.org/WAI/ARIA/apg/patterns/carousel/

I try it.

Rotation Control Button:
Exists as a native button element or implements the button pattern.
Accessible label provided by aria-label or inner text.
Label changes based on action (e.g., "Stop slide rotation" or "Start slide rotation").
Button does not use aria-pressed.

In Yamada UI, the Rotation Control Button does not exist, so it is not included.

Next and Previous Slide Controls:

Exist as native button elements or implement the button pattern.

No problem because it uses Yamada UI's Button component internally.
Button component is compliant with native button elements.

Styled as arrows.

No problem because of the use of arrow icons.

Do not move focus when activated.

https://github.com/user-attachments/assets/06c899e4-ee20-405f-9682-cd15d22e760f
No problem, because after pressing the prev or next button, I can press the tab and then press the button as it is.

@uraaaa24
It is possible to control the rotation of the slide.Currently, the rotation stops when the pointer is moved over the slide.
I also feel that it was possible for the developer to place arbitrary buttons to stop the slide.


Updating Live with the latest changes in Main

Docs Build status updates of commit 5a7a4bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-1.0/MSOnline/Confirm-MsolDomain.md
:white_check_mark:Succeeded
View (azureadps-1.0)

azureadps-1.0/MSOnline/Set-MsolDomainAuthentication.md
:white_check_mark:Succeeded
View (azureadps-1.0)

azureadps-2.0-preview/AzureAD/New-AzureADMSAdministrativeUnit.md
:white_check_mark:Succeeded
View (azureadps-2.0-preview)

azureadps-2.0-preview/AzureAD/New-AzureADMSAdministrativeUnitMember.md
:white_check_mark:Succeeded
View (azureadps-2.0-preview)

azureadps-2.0-preview/AzureAD/Set-AzureADMSAdministrativeUnit.md
:white_check_mark:Succeeded
View (azureadps-2.0-preview)

azureadps-2.0/AzureAD/Get-AzureADGroupMember.md
:white_check_mark:Succeeded
View (azureadps-2.0)

azureadps-2.0/AzureAD/New-AzureADMSGroup.md
:white_check_mark:Succeeded
View (azureadps-2.0)

azureadps-2.0/AzureAD/New-AzureADServiceAppRoleAssignment.md
:white_check_mark:Succeeded
View (azureadps-2.0)

azureadps-2.0/AzureAD/Reset-AzureADMSLifeCycleGroup.md
:white_check_mark:Succeeded
View (azureadps-2.0)

docs-conceptual/azureadps-1.0/install-msonlinev1.md
:white_check_mark:Succeeded
View (azureadps-1.0)

docs-conceptual/azureadps-2.0-preview/new-user-sample.md
:white_check_mark:Succeeded
View (azureadps-2.0-preview)

docs-conceptual/azureadps-2.0-preview/signing-in-service-principal.md
:white_check_mark:Succeeded
View (azureadps-2.0-preview)

docs-conceptual/azureadps-2.0-preview/using-extension-attributes-sample.md
:white_check_mark:Succeeded
View (azureadps-2.0-preview)

docs-conceptual/azureadps-2.0/new-user-sample.md
:white_check_mark:Succeeded
View (azureadps-2.0)

docs-conceptual/azureadps-2.0/signing-in-service-principal.md
:white_check_mark:Succeeded
View (azureadps-2.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Link to http://www.prace-ri.eu/prace-repository-services/

not sure where to put this. Either change the section "Testing" to "Repository hosting and testing platforms" and add it there, or add section "Repository hosting"


Rework entire way SVUnit tests are written

The current way of writing unit tests suffers from the following problems:

it is way too verbose
it is very difficult for newcomers to comprehend
relies on a lot of scripting to put everything together

A new setup based on static initialization would help. We can look to GoogleTest for inspiration. C++ is similar to SV in certain respects, so a lot of concepts would carry over.

I'm curious - can you elaborate on your first two points (the third point is pretty obvious)?
If you're looking to Google Test for inspiration, I'll mention one thing I like about it that I can't do with svunit (or vunit for that matter): all it needs is including a header and to compile with that header. There are no scripts that run the tests -- an executable that runs the tests is simply created based on the build tools that the user is working with. With Google Test, that build tool is usually CMake, but with SystemVerilog, that could be anything (GNU Make, Bazel, a company-internal tool, etc.)

Regarding point number 1, I mean that the user has to write a lot of boilerplate: write a _unit_test module, make sure that it contains an instance of svunit_testcase with the correct name, build that instance, write buid, setup and teardown, even if not used, implement these functions, etc. This feeds into point number 2.

I'll elaborate on point 3 anyway. This is connected to the boilerplate mentioned in number 1, because that code is needed to create the entire infrastructure to run tests. Again, this feeds into point 2, as it's difficult for newcomers to know what is needed to keep SVUnit happy and what is actual test code.

Regarding build, it is also my vision to do most in SystemVerilog (if not all, but that won't be possible - think about #105, for example) and have the scripting do as little as possible, thus making it optional for users who already have a build system they want to integrate with.


[BUG]Volume expansion will succeed even if the volume scheduling fails

Describe the bug
This issue is similar to #1361
To Reproduce
Steps to reproduce the behavior:

Create a volume with (N+1) replicas in the N-node Longhorn cluster.
Expand the volume for multiple times

Expected behavior
The API call should be disabled or should fail.
Environment:

Longhorn version: v1.0.0-rc1

Manual test 1:

Create a volume with (N+1) replicas in the N-node Longhorn cluster.
Verify the volume scheduling failure.
Try to expand the volume and get an error.

Manual test 2:

Create a volume with N replicas in the N-node Longhorn cluster.
Attach the volume and write some data.
Disable scheduling for one node and delete the related replica of the volume.
Verify the volume scheduling failure.
Detach the volume.
Verify that the failed replica is removed and volume scheduling failure is gone.
Try to expand the volume and wait for expansion success.
Attach the volume and verify the existing data.
Write more data to the volume.
Enable the scheduling for the node.
Repeat step 3 ~ 10

Note: we should require the volume to be healthy before it can be resized.
Hmm? If the volume is detached then we allow resizing? I am confused.

After step 5 of test 2, the volume contains healthy replicas only hence the expansion is fine.
If there is still scheduling failed replica after the detachment, the volume cannot be reattached/reused again, that would be a bug.

That means when we attach the volume, the rebuild progress will also start along with volume expansion?

No. The rebuild is disabled for auto attached volumes. (Restoring volume, expanding volume, DR volume). See the fix for #1270

Pre-merged Checklist

[x] Does the PR include the explanation for the fix or the feature?
[ ] Is the backend code merged?
[x] Is the reproduce steps/test steps documented?
[x] If labeled: area/ui Has the UI issue filed or ready to be merged?
[ ] If labeled: require-automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case?
[x] if labeled: require-automation-engine Has the engine integration test been merged?
[x] if labeled: require-doc Has the necessary document PR submitted or merged?

The fix of UI part:
Gray out the button Expand Volume when volume.conditions[scheduled].status == false && v. state == "detached"

Reproduced issue on 1.0.0-rc1
Steps:

Create a volume with (N+1) replicas in the N-node Longhorn cluster with volume size 20G
Expand the volume to 25G
Replicas are seen running and when they come in detached mode, only N replicas are available and Ready for workload:Ready

Validated on the latest master - 05/22/2020 - Ui tag: 9ab6368 and at 12:00 PDT

Create a volume with (N+1) replicas in the N-node Longhorn cluster with volume size 20G
Expand the volume to 25G
Error is seen, volume does not expand. unable to expand volume test-issue-2: cannot expand volume before replica scheduling success
Volume is seen in

Scheduling Failure
Replica Scheduling Failure

@sowmyav27 The PR was merged after rc1, can you retry with the master?

Validated on latest master -05/22/2020, ui tag: 8307588
Steps:

Create a volume with (N+1) replicas in the N-node Longhorn cluster with volume size 20G when node soft affinity: False
the volume will be in detached state with message:

Scheduling Failure
Replica Scheduling Failure

Expand Volume option is not enabled in the UI
When trying to expand volume from API v1/volumes/<volume-name>
Error seen

{
"actions": { },
"code": "Server Error",
"detail": "",
"links": {
"self": "…/v1/volumes/test-2",
},
"message": "unable to expand volume test-2: cannot expand volume before replica scheduling success",
"status": 500,
"type": "error",
}


go-sdk 1.10.0 still depends on dapr 1.13.0-rc.7

When you go mod tidy with reference to v1.10.0 go-sdk, you see state dapr runtime dependency.
require (
    github.com/dapr/go-sdk v1.10.0
    github.com/gorilla/mux v1.8.1
)

require (
    github.com/dapr/dapr v1.13.0-rc.7 // indirect

I think that's simply because this go.mod for the sdk needed to be bumped:
https://github.com/dapr/go-sdk/blob/release-1.10/go.mod#L6

Closed by #528


Canonicalized Media Types

Is your feature request related to a problem? Please describe.
Now that Zarf has been donated it would be nice to have canonicalized media types (either accepting the existing ones or changing to openssf) to add logic on Zarf package handling (particularly OCI packages) to other projects.
Describe the solution you'd like
Zarf Config and Layer media types to be documented / supported for incorporation in other projects (i.e. Renovate, GitLab, etc).
Describe alternatives you've considered
We could push these projects to move away from media types (since by the newer OCI specifications these could be anything) but there are cases where specific annotations or handling may want to be implemented regardless.
Additional context
Some projects handle OCI artifacts only for specific media types and having a canonical media type for Zarf would allow this to be PRed into these projects.

@salaxander @schristoff did we ever decide on this?


Model name can not be made unique to a given automl config / pipeline.

Say for example, that the many models training accelerator (MMA) is to be used with two different automl configs in two pipelines but the same training data and partitions. The registered models will have the same names in the registry.  There is, as far as I can see currently no way to append information to the model name to make it unique in this situation.
I suggested solution would be to allow the user to optionally pass in a model name prefix or suffix. It then becomes the API consumers responsibility to make the name unique in what ever scope they choose.

We can combine and track this feedback and request within this issue: https://github.com/microsoft/solution-accelerator-many-models/issues/132
Closing, but please reopen if you feel it is not adequately addressed.


Add ITU-R BS.1770-4 Loudness

🚀 Feature
Implement a standard algorithm for computing audio loudness, like ITU-R BS.1770-4.
Motivation
Audio loudness is an important feature for representing audio. For example, it's used in this popular library: https://github.com/magenta/ddsp
Pitch
Here is a numpy implementation of ITU-R BS.1770-4. It'd be helpful to have this translated to PyTorch and included in this library: https://github.com/csteinmetz1/pyloudnorm/blob/master/pyloudnorm/meter.py
Here is the official loudness implementation from the original paper: https://github.com/BrechtDeMan/loudness.py/blob/master/loudness.py

Hi @PetrochukM
Sounds good idea. Couple of clarification questions;

What are the differences between the csteinmetz1 implementation and BrechtDeMan?
Are these implementations work for float dtype within the range of [-1.0, 1.0] or do they expect integer type?
What is the equivalent found in DDSP? Is the API there good to follow?

Hi @PetrochukM
Sounds good idea. Couple of clarification questions;

What are the differences between the csteinmetz1 implementation and BrechtDeMan?
Are these implementations work for float dtype within the range of [-1.0, 1.0] or do they expect integer type?
What is the equivalent found in DDSP? Is the API there good to follow?

Thanks for the questions:

"csteinmetz1" includes multiple loudness implementations, including "BrechtDeMan". They have a filter_class called "DeMan".
They both expect floating dtype for the audio.
a. In DDSP, they implemented loudness here: https://github.com/magenta/ddsp/blob/5a06bced8e4b2f77aabe418d07f7279fe237daff/ddsp/spectral_ops.py#L184
Their loudness implementation is A-weighted, instead of K-weighted, like in ITU-R BS.1770-4. They also calculate loudness with a spectrogram, instead of the raw audio. Either way, the calculation of loudness can be done either way, equivalently. They also don't filter out quiet frames before calculating the audio loudness, as recommended in ITU-R BS.1770-4.
b. I have not used their API in the past, so I don't have a good gauge of its effectiveness. Their library is only "used by" 5 people based on Github statistics.

Thanks for the questions:

"csteinmetz1" includes multiple loudness implementations, including "BrechtDeMan". They have a filter_class called "DeMan".
They both expect floating dtype for the audio.
a. In DDSP, they implemented loudness here: https://github.com/magenta/ddsp/blob/5a06bced8e4b2f77aabe418d07f7279fe237daff/ddsp/spectral_ops.py#L184
Their loudness implementation is A-weighted, instead of K-weighted, like in ITU-R BS.1770-4. They also calculate loudness with a spectrogram, instead of the raw audio. Either way, the calculation of loudness can be done either way, equivalently. They also don't filter out quiet frames before calculating the audio loudness, as recommended in ITU-R BS.1770-4.
b. I have not used their API in the past, so I don't have a good gauge of its effectiveness. Their library is only "used by" 5 people based on Github statistics.


Support for multi-FASTA

Codecov Report

Merging #74 into master will decrease coverage by 50.06%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##           master      #74       +/-   ##
===========================================
- Coverage   91.62%   41.56%   -50.07%
===========================================
  Files           5        5
  Lines         227      243       +16
  Branches       34       41        +7
===========================================
- Hits          208      101      -107
- Misses         16      132      +116
- Partials        3       10        +7


Upgrade to Ember 3.10

What is this?
This should close all the dependabot PRs and upgrade the addon to latest using ember init

Looks like I forgot to lint before pushing. The tests should pass now 🤞