Distro packages for containerd

While we are working on the 1.0 milestone we need to start thinking about packaging.  We want to work with distro maintainers to produce and maintain containerd packages.
You should be able to apt-get install containerd or dnf install containerd without adding custom sources as a user.
Distro Checklist:

[ ] Debian
[ ] Ubuntu
[x] Fedora
[ ] Arch
[ ] Alpine

@tianon Any help or recommendations about pointing us in the right direction would be appreciated.

This is definitely something I'd love to see/help with! :heart:
Right now, the situation is somewhat complicated by the existence of containerd 0.2.x and its use by Docker (which for many/most distributions means they've already got a "containerd" package, but it's packaging the 0.2.x branch for use with their associated Docker package; ala https://packages.debian.org/sid/containerd, https://packages.ubuntu.com/artful/containerd, etc).
Once Docker is using containerd 1.x as well, I think that particular problem can largely go away though. :+1:

@tianon why wouldn't they package it like we did, docker-containerd?

Would we package 1.0 and have docker packages depend on the older tags?

why wouldn't they package it like we did, docker-containerd?

Because it was created, published, and distributed as a separate project which Docker just happens to use.  The source for it isn't even vendored in Docker itself, although for packaging that doesn't matter as much since most distros require purging the vendoring anyhow (usually called "code copies" in distro policy, which are considered a security issue).

Could we package 1.0 and have docker packages depend on the older tags?

So, in many distros, you only get one version of a particular package at a time.  In Debian, the way this sort of situation is often handled is via ugly package names like php5.6 or golang-1.8-go, combined with a metapackage like php or golang-go.  This could potentially be handled by introducing something like a new containerd0 package or a new containerd1 package (at least in Debian), but that's not exactly ideal.
If we can get Docker itself using containerd 1.x, then "all" we have to do is update Docker in the distributions (although that's definitely non-trivial due to the massive constantly-changing dependency tree of Docker's source).
So, TL;DR, the way Docker uses deps and the re-use of the containerd name for 0.2 vs 1.0 (which are arguably very different now) makes this a bit complex, although solvable.

Do you know who works on the fedora packages?

I'm not sure, but I think @lsm5 and/or @maxamillion are either still involved or might be willing to redirect us to the correct folks. :smile: :pray:

I'll get this going for fedora

what's the ETA for v1 GA? I'll try and get the fedora package approved before that

I don't mind going either way.  For Debian either using an ugly package name to have both docker-containerd and containerd is fine with me.  I'm a bit skeptical that Docker will move (and stick to) a released version of containerd but will be ecstatic if that happens. (-:

On second thoughts, I'd prefer if @maxamillion or maybe someone from containerd community could take the lead in packaging and maintaining this for Fedora. I could happily review and approve the package request and maybe co-maintain it, but it'll be hard for me to dedicate time for this, what with 4 distros on my back now. Apologies :(

@lsm5 no problem.  Getting started is the hardest part for someone new like us.  If Max is not able to do it, any pointers would be appreciated.

I can do an initial packaging but I don't know that I could commit to being the long term maintainer of the package. I'm spread pretty thin as it is.

I'm new to containerd.  Is the end goal to ship a containerd command to end users?  Should it be run as a service, such as via systemd?  Should the source code be shipped for other packages to build against?  From the README:

containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users.

@crosbymichael no problem, if you know of someone willing to volunteer, I can work with them toward seeing this through.

@carlwgeorge It would run as a systemd service on systems that support systemd.
Even if it is not a user facing service, other packages that depend on containerd will need a containerd package in their dependencies that gets installed.
Having a package also allows containerd to be updated independently of software that depends on it.

Not sure if this justifies it's own issue or not, but since it's directly related to packaging I'll ask here first: would it be possible to add a manifest file in the vendor directory that lists the vendored dependencies and their revision (example)?

@carlwgeorge is that type of manifest read by packaging programs?  I only ask because we have the vendor.conf file and want to make sure that things don't get out of sync with what is actually vendored.

@crosbymichael Oh, I didn't notice that file before; that will work fine.  AFAIK there isn't a standard packaging tool that reads the manifest file, I just wanted something I can programatically query with a python one-liner or awk to generate the info needed to comply with packaging guidelines for bundled libraries (example).  That vendor.conf file is actually already closer to the format I need than a json manifest file anyways.

Perfect!

@carlwgeorge here is the code for parsing the vendor.conf files:
https://github.com/LK4D4/vndr/blob/master/clone.go#L24
Just incase its helpful to anyone.

@carlwgeorge thanks for picking this up, please assign me as reviewer once you put up an rpm spec for review!

I've got some RPMs available in a COPR repo for initial testing.  I hit up @crosbymichael on IRC and he clarified that the main goal is to ship the following files:

/usr/bin/containerd
/usr/bin/containerd-shim
/usr/lib/systemd/system/containerd.service

The repo has packages for EL7, Fedora 26, Fedora 27, and Fedora Rawhide.  Please try them out and let me know if anything is wrong/missing.  In particular I'm wondering if including a default configuration file is appropriate.

@carlwgeorge thanks!  I'll check these out today

@carlwgeorge Awesome!
I just tested this on f26 and it worked flawlessly.  I was able to enable the service and run containers without anything else being installed.  Really good work and thanks so much.
The only thing I'm considering is if we should add ctr or not.  @stevvooe @dmcgowan what do you think?  Should we keep it out of packages for now until we can support it or include it as a dev tool that is installed along side containerd?

@crosbymichael There is some diagnostic functionality in ctr that helps a lot. Having it in place seems important. I don't know if we can put a banner on it that prints out a big warning message every time. We can also place a warning in the manpages. If we ship it, there is a 100% chance someone will rely on the behavior of ctr, if with those measures.
I am really not sure if unstable or missing is worse here.
We could ship it as ctr-unstable or ctr-spidercave or something that will make it obvious.

@stevvooe we can always have the binary on our release page that people could download

I updated the packages in that COPR to include:

a default config file using the output of containerd config default
/usr/bin/ctr, with a conditional flag to disable it later if needed

If needed, it would be trivial for me to rename the ctr binary to ctr-unstable in the RPM spec file without any upstream changes.

How do we support installing multiple versions of containerd simultaneously? e.g. v1.0 and v1.1.
What would be binary names, socket paths, and config paths?

@AkihiroSuda In the RPM ecosystem, in order to have multiple versions of an application installed, you need to use alternate package names (containerd11, docker-containerd) and file locations (/usr/bin/containerd-1.1, /usr/bin/docker-containerd).  But even when you do that, you can only have one package of an exact name installed at a time.
Here are the files in the package I created:

/etc/containerd/config.toml
/usr/bin/containerd
/usr/bin/containerd-shim
/usr/bin/ctr
/usr/lib/systemd/system/containerd.service

@AkihiroSuda that is not a usecase or priority.  Packages just don't do that nor should they.  Its not a package concern.

@carlwgeorge both are good.
What happens after its approved on the official review?  Since we are still in beta and working towards the 1.0 RC then GA release, does the version in the package reflect this?

On Tue, Oct 10, 2017 at 03:02:18PM +0000, Michael Crosby wrote:

@carlwgeorge both are good.
What happens after its approved on the official review?  Since we are still in beta and working towards the 1.0 RC then GA release, does the version in the package reflect this?

Yup, the release string will have "rc" in it.

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/containerd/containerd/issues/1508#issuecomment-335502426

--
Lokesh
IRC: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5

@carlwgeorge
ok
Btw, please add runc version constraint to http://copr-dist-git.fedorainfracloud.org/cgit/carlwgeorge/containerd/containerd.git/tree/containerd.spec ?

@crosbymichael After the official review, it will be added to the main repos, so users don't have to add the additional COPR repository.  As @lsm5 mentioned, pre-release versions are annontated with a unique release field.  Currently the package is containerd-1.0.0-0.2.beta.1, which is a version of 1.0.0 and a release of 0.2.beta.1.  I'll increment the release as needed for future betas and release candidates (0.2.beta.2, 0.3.rc.1, etc), and the final 1.0.0 will have a release of just 1 (higher than all the previous 0.* releases).
@AkihiroSuda What is the minimum required version of runc?

Currently https://github.com/containerd/containerd/blob/master/RUNC.md , but will be runc 1.0 GA in containerd 1.0 GA

@AkihiroSuda Targeting a specific commit requirement is not tenable within the spec file.  The RPM dependency resolver has no way to know the relationship between the commits.  The only way to do it would be to maintain a mapping of all the RPM releases to their respective commits, then manually researching where the required commit falls in that commit history, and requiring the RPM release that follows that commit.  In fact, checking the existing versions of runc shows me that I can't meet that requirement until Fedora's runc is updated to 0351df1 (2017-09-26) or newer.
Fedora: runc-2:1.0.0-10.rc4.gitaea4f21 built from aea4f21 (2017-09-01)
RHEL: runc-0:1.0.0-12.1.gitf8ce01d built from f8ce01d (2017-04-21)
I mention RHEL because I would eventually like to submit containerd to the EPEL repository so RHEL and CentOS users can take advantage of it as well.
How strict is the minimum version requirement?  If it only matters for certain advanced features, and if the required commit is going to be a fast moving target, I would be content to just have my package require runc >= 1.0.0.  That would be close enough for now, and I could modify it later to require the version-release that corresponds to the first 1.0 GA version (i.e. runc >= 1.0.0-30).

On Tue, Oct 10, 2017 at 06:32:08PM +0000, Carl George wrote:

I mention RHEL because I would eventually like to submit containerd to the EPEL repository so RHEL and CentOS users can take advantage of it as well.

I'd suggest sending CentOS Virt SIG instead of EPEL because you have a
lot more freedom over there RE: dep bumps v/s EPEL, but your call :)
--
Lokesh
IRC: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5

On Tue, Oct 10, 2017 at 07:04:25PM +0000, Lokesh Mandvekar wrote:

On Tue, Oct 10, 2017 at 06:32:08PM +0000, Carl George wrote:

I mention RHEL because I would eventually like to submit containerd to the EPEL repository so RHEL and CentOS users can take advantage of it as well.

I'd suggest sending CentOS Virt SIG instead of EPEL because you have a
lot more freedom over there RE: dep bumps v/s EPEL, but your call :)

In fact, you can get containerd into Virt SIG right away without waiting for
fedora review.
--
Lokesh
IRC: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5

We will depend on versioned releases of runc in the future post 1.0.
However, what is the best way to notify package maintainers when we release a new version of containerd with a runc bump? 1.0->1.1?  Is adding a note in our release notes good enough?

Yes, mentioning changes in the minimum required version of runc in the releases notes would be ideal.  Additionally, it would be useful to maintain a list of the minimum versions of dependencies in a well known location, such as the project README.  Your README already points out the minimum golang version required (1.8), which is why I already have that specified in the spec file as a build requirement.

@carlwgeorge thanks.  I'm sure we can get something setup to generate the release docs with this info.
cc @stevvooe @dmcgowan

I updated the COPR with 1.0.0-beta.2.  Unfortunately due to #1632 I won't be able to submit it to EPEL for RHEL/CentOS consumption.  In fact, I can't submit it to Fedora 26 either (current release).  It will only be for Fedora 27 (currently in beta) and up.

@carlwgeorge why don't they have go 1.9 packaged already?

@carlwgeorge i mean, you can always try to build with it but there is a race in IO until the distros can update to 1.9

Fedora has an updates policy dictating what is acceptable within a stable release.
RHEL has a compatibility policy as well as an extensive QA process.  Go is in the optional channel, which the policy doesn't apply to, so it can be updated, but there is still a long QA process.  Go 1.8 was released on 2017-02-16, and was added to RHEL 7.4 on 2017-08-01.
CentOS rebuilds RHEL sources, so are at the mercy of Red Hat's decisions.  The CentOS SIGs have the freedom to override base RHEL versions, but those aren't enabled by default.
Maybe the best approach would be to phrase it as "1.8 required, but 1.9 recommended"?

@carlwgeorge i could live with that.  Lets see what @stevvooe and @dmcgowan think

containerd approved on fedora, @carlwgeorge will handle the rest. Enjoy!!

Nice.  Thanks @carlwgeorge && @lsm5

@carlwgeorge/@lsm5 when will the Fedora package db reflect the inclusion of containerd? Currently, I am not seeing anything..

@mataneja PackageDB was deprecated.  containerd is distgit, and packages have been published for Rawhide and F27 (currently still in updates-testing).

I have pushed containerd-1.0.0-0.5.beta.3.fc27 (1.0.0-beta.3) to the Fedora 27 testing repo, if anyone wants to help test it.

The Arch package (https://www.archlinux.org/packages/community/x86_64/containerd/) was updated shortly after the official release. cc @seblu who seems to be the primary maintainer (hope you don't mind the ping).
We may be able to check that one off the list.

Hi,
Yes, the job is done on Arch Linux. You can do pacman -S containerd without adding external sources.
Cheers,

Alpine also looks to be updated in edge: https://pkgs.alpinelinux.org/package/edge/testing/x86/containerd
cc @ncopa

@crosbymichael Might want to mention here whether or not there is an intention to support 32 bit .. 386 distro variants or just 64bit.  See #2099

My suggestion is for the team to focus on 64-bit only as priority 1 and leave 32-bit for later.

Ping on this, for Ubuntu, Debian, CentOS & RHEL.
Have you considered hosting your own repo?

Regarding RHEL/CentOS, the best place for this would be EPEL (I already package it in Fedora).  However, containerd 1.1.0 bumped the minimum golang version to 1.10, and RHEL7 only has golang 1.9.  EPEL packages aren't allowed to override/update stock RHEL packages, so we're stuck waiting on Red Hat to update golang.  To their credit, it's happened multiple times in RHEL7's lifecycle (from 1.2 all the way to 1.9), so I would say there is a good chance of it happening.  I just worry that by that time containerd will have bumped to an even higher minimum version of golang.

Hey guys, I am working on the debian package for containerd (and runc).
https://github.com/godarch/debian-repo-source/tree/master/containerd/debian
I don't like the idea of my having debian/ in an external repository. I think it should exist in containerd and runc.
What do you guys think? If I make a pull request, would you guys be receptive to me adding the required debian/* files?

@pauldotknopf Are you coordinating with the people already working on the containerd packaging? See e.g. https://salsa.debian.org/arnaudr-guest/containerd and https://salsa.debian.org/go-team/packages/runc
In general, I'd recommend against merging the debian/ subdirectory with the upstream project. The packages can and typically are updated on a different schedule from the upstream release schedule. You'll want to be able to tag your package release commits independently from the upstream releases. A common practice is for your packaging repository to contain only the debian/ subdirectory, and I'd recommend taking that approach if at all possible.

Hello,
Is there any repository where I can find debian files for containerd.io packages from here: https://download.docker.com/linux/ubuntu/dists/xenial/pool/stable/amd64/ ?
How are they built?
Thanks in advance.

@carlwgeorge could you share your rpm spec for centos-7, since we have some our patches on runc and we want to package the containerd again? Thanks in advance! :smile:

@carlwgeorge Thanks for your reply!

Strangely enough, containerd seems to build fine on RHEL 7 with the older protobuf 2.5.  I even built it without protobuf installed in the buildroot.  Protoc/protobuf 3.x is explicitly listed as a build requirement.  Am I missing something here?

@estesp Thanks for the clarification.  In distro packaging lingo, it sounds like protobuf is more of a development requirement rather than a build requirement.  Since I only care about going from a tagged tarball (with unmodified sources) to a distro package containing the binaries, I'll remove the protobuf BuildRequires in the Fedora spec file.  This should open things up for me to build containerd in EPEL for RHEL/CentOS 7.  I'm sure at some point the EL7 kernel version (3.10.0) will become problematic, but we'll cross that bridge when we get to it I suppose.

Can we please get the source (and debian-specific files) of Docker's containerd debian package?
As @skolekonov correclty pointed out, they are not open source and there is currently no way to debug/rebuild their broken containerd package for ARMv6 devices (i.e. Rasperry Pi Zero).
related: https://github.com/moby/moby/issues/38175

The original comment now has all 5 checkboxes marked; is there anything else we want to use this issue for, or should we close and handle any one-off discussions per distro (ongoing packaging or questions) as new issues? @crosbymichael

Centos please? :)

@kfox1111

Centos please? :)

I think @carlwgeorge said in a prior comment EPEL would be the location for a containerd package, which should make it available to CentOS as well as RHEL. I'm not sure if there is any more status since then, but hopefully Carl can weigh in.

@kfox1111 EPEL already has containerd-1.2.1-1.el7.  I'm a little behind the latest 1.2.6, but I can take a look at getting that updated.  According to https://github.com/containerd/containerd/blob/v1.2.6/BUILDING.md the minimum golang version is still 1.10, so I don't forsee any issues. :crossed_fingers:

1.2.1 is actually broken. See https://github.com/containerd/containerd/issues/2942 for details. It created quite a mess to fix.
1.2.4 would be a big help. 1.2.7 would be awesome. :)
Thanks,
Kevin


i18n(zh-cn): Update 0-introduction/index.mdx

Description (required)
Update 0-introduction/index.mdx
Related issues & labels (optional)

#9240
Suggested label: i18n

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

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

Tracked Files

File
Note

zh-cn/tutorial/0-introduction/index.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

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


How to convert image (jpg) to valid image txt

Hi.. anyone can help me. how to create valid_image.txt file?

probably too late...
you need to manually create it by following the format introduced here: https://github.com/felixchenfy/Realtime-Action-Recognition#data-format


algorithm for shrinklines and strechlines

Are the seed points chosen as a subset of points which satisfy some condition (like in DOI:10.1063/1.3690153)?

Apart from the removing orientation discontinuity part which is done locally now, is the remaining part of the algorithm similar to the one given in the DOI referenced above?

DOI:10.1063/1.3690153 pre-dates LCS Tool and is not a good reference for the algorithms in LCS Tool. For information on LCS Tool's algorithm's, read this document: https://github.com/jeixav/LCS-Tool-Article/.


docs: code of conduct

closes #59

Thanks, @TobiTenno, for creating the PR.
I agree with you that the emails from the romcal email address should be forwarded to each of us. If there is no such adress created, could create something like<EMAIL_ADDRESS>I presume<EMAIL_ADDRESS>(or some other TLD) would be the best though. :wink:
We could also use a suffix (or whatever it is called), e.g<EMAIL_ADDRESS>for specific stuff.
This email address could be used for sources shared with us privately (for now, I asked contributors to send them directly to me, however, it might be better to send them to a romcal email address, e.g. romcal+sources@...).

Anyway, why did you set Prettier to ignore MD files? :thinking:

Anyway, why did you set Prettier to ignore MD files? 🤔

@tukusejssirs I was seeing it reformat parts that seemed odd. I'll run it again and see if it doesn't look as messy.

Thanks, @TobiTenno, for creating the PR.
I agree with you that the emails from the romcal email address should be forwarded to each of us. If there is no such adress created, could create something like<EMAIL_ADDRESS>I presume<EMAIL_ADDRESS>(or some other TLD) would be the best though. 😉
We could also use a suffix (or whatever it is called), e.g<EMAIL_ADDRESS>for specific stuff.
This email address could be used for sources shared with us privately (for now, I asked contributors to send them directly to me, however, it might be better to send them to a romcal email address, e.g. romcal+sources@...).

@tukusejssirs
I'm happy to go make this, but I'd rather collab w/ you and @emagnier (probably privately for this kind of thing) and sync up

looks like i just wasn't looking close enough at the formatting it was prompting, @tukusejssirs, i've backed out the ignore and formatted the COC

I'm happy to go make this, but I'd rather collab w/ you and @emagnier (probably privately for this kind of thing) and sync up

Okay. When do you to have time for a quick chat regarding this? Where should we chat (gMeet, Discord, …)?
And sorry, I have disabled auto-merging for this PR unintentionally.

@tukusejssirs @emagnier email updated


RuntimeError: The size of tensor a (433) must match the size of tensor b (431) at non-singleton dimension 3

Hello, thank you for your excellent work!
I tried to set up the same environment using the guide you provided to run the offline demo.
However, I encountered an error related to a size mismatch between attention_mask and attn_weights. The error message is as follows:
2024-06-28 10:01:55 | ERROR | stderr |   File "/opt/conda/envs/llavidal_env/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 350, in forward
2024-06-28 10:01:55 | ERROR | stderr |     attn_weights = attn_weights + causal_mask
2024-06-28 10:01:55 | ERROR | stderr | RuntimeError: The size of tensor a (433) must match the size of tensor b (431) at non-singleton dimension 3
Could you please provide some hints on how to resolve this issue? Thank you!

Hello, thank you for your interest and very sorry for the late response!!
This issue happened because the demo was expecting object features, causing an input shape mismatch since our model does not use object features during inference.
I have fixed this in the most recent version of the code. Please pull the updated repo or change this single line in your own repo:

https://github.com/ADL-X/LLAVIDAL/commit/98970660d030f73429f1f4de0755eb1c040c6c68#diff-91bd1d661d4d29c71f521ab26fd6b809f8b082dcef05a220a4330b35842e4feeR187


Code error even on fresh install

Describe the bug
When you launch note block studio you get a code error with something about JPEG
To Reproduce
Steps to reproduce the behavior:

Open note block studio

Expected behavior
Note block studio opens normally

Hi! Can you please post a screenshot of the error?

Hi! Can you please post a screenshot of the error?

Partially fixed in 8bcb5b5ee79c71f916e957c3a0623569f97ea70f


Incorrect detection of OpenSSL-specific TLS certificate files on NixOS

Julia on the NixOS distribution complains about "NetworkOptions could only find OpenSSL-specific TLS certificate files which cannot be used by MbedTLS", which seems to be incorrect.
NixOS provides /etc/ssl/certs/ca-bundle.crt, which contains both certificate variants: -----BEGIN CERTIFICATE----- as well as -----BEGIN TRUSTED CERTIFICATE-----. An excerpt from the file is shown below.
It seems MbedTLS understands this file, which can be confirmed with the following code:
julia> using NetworkOptions
julia> ENV["JULIA_SSL_CA_ROOTS_PATH"] = "/etc/ssl/certs/ca-bundle.crt"
julia> download("https://google.com")
...
julia> ca_roots()
"/etc/ssl/certs/ca-bundle.crt"

Without setting the environment variable, the warning is printed and ca_roots() returns the bundled_ca_roots():
julia> using NetworkOptions
julia> download("https://google.com")
Warning: ...
julia> ca_roots()
"/nix/store/kwizqkjrky766m6vqcxs5qjvjxf5qjji-julia-bin-1.8.0/share/julia/cert.pem"

I suppose, that the warning should be shown only when the number of BEGIN CERTIFICATE lines is zero and not if the number of BEGIN TRUSTED CERTIFICATE lines is greater than zero.
Excerpt from /etc/ssl/certs/ca-bundle.crt on NixOS:
Amazon Root CA 3
-----BEGIN CERTIFICATE-----
MIIBtjCCAVugAwIBAgITBmyf1XSXNmY/Owua2eiedgPySjAKBggqhkjOPQQDAjA5
MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRkwFwYDVQQDExBBbWF6b24g
Um9vdCBDQSAzMB4XDTE1MDUyNjAwMDAwMFoXDTQwMDUyNjAwMDAwMFowOTELMAkG
A1UEBhMCVVMxDzANBgNVBAoTBkFtYXpvbjEZMBcGA1UEAxMQQW1hem9uIFJvb3Qg
Q0EgMzBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABCmXp8ZBf8ANm+gBG1bG8lKl
ui2yEujSLtf6ycXYqm0fc4E7O5hrOXwzpcVOho6AF2hiRVd9RFgdszflZwjrZt6j
QjBAMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgGGMB0GA1UdDgQWBBSr
ttvXBp43rDCGB5Fwx5zEGbF4wDAKBggqhkjOPQQDAgNJADBGAiEA4IWSoxe3jfkr
BqWTrBqYaGFy+uGh0PsceGCmQ5nFuMQCIQCcAu/xlJyzlvnrxir4tiz+OpAUFteM
YyRIHN8wfdVoOw==
-----END CERTIFICATE-----

Trusted for:
  - <IP_ADDRESS>.<IP_ADDRESS>.1 (RFC5280: serverAuth key usage)
  - <IP_ADDRESS>.<IP_ADDRESS>.4 (RFC5280: emailProtection key usage)
-----BEGIN TRUSTED CERTIFICATE-----
MIIBtjCCAVugAwIBAgITBmyf1XSXNmY/Owua2eiedgPySjAKBggqhkjOPQQDAjA5
MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRkwFwYDVQQDExBBbWF6b24g
Um9vdCBDQSAzMB4XDTE1MDUyNjAwMDAwMFoXDTQwMDUyNjAwMDAwMFowOTELMAkG
A1UEBhMCVVMxDzANBgNVBAoTBkFtYXpvbjEZMBcGA1UEAxMQQW1hem9uIFJvb3Qg
Q0EgMzBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABCmXp8ZBf8ANm+gBG1bG8lKl
ui2yEujSLtf6ycXYqm0fc4E7O5hrOXwzpcVOho6AF2hiRVd9RFgdszflZwjrZt6j
QjBAMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgGGMB0GA1UdDgQWBBSr
ttvXBp43rDCGB5Fwx5zEGbF4wDAKBggqhkjOPQQDAgNJADBGAiEA4IWSoxe3jfkr
BqWTrBqYaGFy+uGh0PsceGCmQ5nFuMQCIQCcAu/xlJyzlvnrxir4tiz+OpAUFteM
YyRIHN8wfdVoOzAWMBQGCCsGAQUFBwMBBggrBgEFBQcDBA==
-----END TRUSTED CERTIFICATE-----

Thanks for the report and analysis. I'll see if I can fix the logic here.

Is there a simple way to silence this warning on julia 1.8?

The change that fixed this could be backported to 1.8 since it's arguably a bugfix.

It'd be truly amazing to have it backported.


[Feature Request]: Hiding outdated workbench image version from Dashboard

Feature description
Currently, Opendatahub ships with multiple OOTB workbench images. Each image has 2 version included with it (eg: Data-Science 2023.1 and 1.2). With the latest OpenDatahub 2.4 release, there is an introduction of new version tag 2023.2.
With this cadence to support 1.2 version image has come to an end from the OpenDatahub/Notebook component.
As we prompt users to switch to newer images, we should also start disabling (i.e Hide old version tag) from Dashboard UI.
So the user can spin a new workbench with out-of-date image version.
This would not cause hindrance to long-running notebooks. It is only a positive way of asking user to utilize newer version of these images.
Based on this IDE team has already worked: https://github.com/opendatahub-io/notebooks/issues/154
Included annotation to the out-of-date images:
 opendatahub.io/image-tag-outdated:true
Task to perform:

Based on the annotation set, hide the version from the workbench view.

Describe alternatives you've considered
None
Anything else?
No response

Verified in RHOAI 2.5: When notebook has an outdated image, it is showing:

Just for completion - the situation that Noam just described is for an imagestream with just one tag (version). If there are more tags in the imagestreams available, only those tags that aren't marked as outdated are shown in the UI as expected.
Thank you, guys.


[WIP] Fix python max line length

Main Changes
In CONTRIBUTING.md we say that all python code should follow PEP8.

[ ] Limit all lines to a maximum of 79 characters.

[ ] For flowing long blocks of text with fewer structural restrictions (docstrings or comments), the line length should be limited to 72 characters.

Associated Issues

Closes #193

Tests

[ ] Quadcopter still flies as expected

Given we're working on #215, should we close this PR?

Given we're working on #215, should we close this PR?

Yea sounds good


added the grpc v1.14.2 release artifact to install_bazel_packages.sh

added the grpc v1.14.2 release artifact to install_bazel_packages.sh
Fixes issue 6754

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Should Spring Cloud Config be extracted from Autoconfigure module?

It was weird to see Spring Cloud Config related doc in the Autoconfigure README.
https://github.com/spring-cloud/spring-cloud-gcp/blob/master/spring-cloud-gcp-autoconfigure/README.adoc
It took me a while to realize that Spring Cloud Config for GCP is now folded into Autoconfigure. Even thought there is few classes involved, organizationally it feels a little weird.

We went back and fourth on this quiet a bit. Everyone seemed to be happy in the end to have it in the autoconfigure module and use a flag to turn it on.

it looks like we have the config starter, but the starter has no README like other starters.

Oh interesting, there are READMEs for both the implementing module and the starter module. Not quite sure where the line is. I see moving the README straight out of Autoconfigure in #409 is probably incomplete.

I think, ultimately, we should try to cut down on the module READMEs and link to the refdoc wherever possible instead. Currently, there is too much documentation duplication.

+1. That would make sense if we can extract all READMEs to the ref doc.

I think we can live with config in the autoconfigure module, let's close this one out.


Fix session retry and activity cancellation bug

What was changed

Disable retries on session creation activity
Remove session creation's manual checking of max-session limit and instead reuse the worker activity limit
Fix additional bug on #726 that surfaced during a session cancellation test

Why?
See #722
Session creation activity (which is really "session run activity" since it spans the life of the session) was originally developed to retry only on a "too many sessions" error it manually returned when checking session count. It was even meant to not retry timeouts in case of worker death. When Temporal removed the ability to specifically disable retries for timeouts, this affected sessions.
Now, instead of the only reason for sessions to retry being a max-limit error, we disable retries on sessions and move max-limit to the activity worker itself. This allows us to remove in-session-creation-activity limit checks and other code that prevented polling during too many sessions.
Also, during development of an integration test, session cancellation without workflow cancellation was causing activity cancellation to have out-of-order command state machine issues similar to those seen in #726. #726 decremented a counter for all activity cancellations even though it incremented the counter only when the workflow was being cancelled. We added a check to make sure we only decrement that counter in the same scenario it was incremented.
Checklist

Closes #722

Do we have integration test coverage for session recreation?
Does it still work and respect concurrent limits with this new approach?

No, we never have (session creation and session recreation call the same internal code and the small part that is unique to recreation has unit test coverage). I will add it for peace of mind though.

After further discussion, this incorrectly removes limits on session recreation by removing the session bucket. We are having internal discussions on this.
I am likely going to open the activity cancellation fix as a separate PR.

I am closing this PR. This approach is not safe for session recreation. Will update #722 with the path forward.


Pulsar schema validation: schema info should log "default": null if it was part of Avro schema

Describe the bug
The Avro schema supports default values of null. The syntax is "default": null. pulsar-admin accepts this syntax, but support for this syntax is lacking elsewhere in Pulsar, resulting in IncompatibleSchema exceptions between schemas that appear identical.
This ticket asks for improved logging for schema info objects that contain the "default": null specification.
To Reproduce
Steps to reproduce the behavior:

Using Pulsar 2.7.1,  run bin/pulsar standalone
Configure schema compatibility policies on a namespace:

bin/pulsar-admin namespaces set-is-allow-auto-update-schema --disable climate/field-service

bin/pulsar-admin namespaces set-schema-compatibility-strategy climate/field-service --compatibility FORWARD_TRANSITIVE

bin/pulsar-admin namespaces set-schema-validation-enforce --enable climate/field-service

bin/pulsar-admin namespaces set-schema-autoupdate-strategy climate/field-service --disabled

Upload the following schemas into a new topic. They differ in only one place, the specification of "default":null.

// ActionV0.schema
{
    "type": "AVRO",
    "schema": "{\"name\":\"Action\",\"type\":\"record\",\"fields\":[{\"name\":\"action\",\"type\":[\"null\",\"string\"],\"default\":null}]}",
    "properties": {}
}

// ActionV1.schema
{
    "type": "AVRO",
    "schema": "{\"name\":\"Action\",\"type\":\"record\",\"fields\":[{\"name\":\"action\",\"type\":[\"null\",\"string\"]}]}",
    "properties": {}
}

tai.meng@C02Z65UGLVDQ ~/pulsar/apache-pulsar-2.7.1 $ bin/pulsar-admin schemas upload --filename ~/pulsar/pythonSandbox/schemas/ActionV0.schema climate/field-service/actions
tai.meng@C02Z65UGLVDQ ~/pulsar/apache-pulsar-2.7.1 $ bin/pulsar-admin schemas upload --filename ~/pulsar/pythonSandbox/schemas/ActionV1.schema climate/field-service/actions

Two schema versions are uploaded because they are compatible. They are printed as the same, so it's impossible to see their difference after uploading them:

tai.meng@C02Z65UGLVDQ ~/pulsar/apache-pulsar-2.7.1 $ bin/pulsar-admin schemas get climate/field-service/actions --version 0

{
  "name": "actions",
  "schema": {
    "name": "Action",
    "type": "record",
    "fields": [
      {
        "name": "action",
        "type": [
          "null",
          "string"
        ]
      }
    ]
  },
  "type": "AVRO",
  "properties": {}
}
tai.meng@C02Z65UGLVDQ ~/pulsar/apache-pulsar-2.7.1 $ bin/pulsar-admin schemas get climate/field-service/actions --version 1

{
  "name": "actions",
  "schema": {
    "name": "Action",
    "type": "record",
    "fields": [
      {
        "name": "action",
        "type": [
          "null",
          "string"
        ]
      }
    ]
  },
  "type": "AVRO",
  "properties": {}
}

Using the Python client library, I found no way to produce a message using version 0 of the schema. Everything I tried resulted in an IncompatibleSchema exception.

class Action(Record):
    action = String()

However, the Action class above works with version 1 of the schema, the one without "\default\":null specified.

Expected behavior
The two schemas are different, so they should not be printed as identical. In this case, the "default":null should be printed when calling bin/pulsar-admin schemas get climate/field-service/actions --version 0.
Further, there should be a way to construct a Record class using the Python client library, so an event can be written to a topic with a schema containing "default":null.
Screenshots
N/A.
Desktop (please complete the following information):

OS: MacOS Catalina Version 10.15.17

Additional context
"default":null seems like a common default value to specify in Avro schemas. The IncompatibleSchema exception that it causes complicated efforts to triage mistakes and bugs that resulted in IncompatibleSchema. Bug tickets whose triage was significantly complicated due to the presence of "default:null: https://github.com/apache/pulsar/issues/9571, https://github.com/apache/pulsar/issues/8510.
The overall impact is that Avro schema support seems quite broken in Pulsar. There were questions on whether Kafka's Avro schema support is this buggy. If we had still been deciding between Kafka and Pulsar, this may have changed our decision.
Another solution is to create a new doc page for Pulsar's Avro support. On that doc page, known limitations of Pulsar's Avro support should be documented. Sample text for this problem (it might not be correct, but it would help anyone experimenting with Avro support in Pulsar):
Pulsar implements support a subset of Avro schemas.

Pulsar does not support `"default":null` for string fields.

To specify a default value of null for a string field, simply omit that clause.

This is because for string fields without default values, Pulsar consumers will default these fields to null and auto-convert null into the empty string for consumers.

The issue had no activity for 30 days, mark with Stale label.


fix(rest/queue): logical error in response status handling

Closes #546

Then merge it

I guess Skillz needs to approve it


Root-overlay bind mount service not running

The etc-systemd-system-resin.target.wants.mount service is not running on boot which means you cannot enable any services without making the FS RW.
Freshly burned image, first boot:
root@resin:~# systemctl status etc-systemd-system-resin.target.wants.mount
● etc-systemd-system-resin.target.wants.mount - Resin target mount point to persistent location
   Loaded: loaded (/lib/systemd/system/etc-systemd-system-resin.target.wants.mount; enabled; vendor preset: enabled)
   Active: inactive (dead)
    Where: /etc/systemd/system/resin.target.wants
     What: /mnt/conf/root-overlay/etc/systemd/system/resin.target.wants
root@resin:~# touch /etc/systemd/system/resin.target.wants/test.txt
touch: cannot touch '/etc/systemd/system/resin.target.wants/test.txt': Read-only file system
root@resin:~# systemctl start etc-systemd-system-resin.target.wants.mount
root@resin:~# touch /etc/systemd/system/resin.target.wants/test.txt
root@resin:~# ls /etc/systemd/system/resin.target.wants/
test.txt
root@resin:~#

Flowdock

This is because the resin-supervisor service has the dependency on etc-systemd-system-resin.target.wants.mount . I think it would be reasonable to move this dependecy as a docker's one which would fix this problem on unmanaged as well. @floion @telphan @michal-mazurek Any comments about it?

That would not be a natural dependency. And it would not make sense later when inspecting the docker service later.
Instead, can we not have the provisioner do this? If it is part of the promotion process, then I guess this promotion process would be responsible of enabling this service in the initial steps of the process.
Is that feasible @josephroberts ?

@floion @agherzan yes I can enable the service before starting the promotion if that's the best approach.

I totally agree with @floion on this. I was more trying to find a compromise but having it in the provision sounds like the way forward.


[Question] is it a documentation that list all methods ?

Hi,
I can't find a documentation who list the methods and actions that we can perform with term, but I'm sure one exists.
So could someone give me the link ?

http://xtermjs.org/docs/api/Terminal/

Thank you ! I think i'm blind

@tsl0922 is it me or there isn't a method to delete character ? (when we press "return" for example)


Publish VS Code extension on Open VSX registry

Could you please publish the sphinx-needs-vscode extension, and any future updates, on the Open VSX registry?
The VS Code Marketplace is for use with Microsoft Visual Studio products only. The Open VSX Registry is a community driven and fully open platform for publishing and consuming VS Code extensions. Our development environment is forced to use this registry instead of the Microsoft marketplace.

Thanks for the release version 0.3.1 !
Could you perhaps add it to Open VSX as well?


⚠ Bofrost.de has degraded performance

In 450ad44, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1644 ms

Resolved: Bofrost.de performance has improved in 7aee797 after 6 minutes.


VM creation from Shared Image Gallery does not pass Purchase Plan details

I have encountered a bug in Azure DevTest Labs when creating a new VM which is based on a Shared Image Gallery image which includes Purchase Plan information.
I have created a custom image using the CIS Red Hat Enterprise Linux 7 image from the Azure Marketplace. This image has been stored as an image within a Shared Image Gallery (which is also attached to a DevTest Labs instance), and the shared image includes all the purchase plan information (publisher, offer, SKU).
I am seeing the following behaviour when using this image:

I can successfully create a new VM from this image (outside DevTest Labs)
I can successfully deploy a new VM within DevTest Labs from the original marketplace image
I cannot deploy a new VM within DevTest Labs using the shared image

When trying to deploy a new VM within DevTest Labs using the shared image, the deployment constantly fails with the following error:
{
    "status": "Failed",
    "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The resource operation completed with terminal provisioning state 'Failed'.",
        "details": [
            {
                "code": "VMMarketplaceInvalidInput",
                "message": "Creating a virtual machine from Marketplace image or a custom image sourced from a Marketplace image requires Plan information in the request. VM: '<VM_ID>."
            }
        ]
    }
}

The purchase plan information is therefore not being passed from the shared image to the DevTest VM deployment. However, clearly it is possible to deploy a VM in DevTest Labs from a Marketplace image which includes purchase plan information, because the original CIS RHEL image works fine.
All of the recent examples for deploying to DevTest Labs are using an undocumented API version (2018-10-15-preview) which is making troubleshooting and experimentation very difficult.
Essentially at this point, it does not appear to be possible to deploy a new VM in Azure DevTest Labs from a Shared Image Gallery image which contains purchase plan information.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 965a0db2-4c54-554a-b972-3d0473eb9a0e
Version Independent ID: 1ce1182f-c558-b1e8-cb51-35155e8cea76
Content: Add a VM using a shared image in Azure DevTest Labs - Azure DevTest Labs
Content Source: articles/devtest-labs/add-vm-use-shared-image.md
Service: devtest-lab
GitHub Login: @spelluru
Microsoft Alias: spelluru

Further to this, looking at the auto-generated ARM template when deploying the CIS RHEL Marketplace Image to DevTest Labs, the properties section includes the following information, including the planId:
"properties": {
        "labVirtualNetworkId": "[variables('labVirtualNetworkId')]",
        "notes": "CIS Red Hat Enterprise Linux 7 Benchmark L1",
        "galleryImageReference": {
          "offer": "cis-rhel-7-v2-2-0-l1",
          "publisher": "center-for-internet-security-inc",
          "sku": "cis-rhel7-l1",
          "osType": "Linux",
          "version": "latest"
        },
        "planId": "cis-rhel7-l1",

Looking at the same deployment template but specifying the shared image as the source, the properties section includes the sharedImageId property but does not include the planId, nor is there any option in the deployment to include it.
If I use an ARM template deployment for the shared image and include the planId property, the deployment simply fails with the same error message:
{
    "status": "Failed",
    "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The resource operation completed with terminal provisioning state 'Failed'.",
        "details": [
            {
                "code": "VMMarketplaceInvalidInput",
                "message": "Creating a virtual machine from Marketplace image or a custom image sourced from a Marketplace image requires Plan information in the request. VM: '<VM_ID>"
            }
        ]
    }
}

@jamesbannan Thanks for the question and the details! We're investigating this and will get back to you shortly.

@jamesbannan Thank you for bringing this to our attention. Our product group is investigating the issue further.
I will get back to you once I have an update. Thanks for your patience.

@jamesandersen, did you try to create a VM from the custom image itself? I can repro your case with a custom image. So, I am not sure if it is isolated to SIG images. Can you please confirm?

@leovms Yes, I was able to create a VM outside DevTest Labs from the custom image without any problem. The image was created using Hashicorp Packer, and the final step deprovisions the VM:
{
    "execute_command": "chmod +x {{ .Path }}; {{ .Vars }} sudo -E sh '{{ .Path }}'",
    "inline": [
      "/usr/sbin/waagent -force -deprovision+user && export HISTSIZE=0 && sync"
    ],
    "inline_shebang": "/bin/sh -x",
    "type": "shell"
}

@jamesbannan when I refer to custom image, I mean a DTL custom image. So, when you create the original VM from the gallery image, you mentioned that you created a custom image and I'm assuming this was a DTL custom image. If so, when you then create a new VM from that custom image, within DTL, does that work? I find it does not and I'm looking for confirmation from you that it also does not work, as it confirms I'm following the correct repro steps.
Similarly, when you configure the SIG image, do you specify the Purchase Plan information? Even from SIG, I am able to repro your issue if I don't configure the Purchase Plan in the SIG, when I try to create a VM from that SIG image.
Having said all that, I am confirming that DTL does not pass along the Purchase Plan information to the underlying call when creating the VM. I am fixing that now. It will take a few days for the fix to roll out. In the meantime, I would appreciate that you confirm my observations.

@leovms I see - my mistake. No, I didn't create the custom image within DTL and I haven't tried. The process I have for building the image is using Azure DevOps and Packer, and the azure-arm builder wasn't able to provision a new VM within DTL and capture it as a custom image. So my approach has been to use Packer to provision a VM outside DTL, capture it to a managed image, and then bring into SIG as a new version. The SIG is attached to DTL.
There is a recent PR in the Packer project to add integration with DTL, but I've not checked out the functionality included in the merge.
To answer your other questions, Yes when I configure the SIG image I definitely include the purchase plan information. When DTL first failed to apply the custom image via SIG I hadn't included the purchase plan information, and I thought that this was why it failed. I went back and added the purchase plan information, and that was when I discovered that the information wasn't being passed through to DTL, regardless of the information supplied in the SIG image.

@jamesbannan, thank you for reporting this and the details on the issue. The fix is currently being validated and should be rolling out sometime after that. It takes about 1 week to roll out to all regions.

@jamesbannan The fix should have been rolled out to all regions by now. Please retry and let us know if you see any issues. Thanks for your patience!

Hi @BhargaviAnnadevara-MSFT - thank you for the update. I have tested a deployment of a custom RHEL image from a shared image gallery attached to DevTest Labs and it worked perfectly :-) I'll close this call now - thanks all for your assistance with this issue.

@jamesbannan Thanks for confirming! We're glad we could resolve your issue!


Storage: (Refactor) Avoid referencing DeltaMergeStore.h

What problem does this PR solve?
Issue Number: ref #5831

Currently the DeltaMerge/DeltaMergeStore.h is imported in Storages/StorageDeltaMerge.h, which makes the pimpl useless -- When changing private member functions in DeltaMerge/DeltaMergeStore.h, a lot of external functions need to be recompiled.
It does not make sense to leak the "ThreadType" in the Delta Merge Public API, as background threads are purely internal.

What is changed and how it works?

Changed TaskRunThread to MergeDeltaReason, which makes more sense.
No need to specify TaskRunThread or MergeDeltaReason in DeltaMerge public API mergeDeltaBySegment, as run thread or merge reason are purely internal.
Forward declare RowKeyValue so that the import of internal DeltaMerge headers can be avoided.

[x] This PR is based on https://github.com/pingcap/tiflash/pull/5833, so merge that PR first to get a nicer diff.

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/merge


Store survey data in Redux

Summary

[ ] save state from user survey in Redux
[ ] current date is also saved in Redux

Motivation

Once we store this data in Redux, we can persist it to the database
We can re-populate the next day's questions with the previous day's answer

Describe alternatives you've considered
If we don't persist this in Redux, we are breaking our tentative and kind of unfinished style guides
Additional context
Partially relies on #255 being completed to ensure we save all the questions

Can I try to help with this issue? I'd gladly work with anyone if it needs to be done quickly.

We actually are gonna put this on hold until #237 is done. Apologies I'll update the tags!

I'm going to close this. For the time being, it seems superfluous to store this in Redux - the times we need survey data, we need to pull a specific observation from the database anyway.


Cache date serialization.

Gee Dawid, wouldn't it be nice copy some neat premature optimization from here:
https://github.com/tokio-rs/tokio-minihttp/blob/master/src/date.rs

Considering that the timestamp is in microseconds, it does not seem worth it.


2023-06-30 fails to compile with uhdm-1.70

/wrkdirs/usr/ports/cad/yosys-systemverilog/work/yosys-systemverilog-2023-06-30-eceb24b/yosys-f4pga-plugins/systemverilog-plugin/UhdmAst.cc:5095:33: error: too few arguments to function call, expected 2, have 1
        if (!object->Compare(obj)) {
             ~~~~~~~~~~~~~~~    ^
/usr/local/include/uhdm/BaseClass.h:174:19: note: 'Compare' declared here
  virtual int32_t Compare(const BaseClass* other,
                  ^

FreeBSD 13.2

Thanks for the report!
This is expected, Surelog and UHDM are still under heavy development and new versions break all the time (sometimes the compilation like in this case sometimes it compiles and runs but produces a wrong result).
Use this repo (yosys-systemverilog) and the submodules in specific versions to ensure full compatibility (between the plugins, UHDM and Surelog).
In the meantime we are continuously working on having the latest versions, but it's not trivial due to the second type of the issues (i.e. compiles and runs, but produces incorrect netlists).


rultor

@rultor hello

@rultor hello

@alpho320 Hi there! I understand a few simple commands: "merge", "deploy", etc. This page explains them briefly. Any questions or bug reports are welcome. Have fun :)


Fix(common): format logs in correct local timezone

Description of change
Logs were formatted in UTC regardless of local timezone, resulting in incorrect times. We now format the datetime with rfc3339 which includes the correct timezone.
Testing is a bit hacky with the mutex, as per the comment, Time uses libc to get the timezone. By forcing the env var to the expected timezone we get the result we want. Originally had more than one test, hence the mutex. Decided to leave it in, as any additional test using timezones would yield crazy racing errors. Happy to remove it if needed.
Closes #834
How has this been tested? (if applicable)
Added unit tests.
Having some issues running the full test suite / local env. Should be alright but timezones.

Thanks for the feedback, added a clarifying comment, cleaned up and readded dim()

Having some issues running the full test suite / local env. Should be alright but timezones.


sedimentation_1_particle example is broken

The sedimentation_1_particle example is broken and the documentation for resolved CFD-DEM is out of date.
The exception thrown is related to the DEM coupling frequency parameter which is "not declared". I suspect the name of the parameter was changed, but not the documentation and the example...

FIxed


Actual behaviour

@shykes ### Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing 😞


NEW: Python Wrapping for MinimalPathExtraction

Enables the MinimalPathExtraction module to be wrapped for Python.
-Definition of class PathInfo has been removed from SpeedFunctionToPathFilter.h
and is now known as SpeedFunctionPathInformation with its own header files. This
enables to create an instance of this class in python.
-Wrapping files have been added for each class
-Instanciation of Path Information has been modified in MinimalPathTest.h and
SpeedFunctionToPathFilter header files in order to fit the new definition of
the class.
-ImageToPathFilter header files have been removed because they already exist
in ITK/Module/Nonunit/Review and are already wrapped there. Another commit on
the ITK git repository will be created to move those files in the Path module.

Great work.  I tested locally against Git master.  The Remote module configuration can now be updated.


Viewer not loading, no errors

Hey Matthew,
I've managed to break the viewer and I can't work out why it's not displaying. I'm not getting any errors and my lack of experience has left me doing a lot of head scratching. Any advice would be appreciated.
Here's the live page:
https://www.shadowvisuals.com/timberland_flooring.html

The viewer height is zero. Your stylesheet sets the panorama div height to 40%, but the parent element doesn't have a height set, so 40% of zero is zero. You'll need to either give the div a fixed height or give the parent element a height.

That was it. Thanks, much appreciated.


Update storage.md

Thanks @phiamazon - please would you sign the CLA as requested by the googlebot in a previous comment. When you've signed the CLA, add a comment on this PR with the words suggested by the bot. That will prompt the bot to re-check the CLA.

/ok-to-test

Thanks for this update! The same update has been applied and merged from PR https://github.com/kubeflow/website/pull/1869, so I'll close this PR.
/close


feat(board): associate WI with iteration using drag and drop in board…

… view.
Story: https://openshift.io/openshiftio/openshiftio/plan/detail/3c37c431-b0db-4c2f-941c-94e2bc2c18e0
This PR is only for board view.

@vikram-raj snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io

@vikram-raj do the iteration count get updated?

@vikram-raj snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io

@nimishamukherjee Yes, it gets updated.

@vikram-raj snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io

@vikram-raj snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io

@vikram-raj snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io

@vikram-raj fabric8/fabric8-ui:SNAPSHOT-PR-2068-10 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io

@vikram-raj fabric8/fabric8-ui:SNAPSHOT-PR-2068-11 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io

@vikram-raj fabric8/fabric8-ui:SNAPSHOT-PR-2068-12 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io

@vikram-raj I'm using the snapshot url and cleared the cache

The work item count is not being incremented
The work item remains in the current iteration even after I have associated it with another iteration.

@nimishamukherjee Work item gets associated with iteration but when I filter the work item with iteration it the API return wrong work item which is not associated with that iteration.

@pranavgore09 can you have a look at this. Can this be fixed before our demo?

@nimishamukherjee @vikram-raj
I am putting up the scenario regarding nested iterations and WI in it.
Consider there are two iterations i1 and i2. And i1 is the parent of i2.
Consider there are two work items w1 and w2.
Now let's say we have assigned i1 to w1 and i2 to w2.
When we filter on parent iteration i1 -> we should get w1 and w2. (Because work items from child iterations are also added in the filter)
When we filter on child iteration i2 -> we should get only w2.
HTH.

Thanks @pranavgore09

@vikram-raj fabric8/fabric8-ui:SNAPSHOT-PR-2068-29 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2068-fabric8-planner.badger.fabric8.io


Bump google.golang.org/grpc from 1.51.0 to 1.53.0

fixes https://github.com/knative-sandbox/eventing-rabbitmq/pull/1157

/lgtm


          <img width="971" alt="123123123" src="https://github.com/cubiq/PuLID_ComfyUI/assets/125015943/5890a69f-4324-4d66-ac35-9c8ecf5a638f">

重装这个就可以了
Originally posted by @GonDesign in https://github.com/cubiq/PuLID_ComfyUI/issues/36#issuecomment-2207951365

I don't know what this is


Fix tf formula in hw1 in week02

I think that the formula of TF-IDF is missed normalisation in TF part. Could you please check?

@poedator @justheuristic


Show products in category section in dashboard

I think it will be better to show products count and products in category in dashboard.
So When I click category it shows root category list with total number of products like

Electronics(29)
Books(123)

and, when I click Electronics, if it has subcategory, then shows subcategory(ex- Computer(14)) if no subcategory then show products list of electronics.
What do you think?

It has been implemented in the Dashboard 2.0.


Altair uses a never provided credentials in Authorization header

Hi,
Altair adds Authorization header with credentials that was never provided.
I have a local project, with URL protected by basic authorization mechanism -
http://localhost/doc
During development I saved credentials for that URL in browser (and Chrome saved it to passwords.google.com).
On the same project I have GQL endpoint, http://localhost/graphql which accepts mutation for user login:
mutation {
  login(username: "john.doe", password: "realpassword") {
    token
  }
}

Altair sends requests like this:
POST /graphql HTTP/1.1
Host: localhost
Connection: keep-alive
Content-Length: 140
Authorization: Basic censoredCredentialsInBase64Format=
Accept: application/json
DNT: 1
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36
Sec-Fetch-Mode: cors
Content-Type: application/json
Origin: chrome-extension://flnheeellpciglgpaodhkhmapeljopja
Sec-Fetch-Site: cross-site
Accept-Encoding: gzip, deflate, br
Accept-Language: cs-CZ,cs;q=0.9,sk;q=0.8

{"query":"mutation {\n  login(username: \"john.doe\", password: \"realpassword\") {\n    token\n  }\n}","variables":{},"operationName":null}

In Altair I have no set any headers via "Set Headers" functionality.
Expected behavior
Altair doesn't touch my passwords!!! I'm definitely sure I didn't set the Authorization header with this credentials, 100%.
Screenshots
No screenshots available.
Desktop (please complete the following information):

OS: Debian 9
Browser: Chrome
Chrome/76.0.3809.100

Additional context
Deleting credentials from passwords.google.com, clearing "host" cache data and restarting browser helped me.
Edit: formatting

Hey, this is quite an interesting case. Do you have any environment variables in Altair? Can you try the same thing with the Firefox add-on (it might be a browser policy, not sure).

I'm pretty sure the behavior you're experiencing is from the user agent 🙂 and Altair isn't "touching" your password.
Another thing you can do to verify this behavior is sending a fetch request (with credentials set to include) from your developer console to the same domain and see what headers are sent in the network tab.

Hi, thx for quick reply.
No environment variables in Altair has been set.
I tried open developer console in new browser tab and executed:
fetch('http://localhost/graphql', {mode: 'no-cors'});

On host was listening netcat (nc -lvvp 80).
That is something like:
fetch('http://localhost/graphql', { credentials: 'include' });

you're right! now I understand, thanks for the clarification

You're welcome! Just to clarify, sending the request with fetch from the console with credentials included also added the basic auth header?

Yes, credentials was included.


Fails to Start

Environment

OS: Ubuntu 16.04.2 LTS
Erlang/OTP: R19/8.3
EMQ: 2.3-beta.1

Description
emqttd fails to start. Nothing useful seems to be logged. I've bumped all the log levels to debug without any success. This was first attempted with the clustering set to DNS but still happens when set to manual.
# tail -f /var/log/emqttd/*
==> /var/log/emqttd/erlang.log.1 <==
===== LOGGING STARTED Tue Jul 25 19:14:02 UTC 2017
=====

=====
===== LOGGING STARTED Tue Jul 25 19:14:36 UTC 2017
=====

=====
===== LOGGING STARTED Tue Jul 25 19:16:20 UTC 2017
=====

==> /var/log/emqttd/run_erl.log <==
run_erl [13745] Tue Jul 25 19:16:20 2017
Args before exec of shell:
run_erl [13745] Tue Jul 25 19:16:20 2017
argv[0] = sh
run_erl [13745] Tue Jul 25 19:16:20 2017
argv[1] = -c
run_erl [13745] Tue Jul 25 19:16:20 2017
argv[2] = exec "/usr/sbin/emqttd" "console"

Here's my attempt:
# dpkg -l | grep emqttd
ii  emqttd                              2.3                                        amd64        Erlang MQTT Broker
# emqttd start
# time emqttd start

real	0m27.017s
user	0m10.796s
sys	0m1.524s

/etc/emqttd/emq.conf:
# grep -v "#" /etc/emqttd/emq.conf | grep -v "^$"
cluster.name = emqcl
cluster.discovery = dns
cluster.autoheal = on
cluster.autoclean = 5m
cluster.dns.name = <Round Robin DNS A record>
cluster.dns.app = emq
node.name =<EMAIL_ADDRESS>node.cookie = xxxxxxxx
node.smp = auto
node.kernel_poll = on
node.async_threads = 32
node.process_limit = 256000
node.max_ports = 65536
node.dist_buffer_size = 32MB
node.max_ets_tables = 256000
node.fullsweep_after = 1000
node.crash_dump = /var/log/emqttd/crash.dump
node.dist_net_ticktime = 60
node.dist_listen_min = 6369
node.dist_listen_max = 6379
log.dir = /var/log/emqttd
log.console = console
log.console.level = error
log.syslog = on
log.syslog.level = error
log.error.file = /var/log/emqttd/error.log
log.crash = on
log.crash.file = /var/log/emqttd/crash.log
mqtt.allow_anonymous = true
mqtt.acl_nomatch = allow
mqtt.acl_file = /etc/emqttd/acl.conf
mqtt.cache_acl = true
mqtt.max_clientid_len = 1024
mqtt.max_packet_size = 64KB
mqtt.websocket_protocol_header = on
mqtt.conn.force_gc_count = 100
mqtt.client.idle_timeout = 30s
mqtt.client.enable_stats = off
mqtt.session.max_subscriptions = 0
mqtt.session.upgrade_qos = off
mqtt.session.max_inflight = 32
mqtt.session.retry_interval = 20s
mqtt.session.max_awaiting_rel = 100
mqtt.session.await_rel_timeout = 20s
mqtt.session.enable_stats = off
mqtt.session.expiry_interval = 2h
mqtt.session.ignore_loop_deliver = false
mqtt.mqueue.type = simple
mqtt.mqueue.max_length = 1000
mqtt.mqueue.low_watermark = 20%
mqtt.mqueue.high_watermark = 60%
mqtt.mqueue.store_qos0 = true
mqtt.broker.sys_interval = 60
mqtt.pubsub.pool_size = 8
mqtt.pubsub.by_clientid = true
mqtt.pubsub.async = true
mqtt.bridge.max_queue_len = 10000
mqtt.bridge.ping_down_interval = 1
mqtt.plugins.etc_dir =/etc/emqttd/plugins/
mqtt.plugins.loaded_file = /var/lib/emqttd/loaded_plugins
listener.tcp.external = <IP_ADDRESS>:1883
listener.tcp.external.acceptors = 16
listener.tcp.external.max_clients = 102400
listener.tcp.external.access.2 = allow all
listener.tcp.external.backlog = 1024
listener.tcp.external.buffer = 4KB
listener.tcp.external.nodelay = true
listener.tcp.internal = <IP_ADDRESS>:11883
listener.tcp.internal.acceptors = 16
listener.tcp.internal.max_clients = 102400
listener.tcp.internal.backlog = 512
listener.tcp.internal.tune_buffer = on
listener.tcp.internal.buffer = 1MB
listener.tcp.internal.recbuf = 4KB
listener.tcp.internal.sndbuf = 1MB
listener.tcp.internal.nodelay = true
listener.ssl.external = 8883
listener.ssl.external.acceptors = 16
listener.ssl.external.max_clients = 1024
listener.ssl.external.access.1 = allow all
listener.ssl.external.handshake_timeout = 15s
listener.ssl.external.keyfile = /etc/emqttd/certs/key.pem
listener.ssl.external.certfile = /etc/emqttd/certs/cert.pem
listener.ws.external = 8083
listener.ws.external.acceptors = 4
listener.ws.external.max_clients = 64
listener.ws.external.access.1 = allow all
listener.ws.external.backlog = 1024
listener.ws.external.recbuf = 4KB
listener.ws.external.sndbuf = 4KB
listener.ws.external.buffer = 4KB
listener.ws.external.nodelay = true
listener.wss.external = 8084
listener.wss.external.acceptors = 4
listener.wss.external.max_clients = 64
listener.wss.external.access.1 = allow all
listener.wss.external.handshake_timeout = 15s
listener.wss.external.keyfile = /etc/emqttd/certs/key.pem
listener.wss.external.certfile = /etc/emqttd/certs/cert.pem
listener.api.mgmt = <IP_ADDRESS>:8080
listener.api.mgmt.acceptors = 4
listener.api.mgmt.max_clients = 64
listener.api.mgmt.access.1 = allow all
sysmon.long_gc = false
sysmon.long_schedule = 240
sysmon.large_heap = 8MB
sysmon.busy_port = false
sysmon.busy_dist_port = true

Also attempted with clustering set to manual and the cluster.dns.* options commented out.

It looks like there was a problem with the DNS entry I had setup. It was pointing to older versions of emqttd that weren't compatible with clustering. It would be helpful if there were some log messages or other output that would call out why emqttd is failing to start.

This was coupled with a permission issue on the .erlang.cookie file.

Hijacking to ask a question. I successfully have DNS based auto clustering working now. Thanks! Loving the feature.
Auto clean works great as well.
Does emqttd recheck the DNS entries over time and join with all the entries it eventually finds, or is DNS only queried at first start? It would be nice if it had a polling feature that rechecked the clustering type for new nodes to join on some interval. Guess this became a feature request.

@Linuturk  plan to support periodic DNS query in the future.

Popping this here for reference. I'm solving this now with a bash script setup in cron.
#!/bin/bash

NODECOUNT=`curl -s http://admin:public@localhost:7101/api/nodes | python -m json.tool | grep "name" | wc -l`

timestamp() {
	date --rfc-3339=seconds
}

echo $(timestamp) "Found $NODECOUNT node(s)."

if (( $NODECOUNT < 2 )); then
	echo $(timestamp) "Fewer than 2 nodes. Restarting..."
        /etc/init.d/emqttd restart
fi


Infinite loop in create_data.py?

Hello,
I'd like to create my own dataset to train a quantizer model myself.
When running the create_data.py file after loading my texts, the while loop (probably) runs indefinitely - my data consists of 6300 text strings, and by now the code has generated over 35,000 npy files from the texts. Even if I load only 1 short text of 15 words, it doesn't stop running. Might there be something wrong? When is it going to stop?
Thanks for your advice.

So I guess the solution is either to just stop the data creation process once you think you have enough npy files,
or to modify the code so that it only uses X samples for the creation of npy files and stop there. I went with the latter.
The issue can be closed.


The component doesn't support "RTL" dirction

first I'd thank you for this component
is it possible to use this component from
right to left "I mean staring from right"?
if not can you add these feature?
thank you

You can set the index to the last page, and use the onSlideChange to monitor the index, if it is 0, you are at the 'last' slide


build: update to btcwallet dependency with ZMQ message buffer reuse

bitcoind notifies transactions once they're accepted into the mempool and once they're confirmed in a block. Previously, reading a message from ZMQ would allocate a buffer with the size of the message. This can cause nodes to perform a large number of allocations within a small amount periodically (3000 300B allocations every 10 mins on average), which can cause a lot of GC pressure on lower resourced nodes. To remedy this, we introduce two static buffers, one for blocks and another for transactions, that will be reused for every message read. Each is constrained by its maximum expected size.
Fixes https://github.com/lightningnetwork/lnd/issues/3370.

I am testing this on a system that was reliably experiencing ~100% cpu usage at nearly all times. So far so good, I will update this thread again if cpu usage is still low after some time. Thanks a lot!

Unfortunately I just checked cpu utilization again and it's back over 100%. This is consistent with previous behavior, where cpu utilization started off low (0-15%) for at least half an hour or so, and then gets pegged at 100%+ after some hours.

@sangaman could you re-apply the branch (new changes pushed) and try again? You should confirm that lnd --version shows the commit https://github.com/lightningnetwork/lnd/pull/3695/commits/b5827e3079fb59ac9d0c0bc563305f4d43764c09. You should also start lnd with the --profile=PORT flag so that you can obtain a CPU profile with go tool pprof http://localhost:PORT/debug/pprof/profile if you happen to experience the high CPU issue again.

Done. I'm using the latest from this branch, restarted lnd with the --profile option, and getinfo prints "version": "0.8.0-beta commit=v0.8.0-beta-130-g39e3a45d999f59f39ad3f33c939680e2e77d3fa2". I will obtain a CPU profile if the 100% cpu usage returns.

So far so good... cpu usage still low.

Cpu usage still low after more than 24 hours, I'd say the issue is fixed for me with the latest commit.

Never mind, cpu usage back up over 100%. Profiling is on, however. What command should I use to obtain a cpu profile, png?

@sangaman the issue seems to not be resolved yet. Will close this and continue investigating.


[Identity] Archboad review feedback naming updates

Packages impacted by this PR
@azure/identity
Issues associated with this PR
None
Describe the problem that is addressed by this PR
Naming changes for following API:

credentialProcessTimeout => processTimeout
disableAuthorityValidationAndInstanceDiscovery => disableInstanceDiscovery

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-identity


tree layout: Support transparent intermediary nodes to keep the tree tidy

(I opened a question here, but I don't think it's possible under the current core so I don't expect many answers)
The current tree implementation seems to always put children at exactly one depth increment relative to their parent. The problem is that in some pathological cases where one child is much larger than the others, it leads to very wide nodes:

Ideally, I would have liked a way in D3 to say that if this situation happens, the heaviest branch are allowed to be shifted at a deeper depth to free the space necessary for the tree width to be shrinked. Basically, I'd like this:

Instead of this:

Very interesting idea! Have you built a prototype of this yet?

Looks like something like this is discussed in Tree Drawing Algorithms by Adrian Rusu.


HV-1699 Hibernate-validator 6: Weird behavior of the @Max annotation with a BigDecimal set on a Number field

https://hibernate.atlassian.net/browse/HV-1699

If a *Number* validator was used it would convert any number to long hence some data might be lost.
Change how numbers are compared in Max/Min validators

for Min/Max Number validators check if actual numbers are not with floating point (float,double) and if they are direct them to correct number comparator helper method
for big numbers (BigDecimal, BigInteger) check in number comparator helper before converting to long. If actual numbers are from the 'Big*' classes direct the call to corresponding overloaded versions of the method so that no data will be lost
Compare floating point numbers using Double#compare()

Merged. Will backport to 6.0. Thanks!


[SMP-1584] Update air gap docs with module file info

Update air gap docs with module file info
For reviewers, a preview is available.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Edit this hyperlink
https://console.cloud.google.com/storage/browser/smp-airgap-bundles;tab=objects?pageState=("StorageObjectListTable":("f":"%255B%255D"))&prefix=&forceOnObjectsSortingFiltering=false&pli=1
With
https://console.cloud.google.com/storage/browser/smp-airgap-bundles

Edit this command
./harness-airgap-images.sh -r REGISTRY.YOURDOMAIN.COM:PORT -f harness-airgapped.tgz
With
./harness-airgap-images.sh -r REGISTRY.YOURDOMAIN.COM:PORT -f <moduleName-images.tgz>

Replace <harness-docker-images.txt> from here
All Docker files required to deploy Harness are stored in the Harness air gap image bundle in the harness-docker-images.txt file.
TO:
https://github.com/harness/helm-charts/releases

Please edit this step:
Add the *.tgz for each module you want to deploy and the harness-docker-images.txt file to your air-gapped network. You can now push your images locally.
TO:
Add the *.tgz for each module you want to deploy to your air-gapped network. You can now push images locally.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


[cherrypick d34d3af068] [BEAM-5375] KafkaIO : Handle runtime exceptions while fetching from Kafka better.  (#6391)

Cherry-pick #6391 into release-2.7.0.
+R: @charlesccychen

Thanks, this LGTM.


Map not working properly when goes to background

I am trying to integrate background active tracking in my app.
As you can see from the image below, the red marker is where I started working and blue pulse icon is where I stopped. I had only walked a distance somewhere between 0.1 - 0.2 km, it was a U-turn. The app works well when the app is in the foreground, polylines render correcly. But as soon as the app goes into the background, and to the foreground again, it would think that I've traveled far, ergo, the ridiculous polylines.
I have already followed the steps according to the API and enabled NSLocationAlwaysUsageDescription to enable always on GPS but it does not render correctly.

Are you using built in navigator.geolocation to get user's position?

Yes, and I have not seen any examples that are able to optimize the GPS tracking module 😢

Okay then you are screwed :D

@henrikra why?

Since built in geolocation module does not work right when app is on background. You would have to make something custom or use maybe something like this which is not free https://github.com/transistorsoft/react-native-background-geolocation

@henrikra I'm suspecting the problem is with the phone itself. Though I have no way to be sure other than testing with another physical phone. Is there a way to calibrate/debug my iPhone's GPS?

Trust me. I have been working with React Native and GPS stuff for over 6 months now. Ping me if you solve this xD

@henrikra That's terrible to hear 😢 Then how do you resolve your problem? Custom build something or purchase the module?

We bought the paid geolocation I linked you. It works pretty good on iOS but for Android we made totally custom.

Ah, I see. Will try to do some deep research on this polyfills later. It must be something that we are missing.

see my answer (I'm using a objective C lib, using native geoloc api for iOS, for RN) https://stackoverflow.com/questions/43629524/react-native-ios-geoloc-has-poor-accuracy-by-default/43639144#43639144
check that too https://github.com/facebook/react-native/issues/12967#issuecomment-292176191 (is your issue duplicating that one?)

@jcharlet Things look pretty good now with react-native-location! Thanks!


Hotmail account not working with azure aad

Hi,
I tried my Hotmail/live account, not able to authenticate but organizational account works fine. Is there anything I need to do for Hotmail or live account?
Thanks.

In order to use a hotmail or live account you have to use the converged endpoint (v2 apps). Below is an OIDC .NET sample using v2 that should be what you need.
https://github.com/Azure-Samples/active-directory-dotnet-webapp-openidconnect-v2


#Setup Docker compose up not working due to missing .env files

@echo75 Since I know it's docker build I started to run it
@Dr4gon ➜ /workspaces/graduation-project-johan-hedman (main) $ docker compose up
Failed to load /workspaces/graduation-project-johan-hedman/backend/.env: open /workspaces/graduation-project-johan-hedman/backend/.env: no such file or directory

It's important to make sure the at least have dummy .env files with localhast parameters in the folder.

@echo75 Of course, you'll both in the front- and backend an .env file. I'm aware that you have your secrets stored there. But u need to at least provide a dummy .env file to make it locally work for every developer after u.

Yeah, that would be nice. I know from other projects that it's MONGODB_CONNECTION_STRING=mongodb://mongo:27017
which u changed to MONGODB_URI and therefore the app crashes.
graduation-project-johan-hedman-api-1       | app.js is running
graduation-project-johan-hedman-api-1       | /app/node_modules/connect-mongo/build/main/lib/MongoStore.js:126
graduation-project-johan-hedman-api-1       |                 .db(options.dbName)
graduation-project-johan-hedman-api-1       |                  ^
graduation-project-johan-hedman-api-1       |
graduation-project-johan-hedman-api-1       | TypeError: Cannot read properties of undefined (reading 'db')
graduation-project-johan-hedman-api-1       |     at /app/node_modules/connect-mongo/build/main/lib/MongoStore.js:126:18
graduation-project-johan-hedman-api-1       |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
graduation-project-johan-hedman-api-1       |
graduation-project-johan-hedman-api-1       | Node.js v20.5.1
graduation-project-johan-hedman-api-1       |
graduation-project-johan-hedman-api-1       | [nodemon] app crashed - waiting for file changes before starting...

After changing the configuration value to MONGODB_URI, the app finally starts properly 😁

There is a .env.example in the front-and backend though, with the parameters you need

@johan-hedman I'm aware of that. A newbie won't know what an .env file is or how to use it properly. It would be much easier to simply start the application 😁

@johan-hedman I copied this directly into my .env file
MONGODB_URI = mongodb://localhost:27017/movies-test
SESSION_SECRET =<PHONE_NUMBER>ABCDEFabcdef
FRONTEND_URL = http://<IP_ADDRESS>:5173
OMDB_API_KEY = 11111111

The application doesn't let me even see the page anymore
frontend_1  |   ➜  Local:   http://localhost:5173/
frontend_1  |   ➜  Network: http://<IP_ADDRESS>:5173/
api_1       | app.js is running
api_1       | GET /accounts/session 200 5.323 ms - -
api_1       | GET /accounts/session 200 0.794 ms - -
api_1       | /app/node_modules/mongoose/lib/connection.js:788
api_1       |     err = new ServerSelectionError();
api_1       |           ^
api_1       |
api_1       | MongooseServerSelectionError: connect ECONNREFUSED <IP_ADDRESS>:27017
api_1       |     at _handleConnectionErrors (/app/node_modules/mongoose/lib/connection.js:788:11)
api_1       |     at NativeConnection.openUri (/app/node_modules/mongoose/lib/connection.js:763:11) {
api_1       |   reason: TopologyDescription {
api_1       |     type: 'Unknown',
api_1       |     servers: Map(1) {
api_1       |       'localhost:27017' => ServerDescription {
api_1       |         address: 'localhost:27017',
api_1       |         type: 'Unknown',
api_1       |         hosts: [],
api_1       |         passives: [],
api_1       |         arbiters: [],
api_1       |         tags: {},
api_1       |         minWireVersion: 0,
api_1       |         maxWireVersion: 0,
api_1       |         roundTripTime: -1,
api_1       |         lastUpdateTime: 550138,
api_1       |         lastWriteDate: 0,
api_1       |         error: MongoNetworkError: connect ECONNREFUSED <IP_ADDRESS>:27017
api_1       |             at connectionFailureError (/app/node_modules/mongodb/lib/cmap/connect.js:367:20)
api_1       |             at Socket.<anonymous> (/app/node_modules/mongodb/lib/cmap/connect.js:290:22)
api_1       |             at Object.onceWrapper (node:events:629:26)
api_1       |             at Socket.emit (node:events:514:28)
api_1       |             at emitErrorNT (node:internal/streams/destroy:151:8)
api_1       |             at emitErrorCloseNT (node:internal/streams/destroy:116:3)
api_1       |             at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
api_1       |           cause: Error: connect ECONNREFUSED <IP_ADDRESS>:27017
api_1       |               at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16) {
api_1       |             errno: -111,
api_1       |             code: 'ECONNREFUSED',
api_1       |             syscall: 'connect',
api_1       |             address: '<IP_ADDRESS>',
api_1       |             port: 27017
api_1       |           },
api_1       |           [Symbol(errorLabels)]: Set(1) { 'ResetPool' }
api_1       |         },
api_1       |         topologyVersion: null,
api_1       |         setName: null,
api_1       |         setVersion: null,
api_1       |         electionId: null,
api_1       |         logicalSessionTimeoutMinutes: null,
api_1       |         primary: null,
api_1       |         me: null,
api_1       |         '$clusterTime': null
api_1       |       }
api_1       |     },
api_1       |     stale: false,
api_1       |     compatible: true,
api_1       |     heartbeatFrequencyMS: 10000,
api_1       |     localThresholdMS: 15,
api_1       |     setName: null,
api_1       |     maxElectionId: null,
api_1       |     maxSetVersion: null,
api_1       |     commonWireVersion: 0,
api_1       |     logicalSessionTimeoutMinutes: null
api_1       |   },
api_1       |   code: undefined
api_1       | }
api_1       |
api_1       | Node.js v20.5.1
api_1       | [nodemon] app crashed - waiting for file changes before starting...


AddCommandHandler<string[]> doesn't register command with arbitrary number of parameters

What is the current behavior?
If method is registered with AddCommandHandler<string[]> instead of [YarnCommand], it's not registered correctly and throws error at play time:

What is the expected behavior?
It's expected that AddCommandHandler method behaves the same as YarnCommand attribute and register command that takes arbitrary number of parameters.
Please tell us about your environment:

Yarn Spinner Version: 2.4.0
Unity Version: 2022.3.10f1

Other information
Can't call command (X): incorrect number of parameters
UnityEngine.Debug:LogError (object)
Yarn.Unity.DialogueRunner:HandleCommand (Yarn.Command) (at ./Library/PackageCache/dev.yarnspinner.unity@2.4.0/Runtime/DialogueRunner.cs:903)
Yarn.VirtualMachine:RunInstruction (Yarn.Instruction)
Yarn.VirtualMachine:Continue ()
Yarn.Dialogue:Continue ()
Yarn.Unity.DialogueRunner:ContinueDialogue (bool) (at ./Library/PackageCache/dev.yarnspinner.unity@2.4.0/Runtime/DialogueRunner.cs:1142)
Yarn.Unity.DialogueRunner:SelectedOption (int) (at ./Library/PackageCache/dev.yarnspinner.unity@2.4.0/Runtime/DialogueRunner.cs:1083)
Yarn.Unity.OptionsListView/<<RunOptions>g__OptionViewWasSelectedInternal|15_2>d:MoveNext () (at ./Library/PackageCache/dev.yarnspinner.unity@2.4.0/Runtime/Views/OptionsListView.cs:176)
UnityEngine.SetupCoroutine:InvokeMoveNext (System.Collections.IEnumerator,intptr)

Fixed in f4dc45be64a5993a26ee0bbea931e24646f1bb6c, and backported to v2 in 237d5de777b5085cf1ba9b25ee1f44d5a3e590cf . Thank you!


Help needed in the HPP file

I have a ROS system which I am planning to migrate to ROS2 using this bridge. I have declared some variables in the header file. How do I convert these variables ROS2. My code inside the hpp files looks something like this:
        private:
            // ROS
            ros::NodeHandle                 nh;
            ros::NodeHandle                 nhPriv;
            ros::Time                       t;

            ros::Subscriber                 odomSub;
            ros::Subscriber                 imuSub;
            ros::Subscriber                 poseSub;

            ros::Publisher                  filterPub;

I have never checked what needs to be changed to migrate into ROS2.
It would be helpful if you tell me more about the changes or give me a link.
That aside, I don't think you are supposed to use ROS' structures (e.g., Nodehandle, Time, Subscriber, Publisher) inside the hpp file as the bridge library is intended to be used on non-ROS applications (standard C++11 applications in this case).

the bridge library is intended to be used on non-ROS applications

Do you mean to say that I can' t use it to port my existing ROS application?

Why would you need to port a ROS application when it's already a part of ROS ecosystem?
The library is for C++11 non-ROS applications to communicate with ROS system.
That's why you don't see any ROS structures in my code, just websocket and json.

I want to port it from ROS 1 to ROS 2 in order to compare the performance.

If you want to compare the performance of ROS and ROS2, why don't you just use them by themselves without rosbridge?

It's a really long story. BTW thanks for the help.

I'm not sure what you want to do here, hopefully you can figure it out.


Extra Line Spaces

Hello,
When copying from a listing in the editor then pasting in another app extra line spaces are inserted throughout the listing. Tried this on three different other apps and the behaviour is replicated. Can this please be fixed i.e. remove the additional newline characters presumably?
Thanks.

I think the new code editor behaves well.
Thanks


RNGoogleSignin was called with 3 arguments but expects 2 on iOS

I'm not sure how this gets called, but it works for me on android fine.  II'm pretty much following the example...
  componentDidMount() {
    GoogleSignin.configure({
      scopes: [],
      iosClientId: 'myiosid',
      webClientId: 'mywebid',
      offlineAccess: false
    });

    GoogleSignin.currentUserAsync().then((user) => {
      console.log('USER', user);
      this.setState({user: user});
    }).done();
  }

rn 0.18.1, xcode 7.2, react-native-google-signin 0.4.0

did you update the RNGoogleSignin folder inside your ios project ?


use "is-browser" package

Because node/io does not need cross-realm support. All that a server environment needs is:
return typeof value==="string" || value instanceof String===true;

Or, have two files in the release: client.js and server.js

You're incorrect - node does need cross-realm support. See the vm core module.

Related to #1


Update exposed libraries for Mendix 8.9

In 8.9 we're updating the libraries that can be used in pluggable widgets. Also added some libraries that were missing before.

Thanks @jobvs. The list of libraries is getting very long, which is a good thing, but it's a little hard to read. Instead of a long list of links in a doc, could we give one link to a repo or somewhere else which also has this info?

Currently there is no other place that has this info. It really is what this doc page is about. Do you have a suggestion for another place? Turning it into a table might help readability?

Currently there is no other place that has this info. It really is what this doc page is about. Do you have a suggestion for another place? Turning it into a table might help readability?

Ok I understand @jobvs . Yeah, a table was going to be my plan B. I'll mess around with it and see if I can make it prettier. Thanks for adding the PR.


How to use this ?

Yesterday I installed it directly using "via link" in extensions tab
But I unable to find the UI of this utility. I also searched in scripts, but can't find anything
Could you please post some screenshots to show how to use this ?

If the script is installed (git clone or "install from url"), you should see it in the img2img tab, under scripts:

If not, you may want to check here:

You may also want to check your command prompt window for errors. Mind giving those a look at letting me know? I'm particularly interested in any adverse behavior after yesterday's A1111 changes.

@LonicaMewinsky
Thanks.
But  not working

No errors in console logs

not a fix but an easy work around is to put the python script directly into the scripts folder


ini file aborts script

I am having a problem using an ini file for the connection criteria
both in using a default 'dbsync.ini' and the same result using the '--config-file my-cfg.ini' option
I have verified a working command line, however when I move that config data into a *.ini file the script seems to abort right after the message;
Reading ini file 'my-cfg.ini.ini'
--verbose displays nothing additional.
though
-v does trigger a display of
ea-php-cli Copyright 2017 cPanel, Inc.
oddly ... if I leave the --execute off the command, I do get;
[notice] Dry run only. No data will be written to target.
when using without an ini file and --verbose the next line is;
[info] Hash calculation:
with the ini file neither that or anything else is displayed following the reading of the ini and Dry run notice.
*** EDIT ***
not sure if this should be a separate post ... but IS related to the the reading of the ini file.
the password string is rejected if includes certain characters. double quotes and carats for sure ... possibly others? though that same password string works fine via command line without ini.

any update on this?
any additional information needed?
we would surely like to use this handy script and attach it via cron ... we hesitate to do so via individual command-lines.
thanks

Judging by the error message (contains the words "ea-php-cli Copyright 2017 cPanel, Inc."), it looks like the issue you are having is related to the platform you are running this on. It doesn't look like db-sync is being executed properly. Unfortunately there isn't enough info here for me to help diagnose the exact issue... is there anything else you can provide?

I am a linux novice, so not really sure what else might be useful?!?!
CentOS release 6.9 (Final)
BlueHost VPS host running cPanel v. 11.66
ea-php-cli Copyright 2017 cPanel, Inc.
PHP 7.0.26 (cli) (built: Dec  4 2017 16:05:39) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with the ionCube PHP Loader (enabled) + Intrusion Protection from ioncube24.com (unconfigured) v6.1.0 (), Copyright (c) 2002-2017, by ionCube Ltd.
if there is something specific that would assist you in finding a solution, just ask!

I'm going to close this issue for now - seems like you might be having problems with a specific host provider and I don't think I'm going to be able to help

it is fixed. Actually it is not the code issue. it is about the mysql
version issue. Basically higher mysql version has more restriction on the
date with null value and it mesed up there. if you turn such off and the
code runs good. Thanks!
Shenghua Li, CEO
Halcool LLC
Tel:<PHONE_NUMBER>
email<EMAIL_ADDRESS>On Wed, May 9, 2018 at 6:57 AM, Joe Green<EMAIL_ADDRESS>wrote:

Closed #28 https://github.com/mrjgreen/db-sync/issues/28.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mrjgreen/db-sync/issues/28#event-1617444249, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfCDQxiauamCSKkzUmqLDo8gnit_rXr_ks5twtmPgaJpZM4O5CEw
.


Environment Problem

Hi authors,
Thanks for initial code, I want to konw are there any strict requirements for the Python dependent environment configuration of your model?

In my experience, there is no strict requirement.
I used python 3.7 and the version of packages is listed in src/requirements.txt.

Thank you very much for your reply timely.


Skip Button/Go to next step functionality enhancement

This enhances 'Step Challenges' functionality. Currently, Step Challenges force user to click on 'Open in New Tab'.
The improvement is that 'Open in New Tab' is not forced on users if they have completed the challenge already. The code verifies if a user has completed a challenge or not. If completed, he will have a free pass at 'Go to next Step'.
Tested in local machine. Chrome-- both for 'logged in' users and 'not logged in' users.
To test in local machine, I removed completed challenges using mongo shell.
To remove the completedChallenges list in your database, in order to simulate that you are doing challenge/waypoint for the first time, I followed the following steps.

Open mongo shell mongo shell
use freecodecamp
db.user.find().pretty()
Identify the "username".
db.user.update({"username":__username__},{$set:{"completedChallenges":[ ]}})

Closes #3690

Well done!