Error: local-exec provisioner error

Hello
I've been trying to build the grid in two different regions (eu-west-2 and eu-west-1) but I keep seeing the following error when I run the command: make transfer-images  TAG=$TAG REGION=$HTCGRID_REGION
│ Error: local-exec provisioner error
│
│   with null_resource.pull_python_env,
│   on ecr.tf line 39, in resource "null_resource" "pull_python_env":
│   39:   provisioner "local-exec" {
│
│ Error running command 'docker pull
│ <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda-build:build-python3.7': exit status 1. Output: Error
│ response from daemon: manifest for
│ <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda-build:build-python3.7 not found: manifest unknown:
│ Requested image not found
│
╵
╷
│ Error: local-exec provisioner error
│
│   with null_resource.push_dotnet50,
│   on lambda_runtimes.tf line 82, in resource "null_resource" "push_dotnet50":
│   82:   provisioner "local-exec" {
│
│ Error running command 'docker push <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda:5.0.2': exit status
│ 1. Output: The push refers to repository [<aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda]
│ tag does not exist: <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda:5.0.2

I was wondering if someone could point me in the correct direction to get this issue resolved?
Many Thanks
Jinal

Hello!
I think I have temporarily fixed it by:
Manually tagging lambda-build version from 1 to build-python3.7
docker tag <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda-build:1 <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda-build:build-python3.7
docker push <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda-build:build-python3.7

And In vim deployment/image_repository/terraform/lambda_runtimes.tf changed:
docker push ${data.aws_caller_identity.current.account_id}.dkr.ecr.${var.region}.amazonaws.com/lambda:5.0.2

to
docker push ${data.aws_caller_identity.current.account_id}.dkr.ecr.${var.region}.amazonaws.com/lambda:5.0

Not sure, if those are the corrections, but they seemed appropriate!

I am now seeing a slightly different error:
╷
│ Warning: Helm release "htc-agent" was created but has a failed status. Use the `helm` command to investigate the error, correct it, then run Terraform again.
│
│   with module.htc_agent.helm_release.htc_agent,
│   on htc-agent/htc-agent.tf line 9, in resource "helm_release" "htc_agent":
│    9: resource "helm_release" "htc_agent" {
│
╵
╷
│ Error: timed out waiting for the condition
│
│   with module.htc_agent.helm_release.htc_agent,
│   on htc-agent/htc-agent.tf line 9, in resource "helm_release" "htc_agent":
│    9: resource "helm_release" "htc_agent" {
│
╵

Not sure if it's related to the issue above. Any assistance is appreciated!

Figured it out!
There's a bug on the latest version of the image public.ecr.aws/lambda/provided  where the entrypoint lambda_entrypoint_signal.sh has incorrect permissions.
So I used an older image and it's all working fine now!
This is how I did it:
docker pull public.ecr.aws/lambda/provided:al2.2<IP_ADDRESS>
docker tag public.ecr.aws/lambda/provided:al2.2<IP_ADDRESS> <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda:provided

Thank you for raising this issue,
In order to  accelerate the resolution of this error can you please give  us more details about your environment:

operating system
version of the grid (should be one of the following: v0.1.0, or v0.2.0 or latest from main branch)

Best Regards
Clement

Hi Clement
Of course! Apologies, I should have added that at the very top. Please find the details below:
Operating System: CentOS Linux release 7.7.1908
Grid Versions Issue encountered on: latest, 5e9cc89 and v0.2.0

Hi @clementrey-dev
Another issue I found oh the latest Grid Version was, when setting HTCGRID_REGION=eu-west-2 and running:
make init-images  TAG=$TAG REGION=$HTCGRID_REGION
the images were still being built and sent to the ECR in eu-west-1.
Do let me know if you would like me to raise a separate Issue for that.

No need, this is part of the same issue.
Thank you for the info.

HI @jinalshah ,
Fixes has been pushed.
Feel free to reopen this issue if the error persist.

Hi @clementrey-dev
Lovely, thank you very much! Appreciate the swift responses!
Just destroying my existing cluster and rebuilding it with the latest updates.

Hi @clementrey-dev
The following image was not pushed to the registry, so I've had to push it manually:
docker push <aws-account-id>.dkr.ecr.eu-west-1.amazonaws.com/lambda:python3.8

Cheers
Jinal

Also, as part of the pre-reqs/environment prep - it might be worth adding this to the README  (or maybe just adding a little note somewhere):
If ~/.kube/config exists, do mv ~/.kube/config ~/.kube/config.old
Because if you have an existing kube/config file - the build throws an error and it's difficult to trace where the error is coming from! It could catch someone out...

Found another issue:
When obtaining the clientid for the AWS Cognito credentials, running the command:
clientid=$(make get-client-id  TAG=$TAG)

stores the value as:
make[1]: Entering directory `/srv/aws-htc-grid-poc/aws-htc-grid/deployment/grid/terraform' <clientid>make[1]: Leaving directory `/srv/aws-htc-grid-poc/aws-htc-grid/deployment/grid/terraform'

Rather than just the value of the clientid: <123a456>

Documentation or maybe Makefile Update:
Probably worth noting that we should also export:
export HTCGRID_ACCOUNT_ID=$(aws sts get-caller-identity --query 'Account' --output text)
export S3_LAMBDA_HTCGRID_BUCKET_NAME="${TAG}-lambda-unit-htc-grid-${S3_UUID}"

As running make python-quant-lib-path TAG=$TAG ACCOUNT_ID=$HTCGRID_ACCOUNT_ID REGION=$HTCGRID_REGION BUCKET_NAME=$S3_LAMBDA_HTCGRID_BUCKET_NAME without the two export options leads to the build failing...

@jinalshah

Also, as part of the pre-reqs/environment prep - it might be worth adding this to the README (or maybe just adding a little note somewhere):
If ~/.kube/config exists, do mv ~/.kube/config ~/.kube/config.old
Because if you have an existing kube/config file - the build throws an error and it's difficult to trace where the error is coming from! It could catch someone out...

Sometimes I got this errors when my .kube/config  refers to a kubernetes cluster,context or users which have already been terminated. Maybe that could be the reason why you got that error.
Can you eventually confirm it or infirm it  my assumption?

Found another issue:
When obtaining the clientid for the AWS Cognito credentials, running the command:
clientid=$(make get-client-id  TAG=$TAG)

stores the value as:
make[1]: Entering directory `/srv/aws-htc-grid-poc/aws-htc-grid/deployment/grid/terraform' <clientid>make[1]: Leaving directory `/srv/aws-htc-grid-poc/aws-htc-grid/deployment/grid/terraform'

Rather than just the value of the clientid: <123a456>

Can you share with me you version a make (please run make --version) ?

Documentation or maybe Makefile Update:
Probably worth noting that we should also export:
export HTCGRID_ACCOUNT_ID=$(aws sts get-caller-identity --query 'Account' --output text)
export S3_LAMBDA_HTCGRID_BUCKET_NAME="${TAG}-lambda-unit-htc-grid-${S3_UUID}"

As running make python-quant-lib-path TAG=$TAG ACCOUNT_ID=$HTCGRID_ACCOUNT_ID REGION=$HTCGRID_REGION BUCKET_NAME=$S3_LAMBDA_HTCGRID_BUCKET_NAME without the two export options leads to the build failing...

That is unfortunately another bug. Would you eventually create another issue for this items ?

Found another issue:
When obtaining the clientid for the AWS Cognito credentials, running the command:
clientid=$(make get-client-id  TAG=$TAG)

stores the value as:
make[1]: Entering directory `/srv/aws-htc-grid-poc/aws-htc-grid/deployment/grid/terraform' <clientid>make[1]: Leaving directory `/srv/aws-htc-grid-poc/aws-htc-grid/deployment/grid/terraform'

Rather than just the value of the clientid: <123a456>

Can you share with me you version a make (please run make --version) ?

Make version: GNU Make 3.82
Operating System CentOS Linux release 7.7.1908

@jinalshah

Also, as part of the pre-reqs/environment prep - it might be worth adding this to the README (or maybe just adding a little note somewhere):
If ~/.kube/config exists, do mv ~/.kube/config ~/.kube/config.old
Because if you have an existing kube/config file - the build throws an error and it's difficult to trace where the error is coming from! It could catch someone out...

Sometimes I got this errors when my .kube/config refers to a kubernetes cluster,context or users which have already been terminated. Maybe that could be the reason why you got that error.
Can you eventually confirm it or infirm it my assumption?

Weirdly, I repeated the build 4 times with the existing kube/config file in place - but it just didn't like it and kept failing until I removed/renamed it. I had the same issue on the weekend too... (I'll try another build after a demo this Friday and let you know how I get on!)


static or anonymos namespace

Does this issue mean that we should discuss whether we should use static or an anonymous namespace for functions that are local to a translation unit?
I'm open for both, but yes, we should add that to the styleguide. What do you prefer?


Vendor Buying Not Limited

In the vendor buy templates there is a number that should represent how many total the vendor should buy I believe. and this is not respected when a player actually goes to sell the items. They can sell unlimited amounts until the vendor runs out of gold. quite an abusive mechanic if allowed with lots of vendgold, and often times sphere prices items without a value setting on the resources to make it.

related to https://github.com/Sphereserver/Source-X/issues/814

This seems to be related to https://github.com/Sphereserver/Source-X/issues/814
i would expect here we could put settings on how many of a particular item an npc vendor would buy from players and keep in their inventory.

@itemsell Allow u to do custom it.
I am doing a trigger for selllist and buylist, Ill see if I can add this but I see it hard.

The place you're looking at is correct, but you already have the item pointer at vendSell.
vendItem is the item at player's backpack and vendSell is the item at LAYER_BUYS from the vendor.
I'm working at a commit, but using an optional flag, because most people don't really care about this limit.

Closing out, thanks Julian.


Link users to recipes when creating.

When I create a recipe in my prod instance, the user that I'm log-in as isn't getting assigned to the recipe as a creator. No one is.

Fixed with #76


Applying multiple buffering techniques to PDF rendering

Hello,
I've been playing with pdf.js and even though it works great in general, there's a small nitpick which I think I can solve but I thought I'd ask here first.
Every time I call the render() method (with its proper renderContext argument), the canvas' contents get erased for a few milliseconds before the next page appears on the screen. This is how it looks visually: https://gfycat.com/EasygoingPopularAntbear.
I'm running Windows 8.1 and Google Chrome 61.0.3163.79.
I believe this is due to pdf.js rendering the next page's contents on the same canvas the current one is being displayed. Could this be solved by using Double Buffering, by rendering to a second (invisible) canvas and switching them once the task is done?
If this is correct and I'm not working on a corner case, I believe this should be implemented into the library and I'd be more than happy to do it myself. I'd like to know your thoughts about this.
Thanks!

Yes, for you custom solution you can apply a double buffering. We also recommend to use different canvases for different visible pages, which will give the same effect if canvas will be replaced after painting. The demo viewer already applies this technique during zoom operations. Closing as answered.


Don't perform safety check for every job

Only perform the state == draft check if we would send to the live content store.

It would be useful to have the reasoning behind this change in the commit message.

Commit message updated

Merged to avoid bikeshedding.

Commit message updated

:+1:


v2.5.1

Oof, I'm sorry Tom I didn't realize you were cutting a release when I merged the fetch-metadata bump... it's just an action we control and the changes should be super safe, but still, it's annoying!


[WIP] api: remove app_name duplication of route related calls

Partially addresses #361

@treeder @pedronasser @seiflotfy @denismakogon

LGTM

Feel free to resolve the conflict and merge


auto enable hosted add-ons

The related issue: https://github.com/stolostron/backlog/issues/26723
Signed-off-by: Yang Le<EMAIL_ADDRESS>

/assign @qiujian16 @zhujian7

/lgtm
/hold for other reviewers to take a look

/lgtm

/hold cancel


css: Use SCSS nesting in alerts.scss.

Testing Plan:
Only in commit 3262553 there were changes that might affect the current styling. Tested visually and diffed the styles. (All rules have the same priority as before)

Nice, merged, thanks @vrongmeal!  Maybe we should put together a table with a list of all our CSS files and checkboxes for whether we've done this process for them yet?  It seems like we've completed something like half the files, and we might want to start talking about things like splitting out parts of files like zulip.scss and portico.scss.
We'll also start getting into some of our oldest CSS files that generally don't have top-level nesting already in place even in places where they really should (e.g. settings.scss and subscriptions.scss).
$ wc -l static/styles/*
    93 static/styles/activity.scss
   140 static/styles/alerts.scss
   372 static/styles/app_components.scss
    46 static/styles/archive.scss
   271 static/styles/billing.scss
   136 static/styles/components.scss
   503 static/styles/compose.scss
   154 static/styles/drafts.scss
   293 static/styles/hotspots.scss
   147 static/styles/informational-overlays.scss
   135 static/styles/input_pill.scss
   114 static/styles/integrations_dev_panel.css
  4285 static/styles/landing-page.scss
   547 static/styles/left-sidebar.scss
   322 static/styles/lightbox.scss
   378 static/styles/media.scss
   591 static/styles/night_mode.scss
   359 static/styles/popovers.scss
  2247 static/styles/portico.scss
  1078 static/styles/portico-signin.scss
     4 static/styles/portico-styles.scss
   393 static/styles/pygments.scss
   301 static/styles/reactions.scss
     7 static/styles/reuseable_components.scss
   242 static/styles/right-sidebar.scss
  1942 static/styles/settings.scss
   250 static/styles/stats.scss
  1109 static/styles/subscriptions.scss
    11 static/styles/typing_notifications.scss
    51 static/styles/user_circles.scss
    64 static/styles/user_status.scss
   139 static/styles/widgets.scss
  3031 static/styles/zulip.scss

@timabbott I created #12528 to keep track. I'm starting with lightbox.scss and then we can move on to more complex files.


Inconsistent punctuation when sentence ends with quoted text

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
There are many places that don't follow the style guides on punctuation.
What part(s) of the article would you like to see updated?
Anywhere that has:

For more information, see "something." # note the period inside the quotation mark

to:

For more information, see "something". # note the period outside the quotation mark

Additional information
I've done a rudimentary search in *.md files in VS Code:

". -> 470 instances
." -> 8,341 instances

Seeing a huge number of ." usage despite being against the style guides prevented me from raising a pull request myself (maybe I've misunderstood the style guide? 🤔).
Style guide: Punctuation

When referencing a UI element in quotation marks, place any subsequent punctuation outside of the quotation marks

Maybe it's specific to "UI elements" as opposed to "links"? 🤔
But, this 👇 is also a "link", why is the punctuation outside the quotation mark? 🤔
Building and testing Java with Gradle

Compare that 👆 with its sister page "Building and testing .NET":

Vào 7:17, CN, 18 thg 2, 2024 welcome[bot] @.***> đã
viết:

Thanks for opening this issue. A GitHub docs team member should be by to
give feedback soon. In the meantime, please check out the contributing
guidelines https://docs.github.com/en/contributing.
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/issues/31712#issuecomment-1950611773, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BGCSWPZIMCMA4FQL7LYL4E3YUFCBRAVCNFSM6AAAAABDNV4N62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGYYTCNZXGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Code of Conduct

[x]  I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
There are many places that don't follow the style guides on punctuation.
What part(s) of the article would you like to see updated?
Anywhere that has:

For more information, see "something." # note the period inside the quotation mark

to:

For more information, see "something". # note the period outside the quotation mark

Additional information
I've done a rudimentary search in *.md files in VS Code:

". -> 470 instances
." -> 8,341 instances

Seeing a huge number of ." usage despite being against the style guides prevented me from raising a pull request myself (maybe I've misunderstood the style guide? 🤔).
Style guide: Punctuation

When referencing a UI element in quotation marks, place any subsequent punctuation outside of the quotation marks

Maybe it's specific to "UI elements" as opposed to "links"? 🤔
But, this 👇 is also a "link", why is the punctuation outside the quotation mark? 🤔
Building and testing Java with Gradle

Compare that 👆 with its sister page "Building and testing .NET":

@itecompro Thanks so much for opening this issue! I'll get this triaged for review ✨

FYI:

Maybe it's specific to "UI elements" as opposed to "links"? 🤔

Exactly that.
So there will be both instances — page titles like …, see "[AUTOTITLE]." should include the punctuation inside the quoted title, whereas exact reference to an element or similar item has the quoted text exactly match like …is "push" or "pull_request".
Yes, there are issues with both, as demonstrated above. Fixing needs to be done contextually thou, not a mass find&replace.

@janbrasna,
References to UI elements are consistent and they have the punctuation outside; no problem there ✅
I do, however, see inconsistencies with links themselves (I've already put an example in my original request, but here is another one):

should include the punctuation inside the quoted title

I don't want to be the pedantic one here (or maybe I do, otherwise why did I open the issue in the first place 😂), but it's not grammatically correct 🤓
Periods/Punctuation belong to the sentence, not the link (which is why it's not hyperlinked, i.e. outside markdown's link []()).
Putting a period inside quotation marks (which is just part of the sentence) doesn't justify not completing the sentence; the sentence is Please see SOMTHING.; now SOMETHING happens to be a link: "Some link"
But yes, I agree. It's gonna cause problems with a mass find/replace. Best to be fixed on a case-by-case basis.
Thanks guys 🙏


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-extensions/client-writers
/assign knative-extensions/client-writers
Produced by: knative-extensions/knobots/actions/update-deps

@cardil is the golangci-lint version too old. The errors seems a bit strange. Not popping in GH action check.

/approve
/lgtm


Add training instances and training partners to a map

We need to guide users to our training, the closest one if possible to save the environment.
We already had some attempts to collect this information but no one ever succeed as far as I remember. What do you think about the following idea and make it github based?
https://github.com/bgruening/galaxy-maps
@bebatut @nekrut @hrhotz

cool :-)
On 09.08.2016 13:12, Björn Grüning wrote:

We need to guide users to our training, the closest one if possible to
save the environment.
We already had some attempts to collect this information but no one
ever succeed as far as I remember. What do you think about the
following idea and make it github based?
https://github.com/bgruening/galaxy-maps
@bebatut https://github.com/bebatut @nekrut
https://github.com/nekrut @hrhotz https://github.com/hrhotz
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bgruening/training-material/issues/15, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALMe0Rs8CPdEXrMlz_-Y2AFW3I_CKMxAks5qeGCOgaJpZM4Jf93n.

--
Dr. Dilmurat Yusuf
Bioinformatics Scientist
Scientific Bioinformatics Platform
The Berlin Institute for Medical Systems Biology (BIMSB)
Max Delbrueck Center (MDC) for Molecular Medicine
Robert-Rössle-Str. 10, 13125, Berlin, Germany
Building 89, Room 1.08
web: http://bioinformatics.mdc-berlin.de/team.html#dilmurat-yusuf-phd
email<EMAIL_ADDRESS>office tel: +49 30 9406 1795

Bjoern, you are a constant source of great ideas! :)

Or you could add to the Galactic Radio Telescope. The GRT is not really used yet, but going forward this might be more useful for administrators than tracking in a single geojson file.
The GRT already has infrastructure for a registry of Galaxies with short name + description, it would be trivial to add a "please provide your lat/lon" field. :)

We start to collect instances and instructors in this map: https://github.com/bgruening/galaxy-maps.
So, I think we can close this issue


wind 10 to win 7 still errors

I couldn't make the unzip and remove function work. Still orig 5 errors. After scan, comment was not formatted.
I am a klutx, so maybe its me.
thankks
This work item was migrated from CodePlex
CodePlex work item ID: '3'
Vote count: '1'

[lonestranger@13/04/2016]
Nothing cam up while using repair function. Thoughts?

[lonestranger@13/04/2016]
Nothing came up during repair cycle

[lonestranger@18/04/2016]
Mon 18 Apr
Lets try again.  The point and clk does not work for me.  When scanning now, the 5 remaining say; improperly coded. Printer, safe restore, music, anti virus(I don't know if there'e a # 5) don't work.  Can you try aother approach, take this computer over and correct???  What if I load back windows 10, will my problems dissapear???  If I cannot, who do you recommend??
thanks
lonestranger

[lonestranger@22/04/2016]
22 April 1630
I may have more than one comment section, BUT today I ran the repair tasks and after following your inst. the results were 5 repairs successful.
Thanks for your patience and great effort on your part.
lonestranger

Issue closed by Dijji with comment
Resolved as described by the raiser
Reason closed
Fixed


[BUG] v2 volume always displays engine upgrade available on UI

Describe the bug (🐛 if you encounter this issue)
Install Longhorn master-head (longhorn-manager be08850), and create a v2 volume,  always displays engine upgrade available on UI:

But it's actually unable to be upgraded:

To Reproduce
create a v2 volume on Longhorn master-head
Expected behavior

Support bundle for troubleshooting

Environment

Longhorn version:
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of management node in the cluster:
Number of worker node in the cluster:

Node config

OS type and version:
Kernel version:
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe/HDD):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:
Impacted Longhorn resources:

Volume names:

Additional context

The task is https://github.com/longhorn/longhorn/issues/7445
cc @scures

Duplicated.


[BUG]

for example, if I want to play the song Bad Girls in my Shazam playlist, I have to go to the song Eternal Youth so I can play Bad Girls. This is quite confusing. Also, there is the problem when I have random mode on and want to listen to a specific song, I usually go to the song and click on it. But now it plays me a completely different song. My understanding of the mode is that when I skip the song I get a random song, but when I click on a specific one I also want it to play.

Wrong repository.
Try making an issue in the ciderapp/Cider repository.


Share and use public and private key

How could I go about sharing and then using a generated public key?
I have wrote the functions:
-(NSString*)keyTo64String:(id)key{
    NSData *key_data = [NSKeyedArchiver archivedDataWithRootObject:key];
    return [key_data base64EncodedStringWithOptions:0];
}

-(id)string64ToKey:(NSString*)key{
    NSData* priv_actual_data = [[NSData alloc] initWithBase64EncodedString:key options:0];
    return [NSKeyedUnarchiver unarchiveObjectWithData:priv_actual_data];
}

The first function will return a string representation of the MIHPublicKey or MIHPrivateKey object.
And the second from the string to the object.
It would be cool if I could export the key in a format similar to a .pem file. It would also be great if I could read that format and turn it back into the object.
How would you recommend doing it?

I have noticed the dataValue but what about being able to set this?

All keys (symmetric and asymmetric) have a constructor - initWithData:dataValueand a getter dataValue which work with the raw key values. PEM is just the raw values BASE64 encoded. Have a look at the unit tests in MIHRSAKeyTests.m for sample usage with PEM files.

Awesome thank you.

Yes, ECC was on my TODO list. But since I never needed it I also never done so.


show names of stopped containers

This got broken in b78c503
Fixes #1691

Thanks for the fix! LGTM (provided circle gets green)


fix(55796): JSDoc does not support @this when using an arrow function as method in class

Fixes #55796

This PR adds an error for @this on an arrow function. It doesn't allow @this to change the type of this in the body of the arrow function.


Floating submit button possible?

Hi,
I try to create floating submit button  which keep position even croll up and down on table in card.
Possible?

CSS position:fixed to make an element keep its position even while scrolling. Does it solve your issue?


not a real issue

Is mkp224o intended to run until cancelled or does it self-terminate? It's generated 12 addresses and it's still running lol

Yes that is how it's supposed to work. You can pass -n <count> to have it stop after finding <count> keys.

thank you

i g closing because answered.


FE v5.1.0-beta11 swagger exception due to empty schema being removed

        config.Serializer.RequestDeserializer = async (req, tDto, jCtx, ct) =>
        {
            using var reader = new System.IO.StreamReader(req.Body);
            return Newtonsoft.Json.JsonConvert.DeserializeObject(await reader.ReadToEndAsync(), tDto);
        };

Nothing has changed in the code, and I use Newtonsoft.Json as a serialization
System.InvalidOperationException: Could not find the JSON path of a referenced schema: Manually referenced schemas must be added to the 'Definitions' of a parent schema.
at NJsonSchema.JsonPathUtilities.GetJsonPaths(System.Object rootObject, System.Collections.Generic.IEnumerable`1 searchedObjects, Newtonsoft.Json.Serialization.IContractResolver contractResolver) at offset 151
at NJsonSchema.JsonSchemaReferenceUtilities.UpdateSchemaReferencePaths(System.Object rootObject, System.Boolean removeExternalReferences, Newtonsoft.Json.Serialization.IContractResolver contractResolver) at offset 66
at NJsonSchema.Infrastructure.JsonSchemaSerialization.ToJson(System.Object obj, NJsonSchema.SchemaType schemaType, Newtonsoft.Json.Serialization.IContractResolver contractResolver, Newtonsoft.Json.Formatting formatting) at offset 12
at NSwag.AspNetCore.Middlewares.OpenApiDocumentMiddleware.<GetDocumentAsync>d__11.MoveNext() at offset 383
at NSwag.AspNetCore.Middlewares.OpenApiDocumentMiddleware.<Invoke>d__10.MoveNext() at offset 209
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.<Invoke>d__6.MoveNext() at offset 363

beta 11 was supposed to fix this.
see here: https://discord.com/channels/933662816458645504/1014025472792870992
can you help me reproduce this issue?
can you reference the FastEndpoints.Swagger source code instead of the nuget package in your project and place a breakpoint on this line and see which schema is being removed.
can you post the troublesom request dto here so i can check it out.
thanks!

    public abstract class BaseRequest : BaseAccessRequest
    {
        [FromHeader(HeaderName = "openid"), DefaultValue("user's openId")]
        public string? OpenId { get; set; }
    }
    /// <summary>
    /// 强制AccessToken
    /// </summary>
    public abstract class BaseAccessRequest
    {
        /// <summary>
        /// 强制客户端AccessToken
        /// </summary>
        [FromClaim("role")]
        public string? Role { get; set; }
    }

try v5.1.0-beta15. should be fixed now.
the empty schema removal was having issues with inherited dtos like above.
so it's not possible to remove empty schema from swagger doc when using inheritance like you're doing.
so you must make nswag flatten the inheritance hierarchy for empty shchema removal to work.
doing the following will take care of it:
builder.Services.AddSwaggerDoc(removeEmptySchemas: true);

spent almost 4 hours trying to figure out a better solution. this is the best i could come up with.
if someone else has a better approach, please send in a PR.


Restore mutable variables as the default

To get the tests going again.

@swift-ci please test

It seems like the REPL-related tests pass at least.

@swift-ci please test

@swift-ci please test

After consulting in person, :shipit:


Spelling fix.  Changed ana to and

@sguitardude : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks, @sguitardude


integration testing

We should perform an integration test in presubmit. As any additional code complexity is added and we start to roll out registry.k8s.io to projects, it is very important that we test thoroughly, and unit testing alone will not be sufficient.
We should start by having a tool like crane pull an image through a locally running copy of archeio in an integration test target, and adding this to CI.

See also https://github.com/kubernetes-sigs/oci-proxy/issues/24 for full e2e testing post-merge.

/assign
/sig k8s-infra

Ref: https://github.com/kubernetes/k8s.io/issues/3411

done in #47


feat: gRPC Access Log Service (ALS) sink

replace https://github.com/envoyproxy/gateway/pull/3062

/retest

/retest


Corrected typo

This PR will resolve issue #29 .

Something is going on with the pipeline build. I'm looking in to it now.

@96RadhikaJadhav , your change did not cause the failure.
The Pre-job: Get the PFX file certificat job failed because forks are not allowed to access secure files in the pipeline:

References secure file. PRs from repository forks are not allowed to access secrets in the pipeline. For more information see https://go.microsoft.com/fwlink/?linkid=862029

Once your change merges, the build will pass. Sorry for the confusion, you're the first contributor to commit from a fork... So we all learned something today. I'll updated the README with this information.


Drop CHANGELOG.md and switch to github releases

Currently changes are tracked in [CHANGELOG.md], including the version, which is a bit of a pain to manage if there's more than 1 thing going on at a time due to merge conflicts on a non-critical file.
Historically I've cleaned this up by just pushing to master, however that's not an option anymore.  As such, I propose dropping it (marking it as deprecated but leaving it for historical value) entirely and switching to github releases.  This would be done after #264
Personally I'm not a big fan of having the history tied to the github ecosystem rather than the repo, but I value the productivity more.

opinions, @ash2k, @aelse ?

👍

Doesn't a merge from master into a branch before raising a PR solve this? We're not so fast moving that changelog gets frequent updates.

It does, but it effectively serializes the PR process, and #260 is up to 3 merges now.

If we switch to github releases it makes this project more of a snowflake concern for us to manage and I want to avoid that. It doesn't seem like it's a huge burden to resolve conflicts in a markdown file, even if it happens 2 or 3 times in the course of a long running PR.
If we can do better on reducing the time it takes to get changes merged in this problem probably goes away for the most part. Not all of us are paid to work on this project (any more, @tiedotguy  😄) and any time given is a gift, but I'll put more focus on giving timely feedback in future

I think it is fair enough to say that we carry on with using the change log and using tagged commits @tiedotguy


Auto reshare new RK with same Keeper on 2nd level for level 3 setup

Check level 3 is getting complete or not.

-Not able to complete level 3.After scanning the secondary key QR, the approval model is not showing up

verified this issue on devapp v1.9.5(337)


"Address" question type: implement Address Line 2

#398 added the bare bones of the Address question type; the only part left out was Address Line 2. Let's add that to the data model and the UI. See that issue for more context.

Thanks for making this @neel-a-mehta !


libspdm_{set,get}_data should check location

libspdm_data_location_t is declared as
https://github.com/DMTF/libspdm/blob/6684f43117784b12e25e665df65d1d122540f11f/include/library/spdm_common_lib.h#L146-L151
However LIBSPDM_DATA_LOCATION_LOCAL and LIBSPDM_DATA_LOCATION_SESSION typically get grouped together. For example
https://github.com/DMTF/libspdm/blob/6684f43117784b12e25e665df65d1d122540f11f/library/spdm_common_lib/libspdm_com_context_data.c#L186-L201
In this example the function should return an error or assert if parameter->location == LIBSPDM_DATA_LOCATION_SESSION.

Some aren't even checked. For example
https://github.com/DMTF/libspdm/blob/6684f43117784b12e25e665df65d1d122540f11f/library/spdm_common_lib/libspdm_com_context_data.c#L264-L269


[WIP] Added Travis CI

LGTM @quarckster, we just need to figure out why required packages are not installed (might be caused by Go 1.11 instead of 1.12 or 1.13)

Yeah, I'm figuring out how to manage golang build system.

Probably you need to set
export GO111MODULE="on"


This graph is rendered kinda funky

IMO the in root should be encapsulated in their own subgraph. For what it's worth, this happens if you merge duplicates:

main.hcl is:
# create certificates for a Kubernetes cluster
param "master_ip" {}

task "directory" {
  check = "test -d ssl"
  apply = "mkdir ssl"
}

task "ca.key" {
  check = "test -f ssl/ca.key"
  apply = "cd ssl; openssl genrsa -out ca.key 2048"

  depends = ["task.directory"]
}

task "ca.crt" {
  check = "test -f ssl/ca.crt"
  apply = "cd ssl; openssl req -x509 -new -nodes -key ca.key -subj \"/CN={{param `master_ip`}}\" -days 10000 -out ca.crt"

  depends = ["task.ca.key"]
}

module "cert.hcl" "server" {
  params {
    cn   = "{{param `master_ip`}}"
    name = "server"
  }

  depends = ["task.ca.key", "task.ca.crt"]
}

module "cert.hcl" "kubelet" {
  params {
    cn   = "{{param `master_ip`}}"
    name = "kubelet"
  }

  depends = ["task.ca.key", "task.ca.crt"]
}

cert.hcl is:
# cert
param "cn" {}

param "name" {}

param "ca_crt" {
  default = "ca.crt"
}

param "ca_key" {
  default = "ca.key"
}

task "directory" {
  check = "test -d ssl"
  apply = "mkdir ssl"
}

task "key" {
  check = "test -f ssl/{{param `name`}}.key"
  apply = "cd ssl; openssl genrsa -out {{param `name`}}.key 2048"

  depends = ["task.directory"]
}

task "csr" {
  check = "test -f ssl/{{param `name`}}.csr"
  apply = "cd ssl; openssl req -new -key {{param `name`}}.key --subj \"/CN={{param `cn`}}\" -out {{param `name`}}.csr"

  depends = ["task.key"]
}

task "crt" {
  check = "test -f ssl/{{param `name`}}.crt"
  apply = "cd ssl; openssl x509 -req -in {{param `name`}}.csr -CA {{param `ca_crt`}} -CAkey {{param `ca_key`}} -CAcreateserial -out {{param `name`}}.crt -days 10000"

  depends = ["task.csr"]
}

This is kinda closed since the duplicates are merged by default now. I'm going to close it since it's getting out of date. If we get complaints about this kind of thing in the future they should go in their own issues anyway.


Update Builder.php

I have users table that has 5000 rows.
I has some query like this
select users.* from `users` group by `users`.`id` order by `users`.`id` asc

(don't ask me why I am grouping this, it's just a little part of a query which I has issue with)
Result:
$query = $model->groupBy('id');

$query->count();  //  1
//  because count() didn't remove 'group by', and it's return
//  $results[0] which is 1 (as another 5000 rows of aggregate column)

$query->get();
//  Collection {
//    #items: array:5000
//  }

So with cloneWithout(['groups']), we will remove 'group by' and result of method count() will be correct

hmm, nope. This will break count() when we really need 'group by'


New preset: highway=proposed

It's a very popular tag, used over 85,993 times.
https://wiki.openstreetmap.org/wiki/Tag:highway%3Dproposed
I often use it because in my city they often create new name for a future street and create addresses with this street, although sometimes the road isn't physically build.
Fields:

Type
Name
Source

The last tag is important, because proposed roads are not visible on the ground so filling in this field is important.
It can be even unsearchable preset, but at least this. It will be easier to fill in the fields even after typing highway=proposed manually.

Hmm this one's tricky. As the wiki notes, proposed features are controversial since they're not verifiable on-the-ground. Plus there could be plans for non-authoritative sources, multiple different plans, plans that change dozens of times, plans that get pushed back years, and plans that get cancelled altogether. I definitely don't think we can have an addable/searchable preset; I'm not sure about an unsearchable one.

But it's used anyway. So it would be good to see the preset name if someone click such feature while editing. That's why I suggested to be unsearchable.

We don't add presets just because people are using a tag. People can make up tags for anything and often do.
Unsearchable presets have their place, but mappers who encounter may them understandably assume the feature type is "official" and get confused when they can't add their own.

I would strongly against promoting this kind of unverifiable, controversial type of data that is never based on survey on mapping from aerial images.

@maro-21 After further consideration, I think this type of change needs to be discussed in the broader OSM community first. An unsearchable preset may seem like a minor thing, but it'd be a significant change to support proposed features in any way.

I would strongly against promoting this kind of unverifiable, controversial type of data that is never based on survey on mapping from aerial images.

Proposed highways aren't rendered on maps anyway. No one will be hurt.
This tag is often used anyway, no matter if there is a preset or not.
Quincy: Why? This preset is for mappers, not for renderers. Not having a preset won't stop people from adding such roads.

No one will be hurt.

Collecting in OSM data that should not be collected in OSM in undesirable (highway=proposed is quite controversial here)

Not having a preset won't stop people from adding such roads.

But it will reduce it and they will be lower chance of false opinion that adding such data is supported by OSM community.

Proposed highways aren't rendered on maps anyway.

There is more than one map, see for example https://jakdojade.pl/krakow/trasa/


Page dots briefly jump to page 0 on drag

Cannot repro in emulator, but sometimes ArrayPageViewController.pageControlSelectionDidChange gets called with 0, then 1, 2, etc... until arriving at the correct page.

Can no longer repro on iOS 15.1.1.


feat(docs): using telepresence in development mode.

Description
Updates the CONTRIBUTING.md adding instructions on how to use telepresence to run the Kubewarden controller locally.
Fix https://github.com/kubewarden/kubewarden-controller/issues/548
Test
Follow the instructions added in the PR.

I followed the instructions of the PR locally. There are some extra things that have to be done.
Avoid fights between the in-cluster controller and the one on the dev machine
Telepresence will forward the webhook calls to the local process, but the Pod running the controller will keep working inside of the cluster.
Because of that, we will end up having two controllers attempting to reconcile the same set of resources. This leads to "interesting" situations... like the default PolicyServer being continuously redeployed because the two controllers keep changing the Deployment definition :facepalm:
To prevent that from happening, delete the controller that was created by the helm chart:
kubectl delete -n kubewarden deployments.apps kubewarden-controller

Create a new one using the dummy file I've attached. We must have a Deployment defined for kubewarden-controller, otherwise telepresence won't be able to intercept it.
kubectl apply --namespace kubewarden -f hack/kubewarden-controller-dummy-deployment.yaml

Use the proper certificate
The local webhook server is reached by the kube-api-server, but it complains because the certificate being used uses the wrong SAN. It's not the one of the cluster-ip, but it's something about localhost.
I've fixed that by changing the run target of the Makefile to:

create an empty cert directory
download the certificate and its private key from the kubernetes secret

I've then patched the main program to take a new cli param that is used to customize the directory where these files are expected to be. By default the code from kube-builder searches the certificate under /tmp/something, which is the path where k8s injects the secret, this flag overrides this behavior.
The controller has to be started with the following command, this should be patched inside of the instructions:
WEBHOOK_HOST_LISTEN=<IP_ADDRESS>make run

Now everything should be working as expected
Don't forget to quit!
The instructions should also mention that you should do a telepresence quit once you're done with it (or if you delete the testing cluster and create it again). Otherwise weird behaviors will pester you.
Summary
The right order to follow is:

install cert-manager
install kubewarden crds
create kubewarden namespace
install the kubewarden-controller helm chart, I'm pretty sure we can use the default options (no need to change the run as root because we're going to delete the deployment)
delete the deployment of the kubewarden-controller
create the dummy deployment of the kubewarden controller
telepresence helm install
telepresence connect -n kubewarden
telepresence intercept kubewarden-controller --port 9443:443
WEBHOOK_HOST_LISTEN=<IP_ADDRESS>make run

Everything should be working now, to verify that:
helm install -n kubewarden kubewarden-defaults --set recommendedPolicies.enabled=True kubewarden/kubewarden-defaults

You should see all the output produced by the controller running on your workstation
More notes
We are not running the controller in "local development" mode anymore. Because of that the webhooks exposed by the controller are NOT registered by the Go code. We rely on the (Validating|Mutating)WebhookConfiguration objects created by the helm chart.
This is fine, unless you add a new endpoint that is not yet known by the helm chart. I think this is fine, we have to document that.

@jvanz I've done a forced push against your branch because I needed to rebase against main

Telepresence will forward the webhook calls to the local process, but the Pod running the controller will keep working inside of the cluster.

I'm not facing this issue. After the pod with the telepresence agent is running the old one is removed:
$ k8s get pods -n kubewarden
NAME                                     READY   STATUS    RESTARTS   AGE
kubewarden-controller-5577f5dbb6-m7w9w   2/2     Running   0          3m41s

Furthermore, if we applied the deployment manually, we will not using the production helm charts which, as far as I remember, will be one of our goal. To be as the closest as we can from the production. I agree that there are cases where we need something more customized that may require another deployment file and so on. But I'm not sure if this will be required for most of the cases.

After a discussion in other communication channels, we device to use tilt. Closing this PR.


Chanfana using Hono and Swagger UI

Looking at the Chanfana Minimal Hono Example
import { fromHono, OpenAPIRoute } from 'chanfana'
import { Hono } from 'hono'
import { z } from 'zod'

export class GetPageNumber extends OpenAPIRoute {
  schema = {
    request: {
      params: z.object({
        id: z.string().min(2).max(10),
      }),
      query: z.object({
        page: z.number().int().min(0).max(20),
      }),
    },
  }

  async handle(c) {
    const data = await this.getValidatedData<typeof this.schema>()

    return c.json({
      id: data.params.id,
      page: data.query.page,
    })
  }
}

// Start a Hono app
const app = new Hono()

// Setup OpenAPI registry
const openapi = fromHono(app)

// Register OpenAPI endpoints
openapi.get('/entry/:id', GetPageNumber)

// Export the Hono app
export default app

It uses the "normal" hono and zod imports, and not the OpenAPIHono from https://hono.dev/examples/zod-openapi which I assume is the recommended way with Canfana?
To expose the SwaggerUI we can do:
app.get('/ui', swaggerUI({ url: '/doc' }));

but how to expose the openapi spec under /doc using Chanfana and Hono?

Actually this was quite simple to do, but my approach above was wrong.
There was no need to install @hono/swagger-ui nor to do app.get('/ui', swaggerUI({ url: '/doc' }));.
Just use do this and it worked:
// Setup OpenAPI registry
const openapi = fromHono(app, {
    docs_url: "/",
});


Suggestion: add link to your paper

Hi authors! I'd suggest you link your published paper to this repo for ease of finding a technical reference: https://content.iospress.com/articles/semantic-web/sw233471

Dear @george1459 Thanks for the hint. We (@xixi019) will do so :D


FIXfix map proto contains_null

Proposed changes
when we select map in order by and limit;  be node will coredump
here is stack info

Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.03 seconds
stream load tsv:          506 seconds loaded<PHONE_NUMBER>9 Bytes, about 140 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          32 seconds loaded 861443392 Bytes, about 25 MB/s
insert into select:          29.7 seconds inserted 10000000 Rows, about 336K ops/s
storage size:<PHONE_NUMBER>7 Bytes


Better logging of processed webhooks

Heres the data i want to log:
f"{method} {path} {size} {status} {response_time} {forwarded_host} {user_agent}"
Probably will want this to be json parsable too

#109


Added more comprehensive voice command tests

Overview
Added more comprehensive voice command tests, also changed the Teardown script order so bugs involving a prematurely destroyed MixedRealityToolkit and MixedRealityPlayspace game objects don't hide the actual test errors
Changes

Fixes: #5216

/azp run

/azp run


nodejs: switch from EXTRA_OECONF to PACKAGECONFIG_CONFARGS in configure

Arguments from PACKAGECONFIG only get appended to EXTRA_OECONF if the
autotools class is inherited in the recipe. As this is not the case
with the node recipes, the PACKAGECONFIG settings never make it into the
build. Switch to directly using the PACKAGECONFIG_CONFARGS variable to
the right arguments get passed through.

Looks like PACKAGECONFIG_CONFARGS is going to be supported in Yocto 2.2 release. Correct?

I'm not 100% sure on the timescales but I know that this layer coupled with current oe-core master doesn't take packageconfig variables into account without this fix. When they changed it I don't know; I havn't seen anything on the mailing lists.

Found it
https://github.com/openembedded/openembedded-core/commit/c98fb5f5129e71829ffab4449b3d28082bc95ab4

Yes, this is not yet in 2.1 Krogoth but probably will land in 2.2 release.
Based on this information, I'm +1 to including this in master branch, but I'll be careful not to merge this to krogoth or jethro branches going forward.

Sorry, I just created another pull, did not look here. Why was this not merged?
There is now one issue with this patch here: It is missing the node v7 include.
Also the real transition happened here:
https://github.com/openembedded/openembedded-core/commit/c2f7da23d07b10318e8d8bf68e3edd759d7823a3
It was not mandatory in krogoth, but already supported. I can confirm that it is working with krogoth.

Merged in #66


[Hub Generated] Review request for Microsoft.Subscription to add version preview/2020-01-01-preview

If you are a MSFT employee you can view your work branch via this link.
Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

this pr seems to be very old, pls reopen if still needed


Poor formatting: Newtype-like expression

Original
(Less than 100 characters)
        Err(Error::custom("data did not match any variant of enum PaymentSourceParams"))

After rustfmt
        Err(Error::custom(
            "data did not match any variant of enum PaymentSourceParams",
        ))

This is an expected behavior: function and macro calls are split into multiple lines when the arguments have more characters than the threshold. Err and Error::custom are combined to avoid a weird-looking indentation.


How is it different from other MVVM architecture?

Hey @NourEldinShobier, nice work.
Can you highlight how this package is different from other MVVM packages like stacked.
Thanks.

Hi @saileshbro , actually I did highlight the differences between both of them in the FAQ section.

I believe the buildcontext should never be accessed inside viewmodel.

hi @sanalkv , that's a good point... Long story short, I believe each person has different preferences. Being able to access the buildcontext from the view model has some advantages like fetching the providers from the VM itself...etc. Basically, it helps you to keep the view clean of any logic that is not related to view itself
That being said, I know that it's a double-edged feature that some developers might abuse, but that doesn't mean it shouldn't exist
Again, I believe each person has different preferences =D


Add Some Explanation in /README.md about the TM Tutorial

Needs a similar explanation to what exists for gpu stuff

yes, working on it


character menu problem

Describe your bug here. Mind you, if you are modding, please try testing your bug in a clean version of the engine instead, this ensures the bug is actually caused by the engine itself. Also, if you're using an older version of JSE, please try the latest action build in the Actions tab or the latest release build. The issue has probably been fixed since that version. Oh yeah, and also be sure to check the pinned 'JS Engine: Known Issues' issue, to double check if your issue hasn't already been found!
it happens in the character debug
now I have to rechart the song thanks to this horrible bug, now my chart is now lost so I have to start from the beginning thanks to this horrible bug
Command Prompt/Terminal/Crash logs (if existing)
editors/ChartingState.hx (Line 1035)
flixel/ui/FlxButton.hx (Line 521)
flixel/ui/FlxButton.hx (Line 507)
openfl/events/EventDispatcher.hx (Line 444)
openfl/display/DisplayObject.hx (Line 1400)

Uncaught Error: Null Object Reference
Please report this error to the GitHub page: https://github.com/JordanSantiagoYT/FNF-PsychEngine-NoBotplayLag

> Crash Handler written by: sqirra-rng

Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
I will explain it in words

so when I was adding my new character to the mod I accidentally renamed "character name down" to "character name" I tried fixing it and when I tried fixing it and clicked add/update the game crashed

this bug was found on version 0.19.1

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
the bug happened in my fnf mod
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

..
don't use 1.19.0 first of all

yeah update to the latest version, since that might’ve fixed that issue in a newer version

..
don't use 1.19.0 first of all

idk why i use 1.19.0


Latest image empty IP address

Hi
I pulled latest mongo from docker hub, and docker inspect mongo | grep "IP" shows empty address.
       "Networks": {
            "cornerjob_default": {
                "IPAMConfig": null,
                "Links": null,
                "Aliases": [
                    "d3a5481cecc5",
                    "mongo"
                ],
                "NetworkID": "2dccd35cf9479b86ce32ee600153c5f74f3eaa162532412b2c5b9e4a2b90a932",
                "EndpointID": "",
                "Gateway": "",
                "IPAddress": "",
                "IPPrefixLen": 0,
                "IPv6Gateway": "",
                "GlobalIPv6Address": "",
                "GlobalIPv6PrefixLen": 0,
                "MacAddress": "",
                "DriverOpts": null
            }
        }
    }

How can I set a IP on docker-compose.yml file?

 I had to link it to my Docker-container. yml file first.
Thanks


Update armeria to 1.24.1

About this PR
📦 Updates com.linecorp.armeria:armeria from 1.24.0 to 1.24.1
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.linecorp.armeria", artifactId = "armeria" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.linecorp.armeria", artifactId = "armeria" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #1872.


Arabic translation of Basic Algorithm Scripting

[ ] Meet Bonfire
[ ] Reverse a String
[ ] Factorialize a Number
[ ] Check for Palindromes
[ ] Find the Longest Word in a String
[ ] Title Case a Sentence
[ ] Return Largest Numbers in Arrays
[ ] Confirm the Ending
[ ] Repeat a string repeat a string
[ ] Truncate a string
[ ] Chunky Monkey
[ ] Slasher Flick
[ ] Mutations
[ ] Falsy Bouncer
[ ] Seek and Destroy
[ ] Where do I belong

Closing in favor of https://github.com/FreeCodeCamp/TranslationExpansion/issues/24


[perf_tool] Add stub implementation of an experiment Runner

Summary: Adds an empty implementation of the experiment Runner. This will be responsible for executing all the different steps of an experiment, from getting a cluster, to deploying workloads, to recording metrics. Currently, it doesn't do anything. This PR also adds the protobuf definition for RunSpec which specifies how long to run experiments for.
Type of change: /kind test-infra
Test Plan: No functional changes, just adds a stub for the runner which will be implemented in future PRs.

@pixie-io-buildbot test this please

@pixie-io-buildbot test this please


Enclose python exe path in ""

Fixes #6746
Enclose the path of the python executable in double quotes so that executing a script in an external system terminal works correctly when the path to the Python interpreter contains spaces.

@jnsebgosselin, the test failures are unrelated to this. I'll fix them in #6736.

Ok, after this PR, I'm aiming to be able to execute this script
# -*- coding: utf-8 -*-
print('test')

in an external system console with a Python executable located in C:\Python36's Path Test in a file saved in C:\Queen's Space\let's test this.py.
Anything else I should include?

Using utf-8 chars in the path is always a good idea (e.g. Chinese or Arabic chars).

@ccordoba12 Have we defined a typical string to use to test this? If not, maybe we should so that our test for this are consistent across?

There are some Chinese and Arabic chars floating around in several test files. Perhaps you could try to define them as a constant in a single place in this PR.

Perhaps you could try to define them as a constant in a single place in this PR.

Ok good idea, I'll try that.

@ccordoba12 I'm setting the path to the interpreter in the Python  interpreter option as in the screenshot below.

It seems the IPython console is picking the right Python interpreter, since it throws an error about ipykernel and cloudpickle not being installed, which is expected since the Python env is empty.

But, when I'm running the script in a external console, it doesn't use the interpreter I've set in the option, it is using the Python interpreter used to run Spyder (I think).
Is it by design it is done that way? That would be more useful if the script was executed with the Python interpreter I've set in the option instead.

This is the function used to fetch the path to the python executable located in spyder\utils\misc.py :
def get_python_executable():
    """Return path to Python executable"""
    executable = sys.executable.replace("pythonw.exe", "python.exe")
    if executable.endswith("spyder.exe"):
        # py2exe distribution
        executable = "python.exe"
return executable

So I guess it indeed return the path to the Python executable in which Spyder is running?

So I guess it indeed return the path to the Python executable in which Spyder is running?

Yes. sys.executable returns the interpreter on which Spyder is running.

Yes. sys.executable returns the interpreter on which Spyder is running.

But why not using the Python interpreter that is set in the preferences?

But why not using the Python interpreter that is set in the preferences?

I have no problem with that. I think that's what most people would expect, but no one has complained about it before.

I have no problem with that. I think that's what most people would expect, but no one has complained about it before.

Can I implement this in this PR? If so, should this be done against master?

Can I implement this in this PR?

Yes, please do.

If so, should this be done against master?

3.x is fine. I think this change is no disruptive enough to justify making it against master.

Hello @jnsebgosselin! Thanks for updating the PR.

In the file spyder/app/mainwindow.py, following are the PEP8 issues :

Line 160:1: E402 module level import not at top of file
Line 160:80: E501 line too long (80 > 79 characters)

@jnsebgosselin, adding a test for this is not easy, so I think this is ready.

The failure in CircleCI is unrelated to this.

Thanks a lot @ccordoba12 for reviewing and rounding up this PR!

No problem :+1:


ci(release): add osx x64 arch

Fixes #506
Safe to merge PR:
Adding build support for osx x64 arch (see related issue).

@microsoft-github-policy-service agree


Create Syntax Guide

This PR contains:

Describe the problem you have without this PR

This is just copy pasted stuff.


Tests are not sorted in a Cluster scan report

On master-head - commit id: 0ccce4

Deploy CIS v2 app in Dashboard
Navigate to CIS benchmarks on the top left menu.
Run scan. Wait for the scan to finish.
Click on the scan (which might show Pass/fail)
Scan Report is seen.
The tests are not sorted.

They are sorted, but in the alphabetical sense where .12 comes before .2

...which is sorted wrong.  This isn't the end of the world but it's lack of attention to detail in plain sight. The rows just need an alternate version of the number that sorts properly on them (e.g. zero-pad each number to several digits wide), and then the table definition to be told to use it.

Verified on 2.5-head - commit id: 9d3882175

Deploy CIS v2 app in Dashboard
Navigate to CIS benchmarks on the top left menu.
Run scan. Wait for the scan to finish.
Click on the scan (which might show Pass/fail)
Tests are sorted.


fix(cssom): add missing webkitTransition property

I have noticed that TypeScript uses the following property that is missing here:
webkitTransition: string | null;

Down to merge this, I'll just need it rebased since it's over a few months old. Dw about the appveyor or re-recording the tests 👍


Implement target power control in DAP_Connect/DAP_Disconnect handlers

V1.1 hardware has T_VCC_EN signal that controls 3.3V target power (and should be handled carefully), V1.2 hardware also has T_ENABLE signal to control 5V line.

How would you map DAP_Connect onto T_VCC_EN etc? Turning them on when we connect, or only when we connect and no target vcc is discovered, sounds liable to cause unexpected and bad surprises if the user didn't want 3v3 to suddenly appear on the target. Last time I looked I didn't really find anything in CMSIS-DAP that's suitable for controlling probe-supplied-power; maybe it needs to be a vendor command.

AFAIK, target power is usually handled in DAP_Connect, but I agree that controlling 3V3 line can be dangerous. We can control 5V line, though, this should be safe. This line is "reserved" in stlink docs, but controlled by stlink.

I'd rather make this a persistent setting with a vendor specific command :) Because I want it to always supply power :)

Persistent as in "as long as the probe remains powered", so you turn it on/off separately from a debug session?
Would we extend probe-rs to add hs-probe's vendor specific command for controlling power? Not sure if you'd then have to expose that through to the cargo flash/embed etc tools or make a new binary that just lets you set power on/off...

3V3 power can be provided via pin2, just like on stlinkv3 (though it doesn't provide enough power on this line).

Ah, only on the STDC14 connector though, not on the standard Cortex Debug connector (the inner 10 pins)?

@adamgreig yes, 5V and 3V3 are present only on STDC14.

At least on the 1.2 schematic, aren't STDC pins 2 and 3 both connected together, so the cortex debug connector pin 1 (stdc14 pin 3) is also toggleable 3v3?

Yes, they are connected on V1.2 schematic and it's probably something we should reconsider :)

I've lost track of what changed in 1.1 too, but previously didn't we have 5v and 3v3 both hardwired on STDC14 1 and 2, and then the selectable 3v3 on STDC14 pin 3? I'd still really want to be able to toggle 3v3 supply on STDC14 pin 3, so that when using it with a standard debug cable/connector you can still supply target power.

This "power" part was the same in all hs-probe versions so far. Ok, so it's better to leave the schematics as it is, but control 3V3 line only with a special vendor command (or persistent configuration)?

The schematics seem fine, though I don't know if STDC14 users would normally expect pins 1 and 2 to be always on (or at least always on when you try to connect to a target). Certainly we don't want pin 3 to be always on 3v3, but it seems good to be able to turn that on when desired, so probably the current schematic is the best option.
I would have thought the vendor command is what enables power until either the probe is unplugged from USB or another vendor command is used to disable power. I don't know if @Yatekii meant it should persist it to non-volatile memory so it applies power again when you next plug the probe in, though that seems like it might also be quite surprising or cause accidents. I don't know what software we'd provide to let the user run those vendor commands, though.

Persistent as in "as long as the probe remains powered", so you turn it on/off separately from a debug session?
Would we extend probe-rs to add hs-probe's vendor specific command for controlling power? Not sure if you'd then have to expose that through to the cargo flash/embed etc tools or make a new binary that just lets you set power on/off...

Persistent as in "stored in eeprom" :)
Idk what the best way to control this is :)

I'd not have it persistent as in "stored in eeprom" as this might have strange effect when going between different boards.
However to keep it during one "plug in" is fine IMO.

Well, then you cannot use that feature independently of a driver :) Works for me, but idk for others :)

And now with the v1.3 there is one more place 5V can come that needs to be handled (KEY pin). :)

Well, then you cannot use that feature independently of a driver :) Works for me, but idk for others :)

We could control this via cargo feature in the firmware, and then you simply flash the "5V default on" firmware variant?

As a quick-and-dirty workaround to enable the 5V and 5V_KEY output pins, this should do, right?
diff --git a/firmware/src/main.rs b/firmware/src/main.rs
index 8c3c8d1..822a9b9 100644
--- a/firmware/src/main.rs
+++ b/firmware/src/main.rs
@@ -70,6 +70,7 @@ fn main() -> ! {
         led_green: gpiob.pin(8),
         led_blue: gpioe.pin(0),
         t5v_en: gpiob.pin(1),
+        t5v_key_en: gpiod.pin(7),
         tvcc_en: gpioe.pin(2),
         reset: gpiog.pin(13),
         gnd_detect: gpiog.pin(14),
diff --git a/hs-probe-bsp/src/gpio.rs b/hs-probe-bsp/src/gpio.rs
index 924e349..ea0ecb3 100644
--- a/hs-probe-bsp/src/gpio.rs
+++ b/hs-probe-bsp/src/gpio.rs
@@ -368,6 +368,7 @@ pub struct Pins<'a> {
     pub led_blue: Pin<'a>,

     pub t5v_en: Pin<'a>,
+    pub t5v_key_en: Pin<'a>,
     pub tvcc_en: Pin<'a>,
     pub reset: Pin<'a>,
     pub gnd_detect: Pin<'a>,
@@ -419,6 +420,13 @@ impl<'a> Pins<'a> {

         // Push-pull output drives target 5V supply enable.
         self.t5v_en
+            .set_high()
+            .set_otype_pushpull()
+            .set_ospeed_low()
+            .set_mode_output();
+
+        // Push-pull output drives 5V key supply enable (low = active).
+        self.t5v_key_en
             .set_low()
             .set_otype_pushpull()
             .set_ospeed_low()

At least it does seem to work 🙂
(Careful, the 5V_KEY pin needs a hardware fix, since it's on the wrong pin of the connector.)

A feature-gate would also help to contain the magic smoke inside other probes :)


Add error handling coming from contract

Related Issue(s): #Add link to issues
Closes Issue(s): #Add link to issues this PR closes
Nearcore Branch Info: #Example: commit df431768f95bc4117dc7c4d954e38f1b96fd3b9f (HEAD -> stable, tag: stable-2020-07-13, origin/stable)
Unit tests completed?: #Y/N
Relevant README/Documentation Updated?: #Y/N

Future directions: https://github.com/near/nearcore/pull/3204#issuecomment-768339895


Update flags docs

Description
I noticed that the flags docs were not updated for the 3.7.0 release
Checklist

[ ] Read the contributing guidelines
[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added new entries to the RELEASE.md file
[ ] Added tests to cover my changes

Legal notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

The failing tests appear to be unrelated Python e2e issues, so I'm going to go ahead and merge


Support access control

Expected behavior
I expected to apply mask for case class with access control.
Steps to reproduce the behavior
@customize
private[config] Password(@mask value: String)

[error] /path/to/project/config/Password.scala: Unsupported case class type. Cannot rewrite toString().
[error] @customize
[error]  ^

Workaround
Without access control.
@customize
Password(@mask value: String)

Thanks a lot for reporting, @kenchan0130! Version 1.3.0 with access control support is now on its way to Maven Central.

@kciesielski
Thank you your support!
I am very happy!
By the way, do not you have to worry about protected?
I have no immediate problems. Because I became anxious, I did a comment.

@kenchan0130 you mean protected[pkg] case class? It's quite uncommon, because it means effectively the same, so no worries for now.

Yes.
I knew it.