Add Rodentia

About the PR

Adds the Rodentia, a species of rat/mouse/squirrel/bat/hamster/rabbit/beaver/possum-like humanoids. As seen on Delta-V, Goob, Cosmatic Drift, and others.
Credit goes to @portfiend for initially developing the Rodentia for DeltaV.
Why / Balance

We got dogs, cats. Why not rats? Many marines have been eager for this PR.
Balance: Rodentia on other servers are quite small. I'd initially wanted to split the difference and make these dwarf-proportioned, and I still don't think that would be an issue. As far as I can tell, we don't have a dwarf-meta powergamer problem; the full tile sprite width does a lot to keep dwarves in check. For now, as requested by Whisper in the discord, rodentia are human size.
It's weird though. Please consider dwarfing the rats.
Technical details

C#: Adds a new Last First naming scheme which Rodentia use elsewhere.
YAML: Adds rodentia, their associated sprites/markings, speech sounds, name conventions, etc.
PNG/JSON: Adds rodentia sprites, as well as custom mask sprites that fit the Rodentia Round Snout.
Note: the Bat Snout is too large and clips out of the rodentia gas mask by 1 pixel. This is because of #5173, which I may have a solution in the wings for. Expanding the gas mask even further looks awkward on default rodentia faces, I believe the best course of action will be to let the bat snout clip until the gas mask issue is resolved.
Media

(The above screens show the dwarf-proportioned rodentia, which have since been made full size. They demonstrate a variety of outfits and equipment)

(This screen shows a squirrel the size of a human man)
Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl:

add: The Rodentia species can now enlist in the marines.

You have a bunch of sprites with no source linking to the tg body parts.
You'll need to find the source of these original sprites and link them, and double check the license used.

That was the attribution on portfiend's sprites on DeltaV. I'll update these to be like the Vulpkanin's sprite attributions.

I have done my best to address all feedback. I noticed that while Delta-V's sprite metadata claims CC-BY-SA-3.0, their own code (and thus our usage of their sprites) is under AGPLv3. So I corrected the metadata for the imported sprites. Hopefully I've done it right this time?

I have done my best to address all feedback. I noticed that while Delta-V's sprite metadata claims CC-BY-SA-3.0, their own code (and thus our usage of their sprites) is under AGPLv3.

The sprites used for vulp are from a commit before deltav was AGPLv3, they're also not ported directly from deltav but from another server that already handled the problem, which you'll essentially need to do here as well, unless they were added during/after AGPLv3, in which case we can't accept these sprites / whatever was sourced from deltav under any circumstances due to the license conflict. Sorry that you had put so much effort into this, but it's very unlikely we'll be able to add these for reasons out of control of either of us.

I have done my best to address all feedback. I noticed that while Delta-V's sprite metadata claims CC-BY-SA-3.0, their own code (and thus our usage of their sprites) is under AGPLv3.

The sprites used for vulp are from a commit before deltav was AGPLv3, they're also not ported directly from deltav but from another server that already handled the problem, which you'll essentially need to do here as well, unless they were added during/after AGPLv3, in which case we can't accept these sprites / whatever was sourced from deltav under any circumstances due to the license conflict.

The vulp attribution lines specifically do say that they are ported from Delta-V.
Rodentia were added after the code went AGPL. However, DeltaV's listed license for these sprites is CC BY SA 3.0 as you can see on their own meta.json files (e.g. this one). Additionally, the creator of the PR gave consent for ports in the PR itself.

AGPL is for code, assets like sprites (and especially ones that are -SA) are still the same license

The vulp attribution lines specifically do say that they are ported from Delta-V.

Yes, because it was explicitly copied from the fork that provided it, the sprites come from deltav, not the fork, obviously.

Additionally, the creator of the PR gave consent for ports in the PR itself.

Thanks for sharing this supporting information, it should be enough to be perfectly fine with this, I'll run it by smug as well and ask a few others just in case.
It's probably safe to assume the creator doesn't really understand how licensing works but it should be fine to port now.

You could probably add more xenonid translations for "rodent" and "rodents" if you care, but otherwise, assuming everything here has been tested to work and render correctly, this seems good to go. I'd still like smug to do their own review regardless as usual.
Additionally, you're absolutely invited to make a wiki addition to the species page, as the person advocating for this species. https://wiki.rouny-ss14.com/wiki/Species

At this point, I would rather do that chatsan expansion as a tiny follow-up PR. Probably after I've finished working on next PR, which is to fix issue #5173.
I'll gladly add Rodentia to the wiki though!

Oh! And regarding testing: I've been pretty thorough. I tested every armor I could find, most of the CM outfits available through the Debug > Set Outfit command, tested all the markings, tested gas mask, coif, rebreather, and sterile mask (it seems like the medical gas mask isn't really used? if that changes I'm happy to work out a sprite for that too). Tested xeno interactions like parasite latching, devouring, wall nesting, chestbursting. Tested carrying, dragging, wielding weapons. I can't guarantee there aren't any edge cases I missed, but I've been as thorough as possible.
I didn't update all my PR screenshots for the full-sized rats, but I've continued to test quite a lot since sizing them up.

Additionally, you're absolutely invited to make a wiki addition to the species page, as the person advocating for this species. https://wiki.rouny-ss14.com/wiki/Species

How's this? https://wiki.rouny-ss14.com/wiki/Species

Thanks for the PR!


Use with Monk Active Tiles

There is any chance to change the macro, and let pass the list to be selected as a param?
So it can be used in Monk Active Tiles for traps.

There is any chance to change the macro, and let pass the list to be selected as a param? So it can be used in Monk Active Tiles for traps.

Do you have an example?
I can make the macro accept params and return a token. Is that it?

Yes, just like that.

With monk active tiles, if a token enter on a tile, I can activate a macro and get this result to make something.

With monk active tiles, if a token enter on a tile, I can activate a macro and get this result to make something.

the params can be one []?
the return can be the token object?

yes, it would be great and array of tokens and the "choosen" token as a return.

update


Add TSC Meeting notes 05-04-2020

Signed-off-by: Michael Dolan<EMAIL_ADDRESS>

Been useful to have been around for this one :)


Cost model integration

This PR introduces the use of the cost model during query execution

@kurapov-peter, thanks! Could you please also advice something here? I'm not sure if this is a good solution


Can I submit multiple folding jobs as a batch on one GPU in parallel?

I wanted to know if it was possible to submit let's say 5 folding jobs on the same GPU in parallel by increasing the batch size? I don't want to do it one by one. When I try and do multiprocessing and submit 5 separately, the speed is significantly reduced. Any ideas?

Hey， I encountered the same problem. Have you solved this problem?


Fix for Capybara 2.7; Rack driver now considers hidden fields invisible

Fresh bundle install included Capybara 2.7; form_builder specs failed because latest Capybara Rack driver does not find hidden fields by default.

Also replaced fog with fog/aws, and replaced uuidtools with SecureRandom.uuid to reduce dependencies.

FYI, reducing the dependency footprint fog -> fog/aws dropped slug footprint by ~20MB on heroku.

Thanks for the PR! Looks like nobody is maintaining this gem anymore. Are you interested in maintaining it?
Cheers

@dwilkie I hope to have some time next week to look at some pull requests, including this one.

@p8 @dwilkie I am happy to help out; really appreciate this gem and rely on it in several projects.


Check multi-arch images

Is your feature request related to a problem? Please describe.

Maybe some other flags need to be passed to opm when generating the images.
To see if this is happening also to the final version released in operatorhub/openshift-marketplace (that ones are generated internally by the redhat repo)
Describe the solution you'd like
The OLM images should be multiarch at least the ones deployed in Operatorhub/Openshift marketplace
Describe alternatives you've considered
No response
Additional context
No response

I tested the flow in an arm64 kubernetes cluster and is working fine.
So probably the issue is just on how we create our test image but the opensfhit marketplace release is release multi-arch.
I will close this one


Make it easy to change plugin package name

Capital letters are not allowed on package names (on pub.dev) I created a plugin with capital letter package name, I couldn't publish because of that. (Wish it warned me at beginning) I spent my whole day do rename the package, please make that easy.

Hi @emreakcan
https://stackoverflow.com/questions/51534616/how-to-change-package-name-in-flutter
see the accepted edited answer
it is really easy to rename package name.
Thanks

@Abhishek01039, I'm asking about plugin package name, not the app.

Hi @emreakcan
non-capital letter package is a standard naming convention on  https://pub.dev/ and the tool doesn't support changing package or plugin, the tool doesn't have the refracting ability so you have to change your code manually or moving your files into the newly created plugin, use Android Studio to refracted code for all classes
Closing, If you disagree, please write in the comments and I will reopen it.
Thank you

@TahaTesser maybe it can prevent to create plugins with faulty package name?


QUESTION: Seperate tabs for Models and Model Concerns

Hi!
I have this block in rails_helper.rb
SimpleCov.start 'rails' do
  add_filter '/spec/'
  add_filter '/config/'
  add_filter '/vendor/'
  add_filter '/test/'
  add_filter '/lib/'
  add_filter '/db/'
  add_filter '/log/'
  add_filter '/tmp/'

  add_group 'Controllers', 'app/controllers'
  add_group 'Models', 'app/models'
  add_group 'Helpers', 'app/helpers'
  add_group 'Mailers', 'app/mailers'
  add_group 'Views', 'app/views'
  add_group 'Model Concerns', 'app/models/concerns'
end

This gives me tabs for "Models" and "Model Concerns" in coverage report, unfortunately, the "Models" tab also includes the reports on concerns. Indeed, it includes reports on all files in /models and subdirectories.
How can I change the formatting in the line below to only load files in that directory, without any subdirectories?
add_group 'Models', 'app/models'

Hi there,
there are different kinds of filters, see the code dispatching them here and see their actual implementation here
So from my understanding, you could just implement a block that does what you want it to do - e.g. return true for file names in app/models except for app/models/concerns. You could also implement your own filter class of course.
Hope this helps you, let us know if not :)

Thanks!
I managed to get the exclusion working by passing a block.
add_group 'Models' do |file|
  file.filename[%r'/app/models'].present? && file.filename[%r'/app/models/concerns'].blank?
end


[e2e]: docker-based workflow_dispatch main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/4464369018
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.docker-based.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.docker-based.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Mon Mar 20 03:20:40 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/4469154733
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.docker-based.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.docker-based.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Mon Mar 20 14:16:25 UTC 2023
Tests are passing now. Closing this issue.


find_libpython was not able to find a libpython in the current Python environment

I am new to cocotb and facing a similar issue as
**find_libpython was not able to find a libpython in the current Python environment. Ensure
the Python development packages are installed. If they are installed and find_libpython
is not finding the path to libpython, file an upstream bug in find_libpython; then
manually override the LIBPYTHON_LOC make variable with the absolute path to libpython.so
(or python.dll on Windows).
. Stop.
**
I have the following environment setup
Python 3.7.2
pip 24.0
Package              Version
cocotb                 1.8.1
find_libpython     0.4.0
pip                       24.0
setuptools           40.6.2
and PATH is set with <.....>/venv/bin
cocotb-config --lib-dir has some path but cocotb-config --libpython does not give me any path.Also i donot see any libpython.so installed in my virtual environment
Can you please help me to overcome this issue?

Okay, what OS? What environment are you using?

I have changed my python version and now it works fine. Thank you very much for the support


Add Fix Disallowing Capabilities Accessed By FQN

This PR disallows references to capabilities via import or by FQN.
See: https://github.com/kadena-io/pact/issues/638

Fixed in 761adfe5dcb93d054e7883a3776c9bf70889f8ae. Closing


Use AssemblyAI Node SDK

I updated the AssemblyAI plugin to use the AssemblyAI Node SDK.
This did require me to polyfill a couple of Node APIs.

I'd really prefer to not polyfill node APIs, because Rivet is designed to run without any kind of polyfill. Is there anything we can do to make this or your library isomorphic? It's important to me to keep Rivet isomorphic and not depend on any library that's node or browser specific.

I suppose that depends on the bundler used. I haven't tested it. I wonder if it's time to move this plugin out of core maybe? Like https://github.com/abrenneke/rivet-plugin-example-python-exec is the example repo. And I just wrote the docs on creating plugins too

I updated the SDK so it no longer requires polyfills in Rivet. Being built into Rivet was one of the appeals for us to contribute the integration, so I hope we can keep it in, but we can move it out if it makes more sense.

Sure it's fine! There's really not much difference between built-in plugins and external ones at this point. Built-in plugins allow you to modify the Rivet UI though and add functionality there - if you're only adding nodes, the only real difference is that there's no "install" step and the plugin activates immediately

We always went the fewest possible steps to success of course. ;)
Is this PR okay now?

@Swimburger latest builds have these warnings:
[plugin:vite:resolve] Module "stream" has been externalized for browser compatibility, imported by "/Users/Shared/ironclad/rivet/.yarn/cache/assemblyai-npm-3.0.1-41a2932ec5-bfa7c25c89.zip/node_modules/assemblyai/dist/index.esm.js". See http://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] Module "fs" has been externalized for browser compatibility, imported by "/Users/Shared/ironclad/rivet/.yarn/cache/assemblyai-npm-3.0.1-41a2932ec5-bfa7c25c89.zip/node_modules/assemblyai/dist/index.esm.js". See http://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.

@abrenneke The plugin doesn't rely on stream or fs, so we can disregard.
In the next version of the SDK we're using web standard streams tho, so that'll be gone, and we'll have a browser-compatible export that doesn't use fs either.


Fix build errors

this PR fixes these build errors:

undefined reference linker errors caused by missing template instantiations and non-inclusion of .cu source files
build failure on windows caused by referencing a non-standard library bits/stdc++.h and type u_int32_t

I use this PR to test, and get some failure.
running 19 tests
test matrix::tests::test_interleave_columns ... ok
test matrix::tests::test_shift_left_and_fill_zeroes ... ok
test matrix::tests::test_split_matrix ... ok
test matrix::tests::test_rows_to_cols ... ok
test matrix::tests::test_concat_rows_in_matrices ... ok
test tests::test_arc_py_scalar ... ok
test matrix::tests::test_split_vec_to_matrix ... ok
test tests::test_debug_ntt ... FAILED
test tests::test_debug_scalar ... ok
test tests::test_ntt ... FAILED
test tests::test_to_from_arc_bls12_381_377 ... ok
test utils::tests::test_reverse_bit_order ... ok
test utils::tests::test_hex_str_to_u32_vec ... ok
test utils::tests::test_list_to_reverse_bit_order ... ok
test tests::test_read_write_scalars ... ok
test tests::test_read_write_points ... ok
test tests::test_vec_saclar_mul ... ok
test tests::test_vec_point_mul ... ok
test tests::test_msm ... FAILED

I use this PR to test, and get some failure.

I am aware that some of the tests fail but this PR does not try to fix the tests, just the build issues. IMHO the changes in this PR are not the cause of the test failures.

@hugo-blue the Rust interface is still a bit clunky. Fix is on its way
cc @vhnatyk


docs: how to get the cloudpage URL for testing?

on https://fib3.github.io/ssjs-vsc/use/ you say that the command SSJS: Deploy Dev Page "generates" the cloudpage. I have personally not been able to create a cloudpage via API so if you found a ways i'd be thrilled.
anyhow, assuming your solution somehow does this, where do I get the URL from? find it in the SFMC GUI?

what we tend to do is create a cloud page, then put code in there to load a CONTENT BLOCK that we want to debug, then publish the cloudpage.
onload of the page, it will parse the CURRENT version of the content block.
now, for THIS extension you could advise people to create 1 content block + 1 cloudpage at first. the cloudpage loads the contentblock. the content block then is a placeholder itself, given that it can be updated via content builder API, to load whatever code snippet that you ACTUALLY want to test.
that way, the user can have x amounts of actual code-content blocks, 1 placeholder content block and 1 placeholder cloudpage.
each time the user uploads a script your extension could then update that placeholder content block to load this new snippet.
the user would always have the same URL for testing
my 2 cents ;-)
didn't make sense in the context of mcdev but here that could be fun

That's actually pretty much, how the "Asset Provider" handles the development already.

On setup: you (manually) create one universal Dev Cloud Page (of Dev Text Resource) which will run your code.
On the development, you only develop your scripts, and they get automatically deployed as content blocks. (well, on the first go, you need to deploy using SSJS: Upload Script, which is done so you don't deploy scripts you want to keep to yourself).
The Command Get Dev Path is giving you the "secured" path to your resource. Like: ?token=?token=<GUID>&asset-id=<id-of-asset>

I guess, I really need to make a video showcasing the whole extension.

yes, I know. That's why I little bit prefer Server Provider, which loads the scripts from your laptop (the problem is however the fact, that you need to expose your computer via NGROK etc.).
But the initial security measure is the "token" in the path of the page. It's not the best way, but as I said, it's initial.
I am thinking about making other options, but I need to take into consideration, that during the development, you need to pass those "credentials" along to other resources you are working on (e.g.: typical forms that post to another Cloud Page to process). Also, that this needs to be something, that you can use rather easily in the browser.
I am also thinking about options, how to rotate this token automatically, so it's valid for limited time only.

There are several feeatures now (or in the 0.4.4 I am about to release) that help with this.
There's is an "Update Dev Page" command, button to more easily open the URL, and more documentation.
Also, there's the option to use a HTML login instead of the token (basically Basic Auth).


[Feature Request]: Hide methods from suggestions when typing "::"

This idea originated from this StackOverflow question. The idea is to have an option to hide methods (those which the first parameter is self) from the suggestions that are shown after ::. Only associated functions would appear then.
The rationale is that, although methods are associated functions (thus should be listed), most of the time you want to invoke them only with an object, using the . syntax.
In the example below, calc_num should not be listed in suggestions:

It's always 'easy' to add options, but I'm not a fan of hiding valid completions. I think we should sort them to the bottom, if possible, and that may be enough?

I don't think we should do this. Any opinion @matklad?

I don't think we should do this. Any opinion @matklad?

I would love if this was reopened. Personally I'd like the option of either sorting the self functions to the bottom or entirely removing them. 99% of the time, I don't want the self methods and the suggestions are just noise then.
This should definitely be a configuration option though as it could be confusing unless you make the conscious choice to hide those functions.
Are there any specific reasons not to provide such an option? @lnicola why do you think it should not be implemented?

@SorteKanin Personally, I'd like to see the methods sorted by: those belonging to the struct itself, then the traits. And for the trait methods, showing the trait where they come from.

@rodrigocfd that sounds like a good idea for some customizable options yea. But this issue is just about hiding the self functions I'd say.


ash 0.32 build fix

See #54, #55, #56

Thanks! Should be resolved now by #66, so I'm closing this now.

Fwiw the actual, only correct fix seems to have been landed via https://github.com/gwihlidal/vk-mem-rs/commit/d685b50c85df76b275f8a504b93078a4fd9aabb8 in #62 already.


python311Packages.sendgrid: 6.10.0 -> 6.11.0

Diff: https://github.com/sendgrid/sendgrid-python/compare/refs/tags/6.10.0...6.11.0
Changelog: https://github.com/sendgrid/sendgrid-python/blob/6.11.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.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.

Add a :+1: reaction to pull requests you find important.

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

4 packages built:

python310Packages.sendgrid
python310Packages.sendgrid.dist
python311Packages.sendgrid
python311Packages.sendgrid.dist


Adding a 2.2.0 theme version

Hi,
CTFd team added some improvements (#1188) to the CTFd front-end files.
And as you can see, this theme needs to have another branch or to have duplicate files with a different file extensions (.min.extension).
There is other changes described in that pull request and I don't know whether this project is concerned by them or not.
Are these changes can be added to this project ?

We'll need to check that for sure.

The last version that I can use for this theme is CTFd 2.1.5

@mohamedaymenkarmous Ok thanks for the help. But it may take a long time before I have time to work on this. Just so you know.

@noraj no problem
I will be using 2.1.5 version and I will be waiting for releasing the new ctfd-theme-sigsegv2 update that will be compatible with the CTF 2.2.0 version
Thank you


[SPARK-36153][SQL][DOCS][FOLLOWUP] Fix the description about the possible values of spark.sql.catalogImplementation property

What changes were proposed in this pull request?

This PR fixes the description about the possible values of spark.sql.catalogImplementation property.
It was added in SPARK-36153 (#33362) but the possible values are hive or in-memory rather than true or false.
Why are the changes needed?

To fix wrong description.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

I just confirmed in-memory and hive are the valid values with SparkShell.

cc: @HyukjinKwon @srowen @AngersZhuuuu who are involved in that PR.

Test build #143035 has started for PR 33923 at commit 4d1f7ad.

i manually built the docs and checked this.
Merged to master and branch-3.2.

Test build #143035 has finished for PR 33923 at commit 4d1f7ad.

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

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47537/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47537/

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


Docker compose: 5.2.0  - unknown shorthand flag: 'f' in -f

Hi Guys Im trying to use 5.2.0 coming from 3.9.0
I'm getting this error on buildkite

Building services build-${BUILDKITE_BRANCH}-${BUILDKITE_BUILD_NUMBER}-${BUILDKITE_COMMIT} | 0s
-- | --
  | $ docker compose -f docker-compose.yml -p buildkite018f75692ece423b91a4b2fc60fba6c6 build --pull build-${BUILDKITE_BRANCH}-${BUILDKITE_BUILD_NUMBER}-${BUILDKITE_COMMIT}
  | unknown shorthand flag: 'f' in -f

any thoughts on whats causing the issue
this is my step in pipeline.yml
steps:
  - label: ":docker: Build image on host"
    branches: "development staging alpha beta gamma master"
    plugins:
      - ecr#v2.9.0:
          login: true
          region: "us-east-1"
          no-include-email: true
      - docker-compose#v5.2.0:
          build: "build-${BUILDKITE_BRANCH}-${BUILDKITE_BUILD_NUMBER}-${BUILDKITE_COMMIT}"
          push: ****
          config: docker-compose.yml
          env:
            - BUILDKITE_BRANCH

I have a similar issue:
docker compose -f .buildkite/docker-compose.buildkite.yml -p buildkite01902f5ee1bf44b2b9b7420ae359e365 -f docker-compose.buildkite-109425-override.yml build --pull --build-arg IMAGE_SRC=669097903843.dkr.ecr.us-west-2.amazonaws.com/chargify-ci/base app
--
  | unknown shorthand flag: 'f' in -f
  | See 'docker --help'.

Later in the logs:

Management Commands:
--
  | builder     Manage builds
  | buildx*     Docker Buildx (Docker Inc., v0.7.1)
  | config      Manage Docker configs
  | container   Manage containers
  | context     Manage contexts
  | image       Manage images
  | manifest    Manage Docker image manifests and manifest lists
  | network     Manage networks

It looks like docker compose v2 is not accessible for some reason and docker command does not recognize it.

I have a similar issue:
docker compose -f .buildkite/docker-compose.buildkite.yml -p buildkite01902f5ee1bf44b2b9b7420ae359e365 -f docker-compose.buildkite-109425-override.yml build --pull --build-arg IMAGE_SRC=669097903843.dkr.ecr.us-west-2.amazonaws.com/chargify-ci/base app
--
  | unknown shorthand flag: 'f' in -f
  | See 'docker --help'.

Later in the logs:

Management Commands:
--
  | builder     Manage builds
  | buildx*     Docker Buildx (Docker Inc., v0.7.1)
  | config      Manage Docker configs
  | container   Manage containers
  | context     Manage contexts
  | image       Manage images
  | manifest    Manage Docker image manifests and manifest lists
  | network     Manage networks

It looks like docker compose v2 is not accessbile for some reason and docker command does not recognize it.

This is extremely strange and not something I have experienced or seen before. The most likely explanation I can think of is that compose is not recognized as a valid docker plugin or is corrupt in some way (like when there are shims to pass through compose V1 to V2 plugins).
Could any further information be provided with regards your execution environments? Are you running in AWS using a standard AMI? What version of docker? What version of docker compose? How were they installed? What version of the agent? How was it installed? Was it installed after or before docker? Any steps that are working and these are not? 🤯

Installing the Docker Compose plugin should address this issue.
https://docs.docker.com/compose/install/linux/#install-using-the-repository

In the manual install instructions for Docker Compose here
https://docs.docker.com/compose/install/linux/#install-the-plugin-manually
they give the plugins directory locations. I was getting this same error and I had the docker-compose binary installed in the path (in /usr/local/lib) but not in one of the plugins directories.
I put a copy of the docker-compose binary here /usr/local/lib/docker/cli-plugins/docker-compose and it's working fine.


Linux Copy/Paste. Blank preferences

On Ubuntu 16.04 I am unable to copy via selection, and the command ctrl + c as listed does not copy, only terminates the current running task in the terminal.
Any way to implement copy on selection?
Edit preferences shows blank, and the text at the bottom is also not visible. And the only way to exit is closing the tab.
Currently not using any theme.

You can enable copy on selection by putting copyOnSelect in your config.

Thank you, was getting jumbled up by hyper.js and preferences.


MIlestone 2 General Feedback

Hello Group 18!
Well done with your project! The Jane Austen quote was a nice touch :)
Your code ran smoothly, and I can see that you used github issues and commit titles effectively. It might be good as part of the process to open a few more issues to track the overall progress of the team.
Report suggestions:

Table of contents missing
what does wrt in figure legends mean?
having the 0/1 labeled on the x-axis as <50k and >50K would make it easier to understand, and not have to keep double checking which is which
Figure 1 is listed for both box-plots, change second one to Figure 2
why is the summary at the beginning of the report did you report overall accuracy of 1. Where does this come from? and how is this possible with 1806 incorrectly predicted examples? Final conclusion is not as optimistic in its claims as the summary. Align the summary with the conclusions and discussion.
unclear from the report if you kept the features of the dataset in the model or only the ones you showed inthe box-plots?
it would also be nice if you just mentioned that the features are not correlated, tbh I think the correlation plot is more useful to look at than the box-plots because it is not clear to me why the box-plots are being shown. I understand that maybe these are the features you think might best help predict income levels, but this is not clear, nor is it addressed at the end whether these features were most useful in the models for predicting or not.

Added table of contents.
Changed the summary to report accurate results
Explained the selection of features by adding box plots for all numeric variables and also the correlation heat map


XSS Vulnerability using anchor tags

Version

The one present in example page, also happening on latest (1.4.6), probably any tui editor with html enabled
Test Environment

Chrome Version 79.0.3909.0 (Official Build) canary (64-bit)
MacOS 10.14.6
Current Behavior

Enter in editor:
 text

When you clicked on previewed link, alert will pop up with browser cookies (if have any). You can also put window.localStorage or other malicious actions
Expected Behavior

Output is properly sanitised

@kleyu @artemmolotov
Yes, this is a serious issue.. 🤔
I've seen how GitHub and markdown-it editors work, and each editor works like this:
GitHub
 text

 text

markdown-it

Disable html

Enable html

I noticed the same issue with markdown-it when html is enabled. So I think we should check markdown-it first. Whether links that are prohibited by markdown-it are valid only when html is disabled.
And I'll check the your PR this week and let you know the result.
Thanks for reporting the issue.


Re-Export NonEmpty to allow setting the token_extractors without installing crate

Hi,
if you currently try to set your own token_extractors in your KeycloakAuthLayer, you have to pass a NonEmpty list:
e.g.
    KeycloakAuthLayer::<String>::builder()
        .instance(get_keycloak_auth_instance(config))
        .passthrough_mode(PassthroughMode::Block)
        .persist_raw_claims(false)
        .expected_audiences(vec![String::from("account")])
        .token_extractors(NonEmpty::<Arc<dyn TokenExtractor>> {
            head: Arc::new(AuthHeaderTokenExtractor::default()),
            tail: vec![Arc::new(QueryParamTokenExtractor::default())],
        })
        .build()

Currently you have to install the https://crates.io/crates/nonempty crate into your project by yourself.
Maybe we could re-export that crate, so we can use it without explicitly installing it.
T

Hm it seems to be already re-exported. My ide just want to ignore that fact :p


feature request: text-based output without all the pretty around it

I was applying package-benchmark to a comparison effort between a number of different existing libraries and external packages, so compare speeds of how they did their work. When I was dumping the output, I found that I wanted to sort and view the results as an ordered list, and then wanted to go grab and knock together some simple graphs for the comparison between the different libraries. The TextTable output, which looks so great, was completely in the way, and I ended up having to do quite a lot of text editing to grab the data out into a spreadsheet, which I then used to re-order things, make charts, etc.
(I also found that TextTable was clipping some names, as I was getting pretty descriptive there)
The request is for a text based output that applies a bit more directly in this direction, or even a plain .csv output - something that can be easily copy & pasted, or a .csv output that you could open with spreadsheet-of-your-choice kind of setup.
I did look at the tsv format output, but didn't quite know what it was an how to interpret it - and it wasn't in any sort of obvious columnar form - so I don't think that applies.

I think we should add a .csv format usable for direct import to spreadsheets - are you thinking percentiles or raw data?

But to compare speeds I'd suggest also trying .jmh and the online analyzer (or histogram,percentiles and loading multiple files to that analyzer)

In my case, I was after the percentiles (and associated raw numbers at those percentiles) - the equivalent bits that get presented after a run, just easier to resort and use as sourcing for making quick comparison charts. I haven't used the online analyzer, but I'll give that a go!

Wow - that JMH comparison setup is really nice, and very quickly provided some of the detail I was after! We should absolutely reference that in the documentation, with a link to that online view (assuming that's not in the end abusive of someone's service)!

There should be a link to it in main already (and on the landing page) :-) ! But I'll add one more - agree, it isn't bad at all.

Adding percentiles 0-100 output as an alternative in https://github.com/ordo-one/package-benchmark/pull/102 - it worked more-or-less when pasted into a spreadsheet too - although numbers had some issues with decimal points, but may be Swedish locale - will try a bit more.

Ooh - nice, I'll pull that branch down and try it out with some of my local bits. I've got a handy testbed set where I'm comparing the speeds of various implementations of pseudo-random number generators, which was the inciting use case for the request.

Cool, would be great with some additional testing. Perhaps you could go for https://github.com/ordo-one/package-benchmark/pull/103 branch - it should be the latest and greatest right now really. :-)

Maybe should just skip the 99.999(99) percentile in output and keep it simpler. Then import to numbers would be a breeze. WDYT?

using --format histogramSamples, which looks to be the replacement for --format tsv, is still just a single line of values, and kind of oddly with the filename extension of .raw.tsv - no header, so it's hard to know what the values are unless you're really familiar with the benchmarks that were written.
The --format histogramPercentiles was definitely easier to parse - and had headers. The extra 9's didn't do anything for me, but in this mode I'm not as interested in the long-tail latencies - so for my purposes, I'd be totally fine to see it.
The extension pattern on the histogramSamples is a little different yet - listing the metric in the name now as a sort of extension, and then on into detail (example: .throughput.histogram.percentiles.tsv). I think percentiles in the chain is redundant, as it's well labeled in the tab-sep-values.
Oh - and thank you for fixing the --grouping metric headers!

Thanks for trying it out!
histogramSamples is just all the raw histogram samples scaled to the time/SI unit in use (really for external processing using eg. Youplot or spreadsheet, but maybe a header with unit information would be good.)
For the 0-100 percentiles - I'll add support for putting the multiple baselines (if provided) into the same output, will think a bit perhaps should tweak how output is generated based on grouping.

The extension pattern on the histogramSamples is a little different yet - listing the metric in the name now as a sort of extension, and then on into detail (example: .throughput.histogram.percentiles.tsv). I think percentiles in the chain is redundant, as it's well labeled in the tab-sep-values.

This was to separate 'samples' from 'percentiles' as both are .tsv formats - I've added a header and fixed the scaling of the sample data now so it should be more understandable. I also killed off the extra .999:s


v3 image generation throws a 403 error

When trying to create images using the standard Craiyon client, it throws a 403 error from axios. Curious if this is caused by not having an API key with a paid subscription, or if they are down. Has been happening for at least 3 days now.

Sorry my mistake, this screenshot is for a similar library written in Node. But the python one you've created no longer works as well.

I just had a look at it myself and it seems like you say so. I'll be trying to get a workaround this and push the updates as soon as possible. Until then, please wait and make sure to update the library once the changes are pushed.

Since I am not near my workspace for a few days you might need to wait for around 2-3 days. Until then maybe @mdm9300404 can help if he's free, otherwise I'll just do that once I get back to it.

Since I am not near my workspace for a few days you might need to wait for around 2-3 days. Until then maybe @mdm9300404 can help if he's free, otherwise I'll just do that once I get back to it.

No worries. I use this library for fun in my friend and I's discord server, and I've got a workaround in place to use v1 image generations as well. Just wanted to get the information out there!

Since I am not near my workspace for a few days you might need to wait for around 2-3 days. Until then maybe @mdm9300404 can help if he's free, otherwise I'll just do that once I get back to it.

It seems they have Cloudflare detecting Craiyon.py as a script and they're sending blocked/403 forbidden responses now. I'm trying to emulate a web browser to get around the block, but I haven't had any success yet.

Yeah, it appears using a simple request on their api isn't working anymore.
I am trying to figure out how to bypass it still.

The library was breaking due to Craiyon implementing Cloudflare's anti-bot protection page. Bypassed it in the v1.1.0 by using CloudScraper. Please update the wrapper to the latest version by running pip install -U craiyon.py before using it.

The library was breaking due to Craiyon implementing Cloudflare's anti-bot protection page. Bypassed it in the v1.1.0 by using CloudScraper. Please update the wrapper to the latest version by running pip install -U craiyon.py before using it.

I am still getting an error with this. Now it is throwing a 'Attempt to decode JSON with unexpected mimetype: text/html; charset=utf-8' error. Passing content_type='text/html' to the .json() method in the library does not help either.


Configurable nuget sources

The dotnet version now also does a restore first, because dotnet add only accepts one target repository name and would fail if dependencies for the update are missing.

👍 Looks ok and we need this feature, many orgs will have internal nuget feeds serving packages that need auto-updating.


Fix/remove unclear auto behaviour

This PR removes some unclear automatic behaviour of the pydantic plans which were added.

Auto add sinks
Extra args being allowed

Codecov Report
Attention: Patch coverage is 0% with 11 lines in your changes missing coverage. Please review.

Project coverage is 31.63%. Comparing base (11bdaa8) to head (d12acf6).

Files with missing lines
Patch %
Lines

multio/plans/plans.py
0.00%
11 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           develop       #8      +/-   ##
===========================================
- Coverage    32.53%   31.63%   -0.91%
===========================================
  Files           15       15
  Lines          713      705       -8
===========================================
- Hits           232      223       -9
- Misses         481      482       +1

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


ConcurrentModificationException thrown on RedissonSession save method

Expected behavior
Using Redisson based Tomcat Session Manager; no exceptions are thrown and sessions aren't lost prematurely.
Actual behavior
Sessions are expiring earlier than expected and we are seeing the following error:
SEVERE: Exception Processing [...]
java.util.ConcurrentModificationException
	at java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1043)
	at java.base/java.util.ArrayList$Itr.next(ArrayList.java:997)
	at com.esotericsoftware.kryo.serializers.CollectionSerializer.write(CollectionSerializer.java:154)
	at com.esotericsoftware.kryo.serializers.CollectionSerializer.write(CollectionSerializer.java:44)
	at com.esotericsoftware.kryo.Kryo.writeClassAndObject(Kryo.java:711)
	at org.redisson.codec.Kryo5Codec$5.encode(Kryo5Codec.java:171)
	at org.redisson.tomcat.AttributeMessage.toByteArray(AttributeMessage.java:60)
	at org.redisson.tomcat.AttributesPutAllMessage.<init>(AttributesPutAllMessage.java:43)
	at org.redisson.tomcat.RedissonSession.createPutAllMessage(RedissonSession.java:238)
	at org.redisson.tomcat.RedissonSession.save(RedissonSession.java:432)
	at org.redisson.tomcat.RedissonSessionManager.store(RedissonSessionManager.java:420)
	at org.redisson.tomcat.UpdateValve.invoke(UpdateValve.java:74)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:670)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:346)
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:390)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:928)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1794)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
	at java.base/java.lang.Thread.run(Thread.java:829)

Steps to reproduce or test case
This is seen when we run regression tests that repeatedly log in/out, creating and destroying multiple sessions originating from the same user. Only happens intermittently and not on the same tests every time.
Redis version
7.1
Redisson version
3.27.0
Redisson configuration
Happens in both clustered and single node instances, however marginally less in a clustered configuration (2 nodes, 2 shards per node).
Redisson Tomcat Session Manager configurations:

ReadMode: MEMORY
UpdateMode: AFTER_REQUEST
BroadcastSessionEvents: true
We do have a custom keyPrefix
Everything else is default values

Tomcat version: 9.0.86
Java version: 11

It's a Kryo lib issue.
@theigl
Hi. Can you look at it?

This is most likely not a Kryo issue. It looks like the Kryo encoder is given an ArrayList that is modified concurrently by another thread. Kryo always assumes it has exclusive access to the data during serialization. The user of Kryo has to make sure that the data can be safely serialized.

@theigl
Thank you for review. Let me check that.

@theigl
map passed into createPutAllMessage isn't changed since it's life scope is createPutAllMessage method. You can check org.redisson.tomcat.RedissonSession.save() method.

Kryo does not write/remove data from lists so it can't be responsible for the exception. An other thread must access the list at the same time. If you look closely the stacktrace, the error happens in ArrayList, not in a map. So there must be a list somewhere in the map that gets modified.

You are right. User stores list as Tomcat Session attribute.

Fixed. Thanks for report


Which version of community_store_stripe?

The core community_store package README explicitly recommends using a release version for production. How about community_store_stripe. I see that the master branch is currently at v1.0.4, with the last change 2 months ago. Is there any reason not to use v1.0.4?

I'd be suggesting the use of v1.0.4 - the fact there isn't a matching release for it is simply down to me either forgetting to create one, or there wasn't something critical in the last few updates.

Ok, makes sense. Thanks.


Upgrade: update codeflare-sdk package to latest version 0.13.0

Upgrade: update codeflare-sdk package to latest version 0.13.0
Description

Upgrade: update codeflare-sdk package to latest version 0.13.0
https://pypi.org/project/codeflare-sdk/
How Has This Been Tested?

NA
Merge criteria:

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

/test notebooks-e2e-tests

/lgtm

/approve
Merging to get this in for feature freeze


[sailfish-secrets] Have license file as %license. JB#55991

@Tomin1 @mlehtima

This is fine, but I think License tag should be BSD instead of BSD-3-Clause like it is now.

Yes, true. I'll update as such and merge.


U

H

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

ID: 79604501-4e57-c776-6117-82d15c9ebb34
Version Independent ID: fc6e660a-0180-98b5-c53a-30e57507a707
Content: Manage your two-step verification settings
Content Source: articles/multi-factor-authentication/end-user/multi-factor-authentication-end-user-manage-settings.md
Service: multi-factor-authentication
Product: unspecified
GitHub Login: @barlanmsft
Microsoft Alias: barlan

@harvgall Can you please provide details of your ask.

@harvgall We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Switch to using pipeline resource

Change means of consuming external pipeline artifact.
I made this change because for some reason DownloadPipelineArtifact@2 fails for pull requests.

/azp run net - aggregate-reports


Vue CSS and selectors not included after production build

I have Laravel ^7.0 version installed including the laravel-frontend-presets ^4.1
I style the web app in blade and Vue components.
When I run npm run dev all look good.
When I run npm run prod it looks that only selectors from the blade files are included in the output app.css.
In the last two days, I try to figure out the problem and it looks like that postCss does not consider the selectors in all the Vue components and also not the scoped styles.

/** webpack.min.js **/
const mix = require("laravel-mix");

require("laravel-mix-tailwind");

/*
 |--------------------------------------------------------------------------
 | Mix Asset Management
 |--------------------------------------------------------------------------
 |
 | Mix provides a clean, fluent API for defining some Webpack build steps
 | for your Laravel application. By default, we are compiling the Sass
 | file for the application as well as bundling up all the JS files.
 |
 */
mix.options({
  extractVueStyles: true
});

mix
  .js("resources/js/app.js", "public/js")
  .postCss("resources/css/app.css", "public/css")
  .tailwind("./tailwind.config.js")
  .extract(["vue", "vue-chartjs", "vue2-leaflet"]);

if (mix.inProduction()) {
  mix.version();
}

I read different sources like:
https://medium.com/@yazeedobaid/postcss-in-laravel-mix-bc433bfcf7a
I tried his approach, but without any success.
Similar behaviour is reported on stackoverflow but no answer so far: https://stackoverflow.com/questions/61290702/postcss-not-working-with-laravel-mix-scss-and-tailwindcss-outside-laravel
Anyone can confirm this behaviour?

You can add additional patterns for purgecss to consider in your tailwind.config.js file.
By default, we only include ./resources/views/**/*.blade.php and ./resources/css/**/*.css as this preset does not include any Vue configuration.


Breakpoints documentation (em vs px)

Hi, should the docs be updated?
Source says that px are used: https://github.com/twbs/bootstrap/blob/v4-dev/scss/_variables.scss#L121
And documentation states about em: http://v4-alpha.getbootstrap.com/layout/overview/

that was changed with 4c5ba3e5

So, the production wasn't yet updated?

The website is basically only updated when each new release is shipped, to avoid being inconsistent with the release version's code. The v4 site doesn't track the bleeding-edge v4-dev branch.
As stated on the v4 website's homepage and footer, the site currently corresponds to v4.0.0-alpha.2.
We switched from em to px shortly after v4.0.0-alpha.2, so the site still uses em.
The site will be updated when alpha 3 (or equivalent) ships.
If you're using the bleeding-edge v4-dev branch and want fully accurate docs, you should run the docs locally and consult them instead of the getbootstrap.com hosted docs.


Resolved Bug 511 and 568 :  Storybook > Elements > Feed > Select dark theme star color is not change And Storybook > Elements > Widget Portal > Incorrect text

Description

Resolved Storybook >Elements>Widget Portal >Incorrect text
Resolved Storybook >Components>Feeds>Long Feed> Select dark theme star color is not change.
Resolved Storybook >Components>OTP Input >Incorrect text

Screenshot :-
Elements>Widget Portal

Components>Feeds>Long Feed

Components>OTP Input

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Changes Reviewed and PR Approved


todogroup.org and this community do not have a code of conduct

Specifically, where do I report harassment and unacceptable behavior occurring in this community?

I think it's reasonable to assume that we should fallow the same code of conduct we are contributing to. As to the reporting harassment - I did not find any reference to that either.
Maybe @bkeepers could clarify?

The code of conduct document here is a template. The<EMAIL_ADDRESS>address that was suggested in the template bounces.

Yes, it is indeed a template, but I guess we should probably stand by the guidelines we ourselves created and are contributing to.
Maybe we can explicitly state in the readme that we ourselves do adhere to the CoC along with the abuse contact?


Tooltips should be replaced by something less flimsy

Perhaps an ETM-style 'harmonica' info text with the option of including links to documentation and images?
@dennisschoenmakers @antw what do you think?

Let's see some designs or hear some ideas first, @grdw !

Some things for the short run: turn the trigger into a click, remove the transparency which is just horrible.

Some things for the short run: turn the trigger into a click, remove the transparency which is just horrible

:+1:


BufferViewer: fix primitive restart

I wrote these fixes last year while debugging some Dolphin code, so it's been a while... If I remember correctly the buffer view was showing uninitialized memory and primitive restarts of larger-than-one-byte indices were not recognized as such. This should fix it. There was another issue related to primitive restarts in index buffers with a base vertex offset but it looks like you already fixed it in the meantime.

Thanks for this fix! I have a test of primitive restart but unfortunately this bug didn't show up since it won't always cause problems :(.


Feature/improve the import routes

Add routes to tsconfig.json and use them in all the files

See #111


[Question] Auth Code Flow with token only in backend

Is this library suitable for classic auth flow where only the backend has the token and issues a session for the client?
I tried it but there was always a unwanted token request to the provider.
As described here:

... In Step 2, the OpenID Provider authenticates and authorizes the user for a particular application instance. So far, it looks like the Implicit flow. But in Step 3, a one-time-use code is passed back to the web server using a predefined Redirect URI. In Step 4, the web server passes the code, client ID, and client secret to the OpenID Provider’s token endpoint, and the OpenID Provider validates the code and returns a one-hour access token. In Step 5, the web server uses the access token to get further details about the user (if necessary) and establishes a session for the user.

I would be happy to add something to the docs about this in any case :)

Is this library suitable for classic auth flow where only the backend has the token and issues a session for the client?

This library is only designed for OAuth/OIDC client apps running in the browser (and that does not include native apps that deploy an embedded browser). So no, this library is not for to run server-side.

Thanks for clarifying, is there any chance for me to add to the wiki? I can't edit it, maybe consider moving it into a markdown file. I intended to use it client-side in an webapp just with the twist that no client secret or token is present in the frontend in any form.
It basically means this library would simply pass the auth code to the backend and recieve a session in return. Userinfo would come from the backend, not the provider because the frontend has no token.

No, I think you're confused. Or I'm confused as to what you expect an architecture to look like.

I intended to use it client-side in an webapp just with the twist that no client secret or token is present in the frontend in any form.

Yes, that would be satisfied by this library.

It basically means this library would simply pass the auth code to the backend and recieve a session in return.
Userinfo would come from the backend, not the provider because the frontend has no token.

This library maintains a session client-side. If you want a server-side session, then drive the protocol from your server, not from the client side.
The description for this project says:

About
OpenID Connect (OIDC) and OAuth2 protocol support for browser-based JavaScript applications

It's for building a client-side browser-based OIDC/OAuth2 client. That's it.


Display granularity by color

Hi
Is it possible to add gradients of value by color
Red = [0..50]
Green = [51..70]
Yellow = [71..100]
Bruno

Hi @anctsys, you can try with rgba like rgba(255, 0, 0, 0.2)

Can you give me an example to do this
https://cdn1.vectorstock.com/i/1000x1000/96/95/speedometer-green-orange-red-color-vector-20569695.jpg
Thanks

How to add separator ?


publish result to LTI

Description
Fixes #840
Notes (out of scope, known issues, hints for reviewing code, ...)  (optional)
I have a doubt about how to handle an error while publishing a result to LTI, what I did was displaying a toast saying:

if 403 forbidden (probably the http cookie token has expired ?):  "You might be unauthenticated anymore, please try relaunching the exercise. If the problem persits contact us."
For any other error: "An unknown error occurred while publishing your result".
The second message is unsatisfying in my opinion, but I didn't find any relevant option.

Test cases
:warning: Test must be done in localhost because the login module disallows redirecting to branch apps…  :confused:

[ ] Case 1:

Given I am the LTI demo user
When I go to the moodle platform
And I open network panel
And I re-submit the first level
Then I see the publish request is sent … but I got an error :unamused:

[ ] Case 2:

Given I am the usual user
When I go directly to the same task not through LTI
An I open my network panel
And I complete first level
Then I see no publish request is sent

The publish service now works, however the red error message is still displayed.

I have a doubt about how to handle an error while publishing a result to LTI, what I did was displaying a toast saying:
* if 403 forbidden (probably the http cookie token has expired ?):  "You might be unauthenticated anymore, please try relaunching the exercise. If the problem persits contact us."

* For any other error: "An unknown error occurred while publishing your result".
  The second message is unsatisfying in my opinion, but I didn't find any relevant option.

looks good to me

As it is quite urgent and other parts of the workflow have been fixed, I will merge it myself.

@ThomasJuster  I am going to merge it but I recommend you still review my changes.

I checked the last 2 commits, all good :heavy_check_mark:


Warning in order over proprietary Ultralight license

I don't think it's wise to advertise an MIT license without clearly warning people that this wraps a a project with a proprietary license that is not compatible with open source. Making a mistake here could get a company in a lot of trouble and might feel dishonest, though I'm certain your intentions are great. I appreciate that you made the wrapper and hope to experiment with it myself!

Fair enough, I've added an explicit warning inside of the Readme

Looks good! Thanks


How to activate, and keep frozen, multiple adapters?

Hello all,
I have been working on multiple adapters and part of my project requires that I activate all the loaded adapters. However, they must be frozen. I am running this code:
adapters_items = iter(tqdm.tqdm(adapters.items()))
first_item = next(adapters_items)
model_peft = PeftModel.from_pretrained(model, first_item[1], first_item[0], is_trainable=False)

for adapter_name, model_id in adapters_items:
    model_peft.load_adapter(model_id, adapter_name, is_trainable=False)

model_peft.base_model.set_adapter(list(adapters.keys()))

After some debugging, I see that the adapters are frozen (requires_grad=False) until the last line where I set the active adapters. After they are set to be active, requires_grad=True.
I see that set_adapter calls this function on all the LoraLayers, and how it sets the adapters to trainable.

https://github.com/huggingface/peft/blob/ebbff4023ad276cbcb2466fd7e99be7d3ae0ae11/src/peft/tuners/tuners_utils.py#L464-L484

How can I set the active adapter(s) while keeping them frozen?

I think this tutorial can solve this problem:
from peft import PeftMixedModel

base_model = ...  # load the base model, e.g. from transformers
# load first adapter, which will be called "default"
peft_model = PeftMixedModel.from_pretrained(base_model, <path_to_adapter1>)
peft_model.load_adapter(<path_to_adapter2>, adapter_name="other")
peft_model.set_adapter(["default", "other"])

The last line is necessary if you want to activate both adapters, otherwise, only the first adapter would be active.

Thanks!

Wanted to chime in: Only use PeftMixedModel if you want to mix different types of adapters, e.g. LoRA and LoHa. If all adapters are of the same type (e.g. all LoRA), please use PeftModel.
IIUC, the question is about requires_grad being True after calling set_adapter, but you want it to be False. What you should do instead is to call model_peft.required_grad_(False) to freeze all parameters. Or, if you want to only freeze certain parameters, something like this should work:
model_peft.base_model.set_adapter(list(adapters.keys()))

for name, param in model_peft.named_parameters():
    if <some check on `name`>:  # e.g. `if "lora" in name`
        param.requires_grad = False

Note that right now, calling set_adapter always activates the gradients for these adapters. I guess what we could do is to check if is_trainable=False for the respective configs and not activate the gradients for those. I guess this is somewhat niche, but might lead to fewer surprises in cases like this.

Ok, thank you for the clarification. Could I submit a PR to implement that check?

Could I submit a PR to implement that check?

Possibly, but it will unfortunately not be quite trivial. The problem is that set_adapter works on individual layers, which don't have a reference to all the configs. So this change would have to be a bit more involved. Another issue could be that if we change the behavior, it is technically backwards incompatible, not sure how big of a problem that would be in practice.

True, programs may be relying on this behavior (although peft is technically pre v1). This seems like pretty niche behavior to rely on, and the code currently implements a workaround that would not be negatively affected. It is clearly intentionally implemented this way, and as such would it be possible for me to add an option to one of the configs and submit a PR? This way, it would be an opt-in for now?

Alternatively, could we add a separate API, perhaps called set_adapter_keep_frozen?

Hmm, I feel like this use case is too narrow to warrant extending the API like this.
Maybe as a first step we could just document the fact that requires_grad will be set to True for the selected adapter(s) and False otherwise. We could also add a snippet for how to set all requires_grad to False if True is not desired to the docstring. WDYT?

That sounds like a great idea. Should I add this to all set_adapter functions?


feat: add build number to settings screen

Description
As the title. This will be helpful to identify which version of the nightly build you're on.
Test plan

Related issues
n/a
Backwards compatibility
Y
Network scalability
If a new NetworkId and/or Network are added in the future, the changes in this PR will:

[ ] Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

giving less reason to activate the debug menu

but what are the reasons for the end user to activate the debug menu? I thought it was only for the engineers (who are aware of its existence 😅)

giving less reason to activate the debug menu

but what are the reasons for the end user to activate the debug menu? I thought it was only for the engineers (who are aware of its existence 😅)

this is the context for adding visibility for the build number, i think there are genuine use cases for wanting to know the build number of an app outside of while you're engineering a feature. i suppose you could argue that only engineers have the nightly build, and they should be trusted to toggle the dev menu responsibly, but this is an extra step that doesn't seem necessary unless there's some harm to exposing this build number alongside the app version? in the event that we accidentally do a public release without bumping the app version, the build number will also become important for debugging

i thought it would bloat the UI with seemingly unnecessary information for the end users.
the standard version number is something that users see in the app stores and we could refer to it when communicating about the app.
as for debugging, i noticed that when some debugging/investigation is required, we usually require the end users to send their logs, which include the build number. in the discussion you mentioned, what if the user had the expected build number, but still experiencing the issue? we would ask them then to send the logs, right?
however, within the engineering team, we may want to have a shortcut to quickly reveal the build number without going the full circle with logs.
having that said, I don't want to die on that hill 😃 if it really could help us resolve some issues more quickly, then why not

i thought it would bloat the UI with seemingly unnecessary information for the end users. the standard version number is something that users see in the app stores and we could refer to it when communicating about the app.
as for debugging, i noticed that when some debugging/investigation is required, we usually require the end users to send their logs, which include the build number. in the discussion you mentioned, what if the user had the expected build number, but still experiencing the issue? we would ask them then to send the logs, right?
however, within the engineering team, we may want to have a shortcut to quickly reveal the build number without going the full circle with logs.
having that said, I don't want to die on that hill 😃 if it really could help us resolve some issues more quickly, then why not

I hear the feedback that the build number might just be unnecessary clutter for most users, and I agree that we can usually get this info from support tickets when debugging real user issues. That said, I still feel that having the app version + build number is a more precise way to identify what version of the app someone is using. This is especially helpful for the nightly build, which we rely on heavily to test new features—not just engineers, but also folks like Laura and Denisse. It seems much easier for them to include the build number in issue reports than having to dig into the debug menu (if we agree that generally, exposing the debug menu to non engineers is not desirable)


HomeAssistant: Add controls for Fan entities

Description
Adds basic support for Fan entities -- toggle, turn on, turn off, adjust speed.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@tonka3000 Thanks for the review. Added your suggestions:

Icon color when on:

Handle unavailable case:

Thanks for your cotribution @rspeicher 🔥


Tab Colours

In tabbed elements, the colour of the unselected tab is too close to the background colour
Would be good to a have a little more contrast in the colour palette
As a deliverable, you could just point us to the section of code which we need to edit to set this colour so that we choose the colour

@brandenchan this appears to be the Tabs component in components/Tabs.tsx the bg-blue-900/20 in line 15.

@agnieszka-m

@brandenchan this appears to be the Tabs component in components/Tabs.tsx the bg-blue-900/20 in line 15.


QuicTLS for 3.0.3

Updated the tip README commits, otherwise, reasonably clean rebase.

Why don't the checks run?!?!

Not worried about fuzzing.


Tutorial sorting issues

These are small ones, but it would be nice to fix them:

Right now, when I sort by anything apart from level, go into the tutorial detail and come back to tutorials page with browsers back button, sorting goes back to level but the sorting dropdown stays in the previous option, either as newset or last updated. Solution would be reset all filters
Featured content should always stay as the first tutorial independent from sorting. It can disappear with filtering but the featured content should not change its order after sorting.

Solved with #102


The template command fails to dump generated files if it cannot parse as valid yaml file

Output of helm version:
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:49Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.8-gke.12", GitCommit:"188432a69210ca32cafded81b4dd1c063720cac0", GitTreeState:"clean", BuildDate:"2019-11-07T19:27:01Z", GoVersion:"go1.12.11b4", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
GKE

The helm template command in helm 3.0.0 tries to parse the results as yaml files. So if there is a problem with the generated yaml file, I cannot see the file itself to check the problem.
With helm 2, the template command dumped the generated files without trying to parse it as yaml file, so I could check the problem. Now it is not possible.
Sample chart: templatebug.tar.gz
With helm 3:
$ helm3 template templatebug --debug
install.go:148: [debug] Original chart version: ""
install.go:165: [debug] CHART PATH: C:\templatebug

Error: YAML parse error on templatebug/templates/service.yaml: error converting YAML to JSON: yaml: line 4: found character that cannot start any token
helm.go:76: [debug] error converting YAML to JSON: yaml: line 4: found character that cannot start any token
YAML parse error on templatebug/templates/service.yaml
helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort
        /home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:129
helm.sh/helm/v3/pkg/releaseutil.SortManifests
        /home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:98
helm.sh/helm/v3/pkg/action.(*Configuration).renderResources
        /home/circleci/helm.sh/helm/pkg/action/install.go:455
helm.sh/helm/v3/pkg/action.(*Install).Run
        /home/circleci/helm.sh/helm/pkg/action/install.go:214
main.runInstall
        /home/circleci/helm.sh/helm/cmd/helm/install.go:209
main.newTemplateCmd.func1
        /home/circleci/helm.sh/helm/cmd/helm/template.go:63
github.com/spf13/cobra.(*Command).execute
        /go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:826
github.com/spf13/cobra.(*Command).ExecuteC
        /go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914
github.com/spf13/cobra.(*Command).Execute
        /go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
main.main
        /home/circleci/helm.sh/helm/cmd/helm/helm.go:75
runtime.main
        /usr/local/go/src/runtime/proc.go:203
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:1357

With helm 2:
$ helm template templatebug
---
# Source: templatebug/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: %!s(<nil>)
spec:
  ports:
    - port: 80
      targetPort: http
      protocol: TCP
      name: http

It seems that heml 3 uses install internally from template with dry-run and client-only set to true.
Install tries to detect hooks, and sort files accordingly. It needs to parse yaml files, but in case of error the whole command failes.
Maybe in case of client only, ordering errors should be swallowed...

Hey, i think I have same kind of problem - error converting YAML to JSON.
install.go:148: [debug] Original chart version: ""
install.go:165: [debug] CHART PATH: /home/valeriy.yakovenko/training/gitlab/gitstock/gitstockchart

Error: YAML parse error on gitstockchart/templates/job.yaml: error converting YAML to JSON: yaml: line 3: mapping values are not allowed in this context
helm.go:76: [debug] error converting YAML to JSON: yaml: line 3: mapping values are not allowed in this context
YAML parse error on gitstockchart/templates/job.yaml
helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort
	/home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:129
helm.sh/helm/v3/pkg/releaseutil.SortManifests
	/home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:98
helm.sh/helm/v3/pkg/action.(*Configuration).renderResources
	/home/circleci/helm.sh/helm/pkg/action/install.go:455
helm.sh/helm/v3/pkg/action.(*Install).Run
	/home/circleci/helm.sh/helm/pkg/action/install.go:214
main.runInstall
	/home/circleci/helm.sh/helm/cmd/helm/install.go:209
main.newTemplateCmd.func1
	/home/circleci/helm.sh/helm/cmd/helm/template.go:63
github.com/spf13/cobra.(*Command).execute
	/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:826
github.com/spf13/cobra.(*Command).ExecuteC
	/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914
github.com/spf13/cobra.(*Command).Execute
	/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
main.main
	/home/circleci/helm.sh/helm/cmd/helm/helm.go:75
runtime.main
	/usr/local/go/src/runtime/proc.go:203
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1357

Hi @jakethedogg ,
May I ask for your helm chart?

Hi, @zwwhdls !!
gitstockchart/template/job.yaml - content
{{- range $index, $value := .Values.repos }}
{{ $sshkey := "`name of file`" }}
apiVersion: batch/v1
kind: Job
metadata:
  name: gitstock-job-{{ $index }}
spec:
  template:
    spec:
      containers:
      - name: gitstock-job
        image: "{{ $.Values.image.repository }}:{{ $.Values.image.tag }}"
        env:
          - name: google-creds
            valueFrom:
              secretKeyRef:
                name: HIDED
                key: HIDED
          - name: ssh-key
            valueFrom:
              secretKeyRef:
                name: HIDED
                key: HIDED
        command: ["./gitstock.sh"]
        args: ["--licence-key=$(google-creds)", "--ssh-key={{ $.Files.Get $sshkey }}", "-g", "--repo-name={{ .repo_name }}", "--repo-url={{ .repo_url }}", "{{ .repo_name }}"]
      restartPolicy: Never
  backoffLimit: 2
---
{{- end }}

content of gitstockchart/values.yaml
image:
  repository: zensoftwarenl/gitstock
  tag: latest
repos:
  0:
    repo_name: slackpeek
    repo_url: git@gitlab.com:zensoftwarenl/slackpeek.git
  1:
    repo_name: gitstock
    repo_url: git@gitlab.com:zensoftwarenl/gitstock.git

Hi @jakethedogg ,
I can't reproduce it with your chart. 😂

Hi @jakethedogg ,
I can't reproduce it with your chart.

@zwwhdls. I think it is because of secrets which i used for variables. I developed this chart for internal usage, not for public)))
I am not well familiar with HELM. The thing is that this way worked for me, before the release of HELM 3. And I can not understand what changed, that this chart stop working

Hi @jakethedogg ,
I delete the env of secret and run "helm install", it works well. I don't know what happened to your chart. But I really know what happened to the chart of @vazul .
It's because that Helm load the files and then render the templates to yaml with values.yaml. But in the second way, the template becomes:
apiVersion: v1
kind: Service
metadata:
  name: %!s(<nil>)
spec:
  ports:
    - port: 80
      targetPort: http
      protocol: TCP
      name: http

something wrong in metadata.name. In Helm v3, after rendering templates, it also sort them for hook. Codes are: https://github.com/helm/helm/blob/master/pkg/releaseutil/manifest_sorter.go#L128. When yaml.Unmarshal() got the wrong string in file, it raise error.
I don't think it is a bug for Helm. And the way to avoiding this error is to make sure values.yaml can marshal templates correctly.

@zwwhdls, can you, please, past here how template job.yaml looks like, after yours changes and past here values.yaml file as well?

@jakethedogg
job.yaml:
{{- range $index, $value := .Values.repos }}
{{ $sshkey := "`name of file`" }}
apiVersion: batch/v1
kind: Job
metadata:
  name: gitstock-job-{{ $index }}
spec:
  template:
    spec:
      containers:
      - name: gitstock-job
        image: "{{ $.Values.image.repository }}:{{ $.Values.image.tag }}"
        command: ["./gitstock.sh"]
        args: ["--licence-key=$(google-creds)", "--ssh-key={{ $.Files.Get $sshkey }}", "-g", "--repo-name={{ .repo_name }}", "--repo-url={{ .repo_url }}", "{{ .repo_name }}"]
      restartPolicy: Never
  backoffLimit: 2
---
{{- end }}

values.yaml:
image:
  repository: zensoftwarenl/gitstock
  tag: latest

repos:
  0:
    repo_name: slackpeek
    repo_url: git@gitlab.com:zensoftwarenl/slackpeek.git
  1:
    repo_name: gitstock
    repo_url: git@gitlab.com:zensoftwarenl/gitstock.git

"helm install hello hello" return:
# helm install hello hello
NAME: hello
LAST DEPLOYED: Thu Nov 28 10:38:13 2019
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None

"helm template hello hello" return:
# helm template hello hello
---
# Source: hello/templates/job.yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: gitstock-job-0
spec:
  template:
    spec:
      containers:
      - name: gitstock-job
        image: "zensoftwarenl/gitstock:latest"
        command: ["./gitstock.sh"]
        args: ["--licence-key=$(google-creds)", "--ssh-key=", "-g", "--repo-name=slackpeek", "--repo-url=git@gitlab.com:zensoftwarenl/slackpeek.git", "slackpeek"]
      restartPolicy: Never
  backoffLimit: 2
---
# Source: hello/templates/job.yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: gitstock-job-1
spec:
  template:
    spec:
      containers:
      - name: gitstock-job
        image: "zensoftwarenl/gitstock:latest"
        command: ["./gitstock.sh"]
        args: ["--licence-key=$(google-creds)", "--ssh-key=", "-g", "--repo-name=gitstock", "--repo-url=git@gitlab.com:zensoftwarenl/gitstock.git", "gitstock"]
      restartPolicy: Never
  backoffLimit: 2

Created pull request #7094 in which helm will dump the yaml content that cannot be unmarshalled. It will dump only one yaml content in case yaml files has multiple document:
apiVersion: v1
kind: Service
metadata:
  name: good-name
spec:
  ports:
    - port: 443
      targetPort: https
      protocol: TCP
      name: https
---
apiVersion: v1
kind: Service
metadata:
  name: {{ printf "%s" .Values.serviceName }}
spec:
  ports:
    - port: 80
      targetPort: http
      protocol: TCP
      name: http

$ helm install templatebug --dry-run .
Error: YAML parse error on templatebug/templates/service.yaml (in yaml document 2)
---
apiVersion: v1
kind: Service
metadata:
  name: %!s(<nil>)
spec:
  ports:
    - port: 80
      targetPort: http
      protocol: TCP
      name: http
: error converting YAML to JSON: yaml: line 4: found character that cannot start any token

Hey @zwwhdls !
I tried to install your variant of chart and it works for me too! But I still have a question, why it doesn`t work with env variables?
I did one more research, so in case if remove second line in template "{{ $sshkey := "ssh-key.pem" }}" and do not use .File.Get function it works and installing the chart with no problem!
This is how chart look like:
{{- range $index, $value := .Values.repos }}
apiVersion: batch/v1
kind: Job
metadata:
  name: gitstock-job-{{ $index }}
spec:
  template:
    spec:
      containers:
      - name: gitstock-job
        image: "{{ $.Values.image.repository }}:{{ $.Values.image.tag }}"
        env:
          - name: google-creds
            valueFrom:
              secretKeyRef:
                name: HIDED
                key: HIDED
          - name: ssh-key
            valueFrom:
              secretKeyRef:
                name: HIDED
                key: HIDED
        command: ["./gitstock.sh"]
        args: ["--licence-key=$(google-creds)", "--ssh-key=$(ssh-key)", "-g", "--repo-name={{ .repo_name }}", "--repo-url={{ .repo_url }}", "{{ .repo_name }}"]
      restartPolicy: Never
  backoffLimit: 2
---
{{- end }}

The values.yaml file stay the same as well. And in this way chart works well.
But I need to make it work like it was in initial variant! And i really do not understand why it give me an error. Including that factor, that it does not work in different variants of template, but essentially the error is the same

I had a similar issue with my chart, where my stupid use of whitespace trimming led to bad Yaml outputs. The problem is, its really difficult to diagnose where the problem is, because instead of giving you the bad yaml, which you could immediately run through a yaml parser, and see your error, it just tells you what file the error is on, and gives you a line number, which could be in any number of places if you have multiple definitions inside a file.

fixed in #7556, which will be in Helm 3.2.0.

fixed in #7556, which will be in Helm 3.2.0. Use the --debug flag to display the invalid YAML.

Doesn't work.
contra-file-upload-api on  master via ⬢ v14.5.0
❯ helm version
version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"dirty", GoVersion:"go1.14.3"}

contra-file-upload-api on  master via ⬢ v14.5.0
❯ helm install contra-file-upload-api charts/server --debug --values .server.values.yaml --set app.datadog.env=production --set app.datadog.service=contra-file-upload-api --set app.datadog.version=foo
install.go:159: [debug] Original chart version: ""
install.go:176: [debug] CHART PATH: /Users/gajus/Documents/dev/contra/contra-file-upload-api/charts/server

Error: YAML parse error on contra-file-upload-api/templates/deployment.yaml: error converting YAML to JSON: yaml: line 49: mapping values are not allowed in this context
helm.go:84: [debug] error converting YAML to JSON: yaml: line 49: mapping values are not allowed in this context
YAML parse error on contra-file-upload-api/templates/deployment.yaml
helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort
	/private/tmp/helm-20200619-73670-pk36oo/pkg/releaseutil/manifest_sorter.go:146
helm.sh/helm/v3/pkg/releaseutil.SortManifests
	/private/tmp/helm-20200619-73670-pk36oo/pkg/releaseutil/manifest_sorter.go:106
helm.sh/helm/v3/pkg/action.(*Configuration).renderResources
	/private/tmp/helm-20200619-73670-pk36oo/pkg/action/action.go:159
helm.sh/helm/v3/pkg/action.(*Install).Run
	/private/tmp/helm-20200619-73670-pk36oo/pkg/action/install.go:238
main.runInstall
	/private/tmp/helm-20200619-73670-pk36oo/cmd/helm/install.go:229
main.newInstallCmd.func1
	/private/tmp/helm-20200619-73670-pk36oo/cmd/helm/install.go:117
github.com/spf13/cobra.(*Command).execute
	/private/tmp/helm-20200619-73670-pk36oo/.brew_home/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842
github.com/spf13/cobra.(*Command).ExecuteC
	/private/tmp/helm-20200619-73670-pk36oo/.brew_home/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950
github.com/spf13/cobra.(*Command).Execute
	/private/tmp/helm-20200619-73670-pk36oo/.brew_home/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887
main.main
	/private/tmp/helm-20200619-73670-pk36oo/cmd/helm/helm.go:83
runtime.main
	/usr/local/Cellar/go/1.14.3/libexec/src/runtime/proc.go:203
runtime.goexit
	/usr/local/Cellar/go/1.14.3/libexec/src/runtime/asm_amd64.s:1373

It doesn't work for us as well.
should we have this one as re-opened or it's better to create another one?

Turns out you have to use helm template --debug [... all the same parameters].
It wasn't obvious.

I must be missing something because this doesn't work for me. When it encounters the faulty file (I'm quite sure it's an indentation issue), I just get the error and no file:
helm template -f test_4_common_config.yml --debug mail

...
---
# Source: mail/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
...
Error: YAML parse error on mail/templates/statefulset.yaml: error converting YAML to JSON: yaml: line 84: mapping values are not allowed in this context
helm.go:84: [debug] error converting YAML to JSON: yaml: line 84: mapping values are not allowed in this context
YAML parse error on mail/templates/statefulset.yaml
elm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort
        /private/tmp/helm-20200619-73670-pk36oo/pkg/releaseutil/manifest_sorter.go:146
helm.sh/helm/v3/pkg/releaseutil.SortManifests
        /private/tmp/helm-20200619-73670-pk36oo/pkg/releaseutil/manifest_sorter.go:106
helm.sh/helm/v3/pkg/action.(*Configuration).renderResources
        /private/tmp/helm-20200619-73670-pk36oo/pkg/action/action.go:159
helm.sh/helm/v3/pkg/action.(*Install).Run
        /private/tmp/helm-20200619-73670-pk36oo/pkg/action/install.go:238
main.runInstall
        /private/tmp/helm-20200619-73670-pk36oo/cmd/helm/install.go:229
main.newTemplateCmd.func1
        /private/tmp/helm-20200619-73670-pk36oo/cmd/helm/template.go:66
github.com/spf13/cobra.(*Command).execute
        /private/tmp/helm-20200619-73670-pk36oo/.brew_home/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842
github.com/spf13/cobra.(*Command).ExecuteC
        /private/tmp/helm-20200619-73670-pk36oo/.brew_home/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950
github.com/spf13/cobra.(*Command).Execute
        /private/tmp/helm-20200619-73670-pk36oo/.brew_home/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887
main.main
        /private/tmp/helm-20200619-73670-pk36oo/cmd/helm/helm.go:83
runtime.main
        /usr/local/Cellar/go/1.14.3/libexec/src/runtime/proc.go:203
runtime.goexit
        /usr/local/Cellar/go/1.14.3/libexec/src/runtime/asm_amd64.s:1373

helm version
version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"dirty", GoVersion:"go1.14.3"}

This is still broken in 3.4.1
[aianus@mbp ~/src/pricing/chart (k8s)]$ helm template --debug mydemo ./
install.go:172: [debug] Original chart version: ""
install.go:189: [debug] CHART PATH: /Users/aianus/src/pricing/chart

---
# Source: pricing/templates/deployment.yaml
Error: 'error converting YAML to JSON: yaml: line 37: did not find expected key'
[aianus@mbp ~/src/pricing/chart (k8s)]$

Thanks @gajus! It wasn't obvious indeed!

@aianus I too thought it was still broken until I did helm template --debug ... | grep <broken file>. The files are outputted in some random order, which means the broken file can appear way before the error message, it probably isn't the last one that helm outputs.

Why is this closed. I also get mad to find the issue without getting valuable info, like the printed out yaml (even invalid)
{{- define "myChart.Name" -}}
{{- if .Values.canary.enabled }}
{{- printf "%s-canary" .Chart.Name -}}
{{- else }}
{{- printf "%s" .Chart.Name -}}
{{- end }}
{{- end -}}

{{- define "labels" -}}
key: {{ .Values.app.key }}
name: {{ .Values.app.name }}
version: {{ .Values.app.version | quote }}
canary: {{ .Values.canary.enabled | quote }}
app: {{ printf "%s-%s" .Chart.Name .Chart.Version }}
chart: {{ printf "%s-%s" .Chart.Name .Chart.Version }}
release: {{ include "myRelease.Name" . }}
heritage: {{ .Release.Service }}
helm.sh/chart: {{ printf "%s-%s" .Chart.Name .Chart.Version }}
app.kubernetes.io/name: {{ .Values.app.name }}
app.kubernetes.io/version: {{ .Values.app.version | quote }}
app.kubernetes.io/instance: {{ include "myRelease.Name" . }}
app.kubernetes.io/managed-by: {{ .Release.Service }}
{{- end -}}

{{- define "annotations" -}}
meta.helm.sh/release-name: {{ include "myRelease.Name" . }}
meta.helm.sh/release-namespace: {{ .Release.Namespace }}
{{- end -}}

kind: ConfigMap
apiVersion: v1
metadata:
  name: {{ (include "myChart.Name" .) }}
  namespace: {{ .Release.Namespace }}
  labels:
    {{- include "labels" . | nindent 4 }}
  annotations:
    {{- include "annotations" . | nindent 4 }}

Error: UPGRADE FAILED: YAML parse error on myservice/templates/configmap.yaml: error converting YAML to JSON: yaml: line 6: could not find expected ':'
helm.go:81: [debug] error converting YAML to JSON: yaml: line 6: could not find expected ':'
YAML parse error on myservice/templates/configmap.yaml
helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort
	/home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:146
helm.sh/helm/v3/pkg/releaseutil.SortManifests
	/home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:106
helm.sh/helm/v3/pkg/action.(*Configuration).renderResources
	/home/circleci/helm.sh/helm/pkg/action/action.go:165
helm.sh/helm/v3/pkg/action.(*Upgrade).prepareUpgrade
	/home/circleci/helm.sh/helm/pkg/action/upgrade.go:215
helm.sh/helm/v3/pkg/action.(*Upgrade).Run
	/home/circleci/helm.sh/helm/pkg/action/upgrade.go:124
main.newUpgradeCmd.func2
	/home/circleci/helm.sh/helm/cmd/helm/upgrade.go:155
github.com/spf13/cobra.(*Command).execute
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:850
github.com/spf13/cobra.(*Command).ExecuteC
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:958
github.com/spf13/cobra.(*Command).Execute
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:895
main.main
	/home/circleci/helm.sh/helm/cmd/helm/helm.go:80
runtime.main
	/usr/local/go/src/runtime/proc.go:204
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1374
UPGRADE FAILED
main.newUpgradeCmd.func2
	/home/circleci/helm.sh/helm/cmd/helm/upgrade.go:157
github.com/spf13/cobra.(*Command).execute
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:850
github.com/spf13/cobra.(*Command).ExecuteC
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:958
github.com/spf13/cobra.(*Command).Execute
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:895
main.main
	/home/circleci/helm.sh/helm/cmd/helm/helm.go:80
runtime.main
	/usr/local/go/src/runtime/proc.go:204
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1374

Just to add a note that sometimes the syntax error appears overlapped with any other valid yaml output rather than appearing with the invalid yaml.

Why is this closed. I also get mad to find the issue without getting valuable info, like the printed out yaml (even invalid)

Please remember to run helm template --debug instead of helm upgrade --debug.
I always forget it myself and get frustrated too!

Hello.
It looks like helm template --debug works to dump invalid Chart files, but not if it's the values.yaml file itself which is invalid:
$$$ helm template --debug dummy dummy.tgz
install.go:200: [debug] Original chart version: ""
install.go:217: [debug] CHART PATH: /home/ops/dummy.tgz

Error: cannot load values.yaml: error converting YAML to JSON: yaml: line 2: did not find expected key
helm.go:84: [debug] error converting YAML to JSON: yaml: line 2: did not find expected key
cannot load values.yaml
helm.sh/helm/v3/pkg/chart/loader.LoadFiles
        helm.sh/helm/v3/pkg/chart/loader/load.go:108
helm.sh/helm/v3/pkg/chart/loader.LoadArchive
        helm.sh/helm/v3/pkg/chart/loader/archive.go:195
helm.sh/helm/v3/pkg/chart/loader.LoadFile
        helm.sh/helm/v3/pkg/chart/loader/archive.go:65
helm.sh/helm/v3/pkg/chart/loader.FileLoader.Load
        helm.sh/helm/v3/pkg/chart/loader/archive.go:43
helm.sh/helm/v3/pkg/chart/loader.Load
        helm.sh/helm/v3/pkg/chart/loader/load.go:62
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:226
main.newTemplateCmd.func2
        helm.sh/helm/v3/cmd/helm/template.go:88
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.6.1/command.go:916
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.6.1/command.go:1044
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.6.1/command.go:968
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
        runtime/proc.go:250
runtime.goexit
        runtime/asm_amd64.s:1598

helm version returns the following:
version.BuildInfo{Version:"v3.11.3", GitCommit:"323249351482b3bbfc9f5004f65d400aa70f9ae7", GitTreeState:"clean", GoVersion:"go1.20.3"}
My values file:
test:
  {{ if true -}}
  bla: bla
  {{- end }}

I'm suspecting that it is not "templating" my values file, i.e. it does not resolve the {{ if true -}} found in it, but interprets the { as a YAML dictionary  header.
So, I can't do something similar to the following in the values file of my Chart (the real use case that I'm failing to achieve):
appli:
  ...
  {{ if hasKey .Values.extra -}}
  extra:
    {{ .Values.extra | toYaml | indent 4 }}
  {{- end }

Thanks for your attention


[Feature Request]: Clean up examples/demos page header on documentation site

Contact Details
No response
Describe the new feature versus the current behaviour
https://agjcalendar.agjjquery.org/examples-and-demo/
The current header includes an older version of jQuery (3.7.0 instead of 3.7.1) and the comments are // JavaScript comments instead of  XML/HTML comments
Is there any risk this change will not be backwards compatible with current integrations?
No response
Any other information
No response

Fixed as part of v1.1.0


Updated README.md, Index.md, UserGuide.md and AboutUs.md

Added some file paths in .gitignore as well as my project created them automatically

Related Issues #3, #4, #5

Codecov Report

Merging #26 (b04574c) into master (7436443) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #26   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


Mouse button down event not emitted when one button is already pressed

Godot version: 3.1 beta 8 & 10 Tested
OS/device including version: Linux Kubuntu 18.10
Issue description:
When a mouse button is pressed and held, and a second mouse button gets pressed, the button down event will not be emitted for the second event.
Steps to reproduce:
Press MB1 and hold it, press MB2 and notice that the event for the 2. event.is_pressed() is not called.
Releasing MB1 and MB2 does each create the button up event as expected.
Use case: MB1 pressed triggers aim, MB2 pressed triggers fire.
Minimal reproduction project:
func _unhandled_input(event):
	if( event is InputEventMouseButton ):
		print("MB: ", event.button_index, event.is_pressed() )

Output is:
MB: 1True
MB: 2False
MB: 1False
Output desired:
MB: 1True
MB: 2True
MB: 2False
MB: 1False

Confirmed in 4da21d1c. It works fine in 3.0.6.


bug fix about down-selected source number

This PR fixes a bug when down-selecting the source galaxy numbers, the strong lensing probability was computed on the total galaxy population while only being drawn from the down-selected one.
In addition I changed some definitions to property returns

@nkhadka21 there is one line not being tested which stems from the ABC method. If you can review it today that would be great, such that we can merge the fix. Thank you!(Initial report for the issue by @bryce-wedig)


EVP_KDF_fetch fails to get TLS13-KDF

According to the documentation (https://www.openssl.org/docs/manmaster/man7/EVP_KDF-TLS13_KDF.html), I should be able to get TLS13-KDF with EVP_KDF_fetch, as I have done for TLS1-PRF, PBKDF, SSHKDF, etc.
However, when loading it thusly:
    EVP_KDF *tls13kdf = NULL;
    EVP_KDF_CTX *kctx = NULL;

    tls13kdf = EVP_KDF_fetch(libctx, "TLS13-KDF", "fips=yes");
    if (tls13kdf == NULL)
        die("no TLS object object");
    kctx = EVP_KDF_CTX_new(tls13kdf);
    if (!kctx)
        die("no context");
    EVP_KDF_free(tls13kdf);

I receive the following:
ERROR: died at no TLS object object
800BD411FD7F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto/evp/evp_fetch.c:346:Non-de
fault library context, Algorithm (TLS13-KDF : 0), Properties (fips=yes)

The library context is properly initialized and the FIPS config is loaded. The issue occurs similarly even if I use a default context with NULL parameters.
Is this a bug, or is it not fully implemented? Between the documentation and the test recipies, I assumed it would be.

Which OpenSSL version are you using? This KDF was only very recently added and does not appear in 3.0-beta2. You can only get it if you are using the git master branch version of OpenSSL.

Which OpenSSL version are you using? This KDF was only very recently added and does not appear in 3.0-beta2. You can only get it if you are using the git master branch version of OpenSSL.

I am using master as of about a half an hour ago. When I pulled it, it said beta3-dev.

@mattcaswell error was on my end. My LD_LIBRARY_PATH was still pointing to a location with an earlier build, although I linked against the latest master.
false alarm.