camera plugin test -[CameraOrientationTests testOrientationNotifications] Failed to set device orientation: Not authorized for performing UI testing actions

On Xcode 13.0 beta 1, -[CameraOrientationTests testOrientationNotifications] introduced in https://github.com/flutter/plugins/pull/4010 fails:
XCUIDevice.sharedDevice.orientation = UIDeviceOrientationPortrait;

Error: Failed to set device orientation: Not authorized for performing UI testing actions.
https://github.com/flutter/plugins/blob/af2407514b0bcee1777f9e17ba94c23781b7c19f/packages/camera/camera/example/ios/RunnerTests/CameraOrientationTests.m#L27

I guess Xcode 13 will limit the use of XCUIDevice to XCUITests.
@stuartmorgan we discussed not needing a XCUIDevice camera, but I think we either need to add one or delete this test.  WDYT?

I'm in favor of adding XCUITests anywhere we end up actually needing them, so converting them over SGTM.

BUT why is this working then on a real device using iOS 15? I mean in our case even XCUIScreen.main.screenshot() is broken which is nowhere marked as working differently now...

@stherold Don't know, that's a question for Apple.  🙂


Tests fail unreliable

The test remove_all_inputs_notebook fails unreliable sometimes. I made a table to list the used versions:

OS
Python
Pandoc
pipeline fails

Windows
3.8.5
2.8
1

Windows
3.8.5
2.10.1
3

Windows
3.9.0
2.7
1

It seems like if the source notebook is not executed properly: https://github.com/m-rossi/jupyter-docx-bundler/blob/master/jupyter_docx_bundler/tests/conftest.py#L308


Link names to corresponding profiles

As a staff member, if I click an adopter name or pet name in the Applications table, I should be redirected to the corresponding profile.

I would love to work on this issue . I have a doubt though.  Just next to applicant name we have a profile icon linking to the adopter profile. So I am wondering how to avoid redundancy here . Should we have both or remove which one ?

Yeah totally, theres another ticket to remove that column so lets just update links for now


Add an asychronous email queue for registration

Wraps email sending functionality in an asychronous queue so we don't overwhelm the server when sending large numbers of emails. If running registration with replicas, they all work on a shared email queue.

@petschekr I've tested locally that all 5 entrypoints send email correctly


Migrate verifier to use common.MarkedSource [phab:D1649]

Created by schroederc at 2017-05-17 20:22:53:
Continuation of #2071 and #2072.

zarko accepted this revision at 2017-05-17 20:23:39

schroederc closed via commit 358fea8c5967c6241a88a8b1483cf0caff0e7023 at 2017-05-17 20:24:08


App for Nixpkgs backports

CI currently doesn't get triggered for the automated Nixpkgs backports, e.g. see https://github.com/NixOS/nixpkgs/pull/360258. This happens because the PR is created by the default GitHub Actions bot account, which has some built-in infinite recursion prevention measures.
We can fix this by using a separate GitHub App bot account instead. This is a dependency for https://github.com/NixOS/nixpkgs/pull/360260.
Instructions for @NixOS/org:

Create new App (direct link)

Name: Nix Backports
Homepage URL: https://github.com/NixOS/nixpkgs
Disable Webhooks
Permissions:

Repository > Contents: read-write (to create the backport branch)
Repository > Pull Requests: read-write (to create the backport PR)

Install the App on the NixOS, give it access to only https://github.com/nixos/nixpkgs
Set the App ID as a new repository variable (direct link) named BACKPORT_APP_ID
Generate a private key for the App and set it as a new repository secret (direct link) named BACKPORT_PRIVATE_KEY

For NixOS/nix, @Mic92 has set up mergify. This solves the GHA recursion prevention problem, and could save us from reinventing the wheel. I think installing that GitHub App does not create any disruption before its config file is added to the repo (or after, if handled with care), but I'd like to confirm that. @Mic92 wdyt?

I think for now it would be easiest to just add the tightly-scoped GitHub app, it doesn't take much to make use of it: https://github.com/NixOS/nixpkgs/pull/360260

I am ok either way. Can we have mergify as well? It has commands to rebase/squash pull requests and also the merge queue feature is need (heavily used in nixos-hardware) to make sure main is always green.

I'd rather have everyone use Mergify (or GH merge trains) since we now can actually reliably (and quickly!) report on eval status. I don't think we should add Mergify to Nixpkgs until we decide how to handle that.

@winterqt what do you want to know about mergify? There is no much magic needed to use it. I can prepare a simple configuration. The big advantage of mergify over github merge queues is that, it allows to specify rules in a configuration file, so we don't need admin rights every time we add a new check. The other advantage is that the merge action can be triggered with labels, which allows for automerging backports for example.

I'm saying that that's sort of a large enough change that we'd need to communicate to all committers -- I'd rather not have some people using it and some not.

Well. Before we make it mandatory, we should evaluate it in a smaller group. If the alternative is not using merge queues, there is no downside if some testers are using it. We also need this feature for merge-bot.

New issue: https://github.com/NixOS/org/issues/39

@winterqt I guess you mean #39, not this issue.

Done. We'll follow up on the Mergify stuff soon.

With this done, https://github.com/NixOS/nixpkgs/pull/360260 is now ready :)


Unable to resize window on wayland when native titlebar used

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.95.3 (Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813)
OS Version: Linux x64 6.11.10-200.fc40.x86_64 (Fedora Workstation 41)

Also tested on insiders build

VS Code Version: 1.96.0-insider (Commit: 475acb4b9bdd77d4204224990bf288ed5bfe6b0e)
OS Version: the same

Steps to Reproduce:

Change TitleBar style to native;
Start vs code with command code --ozone-platform=wayland. With or without options --ozone-platform-hint and --enable-features it does not matter;
Try to resize window with mouse;
You don't see any changes in coursro appearance when pointer close to application window edge or right above it.

The only ways to change window size are

Double click on titlebar to maximize window;
By calling window.resizeTo(w, h); from developer tools.

/duplicate 210624

#210624


Fatal error, see debug.log

I've installed 0.10.2, but on an existing wallet.dat. It started loading the transaction chain, but at 49 weeks behind, I got an error 'fatal error, see debog.log for details'. The last line of debug.log was:
*** System error while flushing: CDB : Error -30974, can't open database

If I close and re-open bitcoin-qt, it works for a while before throwing this error again.

My friend... are you sure you're on the right repository here?

@stijnsanders I'm going to close this for now, since it doesn't seem like you're talking about Atom. Let me know if this is actually Atom-related.

oh yes, completely the wrong repo (things so great you have to name them twice (in the URL): atom, bitcoin..)


Running the workflow removes rust override set up by previous actions-rs/toolchain call

My workflow would set up a nightly Rust and then the Xtensa port, something like this:
      - name: Install nightly Rust
        uses: actions-rs/toolchain@v1
        with:
          profile: default
          toolchain: nightly
          override: true
          components: rust-src

      - name: Install Rust for Xtensa
        uses<EMAIL_ADDRESS>        with:
          version: "<IP_ADDRESS>"
          buildtargets: esp32

xtensa-toolchain removes the override so later steps use stable rustc instead of nightly.

My memory is a little fuzzy on this, but this was changed in order to handle rust-toolchain.toml files specifying the esp toolchain, which obviously does not exist for the official compiler. You can see this commit is where the changes were made.
I can try to play around with this next week and see if I can get it working without using overrides.

I'm using nightly to run rustfmt and clippy, and even if I flip the order of the two workflow steps, the tools don't get picked up correctly. Due to this I went back to my custom 4-liner install script instead of this workflow for now.
I guess a "remove overrides" option would help, but I might be a special case.

Hi @bugadani! Is, by any chance, the repository where you are using the CI open? If so, would you mind sharing it?

@SergioGasquez sorry it's closed :(

Would you mind testing with:
      - name: Install nightly Rust
        uses: actions-rs/toolchain@v1
        with:
          profile: default
          toolchain: nightly
          override: true
          components: rust-src

      - name: Install Rust for Xtensa
        uses: SergioGasquez/xtensa-toolchain@main
        with:
          version: "<IP_ADDRESS>"
          buildtargets: esp32
          override: false

@SergioGasquez looks like our CI is happy with your solution, thanks for looking into this!

@SergioGasquez It looks like our CI is happy with your solution, thanks for looking into this!

No problem! Just created #11 to merge the changes!


onerror ember.testing call is happening to component file instead of app.js file in route

I have implemented onerror call in my app.js file and inside it I am checking the ‘if’ condition for ‘ember.testing’ in route:
let onerror = function() { if (ember.testing) { throw error; }
but there is same condition i have in my component.js file. So, when error is triggered it call the component.js file , whereas i expected it should call my app.js file condition.
Please can anyone of you suggest the same?

Thank you Chris that helped. :)


Code maintenance - Fix pylint and PEP8 warnings

Run the pylint and PEP8 dev scripts on the existing code base and fix as
many warnings as possible on the files we have added or changed.

Linked with issue #146


Omap operations on nonexistent object

I'm not super familiar with the C or C++ versions of librados, so this may be intended behavior but if you attempt to read omap values on a nonexistent object, you get an Input / Output error, not ErrorNotFound:
func TestOmapReturnedError(t *testing.T) {
	conn, _ := rados.NewConn()
	conn.ReadDefaultConfigFile()
	conn.Connect()
	ioctx, err := conn.OpenIOContext("mypool")
	if err != nil {
		panic(err)
	}
	_, err := ioctx.GetAllOmapValues("def.not.exist", "", "", 100)
	if err != rados.RadosErrorNotFound {
		t.Fatalf("unexpected error code %v", err)
	}
}

And I get: unexpected error code rados: Input/output error
I generally like to treat object not found errors differently from "can't speak to OSD or MON" errors, and Input/output error is a bit vague. If it is not possible to reliable disambiguate the errors and coerce the type with what librados gives us then feel free to close this, but it bugs me.

hi @immesys  ,
It return EIO (Input/output error) because you try to get non-exist omap.
The omap flag would be set when setup omap, so in this situation (never set omap and try to get it) return EIO I think it correct.
thanks!
vicente

Hi, to clarify, my perceived problem is:
If I try to get an omap value, and I receive I/O Error, I do not know if that means the object does not exist or if it means the network / cluster is degraded.
One possible solution I guess is for me to try stat the object after I get the I/O Error to see if the nonexistent object is the cause, but I find it odd that every other rados operation I do will return ErrorNotFound if you try interact with a nonexistent object but omap get will not.
I guess my question is, is there sufficient information at the librados level to disambiguate between sources of I/O error when you do this operation (not found vs other) without additional network round trips? If so, then I believe not using it is a bug. If not, then we can close this.

hi @immesys
sorry for late reply : (

If I try to get an omap value, and I receive I/O Error, I do not know if that means the object does not exist or if it means the network / cluster is degraded.

I think it means not exist here.

One possible solution I guess is for me to try stat the object after I get the I/O Error to see if the nonexistent object is the cause, but I find it odd that every other rados operation I do will return ErrorNotFound if you try interact with a nonexistent object but omap get will not.

I guess my question is, is there sufficient information at the librados level to disambiguate between sources of I/O error when you do this operation (not found vs other) without additional network round trips? If so, then I believe not using it is a bug. If not, then we can close this.

That because we need the omap flag to get it, or it would return nothing.
Then we try to decode it and you would get EIO return code.
for now, I think we do not have sufficient information to clarify these two situation, because the only way to setup omap flag is that you set omap (on my understanding)
The get omap op would return NotFound is that you have omap but you cloud not found omap iterator.
In above situation, you would get NotFound error.
thanks!!
vicente

Receiving EIO return value strikes me as a deeper issue. I can think of two reasons that might occur. The first is if there is a low-level problem in the rados cluster. If everything else is working fine, let's rule that out. The second option is that go-ceph is linking against a client C library that is incompatible with the cluster. I'm not sure to what extent all combinations of ceph versions are wire compatible. In any case, is that the only go-ceph test that is failing for you?

This is actually one of my own tests, and the object in question does not actually exist. My objection is, as you have observed, that I cannot distinguish between an unhealthy cluster, and a non-existent object. One is dire, the other inconsequential, so I would prefer if attempting to access a non-existent object returned ErrorNotFound rather than EIO which I typically treat as an indication of a more severe problem with the cluster.

If you are suggesting that it should not return EIO in this scenario then I will investigate librados version stuff, it is entirely possible that I am not linking against the same version the cluster is running. My build machine uses librados from the xenial repo whereas the cluster is running the latest jewel

Also, to explicitly answer your question, the cluster is healthy and everything else is working fine.

I'm suggesting that if the object is non-existent you should not be receiving EIO. It may be the case, but I am suspect because the error codes returned from librados are usually intuitive (e.g. I would expect something like ENONET). A quick test would be to execute the equivalent C code against your cluster and test the return value, as go-ceph is a very light wrapper around it. I have seen users have an issue where they have a version of ceph in /usr/ and /usr/local. What if you try to read a non-existent object with go-ceph? Certainly in that case we expect something like ENONET and EIO would be more evidence of something wrong with wrapper/library versions.

Ah, good, then we are on the same page.
Other operations appear to return rados.ErrorNotFound (like normal object reads as opposed to OMAP operations) when the object does not exist. I don't recall if I tested xattrs.
I'll try redo this test with go-ceph linking against jewel librados either today or tomorrow and see if I get a change in error code.

I was able to get the travis-ci scripts running again today. I have them running for jewel and kraken, and all of the librados tests pass. Perhaps you could submit the test case that is failing for you so it can run on the CI infrastructure?

I believe that test will reproduce. I did the experiment linking against the latest librados.so and librados header files and I get the same results

Thanks for the patch, and it is indeed failing for both jewel and kraken. I'll take a look at this tomorrow I suspect it will be something simple.

Did this end up being something simple?

Sorry, got swamped. I just pushed a fix and merged your test case. It worked locally on my machine. Here is the CI job for the updated branch. If it passes then you should be good to go https://travis-ci.org/ceph/go-ceph/builds/193813916

The tests seemed to have passed. I'll close this. Please let me know if you have any other issues. Thanks again for reporting.

Awesome! Thank you!


Support multiple BGP upstream peer configuration

As an end user, I have a need to support and configure multiple upstream BGP peers.
It looks as though work may had begun on this previous and was commented out, but I am not sure if that's right or not:
https://github.com/plunder-app/kube-vip/blob/master/cmd/kube-vip-config.go#L49-L58
Thank you for your help.

If we use the Packet API, with --packet then it will automatically find all peers from the API. To specify this manually the --bgppeers flag has been added.

^This will be closed when 0.2.3 is merged into main.


My book cover images will not load

Everything looks great except it won't load the book cover images.  It's just showing the link.  What am I doing wrong?

Oh, I'm sure we can figure that out. Could you post the content of the file that should display the covers?

That did it!  Thank you for creating this!  It might be my new favorite plugin :)


Virtual machine crashes if a new node is started during a wait command

Note: I'm not sure if this is a bug in the Unity or non-Unity part of Yarnspinner, but I'm posting it here because it's happening with the beta, and seems related to #91 so it may be expected behavior by the vm when passed bad input or something like that.
I don't know how computers work.
What is the current behavior?
If a new node is started during a wait command, the wait command continues, interrupts delivery of the new node, and then the Yarn Spinner virtual machine throws a stack empty error at the end of the new node.
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
I'm honestly not completely sure. It's happening very frequently in my project, but never in the same place twice.
All I can say for sure is that it's always preceded by the warning I added for the current line being null, so it may be caused by passing the VM a null line or something like that and my error check there is just preventing the Unity part from crashing before this happens. In which case this can be ignored if that other issue is fixed.
EDIT:
I've narrowed down the cause to either the DoPlayback() coroutine in VoiceOverPlaybackUnity.cs, the wait command coroutine in DialogueRunner.cs, or the interaction between the two.
In my project, the situation is triggered by the following:

First, all nodes are triggered by in-world triggers calling StartDialogue on the dialoguerunner, even if something is already playing. I think that's the correct way based on the sample projects but if not, that may be relevant. All of my lines have associated voiceover.
The first node playing has the following structure:

title: FirstNode
---
Here's a long line of dialogue waiting to be shown to the player
<<wait 1>>
Here's another line.
===

If the next node is triggered during the playback of the first or second line, it works normally with no errors.
If the next node is triggered during the one-second wait, it plays the first line of the second node, but skips to the second line of the second node when the one-second wait coroutine ends. The node then continues to play normally, but the stack empty error is thrown when the second node completes delivery.

What is the expected behavior?
The VM shouldn't crash with invalid input (if that's the cause), or should recover from an error like this, or should catch the error and throw a clearer message about what happened.
Please tell us about your environment:

Yarn Spinner Version: 2.0 beta 4
Unity Version: 2019.4.19f1

Other information
A quick and dirty fix is to add StopAllCoroutines(); at the beginning of StartDialogue() in DialogueRunner, but I'm sure this will cause some other errors down the line, either with other coroutines, or with user-written yarncommands.
Screenshot of console log - the "it happened again" messages are a quick dirty check I threw in UpdateLineStatus() to catch the error in #91, but I have no idea why they're always thrown twice immediately before this stack empty error.

The actual stack trace of the error:
InvalidOperationException: Stack empty.
System.Collections.Generic.Stack`1[T].ThrowForEmptyStack () (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0)
System.Collections.Generic.Stack`1[T].Pop () (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0)
Yarn.VirtualMachine+State.PopValue () (at <fb322facd0ad4285bdf3abe6771489bf>:0)
Yarn.VirtualMachine.RunInstruction (Yarn.Instruction i) (at <fb322facd0ad4285bdf3abe6771489bf>:0)
Yarn.VirtualMachine.Continue () (at <fb322facd0ad4285bdf3abe6771489bf>:0)
Yarn.Dialogue.Continue () (at <fb322facd0ad4285bdf3abe6771489bf>:0)
Yarn.Unity.DialogueRunner.ContinueDialogue () (at Library/PackageCache/dev.yarnspinner.unity@a3a35e8140/Runtime/DialogueRunner.cs:1297)
Yarn.Unity.DialogueRunner.DialogueViewCompletedDismissal (Yarn.Unity.DialogueViewBase dialogueView) (at Library/PackageCache/dev.yarnspinner.unity@a3a35e8140/Runtime/DialogueRunner.cs:1401)
Yarn.Unity.DialogueRunner+<>c__DisplayClass86_0.<DismissLineFromViews>b__0 () (at Library/PackageCache/dev.yarnspinner.unity@a3a35e8140/Runtime/DialogueRunner.cs:1386)
Yarn.Unity.DialogueViewBase.DismissLine (System.Action onDismissalComplete) (at Library/PackageCache/dev.yarnspinner.unity@a3a35e8140/Runtime/Views/DialogueViewBase.cs:92)
Yarn.Unity.DialogueRunner.DismissLineFromViews (System.Collections.Generic.IEnumerable`1[T] dialogueViews) (at Library/PackageCache/dev.yarnspinner.unity@a3a35e8140/Runtime/DialogueRunner.cs:1386)
Yarn.Unity.DialogueRunner.DialogueViewCompletedDelivery (Yarn.Unity.DialogueViewBase dialogueView) (at Library/PackageCache/dev.yarnspinner.unity@a3a35e8140/Runtime/DialogueRunner.cs:1262)
Yarn.Unity.DialogueRunner+<>c__DisplayClass73_0.<HandleLine>b__0 () (at Library/PackageCache/dev.yarnspinner.unity@a3a35e8140/Runtime/DialogueRunner.cs:815)
Yarn.Unity.VoiceOverPlaybackUnity+<DoPlayback>d__7.MoveNext () (at Library/PackageCache/dev.yarnspinner.unity@a3a35e8140/Runtime/Views/VoiceOverPlaybackUnity.cs:140)
UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <a555715ef291462eb190c2c939543f55>:0)

fwiw, we've been seeing this on and off for a while on an older version.  Our stack looks like this:
InvalidOperationException: Stack empty.
  at System.Collections.Generic.Stack`1[T].Pop () [0x00008] in <ae22a4e8f83c41d69684ae7f557133d9>:0
  at Yarn.VirtualMachine+State.PopValue () [0x00000] in <60a9cde088b1430eb5c95ed66926df4f>:0
  at Yarn.VirtualMachine.RunInstruction (Yarn.Instruction i) [0x00142] in <60a9cde088b1430eb5c95ed66926df4f>:0
  at Yarn.VirtualMachine.Continue () [0x000ae] in <60a9cde088b1430eb5c95ed66926df4f>:0
  at Yarn.Dialogue.Continue () [0x0000f] in <60a9cde088b1430eb5c95ed66926df4f>:0
  at Yarn.Unity.DialogueRunner.ContinueDialogue () [0x0000d] in <3964ba3f7c3b4248be52e8b58158f0ad>:0
  at Yarn.Unity.DialogueRunner+<>c__DisplayClass42_0+<<CreateDialogueInstance>g__DoHandleWait|11>d.MoveNext () [0x0003f] in <3964ba3f7c3b4248be52e8b58158f0ad>:0
  at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00026] in <251be4efae014ce8ac9c16c930d6c8b5>:0

(Filename: <ae22a4e8f83c41d69684ae7f557133d9> Line: 0)


Transparent text when typing into an Editor widget on macOS

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

$ go version
go version go1.18.2 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN="/Users/prologic/go/bin"
GOCACHE="/Users/prologic/Library/Caches/go-build"
GOENV="/Users/prologic/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/prologic/go/pkg/mod"
GONOPROXY="github.com/aucloud"
GONOSUMDB="github.com/aucloud"
GOOS="darwin"
GOPATH="/Users/prologic/go"
GOPRIVATE="github.com/aucloud"
GOPROXY="https://goproxy.mills.io/"
GOROOT="/usr/local/Cellar/go/1.18.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.18.2/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.18.2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/prologic/tmp/samples/widgets/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/8h/c9gl4gms3fjb0kyf7nb42ybh0000gn/T/go-build4005998222=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
$ git clone https://github.com/nuxui/samples.git
$ cd samples/widgets
$ go mod tidy
$ go build .
$ ./widgets

Then:

Type some text into the Editor widget at the bottom
See it expand as you type
Notice the text is invisible?

See attached screenshot.
What did you expect to see?
The text I typed!
What did you see instead?

Similarly none of the follow work as expected:

Selection
Double tap
Right click

All these events seem to do nothing. Is this expected?

The ui.Editor default text color is white, set black you see it.
Basic widgets is in developing, like ui.Column, ui.Row, ui.Editor has much defect.
After supported android, I will complete these widgets

Similarly none of the follow work as expected:
* Selection

* Double tap

* Right click

All these events seem to do nothing. Is this expected?

I think you should open a new issue and close this one.
Or change the address of this issue.


[Bug]: An error occurred (ResourceNotFoundException) when calling the DescribeNodegroup operation: No node group found for name: default-20240424100336089600000010.

Installation method
Own AWS account
What happened?
Got error when executed below command:
prepare-environment fundamentals/storage/ebs
Error:
An error occurred (ResourceNotFoundException) when calling the DescribeNodegroup operation: No node group found for name: default-20240424100336089600000010.
An error occurred, please contact your workshop proctor or raise an issue at https://github.com/aws-samples/eks-workshop-v2/issues
The full log can be found here: /eks-workshop/logs/action-1714463707.log
What did you expect to happen?
Expected for command to be successful
How can we reproduce it?
I updated and executed eks.tf
eks_managed_node_groups = {
default = {
instance_types       = ["t2.large"]
force_update_version = true
release_version      = var.ami_release_version
        block_device_mappings = {
    xvda = {
      device_name = "/dev/xvda"
      ebs = {
        volume_size           = 75
        delete_on_termination = true
      }
    }
  }

Anything else we need to know?
No response
EKS version
1.29

Upon further investigation, looks like the command uses old values from env.bash file

So does it appear that you updated the node group in the Terraform, re-ran apply and the node group name changed?

I'm going to close this issue since we've migrated the Terraform to use a static node group name


Use SenateMembers in is_senate_member helper

This PR is required for the new change in subtensor which removes the Senate collective instance, simplifying the runtime for ease-of-use. You can find the matching PR for subtensor here.

We don't need the subtensor update to use this change in the CLI, merging.


provide container information

need more information for running ccs

fix in v0.5.15
look more in
https://github.com/twcc/TWCC-CLI/tree/v0.5#v0515-release-note


"Unauthorized" error after successfully setting API key

Your API key has successfully been set.
But then...

In MakesHttpRequests.php line 101:

  Unauthorized

Running forge credentials gives the same error.

Interesting! I have a feeling this may be related to #13. Can you manually enter your API key in ~/forge.json, and see if that fixes the issue?

Yes! 👌 🎉


Time range for week view/mode

First of all, I really love this package! Super light and easy to use.
So I was looking for a calendar that shows a weekly events and thankfully I found this package. I got it working with some few mods using CSS etc. Read the docs to explore more features but after several minutes of circling around your docs, I can't find a setting/option where I can select what time the calendar (week view/mode) should start and end.
Below is the screenshot of the app I'm working on. As you can see, it's a school schedule - classes starts as early as 6am and the last period ends at 8/9pm. Space consumed by 12mn to 6am is a bit long that a user needs to scroll down to start seeing their schedule.

So yea, maybe a feature/options/settings that's something like this :) I'd like to have my calendar to start at 5am then ends at 10pm - that way it still have a space/allowance after the header and before the bottom of the calendar.

Thank and more power!

First of all, thank you for your kind words. I appreciate it!
I will try to look into this on the weekend, because I agree that this would be a good option to have configurable.
Until this is released, you can try and use an undocumented config-option called scrollToHour. This is a feature I never documented, because I still haven't made it play nicely with all the other config-options. But for your use-case, maybe you could try scrollToHour: 5. Potentially that will help you somewhat, while waiting for the feature from this issue.

This is not quite what you asked for, but I managed to quickly fix the week.scrollToHour option. It is now also documented under: https://tomosterlund.github.io/qalendar/#basic-configuration
About the initial feature proposal: I investigated the requirements in regards to the source code, and it turns out to be a bigger task than I had first estimated. A fair number of places in the source need to be adjusted for this to work out. I went ahead and added the feature to the roadmap, so it won't be forgotten: https://github.com/tomosterlund/qalendar/projects/1
If you could picture building parts of this feature, I can assist you in getting it done. If not, we can close the issue.

Closing issue due to inactivity.
Thanks again for the suggestion. Feel free to open the issue again at any time, if you can picture building parts of the feature.

hello @eriqamiqo
How are you changing the background color of today number of mounth ?

@eriqamiqo your requested feature is now available with version 1.12.0.
Documentation for it: https://tomosterlund.github.io/qalendar/#day-boundaries


Introducing the Cognitive Services RP Swagger

Api version - 2016-02-01-preview

Hi @daniel-ms, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (danvar). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Add warning in README about flashing images

Some people with epilepsy might be sensitive to the fast flashing images shown when running the project, so adding a noticeable warning in README will help those people be prepared for it.

Added to master and 3.2 branch


MapView scroll to zoom in and zoom out does't work

Hi, I am trying to load ESRI map in window_webview and it is working fine, but when I try to zoom and zoom out by scrolling, It doesn't work. I am using the latest version. Is there any method or widget like WebViewAware or how can we fix this?
Thanks for awesome package

I end up adding my own listener to flutter webview widget and handle the same in JavaScript content

I end up adding my own listener to flutter webview widget and handle the same in JavaScript content

Any code examples


React.js Library

Kinda surprised that this doesn't exist already.  Many frontend solutions prefer not dropping a  tag into head.
Any plans for an async React library?

@f2prateek Does analytics.js load synchronously? The more "standard" way to use it would be include it in package.json, and load it and init it in a javascript file.
I get what you're saying wrt to the script being generated dynamically. Maybe the solution is just better documentation on how to use it.
The current approach seems to be to assume it exists in the container environment, but this just feels kinda brittle.

Because of the dynamic generation piece, it has to load async as well. Here's an example we wrote recently https://github.com/segmentio/analytics-react

@f2prateek with the above is it possible to load two separate segment instances on a page for two separate projects? The use case here is for an embeddable website plug-in. Eg, if the host page Already has a segment instance loaded I still need to be able to log to segment from the embedded plug-in.

@f2prateek with the above is it possible to load two separate segment instances on a page for two separate projects? The use case here is for an embeddable website plug-in. Eg, if the host page Already has a segment instance loaded I still need to be able to log to segment from the embedded plug-in.

If you are relying on analytics.js you cannot have two instances on a single web page. You can look at using the HTTP API endpoint. The HTTP API endpoint requires you to provide your own anonymousId or userId and client-side timestamps.

Leaving this here for an example of using React/Sending data to multiple sources: https://github.com/segmentio/ajs-multiple-writekeys-demo


Do not pass --with-libxml-dir to PHP 7.4

PHP 7.4 no longer supports --with-libxml-dir (https://github.com/php/php-src/pull/4037).

Coverage increased (+0.2%) to 41.181% when pulling 8d6dc9cef85deb74b1031e599983ccdb1772586a on morozov:php74-libxml into e5cf9af67aa38a7bbc424cea751986d561c02931 on phpbrew:master.

Coverage increased (+0.2%) to 41.181% when pulling 8d6dc9cef85deb74b1031e599983ccdb1772586a on morozov:php74-libxml into e5cf9af67aa38a7bbc424cea751986d561c02931 on phpbrew:master.

With this PR, it makes phpbrew can not find libxml when build php 7.x when x<=3  in macOS with homebrew. I have to set LDFLAGS and CPPFLAGS for xml manually.

@markwu could you file a new issue please? There, you'll need to provide the phpbrew --debug install command you're using to install PHP <= 7.3 as well as the ./configure command that PHPBrew 1.23.1 and PHPBrew 1.24.1 generate. As far as I remember, there shouldn't be any difference in the result when installing PHP 7.3 or older.

Okay, give me sometime to figure out what's going.


Feature request) Accumulators with no axis should have a layout_type template arg

Similar to #1331, it would be nice to be able to specify the layout_type here in the accumulators as well, as currently it gives me non-intuitive results over in R with its column major layout.
https://github.com/QuantStack/xtensor/blob/0729a89d00184b7bfbb3dac5e26b91cb1a3ea62d/include/xtensor/xaccumulator.hpp#L259

do you have a quick example / test?

// Both required for cumsum() / cumprod()
#include <xtensor/xarray.hpp>
#include <xtensor/xview.hpp>

// -----------------------------------------------------------------------------

// [[Rcpp::export(rng = false)]]
xt::rarray<double> rray_cumsum_impl(const xt::rarray<double>& x) {
  xt::rarray<double> res = xt::cumsum(x);
  return res;
}

> matrix(1:6 + 0, ncol = 2)
     [,1] [,2]
[1,]    1    4
[2,]    2    5
[3,]    3    6
> rray_cumsum_impl(matrix(1:6 + 0, ncol = 2))
[1]  1  5  7 12 15 21

See how it accumulates 1, 1+4, 1+4+2 rather than 1, 1+2, 1+2+3

ok thanks, now i see.
I think it's not that complicated, but also not that easy to fix (for more than the 1D accumulation ...). Basically we need to swap everything over for column major...

can you define XTENSOR_DEFAULT_TRAVERSAL?
This is used in xtensor now: https://github.com/QuantStack/xtensor/blob/master/include/xtensor/xaccumulator.hpp#L260
I think it would fix your issue ...

I can but just fyi "We strongly discourage using this macro, which is provided for testing purpose."
https://xtensor.readthedocs.io/en/latest/dev-build-options.html


UI stack for front-end deployment

Use Typescript-CDK to define a standard S3 bucket / cloudfront / cognito deployment.
CDK example on Project Overwatch:
https://github.com/ScottLogic/project-overwatch/blob/main/cloud/lib/ui-stack.ts
Notes

#385 must be completed first!
Start with a cloudfront domain, but without Route53.
Cognito userpool linked to an Azure AD sandbox: might already have been done as part of #385, otherwise see Project Overwatch example, linked above.
At this stage, manually deploy bundled UI to the bucket, using AWS CLI.
Remember to empty the bucket and destroy the stack after testing! Do not leave it up until we are certain it is secure.
Document the process of setting up Azure sandbox in cloud README - see Overwatch repo for guide.

Questions

Auto-authenticate on app load, or a login button? Or start with the latter then progress?

Out of Scope

Pipeline deployment of all stacks will be covered in a subsequent issue.

Acceptance Criteria
CDK code for (manually) deploying UI stack.
Stack deployed using CDK CLI, UI deployed to bucket using AWS CLI, deployment and connection with back-end verified, then bucket emptied and stack destroyed using CDK CLI.

Progress to date
I have successfully stood up the UI fronted by Cloudfront, but without any authentication. This part can be merged into a (long-lived) feature branch, and then two other issues spawned:

Route53 for routing, so that UI and API can be SameSite
Authentication with Cognito, backed by ScottLogic azure AD


Annotation scheduler.alpha.kubernetes.io/critical-pod not registered / documented

This is a Bug Report

Problem:
Kubernetes previously paid attention to an annotation, scheduler.alpha.kubernetes.io/critical-pod. We now use Pod Priority instead.
Even so, https://kubernetes.io/docs/reference/labels-annotations-taints/ should document that annotation.
Proposed Solution:
Document that annotation; as a side effect, this registers it. I assume that we should also mark it deprecated.
Page to Update:
https://kubernetes.io/docs/reference/labels-annotations-taints/

Additional Information:
/language en
/priority backlog
/sig scheduling

/assign

/triage accepted


no wifi scan complete callback

currently you need to do busy waiting for the scan to complete. This is not optimal in RTOS setups. There should be a callback when the scan is finished.

How would you defined "complete"? You don't need to block at all, just scan for a set time and it will keep returning results. Also you have raised this against the pico-sdk which doesn't maintain this code https://github.com/georgerobotics/cyw43-driver. Closing as not an issue.


Python files wrongly identified as PLpgSQL for the Gramps-project

Any idea why Github identifies 52.5% of the Python files are PLpgSQL files?
Definitely no PLpgSQL in the Gramps project as far as I can identify.
https://github.com/gramps-project/gramps

Probably unrelated but does mention PLpgSQL #2384

This is happening because of these two huge files:

https://github.com/gramps-project/gramps/blob/master/gramps/webapp/empty.sql
https://github.com/gramps-project/gramps/blob/master/gramps/webapp/example.sql

See Linguist overrides to ignore them.

Ok, I did spot those two and didn't believe them to have that much influence over the result.
Thank you


Multiple content pages not support

Describe the bug
To Reproduce
Steps to reproduce the behavior:

Add another content pages
npm run build
Load the new extension ,and you will see the errors

Expected behavior
Works normally
Screenshots

Desktop (please complete the following information):

OS: [e.g. Mac, Window, Linux] Mac
Browser [e.g. chrome, firefox] hrome
Node Version [e.g. 18.12.0] v18.17.0

Additional context
When only one content pages, after build ,it works well ,and without any import script

But when multiple content pages added ,the __vitePreload script  came to be imported using import,and  browser not allowed that.I think it might be the rollups default behavior,but did`t  found a way out

The current manifest configuration can only support one content script, but let's make it better! You can modify your own build settings and manifest settings to load more than one content script.
I'll try to make it easier to do this in Boilerplate, but I don't think it's a high priority.

The current manifest configuration can only support one content script, but let's make it better! You can modify your own build settings and manifest settings to load more than one content script.
I'll try to make it easier to do this in Boilerplate, but I don't think it's a high priority.

yeah,after several attempts, I solved this problem using acustom plugin.
In short, i extract the __vitePreload module code and inject into  root conent pages
// utils/plugins/inline-vite-preload.ts
export default function inlineVitePreloadScript() {
  let __vitePreload = '';
  return {
    name: 'replace-vite-preload-script-plugin',
    async renderChunk(code, chunk, options, meta) {
      if (!/content/.test(chunk.fileName)) {
        return null;
      }
      if (!__vitePreload) {
        const chunkName = Object.keys(meta.chunks).find(key => /preload/.test(key));
        const modules = meta.chunks[chunkName].modules;
        __vitePreload = modules[Object.keys(modules)[0]].code;
      }
      return {
        code: __vitePreload + code.split(`\n`).slice(1).join(`\n`),
      };
    },
  };
}

// vite.config.ts
import inlineVitePreloadScript from './utils/plugins/inline-vite-preload';
...,
plugins:[
    ...
    inlineVitePreloadScript()
]

@Jonghakseo appreciate all the work on the boilerplate, it's been really helpful to use. FWIW, I also need to support multiple content scripts as the extension I'm building has different functionality by domain and I'm trying to keep the permissions as minimal as possible to start and the code modular.
Adding a heads up/pointer to this issue in the README may be helpful a short-term solution

@rosendolu this still works like a charm. Thanks!

@all-contributors please add @rosendolu  for code


Date.relative() without "from now"

There is often a need to format time duration, right now I do it as:
duration.millisecondsFromNow().relative().replace("from now", "")

I think there either should be some alternative to .relative() which would give string without "from now", or even better the method of Number, e.g. Number.duration, similar to Number.bytes(), but for time duration.
I probably can even make patch myself if such feature is ok to be accepted.

Are you saying that you still want the units to be dynamic?
...i.e. date.daysAgo() etc. isn't good enough because it has a static unit?

I want it to say "10 seconds" or "10 minutes" depending on what fits better, i.e. similar to Date.relative()

yes, your example is what I mean. If we e.g. have duration in seconds, it can work as:
(120).seconds().duration() -> "2 minutes"

Well, I quite like this idea and it's relatively easy to do... I put something in for this and pushed it... will try it out for a bit. Of course it will have to be tied to the dates package as date based locale formatting is involved. Out of curiosity, what context are you using this in?

I'm using it server-side in my Node.js frontend for Jenkins at http://hosted-ci.com/

ok! this is now a feature of v1.2.3

Great, thanks!


older alpha & beta docs

I've noticed several issues related to incorrect / old documentation simply because people find themselves on outdated docs. (ie v4-alpha)
Google bootstrap 4 documentation:
the top link is for v4-alpha
The old docs have a "Bootstrap 4 Beta is here!" blue banner at the top, but I don't think it's nearly prominent enough..  And it doesn't explicitly state you're viewing old documentation.

Thoughts on making the banner fixed-top & first-and-foremost stating "This documentation is not current"?

Agreed that's lead to issues which don't use our latest documentation

@mdo thoughts?

Done!


CornerRadius Lightweight styling Resources API

Initial PR for corner radius API spec that covers all of the resource additions being added as part of the 524 proposal from the main repo.

Looking at the examples in the spec document - the ToggleSwitch is affected by this CornerRadius.  Will this extend to circular items like the new Slider Thumb, the RadioButtons, ProgressRing?
Also will the padding be adjusted to ensure text is not cut off on totally round edges of controls?

Looking at the examples in the spec document - the ToggleSwitch is affected by this CornerRadius. Will this extend to circular items like the new Slider Thumb, the RadioButtons, ProgressRing?
Also will the padding be adjusted to ensure text is not cut off on totally round edges of controls?

I imagine that padding will need to be adjusted and tested for during implementation, so yes :smile:
@chigy to confirm, but I believe this will extend to the slider thumb (need to add) and is TBD on the RadioButtons and ProgressRing. We've been doing investigations into improving ProgressRing all up, so I'm  hesitant to add it just yet, and I have not seen any changes to RadioButtons as of yet.

Looking at the examples in the spec document - the ToggleSwitch is affected by this CornerRadius. Will this extend to circular items like the new Slider Thumb, the RadioButtons, ProgressRing?
Also will the padding be adjusted to ensure text is not cut off on totally round edges of controls?

I imagine that padding will need to be adjusted and tested for during implementation, so yes 😄
@chigy to confirm, but I believe this will extend to the slider thumb (need to add) and is TBD on the RadioButtons and ProgressRing. We've been doing investigations into improving ProgressRing all up, so I'm hesitant to add it just yet, and I have not seen any changes to RadioButtons as of yet.

@kikisaints , @mdtauk ,
No, this spec does not touch ToggleSwitch, RadioButtons nor ProgressRing. Please refer to the controls listed in #524.
Slider thumb is being made to be more round so it will be touched.

@chigy - okay I'll remove the toggle switch resource then. Are we allowing slider thumb to be easily adjustable, or is it "perma"-rounding?

@chigy - okay I'll remove the toggle switch resource then. Are we allowing slider thumb to be easily adjustable, or is it "perma"-rounding?

If you change the Thumb, you also need to change the containing shape.  Not to do so would lead to problems like this...

@chigy - okay I'll remove the toggle switch resource then. Are we allowing slider thumb to be easily adjustable, or is it "perma"-rounding?

@kikisaints , let's step back a bit to your proposal (not mine, yours).
Some of your goals might go against you removing some of these controls?

Incurring more template debt
Promote poor styling behavior/conduct
Not future-proof/scale-able for anyone but us

As a platform, do you think it is a good or bad idea to expose these knobs (including toggle switch)?
From design point of view, we wouldn't be recommending changing these values for consistency sake, but do you think developers would want to easily modify those? What's the PROs and CONs on exposing these knobs?
On a side note, I was thinking slider thumb value to be exposed since anytime we change something, I'd like for us to be able to easily go back to previous visual (not because we want that happen, because I want that to be a good rule of thumb for exposing knobs). A bit unique on ToggleSwitch case since we are not changing anything here.

@mdtauk Sorry, when I said slider thumb, I was referring to Slider's slider thumb, not ToggleSwitch's. But you're right, if we were to allow the container to be set, we'd want to adjust the thumb relatively to prevent weirdness' that you've shown in your visual.
@chigy I'm in the camp of the more we can allow people the customize our controls' template attributes, the better. However, not including slider thumb in this iteration doesn't mean we can't add it in a future release. My original spec pitch was that I didn't want us to hard-code any values within the template. We're not necessarily incurring more template debt by not touching a control's template, we're just not fixing it either. Fine line, I know.
The pro of allowing app-authors to customize the thumb and container (separately or together) means a more consistent brand on their part, and allows them to work around any corner cases they run into that we may not have been able to preemptively identify.
The con is that allowing a lot more app-author customization can mean Fluent Design inconsistencies across apps. However, a mild mitigation is that we do have generic.xaml which provides all the defaults, so people do have to go out of their way to make it look different.

@chigy I'm in the camp of the more we can allow people the customize our controls' template attributes, the better. However, not including slider thumb in this iteration doesn't mean we can't add it in a future release. My original spec pitch was that I didn't want us to hard-code any values within the template. We're not necessarily incurring more template debt by not touching a control's template, we're just not fixing it either. Fine line, I know.

@kikisaints , thanks for the clarification. What I'm hearing is that if we had infinite resources, we might do them all but perhaps it does not give us ROI at this point and if customers needs the flexibility, we will add these later?

@chigy I'm in the camp of the more we can allow people the customize our controls' template attributes, the better. However, not including slider thumb in this iteration doesn't mean we can't add it in a future release. My original spec pitch was that I didn't want us to hard-code any values within the template. We're not necessarily incurring more template debt by not touching a control's template, we're just not fixing it either. Fine line, I know.

@kikisaints , thanks for the clarification. What I'm hearing is that if we had infinite resources, we might do them all but perhaps it does not give us ROI at this point and if customers needs the flexibility, we will add these later?

At the minimum, you should implement the ThemeResources and Styling properties needed to move the controls to the new designs you decide upon.  So the ControlCornerRadius and OverlayCornerRadius (as well as possibly ControlBorderThickness, ListBorderThickness properties)

@mdtauk - absolutely, I agree and I believe that's the plan. What I'm proposing is, if there are no new designs for certain controls that could have corner radius designs in the future (we just don't know what they are yet), that we hold off on creating resources for them until we do have designs.
Just like I'd looove to have ControlBorderThickness, OverlayOuterBorderThickness, etc. but we don't have any plans/justifications for those yet, so we're holding off. We may want to do the same for some CornerRadiis on certain controls that aren't getting a makeover in this release.


Cache encoded chunks

#97 removed this functionality because of some code simplifications that have been made.

Implemented in a9309ac.


Support for indexes on views with schema binding (SQL Server)

Is your feature request related to a problem? Please describe.
SQL Server support indexes on views created with schema binding, see "Create Indexed Views" documentation.
DBeaver UI does not have an overview of the indexes and does not offer an option to create indexes for the view, as it does in normal tables.
Describe the solution you'd like
A tab named "Indexes" inside of the view properties, as in normal tables: a list of indexes and possibility to add, edit or delete.
Describe alternatives you've considered
Creating indexes with SQL statement like stated in the documentation.
List indexes as SQL statement with EXEC sp_helpindex 'dbo.MyView'.

Thanks for the feature request @daniol


No longer on NPM registry

I was going to use this for a project but discovered it's no longer on NPM :( We should publish it again.

I don't believe this is correct (perhaps npm was having issues):
https://www.npmjs.com/package/dirty-reprojectors

Ah, I re-published it so that explains why it's there now. Forgot to close this ticket. Sorry about that.


ENH: Add default value support

Resolves #79
Tested using a new q2-test-plugin method.

@jakereps hrmm... can't find your last comment about supporting default values of None (maybe it was deleted? or something funky is going on with GH's new code review system). Anyways, I think your plan makes sense to have the interface support required vs optional parameters (it would match how the CLI works too). Are you planning to make those changes in this PR, or another one? I'm happy to merge this one since we don't support None as a default value yet.

@jairideout, Oh I think I deleted it, as I misread at first thinking optionals were now officially supported. I can do a separate PR to get the current type of "optional" to work, since this just allows the ideas of defaults?

Sounds good, thanks @jakereps!


Fix browserify requirement

My browserify (^10.1.3) is apparently too new to work with gulp-watchify, since it won't install. Your readme doesn't state any incompatibilities, so it's probably just a simple mistake.
Here's npm output:
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from gulp-watchify will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from gulp-watchify will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "--save" "gulp-watchify"
npm ERR! node v0.12.2
npm ERR! npm  v2.7.4
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package browserify does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>

+1

Haven't had a chance to test out the new browserify for breaking changes. If it's working for you, a PR would be awesome!

:+1:

:+1:

Yeap, it works! #8

Your package.json states that ^13.0.0 is the requirement, but the package on npm doesn't reflect that - can you please publish an updated version?

published 0.6.0 finally!


Create login / register forms

It is necessary to make a form for login and registration.
examples: https://freefrontend.com/css-login-forms/

i do this faster...


TC synthesis of types with mvars should be optimized

I'm observing traces such as
[Meta.synthInstance] [0.127923s] ✅ CoeFun (?m.9005 →+* ?m.9005[X]) fun x => ?m.9005 → ?m.9005[X]
  [Meta.synthInstance] [0.000018s] new goal CoeFun (?m.9005 →+* ?m.9005[X]) _tc.0
    [Meta.synthInstance.instances]<EMAIL_ADDRESS>  [Meta.synthInstance] [0.000327s] ✅ apply @FunLike.hasCoeToFun to CoeFun (?m.9005 →+* ?m.9005[X]) fun x =>
        (a : ?m.9090) → ?m.9091 a
    [Meta.synthInstance.tryResolve] [0.000238s] ✅ CoeFun (?m.9005 →+* ?m.9005[X]) fun x =>
          (a : ?m.9090) → ?m.9091 a ≟ CoeFun (?m.9005 →+* ?m.9005[X]) fun x => (a : ?m.9090) → ?m.9091 a
    [Meta.synthInstance] [0.000039s] new goal FunLike (?m.9005 →+* ?m.9005[X]) _tc.2 _tc.3
      [Meta.synthInstance.instances]<EMAIL_ADDRESS>@ZeroHomClass.toFunLike, @AddHomClass.toFunLike, @OneHomClass.toFunLike, @MulHomClass.toFunLike, @RelHomClass.toFunLike, @SMulHomClass.toFunLike, @StarHomClass.toFunLike, @NonnegHomClass.toFunLike, @SubadditiveHomClass.toFunLike, @SubmultiplicativeHomClass.toFunLike, @MulLEAddHomClass.toFunLike, @NonarchimedeanHomClass.toFunLike, @TopHomClass.toFunLike, @BotHomClass.toFunLike, @SupHomClass.toFunLike, @InfHomClass.toFunLike, @SupₛHomClass.toFunLike, @InfₛHomClass.toFunLike]
      [Meta.synthInstance] [0.000087s] 💥 CompleteLattice ?m.29914
        [Meta.synthInstance] [0.000032s] new goal CompleteLattice ?m.29914
          [Meta.synthInstance.instances]<EMAIL_ADDRESS>@Order.Frame.toCompleteLattice, @Order.Coframe.toCompleteLattice, Prop.completeLattice, @Pi.completeLattice, @AddCon.instCompleteLatticeCon, @Submodule.completeLattice, @WithBot.WithTop.completeLattice, @fixedPoints.completeLattice, @Subgroup.instCompleteLatticeSubgroup, @Setoid.co
mpleteLattice, @AddSubmonoid.instCompleteLatticeAddSubmonoid, @Subsemiring.instCompleteLatticeSubsemiring, @AddSubgroup.instCompleteLatticeAddSubgroup, @Subring.instCompleteLatticeSubring, @Subsemigroup.instCompleteLatticeSubsemigroup, @AddSubsemigroup.instCompleteLatticeSubsemigroup, @Con.instCompleteLatticeCon, OrderDual.completeLattice, @Algebra.instCompleteLa
tticeSubalgebra, Prod.completeLattice, @OrderHom.instCompleteLatticeOrderHomToPreorderToPartialOrderToCompleteSemilatticeInf, @Submonoid.instCompleteLatticeSubmonoid, @WithTop.WithBot.completeLattice]
        [Meta.synthInstance] [0.000037s] 💥 apply @WithTop.WithBot.completeLattice to CompleteLattice ?m.29914
          [Meta.synthInstance.tryResolve] [0.000020s] 💥 CompleteLattice
                ?m.29914 ≟ CompleteLattice (WithTop (WithBot ?m.29960))
      [Meta.synthInstance] [0.000076s] 💥 CompleteLattice ?m.29914
        [Meta.synthInstance] [0.000029s] new goal CompleteLattice ?m.29914
          [Meta.synthInstance.instances]<EMAIL_ADDRESS>@Order.Frame.toCompleteLattice, @Order.Coframe.toCompleteLattice, Prop.completeLattice, @Pi.completeLattice, @AddCon.instCompleteLatticeCon, @Submodule.completeLattice, @WithBot.WithTop.completeLattice, @fixedPoints.completeLattice, @Subgroup.instCompleteLatticeSubgroup, @Setoid.co
mpleteLattice, @AddSubmonoid.instCompleteLatticeAddSubmonoid, @Subsemiring.instCompleteLatticeSubsemiring, @AddSubgroup.instCompleteLatticeAddSubgroup, @Subring.instCompleteLatticeSubring, @Subsemigroup.instCompleteLatticeSubsemigroup, @AddSubsemigroup.instCompleteLatticeSubsemigroup, @Con.instCompleteLatticeCon, OrderDual.completeLattice, @Algebra.instCompleteLa
tticeSubalgebra, Prod.completeLattice, @OrderHom.instCompleteLatticeOrderHomToPreorderToPartialOrderToCompleteSemilatticeInf, @Submonoid.instCompleteLatticeSubmonoid, @WithTop.WithBot.completeLattice]
        [Meta.synthInstance] [0.000031s] 💥 apply @WithTop.WithBot.completeLattice to CompleteLattice ?m.29914
          [Meta.synthInstance.tryResolve] [0.000014s] 💥 CompleteLattice
                ?m.29914 ≟ CompleteLattice (WithTop (WithBot ?m.29992))
      [Meta.synthInstance] [0.000081s] 💥 CompleteLattice ?m.29915
        [Meta.synthInstance] [0.000026s] new goal CompleteLattice ?m.29915
          [Meta.synthInstance.instances]<EMAIL_ADDRESS>@Order.Frame.toCompleteLattice, @Order.Coframe.toCompleteLattice, Prop.completeLattice, @Pi.completeLattice, @AddCon.instCompleteLatticeCon, @Submodule.completeLattice, @WithBot.WithTop.completeLattice, @fixedPoints.completeLattice, @Subgroup.instCompleteLatticeSubgroup, @Setoid.co
mpleteLattice, @AddSubmonoid.instCompleteLatticeAddSubmonoid, @Subsemiring.instCompleteLatticeSubsemiring, @AddSubgroup.instCompleteLatticeAddSubgroup, @Subring.instCompleteLatticeSubring, @Subsemigroup.instCompleteLatticeSubsemigroup, @AddSubsemigroup.instCompleteLatticeSubsemigroup, @Con.instCompleteLatticeCon, OrderDual.completeLattice, @Algebra.instCompleteLa
tticeSubalgebra, Prod.completeLattice, @OrderHom.instCompleteLatticeOrderHomToPreorderToPartialOrderToCompleteSemilatticeInf, @Submonoid.instCompleteLatticeSubmonoid, @WithTop.WithBot.completeLattice]
        [Meta.synthInstance] [0.000038s] 💥 apply @WithTop.WithBot.completeLattice to CompleteLattice ?m.29915
          [Meta.synthInstance.tryResolve] [0.000021s] 💥 CompleteLattice
                ?m.29915 ≟ CompleteLattice (WithTop (WithBot ?m.30023))
      [Meta.synthInstance] [0.000073s] 💥 CompleteLattice ?m.29915
        [Meta.synthInstance] [0.000027s] new goal CompleteLattice ?m.29915
          [Meta.synthInstance.instances]<EMAIL_ADDRESS>@Order.Frame.toCompleteLattice, @Order.Coframe.toCompleteLattice, Prop.completeLattice, @Pi.completeLattice, @AddCon.instCompleteLatticeCon, @Submodule.completeLattice, @WithBot.WithTop.completeLattice, @fixedPoints.completeLattice, @Subgroup.instCompleteLatticeSubgroup, @Setoid.co
mpleteLattice, @AddSubmonoid.instCompleteLatticeAddSubmonoid, @Subsemiring.instCompleteLatticeSubsemiring, @AddSubgroup.instCompleteLatticeAddSubgroup, @Subring.instCompleteLatticeSubring, @Subsemigroup.instCompleteLatticeSubsemigroup, @AddSubsemigroup.instCompleteLatticeSubsemigroup, @Con.instCompleteLatticeCon, OrderDual.completeLattice, @Algebra.instCompleteLa
tticeSubalgebra, Prod.completeLattice, @OrderHom.instCompleteLatticeOrderHomToPreorderToPartialOrderToCompleteSemilatticeInf, @Submonoid.instCompleteLatticeSubmonoid, @WithTop.WithBot.completeLattice]
        [Meta.synthInstance] [0.000030s] 💥 apply @WithTop.WithBot.completeLattice to CompleteLattice ?m.29915
          [Meta.synthInstance.tryResolve] [0.000014s] 💥 CompleteLattice
                ?m.29915 ≟ CompleteLattice (WithTop (WithBot ?m.30055))
      ... <many more bombs>

I'm assuming the fact that we try to apply instances that we should know will fail is due to
https://github.com/leanprover/lean4/blob/9bc6fa1c6ef2ad7056adb113350c955e5d516bc5/src/Lean/Meta/DiscrTree.lean#L425-L439
It should probably be possible to have the discrimination tree return a flag expressing that some instances were omitted because of read-only mvars and then throw the stuck exception when no other instance applies instead of returning and trying them all.

In particular, I'm observing 5s spent just on synthesizing CoeFun in Mathlib.Data.Polynomial.FieldDivision, currently the slowest file with 99s.

You're talking about the nested CompleteLattice ?m queries here, right?

It should probably be possible to have the discrimination tree return a flag expressing that some instances were omitted because of read-only mvars and then throw the stuck exception when no other instance applies instead of returning and trying them all.

This breaks monotonicity a bit, because it changes the order instances are tried in (definitely stuck instances are tried last in the proposal).

no other instance applies

I don't think we can easily determine that with the current tabled resolution algorithm.  It might be that we can unify some of the instances, but not synthesize their subgoals.  (But we might be able to solve all of the subgoals of the stuck instance.)

I think it would be easier to provide high-priority instances for function coercions of morphisms, this would also avoid the nested TC synthesis.


Clock: synchronize tests with canonical ones

Addresses #184
Quite similar to PR in xecmascript#218.

Thanks @rchavarria !  You are the energizer bunny of xjavascript!

LOL
Very fun!


Scoper restart

Provided scoperRestart() utility function allowing to restart scoper at any moment.
This may be useful if some scoped styles were appended to the DOM after DOMContentLoaded.
This case may happen very frequently nowadays, particularly on Single Page Applications.
Also, I renamed init() and process() function to scoperInit() and scoperProcess() as init and process may be usual names for global functions

Hey @fcamblor, thanks for the PR, love the additions you've made. Everything looks good to me, so I'll merge and bump the version to 1.1.0!


Diff expression job is not run with Rockhopper

I ran an RNA-seq job this morning with the Rockhopper option.
RNA-seq part ran fine and created gene matrix (gmx) file.
However, differential expression job results were not part of the output.
Please make sure diff exp job is ran as part of rna-seq when Rockhopper is selected.
-Maulik

When initially developing the execution of diff exp app we hadn't perfected the running of other apps from within apps yet. It was suggested we "simulate" the running of another app by invoking the diff exp back end script and creating a "fake" job object.
Now that he has gotten the running apps within apps under control, it should be a dev task to rip the diff exp running back out of prok_tuxedo and invoke the p3-diffexp from the top level perl wrapper script so that in both cases....rockhopper & tuxedo the same, regular diffexp will be called.
As it stands right now, rockhopper is still in the old mode of having to invoke diffexp using the gmx file afterward.

We removed RockHopper Recipe from the submission form, so I guess this is no longer an issue.


Update HRO2 demo to latest packages and use notifications

Is your feature request related to a problem? Please describe.
Current version doesn't exploit latest latency reductions in server's notification handling
Describe the solution you'd like
Update to latest packages and use notifications

Migrated to notifications! using forText


#Change Site Title, Index Title and Site Title

Add some changes to look your site more professional. I hope you like it.

Umm ... I don't remember adding an admin section to this app. Can you maybe attach and image for me to see how the new changes look after execution?

[

](url)
Hey, I have attached it for you. Please take a look and merge it.

Seems fair. Merging.


Fix resolution process

This PR fixes an issue in the resolution process when there are more than 1 level of extends.
Note 1: The lineage computation is still incomplete and will be fixed in the next PR (see https://github.com/open-telemetry/weaver/issues/52). This is not blocking.
Note 2: The current resolution process is iterative and far from optimal but still pretty fast with the current semconv registry. If speed becomes an issue, a graph could be construct from the extends and ref clauses, and a DFS resolution could be used to optimize the entire resolution process.

It's interesting how a small fix ripples through all the test code. I think maybe I need to do a better job focusing on the markdown or we need to start pulling in more of the existing markdown as our tests....
IN any case, looks good! Thanks for fixing this!

Yes looks like using the existing markdown files is our best option at this point.


feat(nodejs): Add Node.js Implementation of Apache RocketMQ Client

Brief Description
A Node.js implementation RocketMQ client follow the Java Code base.
How Did You Test This Change?

I'm trying to run the whole unittest on github action.

Nice work!

Great contribution, thanks @fengmk2.

Codecov Report

Merging #602 (ddd53cd) into master (d450648) will increase coverage by 8.96%.
Report is 1 commits behind head on master.
The diff coverage is 86.66%.

@@             Coverage Diff              @@
##             master     #602      +/-   ##
============================================
+ Coverage     46.68%   55.64%   +8.96%
  Complexity      667      667
============================================
  Files           207      259      +52
  Lines         11989    15454    +3465
  Branches       3405     3731     +326
============================================
+ Hits           5597     8600    +3003
- Misses         6146     6608     +462
  Partials        246      246

Flag
Coverage Δ

nodejs
86.66% <86.66%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

nodejs/src/client/TelemetrySession.ts
68.64% <68.64%> (ø)

nodejs/src/client/RpcClient.ts
69.38% <69.38%> (ø)

nodejs/src/producer/Producer.ts
72.31% <72.31%> (ø)

nodejs/src/client/RpcClientManager.ts
74.56% <74.56%> (ø)

nodejs/src/producer/Transaction.ts
78.57% <78.57%> (ø)

nodejs/src/producer/PublishingLoadBalancer.ts
80.00% <80.00%> (ø)

nodejs/src/retry/ExponentialBackoffRetryPolicy.ts
80.26% <80.26%> (ø)

nodejs/src/util/index.ts
85.54% <85.54%> (ø)

nodejs/src/client/BaseClient.ts
85.86% <85.86%> (ø)

nodejs/src/exception/StatusChecker.ts
87.23% <87.23%> (ø)

... and 42 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Waveshare 3in7 errors

I think the Waveshare 3in7 drivers are non-standard . . . and it's causing the movie not to play.  The display isn't being cleared at all.
Describe the problem

pi@GeneralPie:~/Projects/SlowMovie $ python3 slowmovie.py -o DEBUG
Picking which video to play...
...trying the --file argument...
...trying the video in the nowPlaying file...
...picked '/home/pi/Projects/SlowMovie/Videos/test.mp4'!
Update interval: 120
Frame increment: 4
Playing 'test.mp4'
Video info: 50 frames, 24.125fps, duration: 00:00:02
This video will take 25.0 minute(s) to play.
Traceback (most recent call last):
  File "slowmovie.py", line 322, in <module>
    epd.init()
TypeError: init() missing 1 required positional argument: 'mode'

I changed the line to match the waveshare demo script : epd.init(0)
Ran it again
pi@GeneralPie:~/Projects/SlowMovie $ python3 slowmovie.py -o DEBUG
Picking which video to play...
...trying the --file argument...
...trying the video in the nowPlaying file...
...picked '/home/pi/Projects/SlowMovie/Videos/test.mp4'!
Update interval: 120
Frame increment: 4
Playing 'test.mp4'
Video info: 50 frames, 24.125fps, duration: 00:00:02
This video will take 25.0 minute(s) to play.
Displaying frame 0 of test.mp4 (0.0%)
Traceback (most recent call last):
  File "slowmovie.py", line 342, in <module>
    epd.display(epd.getbuffer(pil_im))
AttributeError: 'EPD' object has no attribute 'display'

At this point I don't know what to tweak or where to look for what to tweak.
This is the second project that didn't run out of the box as expected.
Platform Information

Display: https://www.waveshare.com/wiki/3.7inch_e-Paper_HAT
Raspberry Pi Zero W Rev 1.1
Linux version 5.10.17+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1403 Mon Feb 22 11:26:13 GMT 2021
Python 2.7.16
Python 3.7.3

You are correct - the 3in7 display has some different methods than the standard devices. It takes some additional parameters as part of init() and has some different display methods as well. We're currently working on a solution to handle non-standard displays - hopefully ready soon.

Rock on!
Thanks

This is the second project that didn't run out of the box as expected.

Seems like they never do

@ZubaZ21 - you should be able to follow the instructions and use your 3.7 in display now.  Lookup the display name to use in this table: https://github.com/robweber/omni-epd#displays-implemented

I love the idea of abstracting this.  Very cool.
Pulled it down and ran the test util.
It threw an error.
File
"/usr/local/lib/python3.7/dist-packages/omni_epd/displays/waveshare_display.py",
line 251, in prepare
self._device.init()
TypeError: init() missing 1 required positional argument: 'mode'
I added a 0 so it became self._device.init(0) as that is what the waveshare
driver requested.
Fired it off again and got the following.
pi@GeneralPie:~ $ omni-epd-test -e waveshare_epd.epd3in7
Loaded waveshare_epd.epd3in7 with width 280 and height 480
Drawing rectangle of width 210.0 and height 360.0
Drawing rectangle of width 105.0 and height 180.0
Drawing rectangle of width 26.25 and height 45.0
Traceback (most recent call last):
File "/usr/local/bin/omni-epd-test", line 10, in
sys.exit(main())
File "/usr/local/lib/python3.7/dist-packages/omni_epd/test_utility.py",
line 127, in main
test.draw()
File "/usr/local/lib/python3.7/dist-packages/omni_epd/test_utility.py",
line 85, in draw
self.__draw_on_display(im)
File "/usr/local/lib/python3.7/dist-packages/omni_epd/test_utility.py",
line 67, in __draw_on_display
self.epd.display(image)
File "/usr/local/lib/python3.7/dist-packages/omni_epd/virtualepd.py",
line 202, in display
self._display(self.__applyConfig(image))
File
"/usr/local/lib/python3.7/dist-packages/omni_epd/displays/waveshare_display.py",
line 263, in _display
self._device.display(self._device.getbuffer(image))
AttributeError: 'EPD' object has no attribute 'display'
Let me know if you need further testing.
Aaron
On Mon, May 3, 2021 at 3:34 PM Rob @.***> wrote:

@ZubaZ21 https://github.com/ZubaZ21 - you should be able to follow the
instructions and use your 3.7 in display now. Lookup the display name to
use in this table:
https://github.com/robweber/omni-epd#displays-implemented
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TomWhitwell/SlowMovie/issues/68#issuecomment-831483723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATTPCDNQAMQBIEXT5N7UB4TTL33ERANCNFSM43M6NUKQ
.

Thanks for testing this - I'm going to move this over to the omni-epd repo since it's more of an issue with that.


Refs #35003 -- Corrected margins in admin for LTR languages.

Now to find what regresses from this change.

@knyghty Thanks :+1:


Cross Browser problems with checkboxes and radios.

Hi, there seem to be some problems with checkboxes and radios on your demo page  These impact different browsers in different ways.
Chrome 61 Mac - Radio buttons
Selecting 'Yes' is valid, selecting 'No' is invalid
Safari 11 Mac - Radio buttons
'Yes' and 'No' are both invalid
Firefox 55. - Radio buttons
'Yes' and 'No' are both invalid
Chrome 61 - Checkboxes
Only "Wolverine" is valid
Safari 11 - Checkboxes
No options are valid
Firefox 55 - Checkboxes
No options are valid

Hmm... I'm seeing this too. I'll look into this, thanks!

Sorry for the lengthy delay in fixing this. It appears to have been causing by a polyfill conflict, and should be resolved with v1.1.3.
Looks like it may have been caused by a conflict with this: https://github.com/cferdinandi/validate/issues/27


incorrect documentation in _SliceHelper

The outputs shown for several of the examples in the _SliceHelper docstring are incorrect (based on some previous examples?).
See, for example, this line: https://github.com/tensorflow/tensorflow/blob/359d6f9716c0bb9bd8201ce600da98b0481a8049/tensorflow/python/ops/array_ops.py#L412

The first two section seem correct. The last two seem two be based on the output of the second example.


Remove button text is defaulting to "Remove"

Are you requesting a feature, reporting a bug or asking a question?
bug/question
What is the current behavior?
In a matrix dynamic/dynamic panels, when removebuttontext property is set to empty string "", it is defaulting  to Remove
What is the expected behavior?
when removebuttontext property is set to empty string "", the button should have no text
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
your_code_here

Specify your

browser: chrome
browser version:
surveyjs platform (angular or react or jquery or knockout or vue): angular 5
surveyjs version: 1.0.30

Tried the below snippet, but doesn't work.
    surveyModel.onMatrixRowAdded.add((survey, options) => {       let str = "";       options.question.removeRowText = str;     })

@ashygk You may use a white space. Adding an empty string, means that you want to have the default value.
Thank you,
Andrew

We are displaying an image (trash can) instead of remove button.
If I use a white space, there is going to be some space after the trash can which is visible when clicked because of border its border.

@ashygk You may set empty string to "removeRow" in the localization as well. In this case, by default all remove button will have empty string. I guess, this is what you want.
Please read this topic to see how to change the default strings.
Thank you,
Andrew

Tried the above, setting my locale to en and added default property to "" and en property to "" for remove text. It is still taking the default property and Remove is being displayed as remove text. Same result if the default property is removed and just kept en: ""


Purge questionnaire task only runs on deploy

We should have this as a delayed job

We will review this later - but will not be fixed at this stage.


SDK style projects with WPF do not import nuget props and targets

WPF xaml compilation uses a temporary project with a different name. This breaks importing of props from https://github.com/Microsoft/msbuild/blob/8e015cc049b5f3f9cbd9e10ee30ae86998d934d5/src/Tasks/Microsoft.Common.props#L66 (and the equivalent targets). The end result is WPF compilation fails due to the temporary project not having nuget restore information.

Same issue: https://github.com/NuGet/Home/issues/5894


Couple Open311 repository to ServiceRequest and Service repositories

Currently, the Open 311 repositories for Service and Service Request are decoupled from the "main" Service and ServiceRequest repositories. Given they have similar logic, it might make sense to have the Open311 repositories depend on their "main" equivalents, rather than having their own logic and querying the database directly.
Not an urgent refactor but possibly good in the scenarios that the datastore for Open311, Service, or Service Repository is pluggable and outside the core system.
cc @amirozer

Basically, we need to remove Open311 repositories, and just have the data transform methods (open311/helpers).
We also need to remove a bunch of virtual fields that have been left but are not really in use since 0.0.15-alpha

@amirozer is your preferred approach here to:
i) remove the Open311 repositories
ii) in the request handlers for open311 endpoints, directly call there the service and request repositories, and then return the responses via the transform functions in open311/helpers
it is a simple change and I'll pick it up at some point (not now)

I finished this off in https://github.com/govflow/govflow/commit/2944721464915e3e2e962227ec173c17b0804c84


Optimize integration mobile layout

I'd like to remove huge padding around integration cards on mobile:

zpl://screen?sid=5cda7dad83b4fc5dee7e2369&pid=5acb41c5487a27ab9f0560a1


block: FAQ

Content structure not definitively determined

Volvo's Specifications block looks very similar.
https://github.com/hlxsites/vg-volvotrucks-us/tree/main/blocks/specifications


Test gatsby payload plugin to see if it works well

https://github.com/thompsonsj/gatbsy-source-payload-cms

It doesn't have the ability to handle the data load. Too many requests made to the server (paging), difficult to beat a direct connection to mongoDB ...


Add NewInstanceServiceLoaderTest

Pull Request Test Coverage Report for Build 5664

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 69.807%

Totals

Change from base Build 5663:
0.1%

Covered Lines:
8476

Relevant Lines:
12142

💛  - Coveralls


MetaData support for per app declaration

Is your feature request related to a problem? Please describe.
In CIS, we group multiple ingress, routes and configMap resources into a single AS3 declaration and post it to the BIGIP. But we do not have any mappings that which K8s resources are posted on which tenant/app. As CIS is a stateless application it's not possible for CIS to keep the state that which AS3 tenant/app declaration belongs to which K8s resource.
Describe the solution you'd like
We would like to have a metadata support implemented in per app based declaration where we can set multiple key-value  pairs in metadata.
Metadata may look like this:
metadata: {"foo-ingress": "ingress", "bar-vs-cr": "virtualServer", "echo-transport-server": "transportServer"}
Describe alternatives you've considered
Currently there is no alternatives we have. We store the k8s resource and tenant mapping in memory, but there is no mapping of k8s resource to AS3 application.

Thanks for reaching out. Created AUTOTOOL-3745 and added to internal product backlog.

@vklohiya thanks for creating this. Do we still need the metadata if CIS could POST to

example
POST https://<IP>/mgmt/shared/appsvcs/declare/ocp/applications
{
    "App_1": {
        "class": "Application",
        "Service_2":    {
            "class": "Service_HTTP",
            "virtualAddresses": ["<IP_ADDRESS>"],
            "virtualPort": 80,
            "pool": "Pool_1"
        }    ,
        "Pool_1": {
            "class": "Pool",
            "members": [
                {
                    "servicePort": 80,
                    "serverAddresses": ["<IP_ADDRESS>", "<IP_ADDRESS>"]
                }
            ]
        }
    }
}

Not sure if we still need metadata

Yes @mdditt2000 , it would be required as multiple routes/virtual-server crd can be mapped to single AS3 app.


tests: add some debug output

This can be reverted if we think it is useless,
but I have been asking myself many times why
some dependents are being tested.
This should also help debug an issue we have right now with
homebrew-core.

We can try it.


Support tags injection via JAEGER_TAGS environment variable

For the sake of consistency, it would be useful if tags could be aggregated via JAEGER_TAGS environment variable like in the Java client.

Thanks!


Minor grammar correction

Build failure isn't related.
I'll merge this, but we should probably add something along the lines of "you can get started by looking at the issues tagged trivial on GitHub and trying to fix one of those".


Wildcard/Regex support in access control

For example, the documentation shows an example access control situation that lists valid values of the required attribute:
"cn" : [ "java.util.HashSet", [ "admin, Admin, TheAdmin" ] ]

Could include support for a wildcard feature or full-blown regex such as:
"cn" : [ "java.util.HashSet", [ ".*[Aa]dmin.*" ] ]

Not that you'd trust your admin access control to such a filter but as an example of possible capability.

What we probably could do best is to consider every entry in that set to be a regex pattern. If the pattern is valid, use it to match against what's needed. otherwise, fall back onto the current behavior. That work for you?

Related to https://github.com/Jasig/cas/issues/1417

See https://github.com/Jasig/cas/issues/1421


protobuff dependency

Hey there, firstly awesome plugin thank you for your efforts.
As you noted about brittle dependencies in go am currently investigating a
Error: loading generator plugins: plugin /root/.config/kustomize/plugin/kustomize-sops/v1/sopssecret/SopsSecret fails to load: plugin.Open("/root/.config/kustomize/plugin/kustomize-sops/v1/sopssecret/SopsSecret"): plugin was built with a different version of package github.com/golang/protobuf/proto
make: *** [generate] Error 1

error in the latest version of kustomize i suspect, but may affect this implementation

You can pin it in the makefile by sha as a workaround.
You can also consider using https://github.com/Agilicus/kustomize-plugins/tree/master/agilicus/v1 which achieve the same and more goals, without the brittle use of go.

both are great tips.. ill go with your recommended way :) thanks

i think the issue is being caused by sops protobuff btw..
kustomize uses golang/protobuf 1.3.1 but sops 1.3.2

sorry 1 last thing..
https://github.com/Agilicus/kustomize-plugins/tree/master/agilicus/v1/secrettransformer is what you meant?

try
https://github.com/Agilicus/kustomize-plugins/tree/master/agilicus/v1/secretstringdatatransformer
or
https://github.com/Agilicus/kustomize-plugins/tree/master/agilicus/v1/secretgenerator

yep just noticing hte docs are a little thin in areas will be happy to create a PR with updates just have to understand how to use the aspects

specifically https://github.com/Agilicus/kustomize-plugins/tree/master/agilicus/v1/secretgenerator seems the closest but am i reading this right.. its just a python file iinteresting this opens possiblities..

ah ok reading code all good just the docs are thin.. ill update docs

So, just an update for you and a question

what will the status of this project be now that sops has been removed from kustomize?
I've forked and fixed the references and will have to maintain for the moment. Tho do you have an idea of what the future holds? I imagine "plugins" as per that which you recommended? in which case ill get some time scheduled to contribute?

sops was never in kustomize.
early on in kustomize it added exec plugins. Then all of a sudden they removed them, and added go plugins. So i moved my exect plugin over to go. But it was very very brittle, i'm not sure how anyone can use go plugins with any code.
then kustomize re-added exec plugins.
All our current dev is on the exec plugins. I still use the kustomize-sops (as as go plugin) in a few spots, but might eventually drop it.

Ok this is fantastic news (as you have, I too have a growing irritation
with a number of aspects of go-lang for all its good).
Would you mind if I synced the secretsGenerator so that its a little more
like the the sops-plugin? maybe as a v2? (subjectively it feels cleaner?)
Ill try get some time scheduled in the next sprint for it.
On Fri, Sep 20, 2019 at 4:37 PM Don Bowman<EMAIL_ADDRESS>wrote:

sops was never in kustomize.
early on in kustomize it added exec plugins. Then all of a sudden they
removed them, and added go plugins. So i moved my exect plugin over to
go. But it was very very brittle, i'm not sure how anyone can use go
plugins with any code.
then kustomize re-added exec plugins.
All our current dev is on the exec plugins. I still use the kustomize-sops
(as as go plugin) in a few spots, but might eventually drop it.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Agilicus/kustomize-sops/issues/6?email_source=notifications&email_token=AADA6MVHUNCZVOENANP7AFLQKTNZNA5CNFSM4IYUP57KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7G4RBI#issuecomment-533579909,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADA6MXMAYC6X6HWZHZOTIDQKTNZNANCNFSM4IYUP57A
.


Sidecar does not work without first enabling iGPU in BIOS

Not necessarily a bug but in the documentation as it stands, people are encouraged to switch off iGPU, however as this machine is using iMac19,1 it expects iGPU to provide Sidecar (iPad as extra screen when connected via cable - in my case a Thunderbolt Port to the USB C of the Motherboard)
I have not upgraded to Big Sur yet so iGPU being Disabled may impact Sidecar in the same manner.
Solution: Boot into BIOS, change IGPU (Under Peripherals tab) and set explicitly to ENABLED
Currently using Z390DESI.F9i

Good point. I’ll give this a try myself and change the docs. Thank you

Verified that it works with no changes to the EFI. Have not been able to verify Sidecar works on Big Sur because I don't have an iPad. Let me know if it works once you upgrade, @QueercoreTrash
I also added a BIOS guide and mentioned the fix you suggested there.
Thanks for the input!


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2023-12-03)
Features

add tokenStorage to define where to keep the token (5c8170a)
add use-sync-external-store shim (5c8170a)
force loading to eager if placeholder used (5c8170a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mddanish00/react-utterances-client/releases/tag/v1.1.0 :sunflower:


Include file path in traceback of scan failures in pipeline log

This is follow up from https://github.com/nexB/scancode.io/issues/1121

See https://github.com/nexB/scancode.io/issues/1121#issuecomment-2007624322


Fixed #6727 - patch_cache_control now properly patches an empty string

Buildbot, test this please.

merged in 1f29164ced01bde92c72d20d67bc453484a4f078, thanks!


Investigate a mode in msbuild that reduces the actions during build

For the Live Unit Test scenario, we've been requested to provide a mode where we skip all checks and trust the caller to provider the information as to what has changed (ie trust VS) and treat that information as that output of the up-to-date check.

Need to follow up with LUT team to get clarification on the ask and the data they have that indicates the up to date checks are slow.

From conversations, some options here for a LUT mode would exclude PDB generation, potentially turn off some analyzers, diable some artifact generation (nuget/vsix/xml docs that wouldn't be used in test).  Still in discussions on what this looks like.

This is tracked separately and driven by the LUT team.


Publish RSVPs to twitter

I would like my RSVPs to POSSE to twitter. I guess it is not working now because RSVPs are treated specially for event sites, but it doesn't need special treatment - just take the content and do it the same as a note.

sure! makes sense, will do.


bug: duplicate tags

Bug Report
Installation Method
Docker
Environment

Open WebUI Version: v0.3.12
Operating System: Gentoo Linux
Browser (if applicable): Firefox

Confirmation:

[X] I have read and followed all the instructions provided in the README.md.
[X] I am on the latest version of both Open WebUI and Ollama.
[X] I have included the browser console logs.
[X] I have included the Docker container logs.
[X] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
When adding a tag to a chat, if that tag already exists, there's a large chance that it will be duplicated both in the sidebar tag list, and in the list of tags on the chat itself.
Actual Behavior:
One tag = one tag. Do not display duplicates of the same tags.
Description
Bug Summary:
When using a tag that already exists, the UI will duplicate it. However, there seems to only be a single tag stored on the chat in the backend.
Reproduction Details
Steps to Reproduce:
Tag multiple chats with the same tag. I think there might be some more factors at play here, because sometimes the duplication is 2x, or 3x, or even 4x. It doesn't necessarily seem related to the number of chats with the same tag.
Logs and Screenshots
Screenshots/Screen Recordings (if applicable):

I'm unable to reproduce this issue, if someone could describe a step by step method to reproduce I'd greatly appreciate it!

Here is a bit more info:

It looks like my assumption about the backend was wrong; these tags are returned with different IDs.
I wonder if this is related to a DB migration that happened at some point along the way. This only started showing up after one of the recent releases (unsure of which one, exactly). They show up as duplicates in the database too.
So it seems like duplicate tags in DB + UI that expects unique tag names = this problem.

Also, I've got a tag table and a chatidtag table. Which one is used? Are both used? o_O

I was able to "fix" this by deleting all but one of the duplicated tags. The duplicated tags can be found by a query like this (sqlite):
select name, count(name), group_concat(id) as duplicated_ids from tag group by user_id, name having count(name) > 1;

This does not, however, help reproduce it. My money is still on a DB migration.

Should be addressed with cf24a65caa6b5602a73dbb6cc83dfbfb976286ef in dev.

This still seems to be an issue with the latest 3.33 Duplicate chats start popping up in the sidebar.  It seems to be triggered by using the search adding a couple words in it then just backspace over the last word entered. The sidebar pulls in what is searched. And once you clear out the search field, duplicates seem to be in the sidebar of some of the chats.  It seems like DB index for the chat history or sidebar values are getting pulled in and contaminating the actually master index.
A possible future fix would be to add two new fields to the DB where chats would have a date & time stamp as well as a Unique sequential record number. Then add a DB integrity verifier that would create an integrity index DB sorted by date of chat as well as record# then build a new cleanup Index DB that would filter out the duplicates.  Also, it may be the bulk export or import of chats stage contaminating also. But seems to show up just after using the search more so just after the bulk import of chats which seems to leave out some of the backed up chats and pop up just after using the search but with duplicates.
I am going to go see if it repeats the problem on 3.34 which just come out today.

@AndroidHemroid would appreciate your help here, PR welcome!


Using with Rainbow Parentheses?

Hi is there any way to make this plug in to work with Rainbow Parentheses (that plugin basically colors different pairs of parentheses differently. It's admittedly more useful in lisps, but still nice for JS)? Right now, YAJS highlighting seems to override it.

I'm using the plugin from @luochen1990 which is more up-to date than the one from @kien. It works nice but the colors are still "a bit" broken. It seems like all parens, brackets and braces are coloured a rightish way except for function-call parenthesis
Those all work:
{{{}}}
[[[]]]
((()))
function(((()))) {{{}}}
if ((())) {{{}}}

Function definitions and object literals are actually special. I'd say it is better if they are rainbow'ed completely but the current behaviour is kinda reasonable:
var obj = {               // those will have
    method: function() {  // the same color
    }
}

Completely broken however are function calls (as opposed to definitions):
callAFunction((())) // here all parens are black

The last one is important to fix imo. I find it reasonable to highlight the parens that enclose the parameters of a function call in a special way but the highlighting of the parens in deeper levels should not be touched (unless they come from another function call).

@Fryie Sorry I don't think yajs can work well with Rainbow Parentheses. Because I have full control on almost every nesting scopes. Which causes regexp rule of rainbow parentheses not working.

@othree yajs does actually work kinda well with rainbow-parenthesis (at least with the plugin I am using). Its just that for object literals and function calls you should only take control over the outermost pair of parens/braces in aCall((())) or var object = {{{}}}. Isn't this possible? If yes, compatibility would be fine.

@ohcibi thanks, I'll try the improved version out.
Thanks to you two for looking into this :)


Document stopping actors.

This PR includes two pieces of information that @Andarist explained to me in issue #1403, actions.pure() and actions.stop().
However, after attempting to document (and reading the code in interpreter.ts for 4.X), I have additional questions that imply to me that there may be additional unaddressed issues here.

Just sending xstate.stop to a StateNode does not seem to be complete to me as it doesn't seem like it is recursive. The receiver of xstate.stop may also be a machine with children which would also need to be stopped. The event does not appear to be propagated. Code.
It seems like you should still call .stop() on the interpreter as well. Code.

Assuming that my hypotheses are correct, maybe Interpreter#stop should also send (from leaf to root?) xstate.stop?

Oh, I've missed your questions in the PR comment itself. Let's get to them:

Just sending xstate.stop to a StateNode does not seem to be complete to me as it doesn't seem like it is recursive. The receiver of xstate.stop may also be a machine with children which would also need to be stopped. The event does not appear to be propagated. Code.

StateNode is a "pure" representation of a machine, it's stateless but the information in it holds a list (or a map, don't remember) of things like activities and children`, those shouldn't be "live" things though.
OTOH the Interpreter is this "live" thing that manages the pure machine that it references. It receives actions that should be executed (apart from assigns, those are completely evaluated & resolved within StateNode). In here it stops a particular child upon receiving a stop action:
https://github.com/davidkpiano/xstate/blob/78e998674b8ac8cbcf926f43b2588787b5631953/packages/core/src/interpreter.ts#L886
and stop should recursively stop all "nested" machines as well:
https://github.com/davidkpiano/xstate/blob/78e998674b8ac8cbcf926f43b2588787b5631953/packages/core/src/interpreter.ts#L492-L497
This should also answer the second question as those were highly interconnected.

How do y'all prefer your modifications to PRs?
A. New commits.
B. Update-in-place (continuously squash to a single commit).
C. Other
And prepping for landing:
A. Squash
B. Commit History
C. Other
And landing strategy:
A. Merge
B. Rebase
C. Other
And test strategy:
A. Failing test in a separate commit first. (red => green)
B. Tests pass at every commit.
C. Other
(Can also drop this into CONTRIBUTING.md if you'd like.)

Sorry for the delay - was quite busy lately with other stuff. I haven't forgotten and will get back to you this week.

How do y'all prefer your modifications to PRs?

IMHO - whatever works best for you. Ideally, we'd like to receive often contributions from the community, and requiring a particular git-flow makes it harder to achieve that, not everyone is well-versed with more advanced git techniques etc. As to the landing strategy - this one can actually be quite easily chosen from the GitHub UI so it's not much of a concern either way.

@nathanhammond Sorry for the delay in reviewing this! @Andarist and I discussed the need for a dynamic stop(ctx => ctx.child) and how it could be useful (and simpler) with regard to this, so I'll make those changes and then re-review this PR with the necessary changes.
Thanks so much for doing this!

Now that #1577 is in, we can simplify these docs:

Stopping Spawned Machines
To stop a spawned machine, use the actions.stop(...) action creator and reference the spawned machine as an expression in the first argument:
on: {
  STOP_SPAWNED: {
    actions: actions.stop(context => context.someSpawnedMachine)
  }
}

The docs have moved to https://github.com/statelyai/docs and we will be addressing suggestions & improvements there.


(Brand) Peapods Milestone 7

[x] refactor tabs to have the same experience as twitter
[x] PodCard

This is done and looks good.


Fixed #135: DM/Add subscription expiration policy to Pub/Sub template

https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/issues/135
Added and fixed tests

/gcbrun