Update Android EN Framework to 1.7.2

Summary | Résumé
This updates the Android Nearby Services (and EN Framework) to 1.7.2. According to the release notes from Google, this should be backward compatible.
Although not mentioned in the release notes from Google, this updated aar file also required an update to the com.google.android.gms:play-services-base dependency.
Test instructions | Instructions pour tester la modification
When building this app, because it is an updated aar file, please be sure to Invalidate Caches / Restart in Android Studio (from the File menu). Also, Clean Project and do a rebuild.
Do a normal end-to-end test to test the functionality.
Unresolved questions / Out of scope | Questions non résolues ou hors sujet
How does updating the googlePlayServicesBaseVersion impact installs on older Android phones, or phones with an outdated Play Services app installed?
Reviewer checklist | Liste de vérification du réviseur
This is a suggested checklist of questions reviewers might ask during their review | Voici une suggestion de liste de vérification comprenant des questions que les réviseurs pourraient poser pendant leur examen :

[x] Have you tested it? | L’avez-vous testé?
[ ] Are there automated tests? | Y a-t-il des tests automatisés?
[ ] Does this break existing functionality? | Est-ce que ça brise une fonctionnalité existante?
[ ] Should any documentation be updated as a result of this? (i.e. README setup, etc.) | Faudra-t-il mettre à jour la documentation à la suite de ce changement (fichier README, etc.)?

 Update Android Framework to 1.7.2


Missing dependencies for branch fast_text_prompting

Pillow / PIL is not in dependency list along with diffusers, accelerate, and omegaconf
will add at a later date, just making note of it here for now

fixed in https://github.com/opentensor/bittensor/pull/1431


update contributing and readme - fix typo, ToC

Description of the change:
Reason for the change:
Link to original source:
Checklist
Make sure all of these items are complete, or else the PR will be ineligible for a code review.

[ ] Code passes all existing tests
[ ] Any new functionality added includes new unit tests in tests/test.py
[ ] Create or update example code to show the new functionality in action.
[ ] All code, branch, and git naming and style conventions are followed (see CONTRIBUTING.md)
[ ] Feature branch has been rebased off of the latest master branch. ( see CONTRIBUTING.md ).

If you have questions, please send an email Sendgrid, or file a Github Issue in this repository.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @pushkyn,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Start making WRY more DRY

If you are looking to get your hands dirty, this is a great issue to get started working with Rust and WRY.
In this PR, https://github.com/tauri-apps/wry/pull/82 there is some code repetition, and if you look closely in the codebase, there are some other cases of it. With regard to mime types (aka media types), there may be situations where we need to add others as time goes on, so having the list in one place makes it easier to update and know that we have feature parity.
Feel free to ask questions here in the issue, or on our discord server.

I'd like to take this up.
For starters, I think I'll add a mimetypes.rs file that declares an enum that looks like
enum MimeTypes {
 CSS,
 CSV,
 JSON,
 JSONLD,
 // . . .
}

and then implement the Display trait for the enum, so that MimeType::JSON.to_string() returns "application/json".
I'm also thinking to add a parse function which basically takes in a URI and gets the last suffix, to transform that into a MimeType.

That sounds great!

Awesome. The secret sauce here though, is in the header bytes - and these extra mime types are for those situations where INFER cannot guess what exactly is going on. Good luck!!!

@nothingismagick yup, that makes sense. Essentially when you cannot get the mimetype from the content, try to get the file extension from the uri and set a mimetype instead.

However, I do have a specific question about when an application/octet-stream would occur. If we take a look at the snippet used to split the url by .:
        let suffix = uri.split(".").last();
        match suffix {
         // . . . all other valid extensions
         None => "application/octet-stream"
        }

I'm just trying to come up with a URI to simulate the None arm here. Any clue?

I think None would never reach since the split iterator always has at least one item.

So in the case a file path doesn't have an extension, the match would be Some("").

Right, yeah that's what I was confused about too. None is never reachable, and we always assume text/html anyways.


Add AWS Kinesis Stream Scaler e2e test

Signed-off-by: Jorge Turrado<EMAIL_ADDRESS>Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Tests have been added
[x] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[x] A PR is opened to update the documentation on (repo) (if applicable)
[x] Changelog has been updated and is aligned with our changelog requirements

Relates to https://github.com/kedacore/keda/issues/1526

/run-e2e kinesis

/run-e2e kinesis

/run-e2e kinesis

/run-e2e kinesis

/run-e2e kinesis

seems like there is some problem in the scaler itself:
https://github.com/kedacore/keda/runs/5712186540?check_suite_focus=true

I'd say that yesterday we reached the API rate limit:
LimitExceededException: Rate exceeded for stream keda-steam under account 58976***922677.

Maybe we should keep the stream created all the time, but tbh, I prefer to don't keep infra created if it's not needed.
Mybe we could check how it works during the next days and if it's a flaky test in due to that, I'll update it for not destroying the infra. (ofc, now the test has to pass in order to do this)
WDYT?

/run-e2e kinesis

I'd say that yesterday we reached the API rate limit:
LimitExceededException: Rate exceeded for stream keda-steam under account 58976***922677.

Maybe we should keep the stream created all the time, but tbh, I prefer to don't keep infra created if it's not needed. Mybe we could check how it works during the next days and if it's a flaky test in due to that, I'll update it for not destroying the infra. (ofc, now the test has to pass in order to do this) WDYT?
+1

Though we should properly handle that part in the scaler as well -> don't cause panic, but return error instead.

 I didn't see the panic error in the metrics server logs

Do you think that I should fix it in the context of this PR or maybe another issue and PR split?

I'd create a separate one.

I'd create a separate one.

Sure!
https://github.com/kedacore/keda/issues/2833

/run-e2e kinesis

/run-e2e kinesis

I got the problem... Reusing the same name for all the streams, the API limit is 10 request every 24 to update the shards. I have updated the PR to generate a new stream on every PR (and delete at the end)

/run-e2e kinesis

/run-e2e kinesis

/run-e2e kinesis

/run-e2e kinesis

/run-e2e aws-kinesis-stream*

/run-e2e aws-kinesis-stream*

/run-e2e aws-kinesis-stream*

/run-e2e aws-kinesis-stream*


make image.json contain an outer object rather than array

when doing dataset generation, the images.json should be an object which has a field containing the array of image urls rather than just an array without the outer object. With the outer object we can easily add other fields later. With the array version (current version) we cannot


Philippines route shields

Added route shields for the Philippines.
Tacloban
Route relation tagging in Metro Manila is inconsistent. National routes are a mix of the oversimplified network=nhn (based on recreational route tagging), network=PH:nhn, and the network=PH:N:* found elsewhere in the country. National expressways all tagged the same way as national routes despite distinct signage. Radial and circumferential route relations lack a network tag. I’ve omitted network=nhn because it would make little sense to show these shields in Europe, where this value is endemic. I included both the other styles because it’s unclear which the community stands behind more; PH:nhn is far more common, but PH:N/E is better distributed throughout the country.
Metro Manila
The Philippines handles concurrencies between national routes/expressways and Asian Highways (#122) by combining them onto a special sign. But at the size that we show route shields, it would be better to separate them into two independent shields displayed in series. Unfortunately, these concurrencies are currently tagged like ref=E2;AH26, which we can’t do anything reasonable with.

I'm concerned about:

National expressways all tagged the same way as national routes despite distinct signage.

and:

I included both the other styles because it’s unclear which the community stands behind more

It sounds like the tagging of highway routes in the Philippines is not mature and/or lacks consensus.  In #180 we removed rendering support for Swiss highway route relations for this reason.  Perhaps we might consider reaching out to the Filipino mapping community to see whether there might be support for standardizing on one of the variants and also separating out relation network=* for the cases of distinct signage?

It sounds like the tagging of highway routes in the Philippines is not mature and/or lacks consensus.

To be clear, I was describing the state of affairs in Metro Manila specifically. The rest of the country seems to be more consistent, and I only included network values that are qualified by PH:, ignoring the problematic nhn value. That said, outreach to the Philippines mapping community is a good idea.

@1ec5 Hi there! From Philippines. but currently in Canada, I'll share what seems to be the current situation with Philippine expressway/numbered route relations.
In its current state, tagging of Philippine expressways is kind of a mess. It was in 2015 when those yellow or white shields began springing up (and have seen one since then), and one user has just began adding relations for those  numbered routes, but it kind of follows an idiosyncratic scheme of network=ph:nhn and nhn:class=expressway/primary/secondary. I have been bringing the network tagging into accordance with the wider network tagging scheme of [country code]:[road type] but there's hundred of these across the thousands of the Philippines' islands, let alone Metro Manila.

@1ec5 Well, relations that use PH:N:primary and PH:N:secondary should be easily migrated into the simpler PH:N, which us justifiable as there aren't much difference between the shields used for a national primary (1-2 digits) and a national secondary (3 digits).

I don’t have a strong opinion on whether to include the primary/secondary/tertiary classification in the network value. It’s easy enough to give them all the same shield. However, if the number already reliably indicates the classification and you don’t don’t think it’ll be needed for, say, a Philippines renderer that colors each classification differently, then the plain PH:N would be simpler. As I understand it, designation is already widely used for the more granular classifications.

@1ec5 Agreed. Just added various route relations last week and retagged those still using the old scheme. ph: suffix is plain wrong (that would be an ISO language code). Also removed AH26 from the main reference where tagged (those can already be covered by int_ref).
FYI, Philippines uses a road classification scheme based on function and importance, not one based on the number (as with most of Southeast Asia). Expressways, yes, will generally be motorway, but below that, it's much like with the US; 1- to 2-digit routes may not have the importance of a trunk, some 3-digit ones form the "best" routes between major cities, tertiary is at best an administrative classification and roads classified that best tagged by their importance, and there's a lot of bypass construction that would justify moving large classifications away from built-up areas.

By the way, I didn’t find an existing tagging scheme for route relations for Metro Manila’s circumferential and radial roads, but those should be easy to implement once they’re tagged.

@1ec5 I wouldn't think circumferential/radial road numbers should be rendered at all. Well, the circumferential road numbers are in common use save C-1, but the only radial road number commonly used is R-10 (more commonly said of as Road 10). After all, those numbers are mostly for planning purposes, and there isn't a standard shield for them. I'll be in favor of rendering only AH26, national road numbers and expressway numbers; Circumferential/radial road numbers should be migrated to unsigned_ref in the route relations.


use SIGWINCH to gracefully shut down on stop

Currently, stopping the containers causes docker to send the default TERM signal to apache, which immediately kills all child processes and exits.
Sending the WINCH signal instead tells apache to gracefully shut down instead (stop accepting new requests, wait for existing requests in progress to finish, then exit)
https://httpd.apache.org/docs/current/stopping.html#gracefulstop
STOPSIGNAL WINCH

Closing as duplicate of https://github.com/docker-library/php/issues/877

This one isn't completely a dupe of that one (different builds of httpd); implemented in https://github.com/docker-library/httpd/commit/3ebff8dadf1e38dbe694ea0b8f379f6b8bcd993e, thanks! :+1:


Error: Invalid int: "1476261..."

It does not accept any value as minDate for Android. I tried new Date().valueOf(). Please explain?

I had to pass it like this: (parseInt(new Date().valueOf()/1e5)). It's nowhere mentioned in the readme. I had to literally check the max digits for int datatype in Java! Also, the last 5 zeroes were not accounted, so divided by 1e5.


S3 support for image saving

Is it possible to enable s3 uploading of images at least of failed tests.

Sorry, not within the scope of this library.


[Color Picker] Editor window: Selection not visible in dark mode

Microsoft PowerToys version
0.79.0
Installation method
GitHub, PowerToys auto-update
Running as admin
No
Area(s) with issue?
ColorPicker
Steps to reproduce
Selecting a dark color in editor window that is in dark mode.
(I don't know it. But I think it is the same in light mode with light colors.)
✔ Expected Behavior
Can see the circle around the color.
❌ Actual Behavior
Can't see the circle around the color,

Other Software
No response

cc: @stefansjfw , @jaimecbernardo
Can you fix this as part of the accessibility improvements you are working on.

I'll check. The problem there is that selection takes the color of the item, so dark ones (black, dark grey, etc.) are not visible in dark mode. So we either make the selection a single color, or somehow detect specific colors and act on that

I'll check. The problem there is that selection takes the color of the item, so dark ones (black, dark grey, etc.) are not visible in dark mode. So we either make the selection a single color, or somehow detect specific colors and act on that

I prefer single color. How was it solved in the old ux because there we had no problems.

https://github.com/microsoft/PowerToys/blob/main/src/modules/colorPicker/ColorPickerUI/Views/ColorEditorView.xaml#L102
Should be a simple change here. @niels9001 any suggestion which system color to use?


老铁没毛病 no trouble, old iron

hi,laotie

six six six

how are you?

I don't know

When do you go home?

alrealy at home, preparing something important this afternoon

I think you know what I'm talking ablout

w .... w.... w.... what？

look at the chat record of qq, I said something gonna happen in this monday

interesting

嗨，laotie


cht.sh gives 500 server error for rust/fn

Not sure if this is an issue with the server proper or with the formatting of the question but here is an example of a query that results in an internal server error:
http://cheat.sh/rust/fn
Additionally, from the command line curl gives the same error as does cht.sh's bash script.

@sullivant That is a very strange bug, I will take a look at it if it will persist in the new version, that is about to be deployed these days.

The new version is deployed. The bug can't be reproduced
@sullivant Thank you very much for reporting it. If you meet any bugs again, please report them immediately


Do not expose native plugin services in Gradle core APIs

The TargetMachine concept shouldn't be visible from a project that doesn't have one of the native plugins applied.
Instead these types should and factories should be made visible in the usual way that a plugin would add things to the project. Project.getMachines() should be replaced by a project extension that is added by the native plugins. The related types should live in platform-native project rather than core-api:

MachineArchitecture
OperatingSystemFamily
TargetMachine
TargetMachineFactory

Also dependencyManagement project should not declare any dependency on platformNative.

PR available here: https://github.com/gradle/gradle/pull/7778


Fix crash when entering Mods menu with no mods

With this pull request, entering the mods screen with no mods will print "No HAT Mods Installed". This was arbitrarily decided by me, so there could maybe be better designs ("Mods" button on main menu is grayed out?)

Seems okay.


PID Tuning not working on actual flight

Hi everyone ,
@AndreasAntener I am new to programming. I have managed to tune my bespoke quad on JmavSim using a step input . all works fine on the simulation. when I transferred PID parameters into the Pixhawk. the quad started behaving weirdly and didnt even managed to takeoff . any help would be appreciated
video link: https://www.dropbox.com/s/chxxrwyg2n9kuug/video-1487278360.mp4?dl=0

Did you calibrate your ESCs?
Also filing an issue is not an appropriate way to request support. You should post newbie questions on one of the support forums.


Updates from PR feedback

Description
Updates from PR feedback - gets the upstream PR unblocked.

Well after merging from main this is much harder to inspect :/ Actual interesting commits:
https://github.com/gregschohn/opensearch-migrations/pull/6/commits/a15266657fab54ee708d0d90700043ab7925c944
https://github.com/gregschohn/opensearch-migrations/pull/6/commits/2a26039213fac5297ab369127c4dc1d9e4529cbe
https://github.com/gregschohn/opensearch-migrations/pull/6/commits/2159a2ab71e18b9ae39b13ff352af512a299cc3e

@gregschohn Thanks for making these changes manually - nothing was needed from this PR.


[enhancement]: Allow options to choose from in a prompt

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
It would be both beneficial and interesting imo to add options to choose from in a prompt. This would save time since you wouldn't have to run all versions of a certain setting, you could just add them in the prompt and have the AI select any of the options ("at whim") and generate a result. There is no guarantee all versions of the prompt would run, but is more likely the higher the image count. This new feature would be called something like "an option block".
The options block in a prompt starts with, for example, a {, followed by each option inside separated by | and ends with a }.
Like so: {blue|red|green}. However, whatever token sequence is fine, it's just a suggestion.
Here are some examples:
A {beautiful|cyberpunk|serene} landscape
Prompts this would generate (for the AI to choose from):

A beautiful landscape
A cyberpunk landscape
A serene landscape

For this example, there would in total be 3 ways this prompt may turn out.
Of course, one could add these anywhere in the prompt. Here's a more advanced example:
A {warrior|mage|bard} scouting from atop a tower at {sunset|dawn|dusk}
Prompts this would generate (for the AI to choose from):

A warrior scouting from atop a tower at sunset
A warrior scouting from atop a tower at dawn
A warrior scouting from atop a tower at dusk
A mage scouting from atop a tower at sunset
.... and so on

For this example, there would in total be 9 ways this prompt may turn out.
Please note
It's important to underline that not all permutations of all options will run. The AI would pick a random item from each option block and continue to the next to create a complete prompt. The results would also be limited by the number of images the user wants to create, not "all permutations of all options set in the prompt".
So, taken the example above ☝  with an image limit of 3, you may get results created from these prompts:

A warrior scouting from atop a tower at sunset
A warrior scouting from atop a tower at sunset
A mage scouting from atop a tower at sunset

If you run the generation again, different items from each option block may be selected, resulting in 3 new prompts and hence 3 new images, it's "random".
Example prompt in UI

Why is this useful?
Consider wanting to create, say, a large collection of various adventure settings with different elements like "a landscape with a castle and adventurers crossing a river" and "a landscape with majestic mountains and dragons in the sky". Currently, you would need to run these two prompts independently. This grows exponentially difficult with more elements in the sentence. With the prompt options ability, you'd input 1 prompt with the parts that can change and let the AI choose one for each generation. It's adds some additional "magic" to what's already pretty incredible.

Further thoughts: Option probability
Note: These are suggestions only
One can further expand on the options with weights on how probable it'll be that the AI chooses that item from the options block.
Options are followed by :<Probability>. Like so:
A {large:0.5|small:0.3|huge:0.2} sword
The prompt above has a higher probability to be "A large sword" (50%) than "A huge sword" (20%). In cases of erronous calculations (where the options do not accumulate up to a 100%), each option falls back to a probability of 1/number of options.
Alternatives
No response
Aditional Content
No response

also to consider, from jonathon pollock on Discord: being able to import words from a word list eg portrait of a {adj.txt} man, would generate one image for each line of adj.txt

syntax would probably be more like .oneOf("red", "yellow", "blue") or .oneOf(file="/path/to/file.txt").

I see we have two related syntax modifiers - .oneOf and .allOf - and both should both take strings or a file. The syntax also feels a bit off here as other modifiers are after strings.

Remember that there's a difference between "All of the options" and "Have options to choose from". This feature would be the latter and limited by the number images set in the UI.
So "A wizard with a {green|red|blue} robe" and 3 images as output would not guarantee three different images, it's just options that can be chosen from. You may still end up with three images with a wizard in blue robes.

open to suggestions about how the syntax should be done. i'm not a fan of making {} meaningful in the way OP suggests - really want to find an imperative command-like way of activating this. does ("red", "yellow", "blue").oneOf() make sense? and how would this look for file input?
not quite sure what .allOf() is for though..?

.allOf() would do one execution per term. So a (red, yellow, "dark blue").allOf() chair would iterate through the list and generate a total of three images.

ah got it. thanks for the clarification @Coreusa

The suggestion has been updated, should be clearer now.

For something like this, it's probably best to prototype using a standalone script that takes in the templated prompt and puts out a file containing the expanded prompts. Then this expanded prompt list could be passed to the CLI using the --from_file argument. Once the syntax is firmed up, the new feature could be added to the built-in prompting syntax.

This is now integrated into the app


[BUG] Too much space between the headings and bullet lists

Screenshots

Desktop (please complete the following information):

OS: macos 11.4
Obsidian Version: 0.12.5

In both Spectrum and the default theme, they have a margin of about 14-15 pixel on headings and on lists.
I can provide you with a custom snippet, just tell me where you want to have the margin be lowered. Heading? Then everything will be closer to heading. List? Then everything will be closer to lists.
@WilliamDev588

Due to a lack of response, I will be closing the issue for now.


MAINT, DOC: bump jupyterlite-sphinx lower bound

* Two versions of jupyterlite-sphinx were released in the last 5 hours, and neither one works with our doc build per gh-21212, so just pin for now. (I did confirm locally)
Update: just bump the lower bound for jupyterlite-sphinx now that there's an upstream fix.
[skip actions] [skip cirrus]

Looks like this did the trick, thanks @tylerjereddy !

(Github is having an incident and the artifacts are not available so I'll approve and come back)

conda-forge release of 0.16.2 is on hold due to azure outage holding up CI https://github.com/conda-forge/jupyterlite-sphinx-feedstock/pull/30#pullrequestreview-2187078933

conda-forge release of 0.16.2 is on hold due to azure outage holding up CI conda-forge/jupyterlite-sphinx-feedstock#30 (review)

Outage is over and conda-forge release is done https://github.com/conda-forge/jupyterlite-sphinx-feedstock/pull/30#event-13566271590

All looks good, thanks folks!


[INTERNAL] Use Object.create(null) for dynamic maps

Coverage remained the same at 94.717% when pulling 9d559591f0f6cd93ea2c1e997d275215cf971aa3 on use-object-create-null into 7a4c242226d3e89b9b603d3904d0348bc765452a on main.

For further information about Object.create(null) vs {} https://davidwalsh.name/object-create-null might be worth to read.


The Absence of Additive Operations in detr_layers.py

When reading the code, I noticed that in the detr_layer.py file, the attn and ffn layers do not perform the addition operation（line 226-236）. I see that the original code and the original paper both include this operation. Why is this the case?

hey, check the implementation of the layers and ffn. They do perform the skip connection addition.


Add <label> in Let It Snow demo

Fix MicrosoftEdge/Demos#239

@dstorey What does WFM stand for? hehehe

@sarvaje works for me

hahaha Thanks!!!
Merging!


[infra-proxy-service] reset node client key, create client & delete client API

:nut_and_bolt: Description: What code changed, and why?

Added changes to cover create client https://docs.chef.io/server/api_chef_server/#post-5
Added changes to cover delete client https://docs.chef.io/server/api_chef_server/#delete-4
In order to reset the key first delete the key using https://docs.chef.io/server/api_chef_server/#delete-5 then added the key using https://docs.chef.io/server/api_chef_server/#post-6

:chains: Related Resources

Fixes: #4534

:+1: Definition of Done

Infra proxy service is now able to respond create client, delete client and reset client chef server APIs.

:athletic_shoe: How to Build and Test the Change

rebuild components/infra-proxy-service
rebuild components/automate-gateway

Steps to test:

To add data using 3rd internal steps https://github.com/chef/automate/blob/master/dev-docs/adding-data/adding_test_data.md#adding-data-to-infra-views

Client detail API with appended default key data:
curl -sSkH "api-token: $(get_admin_token)" https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/clients/rhsm-rhel8?pretty
{
  "name": "rhsm-rhel8",
  "client_name": "rhsm-rhel8",
  "org_name": "4thcoffee",
  "validator": false,
  "json_class": "Chef::ApiClient",
  "chef_type": "client",
  "client_key": {
    "name": "default",
    "public_key": "-----BEGIN PUBLIC KEY-----...-----END PUBLIC KEY-----\n",
    "expiration_date": "infinity"
  }
}

Create Client API
curl -sSkH "api-token: $(get_admin_token)" -X POST https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/clients?pretty -d '{"name": "abctes6t", "create_key": true}'
{
  "name": "abctes6t",
  "client_key": {
    "name": "default",
    "public_key": "-----BEGIN PUBLIC KEY-----...-----END PUBLIC KEY-----\n\n",
    "expiration_date": "infinity",
    "private_key": "-----BEGIN RSA PRIVATE KEY-----...-----END RSA PRIVATE KEY-----"
  }
}

Delete Client API
curl -sSkH "api-token: $(get_admin_token)" -X DELETE https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/clients/abctes6t?pretty
{
  "name": "abctes6t",
  "client_name": "",
  "org_name": "",
  "validator": false,
  "json_class": "",
  "chef_type": ""
}

Reset Client Key API
curl -sSkH "api-token: $(get_admin_token)" -X PUT https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/clients/node2/reset?pretty
{
  "name": "default",
  "public_key": "",
  "expiration_date": "",
  "private_key": "-----BEGIN RSA PRIVATE KEY-----...-----END RSA PRIVATE KEY-----"

:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable
Signed-off-by: Vivek Singh<EMAIL_ADDRESS>

Facing some trouble in Create Client API
{
“error”: “no server found with ID \“chef-server-dev-test\“”,
“code”: 5,
“message”: “no server found with ID \“chef-server-dev-test\“”,
“details”: [
]
}

Facing some trouble in Create Client API
{
“error”: “no server found with ID \“chef-server-dev-test\“”,
“code”: 5,
“message”: “no server found with ID \“chef-server-dev-test\“”,
“details”: [
]
}

@shaik80 hope you have added the chef-server entry provided in the "Steps to test".
Could you please verify with providing the output of:
curl -sSkH "api-token: $(get_admin_token)" https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test?pretty

@shaik80 hope you have added the chef-server entry provided in the "Steps to test".
Could you please verify with providing the output of:
curl -sSkH "api-token: $(get_admin_token)" https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test?pretty

Updated the client detail API containing public key data:
curl -sSkH "api-token: $(get_admin_token)" https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/clients/rhsm-rhel8?pretty
{
  "name": "rhsm-rhel8",
  "client_name": "rhsm-rhel8",
  "org_name": "4thcoffee",
  "validator": false,
  "json_class": "Chef::ApiClient",
  "chef_type": "client",
  "client_key": {
    "name": "default",
    "public_key": "-----BEGIN PUBLIC KEY-----...-----END PUBLIC KEY-----\n",
    "expiration_date": "infinity"
  }
}

Updated the client detail API containing public key data:
curl -sSkH "api-token: $(get_admin_token)" https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/clients/rhsm-rhel8?pretty
{
  "name": "rhsm-rhel8",
  "client_name": "rhsm-rhel8",
  "org_name": "4thcoffee",
  "validator": false,
  "json_class": "Chef::ApiClient",
  "chef_type": "client",
  "client_key": {
    "name": "default",
    "public_key": "-----BEGIN PUBLIC KEY-----...-----END PUBLIC KEY-----\n",
    "expiration_date": "infinity"
  }
}

@msorens have made the tabs to spaces changes it due to vscode issue https://github.com/microsoft/vscode-go/issues/2871 good to review it again.


Fixing issue with Safe name special characters

What does this PR do?

The use of ConvertTo-URL for safe names was used in many places, but not in every needed place
It was missing when creating an account and when adding an Owner to a newly created safe based on a template safe
The change was to move the ConvertTo-URL from each method to the Account object creation and to the specific calls where we need to handle safe name

What ticket does this PR close?
Resolves #180
Documentation

[X] This PR does not require updating any documentation

Resolves #179


Add a sample using robolectric native graphics

Now possible with https://github.com/robolectric/robolectric/releases/tag/robolectric-4.10-alpha-1

Robolectric 4.10 adds support for native Android graphics. It is currently disabled by default and can be enabled using @GraphicsMode(NATIVE). When native graphics is enabled, interactions with Android graphics classes use real native Android graphics code and are much higher fidelity.

@yschimke
Sure! It’s in my TODO list once back from holidays

Roborazzi Tests already merged :)


Use the entire file URI, rather than just the path when reading files from the filesystem

Drive letters on Windows are part of the hostname in an URI, so the entire URI must be used. This closes issue #209

@zhlicen I don't have access to a windows machine at the moment, so I had to do some tricks when testing this on my end. Could you double check for me that this solves your problem from #209?

hi @johandorland ,
I did a test on my windows PC, and yes, this commit solved the problem from #209
Test Code
func TestWindowsPath(t *testing.T) {
	schemaFile := "file://d:/schema/schema.json"
	document := `
	{
		"name"        : "test",
		"description" : "test desc"
	}
	`
	schemaLoader := NewReferenceLoader(schemaFile)
	documentLoader := NewStringLoader(document)

	result, err := Validate(schemaLoader, documentLoader)
	if err != nil {
		panic(err.Error())
	}

	if result.Valid() {
		fmt.Println("The document is valid")
	} else {
		fmt.Println("The document is invalid")
		for _, desc := range result.Errors() {
			fmt.Println("-", desc)
		}
	}
}

Result on xeipuuv:master
Running tool: C:\Go\bin\go.exe test -v -timeout 30s github.com\xeipuuv\gojsonschema -run ^TestWindowsPath$

panic: open schema\schema.json: The system cannot find the path specified. [recovered]
	panic: open schema\schema.json: The system cannot find the path specified.

goroutine 19 [running]:
testing.tRunner.func1(0xc042042c30)
	C:/Go/src/testing/testing.go:622 +0x2a4
panic(0x7beb00, 0xc0420ff3e0)
	C:/Go/src/runtime/panic.go:489 +0x2dd
github.com/xeipuuv/gojsonschema.TestWindowsPath(0xc042042c30)
	D:/samzho/code/go/src/github.com/xeipuuv/gojsonschema/schema_test.go:346 +0x3d6
testing.tRunner(0xc042042c30, 0x8648c8)
	C:/Go/src/testing/testing.go:657 +0x9d
created by testing.(*T).Run
	C:/Go/src/testing/testing.go:697 +0x2d1
=== RUN   TestWindowsPath
--- FAIL: TestWindowsPath (0.00s)
exit status 2
FAIL	github.com/xeipuuv/gojsonschema	0.585s
Error: Tests failed.

Result on johandorland:windows-filepaths
Running tool: C:\Go\bin\go.exe test -v -timeout 30s github.com\xeipuuv\gojsonschema -run ^TestWindowsPath$

=== RUN   TestWindowsPath
The document is valid
--- PASS: TestWindowsPath (0.01s)
PASS
ok  	github.com/xeipuuv/gojsonschema	0.508s
Success: Tests passed.


App shows that time entry has tag checked while it actually isn't

It might be issue with loading the edit view. Maybe previous time entry had tag checked.
case: 254214

Cannot reproduce.


Inefficient serialization functions: too many copies

It's not the case, serialization functions are as efficient as it should be

We could use memcpy for serialization, but it's messing up our interface and make our code less readable


Possible integration of cartographer 3D (online) mapping and OctoMap (offline)

Is your feature request related to a problem? Please describe.
Cartographer is a  system that provides real-time simultaneous localization and mapping (SLAM) in 2D and 3D.
https://github.com/cartographer-project/cartographer
https://google-cartographer-ros.readthedocs.io/en/latest/
OctoMap is a offline 3D representation for 3D environment
https://github.com/OctoMap/octomap
http://wiki.ros.org/octomap
Integration of Cartographer and OctoMap can help us to reuse the historical information of the environment and speed up the SLAM process
Describe the solution you'd like
Save the historical (offline) map in the OctoMap_server hosted in the Cloud
Integrating the 3D map generated online by cartographer with the pre-existing offline map
Plan based on both online and offline map
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Use online map from cartographer only
Additional context
Add any other context or screenshots about the feature request here.
https://www.youtube.com/watch?v=7iM2ynZEuf0
https://www.youtube.com/watch?v=34n1tF5OtQU

[ ]  New personal to work in this task (BEDS)


supress "You've set InstallProvider#stateVerification to false"

Description
I want to stop seeing this console warning every time I run tests / start the app
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[x] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Reproducible in:
package version: 3.9.0
node version: 16.x
OS version(s): any
Steps to reproduce:

set state verificaction to false
start the bolt app

Expected result:
I expect to pass supressStateVerificationWarning: true and not see this message
Actual result:
I see this message every time I start the app
Attachments:

Hi @goldylucks, thanks for writing in!
We intentionally have the warning logs and are not planning to change the behavior at least in the short term. For testing, we suggest passing your own logger for testing like this or changing the log level to ERROR.
I hope this helps.

Thanks for the prompt response @seratch ❤
The thing is, I do want to see warnings in my tests, just not that specific one.
I ended up doing this:
const express = require("express")
const { ExpressReceiver } = require("@slack/bolt")
const installationStore = require("./installation-store")

const receiver = new ExpressReceiver(getConfig())

receiver.router.use(express.json())

module.exports = receiver

/*
 * Utils
 */

function getConfig() {
  const config = {
    signatureVerification: process.env.NODE_ENV !== "test",
    signingSecret: process.env.SLACK_SIGNING_SECRET,
    clientId: process.env.SLACK_CLIENT_ID,
    clientSecret: process.env.SLACK_CLIENT_SECRET,
    scopes: process.env.SLACK_BOT_SCOPES,
    installerOptions: {
      stateVerification: false,
    },
    installationStore,
  }

  if (process.env.NODE_ENV === "test") {
    config.logger = getSlackLogger()
  }

  return config
}

/* eslint-disable no-console */
function getSlackLogger() {
  return {
    debug(...msgs) {
      if (msgs[0].match(/The logLevel given to OAuth/i)) return
      console.debug("[slack logger] DEBUG", msgs)
    },
    info(...msgs) {
      console.info("[slack logger] INFO", msgs)
    },
    warn(...msgs) {
      if (msgs[0].match(/set InstallProvider#stateVerification to false/i))
        return
      console.warn("[slack logger] WARN", msgs)
    },
    error(...msgs) {
      console.error("[slack logger] ERROR", msgs)
    },
    setLevel() {},
    getLevel() {},
    setName() {},
  }
}
/* eslint-enable no-console */


Add support to auto-activate virtualenv found in projetile-project-root

Now it is possible to automatically activate a virtualenv located in the
root of a projectile project (projectile-project-root) however this
isn't done magical, the user has to call (venv-projectile-auto-workon)
in some point after entering the project, i.e. via projectile-hooks,
python-mode hooks or the action projectile-switch-project-action which
is the recommended way and thus documented in the README.md.
By default it will detect only virtualenvs whose name is ".venv" but
the user can expand the options by settings all the desired names in
the venv-dirlookup-names list, this is all documented in the README.
Fixes #24.

I don't know what is this error on the build, in fact I didn't add tests, I'll try to add tests if you wish however I have never done it (at least not in elisp) so be patient 😄

bluh, that test failure is weird. i'll look into it. i would like to add tests for this, but maybe hold off until i can figure out what's going on with the existing tests

OK, dug into this a bit—confirmed that the changes in this PR somehow prevent the virtualenvwrapper.el from loading. You can see this by doing (load-file "virtualenvwrapper.el") and seeing the same error message from above (Lisp error: (wrong-number-of-arguments (1 . 1) 3)). Going to look into it more to figure out what the actual problem is.

@porterjamesj Thanks, you're right I've now learned how to use defcustom correctly hehe, sorry for that.

Hi, reporting back, I came up with this passing test, however I don't know if it's the right thing to do (because of the fake projectile function), what do you think? I basically reused the venv-workon-works test. Or does projectile needs to be a dependency for tests? I don't think so right?
(defun projectile-project-root ()
  "Stub for testing projectile integration."
  temporary-file-directory)

(ert-deftest venv-projectile-auto-workon-works ()
  (with-temp-env
   venv-tmp-env
   (setq venv-dirlookup-names (list venv-tmp-env))
   (venv-deactivate)
   (venv-projectile-auto-workon)
   ;; M-x pdb should ask to run "python -m pdb"
   (should (equal gud-pdb-command-name "python -m pdb"))
   ;; we store the name correctly
   (should (equal venv-current-name venv-tmp-env))
   ;; we change the path for python mode
   (should (s-contains? venv-tmp-env python-shell-virtualenv-path))
   ;; we set PATH for shell and subprocesses
   (should (s-contains? venv-tmp-env (getenv "PATH")))
   ;; we set VIRTUAL_ENV for jedi and whoever else needs it
   (should (s-contains? venv-tmp-env (getenv "VIRTUAL_ENV")))
   ;; we add our dir to exec-path
   (should (s-contains? venv-tmp-env (car exec-path)))))

Cool! That seems like more or less what we want. I agree we should not pull in projectile just to test this. A couple thoughts:

it would be nice to define projectile-project-root using a let inside the test rather than globally.
We should probably extract that list of assertions into a function.

Ok, done, what do you think? I had to use cl to use flet, using only let couldn't see how to call the function :confused:.

Ok, done, I think this resolves #24, what do you think? I had to use cl to use flet, using only let couldn't see how to call the function :confused:.

@ZzAntares Sorry for the long reply! I checked this out to make sure it worked for me and realized that this requires more of a rethinking of how this code works that I had anticipated, and ended up going down a bit of a rabbit hole. Anyway, I wrote some more stuff on top of what you have and now we have a branch that seems to work for me: https://github.com/porterjamesj/virtualenvwrapper.el/tree/projectile. Can you check out that branch and confirm that it works for you as well and then I'll merge it?

Hi, seems that I never replied, even though I remember doing it! O_o.
Well it works fine for me, I don't know what else is missing, I think that's it.

Can your projectile branch be merged to master so I get the update through  melpa?

Shouldn't this PR be closed in favor of #37? I think they add the same functionality.

yep! sorry this is finally all merged, should be melpa installable once melpa builds again


Waybar freezing and high CPU load when there's lots of window events

Hi,
I just had a QEMU + gdbserver session running with a conditional breakpoint, leading to LOTS of window update events (QEMU always updates the window title QEMU ... QEMU [Paused] once per breakpoint, and with a conditional breakpoint somewhere in malloc ... that are quite some updates to be processed^^')
After ending the debugging session, I noticed my PC is still loud (so high CPU load) and waybar is not responding to me scrolling on an empty area (to change workspaces). I forgot to check if the CPU load is really from waybar, but since everything else behaved normally (especially sway), this seems logical to me. I can test this if needed.
I assume waybar was stuck processing window events and I'm not sure, if there is a lot it can do about it .. but in any case, reporting this to explain the behavior to someone else might already be worth it - or you have any ideas how to handle this more graceful :)
I'm using sway as my compositor and have modules sway/workspaces, sway/mode, sway/scratchpad and sway/window enabled in my config.
If you need more info, feel free to ask :)

It does sound plausible. Workspaces, scratchpad and window subscribe to window events.
Can you confirm please, though? ;) And, while this will depend on the machine, I'm curious what ballbark of events per time we're talking about.
The config for these modules might play a role as well, I'm thinking rewrite rules or app icon display, so if you could share the config for these modules, it might help.
At first glance, I share your sentiment of "not sure if there is a lot it can do about it". The modules kinda have to process the events in order to stay consistent after initialisation. On the other hand, if it's specific operations that are very expensive, perhaps there's a way to rate limit. Don't want to promise anything, but let's see where this leads.
Does waybar recover eventually after you stop debugging?

I've tried to reproduce this.
My first attempt was an iced-rs GUI that changes its title once per tick, but that didn't go anywhere. I don't know a lot about iced-rs, but I saw different rates on internal and external screen and I think it was just vsynced. That's not a lot of updates, a wayland client might actually be the wrong choice for this.
My second attempt was looping swaymsg focus commands via swayipc. This achieves roughly 1000 window events per second, after a while I'm seeing this sway error:
[ERROR] [sway/ipc-server.c:945] Client write buffer too big (4194304), disconnecting client
and sway/window doesn't update, and sway/workspaces doesn't switch workspaces. I think this might explain the behaviour.

Honestly, I have no idea how to fix this. With a bit of speculation, the reason for the disconnection seems to be that the modules are not processing the events from the window subscription fast enough, but I don't see how that can be sped up.
N.B. It might be clever to wait with the next get_tree until the last one has been processed, in order to not aggravate the situation, the get_tree responses are much bigger after all, but that is a different fd and limiting this does not prevent the disconnection.
The CPU load seems to be caused by rapid event polling after the socket has been disconnected. This can be addressed by adding a longer sleep in the worker catch branch (e.g. sway/window L37), but that might be bad if it's not this specific disconnection scenario.
Even then the modules remain borked and waybar needs reloading.

I don't have any logs sadly and I didn't look at the waybar codebase yet and am only on my phone rn
But how is the reading from the sway IPC socket implemented? Read something, process, read next? If so, maybe reading everything in a ln extra thread and queue up operations would fix that - have the buffer grow in waybar instead of sway and not get disconnected.
This could then also extended to remove older unprocessed events when you read a new event that overrides them? Like you queue a window title change event, you read another one and the first isn't processed - you never gonna have to process that first one anyway, so just remove it
Does that make any sense? Or should I look at the code before I have "good ideas"?^^`

But how is the reading from the sway IPC socket implemented? Read something, process, read next? If so, maybe reading everything in a ln extra thread and queue up operations would fix that - have the buffer grow in waybar instead of sway and not get disconnected.

Well, I've not written that IPC code, but I'd say, yes, pretty much. There is a worker thread receiving the subscription data which fires a signal containing the response.
A queue could work, I suppose. The modules using the IPC code only ever use the signal to do a GET_TREE. So that could also be limited considerably. But I think I need to spend a lot more time to understand this better.

Hi @LittleFox94 , can you try to reproduce the case, but please don't use your own style.css and use waybar config by default


AKS - VM size list is not up to date

Rancher versions:
2.0.7
Steps to Reproduce:
In Rancher 2, create a new AKS cluster and display the VM size list.
Check in the Azure Portal the VM size avalaible in the AKS creation UI
Results:
The VM list displayed in Rancher UI doesn't match the list displayed in Azure Portal, for exemple B2s
Feature request
It will be great if Rancher UI could display the actual VM Size list corresponding to the location via an Azure API call.

I second this... especially since changing the VM size after provisioning is not supported.

This should be fixed in v2.1: https://github.com/rancher/rancher/issues/15412


Padding at bottom of the card

I love how this card visualizes the comfort level and want to make it part of my dashboard!
Did notice that the padding on the bottom is a little off. Can the padding be fixed so it's consistent with the top/sides?

Hi @masminl unfortunately I can't reproduce the issue, but I've tried some small adjustments
Could you try the pre release 1.5.6-rc0 that I've just released and let me know if it fixes the glitch?

@argaar thanks for looking into this, unfortunately the issue persists. I tried using a different theme on both IOS app and Chrome all the same result. Is there anything I can do to help you reproduce?

@masminl which theme are you using? I can try install it and see if it's bugged on my side

Hi Davide,
I’m using this theme
https://github.com/basnijholt/lovelace-ios-themes
Greetings,
Samuel
Op wo 24 jan 2024 om 12:23 schreef Davide Foschi @.***>

@masminl https://github.com/masminl which theme are you using? I can
try install it and see if it's bugged on my side
—
Reply to this email directly, view it on GitHub
https://github.com/argaar/comfortable-environment-card/issues/19#issuecomment-1907934546,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG4CJ2KSE3AMPVGWVGR3JBTYQDVLVAVCNFSM6AAAAABCDAKNTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBXHEZTINJUGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@masminl Just published 1.5.6-rc1 that should fix the issue, I've installed the theme and tested on my own environment and it seems to be ok.
Very nice theme btw

Indeed the theme is a great one!
I just installed rc1 and the issue is fixed.
Thanks so much for looking into this and fixing so quickly. That’s what
makes Home Assistant the best platform.
Op wo 24 jan 2024 om 14:44 schreef Davide Foschi @.***>

@masminl https://github.com/masminl Just published 1.5.6-rc1 that
should fix the issue, I've installed the theme and tested on my own
environment and it seems to be ok.
Very nice theme btw
—
Reply to this email directly, view it on GitHub
https://github.com/argaar/comfortable-environment-card/issues/19#issuecomment-1908152104,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG4CJ2KLWBFVZ356CATURILYQEF4XAVCNFSM6AAAAABCDAKNTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGE2TEMJQGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Problem with simple arithmetic.

I use https://www.fstar-lang.org/tutorial/
The next code works fine.
module M

type t = d: int {exists (w:int).(w + 1 = d )}

val f : t -> Tot t
let f x = x

val g: (int) -> Tot t
let g x = f 4

But if I replace '+' with '-' in type refinement, then I get an error.
module M

type t = d: int {exists (w:int).(w - 1 = d )}

val f : t -> Tot t
let f x = x

val g: (int) -> Tot t
let g x = f 4

Error:
M(9,12-9,13): Subtyping check failed; expected type t; got type int
Error: 1 errors were reported (see above)

Such behavior is a bit strange for me.

The issue is related to the way the proposition under the quantifier is instantiated: the solver needs a trigger to instantiate it.
Here, because no trigger has been provided in the code, the behavior is a bit unpredictable. In practice it seems that the trigger is something like w-1:
module M

type t = d: int {exists (w:int). (w - 1 = d )}

val f : t -> Tot t
let f x = x

val g: int -> Tot t
let g x =
    assert((4+1)-1 = 4);
    f 4

works. Now in your specific example it is not obvious what the appropriate trigger should be.
It could be inserted in the type definition like type t = d: int {exists (w:int). {:pattern (trigger(w))} (w - 1 = d )}. Hope this helps.

Thanks.


collections code cleanup

Follow up to #1347  and #1400

Hi @liboz, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@forki @eiriktsarpalis I seem to have triggered the Async.Choice bug again. Seems like #1379 might not have fixed it.

Looks okay to me.


Latent system lockup on bionic-minimal-rock64-0.6.31-209-arm64 with mainline kernel

Hello,
I have had 2 lockups within 3 days with the latest build and its corresponding mainline kernel, 4.16.0-rockchip-ayufan-209-g027e722bb. The lockup appears to happen randomly after the machine is on for ~24hrs, after which it is unreachable via the serial console. Please let me know which logs I can provide to help diagnose the issue.

I started having lockups too when moved from a mini sd card to an eMMC module.
Linux rock64 4.4.120-rockchip-ayufan-209 #1 SMP Mon Apr 2 16:05:07 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

I think I can reproduce it quite regularly, so if there are any logs I can post here or some diagnose tasks simple to follow that I can contribute with please let me know.


ODPR-1170: Fix address formatting

Please address warnings in the app. Some are not related to your changes, but were introduced since I fix those last week.

Please bring libraries up to date.

There are still two warnings you can fix in the ViewUtils


Test OED code on CUDA

As suggested by @eb8680, we ought to verify that contrib.oed and contrib.glmm examples and tests work correctly on GPU

i am shocked by @ae-foster's impudence but i guess i can do it....

Just a heads up that the following tests are failing already with PyTorch master with/without CUDA (it seems like there is a difference of 1 between the actual and expected values, so it's worth looking into this in case there is some bug upstream in PyTorch that we can fix before release):

test_eig_lm[model10-design10-y-w1-donsker_varadhan_eig-args10-True-0.3]
test_eig_lm[model5-design5-y-w-donsker_varadhan_eig-args5-True-0.3]

Tests in oed and glmm have been resolved in #1617. So I change the title of this to reflect a better situation. We still need to implement a CUDA version for oed example.


(PUP-7073) Normalize selinux category names

SELinux category names have two forms: an internal 'numeric' form, and
a human-readable name. Several SELinux commands rely on a service
called mcstransd to convert between them. When that service is not
functioning correctly, things will break.
Instead of using mcstransd, Puppet now queries the list of
translations itself and uses them to normalize all internal operations
on the numeric form.

CLA signed by all contributors.

Just to confirm - for example, given a system with a MCS numeric = label mapping such as s0=SystemLow, the point here is that if an is value or should value starts as SystemLow, it will be set to s0 ?

@MosesMendoza That's the deal. It also passes through unrecognized values unchanged, so if the user puts in s0 it'll "just work", and if they put in potato it'll end up out of sync and then fail to make the change, since that's an invalid category.

@branan sounds good. Given the esoteric nature of the functionality we're working with here, any chance we could come up with a more intuitive name for the normalize_selinux_category method? I was scratching my head trying to figure out what was going on.. I wonder if something like category_label_to_value(category) might be more expressive. Thoughts?

@MosesMendoza I came up with selinux_category_to_label, which is the best I've got from reading the docs on what these various words are supposed to mean ¯\_(ツ)_/¯. I'm not sure that's really entirely correct, but everything is terrible.

@MosesMendoza This is updated with slightly nicer error handling if the setrans.conf file is missing.
I suspect I should rebase atop latest master and add gettext markers as needed around my new strings?

This was originally targeted at stable, are we switching to master?
And yes please on the string marking!

@Magisus Yeah, this is being re-targeted at master. The ticket was updated but the PR target apparently wasn't. I'll get it cleaned up.

@Magisus Rebased and added translation. Can you make sure I did that right?


Remove Collaborator Network

Steps
Go to Explore->Collaborator Network
Expected
A cool visualization of the current state of the OSF
Actual
Currently, the Collaborator Network is out of date and problematic.
Proposed solution
I recommend removing it for the moment until we can get something to replace it. There's some discussion in #98 that might also be relevant to a replacement Collaborator Network. If we are super-clever, we can leverage Elastic Search to make a live replacement.

Harsh critics.


Cannot be whitelisted

Hi I managed to make it to the whitelisting of your one's own address to try the minting process (48:08 mn of the video) and the contract gets updated without a problem.
Now when I go back to my Netlify site to refresh the page I still dont get whitelisted.  My account number is correctly between quotes so I really dont know what is up.
When I do this I am on the rinkeby part of y wallet, if I change that to ethereum main the waiting gif keeps turning without ever landing me anywhere...could that be the issue?

You need to be patient when the whitelist addresses are updated. can take a while on Rinkby (happened with me)

It could take some time to update, but you can also check to be sure the whitelisted addresses were saved properly here: https://docs.nftport.xyz/docs/nftport/b3A6NDE1MTQ2MzI-list-all-your-deployed-collection-contracts

actually the problem was that I was trying to mint ahead of my presale date so it would not work (dah)...changed the date and it worked.   Newbie mistake..Thanks for answering anyhow.
Erick
On Friday, April 15, 2022, 07:05:00 AM GMT-5, shusmush @.***> wrote:
You need to be patient when the whitelist addresses are updated. can take a while on Rinkby (happened with me)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Swagger spec for the APIs

What does this PR do?
Fixes #63
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

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

You can

Add the swagger.json file to https://editor.swagger.io/
Postman supports both YAML and JSON formats.
We can additional use Redocly to generate API spec doc (I don't think we need this)


Syntax for feature engineering

I stumbled upon https://github.com/matthieugomez/PairsMacros.jl today and it seems to be close to what we discussed with @vollmersj with respect to defining new columns with a formula-like syntax.
@matthieugomez sorry to ping you here but would you be interested in something like PairsMacros for general-purpose feature engineering to work with MLJ?

There's also this: https://github.com/joshday/Telperion.jl

Continuing the discussion started by @indymnv at https://github.com/alan-turing-institute/MLJ.jl/issues/970:
Existing MLJ transformers are documented here with the exception of InteractionTransformer, which was recently added to MLJModels, but is not documented or re-exported yet by MLJ.jl. Here's the list:
julia> using MLJModels

julia> models() do m
       m.package_name == "MLJModels" &&
       !m.is_supervised
       end
11-element Vector{NamedTuple{(:name, :package_name, :is_supervised, :abstract_type, :deep_properties, :docstring, :fit_data_scitype, :human_name, :hyperparameter_ranges, :hyperparameter_types, :hyperparameters, :implemented_methods, :inverse_transform_scitype, :is_pure_julia, :is_wrapper, :iteration_parameter, :load_path, :package_license, :package_url, :package_uuid, :predict_scitype, :prediction_type, :reporting_operations, :reports_feature_importances, :supports_class_weights, :supports_online, :supports_training_losses, :supports_weights, :transform_scitype, :input_scitype, :target_scitype, :output_scitype)}}:
 (name = ContinuousEncoder, package_name = MLJModels, ... )
 (name = FeatureSelector, package_name = MLJModels, ... )
 (name = FillImputer, package_name = MLJModels, ... )
 (name = InteractionTransformer, package_name = MLJModels, ... )
 (name = OneHotEncoder, package_name = MLJModels, ... )
 (name = Standardizer, package_name = MLJModels, ... )
 (name = UnivariateBoxCoxTransformer, package_name = MLJModels, ... )
 (name = UnivariateDiscretizer, package_name = MLJModels, ... )
 (name = UnivariateFillImputer, package_name = MLJModels, ... )
 (name = UnivariateStandardizer, package_name = MLJModels, ... )
 (name = UnivariateTimeTypeToContinuous, package_name = MLJModels, ... )

A "fancier" version of InteractionTransformer, based on R type "formulas", has been planned, but no-one has really found the time to work on it.
There is a project in progress to roll out a feature_importance method for models that support that, with the idea of adding feature selection tools, such as recursive feature elimination.
TableTransforms.jl referenced by @juliohm above is very active but not yet integrated with MLJ, although we are working towards doing so in the future (at least several months off). I think that is good place to contribute generic table transformers, such as encoders. Some feature engineering tools, such as RFE, will probably not make sense there, as they require supervised learners, for example.
@indymnv It would be helpful if you can identify specific encoders or other tools you use frequently that are missing from MLJ (or TableTransforms.jl)  so they  can be prioritised.

@ablaom Thanks for all the information, in general in my work with ML I use the following encoders a lot.

For categorical variables

Ordinal Encoding: replaces categories by numbers arbitrarily or ordered by target
Frequency Encoder: replaces categories by the observation count or percentage
One-Hote Encoder: done.
grouped tail encoder: groups infrequent categories

For dates and other cyclic variables:

Cyclical encoder: creates variables using sine and cosine

For some numerical variables:

Equal Frequency Discretiser: sorts variables into equal frequency intervals
Equal Width Discretiser: sorts variables into equal-width intervals.

Transformations:

Logarithm
Box-Cox
Yeo-Johnson

Feature Selection:

I use the feature selection, built-in ml models from scikit-learn, or Boruta.

For now, in Julia I have only used One-Hot-encoder, I have not checked the transformations.

Thanks @indymnv . That's most helpful. PR's for missing items welcome 😉


Spawned Arrival not Activated

Hey all,
Playing EDDH and an arriving flight on the RIBSO arrival, call sign GWI9WY never got activated in my airspace.   Went all the way through the arrival route and along the runway heading to its final fix, then headed north because of the other bug.
Another one coming in on the BOGMU (?) arrival almost did the same thing, but became active just as it was lining up with the runway heading.  I forget which call sign it had.
Scott

It's happening again with SXD6677 and EWG6760 on the RARUP arrival, and almost happened to EWG3713 on the RIBSO arrival too, but it came into control at the TOPRA fix.  Weird behaviors.

I'm having trouble reproducing this. Just sped through about 100 arrivals, and all of them appeared active on the scope at the appropriate time. There must be something I'm missing here. :confused:

I've seen this happen in other airports as well, though very rarely. It might be a bug in the code instead of the airport file, or maybe both? You can see an example of this happening in KATL (only available on my fork atm) in this video with AAL509 inbound from the Southwest. I checked the console after I finished recording and there were no errors. I don't think this helps in any way, but I wanted to let you know that it doesn't just happen at EDDH.

Hi,
Could it be browser related?  I'm running on Chrome currently.  I haven't
tried on others.
Scott
On Sun, Jan 1, 2017 at 8:40 PM, Erik Quinn<EMAIL_ADDRESS>wrote:

I'm having trouble reproducing this. Just sped through about 100 arrivals,
and all of them appeared active on the scope at the appropriate time. There
must be something I'm missing here. 😕
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zlsa/atc/issues/773#issuecomment-269928798, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVXawJWeiqCGcr1JAWJtx9DzarXJ1PLHks5rOFWqgaJpZM4LX1Bk
.

Thanks @fechulo, that is helpful to know it's not necessarily airport specific. If anybody is able to reproduce it again, and you are able to pause and leave the tab open, please do so and reach out here. There are a couple of things I'd like to check in the game via the console to see where it went wrong. And I'll continue trying to break it myself as well :)

@erikquinn I have an open tab with the error right now 😆 what do you need?

@Fechulo scroll to the top of the error list and take a screenshot of the first few errors.  Then, with the first error, open it up and take a screenshot of the entire stack trace (if possible).
Was there anything specific you did to get this to happen?  Or was it just through the course of running a simulation?

@n8rzz @erikquinn The only errors in the console don't have anything to do with any aircraft, they're just warnings regarding the SID's:

All I did was open up the game and use timewarp to wait until the bug occurred, no commands were issued to any aircraft.

@Fechulo And, yeah, those errors are a result of airport.json formatting and have nothing to do with the present simulation.  I only have a few minutes, but I'm going to reach out on slack right now and try to walk you through a thing quick.

@n8rzz upon further investigation, we have discovered that the altitude of the offending aircraft is exactly 10000.00011920929ft which is about 36 microns higher than FL100 (the airspace ceiling at EDDH), so the airplane is technically above the airspace. We now know why these aircraft couldn't be controlled and to fix this issue we need to see how the game is calculating the altitude of the aircraft and why it stopped its descent just before reaching 10,000ft.

@Fechulo That's actually all I was planning to look at, good work. :wink:
I can create a new issue now for the actual problem, and link back here to the symptom. Thanks for the assistance. :+1:

Moved to new issue following discovery of the core problem. Closing.

@erikquinn It was actually @n8rzz who told me what to look for, I just followed his instructions :smile:

@Fechulo Good advice for all of us... he's a smart dude. :wink:

@Fechulo And if able, check slack pm's. I had a follow up question.


Confusing about the inputs.

Hello, thanks for your excellent work. I am new in this area and working on applying gcn in the destination of shared bicycles prediction to manage them better. My approach is to see every recorded place  a node, then we have an adjacency matrix. The question is I don't figure out which is the input(I mean X) of this code, I believe it is neither features nor train_mask.

X denote the node features.
On Mon, Apr 1, 2019 at 1:05 PM Junlei Yang<EMAIL_ADDRESS>wrote:

Hello, thanks for your excellent work. I am new in this area and working
on applying gcn in the destination of shared bicycles prediction to manage
them better. My approach is to see every recorded place a node, then we
have an adjacency matrix. The question is I don't figure out which is the
input(I mean X) of this code, I believe it is neither features nor
train_mask.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tkipf/gcn/issues/97, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHAcYKuHgXn0v0kuNWJce6uq-3xeU_1fks5vcfX3gaJpZM4cVi8a
.


Delete of Model triggers ContentObserver event with wrong sql condition

The offending line at
https://github.com/Raizlabs/DBFlow/blob/develop/dbflow/src/main/java/com/raizlabs/android/dbflow/sql/SqlUtils.java#L386
reset the primary ID of the model to 0, and then dispatches a content observer change event with the wrong (reset) primary ID
Switching those two lines should fix the problem

fixed in develop.


TIFF metadata sometimes too large for HDF5 attribute

In the case of a very large number of TIFFs, the number of entries stored relating to the TIFF metadata becomes too large. To resolve this, we can't use the attributes to store all this information. Instead datasets should be created for the metadata in HDF5. If possible, a link to the datasets storing this data can be added to the HDF5 attribute. This means that registration may need to handle this case. Alternatively, the metadata could be stored into a separate HDF5 file.

@anotherGithubLearner, thoughts on this? Do you have a preference?


Implementation of bitmap blk allocator

This PR is a part of several stages to make sure BlkAllocation is persisted under single umbrella. In order to ease the review, splitting this into multiple PRs.
BitmapBlkAllocator
At present we have 3 allocators, Fixed, Varsize, Append.
Fixed uses list for in-memory side and bitmap for persistence
Varsize uses bitmap and slab for in-memory side and separate bitmap for persistence
Append uses only a location and does in-memory and persistence within single structure and no bitmap.
This PR provides class hierarchy as base
                                  -> FixedBlkAllocator
                                  |
            -> BitmapBlkAllocator -
            |                     |
            |                     -> VarsizeBlkAllocator
BlkAllocator
            |
            |
            -> AppendBlkAllocator

All on-disk implementations are moved to BitmapBlkAllocator.
Realtime Bitmap
In this full implementation of this requirement, we would have upper layers to just call one of the 3 apis and everything else is handled inside, viz, alloc_blk(), commit_blk(), free_blk(). All other apis such alloc_on_disk, free_on_disk etc are handled internally. That is same with realtime_bitmap. Currently in homestore 3.x we have realtime_bm being driven by caller. We will achieve the same thing to keep track of realtime bitmap slightly differently and internally, which will come in next PR.
Other adjustments

Also renamed auto_recovery flag in blkallocator to is_persistent which is more apt name from blk allocator perspective.
Removed explicit inited() call for each chunk/blkallocator which is unnecessary. We need one global check if homestore initialize is completed or not, when we are checking for asserts.

LGTM

LGTM except two minor comments


[WIP] - fix date widget

Related to #632
The problem was on date format: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-local#Setting_timezones
We receive a date like 2019-04-17T10:00:00+00:00 with also timezone info, but datetime-local html field doesn't like timezone anymore.
I needed to convert UTC datetime into local datetime and pass the value without timezone to the input field.
And on change i re-convert the date into UTC for plone.restapi.
I haven't touched the widget to use something better because i don't know what's your plans about date widgets. There are some nice plugins for React.
One other thing: right now a new event has empty dates. In Plone these dates are set as now.
Is it a good idea provide now as default when invoking this widget for event fields?
Also adding a button that sets the date as now like in Plone.

There are tons of React widget options. We used the AirBnB datepicker in some projects and had good experience with it.
New events should have the date set to now. I guess this is something the Volto frontend could provide.

@pnicolli @cekk This is superseeded, right? Close it at will


Feature/436 usdf hotfix

Description
The 1.5.0 version of provenanced does not correctly support creation of restricted markers via governance proposal. A restricted marker is required for the USDF stable coin. Unfortunately due to scheduling concerns the 1.6.0 release of provenanced that correctly resolves these issues (see #431, #430) can not be used.
Additionally this uses the upgrade handler to update any existing usdf.c to the right marker_type
closes: #436

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

additional testing notes
original state:
provenance on  tags/v1.5.0 [$!] at ☸ gke_figure-development_us-east1-b_tf-test took 5s
➜ provenanced -t query marker get usdf.c
marker:
'@type': /provenance.marker.v1.MarkerAccount
access_control: []
allow_governance_control: true
base_account:
account_number: "11"
address: tp1c9pv3n0pmjezg0wkgwqze00957ve39hwsjy84h
pub_key: null
sequence: "0"
denom: usdf.c
manager: tp125rltkc8kmkm4hcdnl7uda9deau9aldryh089c
marker_type: MARKER_TYPE_COIN
status: MARKER_STATUS_PROPOSED
supply: "0"
supply_fixed: false
after "usdf.c-hotfix"
➜ provenanced -t query marker get usdf.c
marker:
'@type': /provenance.marker.v1.MarkerAccount
access_control: []
allow_governance_control: true
base_account:
account_number: "11"
address: tp1c9pv3n0pmjezg0wkgwqze00957ve39hwsjy84h
pub_key: null
sequence: "0"
denom: usdf.c
manager: tp125rltkc8kmkm4hcdnl7uda9deau9aldryh089c
marker_type: MARKER_TYPE_RESTRICTED
status: MARKER_STATUS_PROPOSED
supply: "0"
supply_fixed: false
@iramiller we should probably gov propose usdc.fon pio-test so that it runs there before prod


Remove log crate dependency from services

Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
Remove log crate dependency from services
Resolves #1387 by removing the log crate inside the generated code for services.

Great stuff, happy to merge this as-is!


Need to respect timeout option

http://<IP_ADDRESS>:5984/test/_changes?feed=longpoll&timeout=1000
will wait indefinitely, which breaks replication with pouchdb as it expects the server to respond nicely

Still an issue; I can confirm that packages/node_modules/express-pouchdb/lib/routes/changes.js does not check for timeout anywhere.

Marking this as medium; the fix is just to add a setTimeout() to respect the timeout option that is passed in by the user. It's difficult to add a test case for this, but the PouchDB test suite already passes in the timeout option, so if the Travis run is green and the PR looks good, it should be okay.

Forked to band-aid this issue (and with continuous, not just longpoll), and got timeouts respected on my fork... but I'm not submitting a PR because there's bigger issues at play - changes.cancel() never completes until after a change actually happens. So you can respect the timeout and close the http response, but you're still sitting around leaking memory if changes don't happen. It also makes the code more complicated, since it'd be easier (and was my first attempt) to just call cancel() after the timeout and then handle things in the complete handlers. Assuming this is what's being referenced in https://github.com/pouchdb/pouchdb-server/issues/187

Forked to band-aid this issue (and with continuous, not just longpoll), and got timeouts respected on my fork... but I'm not submitting a PR because there's bigger issues at play - changes.cancel() never completes until after a change actually happens. So you can respect the timeout and close the http response, but you're still sitting around leaking memory if changes don't happen. It also makes the code more complicated, since it'd be easier (and was my first attempt) to just call cancel() after the timeout and then handle things in the complete handlers. Assuming this is what's being referenced in https://github.com/pouchdb/pouchdb-server/issues/187


Fix build tasks and packages for publication

Fix build tasks and packages for publication

During last prerelease we ran into some issues with how the files array was defined which conflicted with the needs of the build tasks; this branch updates the build tasks and packages.

Packages point to dist directory location for files and the files array contains only the dist directory
Build tasks use a default set of asset names with an optional hook for assets in the pfelement object inside the package.json

Testing instructions
Be sure to include detailed instructions on how your update can be tested by another developer.

Pull down the latest from the branch and run a build.
Validate that the expected assets for that component to work in production appear in the dist directory.
There should be no errors in the console.

Your repository infrastructure updates should work for at least:

[x] Node v8.x
[x] NPM v7.x

Ready-for-merge Checklist

[x] Expected files: all files in this pull request are related to one feature request or issue (no stragglers)?
[x] Did you update or add any necessary documentation (README.md, WHY.md, etc.)?
[ ] Was this feature demo'd and the design review approved?
[x] Did you update the CHANGELOG.md file with a summary of this update?

Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!

Ohhh, I see! Totally, yes, let's defer.
Michael Clayton
https://clayto.com
On October 29, 2019 12:12:21 PM EDT, "[ Cassondra ]"<EMAIL_ADDRESS>wrote:

castastrophe commented on this pull request.

+1. git status

Check where you are
+2. git checkout master && git fetch origin && git pull origin

Grab master from origin
+3. npm run clean

Wipes node_modules directory and deletes any components not in
master

what this does:

rm -rf node_modules package-lock.json

rm -rf node_modules
+4. git reset --hard && git clean -df

Remove any non-committed files, crufty directories
+5. npm install

Installs all dependencies fresh
+6. git checkout -b temp

Create temp branch

I didn't actually make any changes to this file, just migrated it from
step-4 to step-5.  Do you mind if we defer updates to this until a
later PR?
--
You are receiving this because your review was requested.
Reply to this email directly or view it on GitHub:
https://github.com/patternfly/patternfly-elements/pull/594#discussion_r340177017


Recommend Cython 3 for pure-Python syntax

I know this is officially in the "Cython 3" documentation, but I think most users end up with this documentation. It'd be good to link the annotation typing mainly to Cython 3.

Good idea. Thanks.


Connect to multiple memcache servers

Google_Cache_Memcache seems to only allow for connecting to a single memcache host.  I need the ability to try multiple memcache hosts.

Yes, you're right. We should change this to accept a Memcache class as the first argument, or an array of configuration parameters (host, port, etc).

Closing, as all Cache classes have been removed in favor of PSR-6


Place newly-created custom blocks in the top left of the visible workspace

Resolves
Resolves #1334.
Proposed Changes
Places newly-created custom blocks in the top left of the visible workspace.
AFAIK a good follow-up (which I really wouldn't know where to begin with testing) is to make this go to the top-right corner in RTL mode, if that's something that is wanted.
Reason for Changes
Convenience: without this PR, new custom blocks are placed somewhere else in the workspace, which is both somewhat unpredictable (it's presumably the top left of the "absolute workspace"), and annoying, because you have to scroll all the way there to grab it and pull it where you want it to go.
Test Coverage
Manually tested at several different zoom levels and scroll positions.

@rachel-fenichel Okay, I made the block get placed at the top right in RTL mode. Here are some screenshots of where the block is positioned in LTR and RTL:

There is a bit less of a margin in RTL mode, for some reason. Should the margin there be - 60 instead of - 30, or something similar, to account for that?

Leave it at 30--the margin problem is likely an issue with the measurement of the block itself, not with your math, and it's easeir to undo one bit of wonkiness than two.  Thanks.

@rachel-fenichel Got it.

I tried testing these changes in the custom procedure playground (test/custom_procedure_playground.html) and it doesn't seem to work quite right.
In LTR, the first new block gets placed to the top left of the block that is already at the top left of the current view. When adding more custom procedure blocks, it seems to move the definition block it has already placed on top of the pre-existing ones. See images below:
Workspace when the custom procedure playground is first loaded:

After adding a new block:

After adding a new block a second time "(notice that New block#1 got moved...):

I also tested this in RTL by manually modifiying the workspace options in inject (here) to add rtl: true in the definition workspace and added a custom procedure using the declaration workspace tool.
When RTL is true, the block is definition hat is placed outside of the current view, and every subsequent time I try to add a new custom procedure, the definition hat gets placed further and further away out of view.

@kchadha You're correct that there are issues with blocks being spawned on top of each other, but that is not an issue that is addressed in this PR nor is it one caused by this.
For comparison, here are screenshots of the same actions without my PR..
Workspace when the custom procedure playground is first loaded:

After adding a new block:

After adding a new block a second time:

This third image is the only case where there is any difference under the develop branch (compare with your screenshot in my PR). And.. yeah, the behavior under develop certainly makes more sense than under this PR. It's something to look into.

However, the focus of this PR is the behavior of where blocks are placed after you scroll the workspace. In the following screenshot, which is under the develop branch, I scrolled up and left as far as the workspace would let me, then created a new block (and then took the screenshot):

As can be seen, the new block is positioned immediately adjacent to the existing custom block. That is, it is positioned at the center/origin of the workspace, not the top left of where I had scrolled to.
This PR changes that behavior to create the custom block at the top left of the visible workspace; that is, the top left of where you've scrolled to. Here is a screenshot where I took the same steps under the branch of this PR:

The new custom block is in the top left of the visible workspace.
This is useful for when the user has scrolled significantly far away from the center (or rather, origin) of the workspace. Under develop, if the user creates a custom block, then they won't know where the custom block appeared; they'd see it in the block palette ("my new block") but would have to search the workspace for the "define my new block" hat block. This PR fixes that by predictably creating the new custom block in the top left of the visible workspace, meaning the "define my new block" will always be visible.

It's worth discussing why the behavior of the third screenshots in this post and yours are different, but I don't see why that would block this PR, seeing as A) it doesn't focus on that part of the code in the first place and B) it's a very rare case where the user will create two custom blocks one after the other without scrolling the workspace between. In that case, I think semi-undefined/unpredictable behavior is somewhat acceptable (and of course, it's not like the "define" block isn't created at all; it's just positioned on top of an existing one... which is not altogether surprising since you created two new blocks while scrolled to the same position).
(PS, thanks for mentioning custom_procedure_playground.html to me - while developing, I was rebuilding and testing in scratch-gui each time!)

@towerofnix Thank you for investigating the issue some more. Unfortunately, even though this PR is intended to only fix an issue when the user has scrolled the workspace, the changes here still affect the issue where the user does not scroll because moving the newly placed block actually does scroll the workspace a bit. It looks like the changes in this PR are somehow affecting the logic of block.scheduleSnapAndBump() call, specifically the call to block.bumpNeighbors_().
@rachel-fenichel I'm wondering if you have any idea of what might be going wrong here?

I think the bumping issues already existed.  If I go to the custom procedures playground and create a few blocks (a through d), here's what it looks like:
Create 'a':

Create 'b':

Create 'c':

Create 'd':

Note that starting from the third block created, the blocks overlap--as opposed to in the images above for this branch, when they do it on the second block.
I agree that there's an interaction with bumpNeighbours_, probably just based on the block being placed a few pixels differently in the two versions--the search for neighbours looks for connections within Blockly.SNAP_RADIUS pixels.  The pseudocode for that function looks something like this:
for each connection on this block and all of its descendants
  find all connections of the opposite type nearby
  for each of these connections
    if either connection is disconnected, bump the inferior block

A block that has been bumped does not bump other blocks that it lands near, which is why blocks can end up piled on top of each other at the end of a bump (blockly has this too).
One solution may be to add some randomness into the distance that the block is bumped.  That would mean changing Blockly.RenderedConnection.prototype.bumpAwayFrom_.
My suggestion is to accept this change and treat the bumping problem as a separate one, and try adding some randomness (+/- 5 or 10 pixels in each direction) to see if that makes the problem less bad.  Bumping is trying to fix a perception problem, where a used could think that two blocks are connected even when they aren't, so any fix that tests well with users is probably fine.

@rachel-fenichel, thanks for investigating and writing up the issue more clearly. I think I'll file a separate issue for this and mark it needs-discussion.
@towerofnix, @rachel-fenichel, any idea about why the blocks are getting placed so far off screen and further and further away each time in RTL? If we want to resolve that in a separate issue that's fine with me, but it should either be fixed here or turned into an issue so we can keep track of it.

Issue I just wrote up for it in Blockly: https://github.com/google/blockly/issues/2011
Scratch-blocks should probably have a separate one for this, since you may make different decisions (especially about the custom procedures).
I'm not sure about the RTL problem.

Added an issue for the bump neighbors problem (#1694) and the RTL placement issue (#1695), so I think this PR is good to go!
Thanks @towerofnix!


[BUG] - /Hideout macro hotkey is causing unwanted chat messages

Describe the bug
When you hit the hotkey configured for the /hideout macro during filter writing in a tab you will open the chat and eventually send a whisper to the last person you had whispered.
To Reproduce
Steps to reproduce the behavior:

In your hideout go to a stash tab or any other tab and click on the "type an item filter"
Press your /hideout macro hotkey while typing
Opens chat and display the chat prefix you previously used in open chat
If you press the macro again it will send your message into chat (worst case scenario I had is sending a whisper message to a person without wanting to).

Expected behavior
Should only open the chat, execute /hideout and display an error message if you're already in hideout (covered by the game)
Should close the chat afterwards and not send a message
Screenshots
Before press of the hideout macro

Pressing the hideout macro once

Pressing the hideout macro a second time after typing something

Desktop (please complete the following information):

Version 1.31

Additional context

In my own hideout
Had previously whispered someone
Was writing a filter

I just tested it and it doesn't work like you say. However if you have focus on highlight items (blinking cursor) then your chat will be opened because first enter will unfocus the highlight items, then /hideout will be typed but not in chat since its closed then enter will be pressed and chat window will be open.
Just press hideout macro while not typing anything else. There is no work around that since that macro is typing in chat


Add X-Correlator and other fixes

What type of PR is this?

correction

What this PR does / why we need it:

Add x-correlator to all requests and responses
Added some missing descriptions to silent linting warnings
Remove weird use of allOf for example

Which issue(s) this PR fixes:
Fixes #271
Fixes #282
Changelog input
- Added x-correlator header to requests and responses

Parameter name in the Design Guidelines is X-Correlator. I think the YAML should be consistent with the guidelines.

Yes, situation is that almost all CAMARA APIs are specifying x-correlator in lower case, so we either fix the guidelines or fix all the specs.

We shouldn't wait with the merge of the PR until this is decided in Commonalities, as that will block the work on the planned API split. Therefore my proposal: we go here with lower case x-correlator (it's only "wip") but adding a new issue that we have to observe the outcome of https://github.com/camaraproject/Commonalities/issues/191 and, if the decision there will be for upper case have to adapt.
@eric-murray @RandyLevensalor: if that makes sense for you, please approve the PR.
The second point, about "Missing CLA Authorisation": CAMARA Board has decided to postpone the EasyCLA introduction at least until the next board meeting. Therefore I asked @wrathwolf to deactivate the check also for our repository for the time being.


Feat/user wallet

Allow a user to save a wallet for payouts
Description

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Checklist:

[ ] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Update wallet when rainbowKit is not connected;
Settings page is not protected on the middleware


Validation - Compare - custom id

Attribute 'total_amount' has a custom id 'total_amount'. Client-side validation is not taking this id.
Validation rule
['received_amount', 'compare', 'compareAttribute' => 'total_amount', 'operator' => '<=', 'type' => 'number'],

What steps will reproduce the problem?
$form->field($job_card, "total_amount")->textInput(['class'=>'form-control', 'id' => 'total_amount', 'readOnly'=>'readOnly']) ?>

What is the expected result?
client side JS.
{
    "id": "jobcard-received_amount",
    "name": "received_amount",
    "container": ".field-received_amount",
    "input": "#received_amount",
    "enableAjaxValidation": true,
    "validate": function(attribute, value, messages, deferred, $form) {
        yii.validation.compare(value, messages, {
            "operator": "<=",
            "type": "string",
            "compareAttribute": "**total_amount**",
            "skipOnEmpty": 1,
            "message": "Received Amount must be less than or equal to \"Total Amount\"."
        });
        yii.validation.required(value, messages, {
            "message": "Received Amount cannot be blank."
        });
        yii.validation.number(value, messages, {
            "pattern": /^\s*[-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?\s*$/,
            "message": "Received Amount must be a number.",
            "skipOnEmpty": 1
        });
    }
}

What do you get instead?
{
    "id": "jobcard-received_amount",
    "name": "received_amount",
    "container": ".field-received_amount",
    "input": "#received_amount",
    "enableAjaxValidation": true,
    "validate": function(attribute, value, messages, deferred, $form) {
        yii.validation.compare(value, messages, {
            "operator": "<=",
            "type": "string",
            "compareAttribute": "**jobcard-total_amount**",
            "skipOnEmpty": 1,
            "message": "Received Amount must be less than or equal to \"Total Amount\"."
        });
        yii.validation.required(value, messages, {
            "message": "Received Amount cannot be blank."
        });
        yii.validation.number(value, messages, {
            "pattern": /^\s*[-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?\s*$/,
            "message": "Received Amount must be a number.",
            "skipOnEmpty": 1
        });
    }
}

Additional info

Q
A

Yii version
2.0.12

PHP version
7.0.23

Operating system
Linux d6 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux

Reference to #7627
Yii 2.0.17 - the same problem

We are facing the same issue with Yii 2.0.20.
Can anyone provide an update on this?

This is still happenin in 2.0.38. Has there been a fix?

No. The issue is open.

Currently, this does not disturb the validation process at all (unless there happens to be another html element with same id) right? since the js handles it via attribute-name:
https://github.com/yiisoft/yii2/blob/4ed14bb738a7dde5f80a3cf2cb9987a892c9f7bc/framework/assets/yii.validation.js#L281-L284


Proof of email: Address Not Found error

After I enter my email address I receive the verification code.
I enter the verification code and then I am forwarded to talao.co/sandbox/ebsi..... and get the error "Address Not Found"

@bibash28

No issue on my side:
Added Proof of email from discover..

@jdsika Do you have more info about the context as it is fine from our side ?


Revert "Revert "feat: access points synchronization""

Reverts gravitee-io/gravitee-api-management#7564
Brings back access point syncronizzation to gateway, original PR here - https://github.com/gravitee-io/gravitee-api-management/pull/7380
Reverted because of issues on CI pipeline on merge on e2e tests, I believe have found the issue which was missing spring configuration, gateway is now running ok for me locally

opened new with run-e2e branch name - https://github.com/gravitee-io/gravitee-api-management/pull/7599


Sticky Footer Windows 10 / Chrome 78

Been using Tingle for years... love the plugin.  Using version 15.1.  I noticed a bug on Windows 10 / Chrome 78 only and I was able to fix it with CSS.  Just adding it here in case anyone else has a similar problem.
Notice how the sticky footer (where the arrow is pointed) doesn't stick to the bottom of a scrolling modal.

I fixed it by adding position: sticky to the CSS file

Not sure why.  Adding position: sticky doesn't seem to have any adverse side-effects in other browsers.  Tested in latest versions of IE, Firefox, and Chrome.

Hi @nbcnc,
I'm note sure if it's a Chrome 78 bug or a bad implementation with tingle but I would rather avoid to use position: sticky according to the current support: https://caniuse.com/#feat=css-sticky

After some tests, the bug seems to be related to backdrop-filter property. I can't go deeper right now since I'm on vacation but you can override CSS as a quick fix:
.tingle-modal {
    backdrop-filter: none;
}

Thanks @robinparisi, I'll try that -- but the support for backdrop-filter looks about the same or less than position:sticky according to: https://caniuse.com/#feat=css-backdrop-filter.  CanIUse says IE 11 has no support for position:sticky it but it seemed to work fine for me in Edge.  Hard to tell what to do with this apparent bug but I appreciate the suggestion!

Indeed, but I consider backdrop-filter as an optional enhancement (you can still achieve the same blur effect without it).
Modal position is trickier: I don't know why position: sticky allows to fix the Chrome 78 bug but it doesn't seem logical to me. I will try to understand this behavior and push a fix after my vacations.

After doing some research, it seems that Chrome has the correct implementation for position: fixed (https://developer.mozilla.org/en-US/docs/Web/CSS/position):

The element is removed from the normal document flow, and no space is created for the element in the page layout. It is positioned relative to the initial containing block established by the viewport, except when one of its ancestors has a transform, perspective, or filter property set to something other than none (see the CSS Transforms Spec), in which case that ancestor behaves as the containing block. (Note that there are browser inconsistencies with perspective and filter contributing to containing block formation.) Its final position is determined by the values of top, right, bottom, and left.

It explains why the div with backdrop-filter now act as a containing block.

I just published a patch using a pseudo-element to avoid modifying the parent container.