create argo-workflows guide

Short guide on how to successfully use Dagger in Argo Workflows based on the Argo workflows demo here.
Original PR here https://github.com/dagger/dagger/pull/5678
Fixes https://linear.app/dagger/issue/DOCS-69/docs-for-dagger-in-argo-workflows

I've pushed a small change. I wanted to go through the entire guide, but had to stop at the Argo setup guide since my Docker is remote. Will re-start from the host where Docker is running.
I know that you are all over the #5446 follow-up changes for Step 3 @kpenfound. Will check on this later today.
It will be so great to get this one merged too 💪

updated and ready for review @vikram-dagger @gerhard

Now that dagger-runner are working as they should again, I will go through the new content.
Do you want to commit your changes @vikram-dagger so that we can get this one merged & published?

Do you want to commit your changes @vikram-dagger so that we can get this one merged & published?

I would like to wait for @kpenfound to review my suggestions and commit those he agrees with.

I was able to install Argo on the server & locally. I was also able to submit the workflow:

The problem is that the EKS cluster that I used for testing is not able to provision persistent volumes. The workflow never starts since there is nothing to create the gomodcache volume:

Will provision a new EKS cluster and figure out what we are are missing.


Bug: Getting 200 in refresh-token api for empty token

can you share more context?
I didn't totally get the issue and you how you got it

I fixed the issue, now it's look like this.

Yes, I had the same issue. I now throw an AuthorizationException, catch it in the controller and set the HTTP response code to 401 for such use cases where the token is missing on the refresh API. Thanks @coderbdsust for sharing this.


Add GCMaxPauseCheck for restarting an app experiencing long GC pauses.

You can use this to aggressively restart an application (with safe draining) if the GC pause time starts to exceed some threshold.

LGTM


unable to import evaluate

AttributeError                            Traceback (most recent call last)
 in <cell line: 1>()
----> 1 import evaluate
2 indic_glue_metric=evaluate.load('indic_glue','wiki-ner.ta')
10 frames
/usr/local/lib/python3.10/dist-packages/evaluate/init.py in
27 del version
28
---> 29 from .evaluation_suite import EvaluationSuite
30 from .evaluator import (
31     AutomaticSpeechRecognitionEvaluator,
/usr/local/lib/python3.10/dist-packages/evaluate/evaluation_suite/init.py in
5 from typing import Callable, Dict, Optional, Union
6
----> 7 from datasets import Dataset, DownloadMode, load_dataset
8 from datasets.utils.version import Version
9
/usr/local/lib/python3.10/dist-packages/datasets/init.py in
41 del version
42
---> 43 from .arrow_dataset import Dataset
44 from .arrow_reader import ReadInstruction
45 from .builder import ArrowBasedBuilder, BeamBasedBuilder, BuilderConfig, DatasetBuilder, GeneratorBasedBuilder
/usr/local/lib/python3.10/dist-packages/datasets/arrow_dataset.py in
63
64 from . import config
---> 65 from .arrow_reader import ArrowReader
66 from .arrow_writer import ArrowWriter, OptimizedTypedSequence
67 from .download.download_config import DownloadConfig
/usr/local/lib/python3.10/dist-packages/datasets/arrow_reader.py in
28 import pyarrow.parquet as pq
29
---> 30 from .download.download_config import DownloadConfig
31 from .naming import _split_re, filenames_for_dataset_split
32 from .table import InMemoryTable, MemoryMappedTable, Table, concat_tables
/usr/local/lib/python3.10/dist-packages/datasets/download/init.py in
7
8 from .download_config import DownloadConfig
----> 9 from .download_manager import DownloadManager, DownloadMode
10 from .streaming_download_manager import StreamingDownloadManager
/usr/local/lib/python3.10/dist-packages/datasets/download/download_manager.py in
33 from ..utils.info_utils import get_size_checksum_dict
34 from ..utils.logging import get_logger, is_progress_bar_enabled, tqdm
---> 35 from ..utils.py_utils import NestedDataStructure, map_nested, size_str
36 from .download_config import DownloadConfig
37
/usr/local/lib/python3.10/dist-packages/datasets/utils/py_utils.py in
38 import dill
39 import multiprocess
---> 40 import multiprocess.pool
41 import numpy as np
42 from packaging import version
/usr/local/lib/python3.10/dist-packages/multiprocess/pool.py in
607 #
608
--> 609 class ThreadPool(Pool):
610
611     from .dummy import Process
/usr/local/lib/python3.10/dist-packages/multiprocess/pool.py in ThreadPool()
609 class ThreadPool(Pool):
610
--> 611     from .dummy import Process
612
613     def init(self, processes=None, initializer=None, initargs=()):
/usr/local/lib/python3.10/dist-packages/multiprocess/dummy/init.py in
85 #
86
---> 87 class Condition(threading._Condition):
88     # XXX
89     if sys.version_info < (4, 0):
AttributeError: module 'threading' has no attribute '_Condition'

Upgrading datasets and multiprocess solved the issue
pip install --upgrade datasets multiprocess


Hide buttons in Deployment/Config tabs when in view mode

https://github.com/rancher/dashboard/issues/5035
Removed buttons for the following tabs of Demployment/Config viiew:
General

Labels & Annotations

Pod Scheduling

KeyValue.vue

As the value removeAllowed is not computed nor adopted, it has been replaced by isView, which seems to be the reason of this leftover; prop has been removed accordingly

ArrayListGrouped.vue

IsDisabled computation seems not working or not integrated correctly, as the value returns false also in case of view mode; therefore it has been replaced with mode, while prop is kept to avoid issues
CanAdd has been added to allow enforced cases, default value left to true to match existing cases
mode/isView logic has also been added to match other existing cases, as part of the issue requirement to cover global scope.

Extras

Attributes to the buttons have been added for future unit/E2E tests purposes; value defined based on Cypress guidelines https://docs.cypress.io/guides/references/best-practices
Added code comments for components which may be listed in a styleguide
Added type for form modes, assumed by constant values

After playing around with npx and Jest, it seemed inconvenient to invest further time trying to create tests without a proper integration to the project.


mesh handler

Will update details. Just trying to see what CI thinks

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

Test name
Commit
Details
Rerun command

lint_istio
b3612c7d3e65a773f10e611d4a3ed534578ff74d
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
c2a022dd77f813797794dd7e80e2d03616cad903
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-local-tests_istio
d6b16438fedf3a83989b0adcfc8ab0987ee0c772
link
/test integ-local-tests_istio

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

/test integ-local-tests_istio


🕵 Investigate failures in AWS Nuke job

User Story
As a Modernisation Platform Engineer
I want to investigate our AWS Nuke job
So that we identify and remediate any shortcomings in our current approach
Value / Purpose
Our AWS Nuke and Nuke Rebuild jobs could do with a pass to ensure they're performing as we expect them to.
At present it appears that we have no sight of errors, so at a minimum we should add Slack notifications to them on failure. Further to this, we should look into potential reasons for environments not being rebuilt such as in this example.
Useful Contacts
@dms1981
Additional Information
No response
Definition of Done

[x] Slack notifications added
[x] Investigation into failed nukes complete
[x] Investigation into failed rebuilds complete

The failure for the nuke-rebuilds appears pretty simple. It looks like the SSM parameter for the modernisation-platform account-id is deleted, and not rebuilt separate in time through the scheduled baselines for the rebuild to run. Since we exclude other baselines-created values through the nuke config template, I think we're less likely to have issues by preventing the parameter from being nuked than by trying to juggle schedules.

I'll leave this issue open until I have a chance to observe the behaviour of our Nuke job. However, we will now have Slack alerts on failures. We can see that the failures of the Nuke jobs appear to be only conditional for certain resources (EG, security groups with dependent resources) so I'm hopeful that the more recent version will resolve those. For the rebuilds those appear pretty simple - they're missing SSM parameters the rebuild relies on - so those will either work, or will have further data points for me to refer to and filter.

Rebuilds were successful over the weekend, notifications were successful, and I've added some extra filtering to cover the failures of the Nuke jobs following the version upgrade. If I was going to gold plate this a little I'd like to get a richer notification coming through on Slack, but this covers the essentials.


Default plugin support

Eventually, I'd like this theme to support a few common plugins out of the box. The basic way I intend for this to work is to have branches that add support and basic pages for different plugins, and to keep these branches always in a state where they can be merged into your project.
So for example, to create a new theme that supports RainLab.User and RainLab.Blog, the installation would be as follows.
git clone git@github.com:scottbedard/vuetober-spa.git mytheme

cd mytheme

git merge rainlab-user

git merge rainlab-blog

This repository provide's some great insight into user authentication and middlewares:
https://github.com/cretueusebiu/laravel-vue-spa/tree/master/resources/js
i've already integrated it into this project

That's awesome, I'd love to see what you've come up with! The pattern I generally use to interface with RainLab.User is to use GivingTeam.Auth to expose endpoints, and then using our beforeEach navigation guard to check meta data about the route.

Ill make a fork with the changes, at the same time i could use some help working with a plugin i made for vue regarding permissions https://gist.github.com/Teranode/864842c9f6b6aa60dfe0e4869462f2e1.
I use Vue.use(Gate, { user: store.getters['user/user]) (the store is the problem). When I put this as a plugin and the plugin tries to get the store i get an error that the store isnt there ( im guessing that the Gate is loading before the store)


global var "GLOBALCAN" fails

i'm using the amd variant and was thus looking for a way to avoid canjs' global export. apparently "GLOBALCAN" needs be set to false in tandem with uglify's dead_code option. it works! but not for can/amd/can/view/stache/utils.js which is missing can in its argument list.
i would have annotated the exact code line on github but i couldn't find the amd-build. i guess you're generating that with stealjs so i opened an issue.

Just working on releasing a 2.3.1 which should fix this via #2021

great! could you do the same for canjs/amd/can/view/mustache.js > window.Mustache?

I wonder why Mustache gets added to the window. I'll add a condition to only do this when GLOBALCAN is true.

I'm currently upgrading from 2.1.1 to 2.3.1. the global Mustache still leaks.


[DiagnosticsQoI] Bail on nil literal diagnostics if the source is Optional

A tiny change to get back some QoI because it isn't sufficient to just observe that the initializer of a pattern binding failed a contextual conversion from nil.  If we fire the existing diagnostic, it would pile on optional sugar and never tell the user what actually went wrong.
// Before
var _: Array? = nil // nil cannot initialize specified type 'Array?', add '?' to form the optional type 'Array??'
var _: Array?? = nil // nil cannot initialize specified type 'Array??', add '?' to form the optional type 'Array???'
var _: Array??? = nil // nil cannot initialize specified type 'Array???', add '?' to form the optional type 'Array????'
// ...

// After
var _: Array? = nil // generic parameter 'Element' could not be inferred

"Reported" by a Redditor.

@swift-ci please smoke test

⛵

Wow, it was fast.


Made requested changes to the cheatsheet.md file

Check all applicable boxes below (put an x in between the square brackets, with no spaces)

[x] This is to fix an issue. Issue #: #74
[ ] If I modified anything other than comments, I ran npm run build and npm test

Summary
This pull request makes it so you can loop over an array

Awesome! Thanks @RyanLilla! You're now a Squirrelly contributor!


MSID: 90050 Version: 1 DOI: 2<IP_ADDRESS>0081

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=90050)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/90050/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[ ] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>0081)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/90050/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/90050)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/90050

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/90050

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/90050/v1/90050-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/90050)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Full text/meca package not yet available.


DocService: letting a user copy a debug request as a cURL command

It would be useful if DocService provides a way to copy the current debug request as a cURL command.

May I take a look at this?


Godot double .net project still uses Vector3(float,)

Tested versions
v4.2.stable.mono.custom_build (copied by clicking the version shown in the editor (bottom bar))
System information
Godot v4.2.stable.mono unknown - Windows 10.0.22621 - Vulkan (Forward+) - dedicated GeForce GTX 1650 Ti () - Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 Threads)
Issue description
I compiled Godot with module_mono_enabled=yes, and precision=double parameters.
In Visual Studio Code the line "new Vector3(0d,1d,0d)" throws

CS1503 cannot convert from double to float

even after project build.
I decompiled GodotSharp.dll build by engine compiler and there is struct Vector3 with double X,Y,Z and its valid constructor
when run with float parameters:

Method not found: 'Void Godot.Vector3..ctor(Single, Single, Single)'
at Godot.Node.InvokeGodotClassMethod

It can be that Godot still use an old C# reference?
Steps to reproduce
https://github.com/godotengine/godot/tree/4.2-stable - source code
in source folder cmd:
scons p=windows target=editor module_mono_enabled=yes precision=double
scons p=windows target=template_debug module_mono_enabled=yes precision=double
scons p=windows target=template_release module_mono_enabled=yes precision=double
"bin/godot.windows.editor.double.x86_64.mono" --headless --generate-mono-glue modules/mono/glue --precision=double
"./modules/mono/build_scripts/build_assemblies.py" --godot-output-dir=./bin --godot-platform=windows --precision=double

create new project and c# script
add a Position = new Vector3(0d,1d,0d); to node _Ready()
Minimal reproduction project (MRP)
pastefile.com/mk1s44

You need to also set up a local NuGet package repository: https://docs.godotengine.org/en/stable/contributing/development/compiling/compiling_with_dotnet.html#nuget-packages
@raulsntos This seems to be missing from the "Example" instructions afterwards: https://docs.godotengine.org/en/stable/contributing/development/compiling/compiling_with_dotnet.html#examples

Thanks! after call this command ./modules/mono/build_scripts/build_assemblies.py --godot-output-dir ./bin --push-nupkgs-local ~/MyLocalNugetSource --precision=double and copy the ~ folder to

C:\Users\USERNAME\AppData\Roaming\NuGet
the project will ran without any problems.


Vulnerability fix for KubernetesManifestV0

Task name: KubernetesManifestV0
Description:
Documentation changes required: (Y/N)
Added unit tests: (Y/N)
Attached related issue: (Y/N)
Checklist:

[x] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected
[x] node make.js build --task KubernetesManifestV0
[ ] node make.js test --task KubernetesManifestV0

/azp run


python38Packages.minidump: 0.0.15 -> 0.0.16

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.minidump is: "Python library to parse and read Microsoft minidump file format"
meta.homepage for python38Packages.minidump is: "https://github.com/skelsec/minidump"
meta.changelog for python38Packages.minidump is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

/nix/store/ghlb0bykzy9sgj5dlkym65p4njzypg1v-python3.8-minidump-0.0.16/bin/minidump passed the binary check.

/nix/store/ghlb0bykzy9sgj5dlkym65p4njzypg1v-python3.8-minidump-0.0.16/bin/.minidump-wrapped passed the binary check.

2 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 0.0.16 with grep in /nix/store/ghlb0bykzy9sgj5dlkym65p4njzypg1v-python3.8-minidump-0.0.16

found 0.0.16 in filename of file in /nix/store/ghlb0bykzy9sgj5dlkym65p4njzypg1v-python3.8-minidump-0.0.16

directory tree listing: https://gist.github.com/d96bf21cc2505cd624fbccb59694faf7

du listing: https://gist.github.com/d5b707e183c07fc6e2ba910c84f66227

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

6 package rebuild(s)

6 x86_64-linux rebuild(s)
6 i686-linux rebuild(s)
6 x86_64-darwin rebuild(s)
6 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.lsassy
python38Packages.minidump
python38Packages.pypykatz
python39Packages.lsassy
python39Packages.minidump
python39Packages.pypykatz

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ghlb0bykzy9sgj5dlkym65p4njzypg1v-python3.8-minidump-0.0.16 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.minidump https://github.com/r-ryantm/nixpkgs/archive/a11ee13c8a655edc73826031bf136c7170657b01.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ghlb0bykzy9sgj5dlkym65p4njzypg1v-python3.8-minidump-0.0.16
ls -la /nix/store/ghlb0bykzy9sgj5dlkym65p4njzypg1v-python3.8-minidump-0.0.16/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

python38Packages.lsassy
python38Packages.minidump
python38Packages.pypykatz
python39Packages.lsassy
python39Packages.minidump
python39Packages.pypykatz

Maintainer pings
cc @fabaff for testing.

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

6 packages built:

python38Packages.lsassy
python38Packages.minidump
python38Packages.pypykatz
python39Packages.lsassy
python39Packages.minidump
python39Packages.pypykatz

Result of nixpkgs-review pr 117683 at a11ee13c run on aarch64-linux 1

4 packages skipped due to time constraints:

python38Packages.lsassy
python38Packages.pypykatz
python39Packages.lsassy
python39Packages.pypykatz

2 packages built successfully:

python38Packages.minidump
python39Packages.minidump


Staging actions

Summary
Add Github Action that deploys a copy of the pull request to AWS. The action is triggered by pull requests with the deploy label and should update on changes to the PR. Heavily references https://github.com/jgoux/preview-environments-per-pull-request-using-aws-cdk-and-github-actions .
This action deploys:

S3 bucket to store site
Cloudfront distribution and corresponding record to redirect URL (pr_num.antalmanac.com) to S3 bucket

The dev backend is used in the deployment.
Test Plan
https://github.com/icssc/AntAlmanac/pull/347
Issues
Future Followup (Optional)
Currently, the deployed URL is pr_num.antalmanac.com because of the current certificate. However, maybe another URL such as pr_num.staging.antalmanac.com would be better, but it would require changing the certificate.

Currently, the deployed URL is pr_num.antalmanac.com because of the current certificate. However, maybe another URL such as pr_num.staging.antalmanac.com would be better, but it would require changing the certificate.

How about staging-pr_num.antalmanac.com? That shouldn't require a certificate change since it's still a third-level domain.


Test fails due to proxy URL and routing

What is your Scenario?
Access www.ikea.cn/cn/en with testcafe, click top-right cart icon to go to shopping cart.
It should go to login page but now shows 404 page.
The shopping cart is a standalone SPA with specific routing like /cn/en/pay/cart, /cn/en/pay/pay, etc.
Actually it was working before Feb 10, but we are not sure what change resulted this incompatibility so hope to look for help.
Found below similar issues:
https://github.com/DevExpress/testcafe/issues/6803
https://github.com/DevExpress/testcafe/issues/6653
And we have tried playwright which works fine.
What is the Current behavior?
Redirected to a 404 page, with no error in network request and console.
What is the Expected behavior?
login page should be displayed as manual test.
What is your public website URL? (or attach your complete example)
https://www.ikea.cn/cn/en
What is your TestCafe test code?
import { Selector } from 'testcafe';
fixture('test')
.page('https://www.ikea.cn/cn/en')
test
('test', async t => {
await t.debug();
await t.click(Selector('div').withAttribute('data-track-id', 'head-nav.7'));
await t.expect(Selector('button.cart-login-btn').visible).ok();
});
Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce

TestCafe version
1.18.3
Node.js version
14.18.3
Command-line arguments
testcafe chrome test.js -e
Browser name(s) and version(s)
chrome 98
Platform(s) and version(s)
windows 10; ubuntu 20.04
Other
No response

Thank you for your report. I have reproduced the described behavior in the latest version of the TestCafe Hammerhead playground. We will update this thread once we have any news.

Hi @mypchas6fans,
TestCafe runs tests using the URL-rewritten proxy.
This approach is good. However, there is a way to improve the stability and speed of test execution - the native browser automation API.
We have a test execution mode uses native browser automation - we call it the Proxyless mode.
In Proxyless mode, a few issues are already fixed.
By the way, this issue was also fixed in Proxyless mode.
Try running your tests in Proxyless mode and let us know the results.
This option is available in all interfaces:
// Command-line
testcafe chrome tests --experimental-proxyless

// Programmatic
testcafe
    .createRunner
	.src('tests')
	.browsers('chrome')
	.run({ experimentalProxyless: true });

// Configuration file
{
   "experimentalProxyless": "true"
}

Note that at present it is an experimental mode.
Also, the Proxyless mode is implemented only in Google Chrome. It will not work correctly if you run tests in a non-Chrome browser or in a combination of other browsers.

Sorry for late reponse. This issue still can be reproduced on proxy mode and not on Proxyless mode. Close for now.


How to get raw request body with robot.router.post

Hi there,
I'm using an instance of Hubot to process webhooks from GitHub. I've just got around to securing the payloads with SHA1 (the "Secret" field) and have run in to what I believe might be a bug, or at least, lack of a feature.
I'm using the form content-type, so I need to compute the hash against the raw request body sent by GitHub, however there doesn't seem to be any way to access the raw request body. By the time the robot.router.post callback is fired and the request object passed in, request.body has been processed to some degree (EG, converted to JSON) so it is no longer raw.
I've inspected the request object and there doesn't seem to be a way to access the raw request body. Short of editing Hubot core, is there a way around this I'm missing?
Code example
  # Listen for any POST request
  robot.router.post "/", (request, response) ->

    # Retrieve payload
    payload = JSON.parse request.body.payload

    # Ensure sha1 secret is valid
    crypto    = require('crypto')
    signature = "sha1=" + crypto.createHmac('sha1', process.env.HUBOT_GITHUB_SECRET).update( new Buffer(request.body) ).digest('hex')
    unless request.headers['x-hub-signature'] is signature
      response.send "Hashes do not match\n#{request.headers['x-hub-signature']}\n#{signature}"
      return

I get a response like this
Hashes do not match
sha1=47c04939a4ba9c1139a8b8b556898077b6ca1c84
sha1=510abf153d52710b0cd297a9eacc458422533a00

Does this still work? Can't get a match.
I also see more recent issues posted as well as a pr to allow middleware before the body parser so signing can be done with the raw request body.

@levithomason  This worked for me
getSignature = (payload) ->
    hmac = crypto.createHmac 'sha1', AUTH_SECRET
    hmac.update new Buffer JSON.stringify(payload)
    return 'sha1=' + hmac.digest('hex')

module.exports = (robot) ->
  robot.router.post "/hubot/github-repo-listener", (req, res) ->
    try
      if (debug)
        robot.logger.info("Github post received: ", req)
      signature = getSignature(req.body)
      robot.logger.info("signature: ", signature)
      robot.logger.info("github signature: ", req.headers['x-hub-signature'])
      unless req.headers['x-hub-signature'] is signature
        throw {'message': 'Unauthorized'}
      eventBody =
        eventType   : req.headers["x-github-event"]
        signature   : req.headers["X-Hub-Signature"]
        deliveryId  : req.headers["X-Github-Delivery"]
        payload     : req.body
        query       : querystring.parse(url.parse(req.url).query)

      robot.emit "github-repo-event", eventBody
    catch error
      robot.logger.error "Github repo webhook listener error: #{error.stack}. Request: #{req.body}"

    res.end ""


Migrate core package 'git-diff' into ./packages

Closes #17843

The linux build failure on VSTS is unrelated to this PR.


Implement a custom keyboard handler

Implement a keyboard handler in order to have more precise control of the keys pressed, repeated, released and the currently pressed (SHIFT, CTRL, ALT) and locked shifts (CAPS LOCK, NUM LOCK, SCROLL LOCK, PAUSE. INSERT).
Define a data structure that contains:

the ASCII code
the scan code
a virtual code (which normalizes the value of the key regardless of the pressed shifts or other modifiers)
the pressed shifts
the locked shifts

The keyboard handler has been integrated into the TUI library and has been tested.
The issue is closed.


Credential retrieval: 'str' object has no attribute 'os_startIndex'

The full error:
"ERROR Could not get Splunk_TA_paloalto credentials from splunk.  Error: 'str' object has no attribute 'os_startIndex' "
This happens when running any of the commands from the App/TA.  Specifically for retrieveWildFireReport.py.

The credentials are in the passwords.conf file under Splunk_TA_paloalto/local.
The $SPLUNK_HOME environment is set.
We are running Splunk with Search Head Clustering.

We can perform further troubleshooting if requested.
Thank you

This has been resolved.  Our admin/passwords REST request was returning gibberish such as ASCII control codes and in general non-UTF8 characters, which broke the Atom parsing.
We found three passwords that were not decrypting to plaintext properly and replaced them.  The commands now work.  The app appears to be receiving every entry from the admin/passwords REST endpoing, not just the ones under the Splunk_TA_paloalto namespace.


chore(KFLUXMIG-62): fix nudge in console-plugin in release 2.7

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (release-2.7@9b3f10f). Learn more about missing BASE report.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff               @@
##             release-2.7    #1370   +/-   ##
==============================================
  Coverage               ?   36.46%
==============================================
  Files                  ?      159
  Lines                  ?     2589
  Branches               ?      616
==============================================
  Hits                   ?      944
  Misses                 ?     1463
  Partials               ?      182

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


Feedback StatusBarItem (Smiley) not visible while building from master

VSCode Version: Master Branch. Commit 344e93c6
OS Version: Win 10 Pro

Steps to Reproduce:

Clone the repo, do yarn && yarn run watch, then run ./scripts/code.bat
Observe no smiley on the right hand side

Even changing the setting for smiley (workbench.statusBar.feedback.visible) has no effect even on restart of the development version of vscode

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

No, Its not a duplicate dear bot.

The smiley is disabled in dev. Add this to the root level product.json:
"sendASmile": {
		"reportIssueUrl": "https://fakeurl",
		"requestFeatureUrl": "https://fakeurl"
	}


Leading 4 bytes are all zeroes

It appears that in version 2.8 a new bug was introduced that did not exist in 2.7: in some cases the serialied bson does not have a valid length in the first 4 bytes. Here is an example of what we see:
(this is octal/ascii encoding)
\000\000\000\000\020int\000YxiA\020intToIncrement\000YxiA\020intToRename\000YxiA\tdate\000
I know that BSON serializer writes the length after the document is fully serialized and its length becomes know. Can it be that under some circumstances that length is not patched into the leading bytes?
Thanks

BsonGenerator.Feature.ENABLE_STREAMING is not enabled...

Hi there,
I'm not sure about that but may be the issue you described is related to a regression we found in jongo when moving from bson4jackson 2.7.x to 2.8.x/2.9.x: https://github.com/bguerout/jongo/issues/322#issuecomment-366502380

Thanks, @bguerout, for the link. Was this a regression in bson4jackson or in Jongo? Is there anything I can do for you?
@yfinkelstein I tried to reproduce the error with no avail. I used the following code:
package de.undercouch.bson4jackson;

import com.fasterxml.jackson.databind.ObjectMapper;

import java.io.ByteArrayOutputStream;
import java.util.LinkedHashMap;
import java.util.Map;

public class Issue80 {
    public static void main(String[] args) throws Exception {
        Map<String, Object> data = new LinkedHashMap<String, Object>();
        data.put("Int32", 42);

        ByteArrayOutputStream baos = new ByteArrayOutputStream();
        BsonFactory bsonFactory = new BsonFactory();
        ObjectMapper om = new ObjectMapper(bsonFactory);
        om.registerModule(new BsonModule());
        om.writeValue(baos, data);

        byte[] r = baos.toByteArray();

        for (int i = 0; i < r.length; ++i) {
            String s = Integer.toHexString(r[i]);
            if (s.length() < 2) {
                s = "0" + s;
            }
            System.out.print(s + " ");
        }
        System.out.println();
    }
}

It prints:
10 00 00 00 10 49 6e 74 33 32 00 2a 00 00 00 00

Just as expected. Can you provide a small reproducer to demonstrate the issue?

When upgrading to bson4jackon 2.8+, lot of integration tests in Jongo failed due to While decoding a BSON document 4 bytes were required, but only 0 remain error
I don't think this comes from Jongo because nothing has been modified in this area in v1.4.0 and we were able to reproduce the problem with v1.3.0.
We have fixed this issue by overriding the flush method in BsonGenerator and rollbacking to the 2.7+ behavior
Unfortunately i haven't dug enough to be able to open an issue with an explanation out of Jongo context.

@michel-kraemer I am able to reproduce the bug:
`public static void main(String[] args) throws IOException {
	ObjectMapper objectMapper = new ObjectMapper();
	ObjectNode objectNode = objectMapper.createObjectNode();
	objectNode.putPOJO("date", new Date());

	ByteArrayOutputStream bos = new ByteArrayOutputStream();

	ObjectMapper om = new ObjectMapper();
	BsonFactory bf = new BsonFactory(om);
	BsonGenerator gen = bf.createGenerator(bos);
	om.writeTree(gen, objectNode);
	gen.close();

	byte[] bin = bos.toByteArray();
	for (byte b : bin)
		System.out.print(b + ",");

}`

Output using 2.7.0 (correct)
19,0,0,0,18,100,97,116,101,0,-35,57,-47,101,99,1,0,0,0,
Output using 2.8.0 (incorrect)
0,0,0,0,18,100,97,116,101,0,13,112,-46,101,99,1,0,0,1,0,0,0,

@michel-kraemer This is the one

Looks like a serious regression. Isn't there a test on Data serialization?

@spicyrock Thanks for the reproducer. I'll have a look at it as soon as I can.

I fixed the bug and uploaded a new snapshot to https://oss.sonatype.org/content/repositories/snapshots/de/undercouch/bson4jackson/
@yfinkelstein @spicyrock Please test the snapshot and check if it resolves your problem. I will then release a new version. Thanks for the support!
@bguerout This should also resolve your issue.

@michel-kraemer I can confirmed that  2.9.2-SNAPSHOT fixes the issue found in Jongo.
Overriding the flush method in BsonGenerator is no longer needed.
Thanks a lot.

@michel-kraemer  Do you know when you will build 2.9.2-RELEASE?  Thanks

@spicyrock Today 😄

2.9.2 has just been released.

Thank you @michel-kraemer


[Bug Report] React version < 17 Failed to execute 'attachShadow' on 'Element': Shadow root cannot be created on a host which already hosts a shadow tree.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

ref.current is null in react 17 and no null in react 16
code
Potential Issues
Reproduction link
Steps to reproduce

What is expected?
no error, run right in React version 16
What is actually happening?
Package
@designable/react

@janryWang 请问有计划支持 React 16 吗？

@janryWang 请问有计划支持 React 16 吗？

这个改动还好的吧，可以直接提个PR的


feat: (IAC-1020) Support for Message Broker - Azure Service Bus

Changes:
Support added for Message broker: Azure service bus to be used by SAS Viya Platform deployment.
Resources added using:

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/servicebus_namespace
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/servicebus_namespace_authorization_rule

Tests:
Verified following on the scenarios listed below, please see internal ticket for details.

Verified cluster creation was successful.
Azure Service bus was created.
SAS Viya Platform consumed the Azure service bus information from state file correctly.
Rabbitmq pods were not created.

Note: SAS Viya Platform services are still not ready. Almost all pods stabilized except for few services. Launcher service is failing with [BROKER_MISSING_USERNAME] causing other services to fail. This is expected until all the services are updated to use the new Azure Service bus instead of Rabbitmq.

Scenario
Task
Deploy method
Cadence

1
Defaults, create_azure_message_broker= true, internal Postgres
ansible
fast:2020

2
create_azure_message_broker= true, external Postgres
ansible
fast:2020

3
create_azure_message_broker= true, message_broker_name= "ritika1", aks_cluster_sku_tier = "Standard", external Postgres
ansible
fast:2020

Overall I understand this is to replace RabbitMQ and the changes look good. I would have liked to see a more generic approach to the variables and module names along with some investigation as to how these would look across providers. The variable could have been more message queue based and generic even though they are utilizing Azure's solution.

After some investigation across cloud for message brokers, these are available options:
Azure: Azure Service Bus
AWS: Amazon MQ
GCP: Google Pub/Sub

To keep variables and module names generic I went with name as message broker. Azure service bus provides option to create queues or topics and SAS Viya Platform creates Topics.
I thought it would be confusing to name the variables/modules as message queue when we don't create queues.
I don't mind changing variable/module names, please let me know.


chore: promote python-http2 to version 0.0.1

this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

@nigle-dev: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

verify
07449abe1cabb05071a51ec8b4239f1c13e1e3f9
link
/test verify

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


Build SwiftRefactorExtension.xcodeproj in CI

We should ensure that EditorExtension/SwiftRefactorExtension.xcodeproj builds in CI by building it when running swift-syntax-dev-utils build.

Tracked in Apple’s issue tracker as rdar://113929351


transpileModule() doesn't catch duplicate let/const

TypeScript Version: typescript@next (2.3.0-dev.20170308)
TypeScript does not seem to produce an error diagnostic for duplicate declarations when using transpileModule().  This causes my tooling for miniSphere (which uses TS for ES6->ES5 transpilation) to produce possibly incorrect JS in the presence of a duplicate declaration rather than an early error, as happens with Babel.
tsc correctly produces an error, so this seems to be a bug in transpileModule():
C:\temp>tsc pig.ts
pig.ts(1,5): error TS2451: Cannot redeclare block-scoped variable 'a'.
pig.ts(2,7): error TS2451: Cannot redeclare block-scoped variable 'a'.

Actual behavior:
No error diagnostic, produces the following JS:
var a = 1;
var a = 2;
if (true) {
    var a_1 = 3;
}

transpileModule, as the name implies, is only for transpilation. It does not produce semantic diagnostics.
See https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API

Creating a compiler is simple enough, but you may want to just get the corresponding JavaScript output given TypeScript sources. For this you can use ts.transpileModule

That page also demonstrates how to set up a full checker pipeline to get semantic diagnostics.

I assumed duplicate declarations would be caught, since that's a static syntax error (I think?).  I know I don't get type checking, etc.

It's not a syntax error - the program conforms to the grammar. It is an early error but those are not guaranteed to be found without typechecking.
In general you shouldn't use transpileModule if you care about errors of any sort. It's purely for text-to-text transformation.

The main thing stopping me from using a full compiler harness is that TS wants to see the complete program including all source files on each build, which prevents me from doing incremental builds.
To clarify, what I need is a file-level ES6->ES5 transformation (TS is much faster at this than Babel) without the compile-time module resolution, typechecking, etc. but preferably with early errors.  Is it possible to do that with a full Program harness?

That's not possible due to how the checker is designed.

Thanks, that means I'll need to rethink my TypeScript integration strategy going forward.  For now I'll get by with transpileModule().
Thank you for the help! 👍

I'm assuming you meant "without a full Program harness" - obviously possible with.

Oh, didn't see this edit.  That wasn't a typo, I indeed meant "with" (and it wasn't obvious to me due to the Compiler API documentation being... somewhat lacking).  Good to know!

FWIW if your build process is resident, it's very cheap once everything is set up to update a new Program instance, typecheck a specific file, and get its emit. This is how the language service / compile-on-save works in editors.

Yeah, unfortunately my build process is just an SCons-like command-line tool, so watching for changes in realtime isn't an option for me right now. 🙁

Thanks for the help Ryan, I can close this now since there's nothing to fix.


What's the best way to add support for sql dialects?

Hello,
I'm using monaco-editor to build an SQL editor to support Presto, Spark and Druid.
The grammars are similar to SQL but not exactly the same, what would be the best way to add them to monaco-languages? I'm happy to submit a PR, just looking for some guidance/direction to start.
Similar issues:
https://github.com/microsoft/monaco-editor/issues/1892
https://github.com/microsoft/monaco-editor/issues/1870
https://github.com/microsoft/monaco-editor/issues/1707

Adding a new language is documented here -- https://github.com/microsoft/monaco-languages#dev-adding-a-new-language
I am not an expert in the field, but if these are different dialects, then they need to be defined as different languages to the Monaco Editor, i.e. Monarch tokenizers don't have options or something like that...

Closing due to inactivity.


🧑🏻🏫 Create a tutorial about how to create API inventory using traffic mirroring

💭 Introduction
Akto is an open source API security product.
Your task is to create a video tutorial or written tutorial for Create API inventory using traffic mirroring in Akto.
🎯 Requirements

Your readme file has to be publicly available.
Your tutorial should have all the steps and look nice with description, titles, screenshots, videos or even memes.

✅ Task summary:

[ ] Drop a comment on this issue indicating that you’re working on it.
[ ] Create a readme tutorial with title [Tutorial] How to create automated API inventory using traffic mirroring in Akto?
[ ] Add it to this repo.
[ ] Submit a pull request here.
[ ] Share your work on social media and tag https://github.com/akto-api-security/akto (Reddit / HackerNews / Twitter / Facebook / Linkedin)

🙋🏼♂ Questions:
If you have questions, need any help, or just want to hang out, make sure to join us on our Discord server.

Assigned to you @professorabhay. Happy Hackfesting 🔥

Hey @Ankita28g, I tried to resolve it.  https://github.com/akto-api-security/30-API-security-tests/pull/1
Please look into it and give me your reviews.
Like It is correct or need modifications.....

Thanks @professorabhay. Approved but I will make some changes to it. Thank you for your contribution!


Create a new Python Identity SDK Project

Created by: @marvinkite Dec 07 2020 at 18:14 CET
Last updated: Jul 07 2021 at 09:28 CET
ClickUp ID: IK-396
Create a Python SDK project at https://github.com/indykite/jarvis-sdk-python-proto to connect to https://github.com/indykite/jarvis-proto/tree/develop/proto/identity/v1 gRPC API.
Load the configuration from
INDYKITE_APPLICATION_CREDENTIALS_FILE	file or  INDYKITE_APPLICATION_CREDENTIALS variable and connect to service.
Checklist

[x] Create a basic client
[x] Implement IntrospectToken function
[x] Implement VerifyDigitalTwinEmail function
[x] Retrieve the system root CA
[x] How to decode numeric IDs?
[x] Create an example API usage

Closed: Feb 02 2021 at 19:10 CET


b+tree duplicate keys

I really appreciate this code, nice work.
Is your support for duplicate keys fully supported?
Can you describe the method you used to support this feature?
Thanks

After some looking, it seems to be partially implemented.

Hi @leifzars, thank you for your interest in IonDB! Currently duplicate keys are supported for the B+ Tree and Skip List dictionary implementations.

I submitted two pull requests for bugs found in the duplicate key feature.
So now things are working well


Update Empty Cadence Project Scaffold

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

Comparison is base (9505bbb) 39.80% compared to head (f20c048) 39.80%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1295   +/-   ##
=======================================
  Coverage   39.80%   39.80%
=======================================
  Files          39       39
  Lines        2143     2143
=======================================
  Hits          853      853
  Misses       1197     1197
  Partials       93       93

Flag
Coverage Δ

unittests
39.80% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


How add mock props

HI guys i have isssue.
I'm use this.props.something and cant specyfy in storybook that value like
 static defaultProps = {
  fields: [
      {
        id: 'email',
        constraints: [
          { validator: (val) => /.@./.test(val) },
        ],
        isValid: true,
      }
}

To use that like
  <form action={this.props.action}
                          method={this.props.method}

Where i should add that for element line stories/MainSection.js ?

We don't have a built in way to mock props. But you can use any JS module for that inside your Storybook.
Also we've added props editing support: https://github.com/kadirahq/storybook-addon-knobs


add file not-changed skip rule

Codecov Report
Attention: Patch coverage is 10.00000% with 27 lines in your changes are missing coverage. Please review.

Project coverage is 51.19%. Comparing base (079c9d2) to head (46280e6).
Report is 1 commits behind head on main.

Files
Patch %
Lines

cmd/docstak/run.go
0.00%
12 Missing :warning:

docstak/model/document.go
0.00%
10 Missing :warning:

docstak/files/markdown/document.go
0.00%
5 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
- Coverage   52.34%   51.19%   -1.15%
==========================================
  Files          16       16
  Lines         854      879      +25
==========================================
+ Hits          447      450       +3
- Misses        363      385      +22
  Partials       44       44

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


Add tests for AES-GCM when called through single-step cipher API

Summary: This PR adds unit tests for mbedtls_cipher_auth_{encrypt/decrypt}() for AES-GCM ciphers.
Specifically, it replicates AES-GCM NIST test vectors from test_suite_gcm.aes{128,192,256}_de.data (exercising the GCM abstraction layer) in test_suite_cipher.gcm.data, calling the existing test function auth_crypt_tv which exercises mbedtls_cipher_auth_{encrypt/decrypt}() from cipher.h but which so far had only been used to test CCM and ChaChaPoly.
Fixes https://github.com/ARMmbed/mbedtls/issues/2198.

While I understand this PR, I'm not sure how can I vallidate the data provided for these tests. Do you have any suggestions, @hanno-arm?

@AndrzejKurek The data is what we already use for the GCM test suite; they have only been ported to the cipher layer test suite. That said, though, I haven't been able to find the NIST document which introduces them, even though the comments say they are from NIST.

@AndrzejKurek I missed some dependencies which are fixed in the latest commit. Could you please re-review?

@mpg @AndrzejKurek I updated this PR on the new psa-integration-utilities. Please re-review.

@mpg @AndrzejKurek This PR now targets development instead of psa-integration-utilities, as it doesn't have any dependencies on the other PSA work.

This has now been merged to development-psa so can be closed.

@hanno-arm - Does this need backporting?

Reopening because this fix should go into development, too. Given that the test gap is large and the backporting is easy, backports should be provided. I will take care of it.

Rebased on top of development to resolve ChangeLog merge conflict. @AndrzejKurek @gilles-peskine-arm please re-review.

@hanno-arm - Sorry, but this PR needs rebasing.

@AndrzejKurek @gilles-peskine-arm Rebased to resolve conflicts in the ChangeLog. Can you please re-review?

There's only a changelog change now. Did you forget some commits in a rebase or was the same patch made elsewhere?

This has already been merged into Mbed TLS via the temporary branch development-psa (https://github.com/ARMmbed/mbedtls/pull/2201, https://github.com/ARMmbed/mbedtls/pull/2395) and subsequently into Mbed Crypto. So all that's missing is the backports.


CSS grid auto fit, span and wrapping

https://stackoverflow.com/q/48974380/3935891

Closing as doesn't appear to be a bug.


Add edge bias feature to bias for testing edge cases.

It works by randomly changing some generated values to be one of the random edge cases. The first tests are done with 100% edge cases, and then the chance goes down over the number of test cases until it's 0%.
The average amount of edge case tests can be controlled by edge_bias configuration option. It defaults to 0.25. (25% of generated values are edge cases over all the tests.)
In failure the edge bias is persisted to the persistence file along with the seed, so it should be reproducible.
So far it only does ints, floats and ranges.
I also got some validation for the system, because some of the existing tests started failing.
For example the time::Duration test failed because if both secs and nanos are MAX, the nanos will overflow into secs, and then secs will overflow and the function panics.
Note that I'm not sure if the fix I made is the best, since I just mod by a billion, so it biases the random distribution a bit. I don't know if this is undesireable.
float_samplers test subbsequent_splits_always_match_bounds also started failing (for f32 and f64 versions both) because it couldn't generate multiple intervals for values like
minimal failing input: (low, high) = (
    1.7976931348623155e308,
    1.7976931348623157e308,
), index = Index(
    0,
)

I fixed it by checking for intervals.count == 1, but I feel like that's not the best solution. From reading the other tests, it feels like the intervals are supposed to be able to be split, but in the end I didn't look fully into it.
I also think the tests should include nans and infinities as edge cases, but I didn't add those because it would cause a lot of things to fail, because they're made with the assumption that those are not generated. (Or expecting and asserting.)

This got closed when i switched branch from master to main. I'll re-open against the main branch.
NB: #504 was just recently opened with a similar topic

Would it be possible to add strategy transformation which allows specifying edge cases manually, like jqwik does?


New connections created in scratch never connect

Apparently, every time the server is created, it needs to be defined.


About the performance of PTV3 on S3DIS

Hi, xiaoyang. Thanks for your great work. The performance of PTV3 on S3DIS that I trained is lower than the results reported in the paper (71.13 vs 73.4). Are there any suggestions? Besides, i find the result on the beam class is zero, is this normal?
[2024-02-27 14:40:47,480 INFO test.py line 317 31290] Val result: mIoU/mAcc/allAcc 0.7113/0.7624/0.9132
[2024-02-27 14:40:47,480 INFO test.py line 323 31290] Class_0 - ceiling Result: iou/accuracy 0.9354/0.9617
[2024-02-27 14:40:47,480 INFO test.py line 323 31290] Class_1 - floor Result: iou/accuracy 0.9826/0.9930
[2024-02-27 14:40:47,480 INFO test.py line 323 31290] Class_2 - wall Result: iou/accuracy 0.8569/0.9794
[2024-02-27 14:40:47,480 INFO test.py line 323 31290] Class_3 - beam Result: iou/accuracy 0.0000/0.0000
[2024-02-27 14:40:47,480 INFO test.py line 323 31290] Class_4 - column Result: iou/accuracy 0.3872/0.4147
[2024-02-27 14:40:47,481 INFO test.py line 323 31290] Class_5 - window Result: iou/accuracy 0.6270/0.6419
[2024-02-27 14:40:47,481 INFO test.py line 323 31290] Class_6 - door Result: iou/accuracy 0.7766/0.8329
[2024-02-27 14:40:47,481 INFO test.py line 323 31290] Class_7 - table Result: iou/accuracy 0.8349/0.9106
[2024-02-27 14:40:47,481 INFO test.py line 323 31290] Class_8 - chair Result: iou/accuracy 0.9255/0.9676
[2024-02-27 14:40:47,481 INFO test.py line 323 31290] Class_9 - sofa Result: iou/accuracy 0.6954/0.7279
[2024-02-27 14:40:47,481 INFO test.py line 323 31290] Class_10 - bookcase Result: iou/accuracy 0.7980/0.8798
[2024-02-27 14:40:47,481 INFO test.py line 323 31290] Class_11 - board Result: iou/accuracy 0.8059/0.8847
[2024-02-27 14:40:47,481 INFO test.py line 323 31290] Class_12 - clutter Result: iou/accuracy 0.6220/0.7168

Hi, the secret is run three times (or more), and select the highest. It is a long-time issue that training on S3DIS from scratch is extremely unstable (the data scale is too small). The PTv3
+PPT config is much more stable.

Thank you very much, I will try more times~


force type to unmarshal in echo plugin

Signed-off-by: Yannick Briffa<EMAIL_ADDRESS>

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

After discussing this, it seems unnecessary; closing


Unknown product type: 17973.

          Hi,

HA not founding A9MEM1590 R200 3P 3P+N. Can You help?
Logs:
2024-04-11 11:19:35.288 WARNING (MainThread) [root] Unknown product type: 17973.
Attached full debug logs
home-assistant_powertag_gateway_2024-04-11T10-50-59.589Z.log
Update: I change in file product type 17969 to 17973, Start working
Originally posted by @Seveensv in https://github.com/Breina/PowerTagGateway/issues/15#issuecomment-2049425472

That's odd.

I've asked Schneider for updated documentation, as the one I have doesn't contain your product.

Fyi, I applied the temporary fix that you did manually in v0.2.3. Will be looking for a proper fix when Schneider returns.

Permanent fix is released in v0.3.0. Please let me know if it's still good for you and close the Issue if it is.


add 2024 CEPLAS and Mibinet events

Not ideal, since multi-day series are repetitive.
But otherwise they would be displayed as single events only.

@Freymaurer

@Brilator does this fit into the new layout that was merged?

No. Those were meant for fornax-based site.

I PRed for the time until astro launch. So, if that's around the corner, I'm ready to recreate.

We'll hopefully launch today!


from datetime import datetime is never given for datetime

I narrowed it down to the fixup method but no real succes in fixing it, except from not calling the method when the symbol is in the path https://github.com/alecthomas/importmagic/compare/master...paradoxxxzero:master but this seems hackish and would not work for module in module in module all with the same name...
Any thoughts?

Can you check your index to see if that symbol is available?

Yes it is, all works fine until the fixup method removes the variable
because it's the same as the module, which is what we want for
datetime.datetime but not for datetime.
In both of these cases, the fixup method is called twice, once with
datetime, None and once with datetime, datetime. However it always
returns datetime, None which is wrong for the latter case.
I hope I'm being clear enough :)
Btw Thanks for this awesome project, that I now use daily in
http://github.com/Kozea/wdb and Atom
https://github.com/paradoxxxzero/atom-python-import-magic
Le sam. 17 sept. 2016 à 09:24, Alec Thomas<EMAIL_ADDRESS>a
écrit :

Can you check your index to see if that symbol is available?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alecthomas/importmagic/issues/41#issuecomment-247754928,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQjKEcsd_7zq23B1YoJWDJsVO0KBgb8ks5qq5WkgaJpZM4J_Gyf
.

Ran into the same issue today with pprint.pprint, which I normally import as
from pprint import pprint

In a similar manner, completing for "sin" offers "from numpy.ma.core import sin" but not the more sensible "from numpy import sin".


Shrink DrawFunctionId

Objective
This includes one part of #4899. The aim is to improve CPU-side rendering performance by reducing the memory footprint and bandwidth required.
Solution
Shrink DrawFunctionId to u32. Enforce that u32 as usize conversions are always safe by forbidding compilation on 16-bit platforms. This shouldn't be a breaking change since #4736 disabled compilation of bevy_ecs on those platforms.
Shrinking DrawFunctionId shrinks all of the PhaseItem types, which is integral to sort and render phase performance.
Testing against many_cubes, the sort phase improved by 22% (174.21us -> 141.76us per frame).

The main opaque pass also imrproved by 9% (5.49ms -> 5.03ms)

Overall frame time improved by 5% (14.85ms -> 14.09ms)

There will be a followup PR that likewise shrinks CachedRenderPipelineId which should yield similar results on top of these improvements.

bors retry


Removed two files

Description
Resolves #19487

Type of change

[x] Bug fix~~
[ ] New feature~~
[ ] Documentation update~~
[ ] Other~~

How Has This Been Tested?
I'm not sure there's anything to test here; I simply deleted surface86.cmake and justin-IdeaPad-L340-17IRH-Gaming.cmake as requested.
Reminders:

Please follow the style guidelines of this project.
Please perform a self-review of your code before submitting a PR and asking others to review it.
Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

[ ] I have commented my code where applicable.
[ ] I have updated the release notes.
[ ] I have made corresponding changes to the documentation.
[ ] I have added debugging support to my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have confirmed new and existing unit tests pass locally with my changes.
[ ] I have added new baselines for any new tests to the repo.
[ ] I have NOT made any changes to protocol or public interfaces in an RC branch.

Justin, you said before:

For this work specifically, you will need to follow these instructions as well.

Did you mean I need to regenerate networks.json? I'm only altering src/config-site, not src/resources/hosts, right?

Did you mean I need to regenerate networks.json? I'm only altering src/config-site, not src/resources/hosts, right?

Sorry, that's confusing. You are correct; my mistake.

If you could go ahead and make these changes on develop as well (follow the instructions we discussed here: #19490), that would be excellent. Thanks so much, and let me know if you have further questions.


wip: macro support

@teto btw. it's good to see you around. Would you be willing to try out this branch for a while? (needs "hrsh7th/nvim-cmp" as dependency for autocomplete).
I'm kinda procrastinating on merging this, any feedback would be welcome.

What are good ways to test this ? Maybe you would get more feedback with a description in hte first message. I saw this PR yesterday but without dscription and draft status, I looked the other way :p

@teto If you use default shortcuts, they should resolve to editable commands with some prefiled macros

For code commands such as rewrite:
@agent xy # allows changing command on the fly while writing command

@target_filetype # xy for setting filetype of new buffer made with commands such as GpEnew
@target_filename` path` # ditto as above

@with_repo_instructions serves for adding .gp.md repo instructions optionally (when present they were always added)
@with_current_buf adds current buffer for context
@with_file ` path ` adds arbitrary file for context

The last two should also be usable in chat buffers.

Besides this there are some additional changes concerning Chat buffers:

most chat logic is now handled via custom filetype (chats have markdown.gpchat, so people could use ftplugin/gpchat for customization)
:GpChatHelp to toggle help visibility
chat header uses yaml frontmatter syntax for compatibility with plugins such as Obsidian
chats are auto renamed to include topic.

Some startup optimizations tho shed off milliseconds for people who start new neovim instances a lot and maybe some other things I forgot in the meantime.


Immersive Portals incompatibility [Fabric]

Found another incompatibility with Immersive Portals. Is this launch crash on their side or yours?

resolved in b1.0.3


A unified gamma container, with a science prototyping environment

Unification of the containers
This PR merges the hyp3-rtc-gamma, hyp3-insar-gamma, and hyp3-geocode plugins into a single hyp3-gamma plugin.
Notably, there are now only HyP3v2 entrypoints (geocode-only raises an NotImplementedError), and I've used git-filter-repo to preserve history for the files merged in from InSAR, Geocode, and hyp3lib. These histories will new commit ids, and the tags have been prefixed, because this rewrites history.

Science prototyping environment
This also adds in a Jupter (lab or notebook) prototyping environment to the plugin's Dockerfile which is created by either targeting the prototype environment (with a --target prototype docker build argument) or by default. To run the prototyping environment, assuming you're in the repository root:
docker run --rm \
  -v ${PWD}:/home/conda/hyp3-gamma \
  -p 8888:8888 \
  -it [PROTOTYPE_BUILD_TAG]

which will then be available at localhost:8888
To build the container without the prototyping environment (as would be deployed in HyP3), you would use/add a --target production build target to the above build command, and this target has been added to the GitHub Actions workflow.
This environment has been based off of the Minimal Jupyter notebook stack from the Jupyter Docker Stacks
This environment should be considered a minimal prototyping environment and we will likely want to add in more feature in the future.
TODOs
Before merging, we should:

[ ] Move this repository from ASFHyP3/hyp3-rtc-gamma to ASFHyP3/hyp3-gamma
[ ] Setup actions to publish to an hyp3-gamma ECR in the HyP3v2 account (in the us-west-2 region)
[ ] Switch master branch to main

After, or in tandem to, merging we'll want to:

[ ] Update the API to point to this container
[ ] Update the API to handle new way to call these entrypoints
[ ] Update the InSAR GAMMA README with a move notice, and archive the repository
[ ] Remove GAMMA bits from hyp3lib that have been moved here

This has been open long enough without movement, we've had a bit of development happen in the three packages being combined here. I'm going to close this, rework it on top of the current changes, and adopt a different strategy to get this moved forward.


Add sort option to query methods

This would be super useful for frame-like behavior

implemented directly to master


[Enhancement] Minimum Character status to run a command

Here we check a character status before run specific command. To execute a chat command, character status must be equal or greater than the minimum character requirement of desired command.
And change if repetition with a switch

i don't know why this error happens, I'm using Osx 10.14.6 64 bits and 3.1.100 sdk.
In my notebooks runs fine and in client work the command and the validation.
Finished building project: MUnique.OpenMU.GameLogic. Succeeded: True. Errors: 0. Warnings: 8
any idea?

Still this error:
PlugIns\CreateItemChatCommandPlugIn.cs(26,48): error CS0246: The type or namespace name 'IChatCommandPlugIn' could not be found (are you missing a using directive or an assembly reference?) [D:\a\1\s\src\GameLogic\MUnique.OpenMU.GameLogic.csproj]

I have no idea... I cloned your repo and on my machine it builds without errors as well.
I also can't find the file PlugIns\CreateItemChatCommandPlugIn.cs in this path in my checkout or on the GitHub interface

ok. the quality review fails because a //todo comment.
should i remove it or will merge anyway?

Please remove/resolve them. Otherwise it can be forgotten to solve these TODOs ;)

done.
Increased minimum status required to game master, now we should set as GM the test accounts, otherwise /teleport and /item will not work

Okay, somehow stuff went wrong - I fixed them ;)
I added the test account "testgm" with GameMaster characters to the data initialization


NFS demo does not work with kubernetes 1.6.6

I followed the NFS provisioner demo, and I'm having a [probably subtle] problem getting it working. I'm using k8s version 1.6.6:
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.6", GitCommit:"7fa1c1756d8bc963f1a389f4a6937dc71f08ada2", GitTreeState:"clean", BuildDate:"2017-06-16T18:21:54Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}
all of the pods launch correctly, and the PV and PVCs are created as well:
NAME                              READY     STATUS    RESTARTS   AGE
nfs-provisioner-225303794-7cxh7   1/1       Running   0          5m
nfs-test-1nn61                    1/1       Running   0          4m

NAME      STATUS    VOLUME                                     CAPACITY   ACCESSMODES   STORAGECLASS   AGE
nfs       Bound     pvc-524a260e-650b-11e7-b217-0800274d0770   1Mi        RWX           example-nfs    5m

NAME                                       CAPACITY   ACCESSMODES   RECLAIMPOLICY   STATUS    CLAIM         STORAGECLASS   REASON    AGE
pvc-524a260e-650b-11e7-b217-0800274d0770   1Mi        RWX           Delete          Bound     default/nfs   example-nfs              5m

However, the busybox image is unable to write data into the mounted volume, with error "Invalid argument":
sh: can't create /mnt/index.html: Invalid argument
sh: can't create /mnt/index.html: Invalid argument
sh: can't create /mnt/index.html: Invalid argument
sh: can't create /mnt/index.html: Invalid argument
sh: can't create /mnt/index.html: Invalid argument

getting into the pod, the volume is mounted ( other non-relevant mounts removed for clarity):
/ # mount
<IP_ADDRESS>:/export/pvc-524a260e-650b-11e7-b217-0800274d0770 on /mnt type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=<IP_ADDRESS>,local_lock=none,addr=<IP_ADDRESS>)

but manually trying to do anything on that volume doesn't work:
/ # touch /mnt/foobar
touch: /mnt/foobar: Invalid argument
curiously, its also impossible to umount the volume too, even though i'm root. I was going to try to manually re-mount it:
/ # umount /mnt
umount: can't unmount /mnt: Operation not permitted

I have also tried manipulating the rootSquash and gid parameters on the provisioner with no luck.  Does anyone have ideas on how this could be going wrong?

@wongma7 @dcowden I'm using 1.6.6 and I had 0 problems. I just followed the steps, which seems unclear at some point's but I think I will just make a PR for it.
Thanks,
Levi

I couldn't reproduce this issue either locally nor via Travis CI. However, I don't doubt that it exists. There are a lot of potential culprits... I'd say (the version of) kubernetes is unlikely to be it here. It's probably a weird interaction between NFS-Ganesha and docker.
What storage driver is docker using (output of docker info | grep Storage)?
What happens if you try to mount the nfs server on the host itself, if possible, e.g. sudo mount $NFS_PROVISIONER_CONTAINER_IP:/export/pvc-524a260e-650b-11e7-b217-0800274d0770 /tmp/asdf? If you try to mount it with nfsv4 instead of 4.2 like  sudo mount -t nfs4 $NFS_PROVISIONER_CONTAINER_IP:/export/pvc-524a260e-650b-11e7-b217-0800274d0770 /tmp/asdf ?
Root_squash is no_root_squash by default which should be fine. And it's also normal that you're not allowed to unmount it from within the container, that requires more privileges.
@shadycuz thanks for confirming; and yeah, I wrote everything myself and I'm hardly an experienced writer so please feel free to make clarifications :)

@wongma7 Well you did a great job. I'm brand new to kubernetes and never messed with PV's until today. Though I have some questions, but I will post them when I make a PR.

hi guys thanks, let me try out a couple of these suggestions.  In reading, my hunch is that it could be an nfs4 vs nfs3 thing, but i wasnt able to prove this.

Yes sorry, I’ve known about this for a bit but neglected to document. You
can try to use the mount option storage parameter in the storage class so
that all pvs get that set automatically
On Thu, Aug 24, 2017 at 11:03 AM Roman Sokolkov<EMAIL_ADDRESS>wrote:

This is probably the reason nfs-ganesha/nfs-ganesha#192
https://github.com/nfs-ganesha/nfs-ganesha/issues/192
In my case, remounting with vers=4.1 helped. But still not clear how to
make it work in kubernetes by default.
For one specific PV setting volume.beta.kubernetes.io/mount-options:
"vers=4.1" works.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/external-storage/issues/223#issuecomment-324662372,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMgP-G-55fTVVw_uX00_QNoR5A0XtGNWks5sbZDRgaJpZM4OSQOj
.

just found it ;) https://github.com/kubernetes-incubator/external-
storage/blob/master/nfs/docs/usage.md#parameters
Thanks

I could not get either NFS 4.1 or 4.0 working either unfortunately. A write as soon as the container started caused an Invalid Argument error and the container (redis) crashed. NFS 3 is working alright. (vers=3)

It took me a while to figure out the above, but in the end my StorageClass looked like the following:
kind: StorageClass
apiVersion: storage.k8s.io/v1beta1
metadata:
  name: nfs
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"
provisioner: developerapp.com/nfs
parameters:
  mountOptions: "vers=4.1"

It seems there is also a new mountOptions field which has been introduced to StorageClasses recently (rather then as a field under parameters). This confused me for a bit, but hopefully the above will save someone some pain in future.

@adamcharnock Thanks a lot man! Your suggestion about using the parameters / mountOptions field saved the day :)

@adamcharnock You saved my life!    mountOptions: "vers=4.1" resolves everything! Thank you so much!


Test: New GHPRI create pull request flow

Refs: https://github.com/microsoft/vscode-pull-request-github/issues/2293

[x] macOS @bpasero
[ ] linux @isidorn
[ ] windows @JacksonKearl

Complexity: 5
Authors: @RMacfarlane, @eamodio
Create Issue

Please make sure you are using the nightly version of the extension and file issues in the extension repo
The GitHub Pull Requests and Issues extension has new UI for creating pull requests, making use of a webview in the activity bar. You should be able to:

Start create from the "+" icon in the pull requests view
Start create from the command palette items for "Create Pull Request" and "Create Draft Pull Request"
Choose a different base branch or different remote if you have multiple remotes, and have the diff view update
Be warned in the diff view if the current branch is not published, and be able to publish it from there
Be warned if there is no commit difference between the current branch and your selection
Be warned if you try to create with no title
Change the githubPullRequests.pullRequestTitle and githubPullRequests.pullRequestDescription settings and see different default values for the title/description
Have changes to fields preserved if you navigate away and back to the viewlet
Select repo at beginning of create if you are in a multi-root workspace
Cancel create and return to the pull request list
Create a pull request and draft pull request successfully

Please make sure you are using the nightly version of the extension and file issues in the extension repo

Fyi I wasted 30 minutes until I realised that I need to install the GH PR nightly extension.

Fyi I wasted 30 minutes until I realised that I need to install the GH PR nightly extension.

I am unable to move past the https://github.com/microsoft/vscode-pull-request-github/issues/2395
So I was not able to successfuly finish testing this...

I am unable to move past the https://github.com/microsoft/vscode-pull-request-github/issues/2395
So I was not able to successfuly finish testing this...

After some tries I was able to move past the  microsoft/vscode-pull-request-github#2395 and now this seems to work, not sure what was the root cause...

After some tries I was able to move past the  microsoft/vscode-pull-request-github#2395 and now this seems to work, not sure what was the root cause...

My speculation is that it could be related to wether the branch is pushed to the remote or not before creating the PR?

My speculation is that it could be related to wether the branch is pushed to the remote or not before creating the PR?

I have pushed it to remote and it was not working. Maybe it needs a manual reload - which makes for a bad experience...

I have pushed it to remote and it was not working. Maybe it needs a manual reload - which makes for a bad experience...

I have assigned all the issues to @RMacfarlane, let me know if I should assign them to @eamodio as well (since only know I noticed that he is also listed as author). For now I leave that up to the authors.
In the end I could successfully do the scenario, thus checking my name off.

I have assigned all the issues to @RMacfarlane, let me know if I should assign them to @eamodio as well (since only know I noticed that he is also listed as author). For now I leave that up to the authors.
In the end I could successfully do the scenario, thus checking my name off.


Filetype detection quick fix

Automatic filetype detection can be fixed by adding # vim:filetype=i3config at the end of your config

yes that's right. I didn't put that in the README. I would highly appreciate if you can make a small PR to clarify that in the README file section: File type detection
File type detection
There is no specific extension for i3 config file.
For auto detection, the recommended method is to rename your file to something like:

.i3.config
i3.config
something.i3config
something.i3.config

This way you can keep your file clean somewhere in a
dotfile repository and have it symlinked to ~/.i3/config

If you don't want to, then you can always do:
:set ft=i3config

or
:set filetype=i3config

No need to keep it open as no action required.


Fixed ISSUE 7 - Sign-in form displays raw span html in input fields

The placeholders now display "Username/Email" and "Password"

Publify needs to be usable by an international audience of non-english speakers. Your are hardcoding the english words "Username/Email" and "Password".

Is it "Username" or "Email" or either!?


adding control library docs with index.md

Adding the docs for the control library with index.md file

(#9 is slightly more up to date, but keeping this open so we can both test independently.)

Closing the PR as the workflow for publishing control library docs automatically is now complete and PRs related merged.


AlignParameters: Missing space between colon and type when special characters are used

From @daniel-trinh on June 8, 2014 17:30
When alignParameters is enabled, the colon between the name and type sometimes does not preserve the extra space after the type.
Failing test case:
  """def a(
    |  underscore_ : Int = 1,
    |  underscore2__ : String = "1"
    |)""" ==>
  """def a(
    |  underscore_ :   Int    = 1,
    |  underscore2__ : String = "1"
    |)"""

Currently, the above example gets reformatted as this:
def a(
  underscore_ :  Int    = 1,
  underscore2__ :String = "1"
)

Note the lack of space between the type and colon.
Copied from original issue: daniel-trinh/scalariform#21

As of latest scalariform with SpaceBeforeColon -> true the sample code formats as expected:
def a(
  underscore_ : Int = 1,
  underscore2__ : String = "1"
)


feat(payment): PAYPAL-2947 added MandateTextComponent

What?
Added MandateTextComponent
Why?
To show mandate text when it is needed
checkouts-sdk-js PR with adding field to interface https://github.com/bigcommerce/checkout-sdk-js/pull/2192
Testing / Proof

@bigcommerce/team-checkout

Build failed as well as e2e because there is usage of interface that generates from checkout-sdk-js repository. I've added changes to checkout-sdk-js. And this issue will be solved as soon as i merged this pr https://github.com/bigcommerce/checkout-sdk-js/pull/2192

Build failed as well as e2e because i use interface that is generated from checkout-sdk-js, this issue will be solved as soon as i merge https://github.com/bigcommerce/checkout-sdk-js/pull/2192

Please, update a name of the PR

Could you please bump SDK and have all CI checks passed in this PR?


Support for Text Input

Legacy TVs support text being sent through the remote. I wonder if that is also possible with the new models. Maybe through some other params in this request:
        payload = json.dumps({
            "method": "ms.remote.control",
            "params": {
                "Cmd": "Click",
                "DataOfCmd": key,
                "Option": "false",
                "TypeOfRemote": "SendRemoteKey"
            }
        })

This isn't a homekit feature, so it wouldn't be part of this project.


Add Expansion Indicator to Scenario Selection Screen

Description of Problem or Question
There should be a way to see which expansions each scenario in the downloader require.
Valkyrie Version
2.1.3
Body
I just found out about this awesome software (thanks Bruce!) and before I get into making my own scenarios I would like to try a few of the ones others have made.  I downloaded a few scenarios but then realized that I had expansions enabled in the options.  Since I only own the base game I'm now left wondering which of the downloaded scenarios require pieces I don't own.
I'm thinking this should be relatively straight forward to add as tiles are already sorted by expansion in the editor.
Forgive me if I am missing something.

Hi Adam,
As explained by Scrubbless the information for scenarios is already in the "select scenario" screen, but you need to download the scenario first.
I'd like to improve the download / selection scenario screens to have everything in one single screen: languages, expansions informations, updates ... and also to make download a lot faster.
So you would have all informations, even before download scenarios.
This is related to other ticket : #938  #832 #957


Move prototypes to regular node children?

It is possible to move 3d prototypes node to regular children marking it with reserved symbol like @prototypes and just ignore it in renderer. It will allow to slightly simplify logic of 3d node, but it will also change how serialized node would look like. Instead of:
{
  "root" : {
    "prototypes" : {
      "children" : {}
    },
    "children" : {
      "child" : {}
    }
  }
}

We will get:
{
  "root" : {
    "children" : {
      "@prototypes" : {
        "children" : {}
      },
      "child" : {}
    }
  }
}

Too complicated to implement. Prototypes is now a special group with custom serialization.


[CI] Update Slack.yml and add newcomer-alert workflow

Current Behavior
Currently the slack.yml is outdated. Also there is no automated way of notifying the slack channel when a "good first issue" has been created.
Desired Behavior
Update slack.yml and add newcomer-alert.yml to the Github workflow.

Resources
Add the updated slack.yml file and the newcomer-alert.yml file to the .github/workflow folder.
Files needed:
https://github.com/meshery/meshery-istio/blob/master/.github/workflows/slack.yml
https://github.com/layer5io/layer5/blob/master/.github/workflows/newcomers-alert.yml

I have made this PR #136 to solve the issue but not sure of my understanding.
so please review the PR and assign this issue to me


Validate functions

Reapply #2168.
It looks like we forgot \or patterns in function rules.

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[ ] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

@ttuegel You mean like this?

Tried rerunning Jenkins job: https://office.runtimeverification.com/jenkins/blue/organizations/jenkins/haskell-backend/detail/PR-2585/4/pipeline

This error will be fixed by #2598.


exported vars can be exported several times

Operating system or device - Godot version:
current head, 64bits, win10
Issue description (what happened, and what was expected):
like the title say, a variable can be exported several times without complaints from the editor.
all of the export will appear into the inspector.
if you modify one of them, only the first one will have the "reset" icon, and only the first one will be reset if you press it.
Steps to reproduce:
export var test = "test";
export var test = "test";
export var test = "test";
export var test = "test";
export var test = "test";
export var test = "test";

Link to minimal example project (optional but very welcome):

Still reproducible/relevant in 3.1 master 9ad1800

Not sure if it was fixed in my PR (#19264) but in any case it is fixed in master.


Update Contributing.md

removed the part that says "I've made more or less a working package for debian" as the link seems dead, as it just leads to a 404 page now.

Oops, I probably deleted that when cleaning the branches on my fork. Thanks for noticing that. If you were looking for it, I think the debian-pkg branch on the main repo was more or less what was there? This one https://github.com/etternagame/etterna/tree/debian-pkg , just look at the last commit. But beware that it's (1) super old and probably outdated, and (2) I know nothing about packaging so it's likely doubly wrong.


[BEAM-7086] Refactoring repetitive error code.

Straightforward change, make some function literals for the really
repetitive error code.

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

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @lostluck @aaltay
Small change to fix a backlogged bug.


about the loss of detector

HI, thanks for your great work! I have a question about the loss in code.
In Loss part," d_uv_mat_abs = torch.abs(source_uv_warped.view(B,2,-1).unsqueeze(3) - target_uv_pred.view(B,2,-1).unsqueeze(2)) "  is used to calc the uv loss. My question is the source_uv_warped and target_nv_pred should be algined by there, so why we need a hw*hw for distance ?  Directly using "d_uv_mat_abs = torch.abs(source_uv_warped.view(B,2,-1) - target_uv_pred.view(B,2,-1)) is not enough?

Hmm yes, I think you're right that we may not need that. Did you try running without?

No, but I will give it a try. Thanks!


Adding custom field to user attributes and registration form

Hi, first of all thank you for this amazing project. I agree with all your motivations :).
Which branch is the right one for me to start ?

I have a keycloak server already running.
I want to add a custom theme extending "keycloak" theme
Add a select field to the registration form to add a custom user attribute.

"look_and_feel" branch ?
demo branch ?
I started with the "look_and_feel" following "advanced usage" following this guide.
Replaces those lines by const kcContext = realKcContext ?? kcContextMocks.kcLoginContext;, now if you run yarn start you will be able to debug the login page, replace kcLoginContext by kcRegisterContext and the register page will be loaded instead.
This point doesnt apply for the code of the "look_and_feel" branch though.
You see my confusion ? Otherwise let me know and I can try to explain it in other way :)
Thank you!

Sorry, I don't have time to look at your issue in depth now but I just want to tell you that, as for right now the pattern validation in user attribute is broken.
I hope to fix it today but just in case you'd run against a brick wall...;

Thanks for answering.
I just deployed a custom attribute select field like this. I'll let you know if that works :)

Oh yeah this will definitely work.
We used to do that with email if I am not mistaking.
Checkout that (and that for testing outside of keycloak).
But we gave up this approach in favour of the newer and greater "user attribute" feature:

ref
The intefration of this Keyclaok feature is what's I am saying is half broken still. But I will fix it asap!


ddl: Add the reason why an IStorage instance is recovered

What problem does this PR solve?
Issue Number: ref https://github.com/pingcap/tiflash/issues/6233
Problem Summary:
What is changed and how it works?
Check List
Tests

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

Side effects

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

Documentation

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

Release note

None

/run-all-tests

/run-unit-test

/run-unit-test


v1-release/channels does not respect json content type

Describe the bug:

curl --header "Accept: application/json" https://update.k3s.io/v1-release/channels returns an HTML page instead of JSON content which breaks custom installation scripts.
Steps To Reproduce:

Run the above command
You will see HTML content

Expected behavior:

Run the above command
You should see JSON content

Actual behavior:

Run the above command
You will see HTML content

Additional context / logs:

It's breaking https://github.com/PyratLabs/ansible-role-k3s which a lot of people use.

Issue is now fixed

Duplicate of https://github.com/k3s-io/k3s/issues/10578
If there is an outage, you may get a html error page from Cloudflare.

I don't think this has been resolved. Just tried the following:
❯ curl --header "Accept: application/json" https://update.k3s.io/v1-release/channels

<!DOCTYPE html>
<!-- If you are reading this, there is a good chance you would prefer sending an
"Accept: application/json" header and receiving actual JSON responses. -->
<link rel="stylesheet" type="text/css" href="https://releases.rancher.com/api-ui/1.1.8/ui.min.css" />
<script src="https://releases.rancher.com/api-ui/1.1.8/ui.min.js"></script>
<script>
var user = "admin";
var curlUser='${CATTLE_ACCESS_KEY}:${CATTLE_SECRET_KEY}';
var schemas="https://update.k3s.io/v1-release/schemas";
var data =
{"type":"collection","links":{"self":"https://update.k3s.io/v1-release/channels"},"actions":{},"resourceType":"channels","data":[{"id":"stable","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/stable"},"name":"stable","latest":"v1.30.4+k3s1"},{"id":"latest","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/latest"},"name":"latest","latest":"v1.31.0+k3s1","latestRegexp":".*","excludeRegexp":"(^[^+]+-|v1\\.25\\.5\\+k3s1|v1\\.26\\.0\\+k3s1)"},{"id":"testing","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/testing"},"name":"testing","latest":"v1.31.0-rc2+k3s1","latestRegexp":"-(alpha|beta|rc)"},{"id":"v1.16","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.16"},"name":"v1.16","latest":"v1.16.15+k3s1","latestRegexp":"v1\\.16\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.16-testing","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.16-testing"},"name":"v1.16-testing","latest":"v1.16.14-rc1+k3s1","latestRegexp":"v1\\.16\\.[0-9]*-(alpha|beta|rc)"},{"id":"v1.17","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.17"},"name":"v1.17","latest":"v1.17.17+k3s1","latestRegexp":"v1\\.17\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.17-testing","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.17-testing"},"name":"v1.17-testing","latest":"v1.17.17-rc1+k3s1","latestRegexp":"v1\\.17\\.[0-9]*-(alpha|beta|rc)"},{"id":"v1.18","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.18"},"name":"v1.18","latest":"v1.18.20+k3s1","latestRegexp":"v1\\.18\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.18-testing","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.18-testing"},"name":"v1.18-testing","latest":"v1.18.20-rc1+k3s1","latestRegexp":"v1\\.18\\.[0-9]*-(alpha|beta|rc)"},{"id":"v1.19","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.19"},"name":"v1.19","latest":"v1.19.16+k3s1","latestRegexp":"v1\\.19\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.20","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.20"},"name":"v1.20","latest":"v1.20.15+k3s1","latestRegexp":"v1\\.20\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.21","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.21"},"name":"v1.21","latest":"v1.21.14+k3s1","latestRegexp":"v1\\.21\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.22","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.22"},"name":"v1.22","latest":"v1.22.17+k3s1","latestRegexp":"v1\\.22\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.23","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.23"},"name":"v1.23","latest":"v1.23.17+k3s1","latestRegexp":"v1\\.23\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.24","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.24"},"name":"v1.24","latest":"v1.24.17+k3s1","latestRegexp":"v1\\.24\\..*","excludeRegexp":"(^[^+]+-|v1\\.24\\.9\\+k3s1)"},{"id":"v1.25","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.25"},"name":"v1.25","latest":"v1.25.16+k3s4","latestRegexp":"v1\\.25\\..*","excludeRegexp":"(^[^+]+-|v1\\.25\\.5\\+k3s1)"},{"id":"v1.26","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.26"},"name":"v1.26","latest":"v1.26.15+k3s1","latestRegexp":"v1\\.26\\..*","excludeRegexp":"(^[^+]+-|v1\\.26\\.0\\+k3s1)"},{"id":"v1.27","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.27"},"name":"v1.27","latest":"v1.27.16+k3s1","latestRegexp":"v1\\.27\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.28","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.28"},"name":"v1.28","latest":"v1.28.13+k3s1","latestRegexp":"v1\\.28\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.29","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.29"},"name":"v1.29","latest":"v1.29.8+k3s1","latestRegexp":"v1\\.29\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.30","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.30"},"name":"v1.30","latest":"v1.30.4+k3s1","latestRegexp":"v1\\.30\\..*","excludeRegexp":"^[^+]+-"},{"id":"v1.31","type":"channel","links":{"self":"https://update.k3s.io/v1-release/channels/v1.31"},"name":"v1.31","latest":"v1.31.0+k3s1","latestRegexp":"v1\\.31\\..*","excludeRegexp":"^[^+]+-"}]}
</script>

Looks to me the json header is still not being respected.

I'll see if there is anything out infra team can do about this. K3s engineering teams do not have access to the channel server or cloudflare configuration.