refactor(theme-classic): color mode toggle button fixes

Motivation
The button should be accessible, semantically correct, and consistent with the general style of site. Also removed some dead code, which is unnecessary given that the <button> element is used.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Preview.
Related PRs

Not blocking this PR but I also have this other refactor with a new NavbarColorModeToggle here: https://github.com/facebook/docusaurus/pull/6895/files#diff-51072c1a59c9c7f1396c4aaf865423fe896bf8408a9efb763e8ce832e526934a
I'll update my PR after merging yours.
Similarly I don't like the existing hook assuming color mode can only be 2 values, ie const {isDarkTheme, toggle} = useColorMode();

TBH, adding a third color mode choice would be a huge change because it means any existing UI/UX won't work. I'd rather change the API until we actually make that happen. I haven't seen any content site with more than two color modes.

I haven't seen any content site with more than two color modes.

I have seen a few sites with more than light/dark theme.
In the past, before dark theme was popular, there were so many example of sites/forums providing multiple themes too.
The CSS explains that prefers-color-scheme is likely to be extended

There are also large scale websites implementing alternative color schemes for accessibility reasons, like GitHub: https://github.blog/changelog/2021-09-29-colorblind-themes-beta/
In general, every single time I didn't apply pre-emptive pluralization (https://www.swyx.io/preemptive-pluralization) it ends up bitting me a few months/years later, so I really prefer to do this now when the pain is still low

I was carefully saying "content sites" to rule out GitHub 😄 These sites offering choices often has a centralized settings panel which is probably an overkill for a content site, especially a documentation site.
That said, I'm not against the idea of having multiple color themes. But at that time we can't use either a button or a toggle whatsoever.

I think this is good now. Can confirm everything works, even our wrapped color mode toggle


Add onBeforeAdd to SelectArrayInput

Added new function - onBeforeAdd to SelectArrayInput. this was needed to be able to transfrom the new value to a different value based on some conditions and even to stop adding a new  value based on some conditions
Real usecase: choices are provided by server side, if user add new value with same letters but different letter case ("FrEe" against "free") it added a new value which we didnt want. to prevent that I added the onAddBefore so we could transform the "FrEe" to "free". also I was able to prevent duplication of same tag more than once.

Why can't you use redux-form's parse, which you can specify as a custom prop on every input in admin-on-rest?


Introduce omitempty option for Go

Hello,
This PR relates to #102
.proto example:
message Request {
  string id = 1 [(validate.rules).string = {min_len: 6, omitempty: true}];
  uint64 created = 2 [(validate.rules).uint64 = {gt:<PHONE_NUMBER>953150044, omitempty:true}];
}

Results in following code being generated:
if m.GetId() != "" {
		if utf8.RuneCountInString(m.GetId()) < 6 {
			return TapRequestValidationError{
				field:  "Id",
				reason: "value length must be at least 6 runes",
			}
		}
	}

	if m.GetCreated() != 0 {
		if m.GetCreated() <=<PHONE_NUMBER>953150044 {
			return TapRequestValidationError{
				field:  "Created",
				reason: "value must be greater than<PHONE_NUMBER>953150044",
			}
		}
	}

I added this option for following types:

bytes
map
string
all numeric types
repeated

IMO adding this option for other types doesn't make much sence.
Please take a look and if it's conceptually ok I can continue working on this PR add tests docs etc.
Thanks for the great project!

@rodaine cay you please take a look?

+1 This really needs to be looked at, I was surprised this wasn't an option already

@rodaine minus the few issues above (that are easy to fix), this looks like a very reasonable implementation, and this is a major issue - we really could use this getting fixed. Can you take a look and can we get this in? This would be very appreciated.

@hexdigest CircleCI is failing on the vendor issues as well https://circleci.com/gh/envoyproxy/protoc-gen-validate/896 I would fix this before the maintainers come back and look at this :-)

@hexdigest let me know if you need some help with this, happy to help out

@bufdev I'm almost finished actually but I'm having lots of struggles with bazel like #290
I created a new branch here but most of the jobs in the Makefine simply do not work for me on both this branch and on the master.

Is there something I can do to make this go further? We really need omitempty since the lack of it basically breaks any validation attempt on optional fields.

The bazel build should be fixed now in master. Can you please merge master and resolve conflicts?

@hexdigest ping :-)

Can we please implement this?

The bazel build should be fixed now in master. Can you please merge master and resolve conflicts?

@hexdigest can you please merge master? We would love to use this as well!

We'd love too, please!

@Rubenvdveen @bkleef @darioielardi please move to this PR


Instructions for finding account_id only work if you have a zone

When you generate a new project, Wrangler writes:
You can find your account_id and zone_id in the right sidebar of the zone overview tab at https://dash.cloudflare.com

This only works if you have a zone, but if you're using workers.dev exclusively, then you don't have any zone pages and so the mentioned sidebar doesn't show up anywhere.
I couldn't find anywhere in the UI that showed my account ID in this case. However, the account ID does appear in the URL.

mm - we should update to point them to the account-level workers page. i believe it's on the right panel in that case

correct. but also more than likely this belongs in docs.

Huh somehow I missed that the account ID shows up on the Workers page. I thought I looked there.

but also more than likely this belongs in docs.

Docs are great, but they wouldn't be a replacement for this message.

i'm a dingus and thought you were talking about the readme. saying "account home"  is probably  ideal.

Problem is that the account home doesn't actually have your account ID on it. :(
It looks like we can't directly link to the worker page either, unless we already know the user's account ID... ugh.
This will all be solved when we support an OAuth flow for configuration, of course...

mm - i dont think it'll be solved with oauth since you'll still need to specify account + zone id.
also - don't we have deeplinks or something? cc @neynah

With OAuth, presumably you'd type wrangler login or whatever and then it would open a tab in your browser where you select which account you want, etc. No need to tell people to hunt for an ID to copy/paste...

hmm. yeah - we dont store account_id or zone_id globally since folks often have more than one of each, so they are per-project configuration instead of global configuration like your api key. would probably be nice to spit out list of available account ids when you would run wrangler login like we do now with wrangler whoami

Ohhh, I didn't know about wrangler whoami. Maybe this message here should really direct people to run that. It's much easier than digging around in the dashboard for an account ID...
I guess it's a little weird that our config file mixes deployment information with source code... seems like that makes it hard to, say, have an open source worker on github that anyone can deploy to their own account. Wonder if it makes sense to put account ID and script name in a separate file that could optionally not be checked in, or something.

wrangler whoami

yas

I guess it's a little weird that our config file mixes deployment information with source code... seems like that makes it hard to, say, have an open source worker on github that anyone can deploy to their own account. Wonder if it makes sense to put account ID and script name in a separate file that could optionally not be checked in, or something

this has definitely introduced issues. i think wrangler login and whoami could be instrumental in fixing this problem

agreed @kentonv - i think we should definitely think about ways to better support per-developer settings that dont get checked in to version control.


pecl install grpc-1.27.0 fails

What version of gRPC and what language are you using?
1.27.0
What operating system (Linux, Windows,...) and version?
Alpine Linux 3.11
What runtime / compiler are you using (e.g. python version or version of gcc)
g++-9.2.0-r3
What did you do?
cat >Dockerfile <<EOF
FROM php:7.4-fpm-alpine

RUN apk add --update autoconf g++ make zlib-dev
RUN pecl install grpc-1.27.0 && docker-php-ext-enable grpc
EOF

docker build --no-cache .

What did you expect to see?
A successful build
What did you see instead?
.
.
.
g++ -fvisibility=hidden -DOPENSSL_NO_ASM -D_GNU_SOURCE -DWIN32_LEAN_AND_MEAN -D_HAS_EXCEPTIONS=0 -DNOMINMAX -DGRPC_ARES=0 -DGRPC_POSIX_FORK_ALLOW_PTHREAD_ATFORK=1 -I. -I/tmp/pear/temp/grpc -DPHP_ATOM_INC -I/tmp/pear/temp/pear-build-defaultuserplJEAe/grpc-1.27.0/include -I/tmp/pear/temp/pear-build-defaultuserplJEAe/grpc-1.27.0/main -I/tmp/pear/temp/grpc -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib -I/tmp/pear/temp/grpc/include -I/tmp/pear/temp/grpc/src/core/ext/upb-generated -I/tmp/pear/temp/grpc/src/php/ext/grpc -I/tmp/pear/temp/grpc/third_party/abseil-cpp -I/tmp/pear/temp/grpc/third_party/address_sorting/include -I/tmp/pear/temp/grpc/third_party/boringssl/include -I/tmp/pear/temp/grpc/third_party/upb -DHAVE_CONFIG_H -std=c++11 -fno-exceptions -fno-rtti -g -O2 -c /tmp/pear/temp/grpc/third_party/abseil-cpp/absl/base/internal/spinlock_wait.cc  -fPIC -DPIC -o third_party/abseil-cpp/absl/base/internal/.libs/spinlock_wait.o
In file included from /tmp/pear/temp/grpc/third_party/abseil-cpp/absl/base/internal/spinlock_wait.cc:27:
/tmp/pear/temp/grpc/third_party/abseil-cpp/absl/base/internal/spinlock_linux.inc:17:10: fatal error: linux/futex.h: No such file or directory
   17 | #include <linux/futex.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:1046: third_party/abseil-cpp/absl/base/internal/spinlock_wait.lo] Error 1
ERROR: `make' failed
The command '/bin/sh -c pecl install grpc-1.27.0 && docker-php-ext-enable grpc' returned a non-zero code: 1

Anything else we should know about your project / environment?

Esun, this looks like another absl issue.

linux-headers needs to be installed for missing linux/futex.h file.


NO_PROXY variable for npm

Patch to setup npm to use $no_proxy

LGTM.
Thanks for the contribution.
Also don't need to bother with the CI error for now, that unstable behavior happened before.
https://travis-ci.org/nodeshift/centos7-s2i-web-app/builds/554295648#L388

Lets not forget to also bring this into the 12.x and 10.x branches


pkgdev mask: Extend comment template, support -b/--bugs

A two-in-one :-) I'll extend the test cases as well.

pkgdev mask: Extend mask comment template
To aid developers in writing comments for package.mask, extend the
comment in the temporary file to include example comments.
This is copied straight from the profiles/package.mask file in ::gentoo,
except I've left out the author line and the actual mask line (those are
added automatically).

pkgdev mask: Accept -b/--bug for referencing bugs
When masking a package - and especially last-riting - the author should
provide bug references. When --bug is given, the comment template is
expanded to include the bug refs.

Oh, this was inspired from #36

@radhermit Any additional feedback? I didn't implement the csv_append change you suggested, but only because it didn't work for me - and then I also figured that the current implementation is more in line with pkgdev mask.

@radhermit Any additional feedback? I didn't implement the csv_append change you suggested, but only because it didn't work for me - and then I also figured that the current implementation is more in line with pkgdev mask.

Yep, using both a custom action and a custom type generally requires specific handling that I didn't include in the example code. Other than that, I think you resolved the things I've mentioned at a quick glance.

@radhermit Any additional feedback? I didn't implement the csv_append change you suggested, but only because it didn't work for me - and then I also figured that the current implementation is more in line with pkgdev mask.

Yep, using both a custom action and a custom type generally requires specific handling that I didn't include in the example code. Other than that, I think you resolved the things I've mentioned at a quick glance.

Alright, I'll leave it as-is for now. Thanks for all the input!

I will try to use this locally on my machine and look how it works. This might take 1-2 days. After that I think we can merge it.

OK, let me know if you want any changes in there.

Well, it took some more time that the original 1-2 days, but no issues were found.
@laumann Great job!


wasm: shared data and shared queue leak on VM change

vm_id is used as part of the key in the shared data and shared queue. When a VM is gone, the state is not cleaned up.
Ref: https://github.com/istio/istio/issues/27783

once update cpp-host to the latest, this is closed via https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/114


HDFS-16822. HostRestrictingAuthorizationFilter should pass through requests if they don't access WebHDFS API.

Description of PR
After HDFS-15320, HostRestrictingAuthorizationFilter returns 404 error if it receives a request that doesn't access WebHDFS API. With this change, the endpoints, such as /conf and /jmx are no longer visible. This is very inconvenient for administrators. HostRestrictingAuthorizationFilter should pass through requests if they don't access WebHDFS API.
How was this patch tested?

verify the unit test
verify it in my local cluster

For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m  8s

trunk passed

+1 :green_heart:
compile
1m 35s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
1m 27s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 16s

trunk passed

+1 :green_heart:
mvnsite
1m 36s

trunk passed

+1 :green_heart:
javadoc
1m 25s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 35s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 45s

trunk passed

+1 :green_heart:
shadedclient
23m  8s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 21s

the patch passed

+1 :green_heart:
compile
1m 25s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
1m 25s

the patch passed

+1 :green_heart:
compile
1m 15s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  2s

hadoop-hdfs-project/hadoop-hdfs: The patch generated 0 new + 13 unchanged - 1 fixed = 13 total (was 14)

+1 :green_heart:
mvnsite
1m 25s

the patch passed

+1 :green_heart:
javadoc
0m 55s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 26s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 23s

the patch passed

+1 :green_heart:
shadedclient
22m 38s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
240m 36s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m  3s

The patch does not generate ASF License warnings.

350m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5079/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5079

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux c82275ecf8a1 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 49e59412f1644c83346fefc8f59dc72641e68a47

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5079/1/testReport/

Max. process+thread count
3006 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5079/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Thanks for your reviews, @ashutoshcipher and @tomscut. I will merge it.


Decoding multiple tracks

Using the /loadtracks endpoint returns lavaplayer encoded tracks that are almost always decoded immedietly after using the /decodetrack endpoint to get track info. When used with a playlist of hundreds of songs or a search result this can lead to hundreds of calls to the decode endpoint.
Proposed solutions:
Solution 1: Providing track info with each track in the /loadtracks endpoint.
GET /loadtracks?identifier=dQw4w9WgXcQ&info=true
{
  "tracks": [
    {
      "track": "AAAA==",
      "info": {
        "title": "48 hours of screaming",
        ...
      }
    }
  ]
}

Advantage: No additional requests have to be made to load tracks and view track info.
Disadvantage: Modifies the existing response format which could make existing clients incompatible with the endpoint.
Solution 2: Decoding multiple tracks in the /decodetrack endpoint.
GET /decodetrack?tracks=AAAA==,BBBB==,CCCC==,...
[
  {
    "track": "AAAA==",
    "info": {
      "title": "48 hours of screaming",
      ...
    }
  },
  ...
]

Advantage: The endpoint was added yesterday so it is unlikely that changing the response format would lead to incompatible clients.
Disadvantages:

One additional request has to be made to decode tracks whereas with solution 1 it is not required.
URLs have a length limit (iirc) so decoding hundreds of tracks will not be possible.

I suggest you should be using POST requests to decode tracks in bulk


Upgrade the Kubernetes cluster on Hetzner machine

Proposition
The version of the Kubernetes cluster deployed on the dedicated Hetzner machine is a bit outdated and should be upgraded to a more recent which supports to renew automatically k8s certificate, .....
kc get node/centos-77-64-minimal
NAME                   STATUS   ROLES    AGE    VERSION
centos-77-64-minimal   Ready    master   405d   v1.14.9

As kubeadm client proposes a command in order to upgrade an existing cluster, we should detail here how such a process could take place (example: do we have to backup before to upgrade, can we do a dry-run such as : kubeadm upgrade apply --dry-run, ...) ?
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/
WDYT ? @jacobdotcosta

I think we should either have a backup of that server prior to launching the migration process, or clone it onto a dev host to test the migration process.

I think we should either have a backup of that server prior to launching the migration process, or clone it onto a dev host to test the migration process.

a backup of that server

Making a backup of a k8s cluster is not so easy. What do you suggest (if needed) as strategy ?

a backup of that server

Making a backup of a k8s cluster is not so easy. What do you suggest (if needed) as strategy ?

or clone it onto a dev host to test the migration process.

Again. Not so easy to be done. We need the advise of K8s Ops expert for that ;-)

or clone it onto a dev host to test the migration process.

Again. Not so easy to be done. We need the advise of K8s Ops expert for that ;-)

FYI
CentOS-77-64-minimal:~$ kubeadm upgrade plan
[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[upgrade] Fetching available versions to upgrade to
[upgrade/versions] Cluster version: v1.14.9
[upgrade/versions] kubeadm version: v1.14.9
I0128 11:59:09.863122    1125 version.go:240] remote version is much newer: v1.20.2; falling back to: stable-1.14
[upgrade/versions] Latest stable version: v1.14.10
[upgrade/versions] Latest version in the v1.14 series: v1.14.10

Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT   CURRENT       AVAILABLE
Kubelet     1 x v1.14.9   v1.14.10

Upgrade to the latest version in the v1.14 series:

COMPONENT            CURRENT   AVAILABLE
API Server           v1.14.9   v1.14.10
Controller Manager   v1.14.9   v1.14.10
Scheduler            v1.14.9   v1.14.10
Kube Proxy           v1.14.9   v1.14.10
CoreDNS              1.3.1     1.3.1
Etcd                 3.3.10    3.3.10

You can now apply the upgrade by executing the following command:

	kubeadm upgrade apply v1.14.10

Note: Before you can perform this upgrade, you have to update kubeadm to v1.14.10.

FYI
CentOS-77-64-minimal:~$ kubeadm upgrade plan
[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[upgrade] Fetching available versions to upgrade to
[upgrade/versions] Cluster version: v1.14.9
[upgrade/versions] kubeadm version: v1.14.9
I0128 11:59:09.863122    1125 version.go:240] remote version is much newer: v1.20.2; falling back to: stable-1.14
[upgrade/versions] Latest stable version: v1.14.10
[upgrade/versions] Latest version in the v1.14 series: v1.14.10

Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT   CURRENT       AVAILABLE
Kubelet     1 x v1.14.9   v1.14.10

Upgrade to the latest version in the v1.14 series:

COMPONENT            CURRENT   AVAILABLE
API Server           v1.14.9   v1.14.10
Controller Manager   v1.14.9   v1.14.10
Scheduler            v1.14.9   v1.14.10
Kube Proxy           v1.14.9   v1.14.10
CoreDNS              1.3.1     1.3.1
Etcd                 3.3.10    3.3.10

You can now apply the upgrade by executing the following command:

	kubeadm upgrade apply v1.14.10

Note: Before you can perform this upgrade, you have to update kubeadm to v1.14.10.

I was thinking about install another k8s 1.14 cluster and deploying our applications over there.
Having removed the pods in the cert-manager, kube-system and kubernetes-dashboard namespaces we'd "only" have to deploy these:
NAMESPACE              NAME                                           READY   STATUS    RESTARTS   AGE
bot                    snowdrop-bot-869bc47486-hm5rf                  1/1     Running   3          80d
halkyon-site           halkyon-nginx-8c479974d-wwsbb                  1/1     Running   4          405d
snowdrop-site          snowdrop-site-angular-774dd56856-89p6x         1/1     Running   4          405d
snowdrop-site          spring-boot-generator-6587865b98-qspx4         1/1     Running   3          246d

I was thinking about install another k8s 1.14 cluster and deploying our applications over there.
Having removed the pods in the cert-manager, kube-system and kubernetes-dashboard namespaces we'd "only" have to deploy these:
NAMESPACE              NAME                                           READY   STATUS    RESTARTS   AGE
bot                    snowdrop-bot-869bc47486-hm5rf                  1/1     Running   3          80d
halkyon-site           halkyon-nginx-8c479974d-wwsbb                  1/1     Running   4          405d
snowdrop-site          snowdrop-site-angular-774dd56856-89p6x         1/1     Running   4          405d
snowdrop-site          spring-boot-generator-6587865b98-qspx4         1/1     Running   3          246d

FYI
CentOS-77-64-minimal:~$ kubeadm upgrade plan
[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[upgrade] Fetching available versions to upgrade to
[upgrade/versions] Cluster version: v1.14.9
[upgrade/versions] kubeadm version: v1.14.9
I0128 11:59:09.863122    1125 version.go:240] remote version is much newer: v1.20.2; falling back to: stable-1.14
[upgrade/versions] Latest stable version: v1.14.10
[upgrade/versions] Latest version in the v1.14 series: v1.14.10

Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT   CURRENT       AVAILABLE
Kubelet     1 x v1.14.9   v1.14.10

Upgrade to the latest version in the v1.14 series:

COMPONENT            CURRENT   AVAILABLE
API Server           v1.14.9   v1.14.10
Controller Manager   v1.14.9   v1.14.10
Scheduler            v1.14.9   v1.14.10
Kube Proxy           v1.14.9   v1.14.10
CoreDNS              1.3.1     1.3.1
Etcd                 3.3.10    3.3.10

You can now apply the upgrade by executing the following command:

	kubeadm upgrade apply v1.14.10

Note: Before you can perform this upgrade, you have to update kubeadm to v1.14.10.

What does remote version is much newer: v1.20.2; falling back to: stable-1.14 mean, that it will only upgrade to 1.14.10?

FYI
CentOS-77-64-minimal:~$ kubeadm upgrade plan
[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[upgrade] Fetching available versions to upgrade to
[upgrade/versions] Cluster version: v1.14.9
[upgrade/versions] kubeadm version: v1.14.9
I0128 11:59:09.863122    1125 version.go:240] remote version is much newer: v1.20.2; falling back to: stable-1.14
[upgrade/versions] Latest stable version: v1.14.10
[upgrade/versions] Latest version in the v1.14 series: v1.14.10

Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT   CURRENT       AVAILABLE
Kubelet     1 x v1.14.9   v1.14.10

Upgrade to the latest version in the v1.14 series:

COMPONENT            CURRENT   AVAILABLE
API Server           v1.14.9   v1.14.10
Controller Manager   v1.14.9   v1.14.10
Scheduler            v1.14.9   v1.14.10
Kube Proxy           v1.14.9   v1.14.10
CoreDNS              1.3.1     1.3.1
Etcd                 3.3.10    3.3.10

You can now apply the upgrade by executing the following command:

	kubeadm upgrade apply v1.14.10

Note: Before you can perform this upgrade, you have to update kubeadm to v1.14.10.

What does remote version is much newer: v1.20.2; falling back to: stable-1.14 mean, that it will only upgrade to 1.14.10?

What does remote version is much newer: v1.20.2; falling back to: stable-1.14 mean, that it will only upgrade to 1.14.10?

Existing documentation always refers as migration path 1.14 -> 1.15 or 1.15 -> 1.16, ... but no big jump from 1.14 to 1.18 - https://v1-16.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/

What does remote version is much newer: v1.20.2; falling back to: stable-1.14 mean, that it will only upgrade to 1.14.10?

Existing documentation always refers as migration path 1.14 -> 1.15 or 1.15 -> 1.16, ... but no big jump from 1.14 to 1.18 - https://v1-16.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/

The following bash script could be used to do the rollout
#!/bin/bash

# declare -a Versions=("1.14.10" "1.15.15" "1.16.15" "1.17.17" "1.18.15" "1.19.7" "1.20.2")
declare -a Versions=("1.19.7" "1.20.2")
MASTER=centos7.localdomain

for VERSION in ${Versions[@]}; do
   echo "K8s version to be upgraded to : $VERSION"
   sudo yum install -y kubeadm-$VERSION --disableexcludes=kubernetes
   sudo kubeadm upgrade apply v$VERSION -y
   sudo kubectl --kubeconfig=.kube/config drain $MASTER --ignore-daemonsets --delete-local-data
   sudo yum install -y kubelet-$VERSION kubectl-$VERSION --disableexcludes=kubernetes
   sudo systemctl daemon-reload
   sudo systemctl restart kubelet
   sudo kubectl --kubeconfig=.kube/config uncordon $MASTER
done

I started the process and migrated the K8s cluster from 1.14 to 1.15.

During the upgrade from 1.15 to 1.16, the following error was reported by the node kubectl get node/centos-77-64-minimal -o yaml
network plugin is not ready: cni config uninitialized

The fix, as described here:  https://github.com/kubernetes/kubernetes/issues/48798 has been to apply the following resource
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

Following issue has been experimented during upgrade from 1.16 to 1.17
- lastHeartbeatTime: "2021-05-17T12:23:34Z"
    lastTransitionTime: "2021-05-17T12:15:08Z"
    message: 'Failed to initialize CSINode: error updating CSINode annotation: timed
      out waiting for the condition; caused by: the server could not find the requested
      resource'
    reason: KubeletNotReady
    status: "False"

and fixed with: https://rahulschoudhari.wordpress.com/2020/06/16/kubeletnotready-failed-to-initialize-csinode/
@jacobdotcosta : FYI.

Cluster has been successfully migrated to version 1.19.11 today. FYI: @aureamunoz @iocanel @jacobdotcosta @gytis @metacosm
Can you check if web site, bot, ... are working correctly ?


Introduce Entity column option for Protobuf Entity state definitions

Currently, the entity columns are defined in Java with @Column annotation.
While this is convenient, it's completely invisible for those who use them for querying or subscribing to Entity state updates.
Therefore it is proposed to introduce a (column) option.
message UserProfile {
    option (entity).kind = PROJECTION;

    UserId id = 1;

    // ...

    // When this user was registered in the system.
    google.protobuf.Timestamp when_registered = 7 [(required) = true];

    // A year of user's registration in the system.
    int32 year_of_registration = 8 [(column) = true];
}

A presence of [(column) = true] implies optionality of the marked field.
End-users will have two options to set the value for the column:

Use Spine-generated interface when declaring their entity. E.g.

interface UserProfileWithColumns extends EntityWithColumns {

    int getYearOfRegistration();
}

// ...
class UserProfileProjection
            extends Projection<UserId, UserProfile, UserProfile.Builder>
            implements UserProfileWithColumns { ... }

In which case this method becomes mandatory for implementation. The framework routines will then be able to call the methods in all T extends EntityWithColumns entity classes.

Fill the value in manually when updating the Entity state.

In both cases, the year_of_registration column value should be finalized by the moment of transaction commit. If an end-user decides to leave it empty — that's what the framework will count as an intentional action.
In this way, the dictionary of the language shared between a server and its clients will have a clear notion of what can be used for querying and subscribing.

Closed with base#492, #1184.


root can be undefined during traversal

The new version crashes for me on this line: https://github.com/gaearon/react-deep-force-update/blob/master/src/index.js#L65 . Using React v15
This happens on a div that has html content set. Neither of the two attributes are there, but interestingly there is a instance.__reactInternalInstance$wfzkogjc2v, not sure what creates that.
Would it be sufficient to just guard against undefined root and return?

Just tried guarding and returning undefined, doesn't work :(

I take that back, when I uninstall https://chrome.google.com/webstore/detail/react-sight/aalppolilappfakpmdfdkpppdnhpgifn it works again…


Enable support for Rails 7.1

Enables support for all Rails 7 minor releases by restricting dependency to below 8.0, which allows the gem to be installed on Rails 7.1, which was released two weeks ago.
This is inline with updates to support previous major Rails versions, which did not specify a minor release. Examples of previous wysiwyg-rails.gemspec changes after each release:

Bump for Rails 5: https://github.com/froala/wysiwyg-rails/commit/889336ee8d293fbd7f4afc8f2841538413396879
Bump for Rails 6: https://github.com/froala/wysiwyg-rails/commit/8b8c9eae1a60785e8acaad582cbc925023df1972
Original for Rails 4: https://github.com/froala/wysiwyg-rails/commit/0f713c929e37dee4360204909d2ae3c45712518

:+1:  for this please

@justisb  you'll also need to bump the version to 4.1.4 (https://github.com/Popmenu/wysiwyg-rails/blob/rails-7-1/lib/wysiwyg-rails/version.rb)

I believe they keep their version numbers inline with the main Froala releases, e.g. https://froala.com/wysiwyg-editor/changelog/

@harasunu-narayan Any idea when we may be able to get his minor dependency update merged?

@justisb
I think we can close this PR.
This one has been fixed in the commit https://github.com/froala/wysiwyg-rails/commit/87901ed4cb9ea6974c18bf44318b2372085e5d3a#diff-89e7d299629c1014d0f2ac27184582bc530fa6018fcb612faffe9e4489f4b292R17

Fixed by https://github.com/froala/wysiwyg-rails/commit/87901ed4cb9ea6974c18bf44318b2372085e5d3a#diff-89e7d299629c1014d0f2ac27184582bc530fa6018fcb612faffe9e4489f4b292R17.


Getting errors quite regularly in practice

We have this running as a CI job, it probably gets run 8 or 10 times a day and currently is failing about 50% of the time. I've attached some screenshots of the logs. It looks like maybe observatory is doing some throttling but then the retries are too close together and it gets blocked, not quite sure though.
Happy to try to help with a PR if you have an idea where to start looking?
Thanks,
Chris

Hi Chris,
Thanks for this.
I've seen this myself and had retries put at 30 within the action in order to try and counter that.
I do think Observatory throttles, and in their docs they recommend running your own version of the tool - I believe via docker.
Let me do a deeper dig.
All contributions welcome of course, the code for this project is fairly light, it's just exec'ing the observatory CLI.

At first glance I would say the problem lies in the underlying CLI, here:
https://github.com/mozilla/observatory-cli/blob/a4635a41522dee9bec5f3dd21063d95422166d58/index.js#L124-L183
But following on from that it looks like here:
https://github.com/simonireilly/observatory-github-action/blob/8ede7d2376147396669b1954283532703a1aa95b/src/tools/observatory-runner.ts#L25-L37
In this action I might try something different - I'll implement an exponential backoff logic here - because I think the linear single second retry is not configurable:
https://github.com/mozilla/observatory-cli/issues/25

@ChrisSargent I have cut a beta at
Can you try:
- name: Observatory Github Action
  id: observatory
  uses<EMAIL_ADDRESS>  with:
    web_host: https://example.com

Would be good to know if this increases the stability by reducing the total number of requests.

Should be closed by https://github.com/simonireilly/observatory-github-action/releases/tag/v0.1.1
Re-open if it continues


RF: migrate some shared state into URL using jotai-location and useParamState hook

Description
State Management

load locationAtom from jotai-location, which is a util that keeps a piece of state synced with the urlparams, and can be accessed from any file
makes custom useParamState hook that loads that shared locationAtom, and returns a getter/setter just like useState. It accepts the type, the string value to use as the URL param key, and an option default param value.
optimized useGetParamState for when we only need to GET that param state, but not set it

Controls These States With New Hooks

demographicType
multimapOpen
topicInfoOpen
dataTypeId 1 and 2

Renaming

rename all variables so that the DemographicType refers to the type of data disaggregation (like by age, sex, or race_and_ethnicity), and reserve the word Breakdown to refer to any dataset that has been "broken down" by demographic, geographic, timeview, etc.
activeBreakdownFilter -> focusedGroup

Motivation and Context

Refactor code for readability and usability
Has this been tested? How?
Test still pass
Types of changes

Refactor / chore

Post-merge TODO
I have inspected frontend changes and/or run affected data pipelines:

[ ] on DEV
[ ] on PROD

Any target user persona(s)?
Preview link below in Netlify comment 😎

rebuilding piece by piece #2317 #2316


fix: ingest scores when loading CSAF docs

Fixes: #278
Ported test over from OSV's loader, but commented out quite a bit since the ingestion of the product statuses seems incomplete.

Thanks!

@bobmcwhirter can you provide some guidance around ingesting the product status stuff (your commented-out code) so that I can uncomment the bulk of the test?

I think we have no support around product yet but Dejan is working on it.


taking the negative of powers doesn't work

Microsoft PowerToys version
0.78.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
Put the negative sign before a simple exponentiation a ^ b

✔ Expected Behavior
The negative sign should apply to the result of a^b
❌ Actual Behavior
The negative sign is ignored as if it weren't there

Other Software
No response

Maybe it does (-3)^2. What is the result if you input =-(3^2) ?

That's exactly what is happening. Specifying parentheses gives the correct result

Yeah I thought so. I think this is a logical result of omitting specifications. Only real way to prevent any ambiguity is to use parentheses everywhere.

It might be logical depending on the context, but I think the expectation for most people when using a calculator is to respect the usual order of operations

Even PEMDAS has flaws: https://youtu.be/y9h1oqv21Vs?si=esjrpYTK6ODrCkTL (by MinutePhysics)

P.S. note the keywords: logical by context, expectation, usual...

This is no bug. It's mathematics: -3^2 = -3*-3 = 9 (Minus * minus becomes plus.)
So the parenthesis are required to first calculate the power of x and the make it negative.

I still think if the tool is not going to follow the usual order of operations, the documentation should clearly state what order is going to use to calculate the solution


Swift example for ProximityBeacons

There is a legacy example in objective-C but now it is useful to have a swift example. Thanks.
https://github.com/Estimote/iOS-SDK/blob/c0899ceab2ebd219e38e7329daef41b05d17827a/LegacyExamples/ProximityBeacons/Examples/ESTBeaconTableVC.m

Hey @danieltigse !
Thank you for raising this issue to our awareness. We'll definitely need to update the examples soon.
Right now we're busy on other fronts but if you were successful with your implementation and care to improve this for future developers I'll be pleased to review any pull requests you submit 🙂


Remove Coinbase banner

Coinbase Ventures is an investor in Commonwealth, not Edgeware. Commonwealth is a minority governing member in Edgeware and so we should make sure the two are not confused with each other.

Looks good to me, but I need to check if the layout would not look weird with only 3 banners, there.

Hi @johny, circling back here, have you had a chance to look at this?


Flutter application blurred screen & garbled page problem

Recently, I have encountered some strange problems in the development of app with Flutter. At present, I am developing in the master branch, and with the command of flutter build apk to create android package. After installation, there will be the problem of blurred screen & garbled page. The specific reason I haven't found. And iOS also meets similar problems.
Then I tryed to switch to the stable branch for packaging, and find that the stable branch can solve the blurred screen & garbled page problem, but iOS will encounter other problems.
Main problems:
1. The master branch has blurred screen & garbled page problem.
screenshot 1
screenshot 2
Operation steps:

in my project, there is a video player (Chewie: ^ 0.9.10). Open a video at random, play it for about 20s, and then click the screen to have such a problem
or turn on the camera (image_picker: ^ 0.6.3 + 4) and return to take a picture
similar problems may occur in other operations
steps 1 & 2 are very likely to occur

2. The packaging problem of the stable branch iOS-52084.
Project pependences:
environment:
  sdk: ">=2.2.2 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  cupertino_icons: ^0.1.2

  # 系统分享插件
  share_extend: ^1.1.0

  font_awesome_flutter: ^8.0.1
  rxdart: ^0.21.0
  flutter_masked_text: ^0.6.0
  webview_flutter: ^0.3.5+2
  tripledes: ^2.1.0
  json_annotation: ^2.0.0
  dio: ^3.0.9
  shared_preferences: ^0.4.3
  sqflite: any
  path_provider: ^1.3.0
  flare_flutter: ^1.3.3
  # fluwx: ^0.6.1
  # flutter_alipay: "^0.1.0"
  # recorder_wav: ^0.1.0
  camera: ^0.5.7+2
  fluttertoast: ^3.0.3
  flutter_native_image: ^0.0.5+2

  logging: ^0.11.3+2
  # intl: ^0.16.0
  url_launcher: ^5.0.2
  connectivity: ^0.4.2
  encrypt: ^0.2.0+2
  video_player: ^0.10.0+4
  oauth2: ^1.2.3
  flutter_redux: ^0.5.3
  event_bus:  ^1.0.1
  scoped_model: ^1.0.1
  flutter_spinkit: ^3.1.0
  lottie_flutter: ^0.2.0
  flutter_easyrefresh: ^1.2.7
  image_picker: ^0.6.3+4
  # image_crop: ^0.3.0
  image_cropper: ^1.0.2
  #flutter_datetime_picker: ^1.1.5
  flutter_datetime_picker:
    git:
      url: https://github.com/waitwalker/flutter_datetime_picker.git
  flutter_downloader: 1.1.6
  permission_handler: ^4.0.0
  package_info: ^0.4.0+2
  flutter_rating: ^0.0.2
  device_info: ^0.4.0+1
  # timeline_list: ^0.0.3
  # percent_indicator: ^1.0.15
  flutter_localizations:
    sdk: flutter
  intl_translation: ^0.17.4
  shimmer: ^1.0.0
  quiver: ^2.0.3
  equatable: ^0.2.0
  image_picker_saver: ^0.3.0
  udid: ^0.0.2
  screen: ^0.0.5
  path_drawing: ^0.4.1
  flutter_svg: ^0.17.3+1
  date_format: ^1.0.8
  pdf_viewer_plugin: ^1.0.0+2
  table_calendar: ^2.0.1
  paging: ^0.1.0
  photo_view: ^0.8.0
  http: ^0.12.0+4

  # 转场动画
  page_transition: ^1.1.5

  # 刷新
  pull_to_refresh: ^1.5.7

  # 日志信息输出
  logger: ^0.8.3

  # 下拉刷新 上拉加载更多插件
  #pull_to_refresh:
    #git:
      #url: https://github.com/waitwalker/flutter_pulltorefresh.git
      #ref: 'master'

  # 播放器
  #chewie: ^0.9.10
  chewie:
    git:
      url: https://github.com/waitwalker/chewie.git
      ref: 'master'
  jpush_flutter:
    git:
      url: https://github.com/waitwalker/jpush-flutter-plugin.git
      ref: 'master'
  wangxiao_plugin:
    path: ./wangxiao_plugin
  flutter_webview_plugin:
    git:
      url: https://github.com/laxian/flutter_webview_plugin.git
      ref: 'master'
  flutter_umeng_analytics:
    git:
      url: https://github.com/waitwalker/flutter_umeng_analytics.git
      ref: 'master'

  real_rich_text:
    git:
      url: https://github.com/waitwalker/RealRichText.git
      ref: 'master'

dependency_overrides:
  video_player:
    path: ./video_player
  path_drawing: ^0.4.1

dev_dependencies:
  flutter_test:
    sdk: flutter
  build_runner: ^1.0.0
  json_serializable: ^2.0.0
  json2entity: ^1.0.8

flutter:
  uses-material-design: true

  assets:
    - static/images/1.5x/
    - static/images/2.0x/
    - static/images/3.0x/
    - static/images/
    - static/svgs/
    - assets/

  fonts:
    - family: aliIconFont
      fonts:
        - asset: static/font/iconfont.ttf

Flutter doctor:
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.16.1-pre.18, on Mac OS X 10.15.3 19D76, locale zh-Hans-CN)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
[✓] Android Studio (version 3.6)
[✓] VS Code (version 1.43.1)
[✓] Connected device (1 available)

• No issues found!

最近用flutter开发遇到一些奇怪的问题,目前在master分支进行开发,运行flutter build apk 打出来的Android包,安装之后会出现花屏&页面乱码问题,具体原因我还没有找到,iOS打出来的包也遇到类似问题.
于是切换到stable分支进行打包,发现stable分支可以解决Android花屏&乱码问题,但是iOS的会遇到其他问题
主要问题:
1.master分支会出现花屏&页面乱码问题
screenshot 1
screenshot 2
操作步骤:
1).我的项目中有视频播放器(chewie: ^0.9.10),随便打开一个视频,播放20s左右,然后点击屏幕就会出现这样的问题.
2).或者打开相机(image_picker: ^0.6.3+4)拍照后返回也会出现这种情况.
3).其他操作也可能出现类似问题.
4).步骤1&2出现的几率很大.
2.stable分支iOS无法运行打包问题52084.

Hi @waitwalker
1 . For issue related to the 3rd party plugin chewie you may want to open an issue in the dedicated github.

I see that it's already open so please follow the issue there

if you disagree please write in the comments and I will reopen it
Thank you

I got similar problem, the screen blurred, and text shape broken

I got similar problem, the screen blurred, and text shape broken sometimes.

Has the problem been solved？

I got similar problem, the screen blurred, and text shape broken sometimes.

I also encountered this problem, is there a correct answer？

Could everyone who still has this problem please file a new issue with the exact descriptions
what happens, logs and the output of 'flutter doctor -v' please.
All system setups can be slightly different so it's always better to open new issues and reference
related issues.


Update custom-limits.md

Fix typo in custom limits subRequests. Source is https://github.com/cloudflare/workerd/blob/03a3396a9a2ea37f0f32181e9db21aaff2e890b2/types/defines/wfp.d.ts#L9

TY @taylorlee


registerRenderer is mentioned in some places

Four files still mention the absent function:
sq@MacBook-Pro ~/src/react_on_rails$ git grep registerRenderer
spec/dummy/app/views/pages/client_side_manual_render.html.erb:  ReactOnRails.registerRenderer({
spec/dummy/app/views/pages/deferred_render_with_server_rendering.html.erb:  ReactOnRails.registerRenderer({
spec/dummy_no_webpacker/app/views/pages/client_side_manual_render.html.erb:  ReactOnRails.registerRenderer({
spec/dummy_no_webpacker/app/views/pages/deferred_render_with_server_rendering.html.erb:  ReactOnRails.registerRenderer({

Looks like it was forgotten while working on https://github.com/shakacode/react_on_rails/pull/581

Good catch. Can you submit a PR?

I'm not sure because I could fully understand how it works. :)

Fixed in #1059


[Feat] Allow AWS SECRETS MANAGER instead of storing AES Encrypted in db

This pull request introduces a significant security enhancement by providing an option to migrate away from storing AES-encrypted sensitive data directly in our database. Instead, it allows us to leverage AWS Secrets Manager to securely store, manage, and retrieve our application's secrets.
Key Highlights of this Change:
Improved Security: Sensitive data is now protected by AWS Secrets Manager's enterprise-grade security features, including encryption at rest and in transit, strict access controls, and auditing capabilities.
Compliance Alignment: This shift enhances our alignment with various regulatory compliance standards that recommend or mandate the use of dedicated secret management solutions for sensitive data.
Simplified Key Management: No longer will we need to manage AES encryption keys within our application, reducing operational overhead and potential security risks associated with key mismanagement.
Audit Trail: Traceble log of credentials

@HenryHengZJ any thoughts on this feature ? It can be toggled using env. vars.


Unable to access password (access-token) in another app

Unable to access password (access-token) in another app when second app is launched first time. Here is my flow:

I install my App1 and login inside app. Add access-token for my service and i close this app.
Then i install App2 and open the app. UICKeyChainStore return the access-token as NIL.

It only works when:
After installing App2 I open App1 again and close it then open App2. This time it return the access-token of my defined service.
Please let me know how to fix this? I only want to auto login in new apps when a previous app having same keychain access group and logged in.

I got the issue in my code. closing this.


Update Documentation

Change links to point to the new Google FIrebase Docs site (https://firebase.google.com/docs/).  Also clarified that Bolt only work on the Firebase Realtime Database, not Cloud Storage.

I was able to update the guide myself, thanks!


Updated sdk for interruptCallMediaOperation flag.

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/communication-call-automation


ini file configuration handle to make all network creations go under the Common partition

Title: ini file configuration handle to make all network creations go under the Common partition
Details: This is an enhancement request

OpenStack Release
Mitaka (earliest planned)
Description
An ini configuration in the etc file to make all new networks fall onto the Common partition rather than a particular, specified partition.  This would be a hard-set boolean with a default of False.  The resulting handle interpretation should be performed in the icontrol_driver.py.
NOTE:  This is the first implementation step in this feature and, through extension, is not the final step to reveal this new feature.  Please look to future enhancements and pull requests for the release of this feature.  This handle will simply allow for future development to be tested at a functional level later and will not be 'attached' to any functionality until implemented later.  Thus, it is not a bug after this ticket is closed that the configuration handle does not do what it specifies it does until the feature is released.
Agent Version
UNK
Operating System
All that are normally supported

This is currently in master branch.


Random crash

PC Specs: Windows 10, Ryzen 9 3900x, B550 Steel Legend, NO GPU.
Python: 3.8.10,   Chia: 1.1.7
The PC is it used with Remote Desktop Connection, the error happens some time (this time 10 min) after I have disconnected from the PC.
The Error is large so I put it in a .txt file. Error.txt

Hey @TheBrigandRo, thanks for reporting this issue!
This seems to be a very rare event which I haven't run in to yet on my setup.
The error you posted seems to imply that you received multiple signage points at exactly the same timestamp, causing a index collision in the database when the we try to insert this event.
Did this error reoccur after you restarted the monitor?

Well, I don't have a monitor connected (no gpu). I am controlling the PC with the Remote Desktop Connection from windows.
And every time I connect to the PC it's like logging in the user, but when I disconnect the programs keeps running.
And the problem keeps happening, it not something rare on my end.
Is there a way to check the collision and prevented, or just a simple try, catch :))

With monitor I was actually referring to this program and not an actual computer monitor 😄 Since you are the only person reporting this issue I suspect this seems to be something weird with your setup and I suggest we move this discussion to our discord #support channel which you can join using the link in the README.md.

@philippnormann the issue I reported is the same as this


set percentage node used instead of available

First of all, thanks for this exporter. We find it very useful.
While implementing alerting rules based on the metrics provided, I found out an inconsistency between the metric's description Percentage of ephemeral storage used on a node and the actual value returned, which is Percentage of ephemeral storage available on a node. Either the description or the calculation is wrong.
This PR attempts to fix the latter because it makes both ephemeral_storage_{node,container_limit}_percentage metrics consistent with setValue = (usedBytes / c.limit) * 100.0 (the value calculated for container if its limit is set).
What do you think?

Hi @miminar. Thank you, I am always glad to hear from happy users!
I made this test script and it produces the same value. So I need some more context on what I am doing wrong.
I also had some trouble finding Percentage of ephemeral storage available on a node in the library, could you link that code here?
Thanks!
package main

import (
	"fmt"
	"math"
)

var (
	availableBytes float64
 	capacityBytes  float64
)

func main() {

	availableBytes = 50.0
	capacityBytes = 100.0

	setValue := (availableBytes / capacityBytes) * 100.0

	a := fmt.Sprintf("Old value is: %f\n", setValue)
	print(a)

	setValue = math.Max(capacityBytes-availableBytes, 0.) * 100.0 / capacityBytes

	a = fmt.Sprintf("New value is: %f\n", setValue)
	print(a)
}

Output
Old value is: 50.000000
New value is: 50.000000

Hi @miminar. Thank you, I am always glad to hear from happy users!
availableBytes = 50.0
capacityBytes = 100.0

Nice, that's the only case where they are equal :-). Try with capacityBytes=450..

I also had some trouble finding Percentage of ephemeral storage available on a node in the library, could you link that code here?

That's the thing. There is just "Percentage of ephemeral storage used on a node", but the returned value is the percentage of the available ephemeral storage, not used.
This PR changes the calculation to return the percentage used. But if you like, I could change it to just update the metric's help to "Percentage of ephemeral storage available on a node". However, in that case, this calculation would have to be changed as well.

@miminar Ah, I see the error of my ways. I agree; thank you for going into detail!
I have approved this for e2e testing.

When I told you this months ago you rejected the issue :-(

@lozbrown That is correct, and mistakes were made. However, there wasn't clarity around why I needed it, so my opinion changed here. I hope you don't take this personally and I try my best hear out every case.
https://github.com/jmcgrath207/k8s-ephemeral-storage-metrics/issues/41#issuecomment-1854018515
That said, there were some good feature's idea that were raised in that ticket. That we've added and I thank you for that.
https://github.com/jmcgrath207/k8s-ephemeral-storage-metrics/pull/59
My suggestion for raising issues in the future, @lozbrown, is to focus on one topic and kept it concise as possible. It will make it easier for the maintainer to focus on what needs to happen.

@miminar Thank your contribution, the e2e test passed. I will release this later tonight.

I was only kidding, definitely no offence taken and I hope you haven't taken any either.
I'm glad this change has been made and I'll look to upgrade again soon and remove my workarounds.
This is a really useful tool, thanks again for all the work on this

@lozbrown Awesome, Glad to hear. Thanks for understanding.

Thank you for review and merge!
Would you be interested in another contribution adding an optional PrometheusRule à la KubePersistentVolumeFillingUp to chart templates?

@miminar Sounds good to me!

@miminar @lozbrown
Just release this PR in 1.10.2.


How to update Distributor info on Windows Dev Center

Hi, we're Hancom MDS (the former MDS Technology), one of the APAC distributors of Windows 10 IoT Enterprise. We've noticed that the distributor information on the Windows Dec Center is outdated, so could you let us know how to change the information?
In this following URL, you could see the distributor list (outside link), as follows below;
https://docs.microsoft.com/ko-kr/windows/iot-core/windows-iot-enterprise
In the page 2, the MDS Technology from Korea has to be updated.
https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE37tp1
Distributor Name: Hancom MDS
Contact name: Dong Hoon Lee /<EMAIL_ADDRESS>Contact Phone: +82 31 602  2049
Looking forward to hearing back from you soon.
Best Regards,
Elena

@yoojin1011 Please move this issue to https://github.com/MicrosoftDocs/windows-iot/issues


add additional timestamps during timeout retries

28 minutes elapsed between these retries, should have been closer to a minute.  Need additional timestamps to help understand all the time loss.
2022-01-21 09:34:20: (session:1, poll:19) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=30% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 09:44:29: (session:1, poll:20) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=30% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 09:54:39: (session:1, poll:21) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=30% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 10:04:49: (session:1, poll:22) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=30% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 10:14:59: (session:1, poll:23) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=30% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 10:25:10: (session:1, poll:24) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=30% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 10:35:19: (session:1, poll:25) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=30% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 10:45:29: (session:1, poll:26) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=30% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 10:55:40: (session:1, poll:27) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=31% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 11:05:49: (session:1, poll:28) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=31% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 11:15:58: (session:1, poll:29) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=31% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 11:26:08: (session:1, poll:30) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 11:36:18: (session:1, poll:31) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 11:46:27: (session:1, poll:32) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 11:56:36: (session:1, poll:33) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 12:06:46: (session:1, poll:34) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 12:16:56: (session:1, poll:35) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 12:27:07: (session:1, poll:36) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 12:37:16: (session:1, poll:37) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 12:47:27: (session:1, poll:38) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 12:57:40: (session:1, poll:39) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=32% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 13:07:57: (session:1, poll:40) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=33% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 13:18:10: (session:1, poll:41) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=33% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 13:28:19: (session:1, poll:42) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=33% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 13:38:37: (session:1, poll:43) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=33% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 13:48:48: (session:1, poll:44) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=33% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 13:58:58: (session:1, poll:45) HEAT_MODE [HEAT_MODE deviation] act temp=68.0°F, act humidity=34% RH (temporary), set point=68.0°F, tolerance=2.0°F, override=72.0°F
[log_msg]: message text=Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: honeywell HEAT_MODE deviation alert on zone 0
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>email sent from module '<module 'email_notification' from '/home/pi/github/ThermostatSupervisor/email_notification.py'>' running on raspberrypi (<IP_ADDRESS>)
[log_msg]: smtp connection successful
[log_msg]: email account authorization for account<EMAIL_ADDRESS>successful
[log_msg]: mail send was successful
[log_msg]: Email sent!
*** honeywell HEAT_MODE deviation detected on zone 0, reverting thermostat to heat schedule ***
2022-01-21 14:09:11: (session:1, poll:46) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 14:19:20: (session:1, poll:47) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 14:29:29: (session:1, poll:48) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 14:39:38: (session:1, poll:49) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 14:49:48: (session:1, poll:50) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 14:59:58: (session:1, poll:51) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 15:10:09: (session:1, poll:52) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 15:20:18: (session:1, poll:53) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 15:30:28: (session:1, poll:54) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 15:40:38: (session:1, poll:55) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 15:50:47: (session:1, poll:56) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 16:00:57: (session:1, poll:57) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 16:11:07: (session:1, poll:58) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 16:21:16: (session:1, poll:59) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 16:31:25: (session:1, poll:60) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 16:41:34: (session:1, poll:61) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 16:51:44: (session:1, poll:62) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 17:01:54: (session:1, poll:63) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 17:12:03: (session:1, poll:64) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=34% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 17:22:15: (session:1, poll:65) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=35% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 17:32:25: (session:1, poll:66) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=35% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
2022-01-21 17:42:35: (session:1, poll:67) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=35% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F
[log_msg]: Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 449, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 444, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.7/http/client.py", line 1336, in getresponse
response.begin()
File "/usr/lib/python3.7/http/client.py", line 306, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.7/http/client.py", line 267, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/lib/python3.7/socket.py", line 589, in readinto
return self._sock.recv_into(b)
File "/usr/lib/python3.7/ssl.py", line 1052, in recv_into
return self.read(nbytes, buffer)
File "/usr/lib/python3.7/ssl.py", line 911, in read
return self._sslobj.read(len, buffer)
TimeoutError: [Errno 110] Connection timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/requests/adapters.py", line 450, in send
timeout=timeout
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 786, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/util/retry.py", line 550, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/packages/six.py", line 770, in reraise
raise value
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 710, in urlopen
chunked=chunked,
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 451, in _make_request
self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 358, in _raise_timeout
self, url, "Read timed out. (read timeout=%s)" % timeout_value
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='mytotalconnectcomfort.com', port=443): Read timed out. (read timeout=None)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/pi/github/ThermostatSupervisor/honeywell.py", line 700, in refresh_zone_info
all_zones_info = self.pyhtcc.get_zones_info()
File "/home/pi/github/ThermostatSupervisor/honeywell.py", line 195, in get_zones_info
result = self._post_zone_list_data(page_num)
File "/home/pi/.local/lib/python3.7/site-packages/pyhtcc/pyhtcc.py", line 324, in _post_zone_list_data
return self.session.post(f'https://mytotalconnectcomfort.com/portal/Device/GetZoneListData?locationId={self._locationId}&page={page_num}', headers={'X-Requested-With': 'XMLHttpRequest'})
File "/home/pi/.local/lib/python3.7/site-packages/requests/sessions.py", line 577, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/home/pi/.local/lib/python3.7/site-packages/requests/sessions.py", line 529, in request
resp = self.send(prep, **send_kwargs)
File "/home/pi/.local/lib/python3.7/site-packages/requests/sessions.py", line 645, in send
r = adapter.send(request, **kwargs)
File "/home/pi/.local/lib/python3.7/site-packages/requests/adapters.py", line 532, in send
raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='mytotalconnectcomfort.com', port=443): Read timed out. (read timeout=None)
[log_msg]: exception during refresh_zone_info, on trial 1 of 3, probably a connection issue, waiting 60 seconds and then retrying...
[log_msg]: message text=Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: intermittent JSON decode error during refresh zone
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>refresh_zone_info: trial 2 of 3
email sent from module '<module 'email_notification' from '/home/pi/github/ThermostatSupervisor/email_notification.py'>' running on raspberrypi (<IP_ADDRESS>)
[log_msg]: smtp connection successful
[log_msg]: email account authorization for account<EMAIL_ADDRESS>successful
[log_msg]: mail send was successful
[log_msg]: Email sent!
2022-01-21 18:10:22: (session:1, poll:68) HEAT_MODE [following schedule] act temp=68.0°F, act humidity=35% RH, set point=68.0°F, tolerance=2.0°F, override=68.0°F

another example with 30 minutes between good measurements:
2022-01-22 03:48:00: (session:1, poll:123) HEAT_MODE [following schedule] act temp=66.0°F, act humidity=35% RH, set point=66.0°F, tolerance=2.0°F, override=66.0°F
[log_msg]: Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 449, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 444, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.7/http/client.py", line 1336, in getresponse
response.begin()
File "/usr/lib/python3.7/http/client.py", line 306, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.7/http/client.py", line 267, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/lib/python3.7/socket.py", line 589, in readinto
return self._sock.recv_into(b)
File "/usr/lib/python3.7/ssl.py", line 1052, in recv_into
return self.read(nbytes, buffer)
File "/usr/lib/python3.7/ssl.py", line 911, in read
return self._sslobj.read(len, buffer)
TimeoutError: [Errno 110] Connection timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/requests/adapters.py", line 450, in send
timeout=timeout
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 786, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/util/retry.py", line 550, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/packages/six.py", line 770, in reraise
raise value
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 710, in urlopen
chunked=chunked,
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 451, in _make_request
self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
File "/home/pi/.local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 358, in _raise_timeout
self, url, "Read timed out. (read timeout=%s)" % timeout_value
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='mytotalconnectcomfort.com', port=443): Read timed out. (read timeout=None)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/pi/github/ThermostatSupervisor/honeywell.py", line 700, in refresh_zone_info
all_zones_info = self.pyhtcc.get_zones_info()
File "/home/pi/github/ThermostatSupervisor/honeywell.py", line 195, in get_zones_info
result = self._post_zone_list_data(page_num)
File "/home/pi/.local/lib/python3.7/site-packages/pyhtcc/pyhtcc.py", line 324, in _post_zone_list_data
return self.session.post(f'https://mytotalconnectcomfort.com/portal/Device/GetZoneListData?locationId={self._locationId}&page={page_num}', headers={'X-Requested-With': 'XMLHttpRequest'})
File "/home/pi/.local/lib/python3.7/site-packages/requests/sessions.py", line 577, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/home/pi/.local/lib/python3.7/site-packages/requests/sessions.py", line 529, in request
resp = self.send(prep, **send_kwargs)
File "/home/pi/.local/lib/python3.7/site-packages/requests/sessions.py", line 645, in send
r = adapter.send(request, **kwargs)
File "/home/pi/.local/lib/python3.7/site-packages/requests/adapters.py", line 532, in send
raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='mytotalconnectcomfort.com', port=443): Read timed out. (read timeout=None)
[log_msg]: exception during refresh_zone_info, on trial 1 of 3, probably a connection issue, waiting 60 seconds and then retrying...
[log_msg]: message text=Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: intermittent JSON decode error during refresh zone
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>refresh_zone_info: trial 2 of 3
email sent from module '<module 'email_notification' from '/home/pi/github/ThermostatSupervisor/email_notification.py'>' running on raspberrypi (<IP_ADDRESS>)
[log_msg]: smtp connection successful
[log_msg]: email account authorization for account<EMAIL_ADDRESS>successful
[log_msg]: mail send was successful
[log_msg]: Email sent!
2022-01-22 04:15:43: (session:1, poll:124) HEAT_MODE [following schedule] act temp=66.0°F, act humidity=35% RH, set point=66.0°F, tolerance=2.0°F, override=66.0°F


SDTM codelist issues

I'm having an odd issue when generating metadata for the 2.1 definexml.  I've been using the generate from saslib sample program and the settings are:
%define_createsrcmetafromsaslib(
 _cstTrgStandard=&_cstTrgStandard,
 _cstTrgStandardVersion=&_cstTrgStandardVersion,
 _cstLang=en,
 _cstUseRefLib=Y,
 _cstKeepAllCodeLists=N
);

I also tried the other variant:
%define_createsrcmetafromsaslib(
 _cstSASDataLib=srcdata,
 _cstStudyMetadata=work.studymetadata,
 _cstTrgStandard=&_cstTrgStandard,
 _cstTrgStandardVersion=&_cstTrgStandardVersion,
 _cstTrgStudyDS=trgmeta.source_study,
 _cstTrgTableDS=trgmeta.source_tables,
 _cstTrgColumnDS=trgmeta.source_columns,
 _cstTrgCodeListDS=trgmeta.source_codelists,
 _cstTrgValueDS=trgmeta.source_values,
 _cstTrgDocumentDS=trgmeta.source_documents,
 _cstTrgAnalysisResultDS=trgmeta.source_analysisresults,
 _cstLang=en,
 _cstUseRefLib=Y,
 _cstRefTableDS=refmeta.reference_tables,
 _cstRefColumnDS=refmeta.reference_columns,
 _cstClassTableDS=refmeta.class_tables,
 _cstClassColumnDS=refmeta.class_columns,
 _cstKeepAllCodeLists=Y,
 _cstFormatCatalogs=cstfmt.formats ncifmt.cterms,
 _cstNCICTerms=ncifmt.cterms
 );

The issue I get is the metadata source_codelist file shows every possible term for every variable, when I only want the terminology for the terms used within the study data. Everything else seems like it is working correctly and when I change   _cstKeepAllCodeLists=N to  _cstKeepAllCodeLists=Y, it does what I'd expect it to do and show every term regardless of what is in the data. The User Guide has not done much to help me here and I'm not sure what I need to change in order to get this to work the way I want it to. Any advice here would be appreciated.

The 2 different ways of specifying the macro parameters is a matter of taste, and does not influence the result, as long as the SASReferences data set used in the first option is consistent with specifying all parameters in the second option.
The parameter _cstKeepAllCodeLists is about keeping all codelists (Y) or keep only the codelists that are referenced by source_columns.xmlcodelist or source_values.xmlcodelist. It will keep all terms in codelists specified by  _cstFormatCatalogs and _cstNCICTerms.
The macro does not support keeping only the terms used within the study data. Keep in mind that typically the entire range of possible values from a codelist used in the study has to be included in the Define-XML codelist. For example, suppose only mild adverse events have been reported for a study where the data collection instrument collected AE severity as Mild, Moderate, or Severe. In this case, the recommendation is to include all 3 possible terms in the codelist.
Also, the result of the macro only creates an initial set of metadata. It is fully expected that this metadata will need to be further processed. In the macro header it says: "This is ONLY an attempted approximation of source metadata. No assumptions should be made that the result accurately represents the study data. Incomplete reference metadata may not enable imputation of missing metadata. "

Thanks for the explanation. I am having trouble understanding the hierarchy of SASReferences data and which ones take precedence over the other. weather the references were written inline, on a table within the samples folder, or in the Global folder. I don't quite understand which takes precedence, so I default to referencing everything from within the program.

Thanks for the explanation. I am having trouble understanding the hierarchy of SASReferences data and which ones take precedence over the other. weather the references were written inline, on a table within the samples folder, or in the Global folder. I don't quite understand which takes precedence, so I default to referencing everything from within the program.

Macro parameters take preference. When macro parameters are not defined, the SASReferences dataset is used to look up. When things that are not study specific do not have a value in the SASReferences dataset (location of messages datasets, path to macros, ...), there is a lookup in the global lookup table.


docs: added workflows readme

Description
Added a new README to the workflows directory to explain usage of reusable common workflows.
Check the relevant boxes:

[ ] Bug fix (nonbreaking change that fixes an issue)
[ ] New feature (nonbreaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Examples or tests (addition or updates of examples or tests)
[x] Documentation update
[ ] CI related update (pipeline, etc.)

Checklist

[ ] If relevant, a test for the change has been added or updated as part of this PR.
[x] If relevant, documentation for the change has been added or updated as part of this PR.

Merge

Merge using "Squash and merge".
Make sure to use a relevant conventional commit message that is based on the PR contents. The commit message determines whether a new version of the modules needs to be released, and if so, which semver number to use).

Oh I see @SirSpidey created a doc repo. Maybe it should live there? https://github.com/terraform-ibm-modules/documentation

We can add a section for "internal" or maintainer content if you want. Docs are rendered now at https://terraform-ibm-modules.github.io/documentation/ (still a big WIP).

Closing this in favor of https://github.com/terraform-ibm-modules/documentation/pull/5


Improve camera tracking, especially across session pause/resume

Change the ARSession tracking mechanism
Change the way ARSession tracks camera orientation. Before this change ARKit was configured to use real world surfaces to orient itself.  Now it just uses the device's accelerometer.  Result is smoother panning due to the simpler tracking mechanism, and more importantly ARKit can "find itself" after a pause/resume event.
I also added the App Store icon to remove a compiler warning, and fixed an incorrect variable type.
Breaking Changes
None.
Meta
N/A
Checklist

[ ] Appropriate label has been added to this PR (i.e., Bug, Enhancement, etc.).
[ ] Documentation has been added to all open, and public scoped methods and properties.
[ ] Changelog has been updated
[ ] Tests have have been added to all new features. (not a requirement, but helpful)
[ ] Image/GIFs have been added for all UI related changed.

Screenshots

Change the ARSession tracking mechanism

@Pilot-Marc and I collaborated on this and we added the ability to use the default AR configuration (World Tracking, without any code changes) - or specify Device Orientation Tracking as a parameter you pass into the SceneLocationView initializer.


PF3 Theme for PF4

Demonstrate what a PF3 theme for PF4 components looks like. This demo should illustrate what could be achieved with only modifying PF4 variables and no additional customization. This story also includes providing a recommendation for potential variable to add to PF4, which will allow better alignment with PF3.

related (w/ design mockup) - https://github.com/patternfly/patternfly-next/issues/421

Here is as close as I can get to making the PF4 header and navigation look like PF3, using the existing customizable variables in PF4. Note the header is near a 1:1 match, but the navigation is not. https://issue-421-vars--thirsty-noether-30ec26.netlify.com/demos/pagelayout/examples-full/?component=Page Layout PF-3#

Here is the PF3 theme demo after adding some additional variables to support a better match to PF3 styles. Aside from a couple of hardcoded styles for the purpose of the demo, all of the PF3 styling is done by simply overwriting CSS variables.
https://issue-421-vars-suggested--thirsty-noether-30ec26.netlify.com/demos/pagelayout/examples-full/?component=Page Layout PF-3#

In order to theme PF4 to look as close as possible to the PF3 theme mockup using CSS variables only, I needed to introduce some additional variables into PF4 that didn't exist previously.
There are basically 3 types of additions here. 1 and 2 make sense to me to add, but I'm not sure about 3.

Introduce a new variable for a property's value that's already in PF4. The vertical alignment of the text and toggle caret icon in an expandable nav link is a good example. That is current set to align-items: baseline;, and since baseline is hardcoded in PF4, we can't overwrite/change it with a variable in the PF3 theme. Simply changing that to align-items: var(--pf-c-nav__list-link--AlignItems); and setting --pf-c-nav__list-link--AlignItems to baseline in PF4 allows us to set the value of that variable to something else in the PF3 theme.

The only place this wouldn't make sense is when we don't want a user to be able to change the value of a property. In the above example, maybe we always want that value to be baseline, because changing it to anything else goes against the design principle of PF3 and PF4.

Introduce a new property and/or variable that is currently unset in PF4, and it makes sense to add so that the user can change it. The color for the toggle caret icon in the vertical navigation is a good example. The color used in PF4 simply relies on inheriting the color from it's ancestor element(s). So here we're adding a new property and variable to the element, but this should be added anyways, should the user wish to change colors used in the navigation component and also wants to change the color of the toggle caret.

Again, the only place this wouldn't make sense is when we don't want the user to be able to change this property to a particular value. In the example above, maybe using the color green goes against the design principles.

Introduce a new property and/or variable that is currently not in PF4, for no reason other than to create the PF3 theme. The horizontal border/line between the top-level navigation elements in the PF3 theme is a good example. The top-level navigation in PF4 does not have a border, so to enable the border in the PF3 theme, we have to add a bunch of border properties and variables to PF4, set them so that they're not visible, then change the border variables in the PF3 theme so that they're visible. This adds a fair amount of bloat to PF4 for something that will never be used in PF4, all so that we can use it in the PF3 theme, with the side benefit (or drawback?) of a user now being able to customize that border, too.

Page Layout
--pf-l-page__header--AlignItems
--pf-l-page__header--wildcard--AlignItems

be able to adjust vertical alignment of page header elements

Nav Component
--pf-c-nav__list-link--AlignItems

to center nav text and toggle icon

--pf-c-nav__list-link--FontSize

adjust font size of nav links

--pf-c-nav__list-link--after--Top

be able to adjust top positioning of current nav item's blue border/accent line

--pf-c-nav__list-item--BorderBottomWidth
--pf-c-nav__list-item--BorderBottomColor

border support for nav list items (so I can have a bottom border between top level navigation links)

--pf-c-nav__list-item--m-current--BackgroundColor

adds a background color for the current nav list item

--pf-c-nav__simple-list-link--after--Display

set display property of the blue border for nav links to a var so I can toggle it

--pf-c-nav__simple-list-link--FontSize
--pf-c-nav__simple-list-link--LineHeight

adjust font size of simple-list nav links

--pf-c-nav__subnav--MarginBottom

add a bottom margin to subnav

--pf-c-nav__list-toggle--Color

change color of expandable link caret


Harmonize STR with core ontology updates

As we add ports etc., to the core ontology, we need to harmonize the STR ontology in RACK V10.

We have not introduced ports (at least up to this point) so no need to harmonize.


[FEAT] Add support to convert admin user to regular user

pyZscaler doesn't support the ability to convert admin users to regular users via this API endpoint:

/adminUsers/{userId}/convertToUser

This should be added for completeness

Implemented in latest develop branch, ready for 1.7.0


Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found."

I was completed be able to Xcode -> Product -> Archive and Export .ipa with no error in Mac(OS X 10.11.5).
but getting this error in Bitrise workflow.
Exporting IPA from generated Archive...
  $ set -o pipefail && xcodebuild -exportArchive -archivePath "/var/folders/lb/8n5bn9k975qgw662jpqdy7mm0000gn/T/bitrise-xcarchive.2XeBFtsX/ProjectName.xcarchive" -exportPath "/var/folders/lb/8n5bn9k975qgw662jpqdy7mm0000gn/T/bitrise-xcarchive.5gP61qY6" -exportOptionsPlist "/Users/vagrant/deploy/export_options.plist" | xcpretty

2016-06-12 20:45:30.711 xcodebuild[3717:12709] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/lb/8n5bn9k975qgw662jpqdy7mm0000gn/T/ProjectName_2016-06-12_20-45-30.706.xcdistributionlogs'.
2016-06-12 20:45:31.000 xcodebuild[3717:12709] [MT] DeveloperPortal: Using store at URL (file:///Users/vagrant/Library/Developer/Xcode/DeveloperPortal%207.3.1.db).
2016-06-12 20:45:40.494 xcodebuild[3717:12709] [MT] IDEDistribution: Step failed: <IDEDistributionThinningStep: 0x7f8989c2a750>: Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.}
error: exportArchive: No applicable devices found.

Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.}

|                                                                              |
+----+--------------------------------------------------------------+----------+
| 🚫  |<EMAIL_ADDRESS>(exit code: 70)                          | 406 sec  |
+----+--------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-new-xcode-archive/issues  |
| Source: https://github.com/bitrise-io/steps-new-xcode-archive                |
+----+--------------------------------------------------------------+----------+

already tried the following links.
http://stackoverflow.com/questions/33041109/xcodebuild-no-applicable-devices-found-when-exporting-archive
http://stackoverflow.com/questions/33901132/export-failed-error-using-xcodebuild-command-line-tool
https://forums.developer.apple.com/message/75096#75096

Hi,
Can you please include the content of exportOptionsPlist? - it should be printed right before these logs

added exportOptiionsPlist.
however same error occurred.
exportPlist.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>teamID</key>
        <string>myTeamId</string>
        <key>method</key>
        <string>ad-hoc</string>
        <key>uploadSymbols</key>
        <true/>
        <key>uploadBitcode</key>
        <false/>
    </dict>
</plist>

error logs.
Exporting IPA from generated Archive...
  $ xcodebuild -exportArchive -archivePath "/var/folders/lb/8n5bn9k975qgw662jpqdy7mm0000gn/T/bitrise-xcarchive.lZPITzI4/ProjectName.xcarchive" -exportPath "/var/folders/lb/8n5bn9k975qgw662jpqdy7mm0000gn/T/bitrise-xcarchive.czxsuo01" -exportOptionsPlist "exportPlist.plist"

2016-06-13 21:04:55.957 xcodebuild[3669:11911] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/lb/8n5bn9k975qgw662jpqdy7mm0000gn/T/ProjectName_2016-06-13_21-04-55.957.xcdistributionlogs'.
2016-06-13 21:04:56.035 xcodebuild[3669:11911] [MT] DeveloperPortal: Using store at URL (file:///Users/vagrant/Library/Developer/Xcode/DeveloperPortal%207.3.1.db).
2016-06-13 21:05:02.980 xcodebuild[3669:11911] [MT] IDEDistribution: Step failed: <IDEDistributionThinningStep: 0x7fa6ec19ae20>: Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.}
error: exportArchive: No applicable devices found.

Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." UserInfo={NSLocalizedDescription=No applicable devices found.}

Can you try to re-export your Certificate (p12) and download the Provisioning Profile from the Apple Developer Portal directly, and upload these to Bitrise.io ?
This issue can be related to invalid/wrong code signing files, at least so far it mostly was related to.

I tried it. but same error.
other repositories has no problem. only this repository has "No applicable device found" error.
Is there something that is considered to be the cause of that?

Could you please send us the full build log in email / through the on-site chat?
Usually this error (if you use the latest steps) is related to the code signing files and not to a configuration / code, but the build log would help a lot!

ok. I'll send you.

Hi,
We just released a new version of this step which now has an option to use the deprecated export option of Xcode. After some experimenting we found that there are projects which will always fails with the "No applicable devices found." error, regardless of the code signing files, but it'll succeed with the old/deprecated export option of Xcode.
So, to use this option, just upgrade to the latest version (1.8.1) and set the "use_deprecated_export" option to "yes".
Please let us know if this fixes your issue too!

Hi,
I confirmed fixed issue with "No applicable devices found" in 1.8.1.
I am grateful for your prompt response!
On Fri, Jun 24, 2016 at 12:41 AM, Viktor Benei<EMAIL_ADDRESS>wrote:

Hi,
We just released a new version of this step which now has an option to use
the deprecated export option of Xcode. After some experimenting we found
that there are projects which will always fails with the "No applicable
devices found." error, regardless of the code signing files, but it'll
succeed with the old/deprecated export option of Xcode.
So, to use this option, just upgrade to the latest version (1.8.1) and set
the "use_deprecated_export" option to "yes".
Please let us know if this fixes your issue too!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bitrise-io/steps-xcode-archive/issues/37#issuecomment-228091920,
or mute the thread
https://github.com/notifications/unsubscribe/ABjzLgfh98xghEINRZlT2WlabkgNKyBmks5qOqkrgaJpZM4I0OBi
.

Thanks for reporting @morugu !

Hi there, I ran into this issue locally with an Xcode build script (the legacy build API works but the exportOptions approach failed with the same message)
I found it to be related to using RVM or more specifically not using system Ruby (it seems Xcode has a dependency on it). Switching to system ruby (rvm use system) allowed the export options plist approach to work
Locally it's fine but in a CI environment I'm not sure what's best, the legacy API works but will mean that Bitcode can't be supported from what I understand.
Links
https://twitter.com/madhikarma/status/792457412196327425
https://t.co/TnOOXSjXDc
https://github.com/fastlane/fastlane/issues/3184
https://gist.github.com/claybridges/cea5d4afd24eda268164

This step specifically switches back to rvm use system (https://github.com/bitrise-io/steps-xcode-archive/blob/master/step.sh#L451) if RVM is found, as well as tries to invalidate all other ruby version manager for the export (where the ruby version matters) - https://github.com/bitrise-io/steps-xcode-archive/blob/master/step.sh#L324
If you still get the Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." error, it's more likely to be related to your Xcode project (and Xcode's buggy export handling when you don't use the legacy export method), something like: http://stackoverflow.com/questions/39634404/xcodebuild-exportarchive-no-applicable-devices-found

If anyone would have this issue today, please do not change to the legacy/deprecated mode!
Instead, make sure that you use the latest version of this Xcode Archive step, as the latest versions do collect and expose the "ide distribution" logs of Xcode. So far these logs included the actual error in every case we saw.
When running on bitrise.io, make sure that you have a Deploy to Bitrise.io step in your workflow, that will attach all these additional Xcode logs (including the ide distribution error logs) to the build. You will be able to see these on the build's page, in the Apps & Artifacts section. Check those files, you should see the error in one of those.


PackageReference requires all sources to be available

See https://github.com/NuGet/Home/issues/5035 and lots of related issues.
I could not find a specific doc documenting this right now.

@nkolev92 - what exactly should we document here? 'nuget does not work offline' ?

NuGet requires all sources to be available in order to have a deterministic resolution.

@nkolev92 - can you please help with a PR :)

Can you help deciding where?
https://github.com/NuGet/docs.microsoft.com-nuget/blob/master/docs/consume-packages/Package-References-in-Project-Files.md maybe?

PR out https://github.com/NuGet/docs.microsoft.com-nuget/pull/1764