test(device_info_plus): Fix integration test for Android

Description
Fixing tests for installerStore value on Android as it seems like since Android 14 OS returns com.android.shell for apps installed via package manager, adb command (I suppose so) instead of null. Don't see any mentions of it in the documentation. Earlier we didn't see this test failing because we had no API 34 in our build matrix.
Checked with emulators and real phone with Android 14 - on Android 13 I see null, while on 14 for both virtual and real device see com.android.shell when installing example via Android Studio. I believe this fix for the integration test should be correct.

Title should be package_info_plus!

Smart to use device_info_plus to determine the OS version in the unit tests ;)

The first thing that came to my mind. Also, I don't know other ways to do this check.

Title should be package_info_plus!

Thanks for catching. Doing multiple things at once never ends well :(


Unable to install by go get on windows10

Version
1.17.2
What happened?
Hello!
go version go1.20 windows/amd64
I'm trying
go install github.com/kyleconroy/sqlc/cmd/sqlc@latest
but it returns an error:
Relevant log output
# github.com/kyleconroy/sqlc/cmd/sqlc
C:\Program Files\Go\pkg\tool\windows_amd64\link.exe: running gcc failed: exit status 1
c:/programdata/chocolatey/lib/mingw/tools/install/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:/Users/afoni/go/pkg/mod/github.com/bytecodealliance/wasmtime-go/v5@v5.0.0/build/windows-x86_64/libwasmtime.a(helpers.o):helpers.c:(.text$wasmtime_setjmp+0x26): undefined reference to `_setjmp'
collect2.exe: error: ld returned 1 exit status

Database schema
No response
SQL queries
No response
Configuration
No response
Playground URL
No response
What operating system are you using?
No response
What database engines are you using?
No response
What type of code are you generating?
No response

I'm not an expert on Go's dynamic linking, but I presume this is an issue because of sqlc's dependency on certain packages that require cgo.
I would try to go install with these flags to see if you can generate a statically-linked binary: -ldflags "-linkmode 'external' -extldflags '-static'"

Closing as a duplicate. Let's track all of these install issues here: https://github.com/kyleconroy/sqlc/issues/2294


Issue with k8s.io/docs/concepts/overview/working-with-objects/kubernetes-objects/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
The Kubernetes API Reference url is not working
Proposed Solution:
Generate the new Documentation
Page to Update:
https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/

Fixed by #13442


feat: add check for service bindings

Signed-off-by: Michael Dawson<EMAIL_ADDRESS>

Still a Work in Progress while @wtrocki tests it out.

This works well with Strimzi but we need SASL/Plain Auth for this

@wtrocki, what do we have to do for "SASL/Plain Auth ".  If I had more info or a way to test that we could figure out what to adjust.

Worked with @wtrocki to test with RH managed Kafka, landing

Luke had taken a look, going to test after rebase on latest changes and then land.


Stats object is not filled after compilation

The stats object is not filled with stats after compilation. When using node-sass, you can get duration with stats.duration. This is not working with gulp-sass.

This has been resolved in 2.x. Please try it and report back. If we don't hear back, we'll assume it's been resolved and close this issue.
npm install dlmanning/gulp-sass#2.x

As it's been a month, I'm closing this.


CAMEL-12543: WIP [DO NOT MERGE] Add camel-debezium component to Camel

Background:
This intends to add the support of Debezium CDC events to Apache Camel, in order to add the capability to emit CDC events to different ESB components other than Kafka.
Limitations:
I kept the initial version of the wrapper to only support MySQL, if the community finds it helpful, we can add the support for other connectors that Debezium supports (such as Postgress, Oracle, MongoDB and Cassandra).
Note: This is PR a work in progress, there are the following TODOs:

[ ] Add documentation.
[x] Try to enhance the unit tests with integration tests of DBZ embedded engine.
[x] Add Karaf and Spring integration tests.
[ ] Add the sourceMetadata to the headers.
[ ] Extract before into message headers and the message body should be only after.
[ ] Add toMap type conversion to support Map type besides Struct.
[ ] Add an example to demonstrate how to use it. (will send this in a second PR once this is merged).

Please feel free to comment for any changes required

@gunnarmorling it would be good to get some of your thoughts and feedback on this work

Hey @oscerd @jbonofre , I added the integration tests for Spring and Karaf, however due to my unfortunate limited knowledge on Karaf, I am not sure what I did is correct as whenever I try to verify the feature that I added, it always fails with:
Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=camel-debezium; type=karaf.feature; version=3.0.0.SNAPSHOT; filter:="(&(osgi.identity=camel-debezium)(type=karaf.feature)(version>=3.0.0.SNAPSHOT))" [caused by: Unable to resolve camel-debezium/3.0.0.SNAPSHOT: missing requirement [camel-debezium/3.0.0.SNAPSHOT] osgi.identity; osgi.identity=org.apache.camel.camel-debezium; type=osgi.bundle; version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve org.apache.camel.camel-debezium/3.0.0.SNAPSHOT: missing requirement [org.apache.camel.camel-debezium/3.0.0.SNAPSHOT] osgi.wiring.package; filter:="(osgi.wiring.package=io.debezium.config)"]]

And when I run the integration test for Karaf, it alway fails with this error:
java.lang.IllegalArgumentException: No matching features for camel-debezium/0
        at org.apache.camel.itest.karaf.CamelDebeziumTest.test(CamelDebeziumTest.java:30)

Is it possible if you can take a closer look and give me some hints how can I fix this? Thank you

the feature seems to be ok

Hey @oscerd @bedlaj @jbonofre @dmvolod @gunnarmorling ,
I pushed some fixes and added what I needed to add per your comments, please give another look and let me know if I missed something. I have squash the commits to tidy up the PR.
PS: @oscerd, yeah I managed to fix the Karaf features after all so that is why now looks fine :).
Thanks

IMO, this is ready to merge.

If we all agree, I'll merge this one this week.

Merged on master. Thanks.

Thanks @oscerd ! For any further modifications, I can have them in another PRs


After setting application in Active directory, error during signup

After submitting application in Azure AD, error during signup
please check screen shot.

I'm having the same issue. Did you manage to resolve it?

I found a fix for this issue here https://github.com/Azure-Samples/active-directory-dotnet-native-multitarget/issues/10

We have provided some updated text in readme to ensure that you do not miss the admin consent steps. Please give them a try

Closing as OP has not responded


Added Favorite Animal Duck

Hi, this is the repo for semester Fall 2023. Try again and choose base repository: schafert/STAT624_PRDemo

My apologies, Dr. Bruce and I were using the same repo for different courses 😅


Feat:  proper alignment of the comment div

Describe the feature
comment div alignmnet is improper
Describe the solution you'd like
Describe alternatives you've considered
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign level labels @arghadipmanna101


[BEAM-3060] TextIOIT: DataFlow and PerfKit profiles + big hash

This PR adds Maven profiles for DataFlow runner and PerfKit to file-based-io-tests
Additionally hash for large dataset is added and doc for TextIOIT is fixed.
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

SUCCESS
--none--

SUCCESS
--none--

SUCCESS
--none--

@chamikaramj could you please take a look? thanks

SUCCESS
--none--

SUCCESS
--none--

SUCCESS
--none--

Thanks for review @chamikaramj. Please take a look now. Thanks.


Fix handling of nested embedded entities on the edit form (#2688)

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

Merged into branches iso4 in 8452ff91bdbcb835283f65bf028c5b089ef3e440


retain MYSQL DB pvc on deletion

Currently, we delete the pvc when deleting the resource we should retain the DB and allow it to be reused

We will need to modify the trillian DB image when it runs 60-loaddb there isn't a check in to see if the data already exists so it fails due to duplicate

#172


consistency of DefaultPlayer with Player

ADD NEXT

The player included in the playermanager can be changed at any time (as part of the experimental custom players). Everything shipped in the default player will make its way into the playermanager soon


Not re-rendering after value change

Possible duplicate of #18
There is a bug causing the breadcrumb helper to not recompute when its dependant data changes. It only seems to happen when the breadcrumb item is somewhere in the middle of the breadcrumb stack (i.e. the breadcrumb in question has an active subroute).
So far the only way I can reproduce reliably is to use debugger to force a timing delay.
Reproduction: https://github.com/charlesfries/ember-breadcrumb-trail/tree/timing
Steps to reproduce:

Clone and serve.
Visit http://localhost:4200/foo/bar with the inspector open and breakpoints enabled
Skip the breakpoints until there are none

Expectation
The "Home" breadcrumb should say "Home hello" after a delay of 2000ms.
Actual
The "Home" breadcrumb says "Home".
"ember-breadcrumb-trail": "^0.2.0",
"ember-cli": "~3.28.0",
"ember-source": "~3.28.0",

@charlesfries Hey, thanks for the issue!
I took a quick look at the reproduction (thanks for that!) and it seems to be related to the value being updated while the breadcrumbs update loop isn't finished yet. This check fails, so the value isn't updated. It seems that it consistently works if you use run.later or next instead of setTimeout since by then the flag should be reset.
I'm not sure how this can be fixed in the addon though. That check is there to prevent infinite loops (since the addon forces a rerender) so removing it is not an option. I also don't see a way to tell the service that a specific update is fine. The only thing I can think of is adding some sort of diff checking to determine if the title and data has changed, but since the data object is fully user controlled that doesn't sound ideal either.
Can you provide more information about the real setup where you are running into issues?
All of these timing issues kind of confirm that using templates for things like this might not be the best solution (since it requires runloop hackery) and a "route based" breadcrumbs setup would skip all these issues, but the helper based API is so nice from a consumer point of view 😄. Ideally the helper would be an "effect", but that isn't a thing so I tried to mimic that behavior with the runloop. As you noticed, it's far from perfect 😄.


Add conda installation option for rubrix

Add a conda installation option for rubrix. I have already stared working on this one. It has passed all the CI's and will soon be merged. Once the :bulb: PR gets approved/merged, rubrix will be available on conda-forge as:
conda install -c conda-forge rubix

:zap: Once rubrix is available on conda-forge, I will push a PR to update the readme-installation section.

cc: @dvsrepo @recognai

Wow! Thanks so much @sugatoray , this is very appreciated. Looking forward to it. Let us know if you need support

:rocket: A screenshot says it all!


--run-id linux-alar-fki --parameters kernel not working in Ubuntu 18.04

I tried to use the linux-alar-fki script with kernel parameter in an ubuntu 18.04 VM and I am getting the following message (this was tested on a freshly created VM from the Portal):
Script returned with error:
[Error 02/09/2022 18:00:43] Your OS can not be determined. The OS distros supported are
[Error 02/09/2022 18:00:43] CentOS/Redhat 6.8 - 8.2
[Error 02/09/2022 18:00:43] Ubuntu 16.4 LTS and Ubuntu 18.4 LTS
[Error 02/09/2022 18:00:43] Suse 12 and 15
[Error 02/09/2022 18:00:43] Debain 9 and 10
[Error 02/09/2022 18:00:43] ALAR will stop!
[Error 02/09/2022 18:00:43] If your OS is in the above list please report this issue at https://github.com/azure/repair-script-library/issues
[Error 02/09/2022 18:00:43]

Instead of "linux-alar-fki" could you please try out with the new alar2 version please --> linux-alar2
the new version contains a couple of fixes.

Thanks, I just tested this one using linux-alar2 Ubuntu 18.04  and RHEL 7.9. It didn't give me the above error anymore but this other one:
Script returned with error:
[Error 02/09/2022 19:02:46]E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
I tried again, and I didn't get that error, but I executed the restore option and the VM booted using the same kernel, not the previous one (in both cases)
Output of the executing in Ubuntu 18.04:
az vm repair run -g myRG -n 3rdbreakUbuntu1804 --run-id linux-alar2 --parameters kernel --run-on-repair --verbose
Searching for repair-vm within subscription...
Found repair VM: /subscriptions/89378e19-fe1c-444a-8606-c0196dc7a874/resourceGroups/repair-3rdbreakUbuntu1804-20220209191630/providers/Microsoft.Compute/virtualMachines/repair-3rdbrea_
Running script on repair VM: repair-3rdbrea_
Log file is too large and has been cutoff at the start of file. Please locate the log file within the repair VM using the logFullpath to check full logs.
Script returned with output:
[Output 02/09/2022 19:19:46]Starting the recovery [Info 2022-02-09 19:19:46.972639205 UTC] We have the following partitions determined: ["1<PHONE_NUMBER>6574 29.9 GiB 8300 ", "14 2048 10239 4.0 MiB EF02 ", "15 10240 227327 106.0 MiB EF00 "] [Info 2022-02-09 19:19:46.976966139 UTC] Ade is enabled : false [Info 2022-02-09 19:19:46.976991639 UTC] This could be a recent Ubuntu 16.x or 18.x image.Or a RedHat with RAW partitions [Info 2022-02-09 19:19:47.130318117 UTC] /dev/sdc1 [Info 2022-02-09 19:19:47.130358617 UTC] fsck for ext4 cloudimg-rootfs: recovering journal cloudimg-rootfs: clean, 113649/3870720 files, 747402/7836155 blocks [Info 2022-02-09 19:19:47.491845884 UTC] File system check finished [Info 2022-02-09 19:19:47.666074918 UTC] fsck for vfat fsck.fat 4.1 (2017-01-24) 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Performing changes. /dev/sdc15: 11 files, 8921/213716 clusters [Info 2022-02-09 19:19:47.747419241 UTC] File system check finished [Info 2022-02-09 19:19:47.863666931 UTC] mounted /dev/sdc1 to /tmp/assert [Info 2022-02-09 19:19:47.941770129 UTC] Pretty Name is : "Ubuntu 18.04.6LTS" [Info 2022-02-09 19:19:48.033067624 UTC] mounted /dev/sdc1 to /tmp/assert [Info 2022-02-09 19:19:48.104868563 UTC] Pretty Name is : "Ubuntu 18.04.6 LTS" [Info 2022-02-09 19:19:48.104905263 UTC] Pretty Name is : "Ubuntu 18.04.6 LTS" [Info 2022-02-09 19:19:48.174984390 UTC] mounted /dev/sdc1 to /srv/rescue-root/ [Info 2022-02-09 19:19:48.247004531 UTC] mounted /dev/sdc15 to /srv/rescue-root/boot/efi Directory /tmp/action_implementation can not be removed : 'No such file or directory (os error 2)' The current dir is : /var/lib/waagent/run-command/download/1/repair-files-20220209191931/repair-script-library/Azure-repair-script-library-cae6187/src/linux/common/helpers/alar2 [Info 2022-02-09 19:19:48.268209291 UTC] ----- Start action ----- [Info 2022-02-09 19:19:49.865765676 UTC] ----- Action stopped -----
[Output 02/09/2022 19:19:49]Recovery script finished
{
"log_full_path": "/var/lib/waagent/run-command/download/1/repair-files-20220209191931/logs-20220209191931.txt",
"logs": "ected package libllvm6.0:amd64.\r Preparing to unpack .../04-libllvm6.0_1%3a6.0-1ubuntu2_amd64.deb ...\r Unpacking libllvm6.0:amd64 (1:6.0-1ubuntu2) ...\r Selecting previously unselected package libclang1-6.0:amd64.\r Preparing to unpack .../05-libclang1-6.0_1%3a6.0-1ubuntu2_amd64.deb ...\r Unpacking libclang1-6.0:amd64 (1:6.0-1ubuntu2) ...\r Selecting previously unselected package lib32gcc1.\r Preparing to unpack .../06-lib32gcc1_1%3a8.4.0-1ubuntu1~18.04_amd64.deb ...\r Unpacking lib32gcc1 (1:8.4.0-1ubuntu1~18.04) ...\r Selecting previously unselected package lib32stdc++6.\r Preparing to unpack .../07-lib32stdc++6_8.4.0-1ubuntu1~18.04_amd64.deb ...\r Unpacking lib32stdc++6 (8.4.0-1ubuntu1~18.04) ...\r Selecting previously unselected package libclang-common-6.0-dev.\r Preparing to unpack .../08-libclang-common-6.0-dev_1%3a6.0-1ubuntu2_amd64.deb ...\r Unpacking libclang-common-6.0-dev (1:6.0-1ubuntu2) ...\r Selecting previously unselected package libclang-6.0-dev.\r Preparing to unpack .../09-libclang-6.0-dev_1%3a6.0-1ubuntu2_amd64.deb ...\r Unpacking libclang-6.0-dev (1:6.0-1ubuntu2) ...\r Selecting previously unselected package libclang-dev.\r Preparing to unpack .../10-libclang-dev_1%3a6.0-41~exp5~ubuntu1_amd64.deb ...\r Unpacking libclang-dev (1:6.0-41~exp5~ubuntu1) ...\r Setting up libllvm6.0:amd64 (1:6.0-1ubuntu2) ...\r Setting up libgc1c2:amd64 (1:7.4.2-8ubuntu1) ...\r Setting up libclang1-6.0:amd64 (1:6.0-1ubuntu2) ...\r Setting up libc6-i386 (2.27-3ubuntu1.4) ...\r Setting up lib32gcc1 (1:8.4.0-1ubuntu1~18.04) ...\r Setting up libobjc4:amd64 (8.4.0-1ubuntu1~18.04) ...\r Setting up libobjc-7-dev:amd64 (7.5.0-3ubuntu1~18.04) ...\r Setting up lib32stdc++6 (8.4.0-1ubuntu1~18.04) ...\r Setting up libclang-common-6.0-dev (1:6.0-1ubuntu2) ...\r Setting up libclang-6.0-dev (1:6.0-1ubuntu2) ...\r Setting up libclang-dev (1:6.0-41~exp5~ubuntu1) ...\r Processing triggers for libc-bin (2.27-3ubuntu1.4) ...\r [Output 02/09/2022 19:19:46]Starting the recovery [Info 2022-02-09 19:19:46.972639205 UTC] We have the following partitions determined: ["1<PHONE_NUMBER>6574 29.9 GiB 8300 ", "14 2048 10239 4.0 MiB EF02 ", "15 10240 227327 106.0 MiB EF00 "] [Info 2022-02-09 19:19:46.976966139 UTC] Ade is enabled : false [Info 2022-02-09 19:19:46.976991639 UTC] This could be a recent Ubuntu 16.x or 18.x image. Or a RedHat with RAW partitions [Info 2022-02-09 19:19:47.130318117 UTC] /dev/sdc1 [Info 2022-02-09 19:19:47.130358617 UTC] fsck for ext4 cloudimg-rootfs: recovering journal cloudimg-rootfs: clean, 113649/3870720 files, 747402/7836155 blocks [Info 2022-02-09 19:19:47.491845884 UTC] File system check finished [Info 2022-02-09 19:19:47.666074918 UTC] fsck for vfat fsck.fat 4.1 (2017-01-24) 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Performing changes. /dev/sdc15: 11 files, 8921/213716 clusters [Info 2022-02-09 19:19:47.747419241 UTC] File system check finished [Info 2022-02-09 19:19:47.863666931 UTC] mounted /dev/sdc1 to /tmp/assert [Info 2022-02-09 19:19:47.941770129 UTC] Pretty Name is : "Ubuntu 18.04.6 LTS" [Info 2022-02-09 19:19:48.033067624 UTC] mounted /dev/sdc1 to /tmp/assert [Info 2022-02-09 19:19:48.104868563 UTC] Pretty Name is : "Ubuntu 18.04.6 LTS" [Info 2022-02-09 19:19:48.104905263 UTC] Pretty Name is : "Ubuntu 18.04.6 LTS" [Info 2022-02-09 19:19:48.174984390 UTC] mounted /dev/sdc1 to /srv/rescue-root/ [Info 2022-02-09 19:19:48.247004531 UTC] mounted /dev/sdc15 to /srv/rescue-root/boot/efi Directory /tmp/action_implementation can not be removed : 'No such file or directory (os error 2)' The current dir is : /var/lib/waagent/run-command/download/1/repair-files-20220209191931/repair-script-library/Azure-repair-script-library-cae6187/src/linux/common/helpers/alar2 [Info 2022-02-09 19:19:48.268209291 UTC] ----- Start action ----- [Info 2022-02-09 19:19:49.865765676 UTC] ----- Action stopped ----- [Output 02/09/2022 19:19:49]Recovery script finished [STATUS]::SUCCESS [Log-End 02/09/2022 19:19:49]/var/lib/waagent/run-command/download/1/repair-files-20220209191931/logs-20220209191931.txt",
"message": "Script completed succesfully.",
"output": "[Output 02/09/2022 19:19:46]Starting the recovery [Info 2022-02-09 19:19:46.972639205 UTC] We have the following partitions determined: ["1<PHONE_NUMBER>6574 29.9 GiB 8300 ", "14 2048 10239 4.0 MiB EF02 ", "15 10240 227327 106.0 MiB EF00 "] [Info 2022-02-09 19:19:46.976966139 UTC] Ade is enabled : false [Info 2022-02-09 19:19:46.976991639 UTC] This could be a recent Ubuntu 16.x or 18.x image. Or a RedHat with RAW partitions [Info 2022-02-09 19:19:47.130318117 UTC] /dev/sdc1 [Info 2022-02-09 19:19:47.130358617 UTC] fsck for ext4 cloudimg-rootfs: recovering journal cloudimg-rootfs: clean, 113649/3870720 files, 747402/7836155 blocks [Info 2022-02-09 19:19:47.491845884 UTC] File system check finished [Info 2022-02-09 19:19:47.666074918 UTC] fsck for vfat fsck.fat 4.1 (2017-01-24) 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Performing changes. /dev/sdc15: 11 files, 8921/213716 clusters[Info 2022-02-09 19:19:47.747419241 UTC] File system check finished [Info 2022-02-09 19:19:47.863666931 UTC] mounted /dev/sdc1 to /tmp/assert [Info 2022-02-09 19:19:47.941770129 UTC] Pretty Name is : "Ubuntu 18.04.6 LTS" [Info 2022-02-09 19:19:48.033067624 UTC] mounted /dev/sdc1 to /tmp/assert [Info 2022-02-09 19:19:48.104868563 UTC] Pretty Name is : "Ubuntu 18.04.6 LTS" [Info 2022-02-09 19:19:48.104905263 UTC] Pretty Name is : "Ubuntu 18.04.6 LTS" [Info 2022-02-09 19:19:48.174984390 UTC] mounted /dev/sdc1 to /srv/rescue-root/ [Info 2022-02-09 19:19:48.247004531 UTC] mounted /dev/sdc15 to /srv/rescue-root/boot/efi Directory /tmp/action_implementation can not be removed : 'No such file or directory (os error 2)' The current dir is : /var/lib/waagent/run-command/download/1/repair-files-20220209191931/repair-script-library/Azure-repair-script-library-cae6187/src/linux/common/helpers/alar2 [Info 2022-02-09 19:19:48.268209291 UTC] ----- Start action ----- [Info 2022-02-09 19:19:49.865765676 UTC] ----- Action stopped ----- \n[Output 02/09/2022 19:19:49]Recovery script finished ",
"resource_group": "repair-3rdbreakUbuntu1804-20220209191630",
"script_status": "SUCCESS",
"status": "SUCCESS",
"vm_name": "repair-3rdbrea_"
}
Output of the executing in RHEL 7.9:
az vm repair run -g myRG -n breakrhel79 --run-id linux-alar2 --parameters kernel --run-on-repair --verbose
Searching for repair-vm within subscription...
Found repair VM: /subscriptions/89378e19-fe1c-444a-8606-c0196dc7a874/resourceGroups/repair-breakrhel79-20220209192122/providers/Microsoft.Compute/virtualMachines/repair-breakrh_
Running script on repair VM: repair-breakrh_
Log file is too large and has been cutoff at the start of file. Please locate the log file within the repair VM using the logFullpath to check full logs.
Script returned with output:
[Output 02/09/2022 19:24:30]Starting the recovery [Info 2022-02-09 19:24:30.328848068 UTC] We have the following partitions determined: ["1 2048 1026047 500.0 MiB EF00 EFI System Partition", "2 1026048 2050047 500.0 MiB 0700 ", "3 2050048 2054143 2.0 MiB EF02 ", "4 2054144 134215679 63.0 GiB 8E00 "] [Info 2022-02-09 19:24:30.334700819 UTC] Ade is enabled : false [Info 2022-02-09 19:24:30.334735220 UTC] This is a recent RedHat or CentOS image with 4 partitions and LVM signature [Info 2022-02-09 19:24:31.352501751 UTC] fsck for LVM2_member [Info 2022-02-09 19:24:31.352764553 UTC] File system check finished [Info 2022-02-09 19:24:31.352784453 UTC] fsck for XFS on /dev/sdc2 [Info 2022-02-09 19:24:32.973948330 UTC] mounted /dev/sdc2 to /tmp/assert [Info 2022-02-09 19:24:34.018300895 UTC] File system check finished [Info 2022-02-09 19:24:34.018370695 UTC] fsck for vfat fsck.fat 4.1 (2017-01-24) 0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Performing changes. /dev/sdc1: 17 files, 1267/63965 clusters [Info 2022-02-09 19:24:34.159344822 UTC] File system check finished [Info 2022-02-09 19:24:34.201403858 UTC] LVM Details 'LVMDetails { lvm_root_part: "/dev/rootvg/rootlv", lvm_usr_part: "/dev/rootvg/usrlv", lvm_var_part: "/dev/rootvg/varlv" }' [Info 2022-02-09 19:24:36.462705855 UTC] mounted /dev/rootvg/rootlv to /tmp/assert [Info 2022-02-09 19:24:36.489079656 UTC] Pretty Name is : "Red Hat Enterprise Linux Server 7.9 (Maipo)" [Info 2022-02-09 19:24:36.489108656 UTC] Pretty Name is : "Red Hat Enterprise Linux Server 7.9 (Maipo)" [Info 2022-02-09 19:24:37.606572141 UTC] mounted /dev/rootvg/rootlv to /srv/rescue-root/ [Info 2022-02-09 19:24:39.045253922 UTC] mounted /dev/rootvg/usrlv to /srv/rescue-root/usr [Info 2022-02-09 19:24:40.053924138 UTC] mounted /dev/rootvg/varlv to /srv/rescue-root/var [Info 2022-02-09 19:24:40.906413614 UTC] mounted /dev/sdc2 to /srv/rescue-root/boot [Info 2022-02-09 19:24:41.591137837 UTC] mounted /dev/sdc1 to /srv/rescue-root/boot/efi Directory /tmp/action_implementation can not be removed : 'No such file or directory (os error 2)' The current dir is : /var/lib/waagent/run-command/download/1/repair-files-20220209192414/repair-script-library/Azure-repair-script-library-cae6187/src/linux/common/helpers/alar2 [Info 2022-02-09 19:24:41.611819576 UTC] ----- Start action ----- Loaded plugins: langpacks, product-id, search-disabled-repos Resolving Dependencies --> Running transaction check ---> Package patch.x86_64 0:2.7.1-12.el7_7 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: patch x86_64 2.7.1-12.el7_7 rhui-rhel-7-server-rhui-rpms 111 k Transaction Summary ================================================================================ Install 1 Package Total download size: 111 k Installed size: 210 k Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : patch-2.7.1-12.el7_7.x86_64 1/1 Verifying : patch-2.7.1-12.el7_7.x86_64 1/1 Installed: patch.x86_64 0:2.7.1-12.el7_7 Complete! [Info 2022-02-09 19:27:47.143874286 UTC] ----- Action stopped -----
[Output 02/09/2022 19:27:47]Recovery script finished
{
"log_full_path": "/var/lib/waagent/run-command/download/1/repair-files-20220209192414/logs-20220209192414.txt",
"logs": " (1:6.0-1ubuntu2) ...\r Setting up libc6-i386 (2.27-3ubuntu1.4) ...\r Setting up lib32gcc1 (1:8.4.0-1ubuntu1~18.04) ...\r Setting up libobjc4:amd64 (8.4.0-1ubuntu1~18.04) ...\r Setting up libobjc-7-dev:amd64 (7.5.0-3ubuntu1~18.04) ...\r Setting up lib32stdc++6 (8.4.0-1ubuntu1~18.04) ...\r Setting up libclang-common-6.0-dev (1:6.0-1ubuntu2) ...\r Setting up libclang-6.0-dev (1:6.0-1ubuntu2) ...\r Setting up libclang-dev (1:6.0-41~exp5~ubuntu1) ...\r Processing triggers for libc-bin (2.27-3ubuntu1.4) ...\r [Output 02/09/2022 19:24:30]Starting the recovery [Info 2022-02-09 19:24:30.328848068 UTC] We have the following partitions determined: ["1 2048 1026047 500.0 MiB EF00 EFI System Partition", "2 1026048 2050047 500.0 MiB 0700 ", "3 2050048 2054143 2.0 MiB EF02 ", "4 2054144 134215679 63.0 GiB 8E00 "] [Info 2022-02-09 19:24:30.334700819 UTC] Ade is enabled : false [Info 2022-02-09 19:24:30.334735220 UTC] This is a recent RedHat or CentOS image with 4 partitions and LVM signature [Info 2022-02-09 19:24:31.352501751 UTC] fsck for LVM2_member [Info 2022-02-09 19:24:31.352764553 UTC] File system check finished [Info 2022-02-09 19:24:31.352784453 UTC]fsck for XFS on /dev/sdc2 [Info 2022-02-09 19:24:32.973948330 UTC] mounted /dev/sdc2 to /tmp/assert [Info 2022-02-09 19:24:34.018300895 UTC] File system check finished [Info 2022-02-09 19:24:34.018370695 UTC] fsck for vfat fsck.fat 4.1 (2017-01-24) 0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Performing changes. /dev/sdc1: 17 files, 1267/63965 clusters [Info 2022-02-09 19:24:34.159344822 UTC] File system check finished [Info 2022-02-09 19:24:34.201403858 UTC] LVM Details 'LVMDetails { lvm_root_part: "/dev/rootvg/rootlv", lvm_usr_part: "/dev/rootvg/usrlv", lvm_var_part: "/dev/rootvg/varlv" }' [Info 2022-02-09 19:24:36.462705855 UTC] mounted /dev/rootvg/rootlv to /tmp/assert [Info 2022-02-09 19:24:36.489079656 UTC] Pretty Name is : "Red Hat Enterprise Linux Server 7.9 (Maipo)" [Info 2022-02-09 19:24:36.489108656 UTC] Pretty Name is : "Red Hat Enterprise Linux Server 7.9 (Maipo)" [Info 2022-02-09 19:24:37.606572141 UTC] mounted /dev/rootvg/rootlv to /srv/rescue-root/ [Info 2022-02-09 19:24:39.045253922 UTC] mounted /dev/rootvg/usrlv to /srv/rescue-root/usr [Info 2022-02-09 19:24:40.053924138 UTC] mounted /dev/rootvg/varlv to /srv/rescue-root/var [Info 2022-02-09 19:24:40.906413614 UTC] mounted /dev/sdc2 to /srv/rescue-root/boot [Info 2022-02-09 19:24:41.591137837 UTC] mounted /dev/sdc1 to /srv/rescue-root/boot/efi Directory /tmp/action_implementation can not be removed : 'No such file or directory (os error 2)' The current dir is : /var/lib/waagent/run-command/download/1/repair-files-20220209192414/repair-script-library/Azure-repair-script-library-cae6187/src/linux/common/helpers/alar2 [Info 2022-02-09 19:24:41.611819576 UTC] ----- Start action ----- Loaded plugins: langpacks, product-id, search-disabled-repos Resolving Dependencies --> Running transaction check ---> Package patch.x86_64 0:2.7.1-12.el7_7 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: patch x86_64 2.7.1-12.el7_7 rhui-rhel-7-server-rhui-rpms 111 k Transaction Summary ================================================================================ Install 1 Package Total download size: 111 k Installed size: 210 k Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : patch-2.7.1-12.el7_7.x86_64 1/1 Verifying : patch-2.7.1-12.el7_7.x86_64 1/1 Installed: patch.x86_64 0:2.7.1-12.el7_7 Complete! [Info 2022-02-09 19:27:47.143874286 UTC] ----- Action stopped ----- [Output 02/09/2022 19:27:47]Recovery script finished [STATUS]::SUCCESS [Log-End 02/09/2022 19:27:47]/var/lib/waagent/run-command/download/1/repair-files-20220209192414/logs-20220209192414.txt",
"message": "Script completed succesfully.",
"output": "[Output 02/09/2022 19:24:30]Starting the recovery [Info 2022-02-09 19:24:30.328848068 UTC] We have the following partitions determined: ["1 2048 1026047 500.0 MiB EF00 EFI System Partition", "2 1026048 2050047 500.0 MiB 0700 ", "3 2050048 2054143 2.0 MiB EF02 ", "4 2054144 134215679 63.0 GiB 8E00 "] [Info 2022-02-09 19:24:30.334700819 UTC] Ade is enabled : false [Info 2022-02-09 19:24:30.334735220 UTC] This is a recent RedHat or CentOS image with 4 partitions and LVM signature [Info 2022-02-09 19:24:31.352501751 UTC] fsck for LVM2_member [Info 2022-02-09 19:24:31.352764553 UTC] File system check finished [Info 2022-02-09 19:24:31.352784453 UTC] fsck for XFS on /dev/sdc2 [Info 2022-02-09 19:24:32.973948330 UTC] mounted /dev/sdc2 to /tmp/assert [Info 2022-02-09 19:24:34.018300895 UTC] File system check finished [Info 2022-02-09 19:24:34.018370695 UTC] fsck for vfat fsck.fat 4.1 (2017-01-24) 0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Performing changes. /dev/sdc1: 17 files, 1267/63965 clusters [Info 2022-02-09 19:24:34.159344822 UTC] File system check finished [Info 2022-02-09 19:24:34.201403858 UTC] LVM Details 'LVMDetails { lvm_root_part: "/dev/rootvg/rootlv", lvm_usr_part: "/dev/rootvg/usrlv", lvm_var_part: "/dev/rootvg/varlv" }' [Info 2022-02-09 19:24:36.462705855 UTC] mounted /dev/rootvg/rootlv to /tmp/assert [Info 2022-02-09 19:24:36.489079656 UTC] Pretty Name is : "Red Hat Enterprise Linux Server 7.9 (Maipo)" [Info 2022-02-09 19:24:36.489108656 UTC] Pretty Name is : "Red Hat Enterprise Linux Server 7.9 (Maipo)" [Info 2022-02-09 19:24:37.606572141 UTC] mounted /dev/rootvg/rootlv to /srv/rescue-root/ [Info 2022-02-09 19:24:39.045253922 UTC] mounted /dev/rootvg/usrlv to /srv/rescue-root/usr [Info 2022-02-09 19:24:40.053924138 UTC] mounted /dev/rootvg/varlv to /srv/rescue-root/var [Info 2022-02-09 19:24:40.906413614 UTC] mounted /dev/sdc2 to /srv/rescue-root/boot [Info 2022-02-09 19:24:41.591137837 UTC] mounted /dev/sdc1 to /srv/rescue-root/boot/efi Directory /tmp/action_implementation can not be removed : 'No such file or directory (os error 2)' The current dir is : /var/lib/waagent/run-command/download/1/repair-files-20220209192414/repair-script-library/Azure-repair-script-library-cae6187/src/linux/common/helpers/alar2 [Info 2022-02-09 19:24:41.611819576 UTC] ----- Start action ----- Loaded plugins: langpacks, product-id, search-disabled-repos Resolving Dependencies --> Running transaction check ---> Package patch.x86_64 0:2.7.1-12.el7_7 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: patch x86_64 2.7.1-12.el7_7 rhui-rhel-7-server-rhui-rpms 111 k Transaction Summary ================================================================================ Install 1 Package Total download size: 111 k Installed size: 210 k Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : patch-2.7.1-12.el7_7.x86_64 1/1 Verifying : patch-2.7.1-12.el7_7.x86_64 1/1 Installed: patch.x86_64 0:2.7.1-12.el7_7 Complete! [Info 2022-02-09 19:27:47.143874286 UTC] ----- Action stopped ----- \n[Output 02/09/2022 19:27:47]Recovery script finished ",
"resource_group": "repair-breakrhel79-20220209192122",
"script_status": "SUCCESS",
"status": "SUCCESS",
"vm_name": "repair-breakrh_"
}

Could you please provide me the content of /etc/default/grub from the redhat one?
It could be that one property is missing (GRUB_DEFAULT) I saw it missing on a new deployed  CentOS 8.5

Issue fixed. #29 can be closed


Monitoring reasons consolidation

Description
Jira Ticket: SARAALERT-1081
This PR consolidates all of the Monitoree Reasons into one place
Important Changes
app/javascript/components/public_health/PatientsTable.js

Adds Monitoring Reasons as a prop

app/javascript/components/public_health/Workflow.js

Adds Monitoring Reasons as a prop

app/javascript/components/public_health/actions/CloseRecords.js

Iterates over new Monitoring_Reaons for Select Dropdown

app/javascript/components/subject/monitoring_actions/MonitoringActions.js

Adds Monitoring Reasons as a prop

app/javascript/components/subject/monitoring_actions/MonitoringStatus.js

Iterates over new Monitoring_Reaons for Select Dropdown

app/models/patient.rb

Consolidates Monitoring Reasons in one place

app/views/patients/show.html.erb

Adds Monitoring Reasons as a prop

app/views/public_health/exposure.html.erb

Adds Monitoring Reasons as a prop

app/views/public_health/isolation.html.erb

Adds Monitoring Reasons as a prop

Testing
This fix was tested on the following browsers (submitter must check all those that apply):

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] IE11

Broken Git issues. Will re-open PR.


Move ES Service/Operation Reader to other file

forgot to move the reader fns to the service_operation.go file

Coverage remained the same at 100.0% when pulling b19ad85e76d96ed1ccc0097578be770a6166a7c5 on es-service-reader into d0586d906dca4d4e75fb265576be20ee2e024b5d on master.


Migrate many types from str to Text.

This supports an up coming refactor of pex.{dist_metadata,pep_376}
which also requires re-formulating the pyc filters from Iterable ->
Iterable form to boolean predicates to making typing easier at the
loss of ~nothing.

Like #2262, more work in support of #2097 and #1361.

I believe the CI errors are fixed by #2262. I'll wait on that and then merge it here to see if that's true.


chef-server-core_12.1.0-1 fails to install on ubuntu

Installing chef-server on a brand new VM fails with error:
undefined method `exitstatus' for nil:NilClass (NoMethodError)

Steps to reproduce:
mkdir foobar; cd foobar
vagrant init (Change the 'base' box to 'ubuntu/trusty64'
vagrant up
vagrant ssh
sudo su -
wget https://web-dl.packagecloud.io/chef/stable/packages/ubuntu/trusty/chef-server-core_12.1.0-1_amd64.deb
dpkg -i chef-server-core_12.1.0-1_amd64.deb
chef-server-ctl reconfigure

    ================================================================================
    Error executing action `run` on resource 'execute[oc_id_schema]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received ''
    ---- Begin output of bundle exec rake db:migrate ----
    STDOUT:
    STDERR: no ruby in PATH/CONFIG
    ---- End output of bundle exec rake db:migrate ----
    Ran bundle exec rake db:migrate returned

    Resource Declaration:
    ---------------------
    # In /opt/opscode/embedded/cookbooks/cache/cookbooks/private-chef/recipes/oc_id.rb

    130: execute "oc_id_schema" do
    131:   command "bundle exec rake db:migrate"
    132:   path ["/opt/opscode/embedded/bin"]
    133:   cwd "/opt/opscode/embedded/service/oc_id"
    134:
    135:   # There are other recipes that depend on having a VERSION environment
    136:   # variable. If that environment variable is set when we run `rake db:migrate`,
    137:   # and it is set to something the migrations do not expect, this will
    138:   # break.
    139:   #
    140:   # We want to migrate to the latest version, which we can get by looking at the
    141:   # date prefix of the latest file in the db/migrate directory.
    142:   #
    143:   # Also set the RAILS_ENV as is needed.
    144:   environment("RAILS_ENV" => "production",
    145:               "VERSION" => `ls -1 /opt/opscode/embedded/service/oc_id/db/migrate | tail -n 1 | sed -e "s/_.*//g"`.chomp)
    146:
    147:   only_if { is_data_master? }
    148: end
    149:
    150: component_runit_service "oc_id" do
    151:   package 'private_chef'
    152: end
    153:
    154: if node['private_chef']['bootstrap']['enable']
    155:   execute "/opt/opscode/bin/private-chef-ctl start oc_id" do
    156:     retries 20
    157:   end
    158: end
    159:

    Compiled Resource:
    ------------------
    # Declared in /opt/opscode/embedded/cookbooks/cache/cookbooks/private-chef/recipes/oc_id.rb:130:in `from_file'

    execute("oc_id_schema") do
      action :run
      retries 0
      retry_delay 2
      default_guard_interpreter :execute
      command "bundle exec rake db:migrate"
      backup 5
      cwd "/opt/opscode/embedded/service/oc_id"
      environment {"RAILS_ENV"=>"production", "VERSION"=>"20140313153625"}
      path ["/opt/opscode/embedded/bin"]
      returns 0
      declared_type :execute
      cookbook_name "private-chef"
      recipe_name "oc_id"
      only_if { #code block }
    end

Recipe: private-chef::rabbitmq
  * execute[restart_rabbitmq_log_service] action run
    - execute /opt/opscode/embedded/bin/sv restart /opt/opscode/sv/rabbitmq/log
Recipe: private-chef::postgresql
  * runit_service[postgresql] action restart
    - restart service runit_service[postgresql]
  * execute[restart_postgresql_log_service] action run
    - execute /opt/opscode/embedded/bin/sv restart /opt/opscode/sv/postgresql/log
Recipe: private-chef::oc_bifrost
  * runit_service[oc_bifrost] action restart
    - restart service runit_service[oc_bifrost]
  * execute[restart_oc_bifrost_log_service] action run
    - execute /opt/opscode/embedded/bin/sv restart /opt/opscode/sv/oc_bifrost/log
Recipe: private-chef::oc_id
  * runit_service[oc_id] action restart

    ================================================================================
    Error executing action `restart` on resource 'runit_service[oc_id]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '1'
    ---- Begin output of /opt/opscode/embedded/bin/sv restart /opt/opscode/service/oc_id ----
    STDOUT: fail: /opt/opscode/service/oc_id: unable to change to service directory: file does not exist
    STDERR:
    ---- End output of /opt/opscode/embedded/bin/sv restart /opt/opscode/service/oc_id ----
    Ran /opt/opscode/embedded/bin/sv restart /opt/opscode/service/oc_id returned 1

    Cookbook Trace:
    ---------------
    /opt/opscode/embedded/cookbooks/cache/cookbooks/runit/libraries/provider_runit_service.rb:184:in `restart_service'

    Resource Declaration:
    ---------------------
    # In /opt/opscode/embedded/cookbooks/cache/cookbooks/enterprise/definitions/component_runit_service.rb

     37:   runit_service component do
     38:     action :enable
     39:     retries 20
     40:     control params[:control] if params[:control]
     41:     options(
     42:       :log_directory => log_directory
     43:     )
     44:     params[:runit_attributes].each do |attr_name, attr_value|
     45:       send(attr_name.to_sym, attr_value)
     46:     end
     47:   end
     48:

    Compiled Resource:
    ------------------
    # Declared in /opt/opscode/embedded/cookbooks/cache/cookbooks/enterprise/definitions/component_runit_service.rb:37:in `block in from_file'

    runit_service("oc_id") do
      params {:package=>"private_chef", :log_directory=>nil, :svlogd_size=>nil, :svlogd_num=>nil, :ha=>nil, :control=>nil, :runit_attributes=>{}, :action=>:enable, :name=>"oc_id"}
      provider Chef::Provider::Service::Runit
      action :enable
      supports {:restart=>true, :reload=>true, :status=>true}
      retries 20
      retry_delay 2
      default_guard_interpreter :default
      service_name "oc_id"
      pattern "oc_id"
      status_command "/opt/opscode/embedded/bin/sv status /opt/opscode/service"
      sv_bin "/opt/opscode/embedded/bin/sv"
      sv_dir "/opt/opscode/sv"
      service_dir "/opt/opscode/service"
      lsb_init_dir "/opt/opscode/init"
      options {:log_directory=>"/var/log/opscode/oc_id"}
      log true
      restart_on_update true
      run_template_name "oc_id"
      log_template_name "oc_id"
      check_script_template_name "oc_id"
      finish_script_template_name "oc_id"
      sv_templates true
      service_mirror # Declared in

    service("oc_id") do
      provider Chef::Provider::Service::Simple
      action :nothing
      supports {:restart=>true, :reload=>true, :status=>true}
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      service_name "oc_id"
      pattern "oc_id"
      start_command "/opt/opscode/embedded/bin/sv start /opt/opscode/service/oc_id"
      stop_command "/opt/opscode/embedded/bin/sv stop /opt/opscode/service/oc_id"
      status_command "/opt/opscode/embedded/bin/sv status /opt/opscode/service/oc_id"
      restart_command "/opt/opscode/embedded/bin/sv restart /opt/opscode/service/oc_id"
    end

      declared_type :runit_service
      cookbook_name "private-chef"
      recipe_name "oc_id"
    end

Running handlers:
[2015-07-13T15:21:36+00:00] ERROR: Running exception handlers
Running handlers complete
[2015-07-13T15:21:36+00:00] ERROR: Exception handlers complete
Chef Client failed. 135 resources updated in<PHONE_NUMBER>46 seconds
[2015-07-13T15:21:36+00:00] FATAL: Stacktrace dumped to /opt/opscode/embedded/cookbooks/cache/chef-stacktrace.out
[2015-07-13T15:21:36+00:00] FATAL: Chef::Exceptions::RunFailedWrappingError: Found 1 errors, they are stored in the backtrace

This is an ordering problem. Reproduced again. The work around is to stop chef, and reconfigure again.
chef-server-ctl reconfigure
# Wait for error
chef-server-ctl stop
chef-server-ctl reconfigure

Im experiencing the same issue.  any luck resolving this?

Unfortunately I can't remember exactly what I did to work around it. Looking at my bash history, I believe it was as simple as rebooting the machine and manually stopping all dependent services. (rabbitmq, postgres, ect...)
  404  15/10/15 11:43:01 chef-server-ctl stop & chef-server-ctl start & chef-server-ctl tail
  405  15/10/15 11:43:01 chef-server-ctl reconfig
  406  15/10/15 11:43:01 chef-server-ctl reconfigure
  407  15/10/15 11:43:01 chef-server-ctl status
  408  15/10/15 11:43:01 chef-server-ctl test
  409  15/10/15 11:43:01 chef-server-ctl status
  410  15/10/15 11:43:01 chef-server-ctl restart
  411  15/10/15 11:43:01 chef-server-ctl test
  412  15/10/15 11:43:01 chef-server-ctl status
  413  15/10/15 11:43:01 chef-server-ctl tail
  414  15/10/15 11:43:01 chef-server-ctl reconfigure
  415  15/10/15 11:43:01 chef-server-ctl restart
  416  15/10/15 11:43:01 chef-server-ctl upgrade
  417  15/10/15 11:43:01 chef-server-ctl status
  418  15/10/15 11:43:01 chef-server-ctl reconfigure
  419  15/10/15 11:43:01 chef-server-ctl restart
  420  15/10/15 11:43:01 reboot
  421  15/10/15 11:43:01 chef-server-ctl tail
  422  15/10/15 11:43:01 chef-server-ctl test
  423  15/10/15 11:43:01 apt-get update
  424  15/10/15 11:43:01 apt-get upgrade
  425  15/10/15 11:43:01 opscode-reporting-ctl reconfigure

This happened to me after I had an error during installation. The solution was to reset the machine.

I am facing similar problems during the chef-server cookbook run:
https://github.com/chef-cookbooks/chef-server/issues/125
Any idea how to fix it?

Ran into this before moving away from a t2.micro instance. Forgot to triple check the mins on hardware reqs for Chef Server.

Just another data point: vm with 4 vCPU / 4G was failing, 8 vCPU / 16G succeeded,
on chef-server-core_12.15.8-1_amd64.deb and https://github.com/chef-cookbooks/chef-server/releases/tag/v5.4.0, gives the following error but proceeds:
`* execute[chef-server-core-reconfigure] action run[2017-07-24T10:36:56-07:00] INFO: Processing execute[chef-server-core-reconfigure] action run (/home/user/.chef/local-mode-cache/cache/cookbooks/chef-ingredient/libraries/chef_ingredient_provider.rb line 105)
  [execute]
            ================================================================================
            Error executing action `run` on resource 'ruby_block[restart_service]'
            ================================================================================

            Mixlib::ShellOut::ShellCommandFailed
            ------------------------------------
            Expected process to exit with [0], but received '1'
            ---- Begin output of /opt/opscode/embedded/bin/sv restart /opt/opscode/service/oc_id ----
            STDOUT: timeout: run: /opt/opscode/service/oc_id: (pid 8858) 31s, got TERM
            STDERR:
            ---- End output of /opt/opscode/embedded/bin/sv restart /opt/opscode/service/oc_id ----
            Ran /opt/opscode/embedded/bin/sv restart /opt/opscode/service/oc_id returned 1

            Cookbook Trace:
            ---------------
            /var/opt/opscode/local-mode-cache/cookbooks/runit/libraries/helpers.rb:174:in `tap'
            /var/opt/opscode/local-mode-cache/cookbooks/runit/libraries/helpers.rb:174:in `safe_sv_shellout!'
            /var/opt/opscode/local-mode-cache/cookbooks/runit/libraries/helpers.rb:202:in `restart_service'
            /var/opt/opscode/local-mode-cache/cookbooks/runit/libraries/provider_runit_service.rb:56:in `block (3 levels) in <class:RunitService>'
            /var/opt/opscode/local-mode-cache/cookbooks/runit/libraries/provider_runit_service.rb:282:in `block in <class:RunitService>'

            Resource Declaration:
            ---------------------
            # In /var/opt/opscode/local-mode-cache/cookbooks/runit/libraries/provider_runit_service.rb

             53:         ruby_block 'restart_service' do
             54:           block do
             55:             action_enable
             56:             restart_service
             57:           end
             58:           action :nothing
             59:           only_if { new_resource.restart_on_update && !new_resource.start_down }
             60:         end
             61:

            Compiled Resource:
            ------------------
            # Declared in /var/opt/opscode/local-mode-cache/cookbooks/runit/libraries/provider_runit_service.rb:53:in `block in <class:RunitService>'

            ruby_block("restart_service") do
              action [:nothing]
              retries 0
              retry_delay 2
              default_guard_interpreter :default
              block_name "restart_service"
              declared_type :ruby_block
              cookbook_name "private-chef"
              block #<Proc:0x00000008244c28@/var/opt/opscode/local-mode-cache/cookbooks/runit/libraries/provider_runit_service.rb:54>
              only_if { #code block }
            end

            Platform:
            ---------
            x86_64-linux

            Chef Server Reconfigured!

[2017-07-24T10:41:03-07:00] INFO: execute[chef-server-core-reconfigure] ran successfully
- execute chef-server-ctl reconfigure
`

This was a hardware resources issue with me. I was able to successfully run chef-server-ctl reconfigure on a 2 CPU 2GB RAM Digital Ocean droplet.

Sorry it took so long to respond to your issue! Currently we run the Chef Infra Server test pipeline with a t3.medium instance (2 VCPUs and 4 GB memory). And that does not seem to run into issues. We would recommend using instances larger than this. Closing for now, please feel to open if you see this issue on larger instances with newer builds.


Update build configuration

The build configuration of this project is outdated and may no longer work.
This pull request will be merged automatically if there are no conflicts.

:tada: This PR is included in version 2.4.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore: add more pre-commit hooks

Description
Add addtional pre-commit hooks for:

large files accidentially added
merge conflicts
shebang
Terraform formatting is done automatically
format json, yml and markdown files

Verification
Source code not touched.
Checklist

[x] My code follows the style guidelines of the project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] I have used pre-commit hook to update the Terraform documentation

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


nixos/{firewall,nat}: Standardize around an iptables-restore / nftables solution

Right now we use a command defined set of firewall rules. This allows for mutability of rules during normal operation and a simple, flexible interface for users to add new firewall rules using iptables commands.
While this approach has worked in the past, it would be nice to standardize on a cleaner firewall interface using the iptables-restore or nftables utilities.
Personally I'd like to see nftables used for this, as it seems to be the future direction of the linux packet filtering stack.

Currently, are changes made to firewall/nat applied atomically (to prevent packet drops)? (this could be done using iptables-restore).
To deal with external services also modifying iptables, there might be a way to merge the modifications together. Would the ipset utility help? http://ipset.netfilter.org/index.html

ipset only helps for ip address matches, not for generic iptables rules.
Unfortunately just using iptables-restore doesn't actually give you
atomicity in your rule chain as it just processes the clears / adds
internally. You would need to use a modern kernel with nftables to achieve
this effect. Unfortunately that is going to require users to port their
current config to a next generation nftables firewall. I think there is
something to be gained by having both implementations side by side and
phasing out the old one over the period of say a year.
On Mon, Sep 14, 2015 at 11:13 PM Roger Qiu<EMAIL_ADDRESS>wrote:

Currently, are changes made to firewall/nat applied atomically (to prevent
packet drops)? (this could be done using iptables-restore).
To deal with external services also modifying iptables, there might be a
way to merge the modifications together. Would the ipset utility help?
http://ipset.netfilter.org/index.html
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/4155#issuecomment-140290913.

@wkennington iptables-restore does actually clear and apply the rules in a single transaction, and any errors simply result in the previous state continuing on as normal. There's no opportunity for packets to be incorrectly accepted or dropped. In what way is it not atomic?

Ah, I didn't realize we had true atomic support with iptables-restore. At
any rate, I'm still not sure how you would account for externally applied
for rules yet.
On Tue, Sep 15, 2015, 03:57 Alexei Robyn<EMAIL_ADDRESS>wrote:

@wkennington https://github.com/wkennington iptables-restore does
actually clear and apply the rules in a single transaction, and any errors
simply result in the previous state continuing on as normal. There's no
opportunity for packets to be incorrectly accepted or dropped. In what way
is it not atomic?
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/4155#issuecomment-140353336.

Let's try to shrink the problem at least.
To address the external iptables rule I guess we need some intelligence in parsing iptables-save, in order to readd them in an eventual iptables-restore. Is that the only approach possible?

What I'm worried about is how this will interact with
networking.firewall.extraCommands which expect the state of the firewall to
be flushed prior to being executed and therefore cannot be saved. Given
that this conflicts with the idea of parsing running rules to be saved, I
don't think you can come up with a strategy here that doesn't break
something. It would be better to create an entirely new interface with no
surprises and have users migrate.
On Tue, Sep 15, 2015, 11:09 lethalman<EMAIL_ADDRESS>wrote:

Let's try to shrink the problem at least.
To address the external iptables rule I guess we need some intelligence in
parsing iptables-save, in order to readd them in an eventual
iptables-restore. Is that the only approach possible?
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/4155#issuecomment-140486482.

Sacrificing extraCommands sounds acceptable if we get an atomically updated firewall in exchange.

That's utterly terrible given the only way to configure a marginally
complex firewall with our current options is to use extraCommands. It would
make way more sense to drop all runtime supplied firewall rules before
breaking extraCommands, as users should not expect NixOS to preserve
stateful configuration which it already manages.
Again, this is why a new interface needs to be made. There is no reason why
we can't create options which have the ability to define complex nftables
or iptables-restore rules. This would then replace the current firewall
with something flexible that shouldn't need extraCommands.
On Tue, Sep 15, 2015, 11:42 Eelco Dolstra<EMAIL_ADDRESS>wrote:

Sacrificing extraCommands sounds acceptable if we get an atomically
updated firewall in exchange.
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/4155#issuecomment-140494742.

What about when you need atomicity between iproute2 mutation and iptables mutation? Often for complex networks you would setup an virtual interfaces, network namespaces... etc, and then change the iptable rules. How can we compose these actions together into a single atomic change?
@wkennington a new interface in the Nix language that abstracts over iptables/nftables?

(triage) any new leads?

It would be quite nice to have something like mutableFirewall akin to the multipleUsers option. I'm not sure if/how we can enforce this.

I had a short discussion about this yesterday on the IRC channel with @cleverca22.
There are other issues here like how this would interact with docker or other services that dynamically create firewall rules.
AFAICS there are basically two options:

Just accept that IP table rules will be modified by other systems. Parse iptables-save and diff it with the previously saved version to see which rules were manually added. Then generate a new set of firewall rules from the configuration (and the "impure" rules) and apply it atomically. Unfortunately, this will cause a race issue between e.g. docker issuing new iptables commands and the activation of a new firewall.
Creating an iptables wrapper program.

For the iptables wrapper, again, there are two options:

A thin iptables wrapper would just flock() on some file to prevent this race issue. The firewall activation script must flock() this as well to make it act like a mutex. Parsing would work the same as in (1).
Creating a fat iptables wrapper that would manage "custom" iptables state in some /var/run/firewall. flock() is still required. There are two ways to implement this:

Just add the rules to /var/run/firewall. If it's a rule that would remove or modify a chain, check which would match and remove/modify it.
Interpret the rules ourselves and store them in a database. Then generate input for iptables-restore from this. We might do fancy stuff like creating a iptablesCommandFor "daemonName", that would allow us to track by which daemon a firewall rule was created. It even could do some form of access control to only allow a daemon to modify certain rules through the iptables wrapper.

There should be a way for a program to lock iptables, while changing something else at the same time, and then unlock it. Other programs should then queue their iptable changes. Perhaps this can allow one to compose atomic network changes?

Hmm, this sounds overkill and risky. Since firewal rules usually don't change often, wouldn't it be enough to apply our rules with iptables-restore and then reload the services that need to add custom rules ?
This is how I used to do it on debian + iptables-restore + docker IIRC

that is one of the options i had on IRC
a related option, is to patch the docker scripts to make a hook that returns a fragment of an iptables-restore file, and then you concat the output of all of the hooks and the real firewall, and pipe the final result into iptables-restore, but now docker has to provide that hook, and reload the firewall.service target to apply changes

This is not a new problem. Every daemon that changes firewall rules has to deal with admins trashing the rules (just google "<service> iptables-restore" to see). Services usually recommend some kind of workaround: libvirt supports reloading its rules on receiving a HUP signal; fail2ban makes it easy to grep on f2b-* chains; etc.
Rather than trying to make service-specific workarounds, I think it would be sufficient to make declarative rules easier to filter out.
Here is what I suggest:

add a common service.iptables option with a thin wrapper around iptables-restore rules that would force any defined chain name to start with "nixos-". It would need to redirect the usual INPUT, FOWARD, etc. chains accordingly (see also https://github.com/NixOS/nixpkgs/pull/12940).
The interface could look something like:
service.iptables.filter.nixos-forward = ''
  -s <IP_ADDRESS>/24 -j ACCEPT
  -j DROP
'';

There's probably a better interface than this but the idea is to be able to filter out nixos-defined rules easily

make firewall.nix and nat.nix use this new interface

on firewall reload:

filter out nixos-specific chains from the output of iptables-save
generate the new nixos-specific rules as an iptables-restore file fragment
call iptables-restore with the concatenation of the two previous steps

This would allow arbitrarily complex firewall setups, apply them atomically, and interact seamlessly with daemons like fail2ban.
This may be a good rfc to submit to https://github.com/NixOS/rfcs.
Further steps may be:

implementing a similar interface for nftables
allowing to choose between iptables and nftables for firewall.nix and nat.nix
coming up with more abstractions to build on top of these interfaces (see e.g. https://github.com/NixOS/nixpkgs/issues/23181, https://github.com/NixOS/nixpkgs/pull/18842#issuecomment-249292527, https://github.com/NixOS/nixpkgs/pull/22586)

Even simpler: we could instead append -m comment --comment "nixos-fw" to each nixos-defined rule

Any news on this issue?

Some should combine these comments into an RFC so we can collaborate there
and close this issue. I have my plate full right now, any volunteers?

still definitely important

Still important. I have my plate full with other RFC stuff right now, but am happy to help however I can short of driving that process.

Is it possible to atomically replace individual tables inside nftables?
The currently proposed iptables-{save,restore} approach indeed has a lot of problems, similar to exclusively replacing all nftable rules in our nftables module - there's many different things in the system, except from the NixOS firewall with legitimate cases to insert things into the firewall.
If that's possible, one way out of this could be to have a NixOS-firewall specific nftables table. Other things could still mock around with iptables or their own nftables table, but they would stomp less on each others' feet.

That's a good idea. I don't know offhand, I'll wait for someone else to chime in and if nobody else does we should research it.


cross platform friendly

I cannot execute npm run clean on Windows.
This  pull request makes npm-script to cross platform friendly.

Codecov Report

Merging #126 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #126   +/-   ##
=======================================
  Coverage   96.63%   96.63%
=======================================
  Files          10       10
  Lines         327      327
  Branches       19       19
=======================================
  Hits          316      316
  Misses         11       11

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7a0b452...ff140de. Read the comment docs.

I signed it!


Bug: type dropdown box is always set to normal

Can happily change the type to other types and the page reloads the data, but can't then easily select normal again
The dropdown should be on the highlighted type
Also the order is nondeterministic, it should have an order to it.

Fixing this by exploring the router option in dioxus. Making urls more like /dex/:dex/type/:type

done


Xunit Project sample code

This PR was declined because will be implemented in a different way in future version.


Add delete project endpoint

Users need to be able to delete projects since there will be a maximum projects limit of 10

Being done here: #107


[TheTVDBBridge] Replace API key

Replaces API key with one that works. Closes #1434

I'm sure everyone appreciates your selflessness, but not sure if the TVBridge people will be happy to have many RSS Bridge installations sharing your account credentials.
At a minimum, the site operators should be informed, to make sure those credentials are not quickly banned.
See #1343 for supporting private credentials, per instance. #1170 is for private feeds.

https://thetvdb.com/api-information
If the old credentials are disabled for some reason, perhaps they need to be refreshed somehow?

Is there still interest in this?

No. TheTVDB has changed its API model and now requires you to pay to use it.


KAFKA-2983: Remove Scala consumers and related code

Removed Scala consumers (SimpleConsumer and ZooKeeperConsumerConnector)
and their tests.
Removed Scala request/response/message classes.
Removed any mention of new consumer or new producer in the code
with the exception of MirrorMaker where the new.consumer option was
never deprecated so we have to keep it for now. The non-code
documentation has not been updated either, that will be done
separately.
Removed a number of tools that only made sense in the context
of the Scala consumers (see upgrade notes).
Updated some tools that worked with both Scala and Java consumers
so that they only support the latter (see upgrade notes).
Removed BaseConsumer and related classes apart from BaseRecord
which is used in MirrorMakerMessageHandler. The latter is a pluggable
interface so effectively public API.
Removed ZkUtils methods that were only used by the old consumers.
Removed ZkUtils.registerBroker and ZKCheckedEphemeral since
the broker now uses the methods in KafkaZkClient and no-one else
should be using that method.
Updated system tests so that they don't use the old consumers except
for multi-version tests.
Some multi-version system tests had not been updated to include
recently released versions, fixed it.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@lindong28, do you have time to take a look? I started a system tests run, but maybe you could take an initial pass, if you have time.

@ijuma Sure! I will review it.

@ijuma nit: could you please also remove ZookeeperConsumerConnector related <Match> from gradle/findbugs-exclude.xml ?

Rebased and addressed the comments so far. Filed KAFKA-7062 and KAFKA-7063 for follow-ups. If anyone wants to pick them up, feel free. :)

@lindong28, I fixed a few system test issues. One of the remaining ones is log_dir_failure_test.py. 3 of 4 are failing since they have been switched to use the new consumer. I took an initial look and the issue is that the coordinator is not available for the duration of the produce/consume test for the code below:
# Verify the following:
            # 1) The broker with offline directory is the only in-sync broker of the partition of topic2
            # 2) Messages can still be produced and consumed from topic2
            self.producer = VerifiableProducer(self.test_context, self.num_producers, self.kafka, self.topic2,
                                               throughput=self.producer_throughput, offline_nodes=offline_nodes)
            self.consumer = ConsoleConsumer(self.test_context, self.num_consumers, self.kafka, self.topic2, group_id="test-consumer-group-2",
                                            consumer_timeout_ms=90000, message_validator=is_int)
            self.consumer_start_timeout_sec = 90
            self.start_producer_and_consumer()

Since you wrote this test, is there a chance you could take a look? It's a bit worrying that this doesn't work with the Java consumer.

@ijuma Sure, I will look into this issue.

I'm running the broker system tests in Jenkins again, but I believe the only remaining failing test is log_dir_failure_test.py.

@lindong28 do you think you'll have time to look into this today? If not, I'll partially disable the test, file a JIRA and merge this PR. These changes don't introduce the issue after all, they are just exposing the fact that the test as it stands doesn't work with the new consumer.

@ijuma Yes! I am looking into this now. Sorry for the delay.

@lindong28 Thanks! To be clear, there was no delay on your part, it's just that the timeline for this PR to make it into 2.0 is very short. :) So, I was trying to understand your availability to figure out the best path forward. I will wait in case there's an easy tweak to the test to make it pass with the new consumer.

@lindong28 interestingly, only 1 of 4 log dir failure tests failed in the run I started last night:
https://jenkins.confluent.io/view/All/job/system-test-kafka-branch-builder/1804/consoleFull
So, it looks flaky instead of failing deterministically.

@lindong28 Looking at the test a bit more, when we "Shutdown all other brokers so that the broker with offline log dir is the only online broker", how do we ensure that there are no consumer_offsets partitions that become offline?

@ijuma Sure thing. I would be more than happy to make this into 2.0 to make it shiny instead of disabling the test :) Mostly likely I will be able to fix it today.
That is a very good point. The default offsets.topic.replication.factor in Kafka server is 3. Since we start three brokers in the test before we start producer and consumer, the offset topic will be created with RF=3. And I verified that the consumer offset topic is replicated across all three brokers and the test still failed.

Right. Do I understand correctly that we have 2 out of 3 brokers down and the remaining online broker has one log dir offline? It seems like some consumer offset partitions could be in the offline log dir, which would cause the coordinator to never become available again.

@ijuma Ah I see you point. Yes you are right. If the consumer offset topic is in the offline log directory of the only online broker then it will cause the CoordinatorNotAvailableException. Let me try to fix this problem. Thanks!

@lindong28 yes :)

@ijuma Thanks for the suggestion. I think the patch.txt (attached) could fix the issue. It can be applied to this PR by git am patch.txt.
patch.txt

Thanks @lindong28. The log dir failure tests pass after that patch is applied:
https://jenkins.confluent.io/view/All/job/system-test-kafka-branch-builder/1810/

@ijuma Great! The patch looks good overall when I reviewed a few days ago. A few minor commits have been made to ensure that we pass integration tests and system tests. Do you think it is necessary for me to go over this end-to-end again?

@lindong28, it's enough for you to review the commits added since your last review

Thanks for the reviews. Merging to trunk and 2.0.


Implement safeTransferFrom in the HR1155

Summary
We need to create safeTransferFrom method, following Harmony docs.

Already done in #29


replace single quotes with escaped double quotes in query

fixes the following syntax error when performing a GET http://localhost:9090/consoles/index.html.example:
error executing template __console_index.html.example: template: menu.lib:34:6: executing "menu" at <query "up{job='hapro...>: error calling query: Parse error at char 8: invalid syntax

I don't know whom to ping according to the contributing guidelines, so here you are @juliusv :-)

hm. now calling http://localhost:9090/consoles/node.html gives me another syntax error:
error executing template __console_node.html: template: prom.lib:43:69: executing "prom_query_drilldown" at <query $expr>: error calling query: Parse error at char 12: invalid syntax

do I have a configuration or setup problem?

@gesellix Thanks! This actually points out a bug in the new parser we just merged - single quotes were supported in the old parser, but apparently not in the new one. Single quotes were never documented, but I think it's important to keep backwards compatibility here since there's no good reason not to - @fabxc is on it. This will then obsolete this PR though...

@juliusv great, thanks! Would you have a rough time frame?
Nevertheless I'll close this PR.

@gesellix today probably :)

@juliusv w00t! that would  be huge :)

@gesellix Of course we always recommend using the latest released version when in trouble :)

@juliusv well, I tried the Docker image first, which seems to be bleeding edge,? but you're right, I'll continue with a more stable release :)

@gesellix On the other hand, @fabxc just fixed it in https://github.com/prometheus/prometheus/pull/685, so feel free to be our pre-release tester again :)

check: your pre-release looks good, at least regarding the single/double quotes in the templates. Thanks again, to @fabxc, too!


A hook for PageMetadata

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
Consider the PageMetadata component:
https://github.com/facebook/docusaurus/blob/6b618bc9e5fcc9d52d3aa49a9d447f4d7ea76d41/packages/docusaurus-theme-common/src/utils/metadataUtils.tsx#L27-L62
There's no way to hook into this and make adjustments. It would be cool if there was.
Has this been requested on Canny?
No
Motivation
I recently built a plugin which allows users to use Cloudinary as a CDN for images:
https://johnnyreilly.com/docusaurus-image-cloudinary-rehype-plugin
Whilst I'm able to use this to flip to Cloudinary for general image serving, I cannot for og:image / twitter:image which is surfaced in the PageMetadata component.  And interestingly, images there get hardcoded with the baseUrl of the site (which doesn't work for image CDNs)
It would be cool if it were possible to control this somehow.
API design
I'm not quite sure what makes sense, possibly a hook that cook be supplied in the docusaurus.config.js which would have current parameters as inputs, and new parameters as outputs.  Not really sure.
Open to suggestions.
Have you tried building it?
No
Self-service

[X] I'd be willing to contribute this feature to Docusaurus myself.

I had some thoughts about this problem in the past and my idea was rather to re-expose this (and maybe a few others) theme-common component as a first-class theme component so that you can swizzle (wrap/eject) it as any other theme component.
The need to customize this is quite uncommon so swizzle is probably a good-enough solution

It's not so easy to use a Node.js (Docusaurus config) callback in the frontend/client/theme components, unfortunately.

Oh really? Are there specific limitations?

The need to customize this is quite uncommon so swizzle is probably a good-enough solution

Yeah probably. Is there anything specific to do to make something swizzle-able?

Oh really? Are there specific limitations?

Your callback could use Node.js apis like fs and whatever. These things can't be used on the frontend. At best we could serialize/eval the function but it's quite limited and would also be confusing.
We probably need to split our single config file into 2 Node.js/Browser configs for that reason (Nextra does this, separate file for theme config: https://nextra.site/docs/docs-theme/theme-configuration)

Yeah probably. Is there anything specific to do to make something swizzle-able?

Just adding a new file alias in the theme classic should be enough, something like:
export {PageMetadata as default} from "@docusaurus/theme-common"

Thanks - that's helpful background


How to return shadow on android kitkat?

I use version <IP_ADDRESS>, and the shadow of the dialogue was, but after upgrading to 0.7.2+ shadow disappeared. How to get her back?

Sorry, you can't. At least not right now.
AppCompat 22.1's dialog themes are being used at the base of the library, so Google's library is providing the window background and shadow.


remove View Transitions extend tutorial

Description (required)
This removes one of the two "Extend the tutorial" tutorials as part of a larger restructuring of the tutorial/sidebar.
This removes the View Transitions tutorial but salvages some of the most-referred to content.
(Note: an example related to light/dark mode also exists in astro:before-swap, so the new example may not be needed/wanted. If we decide that the existing View Transitions page is helpful enough as it is, happy to not add any new content there!
Notably:

removes the Extend with View Transitions tutorial page
removes the Card at the end of the Build a blog tutorial suggesting this tutorial as a next step (there should not be any other existing internal links to this page)
adds a redirect from this page to the View Transitions guide

Follow up to come:

delete the "Add Content collections" tutorial and use that content for optional new module at the end of the existing tutorial

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

en/guides/view-transitions.mdx
Source changed, localizations will be marked as outdated.

en/tutorial/6-islands/3.mdx
Source changed, localizations will be marked as outdated.

en/tutorials/add-view-transitions.mdx
Source removed, will stop being tracked.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


several errors when monitoring netbox - HA -2021.9.3 - monitor_docker 1.10

I have netbox running as container using this link - https://github.com/netbox-community/netbox-docker
containers are running on a synology NAS
HA logs are spammed with the following:
2021-09-05 19:23:55 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:23:55 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:23:55 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:24:59 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:24:59 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:24:59 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:26:06 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:26:06 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:26:06 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:27:10 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:27:10 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:27:10 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:28:15 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:28:15 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:28:15 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:29:20 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:29:20 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:29:20 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:30:53 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Cannot determine CPU usage for container ('system_cpu_usage')
2021-09-05 19:30:53 ERROR (Thread-3) [custom_components.monitor_docker.helpers] Raw 'cpu_stats' {'cpu_usage': {'total_usage': 0, 'usage_in_kernelmode': 0, 'usage_in_usermode': 0}, 'throttling_data': {'periods': 0, 'throttled_periods': 0, 'throttled_time': 0}}
2021-09-05 19:30:53 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Cannot determine memory usage for container ('stats')
2021-09-05 19:30:53 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Raw 'memory_stats' {}
2021-09-05 19:30:53 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Can not determine network usage for container ('networks')
2021-09-05 19:30:53 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: No 'networks' found in raw packet
2021-09-05 19:31:27 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:31:27 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:31:27 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:32:32 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:32:32 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:32:32 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:34:40 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:34:40 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:34:40 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:35:43 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:35:43 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:35:43 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:36:48 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:36:48 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:36:48 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:37:52 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:37:52 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:37:52 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:38:57 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:38:57 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:38:57 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:40:03 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:40:03 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:40:03 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:41:07 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:41:07 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:41:07 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:42:04 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Cannot determine CPU usage for container ('system_cpu_usage')
2021-09-05 19:42:04 ERROR (Thread-3) [custom_components.monitor_docker.helpers] Raw 'cpu_stats' {'cpu_usage': {'total_usage': 0, 'usage_in_kernelmode': 0, 'usage_in_usermode': 0}, 'throttling_data': {'periods': 0, 'throttled_periods': 0, 'throttled_time': 0}}
2021-09-05 19:42:04 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Cannot determine memory usage for container ('stats')
2021-09-05 19:42:04 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Raw 'memory_stats' {}
2021-09-05 19:42:04 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Can not determine network usage for container ('networks')
2021-09-05 19:42:04 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: No 'networks' found in raw packet
2021-09-05 19:42:14 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:42:14 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:42:14 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:43:19 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:43:19 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:43:19 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:44:23 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:44:23 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:44:23 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:45:28 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:45:28 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:45:28 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:46:32 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:46:32 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:46:32 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:47:16 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Cannot determine CPU usage for container ('system_cpu_usage')
2021-09-05 19:47:16 ERROR (Thread-3) [custom_components.monitor_docker.helpers] Raw 'cpu_stats' {'cpu_usage': {'total_usage': 0, 'usage_in_kernelmode': 0, 'usage_in_usermode': 0}, 'throttling_data': {'periods': 0, 'throttled_periods': 0, 'throttled_time': 0}}
2021-09-05 19:47:16 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Cannot determine memory usage for container ('stats')
2021-09-05 19:47:16 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Raw 'memory_stats' {}
2021-09-05 19:47:16 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: Can not determine network usage for container ('networks')
2021-09-05 19:47:16 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_netbox_1: No 'networks' found in raw packet
2021-09-05 19:47:37 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:47:37 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:47:37 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:48:40 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:48:40 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:48:40 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring
2021-09-05 19:49:46 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Can not determine network usage for container ('networks')
2021-09-05 19:49:46 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: No 'networks' found in raw packet
2021-09-05 19:49:46 ERROR (Thread-3) [custom_components.monitor_docker.helpers] netbox_postgres_1: Too many errors on 'networks' stats, disabling monitoring

This worked before v1.10 or it never worked?

This worked fine before, but to be honest, the container was also updated recently to a newer version. The same docker-compose was used, just updated the container to a newer version (pulled a fresh "latest")

Ok, what do you see when you run "docker stats" on the same node? If there it is not available, it will not in the Docker API either.

I will close this old issue. If still persists, please open a new issue.


[SPARK-5364] [SQL] HiveQL transform doesn't support the non output clause

This is a quick fix for query (in HiveContext) like:
SELECT transform(key + 1, value) USING '/bin/cat' FROM src

Ideally, we need to refactor the ScriptTransformation, which should support the custom SerDe for reader & writer. Will do that in the follow up.

Test build #25959 has started for   PR 4158 at commit c8fe7fc.

This patch merges cleanly.

Hi @chenghao-intel, I already did this and support for custom field delimiter and SerDe in PR #4014.

Test build #25959 has finished for   PR 4158 at commit c8fe7fc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25959/
Test PASSed.

Thank you @viirya . This is just a quick fix in my use case. Hope it merge soon. And I will give some comment in your PR.

Test build #25996 has started for   PR 4158 at commit a7b6989.

This patch merges cleanly.

@viirya I've updated the code, which is a block issue for our partner, it's would be great if you can review this for me. And definitely the TODOs I leave there can be done in your PR #4014

Test build #25996 has finished for   PR 4158 at commit a7b6989.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25996/
Test PASSed.

@chenghao-intel overall it looks good for me except for small comments.

Test build #26069 has started for   PR 4158 at commit 5618fa7.

This patch merges cleanly.

Test build #26069 has finished for   PR 4158 at commit 5618fa7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26069/
Test PASSed.

Closing this since #4014 has been merged.


correct jupyter notebook package name

since ipython notebooks is now called jupyter notebooks they also changed the package names and the easiest thing to do is simply install jupyter package which brinks everything you'll need.

Thanks!


Minimum read-only RBAC permissions

Good day,
We have developers with edit access to some namespaces but not all and we don't want to give them cluster-admin access.
What are the minimum RBAC permissions required for the dashboard metrics to be populated?
Currently when we login to K8Dash as cluster-admin it works but logging in with edit access to a single namespace then the dashboard does not load.

Hey @jppitout. Thanks for the question. This is something that has come up a couple of times and is something we really need to resolve :(
I believe that the other permission you would need to give the user would be the ability to list namespaces. Would that be possible for this particular use case?

@herbrandson
Hi
im facing the same problem
in my scenario  I can't give some of them permission to list namespaces :(

Hi @herbrandson,
Apologies for not getting back to you sooner. The developers are using Lens now, so no need for this requirement anymore.


Fix Emoji Parsing Issue in Commits

Changes Made:
Modified the .cz-config.js file to use a placeholder for emojis in commit types.
Implemented a pre-commit hook to replace the placeholder with the actual emoji during commits.

This creates commits like:
[EMOJI_PLACEHOLDER] feat(core): testing](https://github.com/jjfantini/upwork-task/commit/d76d091e90a4ce98d217037eba19b164b4e645b4)


Central storage of session model data

Like the idea of registering models.
Like that all field values remain easily gettable from sessionModel (not just the current form vals)
Undecided about how tied this is to the journeyModel. I know that is our biggest use case but what if we wanted to collect session data that exists outside of the 'passport' journey? An example might be the data we need for the feedback form (although potentially that is journeyModel data) or maybe a module with its own ideas about where things should be stored on the session. Is this too much flexibity, or am I missing something in the implementation?
Would be good to get an explanation of how this can be used at the field level and also in terms of extending by registering more models.
Fwiw, have pushed up what I'd played around with yesterday in case of any value (not working code). Includes a flag (ignoreDefault) to allow fields to store outside of the journey model if needed. https://github.com/UKHomeOffice/passports-form-wizard/compare/feature/custom-session-storage-for-fields

LGTM