1110 codeupdate- inbound and Concurrent update rebase

This PR contains the following commits:

Concurrent code update support.
Bootside mapping
Support for boot types attributes
All the defect fixes for inband and out of band updates in pldm.

commit list:
66f7ac79 (HEAD -> 1110) Trigger Assemblelids method and handle response (#402)
d0397ba6 PLDM:Wait on the Software Updater (#296)
a5ee378a PLDM: Make boot type as Reipl during MPIPL (#270)
fa3d99a7 PLDM: Reset image activation after sending end update event (#259)
795b9cfe PLDM: Reset image activation match (#241)
9622648c PLDM: Minimise sending BIOS attr change event (#193)
66f7ac79 (HEAD -> 1110) Trigger Assemblelids method and handle response (#402)
d0397ba6 PLDM:Wait on the Software Updater (#296)
a5ee378a PLDM: Make boot type as Reipl during MPIPL (#270)
fa3d99a7 PLDM: Reset image activation after sending end update event (#259)
795b9cfe PLDM: Reset image activation match (#241)
9622648c PLDM: Minimise sending BIOS attr change event (#193)
56cd8dd1 oem: ibm: Set next boot side attribute During a rename, set the next boot side to Perm (same as current) so that in case of a failed update, PHYP knows to boot from the Perm side. The next boot side would be set to Temp on a successful update (via the Priority callback function).
b6fae78a oem: ibm: Side information enhancements (#132)
aea0bc0a PLDM: Remove old boot side setting (#190)
70c1d40b PLDM: Fix code update Rename
abfbe210 PLDM: APR changes in inband CU path (#178)
dca892f7 Pldm RR crash fix (#92)
cb246f9f pldm: Support bios attributes for boot types
3d8f9d9c PLDM: Setting the slot power state to Off (#62)
cd50161d PLDM: Support for LID type running in constructLidpath (#161)
c674f9ca PLDM: Add file type running (#156)
640271bc PLDM: Fix ContainerID for rename sensor (#130)
beec0379 PLDM: Next Boot Support (#123)
1e4220e4 PLDM: Include additional debug traces (#118)
04533600 PLDM bootside bump failure fix (#103)
bd85888e PLDM Fix for bootside attribute defect (#99)
44982b70 oem-ibm: Eliminate the Boot side Effecters and sensors
3e4c6d28 oem-ibm: State effecter for rename operation
bba274a4 oem-ibm: Maintain bootside Mapping and Set bios attribute
c1b78781 oem-ibm: support concurrent FW update

looking at the list , on a first glance i feel https://github.com/ibm-openbmc/pldm/commit/3d8f9d9c9b696b4eacfe78d77d32eeafba9b38ae PLDM: Setting the slot power state to Off (https://github.com/ibm-openbmc/pldm/pull/62)  is not required, its already merged upstream and downstream.


#8920: add strided slice support

single core implementation for now
positive strides now supported with an alternate kernel
TODO: optimize case where there's no slice/stride on W
TODO: add multicore support
TODO: add negative stride support

Ticket
Link to Github Issue
Problem description
Provide context for the problem.
What's changed
Describe the approach used to solve the problem.
Summarize the changes made and its impact.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

could it be done by modifying the existing slice? We already have many different cases ( sharded, rm, tile). If adding more variations the code might be too cumbersome. If shouldn't be too hard to stride with the exsiting code? in the reader kernel, we already have a start/end offset, just by skipping rows in the reader should be okay

Turning this into an action item: #12413


Create greetings.yml

This enables the actions/first-interaction github action for the natlas/natlas repository.
Information about this action
Addressing the opener

Based on your earlier discovery does this PR still make sense?

I don't think so, unfortunately. Maybe a github app like Boring Cyborg would be better. We can mark this one as invalid and I'll explore other options since Github actions seem more limited than I'd hoped.


A

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior. A minimal reproducing set of python commands is ideal.
If the problem involves a specific molecule or file, please upload that as well.
Output
The full error message (may be large, that's fine. Better to paste too much than too little.)
Computing environment (please complete the following information):

Operating system
Output of running conda list

Additional context
Add any other context about the problem here.

Looks like a typo duplicate of #637


removed update & curseforge comments

What happened to the update?
there was and update but now thire is not
also why are curesforge comments disabled

I pulled the update to figure out what is going on with some users crashing due to it
And comments has been off for a while as I do not wish to deal with them


Delete duplicate logrotate config for mail.log

Fixes https://github.com/bokysan/docker-postfix/issues/212. This appears to be a common strategy: https://github.com/docker-mailserver/docker-mailserver/blob/c29fe3ff0bc888016720536228878b3f19131056/Dockerfile#L259.
Before
root@postfix-mail-0:/tmp# /etc/cron.daily/logrotate
error: rsyslog:1 duplicate log entry for /var/log/mail.log
error: found error in file rsyslog, skipping
root@postfix-mail-0:/tmp# echo $?
1
root@postfix-mail-0:/tmp# cat /etc/logrotate.d/logrotate.conf
/var/log/mail.log {
    copytruncate
    rotate 1
    monthly
    minsize 1M
    compress
    missingok
    notifempty
    dateext
    olddir /var/log/
    maxage 90
}

After
root@postfix-mail-0:/tmp# if egrep -q '^/var/log/mail.log' /etc/logrotate.d/logrotate.conf; then
        echo "Removing /var/log/mail.log from /etc/logrotate.d/rsyslog"
        sed -i -E '/^\/var\/log\/mail.log/d' /etc/logrotate.d/rsyslog
fi
Removing /var/log/mail.log from /etc/logrotate.d/rsyslog
root@postfix-mail-0:/tmp# /etc/cron.daily/logrotate
root@postfix-mail-0:/tmp# echo $?
0
root@postfix-mail-0:/tmp# cat /etc/logrotate.d/rsyslog
/var/log/syslog
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/cron.log
{
        rotate 4
        weekly
        missingok
        notifempty
        compress
        delaycompress
        sharedscripts
        postrotate
                /usr/lib/rsyslog/rsyslog-rotate
        endscript
}

Looks good!
All tests pass? I will go over it tonight.
B

@bokysan gentle bump on this

I'll merge this to master and test it out. If it works, I will push out a new version soon.

@bokysan thanks!

@bokysan Any word on a new version?

@bokysan just checking in - could this be released?

In a couple of days. Traveling ATM.

@bokysan bump on this :) would appreciate a new version being cut


Simplify create-svelte

Recapping some discussion in Discord prompted by #934:

our current approach does not scale. the code is already a bit convoluted, #934 makes it more so just by virtue of adding an additional template. if we wanted to add more templates in future, or support (for example) specifying a github repo as a template, things would get out of hand quickly
i'm of the view, and my sense is that at least most of the core team agree, that encouraging CSS preprocessors like SCSS and LESS is undesirable. they're just not really necessary in a world of scoped component styles and CSS custom properties. if people really want to make their apps more complex by throwing preprocessors at them, they are welcome to do so, but npm init svelte is the wrong place to make that happen
therefore the only source code modification that needs to happen is TypeScript
rather than manually writing code that modifies the template, which works in trivial cases but is generally a bit distasteful, we could maintain a TypeScript version of each template and convert it to JavaScript at build time instead (e.g. by running all the .ts files and the <script> of each .svelte file through Sucrase or esbuild)
there's still some modification that needs to happen to package.json, and there's still some complexity around Prettier and ESLint (the Prettier modifier depends on whether you're using the ESLint modifier, which depends on whether you're using TypeScript) but it's stuff that should in theory be common to all projects, and is therefore immune to the aforementioned scaling issue
if we're transforming the template code at build time, we don't really need to include the actual template files in the package, we can just create a JSON file with the contents

If we're moving away from built-in support for Lass/Sass templates, then #972 is also something we can sidestep, as it would be on users to update their ESLint config accordingly.

they're just not really necessary in a world of scoped component styles and CSS custom properties.

They're absolutely vital so long as nesting isn't part of the spec!

In my opinion nested syntax is a good reason to keep built-in support for Less/Sass. Is there a way to remove it from create-svelte but still make it easily available just with <style lang='scss'> ?

they're just not really necessary in a world of scoped component styles and CSS custom properties.

They're absolutely vital so long as nesting isn't part of the spec!

Making element styling dependent on nesting has long been known to be a bad idea even to traditional CSS philosophy:

https://csswizardry.com/2012/05/keep-your-css-selectors-short/
https://cssguidelin.es/#specificity
https://medium.com/@verpixelt/your-nesting-is-harmful-a1ffddaf7e43
https://thesassway.com/avoid-nested-selectors-for-more-modular-css/

And nesting is even less valuable within Svelte components where you can't even nest selectors deeper than what is already in that same file, which I estimate is only about 3-5 levels in most cases.
But even if you disagree, you can still write out your nested selectors explicitly.
A counterpoint is that you might want to style all the various states of a button (hover, active, etc) which isn't the same kind of nesting as previously discussed. But even in that case, writing button:hover, button:active, etc isn't that much more work than button { &:hover { ... } &:active { ... } }.

In my opinion nested syntax is a good reason to keep built-in support for Less/Sass. Is there a way to remove it from create-svelte but still make it easily available simply with <style lang='scss'> ?

Install and set up svelte-preprocess and its needed dependencies yourself.
If it's so necessary, someone in the community's probably going to make a Svelte adder for it anyway.


Rust relay-compiler new persisted query support

Relay's new rust compiler, the next generation for relay now instead of persisting queries to disk as json. It now POST's the query text to a server, and asks it to give back an id.
The idea as confirmed by @kassens is to store this query text, and ID indefinitely in some database or whatever. The compiler, if it has an id wont tell this to the server again. But I feel there will be a force resend of the queries, and maybe a future fallback to json files on disk.
Never the less the implementation is:

At compile-time (relay-compiler), every query for a project that is marked to persist. Will POST to a config driven endpoint.
The POST will contain form-data, of text={query}.
Also through config, you can specifiy extra params to be send, which I dare say is for meta or anything. This can be anything. So I guess HC will just ignore extra fields—or make use of it.
The endpoint must then respond with application/json, and { "id": "<some-id>" } - or an object for errors { "error": "..." }
Relay when then relay this id, in a similar fashion to what it was before—the doc_id param.

Further readings:

https://github.com/facebook/relay/blob/master/compiler/crates/persist-query/src/lib.rs#L39-L73
https://github.com/facebook/relay/blob/master/compiler/crates/relay-compiler/src/config.rs#L396-L402

@artola fyi


Revert "fix: update all 'onXxx' methods to be CloudWatch Events (#2609)"

This reverts commit 28942d2115fe42d4e59e8dbbaec28197c1436e1c.
This is reverting the changes made in this PR, because Elad would prefer a different API, and since we want to release tomorrow I'd rather prefer we only have one breaking change rather than two.

Pull Request Checklist

[ ] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[ ] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated
Design: For significant features, design document added to design folder

[ ] Title and Description

Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

Not sure I want to revert this anymore. Discussion at: https://github.com/awslabs/aws-cdk/pull/2609#discussion_r287235993

How tied together are the different CDK packages?
Can one run v0.32 of everything and stay with v0.31 of cloudwatch-events?
Just curious.

Can one run v0.32 of everything and stay with v0.31 of cloudwatch-events?

No, everything has to be the same version.


Function tool callback

Description
This is a feature that allows applying some human-in-the-loop concepts in FunctionTool.
Basically, a callback function is added that enables the developer to request user input in the middle of an agent interaction, as well as allowing any programmatic action.
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[X] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[ ] Yes
[X] No

Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.

[ ] I added new unit tests to cover this change
[X] I believe this change is already covered by existing unit tests

Suggested Checklist:

[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I ran make format; make lint to appease the lint gods

Hello @logan-markewich, can you check it out? I've done the asynchronous implementation and now everything is up to standard


2.1.0.Alpha1 announcement

@Naros LGTM, thanks. There is one small inaccuracy, otherwise it is good to go.


Update lib for base/dom TS configs to target es2020

Description
Not having definitions for standard es features beyond es2108 is a bit old-school. The cool kids want to use Array.flat() :p
We expect any TS that we write shall be compiled through babel which shall transpile any modern features that are not yet supported by the consuming app/lib's targets, so I'm feeling ok with being being fairly modern with with our lib definition availability.
This Pr updates the lib definitions so both the base and dom configs target "es2020". I believe this option was added in TS 3.5 which is sufficiently long ago (the pr that added it is from April 2019, and 3.5 was released May 2019).
esnext.asynciterable is removed because this functionality was standardised and is included as part of es2018 (which is in turn included by es2020).
Bonus questions
When comparing the difference between dom.json and base.json:
Base has "lib": ["dom", "es2020"]
Dom has: "lib": ["dom", "dom.iterable", "scripthost", "es2020"]
Why's dom in base.json? If that's important then should we be sticking dom.iterable/scripthost in base.json too and just remove the lib defiinition from dom.json?
Type of change

[x] typscript-configs Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish a new version for these changes)

How about setting it to ES2021? Unless a patent-related objection happens over the next few weeks (unlikely), it'll become a standard in its current form.


how can I set the width and height of the panel (32x32)?

I found this in the ESP32RGBmatrixPanel.h:
#define COLUMNS 64
#define ROWS 32

How can I overwrite this before initializing (ESP32RGBmatrixPanel matrix;) in my script (for 32x32)?
Or can I only set this in the ESP32RGBmatrixPanel.h?
My top left is x=32 y=0.

Change it to
#define COLUMNS 32
#define ROWS 32
?

yes, I didn't want to set it directly in the ESP32RGBmatrixPanel.h. In the *.ino file this did not work after the include. I didn't want to change your code to keep it compatible with other displays.

You have to change constructors and add parameters rows and columns to it.
And may be  colorChanellsCount too.
Some modules have R1, G1, B1, R2, G2, B2 => colorChanellsCount = 2.
Some modules have just R1, G1, B1=> colorChanellsCount = 1.

I also have this issue, but I'm pretty sure the problem is the constructor. The 64x32 and 32x32 panels are a different scan rate (1:8) versus 16x32 (1:4) so we'd need to re-write the constructor to support it.
I'm not sure how to properly re-write it, but here's an example Arduino project for driving 1:4 panels:
https://forum.arduino.cc/index.php?topic=503416.0


Maven Central?

This project is awesome.  Thank you for the effort.
I was wondering if there are plans to publish the artifacts to Maven central.  While I appreciate the jitpack.io repository, my concern is security of the artifacts.
If you are considering it and want help, I can assist.
Thank you!

Thanks for the interest, but as I have been more casually maintaining this project these days I don't currently have any plans to set up and maintain artifacts in Maven central. Jitpack has been the most convenient way for me to provide artifacts to users of Maven and other dependency management systems without much effort on my part. So far I have had no reason to be concerned about the security of Jitpack, but if it is a problem for you there is always the option of compiling your own copies of artifacts from source.

Thank you for the response.  Somehow the other day, when I looked at the jitpack.io website, I only found a landing page with no other information nor links.  Today, I see all the documentation, including how artifacts get uploaded there.  That helps a lot.
FYI - I use OSSRH for Maven Central.  It appears to be similar to jitpack except for doing the builds itself.


A reliable way to detect a docker image which doesn't have  an OS-file system (package manager)

Currently the best way I could find to detect the existence of a linux OS is by look for a  "release" or a "version" file in the /etc/*release or /etc/*version path. But this is not the most reliable way to detect.
Would really appreciate any help in figuring out a way to detect a existence of a OS File system in a docker image without running it on a container.

You'll have to look for that filepath in each layer's tarball, taking care to handle whiteout files in case a higher-up layer deleted the file present in a lower-down layer.
There are probably a few tools that bundle this layer-aware extracting logic, my favorite is crane which exposes this as a CLI and Go package, and can even be called like so:
$ crane export ubuntu - | tar -Oxf - usr/lib/os-release
NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
...

(from recipes)
nb: crane export doesn't follow symlinks, which /etc/os-release is on Ubuntu.

As Jason describes you'll need to walk through a view of the image's "rendered" filesystem to figure this out - there's nothing more direct in the image-spec per se to help with this I'm afraid.
I'm going to close this out but if you think there's something that should be addressed in the spec itself feel free to reopen and add some more detail of what you'd propose.


slow serialization and deserialization of maps

serialization and deserialization of map<int, vector > is very slow. i am passing this as object to the archives . It's taking around 3secs to deserialize 113MB file

https://github.com/USCiLab/cereal/issues/413


Update charles lib version

Charles 1.1.1 is out containing important bug fixes. Let's update the version and deploy.

@charlesmike hi there

@charlesmike hi there

Hi @amihaiemil! I can help you index your Github-hosted website, provided that the repository name respects the format owner.github.io (or has a gh-pages branch) and the command is given by the repo's owner.
More on commands here.


Use unittest.mock instead of external module.

Thanks @sir-sigurd! Unfortunately it looks like this is failing on Python 3.5 - any ideas?

It turns out that 'assert_called()andassert_called_once()were added in Python 3.6. They can be replaced withassertTrue(mock.called)andassertEqual(mock.call_count, 1)` or this PR should be postponed to until Python 3.5 support is dropped.


Updated documentation.

Related to https://github.com/kylemanna/docker-openvpn/pull/54
Allow better syntax highlighting.
Added/Fixed hyperlinks.
Spelling.

A lot of typos on my part.  Oops!  Thanks for finding and reading.
What's the benefit of the the shell syntax? Appears to be rendered the same and is alot harder to read in plain-text mode as I most often do.

Currently probably not much benefit. But I know other formats which look quite nice with syntax highlighting (for variables and so on) https://github.com/nickjj/ansigenome/pull/26. For now it just makes it explicit that something is a shell command.

I'd love to merge the typo fixes.
The shell mark-up looks like alot of noise for no visible value.  I'm also concerned that the shell markdown appears to be a Github flavored markdown feature.  I'm not sure if it would work well on https://hub.docker.com
Can you split the commit in your branch so we can move the typos forward? :+1:
It's easier to merge things when the commits are broken up in to smaller atomic commits such as docs: Fix miscellaneous typos and clarifications and docs: Convert to shell Github flavored markdown.    The Linux kernel has a great guide on this topic, but is extremely verbose.  I typically default to following those guidelines.

I just tested the Github flavored markdown on https://hub.docker.com and it works like the 4-space-indention (also without highlighting currently).
Sorry about not spiting the PR. I will just revert the Github flavored markdown thing.

This is how the Github flavored markdown would look like:
https://github.com/jchaney/owncloud
https://hub.docker.com/r/jchaney/owncloud/
I guess I am also not fully convinced about syntax highlighting for Shell.


Validate fn added to support the interface lib

Added a set of function to add the validation of the interface objects. Used in the interface lib as part of the arm functions

/approve
/lgtm


improperly accessed header dimensions

the axes variable defined here is used to access the dimension of the nifti header on this line. the nifti header spec indicates that the dim field of the header is an array like dim = [num_dimensions, i, j, k, num_volumes, ...]. (see section "Image Dimensions" here). In light of this, shouldn't the axes variable be changed to axes = {i: 1, j: 2, k: 3}?

I believe you are right. Good catch!


A couple minor source-build fixes

Add binlogging to the build script.  This makes issues easier to diagnose for us.
Rename the MS.Extensions.FileSystemGlobbing version property to match the usual convention.
Remove a reference to System.Runtime.CompilerServices.Unsafe.  We originally removed this to get rid of a prebuilt but I built VSTest standalone and it doesn't appear to actually be needed.  If it is, I can change it to only be included outside of source-build instead.

@crummel The build broke,  System.Runtime.CompilerServices.Unsafe seems to be required.

I switched this to be conditioned on DotNetBuildFromSource.  It looked like the Linux build did work, is that something you expect?  I could condition it on OS instead.

@crummel I guess it is only required for net451 framework then, can we use that as a condition instead?
 '$(TargetFramework)' == 'net451'

Closing because we have a newer sourcebuild PR pending.


✨ Package and publish rancher turtles on each release

What this PR does / why we need it:

introduces release workflow to run as a GH action similar to what is done both in CAPI/CAPI Operator which will be triggered on a new release tag push. This workflow will create a draft release and publish a helm chart. We will host our repository using github pages and publish helm charts using helm/chart-releaser-action action.
reworks kustomize folders to adjust it to charts introduction and created a new set of kustomize configurations
introduces new Makefile targets for release / releasing charts

This repository will also be used as a helm chart repository, we will host index.yaml in root of project and update it with every release.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes: https://github.com/rancher-sandbox/rancher-turtles/issues/14
Special notes for your reviewer:
Checklist:

[X] squashed commits into logical changes
[ ] includes documentation
[ ] adds unit tests
[ ] adds or updates e2e tests

Generally looks good to me.
With the changes to the config folder have you tried running make dev-env to check that it still works?

@richardcase thanks for review and pointing out. I was able to run it properly including my last commit (https://github.com/rancher-sandbox/rancher-turtles/pull/34/commits/077b53d21be5dd3ed3c399e0b794aec3f8bc18fd) to dev script (had to use newer version of rancher 2.7.5 instead of 2.7.3 since kind uses kindest/node:v1.26.3 image).
The same commit includes a new makefile target to cleanup development environment.

Generally looks good to me.
With the changes to the config folder have you tried running make dev-env to check that it still works?

@richardcase thanks for review and pointing out. I was able to run it properly including my last commit (https://github.com/rancher-sandbox/rancher-turtles/pull/34/commits/41f5d2a9ac9b8e4b5427df52ecaeeffeb098e259) to dev script (had to use newer version of rancher 2.7.5 instead of 2.7.3 since kind uses kindest/node:v1.26.3 image).
The same commit includes a new makefile target to cleanup development environment.

Generally looks good to me.
With the changes to the config folder have you tried running make dev-env to check that it still works?

@richardcase thanks for review and pointing out. I was able to run it properly, including my last commit (41f5d2a) which slightly changes dev script (had to use newer version of rancher 2.7.5 instead of 2.7.3 since kind uses kindest/node:v1.26.3 image). The same commit includes a new makefile target to cleanup development environment.

Aplogies, did not pay attention to failure messages 👀 , I'll investigate if kustomize changes is the cause of it

@richardcase @Danil-Grigorev as discussed offline, this should be ready for re-review again, rancher turtles controller pod not becoming ready does not seem to be related to these changes based on my testing (suspected commit is https://github.com/rancher-sandbox/rancher-turtles/pull/29/commits/9d132ec7e41f5fb645d5be96d7e1144013896c6e)

thanks for doing this!


[5.5][Dependency Scanning] Cherry-pick dependency scanner changes required for Explicit Module Builds

https://github.com/apple/swift/pull/38684: [Dependency Scanning] include -sdk in Swift module building command
https://github.com/apple/swift/pull/38703: [Dependency Scanning] Have the scanner cache answer queries relevant to current search paths only.
https://github.com/apple/swift/pull/37723: [Dependency Scanning] Add ability for -scan-dependencies action to serialize and deserialize dependency scanner cache from a .moddepcache file. Using the serialization format added in https://github.com/apple/swift/pull/37585.
https://github.com/apple/swift/pull/37585: [Dependency Scanning] Add a binary serialization format for the Inter-Module Dependencies Cache
https://github.com/apple/swift/pull/38710: Frontend: remove -swift-module-file. NFC
https://github.com/apple/swift/pull/38761: [Dependency Scanning] Split the ModuleDependencyCache into two: current scan cache & global.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 2d89d9f5094e2921fee92821f284b154c60ae222

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - f97cfaddfb5a5542fb5464190f6dcb88d9642166

@swift-ci please test

@swift-ci please test Windows platform

@swift-ci please test Windows platform


mncvision.id missing some channels

Why some channels epg are missing from mncvision.id and transvision.co.id epg?
eg; hbo, cinemax, natgeo, natgeo wild, discovery, etc
those channels are still exists on https://mncvision.id/schedule and https://www.transvision.co.id/jadwalacara/epg.html
I found this epg and it contains some missing channel epg
https://macan.tv/xmltv.php?username=epg&password=epg

Fixed in https://github.com/iptv-org/epg/commit/b9ce3fe01afad3f44ec57cfe63ea3f57b4bc8390


packaging: Exclude build/dist folders

Also fixes issue where build/lib folders are recursively created
during dev
Signed-off-by: Ryan Northey<EMAIL_ADDRESS>

cc @kfaseela


Pytest start optimization

Speed up tests duration

Screenshots

Pull Request Checklist

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] Database migration files are up to date.
[ ] The changes are tested.
[ ] GraphQL schema and type definitions are up to date.
[ ] Changes are mentioned in the changelog.

Hi,
During pytest start, all migrations running and it takes around of 30s-1m
--nomigrations and --reuse-db accelerate this process (--nomigrations automatically generate only one migration from the current state of the model)
Resume (on my local machine):
Before changes (all tests):
~155s
After changes:
~90s


[Question] How to connect to database using serverless/cloud function.

Hi, I read all documentation that I found, but still can't connect to ydb. I use serverless to deploy the stack.
I use following code to connect:
      const driver = new Driver({
          endpoint: "grpcs://ydb.serverless.yandexcloud.net:2135",
          database: "/ru-central1/b1g5f2a3d9hru8cnrec5/etnsmorj75fl505b6t4g",
          authService: new MetadataAuthService(),
      });

      const ready = await driver.ready(5);

      return {
          statusCode: 200,
          headers: {
              'Content-Type': 'text/plain',
          },
          body: "ready: " + ready,
      }

However when I try to execute the handler, I have following error:
No certificate found
It seems that you are using grpcs (secure) endpoint in a bundled environment.
Either provide YDB_SSL_ROOT_CERTIFICATES_FILE environment variable
or copy contents of ydb-nodejs-sdk/certs to ./certs path relative to the bundled file

This message looks really weird for me. Because:

The npm package is called 'ydb-sdk' not a 'ydb-nodejs-sdk'
There is no such folder 'ydb-sdk/certs'
I found the 'certs' folder in this repository, but next 'copy contents of ydb-nodejs-sdk/certs to ./certs path relative to the bundled file'. How I can do it with serverless? I think it's not trivial.
Anyway why I need to deal with certs if I build a cloud solution? I have aws background, so if I have a role to access the database then I can access it without auth, that is.

For accessing database my cloud function have '-editor' role, but no luck. Can you help me?
P. S. The examples I found looks outdated, and not well structured.

Hi! Sorry hear about that, it was a bug, we fixed it right now, in version<EMAIL_ADDRESS>Please update deps in your package and check, if it works.

As I see, you use MetadataAuthService, I'm not sure that you need it.
TokenAuthService worked fine for me, when I used ydb.serverless.yandexcloud.net. You'll need to use token from yc iam create-token like that: const authService = new TokenAuthService('t1.9euelZ....')


importing panda3d Modules in Vscode 1.68

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

VS Code Version: 1.68
OS Version: windows 10 pro
Hello . I am using Vscode 1.68 for programming python language . I have a problem with panda3d framework because when I try to import Modules in panda3d framework like core and ai the Autosuggestion of Vscode does not show any class and functions.
My python version : 3.10.5
The panda3d version:1.10.11

/extPython
Suggestions are provided by Python extension, not VS Code editor itself.
You should make sure that you have proper configuration of workspace and Python extension for workspace and report issue in extension's repo if problem isn't solved by config.

It looks like this is caused by the Python extension. Please file the issue to the Python extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


Feature backup to sftp

Hi,
i wanted to copy the backup files onto my local sftp/ssh linux server. I added the needed ENV Variables and the needed rsync function in the valheim-backup script.
Also i added the possible ENV Variables into the ENV Table in the readme file.
Greetings
hasechris

I wonder if this should be prefixed BACKUPS_SFTP when really it's BACKUPS_RSYNC and not using sftp anywhere.

@hasechris what do you think about making this more generic? Like instead of over time adding backup_sftp, backup_rsync, backup_s3, backup_ftp, backup_gcp, backup_azure, etc. we could have a generic post_backup hook that allows you to do whatever you like with the created backup file. The default could be : (noop) and if you set it to anything it'll get the name of the created backup file as first argument.


Add submodules support on GitHub through graphql api

:clipboard: Description
Currently, more and more projects use git submodules to split the project architecture, leaving an almost empty main repository (almost only references to submodules)
However, when counting data such as repo size/code size/comments, shields does not take the data of submodules into consideration.
Currently, GitHub GraphQL Api can already query submodules under a warehouse.
As long as the recursive search (specifying the front depth) is required, a submodule tree of the warehouse can be constructed.
The shields (repo size, etc.) mentioned above can be more accurate. (Of course, we may have to verify that the repositories belong to the same owner)
Take my own repo for example:

For some shields that can introduce this function, we can add (bool) includingSubmodules argument.

A slight issue here is that the submodule object isn't a full repository object. It only exposes quite a limited number of properties.
https://docs.github.com/en/graphql/reference/objects#submodule

branch
gitUrl
name
nameRaw
path
pathRaw
subprojectCommitOid

As far as I can tell, things like size, languages etc can't be fetched for all submodules in a single query, so we'd have to make a second round-trip to fetch the details for submodules. With the GraphQL API we could at least query the data for all submodules at once in a second query.
I think I'd want include_submodules to be an optional param which is off by default.
Which badges are you thinking this would apply to?

A slight issue here is that the submodule object isn't a full repository object. It only exposes quite a limited number of properties.
https://docs.github.com/en/graphql/reference/objects#submodule

branch
gitUrl
name
nameRaw
path
pathRaw
subprojectCommitOid

As far as I can tell, things like size, languages etc can't be fetched for all submodules in a single query, so we'd have to make a second round-trip to fetch the details for submodules. With the GraphQL API we could at least query the data for all submodules at once in a second query.
I think I'd want include_submodules to be an optional param which is off by default.
Which badges are you thinking this would apply to?

As you said, it does require a second query to get the exact information, but I think it is worth it. Of course, in order to relieve the pressure on the server, this attribute should be turned off by default.
I think this property can be applied to the following shield first:

https://shields.io/badges/git-hub-code-size-in-bytes
https://shields.io/badges/git-hub-repo-file-or-directory-count
https://shields.io/badges/git-hub-repo-size
https://shields.io/badges/git-hub-repo-stars

https://shields.io/badges/git-hub-code-size-in-bytes
https://shields.io/badges/git-hub-repo-file-or-directory-count
https://shields.io/badges/git-hub-repo-size

I think I agree with the first 3 :+1:

https://shields.io/badges/git-hub-repo-stars

Not sure about stars. If I make a repo and pull in https://github.com/freeCodeCamp/freeCodeCamp as a submodule, my repo now has >300k stars? :smile:

Not sure about stars. If I make a repo and pull in https://github.com/freeCodeCamp/freeCodeCamp as a submodule, my repo now has >300k stars? 😄

We could only count submodules' stars when they are owned by same owner, which could be better.


Error executing luv callback(termux)

Error display on neovim
Error executing luv callback: ....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:299: get https://github.com/ Exafunction/codeium/releases/download/language-server-v1.6.7/language_server_linux_x64.g z - curl error exit_code=23 stderr={ "curl: (23) Failed writing received data to disk/ap plication" } stack traceback:         [C]: in function 'error'         ....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:299: in function '_u ser_on_exit'         .../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:240: in function '_s hutdown'         .../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:47: in function <... /.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:38>
Neovim & Device Info
`~ $ nvim -v
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.0-beta3
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/data/data/com.termux/files/usr/share/nvim"
Run :checkhealth for more info
~ $ uname -a
Linux localhost 4.19.127-gfc2fca064b48-dirty #1 SMP PREEMPT Thu Jan 11 15:50:01 CST 2024 armv7l Android`

While attempting to install the Codeium Neovim plugin in Termux on my ARM64-v8a device, I encountered the following error:
Error executing luv callback:
.../share/nvim-ayoub/lazy/plenary.nvim/lua/plenary/curl.lua:300: get https://github.com/Exafunction/codeium/releases/download/language-server-v1.8.80/language_server_linux_arm.gz - curl error exit_code=23 stderr={ "curl: (23) Failed writing received data to disk/application" }

It seems that there is an issue with writing the downloaded data to the disk or application. Any help or guidance to resolve this would be appreciated.


refactor(bindings/ocaml): Refactor module to support documentation

The current auto-generated OCaml code cannot add documentation comments.
This change separates the automatically generated code, adds a new module to map the automatically generated functions and adds annotations.

Please Update branch to make sure our PR works with main bracnch.


Check Action:Find AWS Lambdas Not Using ARM64 Graviton2 Processor

Description
Issue-537
Testing

Checklist:

[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published.

Documentation
Make sure that you have documented corresponding changes in this repository.

@amit-chandak-unskript , it seems that boto3 needs to be bumped up to 1.26.149 , we have 1.17.107. Updated the code to use paginator.

@amit-chandak-unskript , it seems that boto3 needs to be bumped up to 1.26.149 , we have 1.17.107. Updated the code to use paginator.

Thats great to know @shloka-bhalgat-unskript , please update the version in unskript repo for boto3


[Suggestion] Alpine Dockerfile

Hello,
I use docker whenever it possible, and i found the actual a bit weight (700Mb+) and not really user-friendly.
So i have created a new one (150Mb) based on python:2-alpine
It support :

webview
external conf
AutoRestart

You can see at https://github.com/arckosfr/dockerfiles/tree/master/PokemonGo-Bot
If you want you can use it to replace the original.

+1
How could you have 700mb ? Mine is only 310Mb

yes without python:2.7-onbuild (the size of the tag is not realistic because it exclude the based image weight)

Oh yes ! My mistake ;)

Why did you close it? More and more official images are migrating to Alpine Linux, this shows how image size is a concern to many of us.


Markdown Output in View Mode is wrong

Description
It seems that sometimes the markdown formatting is failing with the rendering within the library. At least for documents. Within the edit mode where the WYSIWYG editor is rendered the rendering of the markdown is then correct. So currently the rendering seem to differ between the view and the edit mode.
Environment

Chronicle Keeper Version: dev-main
PHP Version: 8.4

Steps to Reproduce

Upload a DocX document containing lists with optimization
Have a look to the view mode - it is displayed wrong

Expected Behavior
I would expect that markdown that is shown within the WYSIWYG in a correct way is also correctly rendered within the view mode.

I can not find the error currently. After removing an empty row it worked. In the JSON Storage file was nothing at this line but a whitespace line break like in the other lines. It was only a single file showing the error. The difference to other files is that this file had * signs as listings while the others utilize -.
So no real finding currently but not a critical bug blocking the release of the next version.


lang, ts: Add map type

IDL support for Map types. Depends on https://github.com/project-serum/serum-ts/pull/181.
Because BTreeMap has two generic types I was forced to use syn to extract the two types. Without syn, only with recursive regex, which isn't available. Since I was using syn, I refactored the complete method (if that's not desired I can put it as was).

@armaniferrante I'm happy to write a simple integration test for this if we can get the borsh PR merged: project-serum/serum-ts#181

@armaniferrante I'm happy to write a simple integration test for this if we can get the borsh PR merged: project-serum/serum-ts#181

Sounds great. Let's write a test.

@kevinheavey maybe I am late but when writing the integration tests keep in mind that Javascript Map does key comparisons by reference (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map#key_equality), which works fine for primitive types or values which are the same but here we end up comparing objects which are deep equal but not the same most of the time (e.g., BN objects).

@joaompfe lol actually if you're still around do you wanna add an integration test? Turns out adding to someone else's integration test is messier than I thought

@joaompfe, can I help with this? I would really like to see this feature merged.

@joaompfe could be a useful feature


"nix-shell -p emacs30-nox" errors out

Describe the bug
cannot install emacs30-nox, see attached error.log
Steps To Reproduce
nix-shell -p emacs30-nox
Expected behavior
install of emacs30-nox
Screenshots
see attached error.log
Additional context
compiling from emacs-git and emacs-unstable works
Metadata

system: "x86_64-linux"
host os: Linux 6.6.63, NixOS, 24.05 (Uakari), 24.05.20241203.bcb6888
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.18.8
channels(root): "nixos-24.05"
nixpkgs: /nix/store/kc8l8brczqp1zzha5xq001h6qxv1qb8d-source

Notify maintainers

Anderson Torres<EMAIL_ADDRESS>Adam Hose<EMAIL_ADDRESS>John Wiegley<EMAIL_ADDRESS>Jason O'Conal<EMAIL_ADDRESS>Matthew Bauer<EMAIL_ADDRESS>Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.
error.log

According to the snippet of your error.log, changing (emacs30-nox) to (pkgs.emacs30-nox) presumably will fix the error.
 error: undefined variable 'emacs30-nox'

       at «string»:1:107:

            1| {...}@args: with import <nixpkgs> args; (pkgs.runCommandCC or pkgs.runCommand) "shell" { buildInputs = [ (emacs30-nox) ]; } ""
             |                                                                                ^

Closing as this is not a Nixpkgs issue.

FYI, there are #nix:nixos.org matrix room for questions about using nix and #emacs:nixos.org matrix room for nix/emacs-related things.

nixos-24.11 and nixos-unstable have emacs30-nox while nixos-24.05 does not.
Presumably you are using nixos-24.05.  I just backported emacs30-nox (and other variants) to nixos-24.05.  It takes a few days for it to reach users.  You can check the progress here: https://nixpk.gs/pr-tracker.html?pr=361788.
Feel free to re-open this if you have further questions.


Support for sending custom flags to terminal

[X] I have read the FAQs (https://dvlv.github.io/BoxBuddyRS/faqs)
[X] My feature is not on the Roadmap (https://dvlv.github.io/BoxBuddyRS/ROADMAP)
[X] I have searched for previous issues (https://github.com/Dvlv/BoxBuddyRS/issues?q=is%3Aissue+is%3Aclosed)

Describe your feature request below
I like to have my Distrobox terminal clearly identified. The updated prompt does indicate which Distrobox is being run but when I have open 4+ terminals it can be harder to find a specific one. I really want my Distroboxes and my host terminal to have different color profiles. It doesn't seem that hard to have a text entry field below the Terminal selection for flags that I want to send to the terminal application (in this case a different color profile). If I could set terminal flags per Distrobox that's even better because then every one would have a different color!
I've tried working around this limitation in a few ways but it hasn't really worked out because every way I try to trick my default Terminal or Distroboxes to be different they always have the same color scheme.

Respectfully, distrobox has no knowledge or integration with terminal emulators but BoxBuddy does. If BoxBuddy were to say, "We don't want to deal with the details of terminal emulators at all. Create a script called 'boxbuddy-term' on your path and we'll execute that." then I could have solved this quite easily.
In any case I found a workaround. For those that want this behavior put this script (or a similar one, tweaked to your own system) on your PATH where BoxBuddy can find it.
#!/usr/bin/env bash

PARAMS="$@"
ALT_PROFILE=06548683e8341390652cde42673aafea

if [[ "$PARAMS" == *"distrobox"* ]]; then
    # A distrobox is trying to be launched
    /usr/bin/ptyxis --new-window --tab-with-profile=$ALT_PROFILE $PARAMS
else
    # Enforce normal behavior
    /usr/bin/ptyxis $PARAMS
fi

Of course do what you need to do to execute your terminal of choice and activate the correct profile. Test extensively to make sure it's working as expected and the default terminal isn't busted!

Since I don't use gnome-terminal I opted to make that a named script instead. This simplifies the script so I don't have to do an if-statement anymore (pretty much only BoxBuddy should use my script).


CoreOS MVP: Ignition Server Token Rotation Problem: Rotation kills all in flight provision operations (No overlapping time with old and new token in place)

The current process to rotate ignition tokens has a gap: there is no period of time to where both tokens for a given config version are both active. Let's walk through the full lifecycle of the current process:

Token Secret created here:
https://github.com/openshift/hypershift/blob/main/hypershift-operator/controllers/nodepool/nodepool_controller.go#L467

It is only ever created: (data specifically the token field is never updated after creation)

Ignition Server will grab the token:
https://github.com/openshift/hypershift/blob/c036de9df6f1117b72c9e0bbf588ff659c06f95a/ignition-server/controllers/tokensecret_controller.go#L159

generate the entire config:  https://github.com/openshift/hypershift/blob/c036de9df6f1117b72c9e0bbf588ff659c06f95a/ignition-server/controllers/tokensecret_controller.go#L172
And store it. At this point there will be one entry in the local cache of the ignition server:
token-c7vi53r106v03v8bp1cg-dccab0f-933bb65-e71afcdf       Opaque                                3      5h32m

After 11 hours the ignition server proceeds to delete the token in this code:
https://github.com/openshift/hypershift/blob/c036de9df6f1117b72c9e0bbf588ff659c06f95a/ignition-server/controllers/tokensecret_controller.go#L147-L149

When deleting the secret the token is purged and no longer valid: At this point all in flight operations will fail because the token has been removed from the system. The problem with this is there is no updated period where there is a new token active in the system in parallel with the old token that is about to be rotated out. That is critical to ensure no in flight operations cancel out during that period of time. The key point to think on is what if a user provisions 1 second before the TTL on that secret expires: If it does that it will proceed to take the existing userdata secret and provision the machine with it. The machine will take longer than a second to provision. By the time it boots and calls into ignition: the token will no longer be valid and it will fail the provision process.
What we need to do is determine a way for a given config for two secrets to be valid at a given period of time. Then after X amount of time (configurable should be multiple hours) the rotation should add a new secret in, and update the user-data secret with that value. The current token should move to the "old slot" or queued to be rotated out on the next iteration (view it as token_old). Either token should be honored during that period of time. Then next rotation same process occurs and ultimately the old secret is eliminated.
Impact of this is users provisions fail when they are booted around the time of expiration.

Replication:

Download the token in use from the user-data secret:

`kubectl --kubeconfig /tmp/c7vcvau10qflf8nns0pg-admin-kubeconfig get secrets -n master-c7vi53r106v03v8bp1cg  user-data-c7vi53r106v03v8bp1cg-dccab0f-933bb65-e71afcdf -o jsonpath='{.data.value}' | base64 -d

.....
Specifically interested in the
"ignition":{"config":{"merge":[{"httpHeaders":[{"name":"Authorization","value":"Bearer OTYzZTk3NjEtMjBjMi00NTE3LThhOWUtNWQ1YmUzNTBlYTE0"}],"source":"https://t4dce373102570ed80a75-d603ff82e51c94176a53d44566df9d79-ce00.us-south.satellite.test.appdomain.cloud:30631/ignition","verification":{}}]
section

Curl the ignition endpoint, you will be able to download the payload

curl -vk -H 'Authorization: Bearer OTYzZTk3NjEtMjBjMi00NTE3LThhOWUtNWQ1YmUzNTBlYTE0' https://t4dce373102570ed80a75-d603ff82e51c94176a53d44566df9d79-ce00.us-south.satellite.test.appdomain.cloud:30631/ignition

Wait for secret to get to any short period of time before expiration

token-c7vi53r106v03v8bp1cg-dccab0f-933bb65-e71afcdf       Opaque                                3      10h59m

Watch secret get recreated:

token-c7vi53r106v03v8bp1cg-dccab0f-933bb65-e71afcdf       Opaque                                3      6s

Try to curl using old ignition token

Tylers-MacBook-Pro:armada tylerlisowski$ curl -k -H 'Authorization: Bearer OTYzZTk3NjEtMjBjMi00NTE3LThhOWUtNWQ1YmUzNTBlYTE0' https://t4dce373102570ed80a75-d603ff82e51c94176a53d44566df9d79-ce00.us-south.satellite.test.appdomain.cloud:30631/ignition
Unauthorized

To test fix:
We should have a well known period where 2 token values are active at a period of time. Performance team is also seeing load that periodically every 11 hours we are creating a rush of (440 clusters * 12 node pools per cluster * 3 machine config server pods generated to populate cache of ignition servers = 15840 pods every 11 hours) since we remove the secret that often. We should be able to keep the existing secret in place since all the config has been downloaded. If we kept a cached version of the full config in the secret this would allow us to only have to repopulate when a nodePool actually went through a change versus causing a mass refresh of the entire fleet twice a day.
One suggestion is we can have a
token_1 and token_0 field in the secret along with a field that keeps a compressed cache of the entire machine content that is downloaded from the ignition server. Periodically: token_0 is set with the new token, and then the existing value of token_0 is moved to token_1. That would mean after two iterations the value in token_0 is fully revoked.

Acceptance Criteria:

[ ] A rotation pattern that does not result in large scale redeployments of the machine config server pods on an interval when no config parameters change. (Only thing that should change is the token).
[ ] A rotation pattern where for a well defined period of time: two tokens are able to be used for a given payload in a period of time. The rotation pattern then in a defined motion revokes the oldest, moves the current to the old slot, and then adds the new to the new slot. The user-data secret should be updated to use the new token always for future provisions.


MOTD issues

The new ads/MOTD system seems to cause some issues:
https://sentry.io/compiler-explorer/compiler-explorer/issues/629735356/
Stacktrace (most recent call first):

  at handler (./static/motd.js:80:1)

Could be ad-blocker related, perhaps?

    $.getJSON(url)
        .then(function (res) {
            handleMotd(res, motdNode, defaultLanguage, adsEnabled, onHide);
        })
        .catch(function (xhr, error, exc) {
            Raven.captureException(exc);
        });

I suspect the parameters to catch are wrong, so we're doing Raven.captureException(undefined). Maybe it's a timeout?

Fiddled with this and hopefully fixed in 423f6688efca7a11dd7f5f21281f2e1c82de794c

I changed the function signature but it's still not right :)
MESSAGE
Non-Error exception captured with keys: abort, always, catch, done, fail…

Sentry issue: COMPILER-EXPLORER-47W

Maybe fixed it again...we'll see :-)

This has never gone away. We should either swallow it up, or work out what on earth is going on here :)

MOTD error for /motd/motd-prod.json - error -  is what it shows up - that is, textStatus is "error" and the "errorThrown" is undefined or empty. Breadcrumbs show a normal GET to the right URL goes out. Could be ad blockers etc though?

Dear me I hope I find out what this is. It's really annoying me :)

With latest info:
MOTD error for /motd/motd-prod.json - error - no error - readyState=0 - status=0

so, looks like we get MOTD canceled without even fetching anything, if I'm reading it right. Which I'm probably not.
Anyone with an ad blocker able to repro this?

Got it to trigger (No adblocker needed) by navigating to another page/refreshing when the page is loading, before the reponse gets thru. The request gets cancelled and that's what we see as a status 0 (so at least in that way, this is not an error!)
But, it might be being triggered by something else too, who knows!
Sentry sadly does not save enough information to confirm if every instance of this is because of what I descirbed though

Thanks Ruben! Deploying shortly...

@RubenRBS and I spoke and I think we should probably just ignore these. I think we have accepted that page cancels, navigations, slow page loads, ad blockers etc are all completely sensible and valid errors we'll see.


Gh 1301 getwalks

Codecov Report

Merging #1498 into develop will decrease coverage by 0.17%.
The diff coverage is 50.92%.

@@              Coverage Diff              @@
##             develop    #1498      +/-   ##
=============================================
- Coverage      66.71%   66.53%   -0.18%
- Complexity      1744     1763      +19
=============================================
  Files            724      728       +4
  Lines          23692    23961     +269
  Branches        3000     3038      +38
=============================================
+ Hits           15805    15942     +137
- Misses          6676     6800     +124
- Partials        1211     1219       +8

Impacted Files
Coverage Δ
Complexity Δ

...n/java/uk/gov/gchq/gaffer/operation/Operation.java
59.57% <ø> (ø)
9 <0> (ø)
:arrow_down:

...ddelements/impl/CalculateSplitPointsFromIndex.java
68.75% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../gov/gchq/gaffer/hbasestore/utils/IngestUtils.java
66.66% <ø> (ø)
0 <0> (ø)
:arrow_down:

...v/gchq/gaffer/accumulostore/utils/IngestUtils.java
74.07% <ø> (ø)
0 <0> (ø)
:arrow_down:

...on/resolver/named/NamedOperationScoreResolver.java
92.3% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../uk/gov/gchq/gaffer/commonutil/stream/Streams.java
45.45% <0%> (-4.55%)
10 <0> (ø)

...fer/operation/serialisation/TypeReferenceImpl.java
58.33% <0%> (-7.3%)
1 <0> (ø)

...va/uk/gov/gchq/gaffer/data/graph/AdjacencyMap.java
0% <0%> (ø)
0 <0> (?)

...fer/commonutil/iterable/EmptyClosableIterable.java
16.66% <0%> (-50%)
2 <0> (ø)

.../uk/gov/gchq/gaffer/commonutil/CollectionUtil.java
87.5% <100%> (+1.5%)
26 <3> (+3)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

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


loss一般降低到多少算拟合了。d2训练loss从4降低到0.56，算拟合了吗？训练集的map到0.71了

I use VOC2007 and now the loss reduces from 2 to 0.95 and mAP is 0.86. Just for reference


[pod-gateway] fix: run gateway init as privileged

Description of the change
This sets the gateway init container to privileged: true to support https://github.com/k8s-at-home/pod-gateway/pull/5. This is required for CNIs that disable IP forwarding irrespective of the host node's settings (Calico, possibly others.)
Benefits
Allows the gateway to work with Calico
Possible drawbacks
Not great security wise, but the other option is forcing users to enable container forwarding globally in the CNI settings.
Applicable issues

Additional information

Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Title of the PR starts with chart name (e.g. [home-assistant])
[x] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

Merged into #936 downstream


add IsInvalid property to Handle class

Reason for change:
The ConsumerBuilder starts logging messages to LogHandler from within Build method with partially constructed IConsumer object (Kafka library handle is null). There is no way to determine whether the IConsumer properties can be accessed without triggering an exception.
This property will allow to check whether Handle property in IConsumer interface is valid and therefore other properties and methods could be called.

@confluentinc It looks like @volgunin just signed our Contributor License Agreement. :+1:
Always at your service,
clabot


Model Parallel Example

Is there an example on model parallelism we can follow, especially setting up the mpu? This is mostly for single machine, multi-gpu training, though we'd want to generalize it multi-machine training at some point in the future.

Hi @alexorona
I think you can take a look at our example from MegatronLM, here.

Hi @alexorona
I think you can take a look at our example from MegatronLM, here.

hi @RezaYazdaniAminabadi , is there any example of how to use mpu / model parallelism with a Pipeline Module?

hi @RezaYazdaniAminabadi , is there any example of how to use mpu / model parallelism with a Pipeline Module?

Hi! Is there an examle where ZeRO is used with model parallelism? Megatron-Deepspeed seems to be not using ZeRO in the implementation? Is it using ZeRO?


Create and include a default IamFleetRole per kube-aws cluster

Extracted from https://github.com/kubernetes-incubator/kube-aws/issues/1022#issuecomment-346778723
cc @c-knowles
Perhaps we could either:

Include the default IamFleetRole for each spot-fleet based node pool
Or include it in the root stack and import it into all the spot-fleet based node pools depending on the default IamFleetRole?

The former would be easier to implemented but the latter would consume a lesser num of roles in your aws account.

Default limit is 1000 roles per account.
I'm in favour of the simplified version until someone needs it shared.


search

Also show the percentage of frames matching the search, excluding vertical overlap. Ie, a percentage (up to 100%).


Chat Admin issue (How to ban users from Admin area)

Hi,
-User admin (first user) with all role tested:
Selecting ID users for ban, will result in : USER IS NOT ROOT
Thoughts?

Fixed

Fixed

Having the same issue. How did you fix this?

Same here... any ideas to fix this?
Thanks

Same here... any ideas to fix this?
Thanks

Going to have another go at this one. Will let you know.

Going to have another go at this one. Will let you know.

Ideally you’d think the admin would already have access to all the
support/moderation pages but seems admin account can only do some core
things. Wish there was simply an option to allow admin all access. I can’t
even get the support role to show the support role pages...
On Mon, Jan 25, 2021 at 4:41 PM freakcoderz<EMAIL_ADDRESS>wrote:

Going to have another go at this one. Will let you know.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/3s3s/opentrade/issues/175#issuecomment-767099624, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQC7YRDNBZ3OQ232X6VH43S3XJPXANCNFSM4F326IPQ
.

Ideally you’d think the admin would already have access to all the
support/moderation pages but seems admin account can only do some core
things. Wish there was simply an option to allow admin all access. I can’t
even get the support role to show the support role pages...
On Mon, Jan 25, 2021 at 4:41 PM freakcoderz<EMAIL_ADDRESS>wrote:

Going to have another go at this one. Will let you know.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/3s3s/opentrade/issues/175#issuecomment-767099624, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQC7YRDNBZ3OQ232X6VH43S3XJPXANCNFSM4F326IPQ
.


Update phone section

Before

After
![2022-08-05](https://user-images.githubusercontent.com/47184160/183135638-e4c55459-579c-4bab-9cb3-b16e51b0e116.png)
Make the auto suggest fit

make phone component scale to view width and view height

make the mobile modal reach the bottom and make the buttons gray on select

This is a lot of dead space, is that the design we want?

Yeah, it is a lot of dead space that hides the map. We need to not hide the map...

@tabiodun @aarontitus  Made updates to make smaller modals take less space and ones that use tables take up larger space


excessive traffic generated from overlay networking on kernels <3.16

Excessive traffic is generated from overlay networking on kernels <3.16 when using UCP 1.1.0 with docker 1.11.1 (and probably earlier versions too). My repro uses kernel 3.13 with ubuntu 14.04, but I suspect that it's the same for any kernel <3.16 because overlay networking works differently for later kernels and I haven't been able to repro this issue there.
You might have to tweak some of the parameters to get it to work on your aws account. You need a wide open security group to make sure you don't run into any firewall issues. I also haven't tested the license injection part, so if that doesn't work, enter the license through the web ui. My repro was done using docker machine 0.6 (in case that makes a difference).
 We suspect that these errors become more and more frequent and they might be responsible for DoSing the network after a while. I'm confirming this theory right now. I'll post an update with aws network traffic graphs after I leave this repro running for a while.

Here are some of the results. Part way through I started two more containers on the overlay network and you can see the increase in traffic in the graph. These numbers seem pretty high to me.

After taking these screenshots I removed both containers from the overlay network and the slave traffic went down to around 50kBps on both nodes.

@vikstrous thanks for all the data. Does this happen regardless of the --subnet you used to create the network ?
For example, do you still see the same issue If you create a network using docker network create -d overlay --subnet=<IP_ADDRESS>/16 repronet ?

The LAN IPs of the nodes all start with 172. so I don't expect the subnet to matter, but I haven't tried changing it.

@mavenugo I just tried deleting the containers and network and creating a new network with new containers with a custom subnet and it behaved the same way.

Opened https://github.com/docker/docker/issues/22975 for tracking this in the docker/docker repository

I can repro at least the issue of the weird peer lookups with simply:
Create machine with kernel < 3.16, then...
$ docker run -d --name etcd --net=host quay.io/coreos/etcd`
$ `echo {"debug": true, "cluster-store": "etcd://<IP_ADDRESS>:2379", "cluster-advertise": "<IP_ADDRESS>:2375"}` > /etc/docker/daemon.json && kill -HUP <docker pid>`
$ docker run -d --name test1 busybox top
$ docker network create -d overlay testnet
$ docker run -d --net=testnet --name test2 busybox top

However the code-path for peer lookups does not seem to  confirm that this is the cause of high etcd traffic.

It looks like those AWS graphs are actually per 5 minutes, not per second, which makes way more sense. It looks like an extra 66 bytes per second per container? The traffic is not that high, but it's concerning that there's any traffic at all.


Remove SuppressWarnings nullness from JsonMatcher

This PR addresses #20507 by replacing JsonMatcher's use of the SuppressWarnings nullness annotation with:

Apply final to constructor initialized field
Apply the @MonotonicNonNull annotation to a late initialized field actualMap that is checked for nullness using checkStateNotNull.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Run Java_Pulsar_IO_Direct PreCommit

Run Java PreCommit

assign set of reviewers

R: @Abacn

This looks valid to me.
Just a note - this kind of clean up some times is not as trivial as one thought, and could introduce bugs. Recently I dealt with #29393 which was introduced in nullness clean up and took two other attempt to fix it

Thank you, @Abacn. This is why I'm going a class at a time and extremely slowly. Additionally, I only perform one PR at a time as well and let it merge and wait for some time to see if this introduced new problems.


Bug: Lots of match data on the EA server are lost.

It seems that the problem that the previous EA server game has been lost has not been solved yet.
Not only is the reflection of data delayed, it seems that only some of the match data will be reflected.

@kvahuja, @genexp
It integrates with the issue of #232


Bump IDOM version within Django IDOM

This is just a reminder for myself to do it.

I don't think there's anything that should break when you do this. Let me know if it does though.


Cisco device error in the log

I see this error continuously logged in my proxy minion for cisco device:
Exception argument of type 'bool' is not iterable occurred in scheduled job
Any idea about this error?

Closing, as it's a duplicate of https://github.com/saltstack/salt/issues/47695.


Transparency not working

The option to make the main window in discord transparent doesn't work. Any fixes?

What is your operating system? Have you enabled it and restarted (not reloaded) Discord?  Here's some test css that might help see through the window:
:root {
    opacity: 0.6;
}

im having this problem too.
Windows 10. Yes. How do you do that? where is that.

Go to settings > Zere's Fork > enable transparency and restart discord. Then put that code above into settings > custom css


support gleam

cc: @lpil

Is there no block comments in gleam? Just curious.

~Is there no block comments in gleam? Just curious.~ I've read the docs, and the answer seem to be "no block comments" :)

Yeah, no block comments for now. Thanks for merging 🙂


Spyder Kernel Dieing

Upon opening Spyder, the following appears in the console.
It seems the kernel died unexpectedly. Use 'Restart kernel' to continue using this console.
It seems the kernel died unexpectedly. Use 'Restart kernel' to continue using this console.
...
Restarting the console does not fix the issue.
Please help.
Thanks

Thanks for reporting this bug. Unfortunately, it seems you dismissed the information asked by our issues template, i.e. the information we ask our users when they try to open an issue here on Github.
This information includes Spyder version, operating system, dependencies information and several other things. Without it we are not able to understand and solve Spyder bugs as efficiently as we would like to.
Because of that, I'm going to close your report, and ask you to open a new one with that information filled.
Thanks for understanding :-)


mariadb: 10.2.14 -> 10.2.15

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@grahamcofborg build mariadb

Success on x86_64-linux (full log)
Attempted: mariadb
Partial log (click to expand)
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15/bin/galera_new_cluster: interpreter directive changed from "/bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15/bin/mariadb-service-convert: interpreter directive changed from "/bin/bash" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/bash"
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15/bin/wsrep_sst_mysqldump: interpreter directive changed from "/bin/bash -ue" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/bash -ue"
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15/bin/wsrep_sst_xtrabackup-v2: interpreter directive changed from "/bin/bash -ue" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/bash -ue"
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15/bin/mysql_secure_installation: interpreter directive changed from "/bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15/bin/msql2mysql: interpreter directive changed from "/bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15/bin/wsrep_sst_rsync: interpreter directive changed from "/bin/sh -ue" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh -ue"
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15/bin/wsrep_sst_mariabackup: interpreter directive changed from "/bin/bash -ue" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/bash -ue"
checking for references to /build in /nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15...
/nix/store/i16kkz8jcw9bl9dw41w9h0b57xmj2b57-mariadb-10.2.15

Failure on aarch64-linux (full log)
Attempted: mariadb
Partial log (click to expand)
[ 98%] Building CXX object storage/mroonga/CMakeFiles/mroonga.dir/lib/mrn_context_pool.cpp.o
[ 98%] Building CXX object storage/mroonga/CMakeFiles/mroonga.dir/lib/mrn_smart_bitmap.cpp.o
[ 98%] Building CXX object storage/mroonga/CMakeFiles/mroonga.dir/lib/mrn_operations.cpp.o
[ 98%] Building CXX object storage/mroonga/CMakeFiles/mroonga.dir/lib/mrn_table_fields_offset_mover.cpp.o
[ 98%] Building CXX object storage/mroonga/CMakeFiles/mroonga.dir/lib/mrn_operation.cpp.o
[ 98%] Building CXX object storage/mroonga/CMakeFiles/mroonga.dir/lib/mrn_count_skip_checker.cpp.o
[ 98%] Linking CXX shared module ha_mroonga.so
[ 98%] Built target mroonga
building of '/nix/store/p8cn06sllr5626ycb3pz9w15kw4vqrjn-mariadb-10.2.15.drv' timed out after 3600 seconds
error: build of '/nix/store/p8cn06sllr5626ycb3pz9w15kw4vqrjn-mariadb-10.2.15.drv' failed

Not much we can do about the ofborg timeouts, so let's merge this and observe it on Hydra.


localization

I'm using the "mcamara/laravel-localization" package and was wondering about the json files and the possibility of them being translatable too?
I thought about have a db table for this but I'm still playing around with a few ideas.

I think it'd be possible with what's already provided. Within your module's manifest file, have the properties simply define a localization key:
{
    "name": "blog::manifest.name",
    "slug": "blog",
    "version": "1.0",
    "description": "blog::manifest.description",
    "_etc": "..."
}

Store your translation/lang files with your module:
app/Modules/Blog/Resources/Lang/en/manifest.php
<?php

return [
    'name'        => 'Blog',
    'description' => 'Write blog entries.',
];

app/Modules/Blog/Resources/Lang/jp/manifest.php
<?php

return [
    'name'        => 'ブログ',
    'description' => 'ブログエントリを書きます。',
];

You'll need to verify that your module's are loading their own translation files if you wish to bundle them together: http://laravel.com/docs/5.0/packages#translations. This would be defined in your module's primary service provider.
Then simply use the lang() helper method to translate the manifest:
$blogModule = Module::getProperties('blog');

echo lang($blogModule['name']);

Thanks, will give this a try.
Do you have anything in the pipeline like a "mcamara/laravel-localization" type of package?

Haha, no, I don't.


WarcRevisit Builder with String targetURI

Similar to https://github.com/iipc/jwarc/issues/63 I have added an additional constructor to accept a String instead of an URI when building a WarcRevisit.
I'll add a pull request for this.
https://github.com/iipc/jwarc/pull/68
I would be grateful if this can become part of the jwarc library.

Thanks. Released as 0.21.0


流程图左侧下拉菜单是否可以支持二级下拉菜单

功能描述
目前流程图里面的左侧的下拉就只有一级菜单，业务比较多的时候只有一级菜单就显得结构不是很清晰
期望解决方案
配置参数里面多增加childern等可以配置二级菜单

👋 @Rong-ZS
Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. To help make it easier for us to investigate your issue, please follow the contributing guidelines. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

no! it not a bug, it's a new demand

不支持多级菜单的，可以使用 dnd 来实现，这样会更加灵活。


build: adjust GCP_OPTS format per gcloud reference guide

Perf tests fail with the current GCP_OPTS format and the gcloud
reference docs suggest that these values require the equal when the
long format is specified.
Signed-off-by: Christopher M. Luciano<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

cc @hklai @istio/test-infra-hackers
example failure https://storage.googleapis.com/istio-prow/pull/istio-releases_daily-release/1105/daily-perf-tests/678/build-log.txt

/lgtm
Thanks @cmluciano

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hklai
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [hklai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hklai
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [hklai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/retest

/retest


ContextMenu close logic unexpected

Currently it only closes if the context menu is in the sub-tree of the clicked element. I would expect it close when I click anywhere outside the menu. Most applications seem to handle it this way as well.
E.g. if a context menu is defined for each row in a table, opening the menu of one row then clicking on another will not close the menu, because those are separate trees. (Also, the clicked elements tend to be fairly deep in the tree, so in the table case it may be a span in a cell of the row.)

Maybe the logic was inversed by accident, usually one would check if the click was inside the menu and only close if it was outside.
One of my context menu components had it implemented this way:
function handleBodyClick(e: MouseEvent)
{
	if (showMenu && e.target instanceof HTMLElement
		&& e.target.closest('.context-menu-menu') == null)
	{
		showMenu = false;
	}
}

So it uses closest instead of contains.


Bug/ user unable to manage subscriptions

This issue is likely due to the user using a different e-mail to pay on Stripe.

[ ] Unable people from entering a different e-mail when paying

https://stripe.com/docs/payments/checkout/set-up-a-subscription#prefilling-customer-data this would fix the issue, leaving it for later use.


[IMPORTANT] Arbitrary code injection

http://pyenv.run/ is not secure.
Doing a curl followed by bash allows attackers observing your network connection to run arbitrary code on your PC.
Either upgrade http://pyenv.run/ to HTTPS or directly curl the GitHub file.

@qngapparat The instructions in the README.md say to use https to connect to pyenv.run.

@robnagler  Correct.
However, curl githubusercontent... upgrades to HTTPS, whereas curl pyenv.run uses the unsecure connection.
In my opinion that's a very unnecessary risk (considering the negligible convenience it brings).
Take into account how many people use this tool, a fraction is bound to just type curl pyenv.run. And it's piped directly into bash (!).
Thanks for the quick reply

There's no curl githubusercontent in the README nor is curl pyenv.run recommended. If people type that, there's little to be done.
To your specific point about "upgrading" the connection in the case of curl githubusercontent, this no more secure than accessing without the redirect. The initial non-TLS access would be hijacked if there were an attacker-in-the-middle. The "upgrade" would or would not happen.  Unlike some browsers, Curl does not automatically try TLS first. It should, perhaps, but that's outside our control.
The way you can test this is to not use -L on curl. You will see that nothing is returned, because the server issues a redirect over a clear text connection. That's when the attacker-in-the-middle would inject the attack, because the initial request from curl happens, again, in clear text, in all cases.
It actually gives a user a false sense of security to redirect to TLS. It is a convenience, of course, which is why most sites do it, but in this case, it's better that it just returns the data without the redirect.

Fair enough.


Add support for Linux on IBM Z mainframes and s390x architecture

Description
This is a proposal to add support of Linux on IBM Z and the s390x systems architecture to the OpenTelemetry Collector distributions. The mainframe systems IBM Z and LinuxONE are built on the s390x architecture and are widely used by large enterprises, e.g., in the banking and insurance industry. We see a growing interest of customers but as well from ISVs to explore OpenTelemetry for the mainframe. The support of Linux on IBM Z by the OpenTelemetry Collector distributions will simplify the adoption of OpenTelemetry on the mainframe and enable to drive further observability enhancements for Linux on IBM Z using OpenTelemetry.
Use Cases
We see three primary use cases:

Enable end-to-end observability for distributed applications with services and components deployed in public/private cloud environments and on the mainframe.
Enable customers to use for Linux on IBM Z and the mainframe the same observability products and tools as for other platforms.
Enable ISVs to support Linux on IBM Z and the mainframe more easily.

Support ownership
@bwalk-at-ibm and myself (@rrschulze) will take ownership of the OpenTelemetry support for Linux on IBM Z and the s390x architecture. We will continue to maintain contributions for the s390x platform, i.e., act as owners for issues and problems related to Linux on IBM Z and run regularly verifications on s390 VMs.
We will join the Collector SIG meetings starting from Wednesday, August 2, 2023, and following ones.
In preparation of the PRs (core, contrib, releases) for the s390x support of the collector, we followed the instructions on this page. We tested the qemu-based build on a x86-64 machine and the build results on a s390x VM. In addition, we used and verified the OTel collector on the s390x platform for several scenarios already internally. We plan to submit the PRs  for the s390x support of the collector after discussing in the SIG meeting(s) and will submit an additional PR to update the documentation (e.g., this page) once the releases support the s390x platform.

I would like to define support tiers first as I mentioned previously for AIX here: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/19195#issuecomment-1458560971 Would you be willing to own this part of the process as well? I am happy to work with you on this and review any PRs you open

@mx-psi yes, I can do that. Let me prepare a proposal and new issue for it.

Hi @rrschulze, AFAIK there are already some QE measures in place to test the OpenShift otel distro on ppc64le and s390x. Would it help you to reuse parts of it here?

We have tier 3 support now for linux/s390x and the next release will have binaries for this platform :tada: I am going to close this, if we want to increase the tier we can open a separate issue for it.