Error creating /run/user/0/containers on podman login

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
Description

On a fresh Fedora 27 Cloud Base image, I ran dnf update && dnf install podman buildah, then ran this:
[fedora@buildah-fresh ~]$ sudo su -
[root@buildah-fresh ~]# podman login quay.io
Username: rturk
Password:
error creating directory "/run/user/0/containers": mkdir /run/user/0/containers: no such file or directory
[root@buildah-fresh ~]#

Describe the results you expected:
I expected to successfully log in, but was not able to.
Additional information you deem important (e.g. issue happens only occasionally):
If I run mkdir -p /run/user/0/containers, I am able to successfully log in subsequently.
[root@buildah-fresh ~]# mkdir -p /run/user/0/containers
[root@buildah-fresh ~]# podman login quay.io
Username: rturk
Password:
Login Succeeded!

Asked a colleague, ipbabble, who does not have a /run/user/0 directory and is somehow able to successfully run podman login.
Output of podman version:
Version:       0.2.2
Go Version:    go1.9.4
OS/Arch:       linux/amd64

Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora Cloud Base 27, running in Red Hat OpenStack Platform:
[root@buildah-fresh ~]# cat /etc/redhat-release
Fedora release 27 (Twenty Seven)

It looks like we use a path for temporary login files that exists for normal users, but not root. We can likely work around this by specifying an alternate path if the primary doesn't exist.

I can successfully podman login as the fedora user, yay! However, I can't really do anything else without write permissions to /var/run/containers.
[fedora@buildah-fresh ~]$ podman login quay.io
Username: rturk
Password:
Login Succeeded!
[fedora@buildah-fresh ~]$ podman pull buildah
could not get runtime: mkdir /var/run/containers: permission denied

Running with sudo should let you do anything - we find the login directory via an environment variable, which sudo should preserve, allowing you to use login. Running as non-root won't work for container operations, given overlayfs requires a lot of capabilities (I also suspect image operations will fail for a different reason), so even chowning the directory won't fix matters.

Ok - I burned my instance to the ground and started over to make sure there was no lingering login anywhere and tried again. After dnf -y update && dnf -y install buildah podman:
[fedora@buildah-fresh ~]$ podman login quay.io
Username: rturk
Password:
Login Succeeded!
[fedora@buildah-fresh ~]$ sudo podman pull quay.io/rturk/buildah
Trying to pull quay.io/rturk/buildah:latest...
Failed
error pulling image "quay.io/rturk/buildah": error pulling image from "quay.io/rturk/buildah": Error determining manifest MIME type for docker://quay.io/rturk/buildah:latest: unauthorized: access to the requested resource is not authorized

The quay.io login credentials do not seem to be passed through to my sudo shell. Am I doing it wrong?

Hm. That looks like it should work (and if it shouldn't, we should force podman login to be run as sudo as well). I'll look more into this tomorrow.

FYI the only containers dir I have outside my home dir and /var/lib is in /run and /etc
/run/containers
/etc/containers
NOTHING in /run/user
find /run/user -type d -name containers
find: ‘/run/user/1000/gvfs’: Permission denied

And I run podman login as root and it works. No problem

Ok, here is the output:
[fedora@buildah-fresh ~]$ sudo podman pull --tls-verify=false quay.io/rturk/buildah
Trying to pull quay.io/rturk/buildah:latest...
Failed
error pulling image "quay.io/rturk/buildah": error pulling image from "quay.io/rturk/buildah": Error determining manifest MIME type for docker://quay.io/rturk/buildah:latest: unauthorized: access to the requested resource is not authorized
[fedora@buildah-fresh ~]$ sudo podman pull --creds rturk quay.io/rturk/buildah
Password: Trying to pull quay.io/rturk/buildah:latest...
Getting image source signatures
Copying blob sha256:bf0f1f12b6ba38f3b9f55fc2f9e865ff92bcc8b5523fce9aeb5886dad05372a4
 86.31 MB / 86.31 MB [======================================================] 3s
Writing manifest to image destination
Storing signatures
6e2b497dd3a916710adc4617c34f68ef8177f2fd75d7e7bdbb9442b1d8761ec1

FYI, if I follow those commands up with another podman pull without --creds, it does not work:
[fedora@buildah-fresh ~]$ sudo podman pull quay.io/rturk/nginx
Trying to pull quay.io/rturk/nginx:latest...
Failed
error pulling image "quay.io/rturk/nginx": error pulling image from "quay.io/rturk/nginx": Error determining manifest MIME type for docker://quay.io/rturk/nginx:latest: unauthorized: access to the requested resource is not authorized

Thanks @rossturk!  That definitely smells like login isn't dropping the authentication where pull is expecting it.  Something for us to dig at.  If you've the time, and if I was bright I'd have asked you in the previous, can you try:
sudo podman login quay.io
sudo podman pull quay.io/rturk/buildah
Thanks again!

That puts me back to square one:
[fedora@buildah-fresh ~]$ sudo podman login quay.io
Username: rturk
Password:
error creating directory "/run/user/0/containers": mkdir /run/user/0/containers: no such file or directory

I suspect sudo mkdir -p /run/user/0/containers and rerunning would fix it.

FYI, if you use the --creds in the podman command line, it does not retain those credentials once the command completes.  The credentials are only tucked away and used for follow on commands when entered via 'podman login'.
Thanks for trying the 'sudo podman login', more good data for digging.

BTW here is my debug:
podman --log-level debug login quay.io
Username: ipbabble
Password:
DEBU[0007] Looking for TLS certificates and private keys in /etc/docker/certs.d/quay.io
DEBU[0007] GET https://quay.io/v2/
DEBU[0008] Ping https://quay.io/v2/ err
DEBU[0008] Ping https://quay.io/v2/ status 401
DEBU[0008] Increasing token expiration to: 60 seconds
DEBU[0008] GET https://quay.io/v2/
Login Succeeded!

I think it's super interesting that @ipbabble is able to podman login as root with no /run/user/0 directory at all! He is Fedora on bare metal, I am Fedora Cloud Base. Otherwise, we can't figure out what's different.

I have /run/user/0 on Fedora workstation bare metal, no /run/user/0 on Fedora server on a VM

I have /run/user/[0,1000, 42] But no containers subdir under any of them.

I suspect the issue is that we did most of our dev/testing under Fedora workstation & similar. If it's as simple as creating /run/user/$UID if it doesn't exist, we can do that easily. I'd like to read more on XDG_RUNTIME_DIR before putting that in, though.

I don't have bare metal to look at.  However my F27 workstation vm does not have a /run/user/0 either.  I'm able to pull my image from a private repository using the creds with the pull, or by doing a 'podman login' with or without sudo.  I think @mheon is going down the right track.

I did bit of googling and and read some docs and see that directory in /run/user/<UID> is created by pam_systemd with sets default XDG_RUNTIME_DIR.
From freedesktop org docs it states, pam_systemd — Register user sessions in the systemd login manager. So below is what I see is happening.
If you login with an user, the corresponding /run/user/<UID> is created by systemd-logind.service.
$ ssh<EMAIL_ADDRESS>
# ll /run/user/
total 0
drwx------. 3 root root 80 Mar  1 04:50 0

$ ssh<EMAIL_ADDRESS>
$ ll /run/user/
total 0
drwx------. 3 root   root   80 Mar  1 04:50 0
drwx------. 3 sunilc sunilc 80 Mar  1 04:51 1000

On the other hand if you login with X user and then su to Y user, then the directory is not created for Y user.
Becuase the Y user has not logged in through systemd-login.
$ ssh<EMAIL_ADDRESS>
[sunilc@svma ~]$ su -
Password:

# ll /run/user/
total 0
drwx------. 3 sunilc sunilc 80 Mar  1 04:52 1000

Where does podman login create the files when XDG_RUNTIME_DIR is not set? Where does podman pull look for them?

I wonder how bad it would be for us to create XDG_RUNTIME_DIR in place of systemd-logind if it does not exist. I also wonder about distros that may not have systemd at all - we'll need to do something about them too.
I think the answer is probably to ignore XDG_RUNTIME_DIR entirely and create files in the libpod tmp dir (named by UID, so we don't have conflicts). This is a location we can guarantee exists everywhere.

I think the reason the /run/user/ location was originally chosen is it gets cleaned out on reboot.  It would be nice to have a location that did the same.  Since we don't have a daemon banging around, we can't clear it through some exit routine there.

We should just check for the environment XDG_RUNTIME_DIR, if it does not exist, we default to /run/user/UID/.
That way it works in both cases.

@rhatdan that is what it is doing https://github.com/containers/image/blob/master/pkg/docker/config/config.go#L135.
This was the plan from the beginning from what I remember. If you run as root, the UID would be 0 yes? So even with this the path would end up being /run/user/0, which does not exist always?

There may also be cases where XDG_RUNTIME_DIR is set, but the directory was not created?

@mheon So check for if XDG_RUNTIME_DIR is set and if it is, check if the directory exists, if not create that directory? Is it okay creating /run/user/0 if it doesn't exist? (not sure if that is a thing we are allowed to do)

Whether we can create the directory is a good question. I'll look into that tomorrow.

@mheon okay, I will do some research also. Assigning this to myself.

If XDG_RUNTIME_DIR is not defined  We should default to /run/user/UID, and create it if it does not exist.
If XDG_RUNTIME_DIR we should use it, and NOT create the directory if it does not exist.  Setting the XDG_RUNTIME_DIR directory indicates that the caller knows what he is doing and is in charge of creating the directory.  I don't to have a users typo accidentally trigger the creation of a directory, that the user might not even know about.  I would rather fail.

@mheon how about we print a warning if XDG_RUNTIME_DIR is set but the directory doesn't exist? This way the user will know the cause of the failure. We can also say "Either create the directory or unset XDG_RUNTIME_DIR".

I'd prefer to just fall back to /run/user/UID, but that would definitely be better than what we do now

So while writing a patch for this, I discovered that the code to create the directory if it doesn't exist is already there https://github.com/containers/image/blob/master/pkg/docker/config/config.go#L172.
So this is failing to create the /run/user/0/contianers directory. Could it be permissions?

Oh nvm, I am blind. It is doing Mkdir and and not MkdirAll.

Re-posting from https://github.com/containers/image/pull/424 to keep the conversation in one place:
I’m not convinced about auto-creating /run/user/$UID; /run/user is, at least on my system, root:root 755, so any non-root user is not going to benefit.
It seems to me that if the real fix for that needs to be in some quite different place.

Looking at pam_systemd(8), it removes /run/user when “the last concurrent session of a user ends”; so, if we created the directory without systemd knowing about the session, it can delete the directory at an unpredictable time when some other session terminates.
At least on F26, I do have pam_systemd configured in the system-auth config, which is used by su.  The failure is actually

pam_systemd(sudo:session): Cannot create session: Already running in a session

So, overall, either pam_systemd needs to be taught to handle su, or we need to move away from /run/user, or we would have to give up on su/sudo (which seems untenable).

Well we can't change every distributions handling of su, so that is a non starter.  We need a default location fore the creds, which is currently $XDG_RUNTIME_DIR/containers or /var/run/$UID/containers if $XDG_RUNTIME_DIR does not exists correct?  Doing a MakeDirsAll on this might be the simplest solution.

MakeDirsAll on /var/run/$UID just won’t work for $UID not 0.
Even for root only, breaking the documented rules of that directory isn’t all that great either:
[mitr@f26]$ su -
[root@f26 ~]# ls /run/user
1000  42
[root@f26 ~]# mkdir /run/user/0
[root@f26 ~]# ls /run/user
0  1000  42
[root@f26 ~]# ssh localhost
[root@ssh-f26 ~]# ls /run/user
0  1000  42
[root@ssh-f26 ~]# logout
Connection to localhost closed.
[root@f26 ~]# ls /run/user
1000  42

and /run/user/0 is gone.
Meanwhile, systemd has liked to pretend that su/sudo and nested sessions don’t exist, so I am not quite holding my breath for pam_systemd to improve on its own, either.

BTW using $XDG_RUNTIME_DIR at all can be tricky as well:
[mitr@f26 ~]$ echo $XDG_RUNTIME_DIR
/run/user/1000
[mitr@f26 ~]$ su # Note: not (su -)
[root@f26 mitr]# echo $XDG_RUNTIME_DIR
/run/user/1000
[root@f26 mitr]# mkdir -m 0700 $XDG_RUNTIME_DIR/containers
[root@f26 mitr]# exit
[mitr@f26 ~]$ ls -ld $XDG_RUNTIME_DIR/containers
drwx------. 2 root root 40  7. bře 18.44 /run/user/1000/containers

… and as the original user, I can’t write into my own private directory any more.  IIRC GNOME or D-Bus has been running into this in practice. Although in this case it’s difficult to say whether it is a problem or a feature, some might like that a login from an unprivileged session can be used inside su.

Overall going back to storing the data in the home directory seems most clean to me. That would lose the “log out of Docker on last logout or system shutdown” behavior, but I never saw that as all that valuable; maybe I’m missing something.

I have no objections to using to a dir in the user's home.

I would like to minimize the amount of time, we have clear passwords stored on flat files on disk.
MakedirsAll will work if /run/user/UID exist, it will create containers, if you are root and /run/user/0 does not exist, it will also work to create the content and the parent directories.

We could use a different directory for root running the containers.  Until we have user namespace podman will not run as non root, not sure it will work run with usernamespace as non root then either.

Should we use MkdirAll, but restrict ourselves to only doing it if we are UID 0?

I don't actually think you need that constraint.  Since it will either work or fail, if it fails we get an error.
If XDG_RUNTIME points to /run/user/3267 and it attempts to create /run/user/3267/containers, this will succeed if /run/user/3267 exists and I am logged in as 3267 it will fail if the directory does not exist.

Carving out a root-only exception (e.g. use /run/containers-root or whatever the rules for /run are) would work fine for podman, but the same login code is also used for skopeo and maybe other tools which do not have any privileges.
Tradeoffs… I am instinctively averse to “works 99% of the time, fails unpredictably 1% of the time” designs, but maybe using /run/$UID is better than leaving keys on disk. If $HOME and /run were out of the question for unprivileged users, we wouldn’t have that many options: I don’t think we can rely on the presence of an userspace key storage daemon, and I don’t know about the practicality of using the kernel keyring (especially WRT debugging the state of the system in an emergency).

@rhatdan @mheon @mtrmac So what is the consensus? Store the auth in XDG_RUNTIME_DIR if it is set otherwise to default to /run/usr/UID (and create this if it doesn't exist) like we were doing?

@umohnani8 I don't believe we have a consensus yet, so leaving it as-is for now will have to do

How about if XDG_RUNTIME_DIR is not defined, we run it with /run/containers/UID, then we don't have to worry about systemd removing the directory

I have no problem with this. I presume we create the directory if it doesn't exist? Will we have permissions to do this if we're not root?

I agree with this also. Yeah you will have to be root to be able to create the /run/containers/UID directory. But all podman and buildah commands are run as root anyway, and we can add it to the docs "always run login and logout as root".

@rhatdan should I go ahead and update the patch to save in /run/containers/UID? User will have to run as root though, otherwise we won't be able to create the directory under /run.

Yes, I am really primary concerned about the root use case.

One more thing, apparently /run/containers already exists, with /run/containers/registries.conf created by the atomic-registries package.
I can’t see any issue with sharing it, and using /run/containers/$UID for the login status, but I may be missing something.
Is sharing the directory OK?

Yes,  I don't see an issue.  I am trying to keep all of our stuff under /etc/containers, /run/containers, /var/lib/containers, /usr/share/containers...


Parse object files with ElfFile64 rather than object::File

The latter is what Wasmtime uses today but it pulls in parsers for all object formats supported by object. In the context of Wasmtime, however, we know that all objects produced are 64-bit ELF files so there's no need to pull in, for example, a COFF parser as that'll always return an error anyway. This commit switches uses of the object::File convenience to ElfFile64 instead.

Ah turns out we're already not-enabling coff/xe/etc, so not much else to do!


fix: LEAP-1615: LEAP-456: Fix tool unselect

Pan was blocking the app upon unselection, because there were no tools selected after this. When drawing tools are not displayed (like in usual RectangleLabels case) then it's hard to start drawing again.
Also Selection tool (aka Move tool) was switched to the same behavior, allowing users to unselect it. The default tool will be selected then.
Also Smart tools selection is fixed — when you click on exact tool it's selected without weird jumps and rotation through other tools.
https://github.com/user-attachments/assets/a25ad3b2-a188-4304-b51f-49db9239f2ed
PR fulfills these requirements

[ ] Tests for the changes have been added/updated (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[x] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[x] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)

[x] Product design
[ ] Backend (Database)
[ ] Backend (API)
[x] Frontend

Describe the reason for change
Users can be stuck after using Pan tool and unselecting it. Also that's inconsistent with Move tool.
Does this change affect performance?
nope
Does this change affect security?
nope
What alternative approaches were there?
Make Pan tool also not unselectable like Move tool. But for cases without drawing tools visible that would make it worse.
Does this PR introduce a breaking change?

[ ] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[x] No
[ ] Not sure (briefly explain the situation below)

/git merge

isSeparated and iconComponent are both removed - are they no longer used anywhere?

@yyassi-heartex they are used when we render base tool via ToolView in tools/Base.jsx. and I switched Move tool to render its custom tag like we do in some other tools, so we don't need these params


Support '_' as part of object key names

This would be really helpful. There are some cases where third parties use _ as a separator. If I want to use those raw objects, I need to convert the keynames before I can pass them to string-template.

Just caught this one as well, couldnt figure out why my variables weren't working

For real.

fixed in v1.0.0

Thanks!


Uncaught TypeError: r[t] is not a function/ https://apis.google.com

Hi,
I am trying to get angularfire2 to work with Ionic 2 in a PWA and for some reason I am always getting this error:
Uncaught TypeError: r[t] is not a function
at Object.Y.x.(anonymous function) [as loaded_0] (https://apis.google.com/js/api.js?onload=__iframefcb740853:10:484)
at https://apis.google.com//scs/apps-static//js/k=oz.gapi.en.HUGusW2Obik.O/m…d=1/ed=1/am=AQ/rs=AGLTcCMQfcTc_uts7vlIlqUhKKWbRzGreA/cb=gapi.loaded_0:1:15
Y.x.(anonymous function) @ api.js?onload=__iframefcb740853:10
(anonymous) @ cb=gapi.loaded_0:1
error_handler.js:47
EXCEPTION: The operation has timed out.
My info:
Ionic Framework: 2.0.1
Ionic Native: ^2.8.0
Ionic App Scripts: 1.1.4
Angular Core: 2.2.1
Angular Compiler CLI: 2.2.1
Node: 6.9.2
OS Platform: macOS Sierra
Navigator Platform: MacIntel
User Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1
Any way to solve the issue? Thanks.

Hello! Thanks for opening an issue with us! As this seems like more of a support question i will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!

Is there a solution to this issue? We have same problem quite frequently

Seeing the issue on an existing app as well with the latest version. But i am only seeing it when chrome is emulating the iPhone. In normal mode it works fine.

I can confirm victoriaFrench. It does only happen when emulating in the iphone in chrome. I have my product working live on a device right now and all is well.

I can confirm victoriaFrench. It does only happen when emulating in the iphone in chrome. I have my product working live on a device right now and all is well.


unlink testlibs from kube-apiserver and kubelet, remove test flags

right now a few of our binaries have test flags:
      --httptest.serve=: if non-empty, httptest.NewServer serves on this address and blocks
      --test.bench=: regular expression to select benchmarks to run
      --test.benchmem=false: print memory allocations for benchmarks
      --test.benchtime=1s: approximate run time for each benchmark
      --test.blockprofile=: write a goroutine blocking profile to the named file after execution
      --test.blockprofilerate=1: if >= 0, calls runtime.SetBlockProfileRate()
      --test.coverprofile=: write a coverage profile to the named file after execution
      --test.cpu=: comma-separated list of number of CPUs to use for each test
      --test.cpuprofile=: write a cpu profile to the named file during execution
      --test.memprofile=: write a memory profile to the named file after execution
      --test.memprofilerate=0: if >=0, sets runtime.MemProfileRate
      --test.outputdir=: directory in which to write profiles
      --test.parallel=1: maximum test parallelism
      --test.run=: regular expression to select tests and examples to run
      --test.short=false: run smaller test suite to save time
      --test.timeout=0: if positive, sets an aggregate time limit for all tests
      --test.v=false: verbose: print additional output

This fixes #8744
/cc @thockin

Good catch. LGTM

@thockin assigned for second lgtm, ok-to-merge.

@dchen1107 is a better choice for kubelet. can haz ok-to-merge?

LGTM and thanks for fixing.

The real fix is to move all test-related gunk into separate pkgs, but this is better than nothing.


Syntax highlighter confused by class properties with optional type

VSCode Version: 1.8.1
OS Version: Mac OS X, 10.11.5

Steps to Reproduce:

Write a class containing class properties, e.g.

class Foo {
    state = {
        bar: (null: ?Bar),
    }

    toString() {
        const bar = this.state.bar;
        console.log(`bar = ${bar}`);

        // the rest of the file is in a string
    }
}

The line const bar = this.state.bar; is also incorrectly highlighted.
Changing ?Bar toBar fixes the highlighting.

This issue was moved to Microsoft/TypeScript-TmLanguage#410


Wrong targetFramework selected for UWP apps with MinVersion <= 10.0.15063

Introduction, .NET Standard support in UWP apps
Starting with Windows 10 Fall Creators Update, version 1709 or 10.0.16299, it's possible to use .NET Standard 2.0 APIs in C# UWP apps.
But if my UWP app is targeting previous OS versions as well using the MinVersion parameter, it's not possible to use .NET Standard 2.0 APIs in my app. This is a common scenario for many apps that want to support older Windows 10 versions or Windows 10 Mobile as well. The last SDK version supported on Windows 10 Mobile is 10.0.15063.
The problem with targetFramework precedence
Newtonsoft.Json package version 10.0.1 added .NETStandard1.3 targetFramework to the list of supported frameworks. This caused one unwanted problem - because how the NuGet Framework Precedence system works. This .NETStandard1.3 framework is now selected as the best version for UWP apps. This causes need for referencing NETStandard.Library version 1.6.1, in other words 120+ new or updated dependencies. This all just to have Newtonsoft.Json in the app.
Newtonsoft.Json package version 11.0.1 added .NETStandard2.0 targetFramework to the list of supported frameworks. If my UWP app is targeting MinVersion 10.0.16299 or newer, Newtonsoft.Json NuGet works fine, because the .NETStandard2.0 version is used. But if I use MinVersion <= 10.0.15063, again .NETStandard1.3 framework is selected and NuGet forces to install NETStandard.Library version 1.6.1 dependency to my app.
This is how it looks when including latest Newtonsoft.Json in my UWP app that is targeting MinVersion 10.0.14393:

Expected behavior
There should be no need to install NETStandard.Library version 1.6.1 if I just want to use Newtonsoft.Json in my UWP app. This could be easily solved by adding another targetFramework="UAP10.0" or ".NETCore5.0". This target framework id has better precedence than .NETStandard1.3 in UWP apps.

I don't want to create platform specific TFMs, there is a lot of work involved in maintaining and testing them.


Cerberus Failed to broacast during autostake

Error below
[15:28:34.590] Sending 16 messages in 1 batches of 100
[15:28:34.590] ...batch 1
[15:28:42.332] Failed to broadcast: Broadcasting transaction failed with code 32 (codespace: sdk). Log: account sequence mismatch, expected 227, got 226: incorrect account sequence
[15:28:42.332] Cerberus finished

The sequence error occurs when your wallet has sent another TX that the script isn't aware of. It probably means your autostake runtime is overlapping, if you're using cron then it could be starting another run while the previous is still going?


broken link : ycontributors.finance

https://docs.yearn.finance/contributing/contribute#yearn-contributors-1

https://github.com/yearn/yearn-devdocs/pull/189


Support arguments on http import command

add to http import: http://orientdb.com/docs/last/OrientDB-REST.html#import the support of options for ex: -merge
the options could be simple http get parameters

added closing


The JSON updater file is mal-formatted. AppUpdate can't check for updates

[x] I have verified there are no duplicate active or recent bugs, questions, or requests.
[x] I have verified that I am using the latest version of AppUpdater.
[x] I have given my issue a non-generic title.
[x] I have read over the README, Wiki and FAQs (before asking questions on how to do something).

Details

PiracyChecker version: 2.x.x (Doesn't used this)
Device OS version: 5.1
Device Manufacturer: Lenovo
Device Name: leneovo tab3 7Essentials

Builder
AppUpdaterUtils appUpdaterUtils = new AppUpdaterUtils(getContext())
                .setUpdateFrom(UpdateFrom.JSON)
                .setUpdateJSON("https://somesite.com/MyApp/update-changelog.json")
                .withListener(new AppUpdaterUtils.UpdateListener() {
                    @Override
                    public void onSuccess(Update update, Boolean isUpdateAvailable) {
					Intent updateIntent = new Intent(Intent.ACTION_VIEW, Uri.parse(update.getUrlToDownload().toString()));
                        updateIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
                        getContext().startActivity(updateIntent);
					}

					@Override
                    public void onFailed(AppUpdaterError error) {
                        Log.d("AppUpdater Error", "Something went wrong");
                    }
                });
        appUpdaterUtils.start();

JSON I used
{
  "latestVersion": "1.0.1",
  "latestVersionCode": "2",
  "url": "https://somesite.com/app-debug.apk",
  "releaseNotes": [
    "- First evolution",
    "- Second evolution",
    "- Bug fixes"
  ]
}

Expected Result
Invoking Update Intent
Actual Result
The JSON updater file is mal-formatted. AppUpdate can't check for updates

Even I am getting the same result. Any updates from anyone?

I'm looking into it.

this format worked for me.
I don't see any difference to be honest
{
"latestVersion": "1.2",
"latestVersionCode": "2",
"url": "http://www.google.com",
"releaseNotes": ["v1.2","- New Scanner Scenario", "- Bug Fixes"]
}

I'm not able to reproduce the issue. I have tested using Android 5.1 & 8.1 and uploaded your JSON to Pastebin.
Does uploading the JSON to another server solve the problem?

what happens when I set showEvery(5) and
How long does it wait to show the dialog again?

E/AppUpdater: The JSON updater file is mal-formatted. AppUpdate can't check for updates.

When .showEvery(5) is set, the dialog (snackbar or notification) will be displayed the first time that a new update has been found. Then it will only be displayed every 5 times that the builder has been called.


Caddy Multisite setup not working workdir in dockerfile

Info:

Docker version ($ docker --version): 17.05.0-ce, build 89658be
Laradock commit ($ git rev-parse HEAD): 801ccd47d22999d087896045cdfd1d7316212174
System info (Mac, PC, Linux): Linux
System info disto/version: Linux version 4.4.0-87-generic (buildd@lcy01-31) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017

Issue:
ERROR: for caddy  Cannot start service caddy: oci runtime error: container_linux.go:247: starting container process caused "chdir to cwd ("/var/www/public") set in config.json failed: no such file or directory"

Expected behavior:
The caddy\Dockerfile is properly config for support multisite mode

Reproduce:
Setup project with multisite mode (APPLICATION =../, Caddyfile with config root /var/www/<project_folder>/public)

Relevant Code:
// place a code sample here

bump i also facing this issue anyone have fixed or have idea how to fix this?

Check the caddy\Caddyfile, there are 2 block {}, just comment out every block that you don't need them, such as
# laradock.demo {
#     root /var/www/public
# }

and your should change the WORKDIR config in the caddy\Dockerfile like below
WORKDIR /var/www/<your project folder name>/public

Hope you can solve your problem.

i had done that already, but its not workable for multisite , or separate laravel folder installed apps...
as you can see WORKDIR is only for one folder....
If i did what you said here only one site has SSL , the other one wont even load at all
i think this should be change to adopt for multisite...

The separate apps can signed many times via the caddy\Caddyfile.
From Docker file, you can think about WORKDIR just like a CD command from shell.
WORKDIR /var/www/mailautoreply-ai-basic/public

#Almost forgot, it seems that I've changed the cmd like below
CMD ["/usr/bin/caddy", "-conf", "/etc/Caddyfile"] #<-- this one always call from root hierachy, not caring anything about workdir.


Expose core/relational strings and logging APIs for providers

Issue #14973
Now public:

CoreLoggerExtensions
RelationalLoggerExtensions
CoreStrings
RelationalStrings
AbstractionsStrings

Still internal:

All provider strings and logger extensions
Generated logger definition constructors--providers should access these through the logger extensions

Also cleaned up a few provider internal namespace names to be consistent.

Ping for a review on this. I know it's a lot of files, but it's almost all mechanical namespace changes.


Harbor version rollback

What can we help you?
At first, I set spec.version=2.5.1, harborcluster status is health, then I changed it to spec.version=2.5.2, and then I changed it back to spec.version=2.5.1, and it showed an error.
[root@localhost ~]# kubectl apply -f minimal_stack_fs.yaml
namespace/cluster-sample-ns unchanged
secret/admin-core-secret unchanged
secret/harbor-test-ca unchanged
issuer.cert-manager.io/selfsigned-issuer unchanged
certificate.cert-manager.io/sample-public-certificate unchanged
persistentvolumeclaim/sample-harbor-registry unchanged
The HarborCluster "harborcluster-sample" is invalid: spec.version: Invalid value: "2.5.0": downgrade from 2.5.2 to 2.5.0 is not allowed

The downgrade is not allowed in the harbor.

Maybe we could allow it for patch version only, but what would be the use case ?

/close


Is the server-wrapper in Angular sample app really needed?

Is your feature request related to a problem? Please describe.
Installing webpack and adding specific webpack files and configurations to be able to build the server.bundle.ts has questionned me. Is it really needed? Can Angular not deliver this out of the box? Is the separate server-wrapper build task really needed? If we can ommit the need for all this configuration and the build:task, this would definitly speed up the development process in an Angular multi-project Repo setup (we are using NX from Narwhal).
Describe the solution you'd like
I have looked into the Angular Universal solution and they do not seem to inclulde 2 tasks for building the server bundle. After some researching I have found a few simple changes in the setup of the sample Angular, which seem to produce a valid server bundle, but not only with just one build task (build:server), also half the bundle size!
Before:

After:

Ofcourse I wondering: is there something in my blind spot :)? Can you test this in your setup to validate my proposal?
Additional information
Commit with code changes:
https://github.com/EvtK/jss/commit/62d03b8e60c7e1f56d8a6fea76d585594a15db21

@EvtK Reports no issues so far doing this but would like our feedback on potential issues.

@EvtK I checked it, on my local instance it's working fine. Will allocate time for it later. Probably, can you create a pull request with your changes?

Hi @sc-illiakovalenko, finally got to this :)
here is the PR: https://github.com/Sitecore/jss/pull/522


[Bug] Title is rendered twice when titleLocation is set to left

Are you requesting a feature, reporting a bug or ask a question?
Bug
What is the current behavior?
If you set the questionTitleLocation to left the title is rendered twice (at least in vue)
How would you reproduce the current behavior (if this is a bug)?
See: https://plnkr.co/edit/KnSCjvfsQMTVSNicpXox?p=preview and open your console and search for the elements.

1. Question 1, Page 1

<input type="text" size="25" id="sq_100i" placeholder="" aria-label="1. Question 1, Page 1" class="sv_q_text_root">

1. Question 1, Page 1

Specify your

surveyjs platform (angular or react or jquery or knockout or vue): Vue
surveyjs version: v1.0.8

Culprit
The title is rendered but hidden because of this line:
https://github.com/surveyjs/surveyjs/blob/c09a0b632a0f4de7d072f31d9e157a9230471a3c/src/vue/element.vue#L16-L17
The condition in v-show should be added to the v-if condition of the same line

Thanks, I can confirm that is not rendering twice anymore in v1.0.9


[Bug]: Can't properly embed JSON into a MongoDB query due to escaping

Is there an existing issue for this?

[x] I have searched the existing issues

Description
I'm trying to overwrite an embedded document with JSON data from a JSON form. As you can see on the screenshot, I'm trying to put that JSON data under the "content" key, but the resulting query becomes invalid due to the quotes getting escaped.

Steps To Reproduce

Create a JSON form, then populate it with data
Try embedding the JSON data inside a MongoDB query to overwrite an embedded document within another document
Disabling smart substitution doesn't change anything

Version
Cloud

Here's a demonstration of the problematic behavior. If only there was an option to disable escaping quotes

An obvious workaround I see is to deconstruct the content document and update each field individually, but then there's a problem with the array: the quotes get escaped again. Updating array by index is unreasonable since arrays are dynamically sized.
$set: { content:
  plaque_text: "{{JSONForm1.formData.content.plaque_text}}",
  features: {{ JSONForm1.formData.content.features }}            # <-- array
}

Another option is to try replacing double quotes with single ones, but, interestingly, it does not help, although the resulting query seems legitimate. The error thrown: Update could not be parsed into expected JSON format.

Damn, my bad... It was incorrect MongoDB syntax. That's the working version:
{
  $set: {
    'name': '{{JSONForm1.formData.name}}',
    'content': {{JSONForm1.formData.content}}
  }
}


Update README.md

The note about deprecation was not eye-catching, and sent me on an hour long wild goose chase. So, using Github Markdown magic to add some colour.

@liamcain


Allow text input when setting the time through the time picker

Is your feature request related to a problem? Please describe.
Hi there!  I've been working with this date picker component for a bit now and love it.  However, it feels a bit clunky the only way to enter a time into the time picker is by using the increment arrows or the grid selection overlay.  I think it'd be a better user experience to allow text input when entering a time in the time picker, instead of having to click a bunch or find the time they want in the grid overlay.
(I realize that the input field can be used to do this, but it also requires setting the date.  It'd be preferable if you could use text input to enter a time without also having to do so for the date.)
Describe the solution you'd like
Add a configurable prop that allows the time to be selected through the time picker with text input.  I imagine this would be rendered as an alternative to the grid overlay.  So, if the prop was enabled, clicking on the hours, minutes, or seconds would allow you to enter them through text input instead of opening the grid overlay.  I imagine typing in the hours would also focus the cursor on the minutes field, then the seconds field if enabled.
Describe alternatives you've considered
Using the existing grid overlay, incrementing time picker arrows, and the text input field are all alternatives here, albeit they're slightly less convenient than directly allowing for text input in the time picker.
Any help or guidance to an adequate, existing alternative would be much appreciated!  Thanks for all the good work you guys have done on this component already! :)

It is a bit tricky to add this and can result in a lot of boilerplate code. The best way would be to use overlays or time-picker-inline. You can also make a slot and handle input there in a desired way.


Update service-tags-overview.md

Clarification on "Internet" Service Tag since it causes confusion when there are other Default Routes being learned from OnPremises or other peered VNETs. Added text "This Service tag only applies where the traffic does not hit any other Service Tag."

Learn Build status updates of commit ad3a09b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/virtual-network/service-tags-overview.md
:white_check_mark:Succeeded

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

@asudbring

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Learn Build status updates of commit d4f4393:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/virtual-network/service-tags-overview.md
:white_check_mark:Succeeded

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

#sign-off


Support for PineTime

Hi, is it possible to add support for PineTime? Seems like it's almost like P8 watch which is already supported..

It would not be difficult, however, I do not have a PineTime watch so I am not in a position to add support.

I have one, is it any helpful? My unit is sealed though, so no uart, just bluetooth available.


Not pulling files from correct folder

When attempting to install dependencies / run installer the script attempts to pull directly from the (Username) folder, and not the BetterDiscordAutoInstaller folder contained within, causing it to fail. Copying contents outside of this folder allows it to continue of course

Hi
The problem may be that in your shortcut in the "Working folder" field there is a folder with the user. Change this value to the folder with the script, and if it doesn't help, let me know


Integrate EvaDB with SuperAGI

Search before asking

[X] I have searched the EvaDB issues and found no similar feature requests.

Description
Integrate EvaDB with SuperAGI to make it available through the SuperAGI interface.
Use case
No response
Are you willing to submit a PR?

[X] Yes I'd like to help by submitting a PR!

Could we update the PR we created in the issue? Thanks.


ScrollView setContentOffset not working after setup BLKFlexibleHeightBar.

Hi all,
I have created a view pager with a ScrollView embedded in a BLKFlexibleHeightBar like ones on Android. The scrollview contains many tabs. The custom bar work great: pages with root view are tableview(s) or scrollview(s) scroll and the bar go up and down as expected. But I have a small problem: I can't update the scrollview contentOffset after the bar setup completely. If I set the scrollview contentOffset before initialising the bar, it show with an offset on the bar. Can anyone tell me what ways to do this task? Thanks and sorry for my bad English.

I solved it by tweaking the scrollview center.


Deploy within an environment that strictly disallows public network access

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce
Trying to deploy with
azd env set AZURE_USE_PRIVATE_ENDPOINT true
azd env set AZURE_PUBLIC_NETWORK_ACCESS Disabled
azd up
Any log messages given by the failure
Our Azure environment does not allow public network access at all, and the above fails with:
(✓) Done: Resource group: ISWEACEDEV01-RG-01
(✓) Done: App Service plan: plan-xzr2h4erskcqg
(✓) Done: Azure OpenAI: cog-xzr2h4erskcqg
(✓) Done: Virtual Network: vnet-xzr2h4erskcqg
(✓) Done: Document Intelligence: cog-di-xzr2h4erskcqg
(✓) Done: Search service: gptkb-xzr2h4erskcqg
|      =| Creating/Updating resources
ERROR: error executing step command 'provision': deployment failed: error deploying infrastructure: deploying to subscription:
Deployment Error Details:
InvalidTemplateDeployment: The template deployment failed because of policy violation. Please see details for more information.
RequestDisallowedByPolicy: Resource 'userstxzr2h4erskcqg' was disallowed by policy. Reasons: 'Public network access must be disabled for PaaS services.'. See error details for policy resource IDs.
TraceID: 0742395aac02059fd2be8eaad2c546fd
Expected/desired behavior
Successful provisionning
OS and Version?
Windows 11
azd version?
azd version 1.9.3 (commit e1624330dcc7dde440ecc1eda06aac40e68aa0a3)
Versions
Forked from 905b62e349e1ade9828326f02778f48f0952cf8d (2024-06-17)

Hi @DuboisABB can you please share the full deployment log? I don't know what resource specifically is the one that this deployment has an issue with. Thank you!

Sorry somehow I missed your reply. I finally understood that "Public network access must be disabled for PaaS services" is not a single policy but a whole set of policies. Apparently the config in the bicep files when AZURE_PUBLIC_NETWORK_ACCESS="Disabled" were not strict enough.
The bit that was causing problem was this in storage-account.bicep:
var networkAcls = {
  bypass: bypass
  defaultAction: 'Allow'
}

I changed it to this (I also added a parameter for allowed IP address):
param networkAcls object = {
  bypass: publicNetworkAccess == 'Enabled' ? bypass : 'AzureServices'
  virtualNetworkRules: publicNetworkAccess == 'Enabled' ? [] : []
  ipRules: publicNetworkAccess == 'Enabled' ? [] : (empty(allowedIpAddress) ? [] : [
    {
      value: allowedIpAddress
      action: 'Allow'
    }
  ])
  defaultAction: publicNetworkAccess == 'Enabled' ? 'Allow' : 'Deny'
}


Use attribute output helper instead of rewrite

Don't make a rewrite for this:
https://github.com/jahvi/FileUploadAttribute/blob/master/app/code/community/Jvs/FileAttribute/Block/Product/View/Attributes.php
Better use a attribute output helper:
http://www.webguys.de/magento/attribut-werte-vor-der-ausgabe-im-frontend-veraendern/

Thanks, didn't know you could do that I'll include it on the next update


Show Page Buttons

Summary
In every theme and for a UV show page or thumbnail show page, the 'Add collection', 'Feature', 'Analytics', 'Edit', 'File Manager', 'Attach Child', 'Delete' buttons do not match the HykuCommons styling. See Screeshots
Knapsack

HykuCommons

Acceptance Criteria

[ ] 'Add collection', 'Feature', 'Analytics', 'Edit', 'File Manager', 'Attach Child', 'Delete' buttons match the HykuCommons styling for in every them and for every show page

Closing - should be handled in https://github.com/scientist-softserv/palni_palci_knapsack/issues/177


browser is not reloading while file changes

hi,
when i run npm start i can see this. My project is working but everytime i have to refresh the browser. I uninstalled and reinstalled several times but its not working.
From your angular2 vide tutorial series i compared the npm start log and i found a mismatch "Did not detect a bs-config.json or bs-config.js override file. Using lite-server defaults...
[1] ** browser-sync options **"
not sure what i have to do

MDs-MacBook-Pro:~ axiskafi$ cd /Applications/AMPPS/www/angular
MDs-MacBook-Pro:angular axiskafi$ npm start

<EMAIL_ADDRESS>start /Applications/AMPPS/www/angular
concurrent "npm run gulp" "npm run lite"

[0]
[0] ><EMAIL_ADDRESS>gulp /Applications/AMPPS/www/angular
[0] > gulp
[0]
[1]
[1] ><EMAIL_ADDRESS>lite /Applications/AMPPS/www/angular
[1] > lite-server
[1]
[1] Did not detect a bs-config.json or bs-config.js override file. Using lite-server defaults...
[1] ** browser-sync options **
[1] { injectChanges: false,
[1]   files: [ './**/*.{html,htm,css,js}' ],
[1]   server: { baseDir: './', middleware: [ [Function], [Function] ] } }
[1] [BS] Access URLs:
[1]  ------------------------------------
[1]        Local: http://localhost:3000
[1]     External: http://<IP_ADDRESS>:3000
[1]  ------------------------------------
[1]           UI: http://localhost:3001
[1]  UI External: http://<IP_ADDRESS>:3001
[1]  ------------------------------------
[1] [BS] Serving files from: ./
[1] [BS] Watching files...
[1] 16.03.28 20:51:54 304 GET /index.html
[0] [20:51:54]
[0] Using gulpfile /Applications/AMPPS/www/angular/gulpfile.js
[0] [20:51:54]
[0] Starting 'watch'...
[0] [20:51:54] Finished 'watch' after 12 ms
[0] [20:51:54] Starting 'build-ts'...
[0] [20:51:54] Starting 'build-css'...

[0] [20:51:56]
[0] Finished 'default' after 5.09 μs
[1] [BS] File changed: src/css/app.css
[1] [BS] File changed: app/app.component.js
[1] [BS] File changed: app/boot.js

solved, it was a installation problem, npm-autoinit configuration problem.


[#2991] Add Assert

Add JDK8 style requireNonNull

Codecov Report

Merging #2992 into master will decrease coverage by 0.03%.
The diff coverage is 15.61%.

@@            Coverage Diff             @@
##           master    #2992      +/-   ##
==========================================
- Coverage    37.1%   37.07%   -0.04%
==========================================
  Files        1874     1875       +1
  Lines       63054    63065      +11
  Branches     8775     8778       +3
==========================================
- Hits        23396    23381      -15
- Misses      37230    37255      +25
- Partials     2428     2429       +1

Impacted Files
Coverage Δ

...va/com/navercorp/pinpoint/common/util/Asserts.java
0% <ø> (-25%)
:arrow_down:

.../connection/CollectorClusterConnectionManager.java
0% <0%> (ø)
:arrow_up:

.../collector/cluster/zookeeper/job/ZookeeperJob.java
88.23% <0%> (ø)
:arrow_up:

...ler/receiver/service/ActiveThreadCountService.java
25.45% <0%> (ø)
:arrow_up:

...ientExchangeHandlerImplStartMethodInterceptor.java
0% <0%> (ø)
:arrow_up:

...iler/context/monitor/DataSourceMonitorWrapper.java
62.74% <0%> (ø)
:arrow_up:

.../pinpoint/profiler/instrument/JavassistMethod.java
6.27% <0%> (ø)
:arrow_up:

...r/HttpRequestExecutorExecuteMethodInterceptor.java
0% <0%> (ø)
:arrow_up:

...ercorp/pinpoint/web/dao/hbase/HbaseTraceDaoV2.java
0% <0%> (ø)
:arrow_up:

.../pinpoint/profiler/receiver/CommandDispatcher.java
5.55% <0%> (ø)
:arrow_up:

... and 53 more

Continue to review full report at Codecov.

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


Adjust behaviour of includeDefaultValues to favour "correctness" by default

Background

#170

Currently, CreateAPI uses default values (currently only for booleans) to do two things:

Add a the default argument value to the enclosing types memberwise initialiser
Use it as a fallback value to make a nullable/non-required property in the schema a non-optional type in generated code

After some debate, I've decided that this this special decoding behaviour is not well aligned with the intention of default. That said, the lines here really aren't clear so this could be interpreted in two different ways.

The default keyword specifies a default value. This value is not used to fill in missing values during the validation process. Non-validation tools such as documentation generators or form generators may use this value to give hints to users about how to use a value. However, default is typically used to express that if a value is missing, then the value is semantically the same as if the value was present with the default value. The value of default should validate against the schema in which it resides, but that isn’t required.

https://json-schema.org/understanding-json-schema/reference/generic.html#annotations
One could argue that if an API omits a field in the JSON object that using the default value to fill in is technically inline with the above guidance, but I'm wary of this due to limitations of how we are unable to differentiate between a property being omitted entirely vs it being returned but as null when deserialising.
That said, because there is no other clear way for us to generate code that describes default values of properties, it is nice that CreateAPI is able to make the optional property non-optional and use the default value to fill in the gap in some use cases.
While I think that it's potentially a nice feature, I think it will cause more confusion in the long run as we expand default value support beyond just booleans. Currently this behaviour is opt-out via the includeDefaultValues configuration option.
Proposal
I'm proposing that we remove this behaviour from includeDefaultValues (which defaults to true) moving forward. includeDefaultValues instead will only include supported default values in a types memberwise initialiser.
Alternatives
Make includeDefaultValues opt in
Alternatively, we could make the includeDefaultValues config option opt-in so that CreateAPI can be correct as much as possible by default and offer convenience via customisation points.
I decided against this however because it also brings additional maintenance cost and I'm not sure how popular such behaviour would be. This is based on my own (somewhat limited) experiences so I expect that this could be debated.
## Break includeDefaultValues into two configuration options
Similar to the above, splitting the customisation point into something like includeDefaultValuesInMemberwiseInitializer (opt-out) and includeDefaultValuesAsOptionalDecoderFallback (opt-in) could be another way to maintain this behaviour, making it opt-in and more clearly understood.
Again though, this is more work and I'm not sure if its worth the effort
Conclusion
The proposal here focuses on allowing CreateAPI to evolve through its early stages with as little friction as possible. For people relying on the prior behaviour, this would be a breaking change that could be seen as somewhat inconvenient so I would appreciate any feedback here, but nothing is ever set in stone so we can always revisit things in the future.

In the absence of an explanation for why this change was made in the first place, I support removing this sort of strange behavior. In my opinion, the only default that should be acceptable in a decoding/encoding context is null, which is already handled by Codable synthesis. In addition, while the schema isn't very clear about it and these values can be annoying to use, a non-required boolean is not the same as non-optional boolean and we shouldn't be flattening that type with CreateAPI in the presence of a default value. Furthermore, as referenced in the linked PR and its associated issue, introducing this breaking change as a separate, deliberate move opens up more flexibility to the ability to handle more complex default values beyond booleans. 👍🏼 from me 🙂


supabase-cli: 1.163.4 -> 1.164.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for supabase-cli is: A CLI for interacting with supabase
meta.homepage for supabase-cli is: https://github.com/supabase/cli
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.164.1 with grep in /nix/store/23wvhyjbhmhzmj0jhllj8ihl4nd8k71q-supabase-cli-1.164.1
found 1.164.1 in filename of file in /nix/store/23wvhyjbhmhzmj0jhllj8ihl4nd8k71q-supabase-cli-1.164.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

supabase-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/23wvhyjbhmhzmj0jhllj8ihl4nd8k71q-supabase-cli-1.164.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A supabase-cli https://github.com/r-ryantm/nixpkgs/archive/8ea02a6e18e83fe999a71226ffc7b2a8001edb40.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8ea02a6e18e83fe999a71226ffc7b2a8001edb40#supabase-cli

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/23wvhyjbhmhzmj0jhllj8ihl4nd8k71q-supabase-cli-1.164.1
ls -la /nix/store/23wvhyjbhmhzmj0jhllj8ihl4nd8k71q-supabase-cli-1.164.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

supabase-cli

Maintainer pings
cc @Gerschtli @kashw2 for testing.

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

1 package built:

supabase-cli


Deadlock on Dispose method (OperatorObserverBase.cs line 23)

Hi Yoshifumi-san,
I've been using UniRx successfully on Windows, Mac, iOS, Android, PS4, but now when I'm porting to the Switch, I am experiencing deadlocks on the Dispose method (OperatorObserverBase.cs: line 23).
The thread seems to hang on this System.Threading.Interlocked.Exchange (OperatorObserverBase.cs: line 26).
I commented out the code within the body of the Dispose method for now, and my game is able to run again on the Switch.
I'm not very familiar with threading in general, so I'd like to ask if there is any consequences for simply commenting out this part of UniRx?

I have same issue.
I have following method chain:

Timer(TimeSpan)
TakeWhile(Func<long, bool>)
SubscribeWithState(MyStruct, Action<long, MyStruct>)
AddTo(ICollection)

and if TakeWhile pass no event, then application hang.
If I rewrite not to use TakeWhile, then application run peacefully.

CXxo,xz xz k#9
On Fri, Sep 28, 2018, 3:47 PM NumAniCloud<EMAIL_ADDRESS>wrote:

I have same issue.
I have following method chain:

Timer(TimeSpan)
TakeWhile(Func<long, bool>)
SubscribeWithState(MyStruct, Action<long, MyStruct>)
AddTo(ICollection)

and if TakeWhile pass no event, then application hang.
If I rewrite not to use TakeWhile, then application run peacefully.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/neuecc/UniRx/issues/245#issuecomment-425338800, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABzUEsjgFbSUNu0wuafpQrIZ-B7DSpJnks5ufcXsgaJpZM4PLlD0
.


New version: Zoom.ZoomRooms version 6.1.5

Pull request has been created with komac v2.3.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

@stephengillie this occurs with each deployment of this manifest.

Automatic Validation ended with:

Installation failed with exit code -1978335226
2024-08-06 16:14:03.973 [CLI ] ShellExecute installer failed: 1

Automated error analysis suggests -1978335226 may mean Running ShellExecute failed
(Automated response - build 887.)

Hi @stephengillie this manifest always encounters this issue.


Call the correct TransactionState constructor

The session raised a NullReferenceException on usage after a SaveAsync call when constructed with Session options.
The problem can be found in the ManagedConnection when constructed with SessionOptions.
After a dispose of the TransactionState the ManagedConnection will try to rebuild it on further usage in the buildConnection method, The TransactionState constructor used relies on that the factory has been set before.
This behaviour has been fixed by using the correct constructor and providing the fields needed.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: TobiasSchaffner sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


fix hadolint errors

Fixed errors:
DL3020 Use COPY instead of ADD for files and folders
DL3003 Use WORKDIR to switch to a directory
DL3019 Use the --no-cache switch to avoid the need to use --update and remove /var/cache/apk/* when done installing packages
Remaining errors:
DL3018 Pin versions in apk add. Instead of apk add <package> use apk add <package>=<version>
(It's probably safer to not pin versions in case they aren't available in the future, which might cause the build to fail.)
DL3006 Always tag the version of an image explicitly (community discussion is required to establish which version of alpine should be used).
Fixes #315

/retest

/retest

@mrymsza Could you rebase this please? I want the CI to pass before merging.

@mrymsza Could you rebase this please? I want the CI to pass before merging.


Silverlight plugin is disabled in Chrome 42+, How can ME.js play wma/wmv in future?

In Chrome v42 and newer, Google disables NPAPI plugins by default. Silverlight is a NPAPI plugin that is currently required to be enabled manually. And in further versions (Chrome 45+), NPAPI support will be permanently removed from Chrome.
ME.js support WMA depending on Silverlight.
https://www.chromium.org/developers/npapi-deprecation
https://threatpost.com/google-shuts-off-npapi-in-chrome/112295
How can ME.js play wma/wmv in future?

Why support WMV/WMA in future?  just drop them

There are plenty of online radio resource based on WMA.

@jaredq We are investigating this. We'll keep you posted about any progress on this

@jaredq  Unfortunately, it is not a way to play wmv and wma anymore. Major players such as JwPlayer, VideoJS and Flowplayer are not even considering this format at all, so we are dropping support for them as well, given that they are only-IE propieritary formats


Field name customization

Possible duplicate of #1.
Hi, I want to customize the texts in the cardview and the edittext labels. Is there any way to do that?

The field name is so short. I need more space! Is there any way?

import the folder that's included in their sample (folder name is creditcarddesign).
2.Then modify STRINGS.XML with what you want for the labels.

I did this because I wanted Expiration on the card not Expiry.


sabnzbd post processing error

Hello!
First, I would like to thank you for this automator! I have been using it for quite some time and it really is great. Last week, I started receiving the following types of errors when sabnzbd post processes:
/Library/Python/2.7/site-packages/beautifulsoup4-4.4.0-py2.7.egg/bs4/init.py:166: UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("html5lib"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.
To get rid of this warning, change this:
BeautifulSoup([your markup])
to this:
BeautifulSoup([your markup], "html5lib")
nzbToNzbDrone MP4 edition
Processing episode /Users/name/Downloads/media/complete/nnnn.mkv
Video codec detected: h264
Audio stream detected: aac eng [Stream 1]
Subtitle stream detected: subrip eng [Stream 2]
Subtitle stream detected: subrip eng [Stream 3]
Attempting to download subtitles, please wait
External subtitle file detected, language eng
Importing halt.and.catch.fire.s01e04.bdrip.x264-reward.eng.srt subtitle stream
/Users/name/Downloads/media/complete/nnnn.mp4 created
/Users/name/Downloads/media/complete/nnnn.mkv deleted
/Users/name/Downloads/media/complete/nnnn.eng.srt deleted
Processing episode /Users/name/Downloads/media/complete/nnnn.sample.mkv
Video codec detected: h264
Audio stream detected: aac eng [Stream 1]
Subtitle stream detected: subrip eng [Stream 2]
Subtitle stream detected: subrip eng [Stream 3]
Attempting to download subtitles, please wait
External subtitle file detected, language eng
Importing halt.and.catch.fire.s01e04.bdrip.x264-reward.sample.eng.srt subtitle stream
/Users/name/Downloads/media/complete/nnnn.sample.mp4 created
/Users/name/Downloads/media/complete/nnnn.sample.mkv deleted
/Users/name/Downloads/media/complete/nnnn.sample.eng.srt deleted
/Users/name/Downloads/media/complete/nnnn.eng.srt deleted
Script triggered from SABnzbd, starting nzbDroneFactory...
Loading config from /Applications/media/mp4_automator/autoProcess.ini
{
"name": "DownloadedEpisodesScan",
"body": {
"sendUpdatesToClient": false,
"sendUpdates": false,
"path": "/Users/name/Downloads/media/complete/nnnn",
"completionMessage": "Completed",
"name": "DownloadedEpisodesScan",
"trigger": "manual"
},
"priority": "normal",
"status": "queued",
"queued": "0001-01-01T00:00:00Z",
"trigger": "manual",
"state": "queued",
"manual": true,
"startedOn": "0001-01-01T00:00:00Z",
"sendUpdatesToClient": false,
"id": 12399
}
Response code: 201
Name: DownloadedEpisodesScan
StartedOn: 0001-01-01T00:00:00Z
Traceback (most recent call last):
File "/Applications/media/mp4_automator/nzbToNzbDroneMP4.py", line 36, in
nzbDroneFactory.scan(sys.argv[1], sys.argv[7])
File "/Applications/media/mp4_automator/nzbDroneFactory.py", line 81, in scan
print 'StateChangeTime: ' + str(pyobj['stateChangeTime'])
KeyError: 'stateChangeTime'
A note is that the file is actually getting converted and moved but I just cannot figure out why I would be receiving such an error. Have you seen anything like this?
Thank you!
Dianna

Hm I have not see that error before, off the top of my head I'm not sure what would cause that. I also notice it looks like you're using a pretty old version of the script since you're using the nzbDrone file and that file hasn't existed as part of the script for a long time. NZBDrone doesn't really exist anymore and has been replaced by Sonarr and the script has been updated to reflect that.
My recommendation would be to update over to Sonarr and grab the latest version of the script to go with it. Not sure where that error is coming from honestly.

I was aware of the brand change from nzbdrone to Sonarr and I plan on getting the automator updated. ;)
Maybe that will resolve my issue. I was using it before the rebrand which is how I happened upon your automator. I guess I just missed an update notification for the automator. Hopefully I've also fixed that now.
Again, thank you for the time and effort you put into this!

No problem! Gonna close  this issue for now, if you're still having problems after the update feel free to reopen and I'll see if I can help. Enjoy.


add infix:<∘> to Operators

For some strange reasons it's only in Callable.

what is its precedence?

Same as concatenation (~).

@gfldex Here is a fix db05b11515 . if it satisfies the issue, we can close this one :-)

close via  db05b11


Ingest: load data from LoC

@jamieparkinson can you close this please as I think it's done

It'll be closed automatically when the PR is merged!


Issue #10394: Compute boundingSphere correctly for models created from glTF

This is a pull request aiming to fix #10394. When glTF version 2.0 support was added for models, most likely the only part of the code that was tested was the modelMatrix that determines where the models are drawn, but the logic for bounding spheres was broken.
In current version of Cesium, models created from glTFs that are model-to-world transformed have their bounding spheres in a different place than where the models actually are.

Thanks for the pull request @VsKatshuma!

:x: Missing CLA.

Please send in a Contributor License Agreement (CLA) and comment back here to let us know to check this!
Maintainers, here's how to check for a submitted CLA.

:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

@lilleyse Would you be able to confirm this? See https://github.com/CesiumGS/cesium/issues/10394 for the rationale.

Hi @VsKatshuma,
Thanks for the PR! Can you sign an individual Community License Agreement before I review this PR?

My GitHub user should be under a newly submitted Corporate CLA. Do I also need to sign an individual agreement despite this?
I had not commented on this yet since there seems to be one test that's failing for me. I'm currently looking into it.
Regardless, I'm a bit concerned. Suppose I'm right and computing the bounding sphere has always skipped one transformation. But what if Cesium's users have understood this as the intended functionality, and have constructed their solutions accordingly. Then "fixing" this issue in Cesium has the potential to break other apps.
Then again, the functionality should ideally be correct at the source. I thought about applying the missing transformation in our project, but thought it would be more proper to correct the issue in Cesium instead.

Hi @VsKatshuma,
My mistake, I didn't realize you put it under the corporate CLA. You're good to go.
I think what you have is correct. It's similar to the model matrix update code in update, and the transformations that computedModelMatrix undergoes should be similar to the ones for the bounding sphere. https://github.com/CesiumGS/cesium/blob/46ed67c0bf601b52f3b1acdb7bb13d5decc5a181/Source/Scene/Model.js#L5524-L5544
If we log this change in CHANGES.md as a bugfix, then I think people can adapt their code accordingly if the change breaks their programs.

@VsKatshuma The renders with model matrix test failure has been noted for a while, so no worries. I wonder if it's possible to add a unit test for this change in ModelSpec, though?
Yes, please feel free to add the line to CHANGES.md yourself!

@VsKatshuma Merging now; thanks for the contribution!


vue-validator, webpack - no errors but not working

Hi,
I am confused what's going on.
I have no errors in console but vue-validation is not working at all.
I am using webpack in my project.
Here is main.js :
import Vue from 'vue'
import ep_panel from './ep_panel'

Vue.use(require('vue-resource'));
Vue.use(require('vue-validator'));

/* eslint-disable no-new */
new Vue({
  el: 'body',
  components: { ep_panel }
});

In my component I have:
<validator name="eventVal">
    <form novalidate>
    </form>

{{ $eventVal | json }}

</validator>

Anything else inside is just form.
I tried to put v-validate but after having no success and v-if="$eventVal.valid" is totally not working,
I removed everything to just check if anything is working with vue-validator.
I am getting empty

 in browser and I have no idea why.
Should validator be visible in VueDevtools or not? It's not now.
vue-validator ver. 2
I will appreciate your help.

Should validator be visible in VueDevtools or not? It's not now.

validator don't integrate vue-devtools.

I tried to put v-validate but after having no success and v-if="$eventVal.valid" is totally not working,
I removed everything to just check if anything is working with vue-validator.

Can you provide the minimum codes please?

Can you provide the minimum codes please?

@kazupon what you want exactly? I've provided all relavant code. What else you need? I am really confused why it is still not working.

Sorry, In my enviroment, I tried to   reproduce, but I could not confirmed.
I hope that you provide the reproduction info (minimum codes, error call stacks,etc ...) to me.

I can even send you whole project if you want? Any email ?
2016-05-05 16:28 GMT+01:00 kazuya kawaguchi<EMAIL_ADDRESS>
Sorry, In my enviroment, I tried to reproduce, but I could not confirmed.
I hope that you provide the reproduction info (minimum codes, error call
stacks,etc ...) to me.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue-validator/issues/212#issuecomment-217186189

I can even send you whole project if you want? Any email ?

I hope that provide web code sharing tool (jsfiddle, webpackbin, etc)

It is my duty to clarify it: I had attached vue.js inside my html template when I already have it compiled within my webpack built file and it was causing this issue. sorry!

That's okay 😺


Stellae - Remove Activator as a dependency

Bug Report
Stellae - Remove Activator as a dependency
Tweak/Theme:

Stellae
Version:

1.2
Device:

iPhone 7 Plus
iOS Version:

12.1

Issue/Bug:

Activator causes SpringBoard on my device to crash. I cannot have Activator installed, but Stellae now requires Activator as a dependency even though it only is used for actions. (Activator is version 1.9.12.)

Additional Comments:

I have migrated over to Activator instead of using a awful hacked-together time checking method. Activator is now nearly required for this tweak to work. Try updating Activator to v1.9.13~beta4 from https://rpetri.ch/repo/


SPR, ADL, SNB: Event updates

Update event files for SPR, ADL, and SNB.

SPR, ADL: Add new events and update descriptions.
SNB: Trim leading whitespaces and fix spelling issues.

Merging. These are direct copies of files reviewed and approved internally.


Fix overloading bug

Function parameters for overloaded functions are empty.  We need to implement overloading using the multimethod packaage.

Fixed in #28


[YUNIKORN-2112] Add the install cluster section in the e2e README

What is this PR for?
Make the e2e README more comprehensive.
Add the new option in https://github.com/apache/yunikorn-k8shim/pull/713
What type of PR is it?

[x] - Improvement

What is the Jira issue?
YUNIKORN-2112

@wilfred-s @craigcondit  please take a look !


Hints for the solution of exercise <IP_ADDRESS>

@andreas-roehler  Here are some hints for solution<IP_ADDRESS>
The solution should not use var.
I suggest that type Acc should include the current value of the index as well as the resulting sequence.
You wrote a loop that works. The loop goes like this:

Initially, counter = -1 and the sequence is empty.

At each step, counter = counter + 1 and the sequence is modified as well.

To reformulate this as a fold, you try writing code like this:
def zipWithIndex[A](xs: Seq[A]): Seq[(A, Int)] = {
   type Acc = ???
   val init : Acc = ???
   val update: (Acc, A) => Acc = { case (previousAcc, x) =>  ??? }
   xs.foldLeft(init)(update)
}

The type Acc must hold all data that is being updated by the loop. In your case, this is both the counter and the sequence.
So, the accumulator must be a tuple: Acc = (Int, Seq[A]).
Now you can rewrite your loop as a foldLeft. No more var anywhere.
You just need to write init and update.
The function update will look like this: { case ((previousCounter, previousSeq), x) =>  (newCounter, newSeq) } where you need to write the correct expressions for newCounter and newSeq.

Close this?


fixes issue #1816 support specifying kick and ban msgs

Signed-off-by: Arash Tabrizian<EMAIL_ADDRESS>

It fixes #1816.


Price Token Delimiter Switch

Fixes following issues|Adds following features:

Issue/Feature 1
Switches new price tokens from [[ ]] to (( ))

Resolves: MWPW-NUMBER
Steps to test the before vs. after and expectations:

Steps for feature 1

Pages to check for regression and performance:

https://--express--adobecom.hlx.page/express/?martech=off

@echen-adobe
There's no ticket number for this. The test link is missing.


Eyetracker refactor

added new class to abstract out the implementations for activate, start_tracking, and stop_tracking

WIP - DO NOT APPROVE AND MERGE

Merged simulation socket code branch into this branch


How do we enable this?

I cannot find where to enable this after installation - can you provide some screenshots please? Thanks!

Hi, if you are using Azure DevOps Server (on-premise) you need to click on your profile in the upper right corner, then select the Manage features option, and then just turn on the Query Gantt feature. The feature needs to be enabled per project.

If you are using Azure DevOps Services you can follow the instructions described here https://learn.microsoft.com/en-us/azure/devops/project/navigation/preview-features?view=azure-devops.

For Azure DevOps Services this is not available in preview features using 'for me' OR 'for this organisation':

Ticket should be reopened

Hi Nick,
I just uploaded the new v1.1.1 version,  where the feature is enabled by default, so please, try to update (or uninstall and than install the extension), and you should be able to use the extension:

Thanks - I can see it now :)
Is there any plan to make it a preview feature?


Inline style not worked

I use inline style for color and background-color but it didn't work. Other rules work just fine, it seems.

Same here i used inline style, the pdf generated is not rendering it

Same issue. All inline styling seems to be ignored.


no jaeger-query service visible in UI when in production mode with external elasticsearch storage

Hi there,
deployed Jaeger instance v1.21.0 using Jaeger Operator using an external elasticsearch cluster on kubernetes cluster.
Everything looks fine from logs and ES indices point of view and i can see the span write index growing over time. no errors or whatsoever. collector and query pods also running fine.
I have set use-aliases: true for collector and query components. However, the only problem that I have is that I don't see the jaeger-query service in the list of services for the UI, so wondering what could be the problem or verify that everything works as expected. Is this normal behaviour ? Because, with memory storage and all-in-one installation I can see the jaeger-query in the list of services on the UI.
logs from collector below:
{"level":"info","ts":1613142339.5422573,"caller":"flags/service.go:117","msg":"Mounting metrics handler on admin server","route":"/metrics"}
{"level":"info","ts":1613142339.5422943,"caller":"flags/service.go:123","msg":"Mounting expvar handler on admin server","route":"/debug/vars"}
{"level":"info","ts":1613142339.5429192,"caller":"flags/admin.go:121","msg":"Mounting health check on admin server","route":"/"}
{"level":"info","ts":1613142339.542986,"caller":"flags/admin.go:127","msg":"Starting admin HTTP server","http-addr":":14269"}
{"level":"info","ts":1613142339.543018,"caller":"flags/admin.go:113","msg":"Admin server started","http.host-port":"[::]:14269","health-status":"unavailable"}
{"level":"info","ts":1613142339.780908,"caller":"config/config.go:179","msg":"Elasticsearch detected","version":7}
{"level":"info","ts":1613142339.7914138,"caller":"server/grpc.go:76","msg":"Starting jaeger-collector gRPC server","grpc.host-port":":14250"}
{"level":"info","ts":1613142339.7915013,"caller":"server/http.go:44","msg":"Starting jaeger-collector HTTP server","http host-port":":14268"}
{"level":"info","ts":1613142339.7921262,"caller":"server/zipkin.go:49","msg":"Listening for Zipkin HTTP traffic","zipkin host-port":":9411"}
{"level":"info","ts":1613142339.820321,"caller":"healthcheck/handler.go:128","msg":"Health Check state change","status":"ready"}

Please let me know if you require any further info. Thank you!

Could you please provide the minimal CR that is able to reproduce this problem? Also, you might want to check the metrics on the collector side, especially the "saved by service". It should show you how many spans/traces were saved for jaeger-query.

hi @jpkrohling, thanks for your reply.  Please find below the spec part (with <> placeholders for relevant values):
spec:
    strategy: production
    collector:
      maxReplicas: 3
      options:
        es:
          use-aliases: true
    query:
      options:
        es:
          use-aliases: true
    storage:
      type: elasticsearch
      options:
        es:
          server-urls: <server-url-to-external-elasticsearch>
          username: <elasticsearch-username>
          index-prefix: "stable"
          create-index-templates: false
      secretName: <elastic-secret-name>
      esIndexCleaner:
        enabled: false
      dependencies:
        enabled: false
    ingress:
      enabled: true
      annotations:
        kubernetes.io/ingress.class: nginx
        kubernetes.io/tls-acme: "true"
      hosts:
        - <jaeger-hostname.com>

@rubenvp8510 could you please give this a try?

@jpkrohling , @rubenvp8510, tried some configs on local minikube with an es cluster (elastic/kibana helm charts) and even when deploying the business-application-injected-sidecar.yaml from the examples, the UI doesn't pick it up, ie is not showing. The only way I managed to make it work was to set the use-aliases to 'false' for query and collector and set the global es use-aliases:true, so with cronjobs creation, this worked fine, but is not what I'm after. (the point is to use ILM in ES/kibana to manage this). Could you please try to reproduce it ? Thanks in advance.

figured it out in the end. It was a matter of creating rolling the indices for spans and service, with write AND read aliases with specific naming in ES. For others that might have the same problem/issue, is what I did:

set create-index-templates: true. Deploy jaeger with collector and query aliases set to true (as shown above).
in ES: delete any auto-created indices and aliases, if the get created automatically by Jaeger, but NOT the auto created templates.

{
"aliases": {
"-jaeger-span-write": {"is_write_index": "true" },
"-jaeger-span-read": {"is_write_index": "false" }
}
}
PUT -jaeger-service-000001
{
"aliases": {
"-jaeger-service-write": {"is_write_index": "true" },
"-jaeger-service-read": {"is_write_index": "false" }
}
}
4) create policies for span and service indices and attach the corresponding auto-created templates to them.

and thats it, then query-service should show up in Jaeger UI + any other services that send traces.

two remarks:

1) this should be documented somewhere ie about step 3), ie naming conventions of aliases especially. I figured this out, by setting first initially `es.use-aliases: true` and observe the indices that get autocreated in this case by Jaeger in ES. Is when I noticed that there are two aliases (one read and one for write) attached to each index.

2) one downside is that the autocreated templates comes with some settings/mappings, eg. create 5 primary shards for each index. It can be changed of course in Kibana, but if pods restart, then settings are again overriden by these Jaeger defaults. Thought about setting `create-index-templates: false`. but templates contain too may settings/mappings, and future release might change something there. So decided to let Jaeger auto-create at least the templates.

so with cronjobs creation, this worked fine, but is not what I'm after.

That clarifies it!

this should be documented somewhere ie about step 3), ie naming conventions of aliases especially. I figured this out, by setting first initially es.use-aliases: true and observe the indices that get autocreated in this case by Jaeger in ES. Is when I noticed that there are two aliases (one read and one for write) attached to each index. (You can also log the autocreated rollup cronjob which shows same info)

Great work there! Would you mind opening a PR against our documentation to mention this? I wouldn't leave the PUT calls there, and would rather link the documentation to this issue here, so that other people can see the discussion. My concern is that the documentation might get outdated, confusing people even more. Your description will make people find out how to make it work.

So decided to let Jaeger auto-create at least the templates and don't touch them.

That's a wise decision. Do you think there's anything we can do our side to help in this case?

sure, could open a PR. could you point me where exactly, which section, line ? as you suggested I would just mention something like  For more info on how to setup ES with indices aliases correctly, please refer to this issue on Github. Sounds right ?
Regarding the templates, not sure how it could be, but for example it should be maybe possible to define at least the number of shards (and maybe replicas ?) and not fixed it at 5 primary shards for example.

Where would you have looked first? I would say somewhere here: https://www.jaegertracing.io/docs/1.22/deployment/#elasticsearch
The code for this page is located here: https://github.com/jaegertracing/documentation/blob/master/content/docs/next-release/deployment.md

@jpkrohling , can't push to docu repo it seems. Here is what wanted to add:
For guidance on how to make use of ILM with rollover indices and use-aliases flag for collector and query components, you can refer to this [Github issue](https://github.com/jaegertracing/jaeger-operator/issues/1390)


[Bugfix] Fix weight loading issue by rename variable.

Fix #8186: [Bug]: Phi-3.5-MoE-Instruct on vLLM produces weird strings
Some commit introduced the change of weight loading procedure. PhiMoE should also modify this weight names to load weight into correct tensor.

/ready

Hi @wenxcs, is there any plan to merge this one soon and release a version with this fix?
Thanks.

Thanks for the ping @lhcavalcanti


Bug: HTTP Feature Testing only runs the FIRST test

Describe the bug
HTTP Testing is not working properly.
This bug happens when the controller is locates under folder structure.
e.g.: App/Controllers/Folder/Another/Example.php
When running PhpUnit tests only the 1st test will pass, the other tests will return a ERROR:
CodeIgniter\Exceptions\PageNotFoundException: Controller or its method is not found: App\Controllers\Folder\Another\::example
If you change the methods order, the test that previously passed will now return a ERROR if it is not at first position.
If the Example.php controller is located under App/Controllers/Example.php all the tests will run normally.
CodeIgniter 4 version
4.0 rc3
Affected module(s)
HTTP Feature Testing
Expected behavior, and steps to reproduce if appropriate

Add more methods to Home.php controller.
Place the Home.php under App/Controllers/Folder/Another/Folder/Home.php
Test it using the HTTP Feature:

<?php namespace App\CI4\Controllers;

use CodeIgniter\Test\FeatureTestCase;

class HomeControllerTest extends FeatureTestCase
{

    public function setUp(): void
    {
        parent::setUp();
    }

    public function tearDown(): void
    {
        parent::tearDown();
    }

    public function testSimple()
    {
        $test = defined('APPPATH');
        $this->assertTrue($test);
    }

    public function testShowHomeIndex()
    {

        $result = $this->get('Folder/Another/Folder/Home/Index');

        $this->assertTrue($result->isOK());
    }

    public function testShowHomePage()
    {

        $result = $this->get('Folder/Another/Folder/Home/Page');

        $this->assertTrue($result->isOK());
    }

    public function testShowHomeMain()
    {

        $result = $this->get('Folder/Another/Folder/Home/main');

        $this->assertTrue($result->isOK());
    }
}

This doesn't sound like a FeatureTestCase issue - but a namespace issue with your class. If the class file is located at App/Controllers/Folder/Another/Folder/Home.php.
I've got an example over here that shows using multiple tests in a FeatureTest and they all run and work fine.

Hi sir !
Just tried it again... Didnt work...
Can you try calling it from :
$result = $this->get('Folder/Another/Folder/Home/Index');
In your example you called it from :
$response = $this->get('/');
It will work fine if the Home controller is routed to '/' ... but not if it is at a complex path location like 'Folder/Another/Folder/Home/Index'
Can you put your home controller inside Folder/Another/Folder/Home and tell me if it works ?
Can you show me you home controller ?
THANK YOU VERY MUCH MY FRIEND ! BTW, liked your patreon videos this month ! Thank you !

Also... The controller would not work with a wrong namespace....
:-1:

Thanks for the kind words about the vids. Glad you enjoyed them!
I'll hopefully get a chance to try this tonight. But quick thought - are you using the current develop branch? There were some URL-related fixes that happened since RC3 that might have an impact here.

No ! Will give it a try with the develop branch ! Will post the results very soon ! Thank you for looking this up !
I got stuck with testing because of this ...
=D

@4mesolutions Any update? Were you able to try your tests against the latest from develop?

I checked this issue today and it's valid. After some digging, I found the reason and solution.
So, the problem is here: https://github.com/codeigniter4/CodeIgniter4/blob/develop/system/Router/Router.php#L569
In a given scenario the first test is always passing without problems but the next ones are failing. This is because in the first test we don't have $this->directory set, so $segments array is "filtered" in a while loop. But when it comes to the next test, we already have $this->directory defined, so all segments are returned immediately, causing an incorrect path to a controller.
The solution is simple - just reset $this->directory after every test. I decided to not use a shared instance of the Router service because I don't see any benefits. I'm not sure if this can cause any issues coz I didn't play with Router before - but hopefully, it's gonna be ok.

Thanks for the thorough assessment - and your description makes a lot of sense. Looking at the PR, I’m a little uncomfortable changing that in the core but we can see what the tests say. I don’t imagine there are scenarios where someone would modify the request before the routing.

Yes, I wasn't sure about this change either but frankly, I had no other idea where to put it. We'll see how it goes.

After fixing one test it looks good. But I don't know why this test was passing before. When I tried to run only this one file ./vendor/bin/phpunit tests/system/Config/ServicesTest.php without my changes, tests were failing too, so... a mystery.
Well, it's up to you guys. If you see a better solution - go for it. At least we now know where the problem is.

The problem with using a non-shared instance of the router is that it makes it impossible to poll the Router later for what controller name or method name was used, and other stuff like that.
Maybe we could make CodeIgniter's setDirectory method public and allow it to actually be set to null, then have the FeatureTestCase reset that?

I made a new pull request with suggested changes.

I was wondering why you closed, but I like this solution. Waiting on tests...

Re: tests failing... I saw this during the refactor. There were tests passing in TravisCI that would fail locally for me, and would even have errors (like unmatched class names). I’m not sure if it was some weird caching thing but it has me a little uncomfortable.

Actually, when I run tests locally some of them are failing, but it has something to do with my environment or configuration I guess.


[TS migration] Migrate 'PinButton.js' component to TypeScript

Details

Fixed Issues

$https://github.com/Expensify/App/issues/25061
PROPOSAL:
Tests

Open MoneyReportHeader.js and change shouldShowPinButton to true
Open any money request and verify that the pin is displayed
Click on it and observe state change

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Open MoneyReportHeader.js and change shouldShowPinButton to true
Open any money request and verify that the pin is displayed
Click on it and observe state change

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
android-native-converted.webm

Android: mWeb Chrome
android-web-converted.webm

iOS: Native
https://github.com/Expensify/App/assets/23215729/dddcff1f-8503-4153-b228-e517bbe59679

iOS: mWeb Safari
https://github.com/Expensify/App/assets/23215729/7ed2c8c3-eee5-4ac1-94ba-c6604603071f

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/23215729/4055ed6a-2065-4495-99fa-a97d40892a62

MacOS: Desktop
https://github.com/Expensify/App/assets/23215729/52b9074a-6721-490f-bdd0-521712893809

@pasyukevich remove [No QA] from the PR title please

Resolve conflicts and record videos @pasyukevich

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/stitesExpensify in version: 1.4.14-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/stitesExpensify in version: 1.4.14-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@kubabutkiewicz @blazejkustra @stitesExpensify Can you pls help us with QA steps. How do we test this in Staging in UI?

@mvtglobally There is no way to test it on stage currently. (since the flow includes hardcode)

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.4.14-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Critical issue app:tickCount Sometimes wrong working

my app is crashed, i'm see stacktrace and log
I' m set a ' app:tickCount="17" ' in xml but log  java.lang.IndexOutOfBoundsException: Invalid index 20,
crash because rightThumb swipe and swipe swipe to Right

Did you resolve this issue?


Updated cqm-models version to 3.0.4

Updated cqm-models version to 3.0.4
Pull requests into cqm-parsers require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Hi @dczulada, do we need to release this library? cqm-models changes are mainly related to calculation(cql-execution)

@adongare this shouldn't be required

Thanks @dczulada, will closing this PR.