Helm Chart Version | Need to auto-update the version number in the Charts read.me

We need to auto-update the https://github.com/ortelius/ortelius-charts/blob/main/charts/ortelius/README.md each time a workflow executes. Right now we must do it manually.
Need to pull the version number from the chart and add it to this section of the read.me. For example updating the 10.0.77 to 10.0.78:
![Version: 10.0.77](https://img.shields.io/badge/Version-10.0.77-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v10.0.0](https://img.shields.io/badge/AppVersion-v10.0.0-informational?style=flat-square)
In addition, we need append the same read.me with a change log. The change log can be derived from the git commit history.  Fo example, if we increment to 10.0.78, a new "Changes in" should be added.

This chart deploys all of the required secrets, services, and deployments on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

### Changes in 10.0.54 - 10.0.77
Updated all base images to remove vulnerabilities. Used cgr.dev/chainguard/python, cgr.dev/chainguard/jdk:latest, and python:3.10-alpine, eclipse-temurin:8-jdk-alpine base images. The cgr.dev ones work great if you do not have additional packages (openssl) to install otherwise alpine is needed.

cgr.dev is based on wolfi. Google distroless has vulnerabilities in the base image so they should not be used.

### Changes in 10.0.53

* Added new Microservice for ScoreCard
* Updated ingress for running local Kind Cluster
* Removed dependency on external jwt keys ```

Change is needed in this workflow - https://github.com/ortelius/ortelius-charts/blob/main/.github/workflows/generate-main-chart.yml

sudo go install github.com/mikefarah/yq/v4@latest will install yq that can be used to pull Chart version from the Chart.yaml

Another way to go is to update the main.js to read in the README.md, update it and write out a new README.md

Lets also consider that the simpliest might be as easy as a hook https://github.com/norwoodj/helm-docs

Tests are looking good

Next step is to combine all the readmes into one.

Example Helm doc with chart dependencies https://github.com/norwoodj/helm-docs/blob/master/example-charts/umbrella/README.md

Can the Ortelius values.yaml in ortelius/values.yaml be the grand overload of all things Ortelius Helm Chart configuration?
Essentially, if you want to override any defaults of the Microservices, we can use that values.yaml
One ring to rule them all.
Then Helm-Docs just needs to create Helm README documentation from one file?
We would not need any extra steps to merge the child chart README's.

Can the Ortelius values.yaml in ortelius/values.yaml be the grand overload of all things Ortelius Helm Chart configuration? Essentially, if you want to override any defaults of the Microservices, we can use that values.yaml One ring to rule them all. Then Helm-Docs just needs to create Helm README documentation from one file? We would not need any extra steps to merge the child chart README's. https://github.com/sachajw/ortelius-charts-testing/blob/main/ortelius/values.yaml

Yes, the values.yaml at the Parent chart will override the values in the child charts.  Just need to reference the child chart name when doing the override, i.e. ms-nginx.replicaCnt: 3.  Or you can override at the helm command line a --set parameters.

@sachajw I looked at the MERGED-README.md and its getting closer.  The values from the child charts are making it confusing to follow since the are just the derived values and not the ones you can override.
We should use a new file READEME.template that contains "tag placholders" for the dynamic data to be substituted in, plus the static text.  See from string import Template. That module enables text substitution based on ${MY_VAR} placeholder tag.
Summary Section

Changes Section
This section should be derived from the git commit log.  Work will need to be done on the GH Actions to push across the commit message from the child chart update over to the ortelius-charts repo actions.

Install Command Section
This section should be static text from the README.template since it does not change very often.

Parameters Section
This section should be static text from the README.template since it does not change very often.  And the default values are handled in the charts themselves.

Accessing the Ortelius UI After the Chart Install Section
This section should be static text from the README.template since it does not change very often.

Uninstalling Section
This section should be static text from the README.template since it does not change very often.

@sbtaylor15 awesome find to solve this issue!

Fixed ortelius/ortelius-charts#558


Migrate districtbuilder.org hosted zone to Route 53

Ensure that all of the DNS records in GoDaddy are migrated to Route 53, then update the districtbuilder.org name server configuration on GoDaddy to delegate to Route 53.
This will likely require Terraform state manipulation for both the production and staging AWS accounts.

In addition, we should update the r53_public_hosted_zone variable to reflect the new domain in both staging and production.

@hectcastro Nameservers have been switched over in GoDaddy DNS management to point to the nameservers in our districtbuilder.org hosted zone. Everything looks to be functioning as expected.
I've also removed the districtbuilder.azavea.com hosted zone from Terraform state, manually deleted and Terraform-managed records, and retained the pa.districtbuilder.azavea.com NS records.
This is ready for review.

Everything looks good. I think both versions of DB are functioning as expected with the update domains, and the DTL site is still working well. 👍


feat: added preloader feature

This is a preloader feature to enhance the user experience while the main content loads.
Changes Made

Added PreloaderContainer.js component to manage the loading state.
Created a Preloader.js component that displays a loading animation and text.
Integrated the PreloaderContainer into the main App.js component to ensure it displays Preloader during content loading.

Video Demonstration
I have included a video demonstrating the preloader in action.
https://github.com/user-attachments/assets/461c25f9-42ba-4ef6-9d16-6689450ab25e
Let me know if there are any suggestions or changes needed.

@Anas-Rehberlik Love your work dude nice!! 👍🎊

@Anas-Rehberlik Love your work dude nice!! 👍🎊

Thanks a ton! 🙌 Really appreciate it!👍


allowing user to pass in loadTemplate and and renderTemplate

functions. This will allow ubar to use other templating systems besides
handlebars if the user so chooses. If no template system is passed in,
ubar defualts to its tempalting system using handlebars

fixes issue #12

+1

+1

nice !


If the directory on which a watch is setup is created later, its contents are not added

Suppose I set up a watch on a directory that does not exist.
Now if I create that directory with child objects in it, such as by renaming another directory to the said directory, these child objects are not added. That is only one add event is emitted for the directory and thats it.
I expected that the behaviour would be to add everything in that directory because a watch on a directory, unlike a file, means a watching its contents.

Observed on windows, I assume?

Yes, windows 7 x64, iojs 3.0.0

Are these problems Windows specific?

I don't know for sure, but problems like this are often OS-specific and I recalled that you mentioned Windows in another issue.

I concur! And yes, on Windows.

The same happening here, Node v0.12.7 on Mac OS 10.10.5.

Let us know if that still happens with the latest chokidar.

Works... thanks!!!!


data:zakafan

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

done I changed it

done I changed it

wrong slash, use the other one forward one / this

done

done

Aight all good  👍


[chip-tool] Add support for multiple reads/subscribes into a single exchange

Problem
chip-tool can not issue requests with multiple attributes in a single exchange.
Change overview

Add supports for it

Testing
Locally tested with commands such as:

# Read attributes `0` and `1` from the `onoff` cluster onto endpoint `1
./out/debug/standalone/chip-tool onoff read-by-id 0,1 0x12344321 1

# Subscribe to the `start-up` event from the `basic` cluster onto endpoint 0 and 1
./out/debug/standalone/chip-tool basic subscribe-event start-up 1 3 0 0x12344321 0,1

# Read attributes `0` from all clusters onto endpoint `1` and read attribute `2` from cluster with id `0x28` onto endpoint `1`
./out/debug/standalone/chip-tool any read-by-id 0xffffffff,0x28 0,2 0x12344321 1,1

There is a little bit of code duplication in the ReportEvent and ReportAttribute method but that could be unified later.

Fast tracking tooling changes


Support TLS SMTP

In 449d946e983bb3dd8231185d2f499d7df9ede0fa support for SMTP STARTTLS was added. Support for TLS SMTP (all encrypted) is the only one missing 😄
I'll brush up my (lacking) Go skills and prepare a small PR since I made it work already for our installation. I propose we deprecate the smtp_starttls boolean option and use smtp_tls with three values, off, on, starttls. Would that be acceptable?

@g5pw Yes this sounds great. Would be happy to review a PR with this in place. Thanks!

As promised, here is the v1 @aebruno. Bear in mind that go is pretty new for me though :)

Uh-oh, something is not right, please hold on this for a bit while I test some more...

Alright, it should be good now.

Thanks for the review @aebruno, I'll push the changes shortly. Would you prefer a squashed merge for this or should I reorder the commits a bit?

squashed would be great. Thanks.

Thanks for the review @aebruno, I'll push the changes shortly. Would you prefer a squashed merge for this PR or should I reorder the commits a bit?


HIVE-27733: ensure PerfLogger is thread-safe;

What changes were proposed in this pull request?
Make the PerfLogger class thread-safe.
Why are the changes needed?
Avoid an unpredictable ConcurrentModifcationException
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?
Unit

Thanx @henrib, makes sense. dropped some comments.
Curious as in which case does this occur in actual query?

It is an elusive problem that only occurs sporadically in some tests; the concurrency window triggering the error seems very small so it is not easy to reproduce. But the problem does occur...

@ayushtkn Can this PR be merged?


Using fragment in other fragment makes the object null; the same fragment in the query not

Discussed in https://github.com/FormidableLabs/urql/discussions/2103 but I think this is a bug and not a question.
If I use the below code it doesn't work, the second query (team()) makes the player null in cache.
fragment PLAYER on Player {
  id
  createdAt
  team {
    ...TEAM
  }
}

fragment TEAM on Team {
  id
  createdAt
}

query player($id: ID!) {
  player(id: $id) {
    ...PLAYER
  }
}

query team($id: ID!) {
  team(id: $id) {
    ...TEAM
    player {
      ...PLAYER
    }
  }
}

The code below addresses the issue (this is the only change I do in my code base):
fragment PLAYER on Player {
  id
  createdAt
  # removed these lines from here:
  # team {
  # 	...TEAM
  # }
}

fragment TEAM on Team {
  id
  createdAt
}

query player($id: ID!) {
  player(id: $id) {
    ...PLAYER
    # to here:
    team {
      ...TEAM
    }
  }
}

query team($id: ID!) {
  team(id: $id) {
    ...TEAM
    player {
      ...PLAYER
    }
  }
}

My question is: why it works in queries and not in fragments?

Sorry, I'm closing this and have to ask you to keep it to the discussion first for two reasons;

There's no inherent difference between traversal with or without fragments. Traversal is absolutely identical and the only addition is the decision whether to traverse a fragment found in a selection set
The outcome of the discussion is unclear. If it's hard to reproduce, explain, or pin down to a suspected issue, then it's still not ready for a bug report. While we can help get there and an issue would achieve the same, the alternative here for me is to tack on a "needs more information" label, but since the discussion is still ongoing, that doesn't make much sense

Hope that works for you ✌ also on a side note, the most likely problem here is that you don't have a reverse link built up from responses and if your fragments lead into each other you may accidentally create a loop that neither Graphcache nor your API can resolve

I have a repro!!! 😃😃😃😃
I'm creating a repo in git here, here the gif:

I have a reproduction: https://github.com/frederikhors/iss-urql-fragment-null-obj
😃😃😃😃
The steps

git clone https://github.com/frederikhors/iss-urql-fragment-null-obj
npm install
go to https://codesandbox.io/s/apollo-server-urql-svelte-crud-h1pcl to start the server
npm run dev

The gif

There's no inherent difference between traversal with or without fragments.

This is what I thought too. But moving that fragment into the query then everything works.

the most likely problem here is that you don't have a reverse link built up from responses

How to create it?

if your fragments lead into each other you may accidentally create a loop that neither Graphcache nor your API can resolve

I think I'm not in a loop in this case.

@kitten since Github has been down for a long time I don't know if you have seen these answers, excuse the ping.


Add onChange callback

This closes #94.
Sorry I couldn't wait for confirmation on #94, but I needed this feature. I'm using my fork for the time being, but I'd prefer to go back to using the original pkg once (and if) this is merged here.
Thanks! 😄

@olistic why don't you just call the onChange callback on updateMatches after setState?
updateMatches = () => {
  const matches = this.mediaQueryList.matches;
  this.setState(
    {
      matches
    },
    this.props.onQueryStateChange ? this.props.onQueryStateChange() : null
  );
}

@mjackson just made your suggested changes and I'm happy with the final result. The onChange callback now receives the matches result directly instead of an instance of MediaQueryListEvent. Much cleaner!

This LGTM, I went ahead and merged it in!
@mjackson let me know if you want some stuff tweaked afterwards.


"[Ext.TaskDefinitionError]: The value of 'ngrokArgs' is invalid for the task of type 'teamsfx'"

Hello.
I'm attempting to run this app: https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/hello-world-bot-with-tab by following its README.
When running Debug (Edge) I see the error message "[Ext.TaskDefinitionError]: The value of 'ngrokArgs' is invalid for the task of type 'teamsfx'"
I have env/.env.local BOT_DOMAIN set to xxxxx.ngrok-free.app and BOT_ENDPOINT set to https://xxxxx.ngrok-free.app (xxxx is reported to me when I run ngrok).
Also when attempting to follow the provisioning instructions in terminal I see "(✖) [Core.IncompatibleProject]: Your TeamFx CLI version is old and it doesn't support current project, please upgrade to the latest version using command below:
npm install -g @microsoft/teamsfx-cli@latest"
This is after having already run the required command "npm install -g @microsoft/teamsfx-cli@latest"
I updated VS Code TeamsFx Extension to v4.99.2023021100 using the Visix file as instructed.
How can I run this app?
Thank you.

The issue seems to be related to the 'visix' based upgrade of Teams Toolkit Extension not updating the extension to 5.0.
It was necessary to select 'Prerelease version' on the extension's  info page in VS Code.


Missing options for build-results-section extension type

I am looking into developing an extension of type ms.vss-build-web.build-results-section, and while it exists in the sample, it looks like info is missing on that here. Is there more documentation on developing this type of extension?

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

ID: 56437af3-75da-d219-5364-9b7927298ece
Version Independent ID: ca01655a-9195-cf92-14b4-77ef66053dcf
Content: Extension Points
Content Source: docs/extend/reference/targets/overview.md
Service: unspecified
Product: devops
GitHub Login: @elbatk
Microsoft Alias: elbatk

Hey @brownbl1 , I'll reach out to the product team and see if I can't snag someone who can give you info on that type of extension.

https://github.com/Microsoft/vsts-extension-samples/tree/master/build-results-enhancer

Let me know if that link helps @brownbl1 ! I'll close this out if it does :)

Thanks! Yes, that helps.


Remove icon.svg blank padding

fixed icon.svg logo file by eliminating blank padding.

Thanks for the quick fix 👍
(Changed the PR and commit title to be a bit more descriptive in the history)


 in Admin.js problem

<Provider> does not support changing store on the fly. It is most likely that you see this error because you updated to Redux 2.x and React Redux 2.x which no longer hot reload reducers automatically.
I think this error is due to <Provider store={store}> in Admin.js
I am also getting this warning:
You cannot change <Router history>
Environment

Admin-on-rest version: 1.3.2
Last version that did not exhibit the issue (if applicable):
React version: 16.0.0
Browser: Google Chrome 62.0
Stack trace (in case of a JS error):
gg.log

React 16.0 isn't supported for now. Also, please respect the issue template, we can't determine if the error is on your side or on aor's side with so few details.


Support Python sdist packages

What
Add support to our Python config to support source distribution (sdist) builds.
Why
This follows on from our addition of support for binary wheels in #630. Publishing an sdist rounds out our PyPI distribution, so that e.g. pip install openassetio --no-binary :all:. can work (provided build dependencies are available).
See https://github.com/OpenAssetIO/OpenAssetIO/pull/663#pullrequestreview-1148420512 regarding use of a MANIFEST.in and similarly https://github.com/OpenAssetIO/OpenAssetIO/pull/663#discussion_r1000878295 for a discussion of an alternative using setuptools_scm

We should definitely factor this in when finalizing #655, and save actually doing it until that is done.

We should make sure there is an option (on by default?) that will also install conan and cmake + deps.

We should make sure there is an option (on by default?) that will also install conan and cmake + deps.

Building from an sdist has to be a fully automatic process.
You already have most dependencies specified in https://github.com/OpenAssetIO/OpenAssetIO/blob/main/pyproject.toml#L6-L8. You just need to add conan in there and make sure conan is run from the setup.py before running cmake.


[Suggestion] Allow for more background transitions out of the box

Is your feature request related to a problem? Please describe.
During a visual novel it is common to change the background to go to a different "scene", to make those background changes feel nicer transitions are used. However in dialogic it seems that the only options are either a hard cut to the next background or a fade. It would be nice if it was possible to create your own transitions in order to create a more diverse experience while switching backgrounds. examples include:

non linear fades (like a sudden flash to white to show a heart racing event)
pattern based transitions to fit the theme of a game (for example a game with cats could have paw prints covering the original BG)
a melt fade to creep out the player
etc.

Additionally the current background fade seems to have a small issue where the background can become noticably darker during a quick fade between two almost identical BG's.
Describe the solution you'd like
I think a nice way to give power into the developer's hand would be to allow shader materials to be passed to the background event. These shader materials would have 3 parameters in common:

progress (this would be a float between 0 and 1)
previousBackground (this would be a background set by a previous background event. not always assigned, for example at the start or after a clear with backgrounds turned on)
nextBackground (this would be the background that is being assigned in the current background event)

When a background event happens, it would make use of the fade time to get the current progress. It sets the previous and next background parameters and from there the mechanism that currently handles fades between background can most likely be used to update the progress.
If a developer wants to create their own transition they can create a shader that has those parameters and even other parameters. Inside of the fragment function they can then decide how the transition should behave and they can tweak settings inside a shader material that they then pass to the background event. if no shader material is passed, it could fall back on a default shader material that does a fade like the current fade between background events.
This way the transitions become fairly plug & play and can easily be shared.
an example of how one of these transition shaders could look would be like so:
shader_type canvas_item;

uniform float progress : hint_range(0.0, 1.0);
uniform sampler2D previousBackground : source_color, hint_default_transparent;
uniform sampler2D nextBackground : source_color, hint_default_transparent;

uniform float diamondPixelSize = 10.;

void fragment() {
	float xFraction = fract(FRAGCOORD.x / diamondPixelSize);
	float yFraction = fract(FRAGCOORD.y / diamondPixelSize);

	float xDistance = abs(xFraction - 0.5);
	float yDistance = abs(yFraction - 0.5);

	bool check = xDistance + yDistance < progress;

	vec4 color = texture(screenTexture, UV) * float(!check);
	color += texture(transitionTexture, UV) * float(check);

	COLOR = color;
}

The resulting shader material would look like this

as mentioned earlier, progress, Previous Background and Next Background would be handled automatically by Dialogic's background event. But I as a developer can tweak the size of Diamond Pixel Size in the inspector until I find that it fits my needs.
After setting the Diamond Pixel Size to 50, it looks something like this

Describe alternatives you've considered
The alternative would be to create an extension module for this, but it would not have the same reach as compared to a built in feature. It could allow for people to share their transitions with each other without having to worry about different implementations that can differ in standards.
Another alternative would be to create your own scene and pass that to the background event, but this would require writing in gdscript and doesn't have the same image processing power as a shader running on a GPU.

Thanks for the issue!
I agree with the problem (it should be easy to provide different transitions, even using the same scene).
I'm not too sure about the solution though.
What we have right now
You can already achieve different transitions by creating a custom background scene and overwriting _fade_in() and _fade_out().
This means you could have a shader setup on your custom scene and tween the progress in those methods. It's not perfect though, I agree as it
A) requires setting up the custom scene (we could provide such an example though) and
B) hardly allows different transitions on the same scene.
Your solution
While shaders can create quite cool transitions, they are not very beginner friendly at all. They are also a bit limiting as they only allow image-backgrounds (which to be fair the default background does too). But custom backgrounds can be made of different (possibly animated) objects. For those you might want to use very different ways of animating/fading them.
I will think about different solutions to this a bit more.

While shaders can create quite cool transitions, they are not very beginner friendly at all. They are also a bit limiting as they only allow image-backgrounds (which to be fair the default background does too). But custom backgrounds can be made of different (possibly animated) objects. For those you might want to use very different ways of animating/fading them.

I agree that shaders are definitely not the easiest to learn and use, i do think that they can be more useful than you might expect. Scenes that have animations in them, you could probs makes use of a viewport's texture as one of the inputs. that could at least alleviate that bit of pain.
If shaders indeed become usable for background changes, i think it would be no harm in providing some out of the box materials to use, i think that it would cover a majority of the people's needs and give enough examples for those that aren't satisfied with what you can get out of the box.
I don't think they should be excluded because they are a more advanced topic, but if they are included it should definetely be in a way that makes them easy to interact with.

Another option that would handle a large set of use cases would be that instead of passing a shader material to the background event, the background event would be passed a transition texture to dictate how it will transition and a feather value to smear the transition a bit.
this would remove the complexity of having to know how to use shaders all the way down to "the whiter it is, the later it goes away" and "should it be a hard cut or should it be speared out a bit". This shader is actually not hard to make, assuming the same rules from my original proposal.
here's a rough draft of how it would look:
shader_type canvas_item;

uniform float progress : hint_range(0.0, 1.0);
uniform sampler2D previousBackground : source_color, hint_default_transparent;
uniform sampler2D nextBackground : source_color, hint_default_transparent;

uniform sampler2D whipeTexture : source_color;
uniform float feather = 0.1;

void fragment() {
	vec4 prevColor = texture(previousBackground, UV);
	vec4 nextColor = texture(nextBackground, UV);

	float whipeAlpha = (texture(whipeTexture, UV).r) - progress;

	float whipeBlend = smoothstep(0., feather, whipeAlpha + (feather * (1. -progress)));

	COLOR = mix(nextColor, prevColor, whipeBlend);
}

(this draft assumes a 1:1 aspect ratio for simplicity sake)
As an example, using the following grayscale image:

It would produce a transition like this:

I think this would be a good intermediate solution to add a nice bit of charm to the background transitions as the barrier of entry is quite low.
But considering the systems that are in place, what would be the best way forwards in terms of passing arguments with the
background event, considering that some people want to implement their own scene for backgrounds, they might want to implement their own solution and ignore the values passed through to the background event. As said earlier, these user made scenes have their own limitations due to them being fairly set & done with how you structure them. I don't know how feasible it would be, but if you were able to dynamically build the arguments and pass them to the custom scene, then that would be a powerful feature that allows custom made scenes to be more modular.

I forgot to mention, but this might also be useful for the clear event, as it removed the background as well, useful for when you want to transition back into the scene (for example you are in a city and are done with an exposition dump by an NPC)


marwaita-manjaro: init at 2020-08-29

Motivation for this change
Add Marwaita-manjaro, a green version for Marwaita theme for Gtk based applications.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/282


Integrating with On Prem Aviator Instances

Hi!
I have an on prem installation of Aviator. When trying to integrate with it to land PRs with the cli, I get the following error:
error: failed to queue pull request: Post "https://api.aviator.prod.build.doordash.red/graphql": tls: failed to verify certificate: x509: certificate is valid for *.prod.build.doordash.red, not api.aviator.prod.build.doordash.red

in my settings, I have the following as the apiHost -> https://api.aviator.prod.build.doordash.red
How do I fix this?

Hi!
I have an on prem installation of Aviator. When trying to integrate with it to land PRs with the cli, I get the following error:
error: failed to queue pull request: Post "https://api.aviator.prod.build.doordash.red/graphql": tls: failed to verify certificate: x509: certificate is valid for *.prod.build.doordash.red, not api.aviator.prod.build.doordash.red

in my settings, I have the following as the apiHost -> https://api.aviator.prod.build.doordash.red
How do I fix this?

I think the apiHost for self-hosted github is typically: https://<hostname>/api/v3, so in your case that should be:
https://aviator.prod.build.doordash.red/api/v3

thanks for the quick reply @jainankit
So, I changed the apiHost to https://aviator.prod.build.doordash.red/api/v3
(base) m.manek@H9JX16XVCT av % av auth status --debug
DEBU[0000] enabled debug logging                         av_version=v0.0.43
DEBU[0000] unable to load Git repo (probably not inside a repo)  error="failed to find git directory (are you running inside a Git repo?): exit status 128"
DEBU[0000] loaded config file                            config_file=/Users/m.manek/.config/av/config.yaml
DEBU[0000] loaded config file                            config_file=config.yaml
DEBU[0000] creating GraphQL client                       api_url="https://aviator.prod.build.doordash.red/api/v3/graphql"
non-200 OK status code: 404 NOT FOUND body: "Page not found"
DEBU[0000] executing GitHub API query...                 variables="map[string]interface {}(nil)"
DEBU[0000] GitHub API query succeeded                    elapsed=183.31925ms result="&struct { Viewer gh.Viewer \"graphql:\\\"viewer\\\"\" }{Viewer:gh.Viewer{Name:\"MohammedShabbar Manek\", Login:\"msmanek-dd\"}}" variables="map[string]interface {}(nil)"
Logged in to GitHub as MohammedShabbar Manek (msmanek-dd).
DEBU[0000] command exited                                duration=683.035583ms
DEBU[0000] fetched latest released version               latest=v0.0.43

Seems to 404. I think the cli automatically appends /graphql. Maybe this is a bug?

Ohh that's right, I confused the github url with aviator url. You just need your standard web url for the apiHost: https://aviator.prod.build.doordash.red

ooo awesome! this works, thank you :)


[AutoRelease] t2-billingbenefits-2022-12-12-85945(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3452
Live test success

issue link:https://github.com/Azure/sdk-release-request/issues/3452

/azp run prepare-pipelines


Downlevel TemplateStringsArray for tagged templates should be frozen

Bug Report
The TemplateStringsArray we emit for tagged templates (as well as its raw property) should be frozen when we emit to --target ES5, to match the ES2015 specification. Without this change, developers could run into issues with a spec-compliant String.dedent polyfill. This was first reported here: https://github.com/tc39/proposal-string-dedent/issues/75#issuecomment-1333011358
🔎 Search Terms
tagged template array frozen TemplateStringsArray
⏯ Playground Link
Playground link with relevant code
💻 Code
const f = (ar: TemplateStringsArray, ...args) => ar;
const x = f`a${1}b`
console.log(Object.isFrozen(x));
console.log(Object.isFrozen(x.raw));

🙁 Actual behavior
Neither the TemplateStringsArray nor its raw property are frozen.
🙂 Expected behavior
Both the TemplateStringsArray and its raw property should be frozen.

Unrelated but I really don’t like that the proposal wants to strip blank lines completely.  That feels like more than what a function called dedent should be doing.

@fatcerberus You should open an issue on that repo there if you want to discuss it; this thread isn't the right place. (Though I think you may have misread the proposal.)

Yes, I know this isn't the right place to discuss it.  That's why I said "unrelated".  It was more idle musing than anything; I don't actually have a strong enough opinion one way or the other to bother formally arguing the point.
tbh I'm more curious exactly what this function is doing under the hood that it apparently requires a frozen TemplateStringsArray.


An attempt to move a Container children causes canvas_item_editor_plugin.cpp:514 - Condition "p_list.empty()" is true

Godot version:

3.3 stable
OS/device including version:

Linux
Issue description:

When I (accidentally) try to move a Container child for example Button of a HBoxContainer I get multiple
editor/plugins/canvas_item_editor_plugin.cpp:514 -
Condition "p_list.empty()" is true. Returned: Rect2()

This clutters the Output.
Steps to reproduce:

Create a scene with a container, for example HBoxContainer
Add a child to it (for example Button)
Try to move it in Editor (using mouse)
You will get the error (see above)

Minimal reproduction project:

Also in 3.2.3 stable. Windows.


cargo install wrangler fails on Fedora 35

🐛 Bug report
Describe the bug
error: failed to run custom build command for `openssl-sys v0.9.72
Caused by:
process didn't exit successfully: /tmp/cargo-installfrgjug/release/build/openssl-sys-b87e00376dda7a4b/build-script-main (exit status: 101)
--- stdout
cargo:rustc-cfg=const_fn
cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_NO_VENDOR
X86_64_UNKNOWN_LINUX_GNU_OPENSSL_NO_VENDOR unset
cargo:rerun-if-env-changed=OPENSSL_NO_VENDOR
OPENSSL_NO_VENDOR unset
CC_x86_64-unknown-linux-gnu = None
CC_x86_64_unknown_linux_gnu = None
HOST_CC = None
CC = None
CFLAGS_x86_64-unknown-linux-gnu = None
CFLAGS_x86_64_unknown_linux_gnu = None
HOST_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("false")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
running "perl" "./Configure" "--prefix=/tmp/cargo-installfrgjug/release/build/openssl-sys-20a60254477a46dd/out/openssl-build/install" "no-dso" "no-shared" "no-ssl3" "no-unit-test" "no-comp" "no-zlib" "no-zlib-dynamic" "no-md2" "no-rc5" "no-weak-ssl-ciphers" "no-camellia" "no-idea" "no-seed" "linux-x86_64" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64"
--- stderr
Can't locate FindBin.pm in @INC (you may need to install the FindBin module) (@INC contains: /usr/local/lib64/perl5/5.34 /usr/local/share/perl5/5.34 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at ./Configure line 15.
BEGIN failed--compilation aborted at ./Configure line 15.
thread 'main' panicked at '
Error configuring OpenSSL build:
Command: "perl" "./Configure" "--prefix=/tmp/cargo-installfrgjug/release/build/openssl-sys-20a60254477a46dd/out/openssl-build/install" "no-dso" "no-shared" "no-ssl3" "no-unit-test" "no-comp" "no-zlib" "no-zlib-dynamic" "no-md2" "no-rc5" "no-weak-ssl-ciphers" "no-camellia" "no-idea" "no-seed" "linux-x86_64" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64"
Exit status: exit status: 2
  ', /home/ddowney/.cargo/registry/src/github.com-1ecc6299db9ec823/openssl-src-111.17.0+1.1.1m/src/lib.rs:479:13

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile wrangler v1.19.7, intermediate artifacts can be found at /tmp/cargo-installfrgjug
Caused by:
build failed`
Reproduce the bug
A list of steps to reproduce the bug.

Execute cargo install wrangler

Expected behavior
Install Wrangler
Environment and versions
Fill out the following information about your environment.

operating system: Fedora 35
cargo version: cargo 1.58.0 (7f08ace4f 2021-11-24)
rust version: rustc 1.58.0 (02072b482 2022-01-11)
output of perl --version:  This is perl 5, version 34, subversion 0 (v5.34.0) built for x86_64-linux-thread-multi

Resolved
The FindBin module comes packaged as part of perl-core. Unfortunately it does not appear as though perl-core  was installed by default, although the perl interpreter was.
Resolved by installing perl-core:
sudo dnf install perl-core
Which allowed wrangler to be installed using cargo:
cargo install wrangler
Suggestion
Update documentation to prompt user to ensure perl-core is installed prior to running cargo install wrangler on Linux.

Thanks for reporting this issue! Wrangler v1 is now deprecated and support is only being provided for critical updates or security concerns. As such, we are closing this issue.
New versions of Wrangler are maintained in the workers-sdk repo. If you are running into a similar issue with wrangler v2, please report it in the workers-sdk repo. For more info about wrangler v1 deprecation, please check out our blog post.


[SPARK-22418][SQL][TEST] Add test cases for NULL Handling

What changes were proposed in this pull request?
Added a test class to check NULL handling behavior.
The expected behavior is defined as the one of the most well-known databases as specified here: https://sqlite.org/nulls.html.
How was this patch tested?
Added test class

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83400/
Test FAILed.

I think that the failure is related to the lack of changes in code outside tests but I am not sure...

retest this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83402/
Test FAILed.

I think there is an infra issue. The error for the failed test job seems to me:
chmod: cannot access `target/*': No such file or directory

I am not sure what is happening...

retest this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83403/
Test FAILed.

I suspect the problem is related with dropped path in some Jenkins machines (we met this few times before). I roughly guess worker 2, 6 and 7. I reported this to Jenkins admin.

retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83406/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #83408 has started for PR 19653 at commit 60f2829.

thanks @HyukjinKwon

Thank you for taking this JIRA! Could you summarize the behavior of our Spark SQL in the PR description?

in SparkSQL, the standard SQL UNION clause is rewritten as UNION + DISTINCT

      case SqlBaseParser.UNION if all =>
        Union(left, right)
      case SqlBaseParser.UNION =>
        Distinct(Union(left, right))

We follow ANSI SQL if you rewrite it to SQL

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83418/
Test FAILed.

Our results are exactly the same as Oracle.
LGTM

retest this please

Test build #83421 has started for PR 19653 at commit 92308a4.

I checked with Postgres and we have the same results of Postgres too.

Test build #83421 has finished for PR 19653 at commit 92308a4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83421/
Test PASSed.

Thanks! Merged to master.


MUST --> SHOULD avoid providing sensitive data with events

The rule does not reflect Nakadi status quo as it requires using scopes (provided with tokens for REST API like authorization, instead of supported mechanism based on access control lists maintained as part of the event type definition.
The statement to avoid sensitive data is a recommendation, and not a must rule.

:+1:

:+1:


pkgsMusl.libvirt: fix build

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

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

1 test built:

nixosTests.libvirtd

Thank you!


Changing SEARCH_PATH in Postgres does not work intermittently

Hi,
We are using xorm with great result with Postgres. But we are seeing an issue that happens intermittently. We use non-public schema and run the following command before accessing tables:
store.Engine.Exec("SET SEARCH_PATH TO \"myschema\"")
Sometimes, this does not seem to have any effect and queries keep running against the public schema. This will happen on one computer with same code but not on other computers. Then it will sort of fix on its own. Is there something we are doing wrong? Is xorm reusing connections is some way to cause this?
Thanks.

We found out that if we roll back to v0.5.0 for xorm and core package then public schema error goes away. @lunny, can you please revert the schema connection param change and hopefully, we can start using master again.

@codefx9, I have remove all the schema code and you can test your code to confirm the issue is fixed. And you can reopen it if your issue is still not resolved.


Change Azure region to match allowed list

Tests are failing due to not allowed region.

Buildkite run
https://buildkite.com/redpanda/helm-charts/builds/578

Yes, it's not solved yet. CAPI is missconfigured, so that K8S control plane can not be created. Our new policies in Azure prevents from having publicly opened clusters.


Bump protobuf from 3.25.4 to 3.25.5

:mag: Description
Issue References 🔗

This pull request fixes #
Describe Your Solution 🔧

to fix CVE-2024-8184 reported in https://github.com/apache/kyuubi/security/dependabot/72

Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[ ] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (c6212d0) to head (a9a5740).

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6743   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         684     684
  Lines       42281   42281
  Branches     5768    5768
======================================
  Misses      42281   42281

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fuzz 5x faster

14 execs/s -> 70 execs/s
Motivation

During fuzzing we:

spend ~15% of time in parser
negligible time in desugar & dsl & local vars & namer
spend 33% in constant resolution, mostly in FuzzySearch of constants that didn't resolve(i'm thinking of disabling it in fuzz builds, but we did use to find bugs in it...)
5% finalizing symbols, 2% finalizing ancestors
6% in infer.
20% of time copying initial global state
10% of time freeing final global state


Correct output of multidimensional datasets when using parallel HDF5

This addresses #24. When writing multidimensional output datasets in parallel mode the offsets into the dataset were calculated incorrectly.
There were multiple copies of the write_dataset_nd method in hdfitems.h, one templated and one taking a void * pointer for the input data. Rather than fix them both I've made the templated version just call the void * version with the data type parameter set. This is how it already works for 1D datasets.
Still needs testing.

@jchelly am I correct to assume that when you say "still needs testing" you are performing such tests? I don't want to duplicate efforts, so if you are already on top of this we'll wait until your assessment comes back.

Yes, sorry, I'm testing it. So far I've picked a few halos and checked that I can reproduce the density profiles in the velociraptor output by reading the snapshot file in python and counting particles in spherical shells. My calculation agrees with velociraptor exactly in the few cases I've looked. I'll try to repeat that for all the halos in the snapshot.

Yes, sorry, I'm testing it

Awesome, I just wanted to confirm if I had understood correctly, that's all :). Good luck with the tests!

I believe this is working correctly. The density profiles of all halos in the run I'm using for testing agree exactly with my python code (they didn't before) and the other halo properties are not affected by these changes.

Great, thanks for fixing this! I was looking at the changes, at it took me a while to figure out that the rank parameter of write_dataset_nd is actually the number of dimensions and not the rank of the application in a different communicator.
After making sense of that, I agree the changes look correct, which is also backed up by your tests and observations.


Review algorithm

This PR:

Makes code more predictable on level separators;
(Hopefully) improves readability of the code.

Background: I noticed that there are conformance tests for the "shifted" option that are not hooked yet, I read that such option has interesting properties for comparison hence I invested some time in understanding how to implement it. In the process I went through the current code for understanding implemented algorithm and tests, resulting in this PR.

Force-pushed for amending the 3 noqa comments to be more specific.

Will open new PR shortly including this work.


Hotfix/v1.0.1: Hotfix in Deployment

Title : Hotfix in Deployment
[P.S]
- Updated the  Readme file
- Update the Architect Diagram in Readme file
- Update the user-data script for Ec2
- Update the Roadmap file
- Added the changelog file

:robot: OpenAI

Chat with 🤖 OpenAI Bot (@openai)

Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
Invite the bot into a review comment chain by tagging @openai in a reply.

Code suggestions

The bot may make code suggestions, but please review them carefully before committing since the line number ranges may be misaligned.
You can edit the comment made by the bot and manually tweak the suggestion if it is slightly off.

Ignoring further reviews

Type @openai: ignore anywhere in the PR description to ignore further reviews from the bot.

Files not summarized due to errors (21)
Failed to summarize

ROADMAP.md (nothing obtained from openai)
CHANGELOG.md (nothing obtained from openai)
README.md (nothing obtained from openai)
infrastructure/config.sh (nothing obtained from openai)
infrastructure/modules/serverless/cloudtrail.tf (nothing obtained from openai)
infrastructure/init.sh (nothing obtained from openai)
infrastructure/main.tf (nothing obtained from openai)
infrastructure/init_delete.sh (nothing obtained from openai)
infrastructure/modules/serverless/variables.tf (nothing obtained from openai)
infrastructure/modules/serverless/data.tf (nothing obtained from openai)
infrastructure/modules/xc3/cognito.tf (nothing obtained from openai)
infrastructure/modules/xc3/README.md (nothing obtained from openai)
infrastructure/modules/xc3/loadbalancer.tf (nothing obtained from openai)
infrastructure/modules/xc3/main.tf (nothing obtained from openai)
infrastructure/modules/xc3/output.tf (nothing obtained from openai)
infrastructure/modules/xc3/startup-script.sh.tpl (nothing obtained from openai)
infrastructure/terraform.test.tfvars (nothing obtained from openai)
infrastructure/output.tf (nothing obtained from openai)
infrastructure/terraform.auto.tfvars (nothing obtained from openai)
infrastructure/modules/xc3/variables.tf (nothing obtained from openai)
infrastructure/variables.tf (nothing obtained from openai)

In the recent run, only the files that changed from the base of the PR and between 33b16f740e1dff4841e641f9e4405ff8e795f7c2 and 7b2fa9d7686da303324572e056162811a7ecb90d commits were reviewed.


Remove passing context everywhere it is not needed

Currently, we pass the context to almost every function when we define an interface. Sometimes, this context is not used because the underlying functionality does not need it and will never need it.
The purpose of this ticket is to remove passing context when it is not used.
Examples:

AKV infra
AWS infra
Hashicorp infra

Actually, context.Context is really useful for metrics, tracing and passing metadata about a request, and of cours interrupting a request in the middle if the original request was stopped. It avoids doing expensive IO if we can avoid it.
Out of the 3 services, only Hashicorp vault doesn't handle context. But AKV infra currently use the context API from AKV, the AWS infra could use the context function, but doesn't. It should be updated.


Performance problem

Noticeable stuck when too many monitors are placed.
improvements:

Based on my tests, long belts has significant impact on performance. We can avoid this by only re-compute connections when structures (belts, inserters etc.) are changed. (DONE)
Update monitors in different tick to spread the load. (DONE)
Limit amount of work done in a tick, save progress and continue in another tick.

Also increases ticks between two updates, noticeably reduce lag.


Updates to bereavement benefit content

Users will no longer be eligible for certain benefits in April.
These changes need to go live 6/4.
Trello: https://trello.com/c/qpknCFll/590-content-and-links-update-for-state-pension-through-partner

Closing this PR as it has been superseded by #2991


Eliminate deprecation warnings in Python 3.7+

With this commit we upgrade Jinja2 from version 2.10.1 to 2.10.3. Prior
to that version, Jinja2 has used API that has been deprecated in Python
3.7 and thus emitted warnings.

for reference, these are the warnings we see when running make test:
=============================== warnings summary ===============================
.venv/lib/python3.8/site-packages/jinja2/utils.py:485
  /Users/daniel/Projects/rally/.venv/lib/python3.8/site-packages/jinja2/utils.py:485: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it will stop working
    from collections import MutableMapping

.venv/lib/python3.8/site-packages/jinja2/runtime.py:318
  /Users/daniel/Projects/rally/.venv/lib/python3.8/site-packages/jinja2/runtime.py:318: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it will stop working
    from collections import Mapping

-- Docs: https://docs.pytest.org/en/latest/warnings.html
======================= 694 passed, 2 warnings in 7.30s ========================


Simplify wording re: Supported Distributions + PackageCloud one-liner note

Remove verbose discussion of OpenSSL versions etc. in favour of the easier to understand "current and previous distro version".
Also add note re: PackageCloud one liner.

Thanks. Our support timeline is close to that of Debian releases so we can adopt a shorter version.


Added cryptocurrency calculator

Fixes Issue🛠

Closes #1465
Description👨💻
Added cryptocurrency calculator
Type of Change📄

[ ] Bug fix (non-breaking change which fixes a bug)
[X] New feature (non-breaking change which adds functionality)
[ ] Style (non-breaking change which improves website style or formatting)
[ ] Documentation (non-breaking change which updates or adds documentation)
[X] Responsiveness (non-breaking change which improves UI/UX on different screen sizes)

Checklist✅

[X] I am an Open Source contributor
[X] I have performed a self-review of my code
[X] My code follows the style guidelines of this project
[X] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

https://github.com/Rakesh9100/CalcDiverse/assets/133582566/cf5c9c94-c1fc-42d3-8cad-84db987c657f

@Rakesh9100 This PR is reviewed & can be merged.


ReadOnlyByteBufferBuf | ReadOnlyUnsafeDirectByteBuf get*, copy*, dupl…

…icate*, slice*  methods should be safe to be called from multiple threads.
Motivation:
Get* operations should always be safe to be used from different Threads.
Modifications:

Only use internalNioBuffer when one of the read* or write* mthods are used. This is neccessary to prevent races as those can happen when a slice or duplicate is shared between different Channels
Add unit tests

Result:
Fixes https://github.com/netty/netty/issues/14070. Related to https://github.com/netty/netty/issues/1865

PTAL @lhotari


Fix macro_rules separator parsing.

macro_rules rules are separated by ';' including an optional ';' at the end

Awesome, thanks!
bors r+


Publish-PSResource throws error on version missing

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.

Steps to reproduce
I am trying to create a Gitlab Pipeline to publish to the gitlab Repository. So I created my module with the manifest and then I tried publishing the file with the commands taken from this post:
  try {
        $null = & dotnet nuget remove source $PublishRepoSourceName
    } finally {
        & dotnet nuget add source $PublishRegistry --name $PublishRepoSourceName --username $PublishUserName --password $PublishPassword
    }

    if ($null -ne (Get-PSResourceRepository -Name $PublishRepoSourceName -ErrorAction Ignore)) {
        Unregister-PSResourceRepository -Name $PublishRepoSourceName
    }
    Register-PSResourceRepository -Name $PublishRepoSourceName -Uri $PublishRegistry -Trusted -Priority 1

    $password = ConvertTo-SecureString $PublishPassword -AsPlainText -Force
    $PublishCred = New-Object System.Management.Automation.PSCredential ($PublishUserName , $password)
    Publish-PSResource -Credential $PublishCred -Repository $PublishRepoSourceName -Path $ModuleBuildPath

My variables look like this:
$PublishRepoSourceName = "GitLab"
$PublishRegistry = "https://gitlab.example.com/api/v4/projects/10/packages/nuget/index.json"
$PublishUserName = 'username'
$PublishPassword = 'mydeploytoken'
$ModuleBuildPath = "path\to\my\module\folder"

I have done this in powershell 7.3 with these modules loaded:
ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Manifest   <IP_ADDRESS>               Microsoft.PowerShell.Management     {Add-Content, Clear-Content, Clear-Item, Clear-ItemProperty…}
Manifest   <IP_ADDRESS>               Microsoft.PowerShell.Security       {ConvertFrom-SecureString, ConvertTo-SecureString, Get-Acl, Get-AuthenticodeSignature…}
Manifest   <IP_ADDRESS>               Microsoft.PowerShell.Utility        {Add-Member, Add-Type, Clear-Variable, Compare-Object…}
Manifest   <IP_ADDRESS>               Microsoft.WSMan.Management          {Connect-WSMan, Disable-WSManCredSSP, Disconnect-WSMan, Enable-WSManCredSSP…}
Binary     3.0.16     beta16     PowerShellGet                       {Find-PSResource, Get-PSResource, Get-PSResourceRepository, Install-PSResource…}
Script     2.2.6                 PSReadLine                          {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove-PSReadLineKeyHandler, Set-PSReadLineKeyHandler…}

I tried it in Visual Studio Code and in windows-terminal with admin-priviledges running powershell 7.3
In order to determine the missin "version
Expected behavior
I expected the module to upload the files to my registry.

Actual behavior
It is throwing the error, saying, that "version" is missing:
Publish-PSResource: Unexpectd error packing into .nupkg: 'The required element 'version' is missing from the manifest.'.

In Order to find out whats missing I uncommented the line for
  - PowerShellVersion
  - PowerShellHostVersion
  - DotNetFrameworkVersion
  - CLRVersion

But stil the error stays the same. What did I do wrong?

Error details
Exception             :
    Type    : System.ArgumentException
    Message : Unexpectd error packing into .nupkg: 'The required element 'version' is missing from the manifest.'.
    HResult : -2147024809
CategoryInfo          : NotSpecified: (:) [Publish-PSResource], ArgumentException
FullyQualifiedErrorId : ErrorPackingIntoNupkg,Microsoft.PowerShell.PowerShellGet.Cmdlets.PublishPSResource
InvocationInfo        :
    MyCommand        : Publish-PSResource
    ScriptLineNumber : 1
    OffsetInLine     : 1
    HistoryId        : 21
    Line             : Publish-PSResource -Credential $PublishCred -Repository $PublishRepoSourceName -Path $ModuleBuildPath
    PositionMessage  : At line:1 char:1
                       + Publish-PSResource -Credential $PublishCred -Repository $PublishRepoS …
                       + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    InvocationName   : Publish-PSResource
    CommandOrigin    : Internal
ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo :

Environment data
the manifest file looks like this:

@{

# Script module or binary module file associated with this manifest.
RootModule = 'mpsActiveDirectory.psm1'

# Version Number
ModuleVersion = '0.1.216'

# Supported PSEditions
#CompatiblePSEditions = @()

# Unique Module ID
GUID = 'xxxx-xxxx-xxxxx-xxxx'

# Author of this module
Author = 'my name'

# Company or vendor of this module
CompanyName = 'my name'

# Copyright statement for this module
Copyright = '(c) 2022 my name. All rights reserved.'

# Description of the functionality provided by this module
Description = 'Tools to Manage the ActiveDirectory'

# Minimum version of the PowerShell engine required by this module
PowerShellVersion = '5.0'

# Name of the PowerShell host required by this module
#PowerShellHostName = ''

# Minimum version of the PowerShell host required by this module
PowerShellHostVersion = '5.0'

# Minimum version of Microsoft .NET Framework required by this module. This prerequisite is valid for the PowerShell Desktop edition only.
DotNetFrameworkVersion = '5.0'

# Minimum version of the common language runtime (CLR) required by this module. This prerequisite is valid for the PowerShell Desktop edition only.
CLRVersion = '5.0'

# Processor architecture (None, X86, Amd64) required by this module
#ProcessorArchitecture = ''

# Modules that must be imported into the global environment prior to importing this module
# RequiredModules = @("ImportExcel")

# Assemblies that must be loaded prior to importing this module
#RequiredAssemblies = @()

# Script files (.ps1) that are run in the caller's environment prior to importing this module.
#ScriptsToProcess = @()

# Type files (.ps1xml) to be loaded when importing this module
#TypesToProcess = @()

# Format files (.ps1xml) to be loaded when importing this module
# FormatsToProcess = @()

# Modules to import as nested modules of the module specified in RootModule/ModuleToProcess
#NestedModules = @()

# Functions to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no functions to export.
FunctionsToExport = @('Export-FolderPermissionMatrix','Get-FolderPermissionMatrix','Get-FolderPermissionReport','Get-UserAccessReport','Get-UserGroupMatrix','Set-FolderPermissionMatrix')

# Cmdlets to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no cmdlets to export.
#CmdletsToExport = '*'

# Variables to export from this module
#VariablesToExport = '*'

# Aliases to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no aliases to export.
#AliasesToExport = '*'

# DSC resources to export from this module
# DscResourcesToExport = @()

# List of all modules packaged with this module
# ModuleList = @()

# List of all files packaged with this module
# FileList = @()

# Private data that needs to be passed to this module
PrivateData = @{

    PSData = @{

        # Tags applied to this module. These help with module discovery in online galleries.
        Tags = @('Windows','PSEdition_Desktop','PSEdition_Core')

        # A URL to the license for this module.
        # LicenseUri = ''

        # A URL to the main website for this project.
        # ProjectUri = ''

        # A URL to an icon representing this module.
        # IconUri = ''

        # ReleaseNotes of this module
        # ReleaseNotes = ''

        # Flag to indicate whether the module requires explicit user acceptance for install/update/save
        # RequireLicenseAcceptance = $true

        # External dependent modules of this module
        ExternalModuleDependencies = @('ActiveDirectory')

        # Prerelease Tag
        Prerelease = ''

    } # End of PSData hashtable

} # End of PrivateData hashtable

# HelpInfo URI of this module
# HelpInfoURI = ''

# Default Command Prefix
DefaultCommandPrefix = 'mps'
}

Visuals
No response

We triaged this issue, and will look into resolving this issue soon.

While you're at it, can you fix the missing e in "Unexpectd"?


Update JsonFromTokenUri with api transporter to being able to handle retrieble error codes [429, 408, 500, 502, 503, 504]

Merge when ready (I see you are still force-pushing, so didn't merge)


Fix projection when xlim/ylim provided

This closes #951, #370, and #529 ~but I only have the test for #529 so far.~
Here are the examples from #951. They all run with no errors
import hvplot.pandas  # noqa
import cartopy.crs as ccrs

from bokeh.sampledata.airport_routes import airports

# Case 1: This example works
airports.hvplot.points('Longitude', 'Latitude', geo=True, color='red', alpha=0.2,
                       xlim=(-180, -30), ylim=(0, 72), tiles='ESRI')

# Case 2: xlim/ylim are not obeyed when the map tile is removed
airports.hvplot.points('Longitude', 'Latitude', geo=True, color='red', alpha=0.2,
                       xlim=(-180, -30), ylim=(0, 72))

# Case 3: Setting ymin > 0 raises errors
# Change ymin from 0 to 10
airports.hvplot.points('Longitude', 'Latitude', geo=True, color='red', alpha=0.2,
                       xlim=(-180, -30), ylim=(10, 72))

# Case 4: Setting ymax < 0 also raises errors
airports.hvplot.points('Longitude', 'Latitude', geo=True, color='red', alpha=0.2,
                       xlim=(-180, -30), ylim=(-20, -5))

# Works if geo=False
airports.hvplot.points('Longitude', 'Latitude', geo=False, color='red', alpha=0.2,
                       xlim=(-180, -30), ylim=(10, 72))

Here is the example from #370  which now works:
import xarray as xr
import hvplot.xarray

dz = xr.tutorial.open_dataset('air_temperature')
dz.hvplot('lon', 'lat', coastline=True).opts(ylim=(20, 30))

Originally I thought this resolved #738, but then I realized that it just made that one less likely to occur since I was encountering it because the xlim and ylim I was providing were not being projected so they were outside the valid bounds of the crs.

This is good to go from my perspective

Looks good to me too, thanks @jsignell !


Python File I/O

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #579

Type of change 📝

[x] Audio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)

Domain of Contribution 📊

[x] Python_Domain

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Do not make a PR to the main repo. It should be from your Python branch to the org's Python Branch

@mridu-pant kindly pull in python branch to python branch! You can ping me in discord if u have doubt on this


Fix broken links in Getting Started

While attempting to browse the docs, I noticed some links were outdated/broken. This PR fixes some of the links on the Getting Started page.
Also, I reworded the Linux Configuration section slightly, and made minor edits elsewhere on the page, in an effort to make the documentation a little clearer.

Hello!
LGTM, thanks!
And sorry for not reviewing this PR earlier 😓


Ability to spawn multiple debuggers with automatic port assignment

Godot 3.0.4
I would like to make a game prototype where X clients can join a game hosted by 1 server.
In order to fully debug this, I need to run at least 2 clients and 1 server with the Godot debugger. For the sake of simplicity, I intend to run one client with 1 editor, and all other processes with the command line debugger (so I could even spawn them from the editor automatically when I hit Play with some custom plugin).
Problem:
The debugger port Godot uses is a global editor setting. This can be handy if you know exactly which game you want to debug, but that also means two debuggers launched on two instances of the same project will conflict.
There is a way to specify the port with the command line debugger, but I think it would just be easier to let Godot pick an available port automatically, when not specified.
In fact, even after trying, the command line option also doesn't work, probably because it's not actually what I think it is (then there is no such parameter as described in this issue):
> ../../../bin/Godot_v3.0.4-stable_win64.exe main_server.tscn -d --remote-
debug <IP_ADDRESS>:6008
Remote Debugger: Connection failed with status: '1', retrying in 1 msec.
Remote Debugger: Connection failed with status: '1', retrying in 10 msec.
Remote Debugger: Connection failed with status: '1', retrying in 100 msec.
Remote Debugger: Connection failed with status: '3', retrying in 1000 msec.
Remote Debugger: Connection failed with status: '3', retrying in 1000 msec.
Remote Debugger: Connection failed with status: '3', retrying in 1000 msec.
Remote Debugger: Unable to connect

Note:
It can also help implement the ability to spawn multiple game instances from 1 editor and have multiple debugger tabs, though I don't need this at the moment.

#3696

Duplicate of #3696, but since this one has a more detailed proposal of how it could be implemented, I'll close the older one.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


New features and bugfixes

Change log

Ability to quickly find suspicious actions likely to be exploitations
Fix missing locale in characters
Add banned at timestamp to dashboard
Better sidebar

@ExpDev07 can you merge it when you find the time :)

@ExpDev07 btw, if you don't want to always merge my changes you can add me as a collaborator with the access level "Write" more


Service Endpoint Registration - Error using Reset method if no existing endpoints

In ServiceEndpointRegistration.ps1 it is possible to use the RegistrationType "Upsert" in order to create/update service endpoint registrations.
However, if using RegistrationType "Reset", the initial deletion of the service endpoints fails if no endpoint with specified guid exists in the environment.
It should, however, just check if it exists first and if it does not, skip deletion stage.

@bo-stig-christensen did you try to use upsert?

@WaelHamze As I mentioned in the first paragraph, it works fine with Upsert :-)


Battery replacement percentage does not change cost

Triggering a battery replacement in the "Replace at specified schedule" option triggers 100% of the battery replacement cost, regardless of the percentage specified in "Battery bank replacement percent." In the attached SAM file, both cases see the same expenses, but "replace 100%" gets a larger capacity boost.
Cost should be based on % replacement.
battery_replacement_bug.zip

Additional decisions made during the SAM meeting:

Remove the replacement schedule table - replacements must be specified in the % schedule
@cpaulgilman will need to make these adjustments in the version upgrade script, and was considering adding help messages if the user specifies a replacement cost schedule (costs need to be specified in replacement years)

@cpaulgilman and @dguittet - I started ripping out some of the replacement code, and realized that a feature of the replacement schedule input was to allow multiple replacements per year. For example, if the user specified "2" then this code in battery_t::runReplacement would schedule a replacement in the middle of the year:

Is that a feature we want to maintain? If so, is there a not-confusing way to get it in the percent input, or do we need two inputs?

I can't think of a reason to have more than 1 replacement in a single year.
As an aside, I think there was originally some consideration about battery augmentation (increasing capacity for increased future load) but that could be covered by a percent > 100%.


In the AgriDataModels for Relationships reference the EntityIdentifier

such as in https://github.com/FIWARE/dataModels/blob/master/specs/WasteManagement/WasteContainer/schema.json#L127
instead of saying just "type": "uri"
(be careful not all "type": "uri" will have to be changed, only those that point to other Entities ...
Thanks!

fixed


Unable to connect to remote IPython kernel on Linux from Windows

Description
I'm trying to connect to remote IPython kernel
What steps will reproduce the problem?
Used this guide https://github.com/ipython/ipython/wiki/Cookbook:-Connecting-to-a-remote-kernel-via-ssh

Launched ipython kernel on server (Ubuntu 16.04 LTS)
Downloaded kernel-29941.json
Tried to use "Connect to an existing kernel" spyder feature
Checked "This is remote kernel"
Selected kernel file
Pasted some IP address 52.59.__.__
Selected key file ~/.ssh/ipython.pem

What is the expected output? What do you see instead?
Got "Unable to connect to IPython kernel-29941.json"
I've tried console command:
ipython qtconsole --existing ~/Downloads/kernel-29941.json --ssh 52.59.__.__ - it works
I've also check if the key is ok:
ssh -i ~/.ssh/ipython.pem 52.59.__.__
Please provide any additional information below
Version and main components

Spyder Version: 3.0.0b4
Python Version: 2.7.12
Qt Versions: 4.8.7, PyQt4 (API v2) 4.11.4 on Darwin
Mac OS

Dependencies
pyflakes >=0.5.0 :  1.2.3 (OK)
pep8 >=0.6       :  1.7.0 (OK)
pygments >=2.0   :  2.1.3 (OK)
qtconsole >=4.2.0:  4.2.1 (OK)
nbconvert >=4.0  :  4.2.0 (OK)
pandas >=0.13.1  :  0.18.1 (OK)
numpy >=1.7      :  1.11.1 (OK)
sphinx >=0.6.6   :  1.4.5 (OK)
rope >=0.9.4     :  0.10.3 (OK)
jedi >=0.8.1     :  0.9.0 (OK)
psutil >=0.3     :  4.3.0 (OK)
matplotlib >=1.0 :  1.5.1 (OK)
sympy >=0.7.3    :  1.0 (OK)

"Unable to connect to IPython kernel" pops up instantly, it seems it didn't even try to connect

I have the same problem

The problem is in checking connection file function, to make it work you need to copy connection file to your local jupyter --runtime-dir

@azenin
Hey Azenin, sorry if this a really obvious answer - where did you get ipython.pem file from? Is that a key you've made yourself?
I'm trying to connect to my remote kernel on my Linux server (RHEL) from Spyder on Windows - and it's failing.

@robromanowski yes, you can use ssh-keygen -t rsa to generate your own private/public key pair

@azenin Thanks for the quick response!
That command seems like a great lead. I just ran it, and it seems it made a .pub (instead of .pem) will that work? Or  I do need it to be a .pem

@robromanowski try .pub, if it will not work just rename it

Was gonna try the rename, didn't think it'd be that simple :)
Also, I guess I jumped ahead - I'm having issues finding it.
After i ran ssh-keygen -t rsa
It prompted me Generating public/private rsa key pair. Enter file in which to save the key (/export/home/rr83008/.ssh/id_rsa): ipython (name i used) Enter passphrase (empty for no passphrase):
And then
Enter same passphrase again: Your identification has been saved in ipython. Your public key has been saved in ipython.pub.
Maybe I misunderstand the prompt? I though the location in () the home/username/,ssh/id_rsa was where it was saving it? And I was naming it ipthon? Was I supposed to put a a path there instead of a name?
After it saved I navigated to ~/.ssh, and I don't see the id_rsa directory. Wouldnt it be at id_rsa/KEYNAME.pub?

@azenin Okay, have taken care of the .pub/.pem issue. I have FTP'd it over to my local Win machine.
I go into Spyder, try to connect now (and using the .pub or renaming it to .pem) neither work. i get the same error you do - immediately.
Although your other comment seems to have solved it with the  --runtime-dir command? Thats where my json is by default? when I do ipython kernel and it gives me kernel-#####.json I previously went to that location and FTP'ed the matching number down. I am using that json file in "connect to remore kernel" and the .pub/.pem file I also ftp'd down to my windows machine.

you need to copy kernel-#####.json file from remote machine to dir that outputs jupyter --runtime-dir command on your local machine
and then you can simply type kernel-##### in spyder menu without any need to locate it

@azenin Okay, well I was referring to my file was being saved into the -runtime-dir directory on my remote Linux machine...but for my local machine I don't have Juptyer, and besides Spyder lets you navigate to the .json file so would location matter? I get you can type in the exact name without browsing to the file - but wouldnt browsing also work?
Maybe what I'm trying to do won't work.
I have Spyder on my windows machine. I have remote linux machine I have Jupyter working, and I want to be able to use Windows (so the you have a non-laggy GUI, but have it connect to the remote Linux machine so we are in that workspace).

@ccordoba12 Thanks for the merge!
I did see Paramiko mentioned in one of the many threads I went through.
Anywhere I can read up on what I need to do with it/set it up?

It should work automatically. Have you tried it already?

I did, but most likely user error on my part. I don't think I fully understand what steps need to be done on Windows vs. Linux.
Paramiko is something I need to run on the Windows side? ( I can set it up with Anaconda?)
I'm trying to make a list of what I need to do on each side:
Linux (on my VM):

Find the juptyer --runtime dir
Run the ipython kernel
Know the location of it so I can FTP over to windows

Windows:

FTP into the machine, pull off the kernel.json file that matches
Open Spyder:

use that json
use this connection "rob@lab2073" @host
attach my .pub (or I can rename it to .pem) ssh that @azenin mentioned above
no password for SSH phrase, since I Set it up with no password

When I do that, and try to connect to the linux remote kernel, I get "unable to connect to kernel#####.json
At what point do I do the Paramiko stuff?

Facing the same issue. Mine says unable to open paramiko. I have paramiko installed on both machines

@anuragsodhi potential solution:
I installed paramiko, checked that it imports in spyder. So i checked versions of IPython on Windows and Linux and they were different:
On Windows 7: python 3.6.1, IPython 5.3.0, Spyder 3.1.4
On Linux: python 3.5.2, IPython 6.2.1
I updated Windows IPython from 5.3.0 to 6.2.1 and spyder remote connection worked! Python versions are still different.

Hello, I have a similar issue, and I have some questions...  I'm trying to configure ipython kernel server on a remote VM Instance in Google Cloud,
Is it necessary to open the port that use the kernel to connect with the client? If yes, How can I configure the port to avoid that these were randomly configured?
I have tried to connect several times from Spyder on Windows10 (client) with an SSH key, but I don't get any answers. When I have launched ipthon kernel on the server-side I have assigned the public IP.
Thanks,

Also having this issue, I get an error like so:
"Could not open ssh tunnel. The error was:
q must be exactly 160, 224, or 256 bits long"


Adding windows support for surfer-mcp server

Currently the surfer-mcp server only works on Mac. However, there are errors when doing this on Windows. A solution could be rebuilding the server in typescript and maybe that will work on windows.

× Failed to build chroma-hnswlib==0.7.6 ├─▶ The build backend returned an error
╰─▶ Call to setuptools.build_meta.build_wheel failed (exit code: 1) [stdout] running bdist_wheel running build running build_ext building 'hnswlib' extension [stderr] error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ hint: This usually indicates a problem with the package or the build environment. help: chroma-hnswlib (v0.7.6) was included because surfer-mcp (v0.1.0) depends on chromadb (v0.5.23) which depends on chroma-hnswlib
more info on the error ^^. I've installed build tools but it still doesn't work


Task name is mising in logs

According to documentation, task name should be visible in the output. https://microsoft.github.io/just/docs/logging
const { task, tscTask, parallel } = require("just-scripts");
const { exec } = require("just-scripts-utils");

task("hello", async() => {
  return exec("echo 'hello'", {
    stderr: process.stderr,
    stdout: process.stdout
  });
});

task("build", tscTask({build: true, watch: true}));
task("start", parallel("build", "hello"));

When running npx just start
13:47:26] ■ started 'start'
[13:47:26] ■ started 'build'
[13:47:26] ■ started 'hello'
[13:47:26] ■ Running /home/raziel/EmailProject/node_modules/typescript/lib/tsc.js with /home/raziel/EmailProject/tsconfig.json
[13:47:26] ■ Executing: "/home/raziel/.nodenv/versions/12.16.0/bin/node" "/home/raziel/EmailProject/node_modules/typescript/lib/tsc.js" --build "/home/raziel/EmailProject/tsconfig.json" --watch
hello
[13:47:26] ■ finished 'hello' in 0.04s

For my use case,  name of the task in output is the most important feature.

Not really. Either docs are wrong or there is a bug. It does not matter for me as I implemented limited version of just for myself.

Reopened, sorry. I think the documentation is out of date--I haven't seen output like that recently. @kenotron what do you think--was this a feature you had at some point but removed?


Auto-filter deleted documents on search for native engines

Description
Recently, we added a lot of filtering capabilities for faiss so that users can pass filters to hnsw, ivf, ivfpq, etc. When searching a segment, we should automatically add deleted documents to this filter, so that faiss can skip these as well instead of returning results and getting filtered out after. Currently, lucene implements this behavior for HNSW: https://github.com/apache/lucene/blob/main/lucene/core/src/java/org/apache/lucene/codecs/lucene99/Lucene99HnswVectorsReader.java#L236-L238. There was some discussion around this in #1003

Thanks @jmazanec15 for opening up this issue. I was going to open this issue. I think we should definitely implement a deleted documents filtering capability for Faiss.
But before we implement we should optimize the filtering in general for k-NN. I am working on detailing all the different optimization that is required to be done in filtering. Once we have those optimizations in place we should implement this feature.

Moving to 2.15. I dont think we are going to get in 2.14

Moving to 2.16.


fix an example CLI use in Readme

This fixes the short flags example in the "Ignore files/patterns" section of the Readme, and corrects some minor typos/punctuation in the Readme. (#649)
DCO 1.1 Signed-off-by: Alexander Quine<EMAIL_ADDRESS>

Hey @alxndr would you mind hitting the update branch button above below, Just need it to update so we can merge it in once the tests pass.

@DanPurdy done

Coverage remained the same at 96.993% when pulling 46d39fdefaee50ab0c490c93354a7933f8961ee9 on alxndr:doc-tweak into f0703bbcbe6497d8beab2b9cd8b3d462f7d109f7 on sasstools:develop.

Thanks for the PR 👍


Add Americas High School

Long Term IT course:
https://www.sisd.net/Page/61718
Domain proof:
https://my.sisd.net/

@jc-the-github Pull request merged. Thank you!


Use withDecay for UILargeTitleHeader animations that has velocity

For now it looks unnatural, when one scrolls a ScrollView and then it ends somewhere in between of large title. After one release a finger we trying to adjust a position to proper place, but do not take a current velocity into account. Decay animation seems to fit better in such situation. Take a look into https://github.com/software-mansion/react-native-reanimated/blob/master/docs/docs/api/withDecay.md .

Was done in https://github.com/tonlabs/UIKit/pull/1243


[Feature request] Support pg_pass

It's quite recommended to store password outside the ~/.pg_service.conf but in a ~/.pgpass file.
It could be really helpful to resolve the password from this complementary file when it does exist.
Relevant docs:

https://qwat.github.io/docs/fr/installation-guide/workstation.html#database-configuration
https://www.postgresql.org/docs/current/libpq-envars.html

@Guts we don't have a need to support this at the moment, but any contribution is very welcome :)

Just for making the point, I wouldn't say storing a pw in clear text is ever "recommended". Pgpass support would still be very welcome


Add results for symmetry projected RBM and Lanczos

Reference of the data: https://proceedings.neurips.cc/paper_files/paper/2022/hash/3173c427cb4ed2d5eaab029c17f221ae-Abstract-Conference.html

hi, thank you for your pull request, at the moment we are not yet opening the repository for additional contributions, but we plan to do so in the near future. we will keep you updated with the details!


erlang 20.2.2

The first time I make this pr, the travis ci build failed.
So I make second commit with this msg.
If you don't like the commit msg, I will change it.

not a big deal for the commit msg; actually I want to thank you for every new release you beat me! look at the past record for contributors graph, you have made a lot since beginning of this project

I am thinking if someone can resolve #38 and this project can be put somewhere under @erlang and if I can be co-maintainer I would like invite the top and active contributors as co-maintiners as well /cc @tsloughter @ypaq for any progress?

I'll try pinging some people again today about this.


Plugin incompatible with Android Studio(base on Intellij 2020.3.1)

When kotest-extensions-robolectric is used in the unit test, then use the @RobolectricTest annotation in the unit test:
@RobolectricTest
class RobolectricTest: FunSpec({
    context("test kotest robolectric plugin") {
        test("nested test") {
            1 + 1 shouldBe 2
        }
    }
})

If you start to run the context function from the run icon provided by kotest-intellij-plugin:

kotest-intellij-plugin automatically uses kotest run configuration:

The result will be a test failure (Test passed 0), and the test name will not be displayed in the test report:

However, if the unit test is run from the run icon at the class name, it is successful:

Android Studio automatically uses gradle run configuration:

The test results are also normal:

Therefore, I think that kotest-intellij-plugin may not have good compatibility with Android Studio.
My Context:
Android Studio：2020.3.1 for Mac：

testImplementation("io.kotest:kotest-runner-junit5-jvm:4.6.3")
testImplementation("io.kotest:kotest-assertions-core-jvm:4.6.3")
testImplementation("io.kotest.extensions:kotest-extensions-robolectric:0.4.0")
testImplementation("org.jetbrains.kotlin:kotlin-reflect:1.5.10")
testImplementation("org.robolectric:robolectric:4.6.1")

I've noticed that on IJ on mac in the last few days actually. Can you try editing the all test run configuration to include --tests "*" and see if that helps short term? I noticed that was the difference between using the gutter icon and the main Gradle test target

I've noticed that on IJ on mac in the last few days actually. Can you try editing the all test run configuration to include --tests "*" and see if that helps short term? I noticed that was the difference between using the gutter icon and the main Gradle test target

The problem now is that when I start the unit test from the context function, Android Studio will automatically use "kotest run configurations". And in its configuration window:

I tried adding the --tests "*" parameter to the three input boxes of "VM options", "Program arguments" and "Environment variables", but none of them worked, and the unit test would still fail or even report an error.
It doesn't make sense to set --test "*" in Gradle run configurations, because gradle test can already run successfully.

Oh I see, I guess there are two issues here then 🤔 I'll open one for mine

The problem is still there with 1.1.49-IC-2020.3 in Android Studio:


Add option to choose between Roles and ClusterRoles (restrict cluster creation to tinkerbell namespace)

This is related to pull-request #117.
I agree that users should be able to create clusters outside of the tinkerbell namespace. However, I believe they should also have the option to control access to the entire cluster, as unrestricted access shouldn't be the default or only option.
Currently, Rufio's Helm chart creates a ClusterRole that grants read access to all cluster secrets. While this might be acceptable if the cluster is dedicated solely to running Tinkerbell, it poses a security risk in a production environment where other workloads may be running. Specifically, allowing Rufio to read secrets from all namespaces can be a significant security concern, which some users may find unacceptable.
Expected Behaviour
Users should have the ability to choose whether the Tinkerbell stack has access to multiple namespaces, enabling the creation of Cluster API clusters in namespaces other than tinkerbell.
Current Behaviour
By default, Rufio has access to all secrets across all namespaces, with no option to change/disable this.
Possible Solution
Introduce an option that allows users to decide whether to grant Rufio access to all namespaces or restrict it to the tinkerbell namespace. If possible, also provide the ability for users to specify which namespaces the Tinkerbell stack should have access to (instead of the entire cluster).

Would the ability to disable parts/all RBAC in some fashion so you can craft your own be acceptable?

That would already be better than the current behavior, yes.


Forefox version

Description
Wanted Firefox version!
Use Case
I am using Firefox as a developer.
Proposed Solution
Port it for Firefox addon.
Other information
No response
Acknowledge

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

@takkyun Thank you for reporting issue! Now firefox version is available.
https://addons.mozilla.org/en-US/firefox/addon/aws-peacock-management-console/

@takkyun Thank you for reporting issue! Now firefox version is available.
https://addons.mozilla.org/en-US/firefox/addon/aws-peacock-management-console/


Updated search input

Notes for Reviewers
This PR fixes #7106
before :

after :

Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit 5ee5d9501d60b854483e5f05d8a665f857a6de47 at: https://63ef4dc5aa408852451c7226--meshery-docs-preview.netlify.app

@VIKAS0264 The search icon that was right next to the search bar is now below the search bar, could you please fix that?

These are my suggestions:

There may be no need for that search button outside the search bar as we are also including the icon inside the bar or we can remove the icon inside the bar and have a separate button.
the length of the search is full of the width of the container which can be reduced.
we can have something like a clear or cross to empty the search bar if someone typed incorrectly.

i have gone through your suggestions @ritiksaxena124 @swagataroy30 @deepakdinesh1123 i will work on it and create a new pr.

@VIKAS0264 Don't create a new PR just add a commit to this one

🚀 Preview for commit 697e5bb8afbe934429cec91ecca1f47dbbb01d23 at: https://63f3622cc155444a8ae60228--meshery-docs-preview.netlify.app

styles of the search input are changed

search input from the search page was not fetching results missing form tags were added to fetch results

🚀 Preview for commit 7e3eea0b6afa4332ebdeb7eb4dcb459d63f6b3bc at: https://63f4494a37dfa102e357f887--meshery-docs-preview.netlify.app

@ritiksaxena124 @VIKAS0264 what do you guys think about the idea of populating the search field with the search query? It kinda feels odd to see that disappear every time. And then the showing results line can be moved down.

@ritiksaxena124 @VIKAS0264 what do you guys think about the idea of populating the search field with the search query? It kinda feels odd to see that disappear every time. And then the showing results line can be moved down.

yeah it can be populated just by removing autcomplete off i can add a new commit and make it populate

@VIKAS0264  Let's discuss this on the Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

Lots of activity here. Great.
Good of you to see this one through, @VIKAS0264 👍

Lots of activity here. Great.
Good of you to see this one through, @VIKAS0264 👍

Thank you @leecalcote

🚀 Preview for commit 44d30d7c6f4bc60a54f2ddb525a4010dc6543790 at: https://63f8509014c05e4d6c1d7b81--meshery-docs-preview.netlify.app

hey @deepakdinesh1123 @ritiksaxena124 @Chadha93 @leecalcote I've updated the search input according to your suggestions.
In these new commits

search input in the main field will be populated with query string
styles to search input is modified
search input now fetches results which was not working previously

Hey @VIKAS0264 slight change, It would be great if you can put some spacing between the search bar and the showing results, the second change is the font style of text inside the search bar doesn't resembles the font style of the page

Hey @ritiksaxena124 I've added margin checkout the latest preview i will work on Changing the font

It seems like the color here are changed @VIKAS0264. Please look into this, this change is not wanted.

Hey @asubedy thank you for highlighting first of all the main.css link was not linked to head, but styles to this search input were written in main.css i thought of including it's overriding other pages styles also. I guess i need some help moving forward with this issue @deepakdinesh1123 @ritiksaxena124


Huboard

Any problems with me setting up this GitVersion repo to use Huboard?

TBH I didn't get too much out of it. Gonna close this.
I think these things are not so good for open source as it raises the barrier to entry. I quite liked it for internal projects where you can everyone using the same tools


questions about Oauth2 support for domain federation

i had a customer who is asking the following questions:

if we have any future plan to support integrate Azure AD with 3rd-party federation servers via openidconnect/oauth2. The current powershell cmdlet Set-MsolDomainFederationSettings has a parameter -OpenIdConnectDiscoveryEndpoint, does it mean we are already doing something to support openidconnect/oauth2 for AAD federation?
Currently to support hybrid AAD joined device, the federation server need to support WS-Trust, do we have any plan to switch to other auth method such as SAML/Oauth2?

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

ID: e45e65a0-74ae-440c-0064-2a0b1c6bb0d9
Version Independent ID: a50f705d-ab3f-ca2b-aedd-9ab37bea3d3f
Content: Azure AD Connect: Use a SAML 2.0 Identity Provider for Single Sign On - Azure
Content Source: articles/active-directory/hybrid/how-to-connect-fed-saml-idp.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@SeanXuMSFT Thank you for your feedback . We will investigate and update the thread.

@SeanXuMSFT We have reached out to the product group and we will update once we have a clarification.

@SeanXuMSFT No there are no plans to support OpenIdconnect/Oauth2 as federation protocol. Also there is no near term plan to support SAM/oAuth for AAD join and/or Hybrid join scenarios . This will continue to be WS-Fed only . Alternatively , you can go without federation and use Password hash sync.
Hope this clarifies your query. WE will now close this issue. Should you have any further queries feel free to tag me to your reply and I will be happy to help . Alternatively you can always open a new issue


added some formatting changes to make help more consistent

I ran into this library, and this it's very useful! Below are some minor changes to the help formatting to make it look a little more consistent. What do you think?

Hi @rbonthond Thanks a lot! I have been busy of late. I will have a look at it and get back to you ASAP!


books category with additional items

Moved references mentioned in the page's beginning into a new category called Books. Also, added new books into it

Thanks for sharing!