Syntax error correction in TestDatabases.php

Fixed parseError  syntax error, unexpected ')' correction caused by empty argument passed for Config()->set() method

https://github.com/laravel/framework/pulls?q=is%3Apr+TestDatabases
Laravel 8.x requires PHP 7.3 or above. This error comes from PHP 7.2 or earlier.
https://github.com/laravel/framework/blob/8.x/composer.json#L18-L19
To find the local PHP version installed for the command line:
php -v

It may differ from the PHP version configured for Apache/Nginx.

https://github.com/laravel/framework/pulls?q=is%3Apr+TestDatabases
Laravel 8.x requires PHP 7.3 or above. This error comes from PHP 7.2 or earlier.
https://github.com/laravel/framework/blob/8.x/composer.json#L18-L19
To find the local PHP version installed for the command line:
php -v

It may differ from the PHP version configured for Apache/Nginx.

Thanks for the info. It works fine in PHP 7.3. I will close the pull request.


cmd/go: repeatedly running all.bash in an unchanged tree grows the Go build cache without limit

What version of Go are you using (go version)?

$ go version
go version devel go1.22-890b96f7ab Thu Jul 20 08:03:42 2023 +0000 linux/amd64

Does this issue reproduce with the latest release?
This issue doesn't reproduce when building Go 1.20.6 from a 'git checkout go1.20.6' in the source tree.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/cks/.cache/go-build'
GOENV='/home/cks/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/cks/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/cks/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/w/620/cks/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/w/620/cks/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.22-890b96f7ab Thu Jul 20 08:03:42 2023 +0000'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/w/620/cks/go/src/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3572262321=/tmp/go-build -gno-record-gcc-switches'

What did you do?
git clone https://go.googlesource.com/go
cd go/src
./all.bash
du -hs ~/.cache/go-build
./all.bash
du -hs ~/.cache/go-build
[repeat]

The first all.bash from source will create about 2.3 GB of Go build cache. Subsequent all.bash runs appear to increase this by about 200 Mbytes each time. If you repeatedly build for long enough (if, for example, you're using this as a little stress test on a new system), this will fill up your $HOME with hundreds of GBytes of ~/.cache/go-build. 'go clean -cache' cleans it all away.

cc @bcmills @matloob

Just a note that every 24 hours the cache is checked for old entries, and entries that are older than 5 days are deleted.  So in the long run there is a limit.
But it does seem odd that running all.bash with the same sources would increase the cache size.

@siebenmann, some questions:

Does the cache grow when you run make.bash, or only all.bash?
Does the output of go tool compile -V=full change between runs?
Do you see similar growth if you run go test -short std cmd?

Specifically, I wonder if that ~200 MB of data per run is due to caching packages built from within test temp directories. If so, maybe some tests should be updated to build with -trimpath or similar to get the temp directories out of the cache keys.

(There may be a cmd/go bug here as well — for example, it is possible that this data is in package indexes, which IIRC currently contain absolute paths.)

This growth doesn't happen with just 'make.bash' (which only seems to use 455 MBytes or so from a clean cache). Running go test -short std cmd repeatedly doesn't seem to cause growth, but I'm not sure I'm doing it right because it fails (when all.bash succeeds). There's no difference between go tool compile -V=full outputs across multiple 'all.bash' runs, despite the build cache growing.
In terms of the cache's growth rate versus periodic trimming, the cache size can reach hundreds of GBytes (I saw over 350 GB) if you're running 'all.bash' in a loop repeatedly.

Running go test -short std cmd repeatedly doesn't seem to cause growth, but I'm not sure I'm doing it right because it fails (when all.bash succeeds).

Huh. Could you file a separate issue for the failures you observe from that? (It ought to work.)


Animal brain templates can be applied to other animal types

Describe the bug
As-is, an Alpaca template can be applied to a Panther clone. This doesn't make sense.
Expected behavior
Brain templates can only be applied to animals of the same type. Alpaca templates can only be applied to Alpacas and not Panthers.

Fixed in development branch. This change will be included in the next patch.


Add command to bulk set must-change-password

As part of administration sometimes it is appropriate to forcibly tell users to update their passwords.
This PR creates a new command gitea admin user must-change-password which will set the MustChangePassword flag on the provided users.
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

The majority of this PR is just reducing the size of cmd/admin.go by extracting out the gitea admin user commands.
The actual main contents of this PR is in admin_user_must_change_password.go and models/user/must_change_password.go with docs in command-line.en-us.md

Why do you think we need to backport this to v1.18 ?

@lunny what was the answer to your question?

Why do you think we need to backport this to v1.18 ?

@lunny what was the answer to your question?

This command provides an important tool for server administrators who wish to force users to change their password for whatever reason - likely security related reasons. The command is well contained and can easily be backported. It is a key security tool for server administrators that has been missing for a while.
Whilst we would not normally backport small enhancements like this - sometimes key server administrator tools that have almost zero other effects on the other code should be backported.
The other benefits in this PR are the cleaning up of cmd/admin.go which was previously an horrendously long file - which will now be much easier to fix bugs in.

🎺 🤖


soc: silabs_exx32: Enable mpu on efr32mg soc

Enables the arm v7m mpu on the efr32mg soc and the board
efr32mg_sltb004a.
Tested on hardware with samples/mpu/mpu_test and
tests/kernel/mem_protect
Signed-off-by: Christian Taedcke<EMAIL_ADDRESS>

@ioannisg

BTW, are you able, now to execute all sanity check -t usermode tests properly?

How do i do that?
I tried executing scripts/sanitycheck --device-testing --device-serial /dev/ttyACM0 -p efr32mg_sltb004a but this broke my onboard debug adapter (segger) somehow.

@ioannisg

BTW, are you able, now to execute all sanity check -t usermode tests properly?

How do i do that?
I tried executing scripts/sanitycheck --device-testing --device-serial /dev/ttyACM0 -p efr32mg_sltb004a ~but this broke my onboard debug adapter (segger) somehow~.

Just confirm that you are able to run tests on the platform that are tagged with userspace.

Just for reference: I executed
scripts/sanitycheck --device-testing --device-serial /dev/ttyACM0 --west-flash="--reset-after-load" -p efr32mg_sltb004a -t userspace -v
It returned:
40 of 42 tests passed (100.00%), 0 failed, 2 skipped with 0 warnings in 357.63 seconds

Just for reference: I executed
scripts/sanitycheck --device-testing --device-serial /dev/ttyACM0 --west-flash="--reset-after-load" -p efr32mg_sltb004a -t userspace -v
It returned:
40 of 42 tests passed (100.00%), 0 failed, 2 skipped with 0 warnings in 357.63 seconds

Then that should be fine for me to merge. I leave this to @galak

@galak ping for review


feat: explain dist stream plan

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
example for the tpch-q18
 explain (distsql) create materialized view mv as ...
 Fragment 0
   StreamMaterialize { columns: [c_name, c_custkey, o_orderkey, o_orderdate, o_totalprice, quantity], pk_columns: [c_name, c_custkey, o_orderkey, o_orderdate, o_totalprice], order_descs: [o_totalprice, o_orderdate, c_name, c_custkey, o_orderkey] }
     StreamProject { exprs: [customer.c_name, customer.c_custkey, orders.o_orderkey, orders.o_orderdate, orders.o_totalprice, sum(lineitem.l_quantity)] }
       StreamTopN { order: "[orders.o_totalprice DESC, orders.o_orderdate ASC]", limit: 100, offset: 0 }
         StreamExchange Single from 1

 Fragment 1
   StreamGroupTopN { order: "[orders.o_totalprice DESC, orders.o_orderdate ASC]", limit: 100, offset: 0, group_key: [6] }
     StreamProject { exprs: [customer.c_name, customer.c_custkey, orders.o_orderkey, orders.o_orderdate, orders.o_totalprice, sum(lineitem.l_quantity), Vnode(orders.o_orderkey)] }
       StreamProject { exprs: [customer.c_name, customer.c_custkey, orders.o_orderkey, orders.o_orderdate, orders.o_totalprice, sum(lineitem.l_quantity)] }
         StreamHashAgg { group_key: [customer.c_name, customer.c_custkey, orders.o_orderkey, orders.o_orderdate, orders.o_totalprice], aggs: [count, sum(lineitem.l_quantity)] }
           StreamExchange No_shuffle from 2

 Fragment 2
   StreamHashJoin { type: LeftSemi, predicate: orders.o_orderkey = lineitem.l_orderkey }
     StreamExchange No_shuffle from 3
     StreamProject { exprs: [lineitem.l_orderkey] }
       StreamFilter { predicate: (sum(lineitem.l_quantity) > 1:Int32) }
         StreamProject { exprs: [lineitem.l_orderkey, sum(lineitem.l_quantity)] }
           StreamExchange No_shuffle from 8

 Fragment 3
   StreamHashJoin { type: Inner, predicate: orders.o_orderkey = lineitem.l_orderkey }
     StreamExchange Hash([2]) from 4
     StreamExchange Hash([0]) from 7

 Fragment 4
   StreamHashJoin { type: Inner, predicate: customer.c_custkey = orders.o_custkey }
     StreamExchange Hash([0]) from 5
     StreamExchange Hash([1]) from 6

 Fragment 5
   Chain { table: customer, columns: [c_custkey, c_name] }
     Upstream
     BatchPlanNode

 Fragment 6
   Chain { table: orders, columns: [o_orderkey, o_custkey, o_totalprice, o_orderdate] }
     Upstream
     BatchPlanNode

 Fragment 7
   Chain { table: lineitem, columns: [l_orderkey, l_quantity, l_linenumber] }
     Upstream
     BatchPlanNode

 Fragment 8
   StreamHashAgg { group_key: [lineitem.l_orderkey], aggs: [count, sum(lineitem.l_quantity)] }
     StreamExchange Hash([0]) from 9

 Fragment 9
   Chain { table: lineitem, columns: [l_orderkey, l_quantity, l_linenumber] }
     Upstream
     BatchPlanNode

(55 rows)

What's changed and what's your intention?
PLEASE DO NOT LEAVE THIS EMPTY !!!
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

Should we print stream operator's internal tables?


simplified bootkube status output

Bootkube currently displays a lot of log output from apiserver+scheduler+controller-manager. This can be confusing and makes it difficult to determine if things are "going well".
We should provide some simplified output of bootkube state (although I think we still need to preserve the log output, as that is the primary means for debugging issues.).
The simplified output might be something like:
control-plane started
manifests created
pods pending
done
One option is to split log vs state output on stdout and stderr.
/cc @sym3tri

@aaronlevy not sure I understood the option you suggested. Would a log file approach on each start of provisioning be a good idea? Dump the verbose output into the log file while showing the sequence of steps of provisioning on the console.

@aaronlevy not sure I understood the option you suggested. Would a log file approach on each start of provisioning be a good idea? Dump the verbose output into the log file while showing the sequence of steps of provisioning on the console.

@kenan435 myy initial thought was do so something like putting log output on stdout & the "status" messages on stderr, which would allow a deployer to self-select what they see.
bootkube foo = see all messages (log + status)
bootkube foo > log.txt = redirect verbose log to file
bootkube foo 2> status.txt = redirect status messages to file
bootkube foo &> all.txt = redirect all output to file
Also was thinking that we could possibly send events to the kubernetes api, that way you could also see status as kubectl get events --namespace=kube-system
/cc @pbx0 as he's been taking a look at this

I'm basically implementing it with the same stdout/stderr split for now.  I have them reversed at the moment, stdout is for status and stderr is for logs. I like it better in reverse now that you point it out.

fixed in https://github.com/kubernetes-incubator/bootkube/pull/123


Bump metabase version to 0.44.6

Please bump the version of metabase to 0.44.6
Closes https://github.com/pmint93/helm-charts/issues/43

Thanks @zahir-koradia


bug(collections): Incorrect focus when creating a new document with space collection open

The newly created document in a new plank should receive the focus, but there's a race condition where the newly added document in the space collection receives focus instead.

duplicate of #7045


[boringssl] Update port to 2023-09-25

Since #34011 has been merged we can finally update the boringssl port. This is basically an update of #30986, but without the vcpkg-tools related stuff which got sort of superseeded by #31748

I removed the tools feature due to the fact that the BoringSSL buildsystem doesn't offer a corresponding configuration option and always installs bssl (which by the way is not referenced by the CMake configs).

Note that the boringssl port is not tested by the CI.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

If the corresponding triplet is fixed, please remove it in ci.baseline.txt: https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt#L91-L103

@MonicaLiu0311 the port is disabled in the CI baseline, because this port (BoringSSL) conflicts with OpenSSL, it's an unfortunate situation, but with the current infrastructure it can't be helped. See previous BoringSSL updates for further information (e.g. https://github.com/microsoft/vcpkg/pull/8455#issuecomment-584393250)

Note that the boringssl port is not tested by the CI.

@MonicaLiu0311 the port is disabled in the CI baseline, because this port (BoringSSL) conflicts with OpenSSL, it's an unfortunate situation, but with the current infrastructure it can't be helped. See previous BoringSSL updates for further information (e.g. #8455 (comment))

Successfully installed on the following local triplets:
x86-windows
x64-windows
x64-windows-static
x64-linux
x64-osx


textfield issue in mdc-111

Due to some reason I'm facing an issue in mdc-111 in the textfield component which is that only first text-field is applying the styles of the textfield component and floating label and other textfield of the forms are not.
don't know why
if anyone can help
below are the screenshots:

Can you share your HTML markup and MDC Web version that you're using to investigate?
Here is the latest full demo on Glitch that renders Text Field https://glitch.com/edit/#!/new-web

Please follow docs from material.io for up-to date documentation on latest HTML structure for text field.
Codelabs will be updated to v6 in #135


HTMLEditorField_Toolbar should not be a LeftAndMain action but a nested RequestHandler of HTMLEditorField

SilverStripe allows us to have multiple layers of nested controllers, and would therefore allow us to have HTMLEditorField_Toolbar as a sub RequestHandler of HTMLEditorField.
This would make the HTMLEditorField more portable, meaning easier usable outside of the LeftAndMain context such as in iframes (iframes of FormFields within the CMS) or the frontend.
And additionally also better encapsulate HTMLEditorField and removing code from LeftAndMain that never belonged there in the first place.
However, in order to implement this change, we will also have to refactor either LeftAndMain or the ID handling of file attachments or both.
Because currently a new file is attached via "?ID=$FielID", which LeftAndMain->getCurrentPageID() would mistake for a page ID. See issue #6675.

Sidenote: This issue has a real life inpact on my Content Blocks module, see https://github.com/Zauberfisch/silverstripe-page-builder#installation

Unfortunately, Silverstripe CMS 3 has entered limited support in June 2018. This means we'll only be fixing critical bugs and security issues for Silverstripe CMS 3 going forward.
You can read the Silverstripe CMS Roadmap for more information on our support commitments.


Add a Stat bonuses dictionary to Buffs

Buffs now implicitly give stats (percentage-based however), will need spoofing as well.

done for a while now.


Add a 256G drive and split it between Windows and Linux system

Currently only a 512GB drive is used for both data storage and the Operating System.
Get a 256G SSD and split it between Windows and Linux. Use the 512GB drive only for data storage.

My new laptop only has slot for a single NVMe drive so I'm just gonna dedicate a 50GB partition for it


cleanup golang port scanner example

Because I was a bit sloppy with the commit :sweat:

Coverage remained the same at 92.0% when pulling 59d0fbd50f7888033ac40aad517926ca3546f554 on picatz:add-golang-port-scanner-example into ed7de27c0fbde4af72cdb15fc65ffdd6d2f5fc2b on socketry:master.


Mod Not Working

I don't know if i made something wrong or if I don't look in the right place but the notches won't appear.
I'm currently running on Scarab with Modding API <IP_ADDRESS>33-71, ItemChanger 2.0.5+598 and the dependencies on a pre-existing save file. I didn't try to see if it works on a new save file.
I don't use a Randomizer because it seems to make my game crash on the start of a new save file (tried to launch a new classic save file with a Randomizer 4 build and MaskMakerNotches on but the game got stuck on main menu screen).

Having now tested to be sure, I can say that having the notches not appear on a save file which didn't have the mod installed when it was created is expected behaviour, as adding them to the world happens on save creation, not on save loading.
If the notches are still not there on a new save file, or if it's crashing like you said, can you attach a copy of your modlog.txt? It can usually be found in C:\Users%USER%\AppData\LocalLow\Team Cherry\Hollow Knight\ModLog.txt

Closing as it's been seven months with no reply.


remove a 0 at the end of the tree alias

Hi,
There was a 0 at the end of the "tree" alias, after the ending quote.
It was breaking the use of this alias.

Thank you for the fix.


Remove tags from project yaml

Per DevSite, tags have been deprecated for a while, officially removing from our _project.yaml files, and removing from valid params in tests

:+1:

:tada: This has been pushed live to https://developers.google.com/web/


Domain names in trusts are lower case

They should be upper case for compatibility with the original BloodHound ingestor
Really great tool btw

Fixed in latest master. Thanks for the report!


spoofdpi: 0.11.1 -> 0.12.0

Description of changes
update spoofdpi
fixes package.nix

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

sorry for repeat, previous PR was from master branch, not spoofdpi-update as needed.

OOM while running nixpkgs-review, what's happening

OOM while running nixpkgs-review, what's happening

lmao same, but package.nix built..

Result of nixpkgs-review pr 340525 run on x86_64-linux 1

:white_check_mark: 1 package built:

spoofdpi


Break after  Outlook for Mac

In Outlook for Mac v16.24 there are gaps (possibly margins I can't tell) after each
This is how it should appear:

This is how is appears in Outlook:

<mj-section background-color="#2780bc">
  <mj-column width="50%" vertical-align="middle">
    <mj-image width="150px" src="https://boomerbenefits.com/wp-content/uploads/2019/04/danielle-circle.png"></mj-image>
  </mj-column>
  <mj-column width="50%" vertical-align="middle">
    <mj-text css-class="hero-text" font-family="Helvetica, Arial, sans-serif"  font-size="14px" font-weight="600" color="#fff" padding-left="0" padding-right="0" vertical-align="middle">Medicare
Mini-Course</mj-text>
  </mj-column>
</mj-section>

<mj-section background-color="#ffffff" vertical-align="top">
  <mj-column vertical-align="top" width="100%">
    <mj-text font-family="Helvetica, Arial, sans-serif" align="left" color="#555" font-size="16px" padding-bottom="30px" padding-top="3px">Let's dive right in with Email Lesson 1 - Medicare Starts with the Parts

I created a checklist that will help you through this course. Each lesson corresponds
      to one step on the checklist; making it easy to track your progress. You can download it by clicking here!

 Put all that away!  For today, I want you to forget all that mail about Medigap plans. Just focus on learning about the Parts of Original Medicare. Understanding
      what each part covers will give you a foundation for all the other decisions ahead of you.

 I've also included the video that goes along with this lesson at the bottom, watch it to get a summary!</mj-text>
  </mj-column>
</mj-section>

<mj-section vertical-align="middle" background-color="#ffffff" padding="0">
  <mj-column width="100%" vertical-align="middle" padding="0">
    <mj-text font-family="Helvetica, Arial, sans-serif" align="center" padding="0" color="#555" font-size="25px">Medicare Starts with the Parts</mj-text>
  </mj-column>
</mj-section>

<mj-section vertical-align="middle" background-color="#ffffff">
  <mj-column width="50%" vertical-align="middle">
    <mj-image src="https://boomerbenefits.com/wp-content/uploads/2019/04/hospital.png" alt="" padding-bottom="20px" padding-top="20px" width="150px"></mj-image>
    <mj-text font-family="Helvetica, Arial, sans-serif" align="center" color="#555" font-weight="600" font-size="20px">Part A</mj-text>
  </mj-column>
  <mj-column width="50%" vertical-align="middle">
    <mj-image src="https://boomerbenefits.com/wp-content/uploads/2019/04/medical-kit.png" alt="" padding-bottom="20px" padding-top="20px" width="150px"></mj-image>
    <mj-text font-family="Helvetica, Arial, sans-serif" align="center" color="#555" font-weight="600" font-size="20px">Part B</mj-text>
  </mj-column>
</mj-section>

<mj-section vertical-align="middle" background-color="#ffffff" padding="0">
  <mj-column width="100%" vertical-align="middle" padding="0">
    <mj-text font-family="Helvetica, Arial, sans-serif" align="left" color="#555" font-size="16px" padding-bottom="30px" padding-top="3px">Original Medicare is made up of 2 parts:

Part A Hospital Insurance & Part B Outpatient Insurance. (Part C & D came later - and we'll address those further
      in the course)

 As part of today's lesson, you'll want to read about the Parts of Medicare and what each covers here.

 Tomorrow, we'll be delving into determining YOUR ANTICIPATED COSTS FOR MEDICARE. And if you're ahead of the curve and want to get started on finding your coverage, feel free to email me to request personal help.

Oh - I almost
      forgot! Stay tuned for a link to our next free New to Medicare Webinar. (I'll give you details in tomorrow's email.)
    </mj-text>
  </mj-column>
</mj-section>

<mj-section background-color="#ffffff" >
  <mj-column width="100%" vertical-align="middle">
    <mj-image href="https://www.youtube.com/watch?v=VtSGMsZCO38&feature=youtu.be" src="https://boomerbenefits.com/wp-content/uploads/2019/04/watch-video.png" alt="Boomer Benefits" padding-bottom="0px" padding-top="10px"></mj-image>
  </mj-column>
</mj-section>

<mj-section>
  <mj-column width="100%" padding="0">
    <mj-social font-size="15px" icon-size="30px" mode="horizontal" padding="0" align="center">
      <mj-social-element name="facebook" href="https://mjml.io/" background-color="#A1A0A0">
      </mj-social-element>
      <mj-social-element name="twitter" href="https://mjml.io/" background-color="#A1A0A0">
      </mj-social-element>
      <mj-social-element name="pinterest" href="https://mjml.io/" background-color="#A1A0A0">
      </mj-social-element>
      <mj-social-element name="instagram" href="https://mjml.io/" background-color="#A1A0A0">
      </mj-social-element>
      <mj-social-element name="linkedin" href="https://mjml.io/" background-color="#A1A0A0">
      </mj-social-element>
    </mj-social>
  </mj-column>
</mj-section>

<mj-section>
  <mj-column width="100%" vertical-align="middle">
    <mj-text align="center" font-size="11px" padding-bottom="0px" padding-top="0px">

[[DELIVERY_INFO]]

    </mj-text>
    <mj-text align="center" font-size="11px" padding-bottom="0px" padding-top="0px">

[[POSTAL_ADDRESS]]

    </mj-text>
  </mj-column>
</mj-section>

@jarrodwhitley I just tested on emailonacid and it renders fine on all outlooks
Outlook for mac is less likely to have issues than on windows, it could be your email provider altering the html, how did you send the email ?

@kmcb777 I'm using Drip and sending myself a test email. Since the email spoofs the domain the email automatically goes to my boss, who forwards it to me. He's using a PC. He said that the email looks like that in his inbox.

@jarrodwhitley it can be Drip altering the html when you send it, sadly many providers seem to do this.
Can you try to send it with https://putsmail.com/tests/new (don't check the "Move my css inline")
If it works with putsmail, then it is definitely Drip altering the html

Also note that forwarding an email breaks the layout because receiving servers alter the HTML when they render it, it's a well-known problem with email.

@kmcb777 I'll give that a try and see how it works. Thanks for the tip @ngarnier

@kmcb777 You were correct. When went with putsmail the email looks correct on Outlook. Thanks for help fellas.


How to change color of indicator

I tried to to change indicator color but it didn't changed at all. The color is always blue
tokenView.activityIndicatorColor = UIColor.red

Check this:
http://stackoverflow.com/a/42436203/1444321

My bad, you are asking about Activity Indicator color not token background color. It should work, as you have tried.
Check Objective-c example in latest source code. I have tried changing color to red, and it does work.
Please let me know if issue is still there.


Samples from Armenia are missing

Hi,
First of all, great job! The great idea behind the great app.
However, there is an issue I'd like to report and ask for your advice and help.
I'm trying to use the app to identify parent sequences for Armenian samples submitted to GISAID, but covizu reports only 24 sequences from 150 + sequences from Armenia deposited in GISAID. You can check in GISAID by filtering by region "Asia/Armenia".
I'd be grateful if you an provide with some instructions how to recover all samples.
Thanks,
Arsen

Hi Arsen, thanks for your feedback!  We apply some very strict filters while processing genome sequences, and this can end up removing a substantial fraction of any particular set of samples.  For example, we require that no more than 1% of the genome sequences is missing.  Based on my analysis of these records in the GISAID database, this filter affects at least 59 of 143 records.
I've confirmed that querying CoVizu by the search string "Armenia" returns 24 hits.  Please note that these hits correspond to what we call "beads".  A bead is a circle SVG element that represents one or more samples.  Beads are collected into variants (horizontal lines) that comprise samples that are genetically indistinguishable (either identical in sequence or not sufficiently divergent that they can be separated reproducibly in a phylogenetic tree).  In the case of lineage B.1.1.163, for example, the variant labelled Armenia/IMB1-6 has two beads representing three samples.  This only accounts for one additional sample, however.
Hope this helps!

Regarding instructions to recover all samples, the only thing I can suggest is for you to run your own instance of CoVizu by installing from the opendata branch and then eliminating the filtering criteria that are causing your samples to be excluded.  Sorry that we can't be of more help.

Dear Art Poon,
Thanks very much for the explanations. We will try to follow your advice and install CoVizu locally.
Best regards,
Arsen

Dear Art Poon,
I tried to follow your advice and run CoVizu locally. I have GISAID username and password, so I tried to use batch.py script, but I got following error:
Entering 'covizu/data/ProblematicSites_SARS-CoV2'
From https://github.com/W-L/ProblematicSites_SARS-CoV2

branch            master     -> FETCH_HEAD
Already up to date.
Entering 'covizu/data/pango-designation'
From https://github.com/cov-lineages/pango-designation
branch            master     -> FETCH_HEAD
Already up to date.
Traceback (most recent call last):
File "batch.py", line 144, in
cb.callback("No input specified, downloading data from GISAID feed...")
File "/home/arsen/Documents/covizu/covizu/utils/progress_utils.py", line 32, in callback
self.last_msg_length = sys.stdout.write(
UnicodeEncodeError: 'ascii' codec can't encode character '\U0001f3c4' in position 0: ordinal not in range(128)

Will be gareful for any suggestion.
Best regards,
Arsen

Dear Art Poon,
I tried to follow your advice and run CoVizu locally. I have GISAID username and password, so I tried to use batch.py script, but I got following error:
Entering 'covizu/data/ProblematicSites_SARS-CoV2'
From https://github.com/W-L/ProblematicSites_SARS-CoV2
branch master -> FETCH_HEAD
Already up to date.
Entering 'covizu/data/pango-designation'
From https://github.com/cov-lineages/pango-designation
branch master -> FETCH_HEAD
Already up to date.
Traceback (most recent call last):
File "batch.py", line 144, in
cb.callback("No input specified, downloading data from GISAID feed...")
File "/home/arsen/Documents/covizu/covizu/utils/progress_utils.py", line 32, in callback
self.last_msg_length = sys.stdout.write(
UnicodeEncodeError: 'ascii' codec can't encode character '\U0001f3c4' in position 0: ordinal not in range(128)

Will be gareful for any suggestion.
Best regards,
Arsen

Hi Arsen, you need to use the opendata branch as I tried to indicate in my earlier post:
https://github.com/PoonLab/covizu/tree/opendata
The master branch requires that you have user credentials to a restricted-access GISAID data feed.  In contrast, the opendata feed is designed to take any FASTA and metadata input files, including those distributed by the Nextstrain team.

Hi,
Thanks, but actually I have GISAID credentials and supplied them to
batch.py with --user and --password options.
Best regards,
Arsen
On Fri, Dec 31, 2021, 4:09 AM Art Poon @.***> wrote:

Hi Arsen, you need to use the opendata branch as I tried to indicate in
my earlier post:
https://github.com/PoonLab/covizu/tree/opendata
The master branch requires that you have user credentials to a
restricted-access GISAID data feed. In contrast, the opendata feed is
designed to take any FASTA and metadata input files, including those
distributed by the Nextstrain team.
—
Reply to this email directly, view it on GitHub
https://github.com/PoonLab/covizu/issues/377#issuecomment-1003218478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2YQGUZSHCOPMJJP4GLFSLUTTYEVANCNFSM5K5VOKJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Hi Arsen, I'm quite certain your credentials will not be able to access this feed, sorry.

Dear Art Poon,
I regularly submit Armenian sequences to GISAID using my credentials. I was
also able to download "clade and variants" json file from GISAID in tar.xz
format.
I'll l try to run opendata version of CoVizu.
Best  regards,
Arsen
On Fri, Dec 31, 2021 at 11:04 PM Art Poon @.***> wrote:

Hi Arsen, I'm quite certain your credentials will not be able to access
this feed, sorry.
—
Reply to this email directly, view it on GitHub
https://github.com/PoonLab/covizu/issues/377#issuecomment-1003437039,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2YQGXHCNL5VQDIYGMZY73UTX5FTANCNFSM5K5VOKJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Sorry I should have clarified.  CoVizu is provisioned by GISAID with a specific data feed that you would have to set a URL for via an environmental variable, and we do not distribute that URL nor the username and password access credentials, as per our agreement with GISAID.  You may be able to run the master branch using your set of JSON files but I have no experience with that data format.  Hence, your best bet is probably to use the converter script in the opendata branch to parse your JSON data files.  Please let us know if you run into any issues.


Publish POM-only artifacts for Jupyter purposes

Now you list all the needed artifacts right in the integration. It is convenient, but not efficient enough. It's better to publish artifacts for each spark/scala variation and use only a single dependency in the integration. It will significantly speed up the resolution process (3-6 times). I will improve the resolution of multiple dependencies on our side too.

Hmm, that would result in another 20 packages on maven central called org.jetbrains.kotlinx.spark.jupyter-dependencies_x.x.x_2.x. I don't think Sonatype can handle that XD The current 40+ are already an issue


Arrow keys not supported for moving cursor in dialoguer input

Describe the bug
In the commit command, when writing text in any of the text inputs, navigation with arrow keys is not supported (escape sequences are printed instead).
To Reproduce
Steps to reproduce the behavior:

convco commit
choose type (enter)
In "scope", write "foo" and then the left arrow key
Result: foo^[[D

Expected behavior
The cursor is moved left
System (please complete the following information):

OS: Ubuntu
Version: 23.10

Additional context
This crate should use interact_text instead of interact for dialoguer inputs

Thank you for pointing to the solution

Thanks for the quick fix!


feat(scope): git commit scope resolution

For those working with git work-tree, it should be possible to make tags more granular when performing scope resolution. Specifically, git commits should be suffixed to the scope to further specify a tag scope.
Add git scope resolution

Expose resolve_scope as a module function
Add resolve_scope_in_parts function to return both file_path and git commit of a scope
Refactor resolve_scope function to use resolve_scope_in_parts
Add git configuration option

Update README with relevant details

Update configuration section
Update Tag Scopes section

It would be nice if the scope would resolve as such .git > lsp > directory, not sure if you have already though of this :)

Interesting idea! This should be possible (albeit not built-in) by passing in a function to scope as part of the setup with something like:
require("grapple").setup({
    scope = function()
        -- Attempt to use a git directory as the project scope
        local root_files = vim.fs.find(".git", { upward = true })
        if #root_files > 0 then
            return vim.fs.dirname(root_files[1])
        end

        -- Fallback to "lsp", which will fallback to "directory" if not found
        return require("grapple.scope").resolve("lsp")
    end
})

Awesome, though looks like something isn't running.

Hm. How did you hit this error? It looks like might have been running :GrappleTag? Was there a specific set of arguments you used to hit this error?

@cbochs nope just used ":GrappleTag", am i doing something wrong?
Thought it was supposed to by default tag the current buffer.

That's correct. Does this happen when you call :GrappleTag for any file? If possible, what is the output of :lua =vim.api.nvim_buf_get_name(0) when you have that buffer open?

@cbochs seems to return back the path of the current buffer X:\\Projects\CPP\ShaderVis\main.cpp

GrapplePopup:

GrappleToggle:

That's kind of what I thought this would be. Paths have only been naively implemented in grapple.nvim, always assuming unix-style (/). This assumption breaks down for Windows. I've created https://github.com/cbochs/grapple.nvim/issues/31 to follow-up with this. Sorry for the inconvenience!

Haha all good, guess ill be waiting for the update ;D

Back on-topic with this issue:
Idea: to support finer grained scopes like git branches, commits, or other VCS systems, use the concept of a ScopeSuffix where a scope can now appear as one of the following:

Without suffix: {scope_path}
With suffix: {scope_path}#{suffix}

Advantages:

Easily parsed into a scope_path and suffix
Extendible, supports adding a config option like config.suffix for customizing the type of suffix used.

I like it, basically being able to chain your fall backs.

This is slightly different than fallback chaining. More along the lines of supplementing a project scope so users can have tags that are associated with something like specific git branch (i.e. /my/git/project#main and /mygit/project#dev).
For now, fallback chaining should probably be left to a custom function. However, I think some API should be provided to more easily what the project (root) directory is. Maybe along the lines of 6e3cd09ccd27088fc2f6e5b3edabcf909c2ae5ae

This has been implemented as git_branch using an async scope resolver (see: https://github.com/cbochs/grapple.nvim#project-scopes).


Fix description of  again

Ooops
Here is some real data:
idle_time: 1890963
queue_time: 28
query_time: 37635616
decode_time: 1016
total_time: 37636661
So (28 + 37635616 + 1016) = 37636660 which looks like it is a rounding error off from the reported total_time of 37636661

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Request for feature: manual nudging of autonomous flight modes

3DR solo allows nudging of x-y position during landing.  This is handy when you want to hit the launch pad when you are in rough terrain.  Why use auto-landing then?  Because it is usually better than manual landing on the vertical control, same reason I use ALT-HOLD mode most of the time.
But what if we generalized this and allowed minor nudging of position during all autonomous modes.  One time I crashed a 3dr solo into a big dead tree because the mission waypoint went to close, I would have loved to be able to nudge it while it was on mission to help it dodge the tree.   I'm sure the same could be said for raising altitude on a mission that is about to clip the tip of a tall tree.  Or manually lower the altitude when going under a tree canopy.
I realize this is a hard problem and we may need to implement some more advanced shared autonomy research where stick input is used to infer the goal user has so we can safely modify the autonomous mission with new goal in mind, rather than having the sticks fight the autonomous mission flight control directly.  Could be fun...

We will add this for landing first and then think about how solving the shared autonomy should eventually work.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Resolve syncing conflicts from live-sync-work to live

Pull request opened by OPS to resolve syncing conflicts from live-sync-work to live.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\xjws-s, target branch: live, target branch commit: 9207abd137baea5f32ac748a2660cf4aafc742ad, source branch: live-sync-work, source branch commit: .

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

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\gfyu-s, target branch: live, target branch commit: 9207abd137baea5f32ac748a2660cf4aafc742ad, source branch: live-sync-work, source branch commit: .

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


tests instantiating components

@mcflugen, @mdpiper, @Elchin
Here's the copy of topoflow I'm working on. All of the components can be individually instantiated (without emeli), and most go through IRF without too much trouble and requiring very few outside variables.
The file component_testing/components.py does it for every component in topoflow/components except HIS_*.py. If any dummy variables were defined, they appear right before the call that needed them (so if they appear after .initialize() but before .update(), they were first needed by update). I made small modifications to a couple of files, and those are mentioned in the script.
Neither of the erode components got through the whole process. It appeared to be due to size differences between arrays (in different functions for erode_d8_local and _global), and it might be a result of missing or dummy variables. Both d8_local and d8_global ran, so the problem is probably with erode itself.
Thoughts?

@mcflugen, @Elchin
This is excellent; thank you, @mperignon! The tests you created in components.py were more enlightening than anything I'd read in the docs.
I have a few thoughts:

Should TopoFlow, and the tests in components.py, be added to Travis CI?
We're going to need Scott's input on things that don't work.
I'm now fairly certain that TopoFlow will not be very user-friendly in WMT, since every component allows some combination of custom (Rivertools?) file uploads for their inputs.

@mcflugen, @Elchin
@mdpiper, there is a set of tests included with TopoFlow with varying degrees of completeness. None of them (as far as I can tell) test the coupling of components, but they do something similar to what I did. Neither those nor mine check the results - they just check that nothing explodes. So I don't think that this set of tests should be added to Travis CI just yet, but I do think a new set of tests should.
I'm going to try to run the non-working components through emeli, as Scott intended, and see if they work. It really might just be that they are not getting the input files quite like they want them.
I think we need to make a decision about how much to modify TopoFlow to make it usable with WMT. It's a black box, even when using the components individually, and much of that is due to the use of Rivertools-specific file formats for inputs and outputs. There should be an easy way to just grab the numpy arrays that are being passed around, but the only place I can see to intercept them is when calling topoflow_driver.update(), which is the method that creates a gazillion files.
If we could bypass the normal inputs and outputs and just give it numpy arrays, then it would not be nearly as hard to make it user-friendly(er) in WMT.
ANUGA has really flexible functions for setting quantity values that take all kinds of data and redirect it down the appropriate path to turn them into one common data type. They wouldn't completely solve the problem, but they could allow each input in WMT to be a dropdown menu and a text field. Line 701, for example: https://github.com/GeoscienceAustralia/anuga_core/blob/master/anuga/abstract_2d_finite_volumes/quantity.py

Another issue: the BMI initialize method should allow no arguments, but (as @mperignon has shown) the TopoFlow components require a .cfg file. At least there are several .cfg files in the topoflow/examples subpackage to use as dummies for testing.


Feature/security profile

This pull request might be redundant! It appears to be fully contained in #116
@sebbader


feat: Adapt Badge to respect Spark specs (#342)

📋 Changes description

Update Badge component to respect Spark specs.
Update BadgedBox component to respect Spark specs.

📸 Screenshots
Generated by paparazzi in this PR files
🗒 Other info
BadgedBox is still an @ExperimentalSparkApi as the position of the badge regarding the anchor can change
accessibility still needs to be handled
close #342

Seems like we need to make <string name="spark_rating_with_comments_a11y">Note de %1$.1f pour %2$d avis</string> a plurals


-Also Fixed issue related to DragNDropSimpleadapter background data list...

-Fixed issue ( notifyDataSetChanged was not working when background data attached with DragNDropSimpleadapter was changed). This was causing the app to crash due to index out of bound exception.

Updated Support Library Version to 21.0.3
Updated Android Target Version to 5.0.1

If there is any problems understanding what was fixed then i assume you try to run the DragNDropSimpleAdapter  with below class. You will notice that it will crash.
public class DragListActivity extends Activity {
	private DragNDropListView lv_list;
	private DragNDropSimpleAdapter mAdapter;
	private ArrayList<Map<String, Object>> items;

	@Override
	protected void onCreate(Bundle savedInstanceState) {
		setContentView(R.layout.activity_draglist);
		super.onCreate(savedInstanceState);
		initUi();
		fillStudentList();
	}

	private void initUi() {
		items = new ArrayList<>();
		lv_list = (DragNDropListView) findViewById(R.id.lv_dragList);
		mAdapter = new DragNDropSimpleAdapter(this, items, R.layout.listitem_drag_n_drop, new String[] { "name" },
				new int[] { R.id.text }, R.id.handler);
		lv_list.setDragNDropAdapter(mAdapter);

	}

	private void fillStudentList() {
		for (int i = 0; i < 20; i++) {
			HashMap<String, Object> item = new HashMap<String, Object>();
			item.put("name", "Name " + i);
			item.put("_id", "id " + i);

			items.add(item);
		}
		mAdapter.notifyDataSetChanged();

	}
}

@fidanov @gipi @vlyutskanov  could you guys take a look at it and merge it ?

Thanks!

@fidanov  ur welcome. Glad to help :)


Upgrade social-auth-app-django.

Upgrade from 3.1.0 to 4.0.0 to fix compatibility issue:
https://github.com/python-social-auth/social-app-django/issues/284

This was upgraded to 5.2.0 in the upgrade to Django 4.2


Compile type error message do not show absolute type path leading to confusion

In this case the compile error message might be confusing (it confused me a while):
https://play.crystal-lang.org/#/r/7br4
Error in line 22: no overload matches 'Tool::A#value=' with type B
Overloads are:
 - Tool::A#value=(a : A)

The problem here is it makes me wonder if there was a problem with the inheritance. With this message, I would have understood more clearly:
Error in line 22: no overload matches 'Tool::A#value=' with type B
Overloads are:
 - Tool::A#value=(a : Tool::A)

Yes, this is a duplicate of another issue I can't find right now...


Replace causes instance names to break

https://github.com/sqlcollaborative/dbatools/blob/b68cfdade04ec6d3fec44fec9a9999fcef5081b0/functions/New-DbaPublishProfile.ps1#L128
Tesing on an instance with dashes in name and whne passing in connection string 'SERVER=BB-SQL-123-01\INAMEIntegrated Security=True;Database=master' the replace on this line causes following error -
"WARNING: [New-DbaPublishProfile][10:58:07] Failure | Cannot convert value "BB\SQL\123\01\INAME" to type "Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter". Error: "Failed to parse instance name: BB\SQL\123\01\INAME""
When removing replace am able to create publish profile.

ohh snap, lemme fix


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/pkg e8973c6...7d1b0f1:
  > 7d1b0f1 Add ability to filter objects on injection controller promotion (# 2180)
  > 459d317 Add CheckEndpointState method to SpoofingClient (# 2166)
bumping knative.dev/eventing 4a679a4...0af15fd:
  > 0af15fd Move knative.dev/pkg/source.StatsReporter to eventing/pkg/metrics/source.StatsReporting  - 1/n (# 5587)
  > 144a5b8 tracing fix for APIServerSource and PingSource (# 5567)
  > c86690c upgrade to latest dependencies (# 5588)
bumping knative.dev/reconciler-test 2b7893c...ebe91f9:
  > ebe91f9 Sender now support sub-second period and delay (# 202)
  > 99f4470 upgrade to latest dependencies (# 227)

/retest
/lgtm
/approve

/retest


Invalid HTTP Status

Websocketpp is failing with Invalid HTTP Status...

Did you resolve this issue? I am getting the same error for some days now...
[2017-10-04 18:46:23] [connect] Successful connection [2017-10-04 18:46:23] [error] Server handshake response error: websocketpp.processor:20 (Invalid HTTP status.) Connection failed. Reconnect for attempt:4

Yes I did, I had to make some changes to allow for https connections.

I ended up resolving this issue by using a different underlying service for my server socketio implementation:
Instead of using gevent which relies on long-polling, I now use eventlet which additionally supports websocket transport and allows for communication with this client out of the box.

@jammerxd care to share your changes?

Sure, give me a day or 2.

@aolivier I uploaded my mods to this repo: https://github.com/jammerxd/secure-socket.io-client-cpp

Soooo is this still open?  Currently seeing this same error in my application and cant seem to get past it. Relevant stack trace:
``****

Me as well, looks like it is still an issue:
Jun 13 16:45:24 medrc-recorder-1 recorder[19546]: [2018-06-13 16:45:24] [error] Server handshake response error: websocketpp.processor:20 (Invalid HTTP status.)
Jun 13 16:45:24 medrc-recorder-1 recorder[19546]: [2018-06-13 16:45:24] [application] on_fail: WebSocket Connection failed, stopping telemetry!
Jun 13 16:45:24 medrc-recorder-1 recorder[19546]: [2018-06-13 16:45:24] [application] on_fail: Will try to reconnect in:  19

Did any one got how to resolve this issue?

Maybe just try the tls branch? I'll check it in a day.

Any news on the issue?

Any updates ?

Hi guys , Any updates on this ?

I thought I found the issue was because I was trying to go with wss;// instead of https:// and having the web socket server be behind nginx and having nginx upgrade the connection...I can't remember if that was the issue or not.

for me issue was the tls version was wrong as this library is not upto date + there was no way to add path . I change the codebase and it worked . cheers

@jammerxd I also meet this issue.when I connect to a wss server without nginx,it works;but when I connect a wss server with nginx,it doesn't work! why?

@jammerxd I also meet this issue.when I connect to a wss server without nginx,it works;but when I connect a wss server with nginx,it doesn't work! why?

any updates about this?

I encountered the same problem and resolved it by appending "/" to the resource path:

https://somehost/somepath -> https://somehost/somepath/

Using vcpkg, just install openssl-windows, then compile the project with tls version sioclient.lib.
If you use visual studio, set the properties => vcpkg => Use Static Libraries to yes. libcrypto.dll and libssl.dll will be built when the project is compiled.
But now I am wondering why we set the property to no, tls does not work properly.


update to handle new plane name structure

latest version of the pipeline stopped using LIMS IDs for plane names
also test on single-plane data

this is fixed already


BUG 2125148: csi: remove findCSIChange from predicate

Description of your changes:
findCSIChange will work only for single line values/configuration in the configmap; If the value is multiline, the regex will not
be able to indentify the change because of this one no configurations will be applied to the csi driver. Removing this check so that if there is any update on the configmap, we will reconcile the csi driver.
Note: This might look heavy, but updating config map is not a frequent event.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>(cherry picked from commit 5b843a17a1704f771ed3ab3a4e19328a555c7029)
Which issue is resolved by this Pull Request:
Resolves #
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide).
[ ] Skip Tests for Docs: If this is only a documentation change, add the label skip-ci on the PR.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Pending release notes updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

/assign @travisn

/approve
/lgtm

@travisn This is not merged yet, looks like linter problem in 4.10 (not related to this PR)


add sbt-updates plugin

What are your thoughts on using scala-steward instead? Its a fully configurable bot that automatically creates PR's with dependency updates that is used throughout Scala OS ecosystem (scala/scala center projects themselves even use it).

the PR is based on https://github.com/apache/incubator-pekko/issues/56#issuecomment-1329221043 and the following comment with the version upgrades
it would probably be very noisy to have our PR queue filled up by scala steward when there are zero of those PRs that will be accepted right now
with just having the plugin, at least we can check manually to see if there are new updates

Was editing the post while you replied, on my point here

There is also an argument that this should be a global sbt plugin (which you would place in ~/.sbt/1.0/plugins.sbt for example) with the same reasoning as to having global git settings.

How do you feel about adding a section in CONTRIBUTING.md on how to add such a global sbt plugin instead? I have also done this in the past with sbt-dependency and similar plugins.

sure - I guess this is the sort of plugin that works well as a global one


fix(transformer/async-generator-functions): only transform object method in exit_function

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#7201
#7200  👈
#7199
#7198
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite

Merge activity

Nov 7, 9:35 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Replicated flask and bottle folders for webAppWithTests

Just double checking. These are from the latest master right?

@ShreyasRmsft  Yes. These are copies from latest master


Enabling "hide reposts" on a channel, makes settings permanently expanded(Can shrink in current page, but it's expanded again on next channel entry)

Go to some channel page
Enable "hide reposts"
Shrink settings
Go to some channel (same or different)
Settings are expanded again

"Enabling any filter + fresh click into the page (not using Back/Forward)" would automatically expand it.
I believe the intention was to let the user know there is an active filter running ... the red-highlight of the button might not be obvious.
Can remove if this behavior is no longer wanted.

Yea, I recall that now. We do show the red button when there are filters - maybe that's enough? We could also add a warning (vs taking up a bunch of space).

The filter section no longer expands by default. Probably not ideal either, but much less annoying in most scenarios for most users. The button is still purple when a filter is active. PR: #1994


making various messages during setup more verbose

Partial Fix #388 .

@naresh-kumar-babu - I have to apologize, because I realize now that I don't remember - and can't figure out - which parts, if any, of the original patch (#371) have to do with making setup more verbose. A search on "verbose" and "-v" does not return anything meaningful. Maybe I misread the code before? I don't know. So perhaps this whole task should just be abandoned.
Now I'm curious, though: does adding a "-v" flag to the run-all.sh call have any impact? That script doesn't seem to have such a flag, as far as I can tell.

Okay, having looked more at the code, now I think I remember what this was about: it was just the addition of a few more "echo" calls, and making some of them longer - like changing "Starting job runner..." to "Starting job runner (in 10 seconds)...". Not really that important, but it is something.


[Bug]: Icinga kubernetes pod goes into CrashLoopBackOff at installation

Affected Chart
icinga-stack
Which version of the app contains the bug?
0.3.0
Please describe your problem
Hi, I can not install the chart, the icinga-kubernetes pod goes into a CrashLoopBackOff. In the logs I can see this error:
I0917 10:43:35.582852       1 database.go:286] "Connecting to database" logger="database"
F0917 10:43:36.227691       1 main.go:313] can't retry: can't perform "INSERT INTO service (cluster_ips, external_ips, ip_family_policy, uid, created, cluster_ip, session_affinity, uuid, name, type, publish_not_ready_addresses, health_check_node_port, load_balancer_class, internal_traffic_policy, external_traffic_policy, ip_families, resource_version, external_name, yaml, namespace, allocate_load_balancer_node_ports) VALUES (:cluster_ips, :external_ips, :ip_family_policy, :uid, :created, :cluster_ip, :session_affinity, :uuid, :name, :type, :publish_not_ready_addresses, :health_check_node_port, :load_balancer_class, :internal_traffic_policy, :external_traffic_policy, :ip_families, :resource_version, :external_name, :yaml, :namespace, :allocate_load_balancer_node_ports) ON DUPLICATE KEY UPDATE cluster_ips = VALUES(cluster_ips), external_ips = VALUES(external_ips), ip_family_policy = VALUES(ip_family_policy), uid = VALUES(uid), created = VALUES(created), cluster_ip = VALUES(cluster_ip), session_affinity = VALUES(session_affinity), uuid = VALUES(uuid), name = VALUES(name), type = VALUES(type), publish_not_ready_addresses = VALUES(publish_not_ready_addresses), health_check_node_port = VALUES(health_check_node_port), load_balancer_class = VALUES(load_balancer_class), internal_traffic_policy = VALUES(internal_traffic_policy), external_traffic_policy = VALUES(external_traffic_policy), ip_families = VALUES(ip_families), resource_version = VALUES(resource_version), external_name = VALUES(external_name), yaml = VALUES(yaml), namespace = VALUES(namespace), allocate_load_balancer_node_ports = VALUES(allocate_load_balancer_node_ports)": Error 1265 (01000): Data truncated for column 'type' at row 79

Hi @bosseedi,
Thanks for the report. There was a typo in the schema introduced just recently which has been fixed. Please pull the icinga-kubernetes image and try again. You have to drop and recreate the kubernetes database beforehand though. Or just recreate the whole deployment.
Best regards,
Eric

thanks that fixed the issue


Cluster options in Edit as a Form are not all configurable in current Edit as YAML option

Version: master 4/9
Cluster Options is switchable between Edit as YAML and Edit as a Form. Problem is that it switches as it can all be configured in the Edit as YAML but some of the options on the screen are Rancher only, i.e. Project Network Isolation/Docker Root Directory. The YAML is posted as rancherKubernetesEngineConfig, while those options live in the root. The either need to be split out so make sure it's clear its Cluster vs Rancher or we need to make it configurable at the root when choosing Edit as YAML.

Version - master 3/11
Verified fixed


Migrate to ghcr for 1.3

@ymorimo Just in case, double check please!

@ymorimo Just in case, double check please!


does not contain a method named 'AcquireToken'

I am successfully connected to my MSOnline using Connect-MsolService and my tenant using connect-AzureAD but I still get only the following error and NO output from the script.
Method invocation failed because
[Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationContext] does
not contain a method named 'AcquireToken'.

Import-Module Azure also works with no errors. What am I missing, how do I get this to give me an access token? I am using a global admin account and the same query I am trying to run in the script works just fine online in the browser at MS Graph Explorer beta.

+1 here - same issue.

This script uses Active Directory Authentication Language (ADAL) libraries for authentication. ADAL must be installed via Azure PowerShell or the Azure SDK for authentication to work.
Can you make sure that you have one the ADAL libraries from one of the above installs present and then retry?  This is a separate install in some PowerShell install versions.

@TspringMSFT thanks. In my case it started working after I switched to using 'AzureAD' module. I had stumbled across another article that mentioned that AzureAD is more up to date and can deal with MFA etc ... and voila it worked for me too. Might it be an idea to swap out the use of the 'older' module 'Azure' in the script and put in 'AzureAD' instead?


SINGA-57 Improve Distributed Hogwild

The Trainer::Run and Server::Run was messy due to the monitoring of the network bandwidth for implementing the distributed hogwild. This pull request re-implement this framework removing the bandwidth monitoring.
The ClusterProto::sync_freq field controls the frequency of sync between
server groups.
After updating of Param (slice), the server checks the num of updates
since last sync. It also checks the num of pending syncs (i.e., requests
haven't received reponses) to avoid sending too many msgs to stopped
servers (the msgs would be occupy the memory of the sending buffer)
The server respones to every sync requests with the latest Param values.
Note: current does not support (there is bug) multiple worker groups in
one process for the distributed hogwild framework. We recommend to
replace this cluster topology with in-memory hogwild, i.e., launching
one worker group with multiple workers and one server group.

an example cluster topology of distributed hogwild is
nworker_groups: 2
nserver_groups: 2

Each server group serves one worker group. One worker group and one server group will be created in one processes (two processes will be launched in total).


404 when using query string

I am using batch_api with a Grape API in a Rails app. I found that all batch requests processed normally except for those using query string parameters. For example, this request would work:
{
  "ops": [
    {"method": "get", "url": "/api/v1/model"}
  ],
  "sequential": true
}

The response:
{
  "results": [
    {
      "body": "[{:one=>1}]",
      "headers": {
        "Content-Type": "application/json"
      },
      "status": 200
    }
  ]
}

The same request with a query string fails:
{
  "ops": [
    {"method": "get", "url": "/api/v1/model?per_page=5"}
  ],
  "sequential": true
}

Returns:
{
  "results": [
    {
      "body": "Not Found",
      "headers": {
        "X-Cascade": "pass"
      },
      "status": 404
    }
  ]
}

This was true whether the query string had values or not, i.e., /api/v1/model? also failed without any parameters.
I inspected the Rack env variable in a batch request with a query string. env['PATH_INFO'] = '/api/v1/model?per_page=5' is the value, and this value does not work. If there is a query string appended to PATH_INFO then the call will fail. When I reset PATH_INFO to remove the query string the batch call completed successfully.
The other difference I saw was that rack.request.query_hash was empty, but this didn't appear to impact the request.
This looks like it can be fixed by setting ORIGINAL_FULLPATH and PATH_INFO separately in https://github.com/arsduo/batch_api/blob/master/lib/batch_api/operation/rack.rb#L65.
@env["ORIGINAL_FULLPATH"] = @url
@env["PATH_INFO"] = @url.split('?').first

@arsduo Do you know if there are any unforeseen consequences from this change? Would you accept a PR for this issue?

I was wrong, I had to get rack.request.query_hash set as well. I have patched in config/initializers/api_batch.rb for now to override the method:
require 'batch_api/response'

module BatchApi
  module Operation
    class Rack
      def process_env
        path, qs = @url.split("?")

        # Headers
        headrs = (@headers || {}).inject({}) do |heads, (k, v)|
          heads.tap {|h| h["HTTP_" + k.gsub(/\-/, "_").upcase] = v}
        end
        # preserve original headers unless explicitly overridden
        @env.merge!(headrs)

        # method
        @env["REQUEST_METHOD"] = @method.upcase

        # path and query string
        if @env["REQUEST_URI"]
          # not all servers provide REQUEST_URI -- Pow, for instance, doesn't
          @env["REQUEST_URI"] = @env["REQUEST_URI"].gsub(/#{BatchApi.config.endpoint}.*/, @url)
        end
        @env["REQUEST_PATH"] = @env["PATH_INFO"] = path
        @env["ORIGINAL_FULLPATH"] = @url

        @env["rack.request.query_string"] = qs
        @env["QUERY_STRING"] = qs

        # parameters
        @env["rack.request.form_hash"] = @params
        @env["rack.request.query_hash"] = @method == "get" ? @params : nil
        @env["rack.request.query_hash"] = ::Rack::Utils.parse_nested_query(qs)
        binding.pry
      end
    end
  end
end


indexing issues when deletion is not fast enough on the ES side

Indexing a draft after a previously publish one has been deleted (its draft, not its record) from the ES index, sometimes fails due to the ES collector not passing fast enough (default time 1 minute).
As discussed IRL:

The version of the draft should be kept in DB. Even between publish and new draft, the newly created draft will continue its revision from where it was left before.
Both content in DB and content in ES will be wiped (just the JSON) so it is not searchable.

Fixed with indexing by obj id and version id


Update and Enhance "Prototyping with Figma" Guide on Altinn Studio Documentation

Description
Last update
Altinn Studio Komponenter
V 2.1 - Release 21.05.24
The "Prototyping with Figma" guide on the Altinn Studio documentation site (https://docs.altinn.studio/altinn-studio/guides/design/prototype/) serves as an essential resource for developers and designers who utilize Altinn Studio for creating prototypes. To ensure this guide remains up-to-date and maximally beneficial, we are proposing enhancements that reflect recent updates to our Figma components.
The Figma file for Altinn Studio components has been updated. This update includes new components and patterns that can significantly aid our users in creating more accurate and effective prototypes. The updated Figma file is available here: Altinn Studio Components in Figma
Update Guide Content:* Revise the guide to include references and examples using the latest components from the updated Figma file. This ensures that users have the most current information and can leverage the full capabilities of our design system.
Add New Sections: Introduce new sections or subsections that specifically address how to use the newly added components within the Figma file. Each section should include practical examples and best practices for integration into prototypes.
Improve Navigation and Usability: Enhance Altinn.docs  Delete duplicates of components on the documentation.
Conclusion
By updating the "Prototyping with Figma" guide to reflect the latest changes and enhancements in our Figma components, we can provide a more valuable resource to our community. These improvements aim to foster a more intuitive and efficient design process, enabling creators to build more effective and user-friendly prototypes. We invite the community's feedback on these proposals to ensure the guide meets our users' evolving needs.

This issue draft is structured to clearly identify the need for updates based on the Figma file changes, outline specific improvements, and invite community engagement for further enhancement.
### My tasks
- [x] Update examples and prototypekit and guide
- [x] Delete duplicates of components and clean up the docs
- [x] Update mobile components

### Update new components
- [ ] Datepicker
- [ ] Sub-form
- [ ] Summary 2.0
- [ ] Navigation
- [ ] Sign - delegate task
- [ ] PDF
- [ ] Tabs
- [ ] Card

@olavflar This issue is marked as "Done" in your project, can it be closed? If not, it should be moved to the docs repo.

Do you have a link to the docs repo?

@olavflar This issue is marked as "Done" in your project, can it be closed? If not, it should be moved to the docs repo.

Do you have a link to the docs repo?

@olavflar There is no board for docs as far as I know, we add issues relevant to us to our team boards.


v5 doesn't include bower.json export of release/angular-stripe.js

Hello, trying to upgrade to v5, but release/angular-stripe.js isn't in the bower dependency list. It looks like it isn't set up as a bower package any more?
To replicate:
bower init
npm i bower-files

# v5
bower install angular-stripe@~5
node -e "console.log(require('bower-files')().relative(process.cwd()).ext(true).files)"
# result {}

# v4
bower install angular-stripe@~4
node -e "console.log(require('bower-files')().relative(process.cwd()).ext(true).files)"
# result { js:
#   [ 'bower_components/angular/angular.js',
#    'bower_components/angular-stripe/release/angular-stripe.js' ] }

Happy to do this myself if necessary, including this file manually at the moment.

Yup I no longer support bower in any of the packages I maintain at the moment. Please do handle it on your project level as you see fit.


Choose API Server Framework

I want to select a server framework for the graphql api operational component of the app. I want this to primarily be easy to stand up, and reflect modern standards of quality and features for such frameworks.
Acceptance Criteria

Select a server framework, such as Next.js, Node.js, etc.
This should be generatable thru our monorepo framework from #1
This framework should easily support Apollo Server, as that will be our GraphQL tech of choice.
This framework can and should include a learning curve of some kind, I shouldn't select one that is familiar.

Anti-goals

"Full-service" frameworks, where all aspects of the app are handled for us, such as cross-cutting concerns (security, logging), database connections, modeling, and deployments. I want to select my own frameworks for these components and learn them, rather than be bound to the walled-garden of a full-service framework.
Cross-platform building. I only intend to deal with a simple graphql web api for now, so I have no need to have a server framework that also distributes code for mobile, native, etc.

The following is an academic note. Our server framework only needs to serve GraphQL requests, not actual page content.

Just a note on the difference between Server-side Rendering and Client-side Rendering.
Static Rendering
With static rendering, your pages are generated at build time and then served as static HTML files. This method provides speedy response times because the pages don’t need to be rendered for each request. SEO also works as expected for statically rendered pages because the content is readily available for crawlers. However, statically rendered content can only be updated by deploying a new version of your app. This means that relative to other methods, your content is more likely to become stale between deploys.
Server-side Rendering
With server-side rendering, pages are generated dynamically for each incoming request. This enables content to be updated between deploys (unlike static rendering), and SEO works as expected. However, rendering on every request does add processing time that can noticeably increase response latency.

As a note, the Next.js framework is really catered to allowing for server-side rendering of pages, however we're just using this server as a GraphQL API, so that framework is less desirable, as it's probably too complicated for our purposes.

Nest.js is actually built on top of Express, but can also optionally be run on top of Fastify

This framework is going to have to support at least the following:

Database connections to a Postgres DB, incl. modeling, migrations, etc.
A GraphQL resolver layer and endpoint
A logical layer of some kind
Possibly a separate management interface for scheduled/async jobs?

It seems the recommended way to add a DB to Nest.js is the enterprise-y "ORM" architectural style, which isn't my favorite. It has always seemed really verbose to me, in an unnecessary way.

I'm also really not a fan of the very OOP style of Nest.js, which seems to be prevalent in most of the examples and tutorials I've seen.
i.e. insisting on creating classes with constructors, rather than functions and currying ala the Express server style.

A clear way to control middleware and use of cascading middleware is really desirable.

Koa.js is appealing for it's simplicity and solution to callback hell, however the con of not being compatible with normal express middleware is not ideal.

Honestly, I'm gonna just go with vanilla Express.js and build on that. Most frameworks I've seen are too much or too laterally different.


Use Sidekiq::Process (suite)

This PR is related to #12
I've :

fixed a missing require
fixed the specs
improved global syntax for rubocop

Since the support for Sidekiq <= 4 has been dropped, we should bump a new version. Is increasing the minor number good enough for you ?

 (2.3) [OS] Faire passer la PR sidekiq-worker-killer#12


Python 3 support

That is a lot of work! It would be nice for the package to support both py2 and py3, but py3-only is fine. It looks great! Thank you.


Google json output is not actually json

In the output produced by -e for Google, the .json is not actually JSON.

Fixed in commit 924cdab.


Nsncd: 23.05 regression compared to 22.11

Describe the bug
In 23.05 nsncd is enabled by default.
However we have found this seems to have changed in a breaking manner a behavior in one of our NixOS machines (CI runner).
Steps To Reproduce
Steps to reproduce the behavior:

Have this NixOS configuration for a nixos-22.11 version

{
  security.sudo.enable = true;
  services.openssh.passwordAuthentication = false;
  security.sudo.wheelNeedsPassword = false;
}

SSH into the machine
You can run sudo commands, e.g. sudo ls or sudo su
Have the same NixOS configuration but for a nixos-unstable version
SSH into the machine
:boom: You cannot sudo:

sudo: PAM account management error: User not known to the underlying authentication module
sudo: a password is required

Add services.nscd.enableNsncd = false; to your NixOS configuration
SSH into the machine
sudo commands work

Expected behavior
Either the same configuration should work in nixos-unstable/nixos-23.05 (once it exists), or this breaking change / a migration guide should be added in https://nixos.org/manual/nixos/unstable/release-notes.html#sec-release-23.05-incompatibilities
Additional context
I don't know if any of this is relevant, but just in case:

the machine is a GCP VM instance
the deployment is done via Terraform
we SSH using https://console.cloud.google.com/ which drops us in a browser shell
the user with which GCP SSHs us into the machine is not present in /etc/passwd nor in users.users in the NixOS configuration

Notify maintainers
As I don't really know what is the problem (documentation, code, other?) I am unsure who to ping :neutral_face:
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.95, NixOS, 23.05 (Stoat), 23.05pre-git`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.2`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Git revision of the nixos-22.11 version: 6a0d2701705c3cf6f42c15aa92b7885f1f8a477f
Git revision of the nixos-unstable version: 7f5639fa3b68054ca0b062866dc62b22c3f11505

CC @yorickvP

cc @flokli

@sir4ur0n hmmh, we do have a nixos/tests/sudo.nix which does succeed, and we also have nixos/tests/google-oslogin/default.nix which does succeed, testing ssh over sudo.
What is the user you ssh in as? Is oslogin enabled, or how does it work?

cc @NinjaTrappeur

I can't reproduce locally or in a VM test. Sounds like we have a weird interaction happening here.
@sir4ur0n: Could you dump the nsncd logs around the time you call sudo? If you can, dumping all the journald logs around the time you call sudo could also help.

cc @ConnorBaker , who inherited the workaround :D

We're also being bitten by this switch due to https://github.com/twosigma/nsncd/pull/49.

As written by @NinjaTrappeur, we still need some logs / socket dumps to understand what's going on. This is not visible outside Google Cloud.

Hi, I also got bitten by this. It works for 22.11 but not 23.05, and I can reproduce it consistently:

Create a NixOS 23.05 image with nixos-generators (flakes), have its input's nixpkgs point to nixpkgs/23.05, and upload it on GCP.
Create a VM with said image following the steps here https://nixos.wiki/wiki/Install_NixOS_on_GCE under the Create a VM instance section. I also added the enable-oslogin TRUE metadata part.
SSH into the VM once ready using the gcloud CLI
sudo -i produces the same error message as OP did

I ran dmesg after that, and it seems to be related with nsncd cause I saw a bunch of its segfaults which seems correlated to the number of times I ran sudo -i.
If you were to switch the first step to point to nixpkgs/22.11, I can sudo -i just fine:
[user@host:~]$ sudo -i

[root@host:~]#

If anyone could advise me what logs to post here, and exactly how to get them, I'd be happy to. :smile:

Could you check if https://github.com/NixOS/nixpkgs/pull/263634 fixes this issue as well?

i was following this guide using master branch and had this issue. checking out from 22.11 to build the image fixed it

Thanks for testing this! Closing the issue.

OS built from Image generated from current master(version is inferred to be 24.05) also causes the same error when running on GCP with oslogin=true as mentioned in https://nixos.wiki/wiki/Install_NixOS_on_GCE.

The steps to reproduce:
git clone git@github.com:NixOS/nixpkgs.git

cd nixpkgs

git checkout 4a6c1d765bd660f8379f961e641f5c9fccd312dc

Run the steps described in https://nixos.wiki/wiki/Install_NixOS_on_GCE inside Docker
because I'm on Mac OS M1, but I need linux/amd64 image.
cd  ..

docker run --rm -it --platform=linux/amd64 -v `pwd`/nixpkgs:/nixpkgs--workdir /nixpkgs nixpkgs/nix:latest bash

nix-shell -p 'google-cloud-sdk'

gcloud auth application-default login

export NIX_CONFIG=$'system-features = benchmark big-parallel nixos-test uid-range kvm\\nfilter-syscalls = false\\nexperimental-features = nix-command flakes'

Then, I created Google Storage bucket BUCKET_NAME.
BUCKET_NAME=<MY_BUCKET_NAME> nixpkgs/nixos/maintainers/scripts/gce/create-gce.sh

Then, copy the arfitacts from the container back to my host machine and upload the disk image tar.gz to GCS to create compute image from it.
Then, create Google Compute Engine from the image with metadata oslogin=TRUE.
After the instance launched, connect the instance via ssh.
 gcloud compute ssh --zone "<GCP ZONE>" "<compute engine name>" --project "<GCP project name>"

Now, I'm inside Compute Engine instance.
sudo -i

This results in the following error.
sudo: PAM account management error: User not known to the underlying authentication module
sudo: a password is required

The steps to reproduce:
git clone  git@github.com:NixOS/nixpkgs.git && cd nixpkgs

git checkout 4a6c1d765bd660f8379f961e641f5c9fccd312dc

Then I run the steps described in https://nixos.wiki/wiki/Install_NixOS_on_GCE inside Docker because I need linux amd64 image, but my machine is Mac OS M1.
cd ..

docker run --rm -it --platform=linux/amd64 -v `pwd`/nixpkgs:/nixpkgs --workdir /nixpkgs nixpkgs/nix:latest bash

nix-shell -p 'google-cloud-sdk'

export NIX_CONFIG=$'system-features = benchmark big-parallel nixos-test uid-range kvm\\nfilter-syscalls = false\\nexperimental-features = nix-command flakes'

I create a Google Storage bucket BUCKET_NAME
BUCKET_NAME=nix-gce-img nixpkgs/nixos/maintainers/scripts/gce/create-gce.sh

NOTE: If it failed to upload the artifacts for some reasons, copy the artifacts from the container to your local machine and upload tar.gz in the artifacts to GCS bucket and manually create disk image according to the instruction here https://cloud.google.com/compute/docs/import/import-existing-image.
Then, create a Google Compute Engine instance from the image.
After the instance starts running, connect to it via SSH.
gcloud compute ssh --zone "<ZONE>" "<INSTANCE_NAME>" --project "<PROJECT>"

Now, I'm inside Compute Engine instance.
sudo -i

It results in the following error.
sudo: PAM account management error: User not known to the underlying authentication module
sudo: a password is required

Could this be the Google PAM module segfaulting and crashing the Nsncd daemon?
Is Nsncd generating any useful logs? Is it crashing when you see this error? (journalctl -u nscd to access the logs)
(I do not use gcloud, I cannot diagnose this by myself :( )

The NSS module segfaulting and crashing ns(n)cd indeed did happen than once - see https://github.com/NixOS/nixpkgs/pull/214811 and the linked upstream bug.

related https://github.com/GoogleCloudPlatform/guest-oslogin/issues/33

@picnoir error still happens, cant check logs :(
$ journalctl -u nscd
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions.

here are the logs:
Aug 06 07:16:58 peter-rpc-test-shared.us-east4-a.c.bcwt-sandbox.internal systemd[1]: nscd.service: Main process exited, code=killed, status=11/SEGV
Aug 06 07:16:58 peter-rpc-test-shared.us-east4-a.c.bcwt-sandbox.internal systemd[1]: nscd.service: Failed with result 'signal'.
nscd.service: Consumed 32ms CPU time, received 7.9K IP traffic, sent 1.3K IP traffic.
nscd.service: Scheduled restart job, restart counter is at 3.
Starting Name Service Cache Daemon (nsncd)...
nsncd[213941]: Aug 06 07:16:58.391 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 3s }, path: "/var/run/nscd/socket"
systemd[1]: Started Name Service Cache Daemon (nsncd).

Right, the google NSS module is segfaulting. The segfault seem to bring Nsncd down.

Yeah, seems like Nsncd needs to better handle the NSS segfaults. That's not on my todolist though. PR welcome, I'll review it.
Alternatively, google could also work on fixing their NSS module to prevent it to continuously segfault.


rbd: ignore stdErr for ceph osd blocklist when there is no error

ceph osd blocklist range add/rm <ip> cmd is outputting "blocklisting cidr:<IP_ADDRESS>:0/32 until 202..." messages incorrectly into stdErr. This commit ignores stdErr when err is nil.
Signed-off-by: Rakshith R<EMAIL_ADDRESS>

/test all

/test all

all centos ci will get skipped due to skip e2e label(we don't have e2e for this yet)

@mergifyio refresh


Implement Claim functionality in cancel component

Right now when a user cancels a deployment, he cannot claim his funds, even if there are still tokens left.
Implement a feature on the cancelStream component which sends the money left back to the user when he cancels a stream.
cc. @fubuloubu

related to bug here: https://github.com/ApeWorX/ApePay/blob/main/contracts/StreamManager.vy#L229


Add CI workflow to publish crates on tag/release

This commit adds a new github actions work to publish the package's crates to crates.io. This new CI job run cargo publish on the respective crates in the correct order to publish the entire workspace.

Thanks!
I'm trying to understand what the names of the published crates will be. Should we give them uniform prefixes? Maybe it's already in there?
Also, as discussed. I'll remove the pyo3 related crate and edit this PR.

See #13 which prepares the packages for publishing. This just is adding the CI jobs to do the publishing when we're ready to tag 0.0.1.

I originally had prefixed package names in Cargo.toml with oq3_.  I worked this way for quite a while, but found it inconvenient. I was happier after removing the prefixes. So I wonder if it's possible to change the name just the package name, or whatever is used for retrieving from crates.io.
This appears to be what rust analyzer has done. For example the crate in rust analyzer directory hir-def exports module hir and is in package ra_ap_hir_def.

The discussion around the name should probably be in #13 which actually renames things. In general they can be different but I would strongly argue against it. Besides the obvious consistency issues with potentially have 3 different names (crate, module, and directory) for the same thing, the obvious conflict concerns with having such a generic name like parser apply equally to the package name on crates.io as they do for the actual module name. If you published a package as oq3_parser but still had use parser in the code that would be as likely to conflict with something else that was also being used in the same package's development. I did originally leave the directory names the same in #13 but @jakelishman correctly pointed out we should be consistent in how we refer to things otherwise it'll just be confusing.

From the perspective of using it outside a single application (like building on top of it in Qiskit), it's better to have the prefixes, and that aligns closer with how it's actually packaged.  For example, see how PyO3 (a library, rather than an application) works and packages itself.
Within itself, you can always use x as y; to rename if you need, whereas if we do that outside the library, we're going through two+ logical renames.

Another thing that's becoming clear. If find it convenient for developing to sometimes organize code on the level of crates. For various reasons. For example, but not only, the code can easily be built and tested separately.
However when installing or using crates, it looks like the namespace is flat. So each crate in a workspace has to be installed as a separate crate in ~/.cargo and it has to have a globally unique name. Is this correct?
If so, its worth considering things like moving the code in source_file into semantics.

The discussion around the name should probably be in #13 which actually renames things.

This is correct. I was busily editing my last comment, then saw that I had two response comments in the mean time.

Yeah, since we have to hit a flat namespace, the oq3_ prefix give-or-take serves the same purpose as if we could have published all of the crates in this workspace under a oq3:: prefix.

we should be consistent in how we refer to things

We shouldn't have any gratuitous or accidental inconsistency. But it's common in the PL world to have a regular rule for deriving names. Eg. package 'the-packageprovidesThePackage`.

Yeah, since we have to hit a flat namespace, the oq3_ prefix give-or-take serves the same purpose as if we could have published all of the crates in this workspace under a oq3:: prefix.

I don't follow. The flat namespace is present at the level of crates.io ? But it is possible to publish crates under a prefix, for example oq3::?

Within itself, you can always use x as y; to rename if you need, whereas if we do that outside the library, we're going through two+ logical renames.

Doing use x as y internally probably takes care of most of my objections to using the prefix. Doing it once at the top of the file is not so bad. And I am pretty sure the semantics of rust makes this strictly equivalent to using a different name (this is not the case in all languages)
Or we can do what r-a does:
#![cfg_attr(feature = "in-rust-tree", feature(rustc_private))]

#[cfg(not(feature = "in-rust-tree"))]
extern crate ra_ap_rustc_lexer as rustc_lexer;
#[cfg(feature = "in-rust-tree")]
extern crate rustc_lexer;

Beautiful!  =(

Continuing discussing here what should have been discussed in #13: I committed #13 without changing the naming scheme. For example oq3_lexer is used everywhere, never lexer.

@mtreinish and @jakelishman  This PR is no longer blocked by anything.
I spent an hour or so investigating how to publish, but did not see an obvious best way.
Apparently publishing is problematic enough that there are several tools available to assist.
Many issues are discussed. For example, after a crate is published, it takes an indeterminate amount of time before it is available to satisfy a dependency of a subsequently published crate. It seems there may be an automatic sleep interval inserted into some publishing tools. And I saw some talk of an adjustable period because no single period was satisfactory.
However, someone claimed that versions  are not checked when determining if dependencies are satisfied.
Unfortunately, I am unable to find this claim again or any other evidence that it is true or not. If I understand correctly, this means that if we can register and upload these crates just once, then we should be able to upload them in any order and at any time in the future (assuming we don't trigger some security mechanism for avoiding ddos or filling the archive with garbage, unlikely with three or four small crates)

Right. I meant we can figure out the dependence manually and publish them by hand once. I don't have the secret stuff to publish.  I am pretty sure the order is
oq3_lexer, oq3_parser, oq3_syntax, oq3_source_file, oq3_semantics.

John: yeah, at least for the Qiskit package I have with a direct dependency on oq3_semantics, the (reduced) cargo tree looks like this:
jake@ninetales$ cargo tree  | rg 'oq3_'
├── oq3_semantics v0.0.1 (https://github.com/Qiskit/openqasm3_parser.git?rev=88211a6#88211a67)
│   ├── oq3_source_file v0.0.1 (https://github.com/Qiskit/openqasm3_parser.git?rev=88211a6#88211a67)
│   │   ├── oq3_syntax v0.0.1 (https://github.com/Qiskit/openqasm3_parser.git?rev=88211a6#88211a67)
│   │   │   ├── oq3_lexer v0.0.1 (https://github.com/Qiskit/openqasm3_parser.git?rev=88211a6#88211a67)
│   │   │   ├── oq3_parser v0.0.1 (https://github.com/Qiskit/openqasm3_parser.git?rev=88211a6#88211a67)
│   │   │   │   ├── oq3_lexer v0.0.1 (https://github.com/Qiskit/openqasm3_parser.git?rev=88211a6#88211a67) (*)
│   ├── oq3_syntax v0.0.1 (https://github.com/Qiskit/openqasm3_parser.git?rev=88211a6#88211a67) (*)

which agrees with the order you said.


I want to add my resume

I want to add my resume card to the project.

Assigned this issue to @Krishna3451


Create a jupyter_server extension for the classic notebook.

This could be in a classic_notebook repository on the jupyter organization, or as a PR on the actual classic notebook (with a greater risk of not being merged).
The classic_notebook extension could be a way to enable the classic notebook button with JupyterLab when it is installed on the top of the jupyter_server.

Following some discussions with @minrk on this. There are two main ways to go with this

Create a new classic_notebook project which either depends on notebook and allows the jupyter server to server the classic notebook JavaScript.
Open a PR to the notebook repository to make it use the Jupyter server.

The second approach would be more disruptive for the classic notebook repository which is presumably under maintenance mode, but would result in less duplication. Also, it would mean that the classic notebook would need to be updated upon backward incompatible changes in jupyter_server... An advantage though would be that PRs improving the current notebook server would apply to jupyter_server and won't fall between the cracks.
cc @takluyver @gnestor.

👍 for the second approach, I think it is easier to explain to users as well.

Here's my experiment—making the classic notebook a jupyter_server extension (using the API from #48). It's so much cleaner!
https://github.com/Zsailer/notebook_server_extension
@SylvainCorlay — Should I open a the dracarys PR in notebook? 😉

See this PR in the classic notebook.

Closing for now, since NBClassic exists.


WebCL Rebase M50

Rebase WebCL on M50
Adapted to the following changes:
WebCL: Adding missing virtual final destructors for corrseponding
classes to avoid possible destruction unexpected behaviour.
WebCL: Change WebCLCallback parent class from RefCounted to
GarbageCollectedFinalized for idl generation rule changed. Now the
upstream generate idl interface with callback attribute with oilpan
support.
WebCL: Due to WebCLCallback is oilpan supported, modified RefPtr to
Persistent in corresponding non-garbage-collected class to elimate
compile error.

@hujiajie @rakuco  PTAL

There's no need to replace adoptRef() with explicit Member<>() or Persistent<>(), just use raw pointer there.
Please make sure either Oilpan style or Oilpan-transition style (FooWillBeBar) is used, but not both.


update agent scripts

PR Summary
Commit d6a228af2f48312015d4d3ee31abec12aa38558c moved the location of some of action_spec_ignored.py and memory_component.py. This PR adjusts sources to changes.

@jagapiou please review this small PR when possible

Merged in b4b380bf0483189627be34b91fff700711a9dc92


#15739 Remove new line after certain keywords for compact formatter

New line should not be added after SELECT, UPDATE, INSERT, DELETE, FROM, WHERE and ,

verified


Allow pipeline results to use custom task results

Fixes #3595
This PR enables pipeline results to refer to pipeline tasks that run custom tasks and produce results.

Changes
Adds support to resolve pipeline result references to pipeline tasks that run custom tasks and produce results.
/kind feature
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Pipeline results now can refer to pipeline tasks that run custom tasks and produce results.

@sbwsg fyi

@sbwsg fyi

/lgtm
/approve

/lgtm
/approve