Enhancement: Use the same URL layout as Archive.org for viewing ArchiveBox Snapshots https://archive.org/web/<URL>

To visit an archived version of a website (or archive it automatically) on Archive.org, one can just visit http://web.archive.org/web/https://example.com/ and it will redirect to http://web.archive.org/web/20230116145642/https://example.com/ (or whatever the most recent snapshot timestamp is).
To really emobdy the tagline "ArchiveBox is a self-hosted version of archive.org" we should properly support their URL scheme too.
e.g.

https://demo.archivebox.io/web/https://example.com should redirect to the most recent snapshot https://demo.archivebox.io/web/20230116145642/https://example.com

note: support both the ArchiveBox-style timestamp in unix timestamp format e.g.<PHONE_NUMBER> or the Archive.org-style<PHONE_NUMBER>5642 format and truncated forms 2023, 202301, 20230116
note: also support visiting using snapshots using ulid uuid instead of timestamp as slug, e.g. https://demo.archivebox.io/01ARZ3NDEKTSV4RRFFQ69G5FAV/...
note: support auto prefix-matching slugs so that 2023 matches 202301, 20230116,<PHONE_NUMBER>5642 automatically, and 01AN4Z07BY matches 01AN4Z07BY79KA1307SR9X4MV3  automatically

Full spec:

https://demo.archivebox.io/web/<SLUG> where SLUG can be:
- an original URL, with or without scheme, e.g. https://example.com/index.html, 'example.com/index.html' ➡ redirect to most recent snapshot for https://demo.archivebox.io/web/20230116145642/https://example.com/index.html
- an ArchiveBox snapshot UUID in ulid/spec format 01AN4Z07BY79KA1307SR9X4MV3/index.html or timestamp prefix 01AN4Z07BY/index.html  ➡ redirect to that exact snapshot https://demo.archivebox.io/web/20230116145642/https://example.com/index.html
- an ArchiveBox snapshot timestamp in YYMMDDHHMMSS, shortened forms like YYYYMM, or unix timestamp format e.g.<PHONE_NUMBER>5642/index.html or<PHONE_NUMBER>56/index.html, 202301/index.html,<PHONE_NUMBER>/index.html  ➡ redirect to most recent snapshot matching that prefix https://demo.archivebox.io/web/20230116145642/https://example.com/index.html
Subtasks:

adds derived ulid field + migration to coalesce old uuid and timestamp fields into new ulid format (+asserts all snapshot timestamps are valid and are between 1900 and 2100 AD)
update admin and index UI to show ULID of old UUID4 xxxx-xxxx-xxxxxxx format, add ULID diagram in docs breaking it down into timestamp and randomness
create disambiguation page to show all the matching results for a given SLUG if it's the prefix for multiple possible snapshots
reject Snapshot UUIDs being created that begin with 0, 1,2,htt to make prefix-matching faster and less error prone (avoids clashing with 199x*/20** year, 1* unix timestamp, 01* ULIDs, or http(s?) URL slug prefixes)
add docs examples on how to truly "self-host your own archive.org", add screenshot side-by-side of URL bar examples for visiting snapshots on Archive.org and demo.Archivebox.io

At least one project interested in using ArchiveBox (Kicksecure) would also be interested in this functionality, or any functionality that allows turning a URL into an archived URL via a simple transformation (i.e., append https://archivebox.example.org/whatever/goes/here/<URL>). The use case for this is:

We have two very large MediaWiki instances, with wikis that contain many links to external websites.
For each of those links, we want to link to an archived version of the page we link to.
If the corresponding url for https://example.com/my-page is https://archivebox.example.com/BN833Z or something like that, there's no easy way to convert a link to an ArchiveBox link. Thus adding the archive links requires running a large "archive job" that archives all unarchived links, then gets the corresponding URLs and mass-edits them into the Wiki. This is a pain.
If the corresponding url for https://example.com/my-page is https://archivebox.example.com/web/https://example.com/my-page, no mass-editing is required. A MediaWiki plugin can be used to put a button after each link that offers an archived version of the webpage to the user. (This is what we already do with archive.org.)

Worthy of note, the format doesn't have to be exactly like archive.org for this to work. If ArchiveBox supported the MementoWeb API similar to how archive.today was, we would end up turning https://example.com/my-page into https://archivebox.example.com/timegate/https://example.com/my-page, which works just as well.
Is help wanted here? Depending on how suitable ArchiveBox is for Kicksecure's use case, this might be a feature we'd be willing to implement and work on upstreaming.

This is actually already supported! You can just visit https://archivebox.example.com/archive/https://example.com/archived/url.
We use this feature extensively with several of our paying clients who have similar needs as what you describe.
It's not fully compatible with archive.org / memento, but I have plans to make it cross-comaptible with both in the future.


undefined references linking to clapack

Hi there,
I'm having an issue linking the library to my executable:
 [ 25%] Linking C executable wccsukf
/home/erwindassen/.local/share/JetBrains/Toolbox/apps/CLion/ch-0/173.3727.114/bin/cmake/bin/cmake -E cmake_link_script CMakeFiles/wccsukf.dir/link.txt --verbose=True
/usr/bin/cc -g   CMakeFiles/wccsukf.dir/cUKF.c.o CMakeFiles/wccsukf.dir/wccsukf.c.o CMakeFiles/wccsukf.dir/main.c.o  -o wccsukf /home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a /home/erwindassen/.conda/envs/wccs-dev/lib/libblas.a
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(dtrtri.c.o): In function `dtrtri_':
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/dtrtri.c:169: undefined reference to `s_cat'
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(ilaenv.c.o): In function `ilaenv_':
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:188: undefined reference to `s_copy'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:429: undefined reference to `s_cmp'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:430: undefined reference to `s_cmp'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:430: undefined reference to `s_cmp'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:431: undefined reference to `s_cmp'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:432: undefined reference to `s_cmp'
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(ilaenv.c.o):/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:439: more undefined references to `s_cmp' follow
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(ilaenv.c.o): In function `ilaenv_':
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:245: undefined reference to `s_copy'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:246: undefined reference to `s_copy'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:247: undefined reference to `s_copy'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:265: undefined reference to `s_cmp'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:266: undefined reference to `s_cmp'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:521: undefined reference to `s_cmp'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:522: undefined reference to `s_cmp'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:300: undefined reference to `s_cmp'
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(ilaenv.c.o):/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/ilaenv.c:301: more undefined references to `s_cmp' follow
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(iparmq.c.o): In function `iparmq_':
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/iparmq.c:205: undefined reference to `log'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/iparmq.c:206: undefined reference to `i_nint'
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(dpotf2.c.o): In function `dpotf2_':
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/dpotf2.c:163: undefined reference to `sqrt'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/SRC/dpotf2.c:196: undefined reference to `sqrt'
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(dlamch.c.o): In function `dlamc2_':
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c:525: undefined reference to `pow_di'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c:643: undefined reference to `s_wsfe'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c:644: undefined reference to `do_fio'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c:645: undefined reference to `e_wsfe'
/home/erwindassen/.conda/envs/wccs-dev/lib/liblapack.a(dlamch.c.o): In function `dlamch_':
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c:119: undefined reference to `pow_di'
/feedstock_root/build_artefacts/recipe_root_1486418675549/work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c:115: undefined reference to `pow_di'
collect2: error: ld returned 1 exit status
CMakeFiles/wccsukf.dir/build.make:148: recipe for target 'wccsukf' failed

This might well be an issue on my side but I have no clue. Any dependencies I'm not ware of? The library is compiled into a static library right?
Help is very much appreciated.
Kind regards,
Erwin

Erwin,
I recompiled the feedstock  conda-forge recipe and was successful to create the library.
git clone git@github.com:conda-forge/clapack-feedstock.git
cd clapack-feedstock
conda build recipe -c conda-forge

Looking at your error message, it seems that you are missing F2CLIBS.  This is where s_cat, s_copy, s_cmp,... are defined.
F2CLIBS comes with the clapack library.  cmake and then make will compile it.

Thank you that fixed... I knew it was on my end ;)


Rasa core server silent start

Rasa Core version: 0.11.3
Python version: 3.6.2
Operating system (windows, osx, ...): windows server
Issue:
It's not specific to RASA Core but curious to get some suggestions  , how to start rasa core server silently. (to avoid closing, as windows service)
Content of domain file (if used & relevant):

Please ask these kind of questions in our forum


Behavior of accessor access created with offset

Hi,
I have some code where I create sycl::accessors with an offset intended to index with an offset to the underlying buffer.
sycl::buffer buf{data_ptr, sycl::range{N * M}};
for(int i = 0; i < M; i++) {
  Q.submit([&](sycl::handler& h) {
    sycl::accessor acc{buf, h, sycl::range{N}, sycl::id{i * N}};
    ...
  });
}

I would have assumed that when I index acc[idx] it would be offset with i * N, however, when trying this it is not offset and I have to index with acc[acc.get_offset() + idx], to get the correct offset. Is this expected?

This is a remnant from SYCL 1.2.1. In SYCL 1.2.1, indexing would always start from the base of the allocation. In SYCL 2020, indexing was changed to start from the offset. We have not yet made that change.

That makes sense, thanks!


Add time structure.

About time, I am more curious.
Is there a requirement  to use time?
I think time in the database is a feature  that will be obsolete

About time, I am more curious.
Is there a requirement to use time?
I think time in the database is a feature that will be obsolete

Many database has it, like mysql, neo4j.

Well done.
As we discussed, Time and DateTime should not consist of timezone.

Fixed.


RichText-pluginInit fails

Hi,
I'm trying to replicate your demo with another video, hosted locally on my laptop (via node.js). It's supposed to be a web-app and so I'm trying to download and wrap in as many dependencies as I can. I'm working off the source in http://danielcebrian.com/annotations/demo.html .
I downloaded the plugin locally and was able to make some headway but started getting this error :

The plugin failure happens at page load and then any interaction with the annotation buttons produces the other errors. My $(document).ready() function inits the plugin and looks like this :
$(document).ready(function(){
// init the video containers
videojs('main-player').ready(function(){
	var mainPlayer = this;

	mainPlayer.controls(true);
	mainPlayer.dimensions($("#container-main-player").width(), $("#container-main-player").width() * 9 / 16);
	mainPlayer.preload(true);
	mainPlayer.src("media/24.MP4");

	var options={};

	//Add the div id to annotate by Annotator. In the demo.html the id is "airlock" too.
var ova = new OpenVideoAnnotation.Annotator($('#container-main-player'),options);

});

})
Thanks in advance.

I mis-read the error. It's not from the Richtext plugin. Sorry about that. I will re-post once I understand what's failing.


Update to Angular 13.3

Not sure if this will work, but we'll let GitHub Actions determine that! Updated with ncu -u.

@mshima Can you please approve the workflows for this PR so I can see if there are any failures?

I’ve missed this pr.


[QNN] Add qnn.rsqrt op

Add QNN op for reciprocal sqrt, the default legalization goes through dequantize->rsqrt->quantize

Probably just need to rebase on main after https://github.com/apache/tvm/commit/589fc01026dce43cc096f458972b4c0ba8bf2577
The CI failure does not seem to be the fault of the PR


Typeguards with destructuring parameters

Search Terms
Typeguard
type narrowing
destructuring
Suggestion
It'd be nice to be able to have typeguard functions with destructuring arguments.
Use Cases
When manipulating tuples or other anonymous structured types, whose typeguard relies only on a small part of the object, it would make the code much easier to read.
Currently, typeguards cannot be used with destructuring arguments, which makes it a weird special case.
Examples
const val: Array<[string, boolean]> = ([] as Array<[string | undefined, boolean]>)
    .filter(([foo, bar]: [string | undefined, boolean]): [foo, bar] is [string, boolean] => foo !== undefined);

const val2: Array<[string, boolean]> = ([] as Array<[string | undefined, boolean]>)
    .filter((val: [string | undefined, boolean]): val is [string, boolean] => val[0] !== undefined);

https://www.typescriptlang.org/play/index.html#src=const val%3A Array<[string%2C boolean]> %3D ([] as Array<[string | undefined%2C boolean]>)
    .filter(([foo%2C bar]%3A [string | undefined%2C boolean])%3A [foo%2C bar] is [string%2C boolean] %3D> foo !%3D%3D undefined)%3B%0D%0A%0D%0Aconst%20val2%3A%20Array%3C%5Bstring%2C%20boolean%5D%3E%20%3D%20(%5B%5D%20as%20Array%3C%5Bstring%20%7C%20undefined%2C%20boolean%5D%3E)%0D%0A%20%20%20%20.filter((val%3A%20%5Bstring%20%7C%20undefined%2C%20boolean%5D)%3A%20val%20is%20%5Bstring%2C%20boolean%5D%20%3D%3E%20val%5B0%5D%20!%3D%3D%20undefined)%3B%0D%0A%0D%0Aconst%20val3%3A%20string%5B%5D%20%3D%20(%5B%5D%20as%20Array%3Cstring%20%7C%20undefined%3E)%0D%0A%20%20%20%20.filter((foo%3F%3A%20string)%20%3D%3E%20foo%20!%3D%3D%20undefined)%3B%0D%0A
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. new expression-level syntax)

I'm afraid of bumping a super old thing, but I think i'm running into something that would be resolved if this was.
Given this function export function toPolicy (value: any): [string[], null] | [null, Policy] {   try {     return [null, policyJSONSchema.validateSync(value) as Policy]   } catch (err) {     return [err.errors, null]   } }
Given this callsite const [validationErrors, policy] = toPolicy(req.body)       if (validationErrors !== null) {         throw new BadRequest(`invalid policy: ${validationErrors.join(', ')}`)       }       found.version = policy.version
The policy.version policy is coming back as possiby null, even though it cannot be null if validation errors is null.


[Feat]: Add Perplexity AI website

What feature?
I would like to add Perplexity AI.
Perplexity AI is an advanced artificial intelligence system that specializes in natural language processing tasks. It employs state-of-the-art models to measure the level of understanding and coherence of text. By evaluating the perplexity of language, Perplexity AI provides insights into the complexity and fluency of written content, aiding in language generation, machine translation, and text comprehension tasks.
Add screenshots
Add screenshots
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hello @JasonDsouza212, I have added my work still my issue has been closed. Please look into the matter.


Are there any document about control module?

there are too many code about control module, and it seems there are several times bug fix about control part. so can you please some documentations to help to review the control module, cause it is the safe guarantee part of the system.

@Wsine There are a few documents related to control under https://github.com/ApolloAuto/apollo/tree/master/docs/howto
Also the default lat + lon controllers have more than thousands of  hours of test on it and even on different vehicle platforms and are quite reliable under different driving scenarios.
The fix is mainly for MPC controller. Which is by default turned off and the internal version of it has also been tested for hundreds of hours as well.

thanks @Capri2014 . I am writing a control algorithm, so i take apollo control algorithm as references. thanks for answering.

cool @Wsine please keep us posted. :)


Add new field which indicates the deployment scope of stacks/samples

Which area/kind this issue is related to?

/kind task
/area registry
Issue Description

#1197 needs a new field under the index schema to indicate the deployment scope of a stack/sample, e.g. innerloop or outerloop.
Acceptance Criteria

[ ] Add a new field for deployment scope which accepts values innerloop, outerloop, or both
[ ] Update test cases to include this field
[ ] Update documentation on index schema to include this field

/kind task

blocked by investigation issue #1322

Still needed and waiting for #959 to be resolved.

PR changes are ready for review: https://github.com/devfile/registry-support/pull/237


Instalando a ferramenta kubeadm

nataliagranato@DPCNATALIAGRANATO:~$ sudo curl -fsSLo /usr/share/keyrings/kubernetes-archive-keyring.gpg https://packages.cloud.google.com/apt/doc/apt-key.gpg
nataliagranato@DPCNATALIAGRANATO:~$ echo "deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list
deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main
nataliagranato@DPCNATALIAGRANATO:~$ sudo apt-get update
 apt-get install -y kubelet kubeadm kubectl
0% [Working]k hold kubelet kubeadm kubectl
Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease
Ign:4 http://ppa.launchpad.net/certbot/certbot/ubuntu focal InRelease
Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:7 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease
Hit:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Err:9 http://ppa.launchpad.net/certbot/certbot/ubuntu focal Release
  404  Not Found [IP: <IP_ADDRESS> 80]
Ign:2 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
Get:1 https://pkgs.k8s.io/core:/stable:/v1.30/deb  InRelease [202 kB]
Err:10 https://packages.cloud.google.com/apt kubernetes-xenial Release
  404  Not Found [IP: <IP_ADDRESS> 443]
Err:1 https://pkgs.k8s.io/core:/stable:/v1.30/deb  InRelease
  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/certbot/certbot/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'https://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://pkgs.k8s.io/core:/stable:/v1.30/deb/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'https://pkgs.k8s.io/core:/stable:/v1.30/deb  InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
nataliagranato@DPCNATALIAGRANATO:~$ sudo apt-get install -y kubelet kubeadm kubectl
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package kubelet
E: Unable to locate package kubeadm
E: Unable to locate package kubectl
nataliagranato@DPCNATALIAGRANATO:~$ sudo apt-mark hold kubelet kubeadm kubectl
E: Unable to locate package kubelet
E: Unable to locate package kubeadm
E: Unable to locate package kubectl
E: No packages found

/triage needs-information
What did you want to report @nataliagranato ?

This may be a bug report about a stale localization
/area localization

It seems like this issue might be related to an existing issue https://github.com/kubernetes/website/issues/44765 (possibly duplicate), which acknowledges outdated information within the Brazilian Portuguese documentation for the Install Kubeadm guide.

This issue is not directly related to localization because @nataliagranato used the original content.
But I'll raise the flag with the localization team to work to update the page in PT-BR :)
We can close this issue :)

https://v1-29.docs.kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ looks up to date, but https://v1-29.docs.kubernetes.io/pt-br/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ is stale.

/kind bug
/remove-triage needs-information

Having the same issue with Github Actions CI today I think:
Run npx playwright install --with-deps chromium
Installing dependencies...
Switching to root user to install dependencies...
Get:1 file:/etc/apt/apt-mirrors.txt Mirrorlist [1[4](https://github.com/CleverGift/clevercards-sqa-automation-web-v2/actions/runs/8814985442/job/24196005378#step:5:5)2 B]
Hit:2 http://azure.archive.ubuntu.com/ubuntu jammy InRelease
Get:3 http://azure.archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Get:6 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
Err:6 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)

E: Failed to fetch https://packages.microsoft.com/ubuntu/22.04/prod/dists/jammy/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease' is no longer signed.
Failed to install browsers
Error: Installation process exited with code: [10](https://github.com/CleverGift/clevercards-sqa-automation-web-v2/actions/runs/8814985442/job/24196005378#step:5:11)0
Error: Process completed with exit code 1.

Just tested the preview and it seems to be working fine: https://github.com/kubernetes/website/pull/46001#issuecomment-2074896697

The pt-br page should be fixed with #46001 which is based on the latest en version.
That was the problem, the page in Portuguese is not updated.

So I guess we just need to review and merge https://github.com/kubernetes/website/pull/46001 😉

/close


ISO duration formatting instead of seconds

Describe the bug
When defining duration uda in taskrc:
uda.myestimate.type=duration
uda.myestimate.label=Estimate

it's displayed correctly in the "next" report, eg: "PT3H".
In vit it's displayed without formatting, in seconds: "10800"
I want to have the same effect as in taskwarrior reports.
I've tried to write my own formatter, but sadly it doesn't seem to be picked up:
~/formatter/duration.py
from vit.formatter import Duration

class Duration(Duration):
    def format(self, obj, task):
        if not obj:
            return self.empty()
        formatted_duration = self.format_duration(obj)
        return (len(formatted_duration), self.markup_element(obj, formatted_duration))

    def format_duration(self, obj):
        return "FOO" # test value

    def markup_element(self, obj, formatted_duration):
        return (self.colorize(obj), formatted_duration)

Thanks.

Hmm,
problem resolved itself somehow...
When I added first duration uda in taskwarrior few days ago via command "task xxx edit myestimate: 3h", it was saved like that:
2020-12-05 22:28:39 Myestimate set to '10800'.

But today, when i set this uda field in another task, it is saved like that:
2020-12-11 22:46:05 Myestimate set to 'PT2H'.

First one is only displayed correctly in tw, not in vit. Second one is displayed properly in both apps.
Strange.

Unable to reproduce.
Used https://github.com/vit-project/vit/blob/2.x/scripts/generate-dummy-install.sh to generate test install
Added the following to .taskrc:
uda.myestimate.type=duration
uda.myestimate.label=Estimate

report.next.columns=id,start.age,project,description,urgency,myestimate
report.next.description=Most urgent tasks
report.next.filter=status:pending limit:page
report.next.labels=ID,Active,Project,Description,Urg,Est
report.next.sort=urgency-

Duration renders correctly in VIT:

Thanks for your effort that you've put in reproducing this.
I think I found the reason for the inconsistency I saw.
Taskwarrior defines possible duration formats to use in commands here: https://taskwarrior.org/docs/design/task.html#type_duration
Accordignly to docs that formats:
myestimate:1000s
is perfectly fine.
So when I execute import command that way:
task import tmp_task.txt
and my file tmp_task.txt contains:
{   "id": 296,   "myestimate": "1000s",   "description": "bar",   "entry": "20201219T235203Z",   "modified": "20201220T182347Z",   "project": "PROD_TOOLS",   "start": "20201220T181907Z",   "status": "pending",   "uuid": "c0cf95b0-9a7a-42c7-9819-1824dc9aa32f",   "urgency": 25 }
then taskwarrior renders it correctly:

vit on the other hand show it as raw values:

Now, when I edit task with "mod" command:
❯ task mod 296 myestimate:1000s
it's rednered correctly in both taskwarrior reports and in vit (sane as in the first picture). So there must be some differences between task modify and task import inner workings?


Humble fix

Description
This PR fixes:

ir_emitter to avoid global range redefinition
lets the robot move backward by  setting safety_override to full
Messages names after https://github.com/iRobotEducation/irobot_create_msgs/pull/10

Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Correct execution in Gazebo.
# Run this command
ros2 launch irobot_create_gazebo_bringup create3_gazebo.launch.py

Checklist

[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Hi @fmrico, thank you for the contribution.
First of all, note that the ROS 2 Humble branch is not fully supported yet due to some runtime issues that we haven't fixed yet.
The PR looks good to me.
The CI is running with ROS 2 Galactic, so you can ignore the failure.
I will try the PR (or add a Humble CI) and then merge.

One note, we had previously chosen to have safety override default to “none” so that users are in the habit of changing it if they want to drive backwards, as the Create3 defaults to “none”.  I am open to changing it, I wonder if we should document the difference somewhere in the sim so users will know they need to change the setting on Create to get the same performance with the same code

Good point @justinIRBT.
@fmrico, I tested the PR and it looks good to me.
Would you mind excluding the change to the safety parameter? We could have that as a separate PR as it will require some discussions and possibly changes to the documentation.

Hi @alsora! Reverted safety parameter

Thank you!
I plan to do a release of ROS 2 Humble simulator this week.


OSFUSE-306: renaming the archetypes to remove references to JBoss Fuse

Renaming the archetypes to reflect the new name of the quickstarts.
This can be merged before changing the repository names.

ok to test

@rawlingsj thanks, but it seems that the projects need to be renamed first. It worked on my machine because the module folders were not empty, but there is a gitignore preventing it to be committed on git.
I'll ask you to retest later. Thanks.

retest this please

[merge]


publish .local hosts via avahi

This is a (wip) pull request for #16. For every rap.host with a .local suffix, the avahi daemon will publish the .local host in a local network. In addition a variable rap.avahi_type was introduced in order to set the avahi type.
This pull request has the following issues:

The port number used by avahi is the port that the reverse proxy maps to, while it should probably be port 80 (always?)
The avahi daemon publishes the .local host via multicast, which does not find its way into the LAN via docker. Reading other issues on github a suggestion was to use --net=host with this container, but this breaks rancher-gen-rap, which relies on accessing information about the running container via http://rancher-metadata. Unfortunately, with --net=host the metadata does not provide that information anymore.

Does anyone see a way to integrate this?

Hello ,
Did you manage to solve point 2, as I don't really want to merge something that is not really working with rancher...

No, unfortunately not. I was hoping some else had an idea.

Technically the rancher managed network is layer 3, so it would not support multicast without using --net=host. You may be able to augment this with another service running side-by-side with the RAP container.


Can't download source image from S3

In v3.23 and early version the S3 download success
log:
INFO    [2024-11-07T13:53:54Z] Started /insecure/rs:fit:600:600/plain/s3://bucket/path/%25E6%259B%25B8_114.jpeg  request_id=NsymNJB2qp_Ivv-z-wDj1 method=GET client_ip=<IP_ADDRESS>
INFO    [2024-11-07T13:53:54Z] Completed in 201.934241ms /insecure/rs:fit:600:600/plain/s3://bucket/path/%25E6%259B%25B8_114.jpeg  request_id=NsymNJB2qp_Ivv-z-wDj1 method=GET status=200 processing_options="Width: 600; Height: 600; Format: jpeg" client_ip=<IP_ADDRESS> image_url="s3://bucket/path/%E6%9B%B8_114.jpeg"`

v3.25 ~ v3.26.1 the S3 download failed
log:
INFO    [2024-11-07T13:55:33Z] Started /insecure/rs:fit:600:600/plain/s3://bucket/path/%25E6%259B%25B8_114.jpeg  request_id=KJslFXrkQuE3-OBNOH4Ln method=GET client_ip=<IP_ADDRESS>
ERROR   [2024-11-07T13:55:33Z] Completed in 150.99321ms /insecure/rs:fit:600:600/plain/s3://bucket/path/%25E6%259B%25B8_114.jpeg  request_id=KJslFXrkQuE3-OBNOH4Ln method=GET status=404 client_ip=<IP_ADDRESS> error="Can't download source image: Status: 404; operation error S3: GetObject, https response error StatusCode: 404, RequestID: WXAXVXMA05S09D3V, HostID: 0l9/STnFC5RrmaOOMbQBC8XiWtG+dHEpvUpAxeOEopID8wa8x9k13Y7fMhizfBCMQEsrAjpjkEre6jG2K0zOwSInNtsXWaz8, NoSuchKey: "

Maybe the filename with '%25' cause this 404 ...

Hey @scrazy77?
What's the real key of the object in S3? Does it work if you use s3://bucket/path/%E6%9B%B8_114.jpeg source URL?

s3://bucket/path/%E6%9B%B8_114.jpeg works! but don't know why different results between 2 versions.

That's because we fixed the handling of escaped symbols in non-HTTP(S) source URLs in v3.25.0.
I guess the filename in S3 is 書_114.jpeg. %25E6%259B%25B8_114.jpeg is a twice-URL-encoded filename. Double encoding is a workaround for the bug fixed in v3.25.0.


fix typo

 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.

Thanks for your pr. Please sign the CLA for multiple repositories or organizations.  : )

Ok, done signing.


Audit the portsnap recipe and add testing

We need to audit the recipe for portsnap and get it under test kitchen to have better confidence in releases.

Need Bento images for FreeBSD-9.0, FreeBSD 10.0, and FreeBSD 10.1


implement subtract_scalar_fn for ConstantEncoding

While implementing FoR compare, I've observed that the subtract_scalar_fn isn't implemented for ConstantEncoding yet. Here's my proposal:

Implement a subtract($self, other: $PrimitiveScalar) function for PrimitiveScalar.
Obtain a new Scalar using lhs.scalar().as_primitive().subtract(another_primitive_scalar).
Utilize the new Scalar to create a new ConstantArray.

I believe this issue is closed by #1640


Cannot find any type declaration files of "SheriffSettings" in eslint-config-sheriff

I want to look up the "SheriffSettings" type declaration of the package when I configure it.  I found it in your github monorepo called "sheriff-type".. However I realize that it is a seperated package in your repo, probably not build. I tried downloading it and it pop up 404 not found... Should it be contained in "eslint-config-sheriff" package or as a seperated package on official npm repo?

I didn't publish it to npm.

I didn't publish it to npm.

Do you have a plan to push it?

@KevinKVJ it was meant for internal development but i can plan to publish it in some form, yes.

Perfect! I get it!! Thank you!


Error running the project following the instructions

I followed the instructions on Linux (WSL) and got the following error:
~/stuff/certified-reasoning/learning$ python3 lm_tool.py
Traceback (most recent call last):
  File "lm_tool.py", line 23, in <module>
    import domain
  File "/home/oren/stuff/certified-reasoning/learning/domain.py", line 17, in <module>
    from util import choose_from_list, parse_sexp, format_sexp, randomize_atoms
  File "/home/oren/stuff/certified-reasoning/learning/util.py", line 43, in <module>
    def encode_batch(b: list[str], device: torch.device, bos=True, eos=True) -> torch.LongTensor:
TypeError: 'type' object is not subscriptable

Also Tiktoken is missing from requirements.txt, I had to add it.

My bad, I was using an old Python version (I'm a Python noob).
Now I'm getting this
~/stuff/certified-reasoning/learning$ python3 lm_tool.py
Traceback (most recent call last):
  File "/home/oren/stuff/certified-reasoning/learning/lm_tool.py", line 24, in <module>
    import tactics
  File "/home/oren/stuff/certified-reasoning/learning/tactics.py", line 16, in <module>
    from policy import Episode
ModuleNotFoundError: No module named 'policy'

Thanks for the PRs! I'll leave this open for a few days just in case you hit anything else. Feel free to post here if so!


Release 5.1.5 - update documentation

Need to update the documentation for the 5.1.5 release.

I updated the documentation.  Close this issue.


MINOR: Add LEAVE_GROUP_EPOCH to GroupMetadataManager

Replacing the use a hardcoded -1 with a constant (LEAVE_GROUP_EPOCH) that provides more clarity. Since static members also have a magic number (-2), this will motivate future commits to use constants instead of hardcoded values.

Thanks for this PR @kirktrue ! I can see easily see how this can be extended for static membership case. I had just one question(LGTM o/w) =>

Do these lines also qualify for having -1 replaced with LEAVE_GROUP_EPOCH? In this case, it appears to be a member leave group situation.

I've updated the code to use the constant in place of -1. Thanks!

@dajac @vamossagar12 Please take another look. Thanks!

Thanks @kirktrue , LGTM (I had already approved).


Some issues of design

The title block doesn't work in awvwgk.github.io/fpm-docs/

en/index.html

de/index.html

zh_CN/index.html

es/index.html

The language links only work on the page index.html.

It shows up for me, which browser are you using?

Google Chrome Version 95.0.4638.69 (Official Build) (64-bit)

title block  (doesn't work)
language links (doesn't work, except in index.html)

Mozilla Firefox 93.0

title block (Ok!)
language links (doesn't work, except in index.html)

I fixed the language navigation. Can reproduce the missing style for the title block, maybe I just use a bootstrap card instead of creating it directly in CSS.

other tests
on Windows 10
Firefox Version 94.0.2 (64-bit)

title block (Ok!)

Google Chrome Version 96.0.4664.46 (build 64-bit)

title block (doesn't work)

Microsoft Edge Version 96.01054.41 (64-bit)

title block (doesn't work)

on Android 7.12
Chrome Version 95.0.4638.74

title block (doesn't work)

I switched to a bootstrap card now, I don't think the background gradient did add much value.


Upgrade: csi-attacher from v2.1.0 to v2.1.1

This PR follow up the missing files from ceph-csi:v2.0.1, besides:

deploy/cephfs/kubernetes/csi-cephfsplugin-provisioner.yaml
deploy/rbd/kubernetes/csi-rbdplugin-provisioner.yaml

See https://github.com/kubernetes-csi/external-attacher/releases/tag/v2.1.1
See https://github.com/kubernetes-csi/external-attacher/blob/v2.1.1/CHANGELOG-2.1.md

@humblec PTAL

@Madhu-1 may I have your suggested commit message? I will update it accordingly.

@Madhu-1 may I have your suggested commit message? I will update it accordingly.

commit message still says Upgrade: csi-attacher from v1.2.0 to v2.1.1  you need to update it too

@Madhu-1 thank you very much, how silly am I...

LGTM. Thanks..

@hswong3i this can not automatically get merged as a rebase is attempted by the merge bot. To allow this, you need to check the

[ ] Allow edits from maintainers

box on the right side of the PR.

@hswong3i this can not automatically get merged as a rebase is attempted by the merge bot. To allow this, you need to check the

[ ]  Allow edits from maintainers

box on the right side of the PR.

@hswong3i can you please addlow edits from maintainers? we need it for CI to merge this PR

@Madhu-1 I don't have such button on RHS...

adding this for reference

@hswong3i when creating the PR you will get that option, just remember to enable it when you open a PR.

@nixpanic @humblec how about merging this PR manually?

@nixpanic @humblec how about merging this PR manually?

or do we have any other option?

@Madhu-1 one option here is opening a new PR and checking that option. @hswong3i does that work for you ?

Ok I will reopen the issue


Form Submitted on initialization when i create form with formdata

i am try to create form to edit my data.
i am created and passed formdata in form.
but on initialization of form, form submitted automatically..
what can i do to stop that ??
i want submit form when form data is changed by user...

Hard to tell without any code to look at. Please provide an example as well as the version you're using and reproduction steps.

const schema = {
title: "",
type: "object",
required: ["firstname"],
properties: {
firstname: {type: "string", title: "First Name"},
lastname: {type: "string", title: "Last Name"},
address: {type: "string", title: "Address"},
landmark: {type: "string", title: "Land Mark"},
direction: {type: "string", title: "Direction"},
city: {type: "number", title: "City"},
area: {type: "number", title: "Area"},
pincode: {type: "number", title: "Pincode"},
addresstype: {type: "number", title: "Address Type",
enum: [0,1, 2],
enumNames: ["Home", "Office", "Other"]
},
company: {type: "string", title: "Company/other"},
defaultaddress: {type: "boolean", title: "Default Address"},
}
};
var formData = {
firstname:address.firstname,
lastname: address.lastname,
address: address.address_1,
direction: address.direction,
city:address.city_id,
area:address.area_id,
pincode:address.pincode_id,
addresstype:address.type,
company:address.company,
};
const schema = {
title: "",
type: "object",
required: ["firstname"],
properties: {
firstname: {type: "string", title: "First Name"},
lastname: {type: "string", title: "Last Name"},
address: {type: "string", title: "Address"},
landmark: {type: "string", title: "Land Mark"},
direction: {type: "string", title: "Direction"},
city: {type: "number", title: "City"},
area: {type: "number", title: "Area"},
pincode: {type: "number", title: "Pincode"},
addresstype: {type: "number", title: "Address Type",
enum: [0,1, 2],
enumNames: ["Home", "Office", "Other"]
},
company: {type: "string", title: "Company/other"},
defaultaddress: {type: "boolean", title: "Default Address"},
}
};
handleSubmit(data) {
//console.log(this.props);
console.log('Submission received!', data);
}
this.handleSubmit(formData)}
            />

I'm sorry, can you please write a few sentences describing what's happening precisely, what's expected, what are the steps to reproduce? Please, please, please report this issue as you'd like it being reported to you.

i create onSubmit event on form named  handleSubmit() and passed formdata...
at initialization of form i fetch data from state and passed to formdata schema
but form automatically called handleSubmit() with blank data on loading form...
i want that when user clicked on submit..

please view these image
(https://cloud.githubusercontent.com/assets/6310631/15799443/5d2c0f12-2a7a-11e6-95d4-caa0d1b7d769.JPG)

I still don't get it. Feel free to reopen with a sample minimal reproducible test case.


Torquebox::Logger is unable to log a FixNum

While working with the Google BigQuery gem, I encountered an odd failure:
no method 'debug' for arguments (org.jruby.RubyFixnum) on Java::ChQosLogbackClassic::Logger available overloads: (java.lang.String,java.lang.Object[]) (org.slf4j.Marker,java.lang.String,java.lang.Object[])

I isolated it to this line in Google's general purpose API client, which attempts to log the status code of an HTTP response. Torquebox::Logger#add assumes that it will always be passed arguments that can be passed directly down to the Java method, but as this example demonstrates, that is not a good assumption for the logger to make.
#259 contains a fix for this issue.

Fix has been merged to master. I consider this issue resolved.


[Enum Request] Table 7355 Report Selection Warehouse - Usage Field

Can we please make the Usage field on Table 7355 Report Selection Warehouse an enum so it is possible to specify custom warehouse documents and to make this consistent with the other report selections.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Creating a sosreport streamer script

This should allow/enable sosreports to be run and pulled off of a node directly.

Why aren't we just modifying the existing ceesos script? I do not think creating a new script (something extra to maintain separately) is what we want.
The ceesos script should accept a command-line switch that streams its output rather then attaching it to a case. And then, we should protect against output to stdout/stderr and perhaps capture any unexpected errors in a log file. For example:
#/bin/bash
#

_case_id="$1"
if [ -z "$_case_id" ]; then
    _case_id="$(date -u +'%Y%m%dT%H%M%SZ' 2>/dev/null)"
fi
_tmp_dir="$(mktemp -d -p /var/tmp ohdiag-collection-"${_case_id}"-XXXX)"
_log_file="${_tmp_dir}/sosreport-${_case_id}.log"

trap "{ [ -n "${_tmp_dir}" ] && [ -e "${_tmp_dir}" ] && rm -rf "${_tmp_dir}">/dev/null 2>&1; }" EXIT

if [ -n "${_tmp_dir}" ] && [ -e "${_tmp_dir}" ]; then
    {
        echo "sosreport generation executing for case_id=${_case_id} on $(date)..."
        sosreport --case-id="${_case_id}" --log-size=100 --batch --quiet --no-report --tmp-dir="${_tmp_dir}"
        result=$?
        if [ $result -eq 0 ]; then
            echo "sosreport was successful"
        else
            echo "sosreport report failed with exit status ${result}"
        fi
    } >>"${_log_file}" 2>&1
    (cd "${_tmp_dir}" && tar cf - .) | cat
fi

We would of course want to modify the (cd "${_tmp_dir}"...) | cat line to check the switch to see if it should stream to stdout or attach to a case.

@loleary can you file a PR for your suggestions against https://github.com/openshift/openshift-tools/blob/prod/scripts/devaccess/helper_scripts/ceesos I want to make sure that we start the discussion about enabling this access for CEE sooner rather than later, having the PR is the first step in that process. Once we have that PR we can close this one.

@loleary I am closing this as I have taken your suggestion and provided an update to the current script.


AttributeError: 'TreeNode' object has no attribute 'to_newick'

I need the newick tree to not contain the distances, and I should be able to do that with the to_newick(with_distances = False, semicolon=True, escape_name=True).
But I get this error:
AttributeError: 'TreeNode' object has no attribute 'to_newick'
Here is the code:
ids = list('abcde')

#reconstruct phylogeny tree using Neigbour Joining algorithm
dm = DistanceMatrix(distMatrix, ids)
tree = nj(dm)

print(tree.to_newick(with_distances = False, semicolon=True, escape_name=True))

Hi @YanaHrytsenko, you may be looking at out-dated documentation -- the to_newick was deprecated in 0.4.0. It doesn't look like with_distances is supported by write. However, the following should work for you:
In [21]: example_tree = skbio.TreeNode.read(["(a:0.1,b:0.2)c;"])

In [22]: str(example_tree)
Out[22]: '(a:0.1,b:0.2)c;\n'

In [23]: no_distances = example_tree.copy()

In [24]: for node in no_distances.traverse():
    ...:     node.length = None
    ...:

In [25]: str(no_distances)
Out[25]: '(a,b)c;\n'

It is also possible to use .write. The latest Newick IO documentation can be found here.


fix: sqlalchemy dto for models non Column fields

Examples of such fields are ColumnClause and Label, these are generated when using sqlalchemy.func
Pull Request Checklist

[X] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
[ ] Pre-Commit Checks were ran and passed
[X] Tests were ran and passed

Description

Fix SQLAlchemy dto generation for litestar when using models that have fields that are not instances of Column. Such fields arise from using expressions such as func.

Close Issue(s)

LGTM.
I think 3.8 doesn't like the optional clause inside of the Mapped type though.


Error using variable in subqueries

Description
When using variables in subquery the replace is missplaced.
Query:
@set myvar = '123456';
delete from mytable where fk = (select id from othertable where var = :myvar );

Throws error:
SQL Error [42601]: ERROR: syntax error at or near ";"
  Position: 137

Error position: line: 6 pos: 136

With final/replaced query:
delete from mytable where fk = (select id from othertable where var = '123456'; )

DBeaver Version
Community Version <IP_ADDRESS>406091028
Operating System
macOS Sonoma 14.5
Database and driver

Database PostgreSQL

Steps to reproduce
See description
Additional context
No response

Thank you for bug report.

Actually, it's not a bug. The value for variable is everything between = and the new line. So, you just don't need a ; here.


replace word master with main

Signed-off-by: xuezhaojun<EMAIL_ADDRESS>

/assign @qiujian16
/assign @yue9944882


Close button for menu

Instead of having a separate button for close when we click on menu,
when we hover back to the main content, automatically the menu drop down should go back or get closed.

I feel like this would involve event listeners on the cursor. Or is there an elegant way to do this?

Yes, even I think is better to go with cursor event listener itself.

Or just a click in the main content outside the menu should close the menu dropdown.


Some issue with IR functions

The Stembit_IR blocks donot work and the whole blocks disappears in online as well as offline editors.

Hi muddlehead22,
Please clear cookies of your browser then try again.


Conan 2.0 requirements effect in package_id

Conan 2.0 proposes a new package_id that takes into account the different scenarios that can happen when building and linking C and C++ native binary artifacts like executables, static libraries, shared libraries, etc.
This will be done differentiating 2 major scenarios:

"embed" cases, when the dependency artifact will be embedded in the consumer artifact, like when an executable links a static library. This case will default to use a full_mode policy (old recipe_revision_mode), which guarantees that every change in the dependency requires a re-build in the consumer.
"non embed" cases, where the dependency artifact is in general not embedded/inlined in the consumer artifact, like when a static library depends on another static library or a shared library depends on another shared library. This case will default to use a minor_mode policy, which fully allows the developer to define what needs to be done (not bumping the version or bumping the patch, means no need to rebuild the consumers, bumping the minor means consumers should be rebuilt and bumping the major means that there are breaking changes requiring the consumers to change their code to adapt).

Upvote 👍  or downvote 👎  to show acceptance or not to the proposal (other reactions will be ignored)

Please, use 👀  to acknowledge you've read it, but it doesn't affect your workflow

Comment and reviews to suggest changes to all (or part) of the proposal.

As long as both cases are default configurable, I'm 👍

I'm strongly in favor of this proposal, but I also think that the chosen "use-case" should also affect the visibility of the public headers, as described in this old issue.
Notably, let's have 3 static library packages Aaa, Bbb and Ccc with dependency graph Ccc -> Bbb -> Aaa.
Let's also say that public headers of Bbb include and use public headers of Aaa. This means that if some package Ddd, that depends on Ccc, overrides the version of Aaa to a new, breaking, version, Conan needs to rebuild both Bbb and Ccc, as implementation files (.cpp files) of Ccc may have inlined code from public headers of Aaa, even though they never directly included them - the include was transitive via public headers of Bbb.
My suggestion in the mentioned issue was to also let Conan generators be aware of that, and prevent Ccc from even seeing headers from Aaa unless Bbb declares that it uses Aaa as in "embed use-case". Even though the "embedded use-case" is meant mostly for applications and dynamic/shared libraries, I would argue that it should also be used for head-only and static libraries whose public headers are used/"embedded" by the public headers of the consuming library.
So, by using syntax from the proposal, in the example above, the recipe of Bbb would state something like this:

class BBBConan(Conanfile):

    def requirements(self):
        self.requires('Aaa/1.0.0@user/channel', package_id_mode='minor_mode')

WIthout stating that, Ccc (the user of Bbb) would not get the header search path for Aaa, thus making a compilation for Ccc fail if Bbb mistakenly uses public headers of Aaa in its public headers.

is / will there be a default mode if you set / select nothing ?
(I hope the answer is yes, full_mode is the default :-)

@DoDoENT

WIthout stating that, Ccc (the user of Bbb) would not get the header search path for Aaa, thus making a compilation for Ccc fail if Bbb mistakenly uses public headers of Aaa in its public headers.

I am not sure if I follow. This was already approved in https://github.com/conan-io/tribe/blob/main/design/026-requirements_traits.md, and it has been implemented. Now in Conan 2.0 (released alpha), ccc package does not have visibility over aaa headers, unless bbb explicitly defines it with the appropriate trait self.requires("aaa/1.0", transitive_headers=True).

I am not sure if I follow. This was already approved in https://github.com/conan-io/tribe/blob/main/design/026-requirements_traits.md, and it has been implemented. Now in Conan 2.0 (released alpha), ccc package does not have visibility over aaa headers, unless bbb explicitly defines it with the appropriate trait self.requires("aaa/1.0", transitive_headers=True).

@memsharded , I'm aware of that. I'm just saying that that proposal should come hand-in-hand with this proposal here.
Notably, if you write self.requires('aaa/1.0', transitive_headers=True), it's package_id_mode should default to minor_mode (or whatever is chosen for the "embedded use-case"). Of course, it would still be possible to write self.requires('aaa/1.0', transitive_headers=True, package_id_mode='semver_mode') when you know what you are doing, but at least it would not be the default.
My guess is that, by default, when you opt-in for transitive_headers, you automatically get into the "embed use-case" scenario.
I could be wrong, though,

@DoDoENT

My guess is that, by default, when you opt-in for transitive_headers, you automatically get into the "embed use-case" scenario.

Not really. If you have both bbb and aaa that are static libraries and bbb requires aaa with transitive_headers=True, that doesn't imply that bbb will be inlining/embedded the aaa artifacts, in fact it could mean the opposite, that it is less of an implementation detail of bbb and be just transitive over the public headers, but not used in the .cpp at all.
And for the consumer ccc of bbb, that depends on the type of consumer. If it is an application, it will certainly use the embed case both over bbb and aaa.
Also, the most important, the non-embed doesn't imply that nothing will be ever embedded. It is implying that it is not always embedding the changes. But the user has the control to specify it, bumping the patch (or not bumping), means that only .cpp files were modified, it doesn't matter that headers would be embedded in consumers. If a change is done in a public header, then users can do a bump to the minor version to indicate it, and that will trigger the signal that something that might be embedded by the consumers has changed, and as such, it is necessary to rebuild consumers.

In general, I fully support this proposal. It gives better control over package ID computation of dependencies.
However, it still doesn't address a usecase which I find more important (or did I overread something?):
Why can't a package define it's own mode?
At the moment there is a global definition, and consumers can overwrite the global defaults. This proposal keeps it the same, just the granularity is more fine grained.
Even with this approach, I will still have to modify each and every package which uses library X, if package X might make changes that requires a full_version_mode.
Why can't a package require  "minimum" compatibility, for itself?
E.g. Each library knows best what versioning scheme it uses, e.g. semver ,...
So each package should say: I don't follow any versioning, please always use full version mode. Or: I use semver. Mayor mode is fine (though, can Conan model the case only to use newer artifacts on runtime).
The integrator can then globally specify if they use the packages default, or something "stricter".
Then, if package could specify it's minimum requirement type, there is not so much of a need for their consumers to specify it at all.

@KerstinKeller
We already have a PR with a preliminary PoC for what you are commenting: https://github.com/conan-io/conan/pull/11441. It seems doable, but we think it is important to first outline the basic behaviors, defining in which situations we are in embed, and not-embed mode, etc. Because that implies in https://github.com/conan-io/conan/pull/11441, that there should be probably 2 or more definitions in the recipes for the consumers, at least the "embed" and the "not-embed" one. Because it doesn't matter if a package doesn't follow semver, the case when it is being compiled as a static library and consumed by another static library might be totally different to the one that such static library is being compiled by an application. If you want the two cases to be the same, it is easy, just assign both the same policy, but in general it seems that defining the policies for the different scenarios should be part of this feature.

Hi @mmatrosov

The conans global config has always been frustrating to me. What if I am a part of several "teams or companies"? My team from my job, other teams from my job, several open source projects, my own setup, educational setups?

The idea of any global state influencing build result smells a lot. Is it totally necessary? Can we get rid of it?

How we can get rid of it, this is the reality we see, and you just described it. For example companies will use custom settings, and they will use custom settings in their recipes to affect their builds. They will have very different profiles, and most likely very different hooks. Surely completely different remote repositories. The packages they build for those recipes with those profiles will not work without that. And as you have suggested, same happens for other setups. It is not just the configuration, everything for a setup is connected.
The recommended way to deal with that is to use a different Conan home for each different setup. That home will contain the settings, the profiles, the remotes, the hooks, for that specific setup, and of course the configuration for that specific setup.

The conans global config has always been frustrating to me. What if I am a part of several "teams or companies"? My team from my job, other teams from my job, several open source projects, my own setup, educational setups?
The idea of any global state influencing build result smells a lot. Is it totally necessary? Can we get rid of it?

Sorry for being OT, but it might be helpful in this context
I simply use different CONAN_USER_HOME for different team/project setups
https://docs.conan.io/en/latest/reference/env_vars.html?highlight=conan_user_home#conan-user-home
so there is no global state for me, since I never use ~/.conan
often automatically set via direnv , so by just changing into a directory I have the team/project environment, and only the download cache, which is also set that way, is shared

Thanks for letting me know about conan home. I completely forgot about this feature. I have lived with ~/.conan my whole life and did not have much problems with it. But I have a feeling that situation might change with core.package_id:default_* modes.
Let us consider two global settings mentioned above: settings and remotes. We indeed have custom settings.yaml file, but we append to it. We do not remove stuff. Hence, every recipe from CCI behaves the save way as in CCI CI. We also indeed have our own remotes. But again, we do not remove conan-center, we simply add our artifactory host first. Furthermore, if you assume all remotes contain properly built binaries, it does not matter which remote to choose for the build from the result's perspective. Again, every recipe from CCI behaves the save way as in CCI CI.
But what about core.package_id:default_* modes? It seems like if you build the same dependency graph on two hosts with different default modes, then update some dependencies and built again, you can end up in completely different binaries. Is this correct or am I missing somethig?

Late to the party on this, but an observation.
As much as I appreciate the correctness in identifying downstream packages as out-of-date when making a change to 'my package', to me this suggests that making small changes in common packages could cause a cascade of many package rebuilds in CI systems?
Of course, configuring this to suit your level of 'correctness' and 'comfort' is probably the solution to this.
I'm just wondering if any testing in CI on this proposal has revealed a significant cost overhead in the most correct mode? If I make a minor change, how much effort does it take to get an entire dependency tree back into sync by CI systems?
For example, the library we often speculate about here is zlib, and what needs changing if we need to patch it, as it's often at the very bottom of the pile of dependencies. Certainly, I see all of the downstream packages that link static-zlib into a shared library would be marked out-of-date, and then where that cascades from there.
Is this a reasonable concern?

The feature https://github.com/conan-io/conan/pull/11441, that allows a dependency to define the package_id_embed_mode, package_id_non_embed_mode and package_id_unknown_mode for their dependencies has been merged and it will be available in Conan 2.0-beta.2
This definition will have priority over conf definition of default_package_id_mode, that as the name implies, it is only a "default", and only effective when no one else is defining that value.

Regarding the definition of CONAN_USER_HOME (CONAN_HOME in 2.0), a new feature has been merged in Conan 2.0, the definition of a .conanrc file that defines such a variable, to be able to define the location of the Conan home, differently and auomatically for different projects.

Regarding the definition of CONAN_USER_HOME (CONAN_HOME in 2.0), a new feature has been merged in Conan 2.0, the definition of a .conanrc file that defines such a variable, to be able to define the location of the Conan home, differently and auomatically for different projects.

awesome!

For example, the library we often speculate about here is zlib, and what needs changing if we need to patch it, as it's often at the very bottom of the pile of dependencies. Certainly, I see all of the downstream packages that link static-zlib into a shared library would be marked out-of-date, and then where that cascades from there.

@foundry-markf
In our experience, many companies and teams have been opting-in for the most strict modes, including package_revision_mode, requiring tons of re-builds (sometimes probably unnecessary). So apparently, there is a larger concern about correctness than about resources or speed.
The approach in this proposal is accordingly more on the correctness side, but not extremely, leaving space for user control about what/when needs to be rebuilt using versioning schemas. It is a matter of probabilities, if a shared library is linking a static library, the likelihood of embedding it is very high, recipe_revision_mode will be used, meaning that even a cosmetic change to a recipe like a comment or docstring will trigger the rebuild of the consumer shared libraries. This is up to the user, if they have the discipline and tooling to do the correct version bumps when something in code changes, then it can be relaxed to patch_mode for exampl, but as the proposed default, we chose something that is closer to what we see in practice by users.
For static libraries, we also need to find some balance that works as default for ConanCenter. With now +1300 packages, built for +100 configurations, it is not possible to rebuild everything everytime one library recipe changes one comment. So we went for something stricter than the current default, and went to minor_mode. This can work quite well in practice for environments like ConanCenter, in which third-party packages are being packages, as the source code of the package actually doesn't change when you create new revisions. If you apply this default for your own libraries, it can be done if the developers have enough discipline to bump the patch/minor versions correctly when necessary, but otherwise you might need to go stricter too.

Closing as outdated, still this was super useful thanks again for all feedback


Require clients to be online when creating new shared symmetric encryption keys

Is your feature request related to a problem? Please describe.
We need to make the lifecycle of shared symmetric encryption keys entirely predictable.
Describe the solution you'd like
Clients should

check if shared_key.bob@alice exists (can be done locally and then on atServer - this is how things currently work I believe, so no change required)
if none exists, and we are online, generate one and store it on atServer (and not locally - that way, the only way that shared_key.bob@alice gets into the local data store is if it was synced from the server)

if not online, raise exception for client app stating that one needs to be online when creating new shared symmetric encryption keys

Additional context
See also https://github.com/atsign-foundation/at_protocol/issues/65 which is another part of what's required to achieve the goal of completely predictable lifecycle of shared symmetric encryption keys

Marking for discussion on an architecture call before moving to implementation


Remove six from the project

Python 2.7 is out, let's start to remove six from the project.
Let's also remove future declarations used to get 2.7 compatible with 3.

It seems like other projects we depend on still will require six. We will just remove six from our logic and not reference six as a direct dependency.


Added rxjs to package.json and updated tsconfig.json with missing files

remove those .idea files

Done. Sorry about that.

RxJS is included as a peerDependency, on purpose - it's expected that it would be installed with Angular2 and peer dependencies avoids a possible version conflict.
Typescript automatically transpiles files referenced, so including them all is unnecessary.
Was there a particular reason you made both of these changes?

Thx. for teaching a newbie - been reading up on peer-dependencies, check! Regarding the typescript files: yep - compilation works fine, I just (or rather webstorm) noted that the list of files was incomplete and thought that to be a mistake.

No worries! Thanks for the PR anyway 👍


Is a transaction finalised when the burrow deploy command finished?

I have a question about transaction finalisation in Burrow. When submitting a transaction to Burrow using the burrow deploy command, is the transaction finalized/committed when the playbook finishes? I need to get the time between submitting a transaction and its finalisation. Or is there any other way to reliably get the transaction confirmation times?
Thanks!

What burrow deploy will do is synchronously broadcast each transaction in your playbook, effectively waiting at each step to finalize. When it has been included in a block, your node should be able to fetch the block header from the store (here) which contains a timestamp from Tendermint. If you have the transaction hash, I might suggest that you utilize the web3 RPC to pull the header (here).


WIP: Remove gogen requirement for feature coverage

@therealmitchconnors: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test lint_istio

gencheck_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test lint_istio

gencheck_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test gencheck_istio

integ-local-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test lint_istio

gencheck_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test gencheck_istio

integ-local-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-local-tests_istio

integ-multicluster-k8s-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test lint_istio

gencheck_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test gencheck_istio

integ-local-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-local-tests_istio

integ-multicluster-k8s-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-local-tests_istio

integ-multicluster-k8s-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-pilot-k8s-tests_istio

lint_istio
f837ea695ab8acf9ea69e44610003387f04b8768
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
425f14d0a7d5c9e592f1e59b9a47ed3a5127feb6
link
/test integ-multicluster-k8s-tests_istio

lint_istio
f837ea695ab8acf9ea69e44610003387f04b8768
link
/test lint_istio

integ-pilot-k8s-tests_istio
f837ea695ab8acf9ea69e44610003387f04b8768
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
f837ea695ab8acf9ea69e44610003387f04b8768
link
/test integ-pilot-k8s-tests_istio

lint_istio
ef2318b2e87db1cd4e3706d36e61b5110c415740
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
ef2318b2e87db1cd4e3706d36e61b5110c415740
link
/test lint_istio

integ-pilot-k8s-tests_istio
ef2318b2e87db1cd4e3706d36e61b5110c415740
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
ef2318b2e87db1cd4e3706d36e61b5110c415740
link
/test integ-pilot-k8s-tests_istio

lint_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
ef2318b2e87db1cd4e3706d36e61b5110c415740
link
/test integ-pilot-k8s-tests_istio

lint_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test lint_istio

integ-local-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test lint_istio

integ-local-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-local-tests_istio

integ-pilot-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test lint_istio

integ-local-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-local-tests_istio

integ-pilot-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test lint_istio

integ-local-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-local-tests_istio

integ-pilot-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test lint_istio

integ-local-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-local-tests_istio

integ-pilot-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-galley-k8s-tests_istio

integ-operator-controller-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test lint_istio

integ-local-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-local-tests_istio

integ-pilot-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-galley-k8s-tests_istio

integ-operator-controller-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-local-tests_istio

integ-pilot-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-galley-k8s-tests_istio

integ-operator-controller-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-distroless-k8s-tests_istio

lint_istio
7922ef94681c6598e280d8a1015b843566a539bb
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-telemetry-k8s-tests_istio

lint_istio
7922ef94681c6598e280d8a1015b843566a539bb
link
/test lint_istio

integ-pilot-k8s-tests_istio
7922ef94681c6598e280d8a1015b843566a539bb
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
7922ef94681c6598e280d8a1015b843566a539bb
link
/test integ-pilot-k8s-tests_istio

integ-local-tests_istio
c30a9a4702f83cf63a5d35b0fe60775cc57275a2
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
887a3f0d09f35622937524fb22ee93a52a505a8a
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
7922ef94681c6598e280d8a1015b843566a539bb
link
/test integ-pilot-k8s-tests_istio

integ-local-tests_istio
c30a9a4702f83cf63a5d35b0fe60775cc57275a2
link
/test integ-local-tests_istio

integ-multicluster-k8s-tests_istio
c30a9a4702f83cf63a5d35b0fe60775cc57275a2
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

probably a bad merge :-( +33k lines....

@therealmitchconnors: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
d06a2855c8a1693b0e3ec7bdcd43c126ee004ac0
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@therealmitchconnors: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
725bd45222d078aa9041a73bfcd407525e6e2dbc
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Configured edge router to accept connection from telemetry bench and …

In order to more realisticly test SAF, the setup needed to more closely reflect a real life setup in which data would come into an edge router on the client side before being routed over to the amq bus in SAF: tool -> qdr -> qdr -> sg.
I have added in a new router to satisfy this condition. The performance test automatically deploys and tracks the new router and points telemetry bench to send metrics through it.

 Make more realistic test tool setup (tool -> qdr -> qdr -> sg)


use prism babel loader

What does this do @zarsky-broad ?

Just changes how the prism modules we use are loaded, so that we're not relying on imports that have side effects. The way we're changing it to here is the way that's now recommended.


Feature request: Add ability to set Desired capabilities via Configuration

It will be handy to have a ability to add DesiredCapabilities via Configuration.
For now we can do this by:
public static class CustomWebDriverProvider implements WebDriverProvider {
    @Override
    public WebDriver createDriver(DesiredCapabilities capabilities) {
       FirefoxProfile profile = new FirefoxProfile(new File("/home/test/MozzillaProf/"));
       profile.setAssumeUntrustedCertificateIssuer(false);
       profile.addAdditionalPreference("general.useragent.override", "some UA string");

       capabilities.setCapability(FirefoxDriver.PROFILE, profile);
       return new FirefoxDriver(capabilities);
    }
  }

But it's to verbose, it's will be better to use:
FirefoxProfile profile = new FirefoxProfile(new File("/home/test/MozzillaProf/"));
profile.setAssumeUntrustedCertificateIssuer(false);
profile.addAdditionalPreference("general.useragent.override", "some UA string");
capabilities.setCapability(FirefoxDriver.PROFILE, profile);

Configuration.browserCapabilities = capabilities;

I guess we can close the issue: Configuration.browserCapabilities was added in Jan 2018 by https://github.com/selenide/selenide/commit/559c6aa8d01b39ff0b2eeecf31c1ff9e306f7e83


Update to 0.7

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


[themes] New minimal token color theme options

I suggest either

to create a new default minimal color themes based on current default color themes, such as Light+, Dark+, etc., but with no token coloring, or
to provide an option to completely override tokenColors by providing tokenColors configuration option (instead of tokenColorCustomizations.

I know, that we can choose from many color theme extensions, but I think that users should have an option to choose a minimal token coloring without the need to search for an extension which would do it for them.
Currently, users can achieve the same result also by providing a long list of scopes inside tokenColorCustomizations configuration to apply default text color to, but it is not very convenient and the list of scopes varies based on a selected color theme.
Thank you for your consideration.
Version: 1.85.2 (Universal)
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:32.531Z
Electron: 25.9.7
ElectronBuildId: 26354273
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.3.0

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

It looks to me that this issue will be closed, because there has been no interest in implementing this so far.
For reference, here is an example of a minimal color scheme I was looking for:
https://marketplace.visualstudio.com/items?itemName=fansek.vscode-exupery
https://github.com/fansek/vscode-exupery

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add links with fixed oc-version to repo-page

If I choose to install owncloud via repo sources, owncloud.org gives me only the link to the newest OC version: http://download.opensuse.org/repositories/isv:/ownCloud:/community/Debian_7.0/
Some people want to install a certain OC version and should decide on their own when to upgrade to a new version (stable enough, all their 3rd party apps are compatible). For these people, it would be extremely helpful if you provide a link to a certain OC-version, like OC 7.0.x:
http://download.opensuse.org/repositories/isv:/ownCloud:/community:/7.0/Debian_7.0/

A lot of people are surprised that this is possible! After the problem with the latest upgrades, I think we should provide information about this option or even make it default: For upgrades it's slightly more complicated but people will be more aware of the fact that they are running an upgrade and should perhaps do backups. Normally the upgrade notice appears in OC, in the linked content, we could put the information on how to change sources and also what is going to change and what has to be considered.
I prefer people asking how to change the sources to upgrade to OC 8 than everyone complaining about a broken setup due to an (unwanted?) upgrade.
Also related to: https://github.com/owncloud/owncloud.org/issues/330

Seems that got fixed by https://github.com/owncloud/owncloud.org/pull/473

Well, it's now visible in the change log. @tflidd do you have any concrete suggestions on where else to note this? If not, let's close this as done.

I think we should make older versions easily accessible, for multiple reasons: easy rollbacks, curiosity, testing... I shall write something up for the admin manual.

Great, links to old versions via repo-manager can be found now.
My concern is, the current docs advices the bleeding-edge version of owncloud and don't even give any information of how to follow a more conservative upgrade strategy. Thinking back to the OC 8 upgrade, a lot of people just hit the regular apt-get update/upgrade and killed their setup.
A second point is that especially users of the community version are more likely to use third party apps. Only a few of them are ready when a new upgrade is pushed. So, probably 80% have no interest of upgrading the very first week.
Personally, I would prefer to use fixed sources for one major OC version. When there is a new version, I would show an update message and link it to the manual on how to change the package sources.

@tflidd
@carlaschroder already promised to take care of the documentation (isn't she awesome?) and the updater app in 8.1 will support choosing a 'stable stream' on top of that. The issue with apps is also being addressed although there will probably always be a bit of a delay. I'm not sure what we can really do to improve that situation other than making our API more stable and reliable, and we are doing that...
I'm closing this as I think we've done the best we could :dash:

Ok for me. Really good to see all the improvements here.


Add support for null vs missing input value

This is an attempt to solve https://github.com/graph-gophers/graphql-go/issues/210 by adding support for nullable non-pointer types. This is inspired by the Null types in the sql package.
The idea is to have custom types where we can call UnmarshalGraphQL with a nil input, thus allowing to differentiate between no value (method not called) and a null value (method called with nil).
The main change is to allow a non-pointer type to represent a nullable value if it implements the following interface:
type NullUnmarshaller interface {
	Unmarshaler
	Nullable()
}

Also added nullable types for existing scalars: NullString, NullInt, NullFloat, NullBool and NullTime.
Example
input MyInput {
    a: String
}

type Query {
    myQuery(input: MyInput!): String!
}

type MyInput struct {
	A graphql.NullString
}

type resolver struct{}

func (r *resolver) MyQuery(args struct {
	Input MyInput
}) string {
	if args.Input.A.Valid {
		if args.Input.A.Value == nil {
			// null value provided
		} else {
			// non-null value provided
		}
	} else {
		// field omitted
	}

	return "hello world"
}

Hi @Ackar
Thank you for your contribution. I'll take a closer look tomorrow.

Thank you


feat(sdk): implement support for gear vr

This is the PR #944 by @CoderDawson updated to the latest VRTK version,
modified to be compliant with the new SDK management and with updated
documentation.
Add SDK_GearVRDefines to handle the scripting symbols for the GearVR.
Refactor and update other GearVR/SDK files.
Update documentation (GearVR_README.md).
Tested with GearVR:

object touching and grabbing (005_Controller_BasicObjectGrabbing)
interaction with Unity UI (034_Controls_InteractingWithUnityUI)
teleport (044_CameraRig_RestrictedTeleportZones)

The examples were tested after changing [CameraRig] and [VRTK] in
order to support GearVR.

There were the following issues with your Pull Request

Commit: b1e28ff8a6c0d6dead1d025a12a074045f0844ba
Your subject line is longer than 72 characters

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com


Docs/attributes update

Screenshots are now taken using playwright in the playwright branch.  Playwright is not at the level of being ready for a PR, but I wanted to have a reproducible way for documentation screenshots being taken going forward.

I haven't been following any strict process with docs.   The following will deploy the docs, which I often just run myself.
mkdocs gh-deploy


Is it possible to implement the directional navigation in dwm?

How are you doing the directional navigation i.e;
M-J: focus Down
M-k: focus Up
M-l: focus right
M-h: focus left
and Shift to swap clients?

https://github.com/jzbor/patches

i found this repo with the patch. But last commit was 2 years ago? is this the one used in moonwm and will it be update in the future?

Hi, the main function in moonwm handling this is nextdir. It is in turn used by focusdir for switching the focused window and movedir for moving/swapping windows. It's been some time since I wrote this code and honestly there is a lot of room for improvement. It does not work fine with all layouts especially with stuff like cfacts.
I am pretty sure I started of with this patch from bakkeby. Maybe that helps you a little. My fork was only for some pull requests on some other patches.
Reworking this has been on my todo list for a long time now, but I simply haven't had a good idea that works well with all layouts including floating. If you wish to try my version you should be fine with adding the functions mentioned above (focusdir, movedir and nextdir), but there is no guarantee, since MoonWM has had a lot of changes since dwm and the directional functions are pretty much tailored towards it's standard layouts.

Thanks a lot!

I actually had this fork i did a while back: https://github.com/Ahanaf-Ether/dwm-directionalfocus
problem is though it isn't aware of recent windows!


Update _NIOConcurrency for Swift 5.5 latest changes

Remove availability checks and $AsyncAwait from _NIOConcurrency
Motivation:
The latest changes in Swift 5.5 mean you no longer need the availability checks for concurrency.
Modifications:
Removes the availability checks and compiler directives that are no longer required
Result:
Easier to use _NIOConcurrency

@swift-nio-bot add to allowlist


Check planetary compute and see if we can add it as an input source

https://planetarycomputer.microsoft.com/catalog Quite a lot of data in here


All-in-one search: Removed section about preview feature, added info on new text support, and made minor improvements for clarity.

Some of this content is outdated. Removed section about preview feature, added info on new text support, and made minor improvements for clarity.

@ghogen

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

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


Add logging for admin groups manipulation within dashboard config instance

Resolves: #463
Description
Adds logging for the mentioned cases of changing the odh-dashboard-config CRD instance.
How Has This Been Tested?
Tested locally through modifying the odh-dashboard-config CRD instance on the cluster and checking responses from config GET calls on the backend.
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

Closing this PR, we might wanna explore other alternatives.


Repository license should be one of the GNU family of licenses

Hi Trevor,
If we want the FSF to pick this up and use it,  the license should probably be changed to GPL-3.0-or-later,  or something from their family.
Is this possible?
Thanks, Kate

On Fri, Apr 20, 2018 at 11:43:20PM -0700, Kate Stewart wrote:

If we want the FSF to pick this up and use it, the license should
probably be changed to GPL-3.0-or-later, or something from their
family.

There's not much going on in pull.py, so I don't see a big downside to
allowing proprietary forks.  Who would bother, and even if they did,
would the FSF care?  The licensing for the generated data in the
gh-pages branch, if its copyrightable at all, probably inherits the
FSF's CC-BY-ND-4.0 from 1, possibly with some MIT mixed in due to
pull.py (e.g. for the schema/ JSON-LD).  Hopefully the FSF either
agrees that it's not copyrightable (I don't copy any of their opinion
text) or doesn't mind too much about this particular derivative work.
And, even if we don't officially relicense pull.py, is that script
really how the FSF would choose to maintain it's API?  I'd expect them
to turn our:
HTML -(pull.py)→ JSON
scraping around and use:
JSON -(generator)→ HTML
If there's anything in the JSON schema itself that they consider
copyrightable, that would probably be the only thing that would
survive a transition to FSF ownership.
That said, I'm happy to relicence my contributions here under whatever
license if the FSF has a preference.  I expect @goneall (who's
contributed ef88572 via #3) will feel the same way.  @goneall?

Agree with all of the above - I am quite flexible on the licensing.
The data is being used by the LicenseListPublisher (licensed under the Apache 2.0 license), but the code itself is not referenced or included.