Automated bot for managing GitHub issue/pull request life-cycle

The process followed for submitting PRs, Reviewing and Merging them are detailed at https://github.com/openebs/openebs/issues/213. The current process involves several manual steps (some examples below), that can be automated using a bot:

Verify that pull requests follows the template - which at the minimum mentions the issue being fixed
Assigning the size label to the submitted PRs depending on the code changes
Assigning the status labels or clearing them when PR is merged

There seems to be a lot of shiny new stuff at GitHub marketplace besides actions. I'll update this post with things I find useful.
Free solutions for GitHub issue management

Issue label bot labels issues as bug or feature. It might be really helpful as it doesn't seem to require a lot of configs. It does support label aliases.
It might not be very helpful because we have separate issue templates for bug & a feature, but they do not label the created issue. This is where I miss the /label bug from k8s
Ref: https://github.com/marketplace/issue-label-bot

This PR labeler picks up things from the branch-name
Ref: https://github.com/marketplace/actions/pr-labeler

This one does things based on the PR title.
https://github.com/marketplace/actions/condition-based-pull-request-labeler

Who needs to approve this PR?
Ref: https://github.com/marketplace/pullapprove

None of these solutions seem to fit our use cases completely, we might want to write our own GitHub actions or use two or three of these tools.


Top level acount list empty

With my imported book,  bf4f7d06b3 on develop branch, the top-level account list shows nothing. The recent account list is correct, and accounts dropbox can be used. Sub-accounts list seem to be OK.

That commit just reverts the file chooser selector to what it has been for many previous releases (application/). I think I changed the mime type some commits ago to (file/) but later I realized that this did not improve the selection of apps to provide files for import, but rather made it worse. So I reverted the change.
I do not quite understand what you mean by the top-level accounts list shows nothing? The type in the referenced commit should only affect which apps are shown as possible sources for your file to import.

Sorry I didn't mean the commit caused the problem, but rather the code after that commit has the problem. I don't exactly know which commit caused this.
Just after merging develop into my branch, I noticed there is nothing shown on the top-level account list, only a "create account" button. I thought it was some incompatibility between our edits, so tried to pinpoint the problem, but failed. Later I checked the development head, which also shows the problem, so I think I should post an issue.

Oh, I see. That is indeed weird, and I cannot replicate it.
I know there has been some issue with the different account list fragments sometimes not refreshing properly. But the top-level always was shown and the others had the problem.
My first instinct would be to say there is something going on with the root account. I'll look into it.
Was your book generated by GnuCash desktop? Did the import succeed?

My book is generated by GnuCash Desktop. It imported successfully, I can correctly see the recent account list. And from the Accounts dropdown list, I can access any account correctly.

I cannot replicate it either now.
This may be caused by the db migration code, as my db is already version8 , and the migration code upgraded it again when merging the new migration code.
I haven't go through the code to pinpoint the real cause, but as this situation would never happen in real use, I think we close this issue now.

My bad. It is still happening, randomly.

Found the reason.
It is because deleteAllRecords is moved out of the transaction. Another call to getOrCreateGnuCahsRootAccount (when trying to show the top level account list) created a ROOT account after deleteAllRecords is called, which is not deleted when all others are added to the DB. This results in double ROOT account in the DB.
When trying to show the top level accounts, the new added ROOT (not he one imported) is selected, which has no child account at all, resulting in the empty view.
As in the develop head now, deleteAllRecords is already moved back, I'll close this.

Good that this is fixed. :+1:
@fefe982 can you please test the db migration in develop? I know you have some large datasets which you could try to migrate to db version 8. ;)
Migration works in my tests, but I would like to know it works somewhere else before I put out a beta release. Thanks.

I'm going on a vacation tomorrow, and may not have time to work on this in about ten days. I can test the migration after that, but you won't get the results sooner.

No problem. It can wait.
Have fun on your vacation :+1:

Would you provide apks for 1.5.5 and the most recent beta?
I was not able to successfully switch between gradle / non-gradle projects. I cannot get the project built at master.
And my internet connection is (very) bad and it is painful for me to switch between gradle / non-gradle builds to get all the dependencies from the internet.

Old releases are available on GitHub: https://github.com/codinguser/gnucash-android/releases
I will send you a build for the most recent beta


fix(link model): lock child points when locking link

when locking a link also lock all points that compose the link
when adding a point to a link set point lock state to be as the link lock state

:tada: This PR is included in version 2.18.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@all-contributors please add @omerheller  for code, ideas, doc

@all-contributors please add @ronnetzer  for code, ideas, doc, research


Using OpenSSL for Non-blocking server socket

Hi, I'm writing a non-blocking/event-driven HTTP server and I wanted to use OpenSSL for TLS support. I have implemented it with epoll() and I'm specifically targeting Linux. My question is, How can I use OpenSSL for TLS support for a non-blocking server written with epoll()? I had successfully implemented TLS support with OpenSSL for a blocking socket in the past, but I cannot find any online docs/code example on using OpenSSL for a epoll() based non-blocking server.
It would be great if someone could help me with this.
Thank you!

The s_server test utility has an option to use non-blocking IO.  It uses select() instead of epoll(), but the principles of operation should be close enough.

From my experiments, ssl_accept does not work well with non-blocking epoll... It will always give me resource temporarily unavailable error. But it works with blocking epoll.


simplify hcpatch conditions

I am not able to replicate the error but may be we can simplify conditions and check the code is settings or not
reference: https://github.com/hCaptcha/react-native-hcaptcha/blob/HEAD/Example.App.js

update hcaptcha in mastr in separte branch


TSO plugin has issue not handling "NA"

self.tso500_data_samples[sample][metric] = float(data[i])                │
│ ValueError: could not convert string to float: 'NA'
project-GKYbqYj0FvQ2GQV2PFbb1Y2B:job-GKZ4gg80FvQ1zYk6FkbqF5b6

This line https://github.com/moka-guys/multiqc_plugins/blob/ba3d2437cdc488c897aa3abfaf162700e6568aad/seglh_plugin/modules/tso500/tso500.py#L280
should be updated like  https://github.com/moka-guys/multiqc_plugins/blob/ba3d2437cdc488c897aa3abfaf162700e6568aad/seglh_plugin/modules/tso500/tso500.py#L269

This was fixed in v1.2.0


Nltk trees manu

All my changes to be merged into your branch

Hi @manulera ! I looked though the code and  I ran the code on nbrp strains and it's not working as expected.
Some examples:

"leu1-32:pnpg1-npg1-gfp-tadh1-ura4+": "(ROOT (ALLELE leu1-32) (- :) (PROMOTER_GENE (other p) (GENE npg1)) (- -) (GENE npg1) (- -) (TAG gfp) (- -) (PROMOTER_GENE (other t) (GENE adh1)) (- -) (ALLELE ura4+))"
"ade6-m210<<ade6+:mfm1-k34stop": "(ROOT (ALLELE ade6-m210) (- <<) (ALLELE_AA_SUBSTITUTION (GENE ade6) (other +)) (- :) (ALLELE_AA_SUBSTITUTION (GENE mfm1) (- -) (other k34s)) (other top))",

The reason why this is happening is because these false patterns do follow the chunker rule so they have label of the chunk rule they match to but the value of other tag doesn't match so they are actually false matches. These trees have to be deleted if the value of the other tag doesn't match.

Hi @anamika-yadav99, I noticed that that pattern fails and picks up wrong things. I thikn it's probably the regex pattern. You can have a look and see if you figure it out. You can debug it more easily here: https://regex101.com/

Regex works fine. It's the wrong tree which should be removed.

hhmm you are right. I wonder why though the tree should only be substituted if changes are made, and regex are matched. One error for sure is line 99:
if updated_tree != allele_tree:
# should be
if updated_tree != output_tree:

You can have a look and see if you can fix it. It may have to do with this way of checking whether a match was found (not sure how ParentedTree equality is tested). However, I don't see why the tree should be updated if the regex are not matched: how do we get to either of the options in line 111 when the regex fails?
# Line 111
if outcome == 'match':
    output_tree = updated_tree
elif outcome == 'split parent':

I can have a look at it myself later, I would suggest to use only the part of that allele that fails and see if you can figure out where it fails.

hhmm you are right. I wonder why though the tree should only be substituted if changes are made, and regex are matched. One error for sure is line 99:
if updated_tree != allele_tree:
# should be
if updated_tree != output_tree:

You can have a look and see if you can fix it. It may have to do with this way of checking whether a match was found (not sure how ParentedTree equality is tested). However, I don't see why the tree should be updated if the regex are not matched: how do we get to either of the options in line 111 when the regex fails?
# Line 111
if outcome == 'match':
    output_tree = updated_tree
elif outcome == 'split parent':

There will be one more condition here if the match is found then sure go ahead and return but if outcome =='no match' then the tree should be deleted and all the leaves will have to be inserted back at the same position.
Line 99 is correct. Updated tree will not be equal to allele tree if parser identifies .

Hi Anamika,
The line 99 is incorrect as is. allele_tree is the original input, and it never gets updated, the one that updates is the output_tree (incorporates new chunks found with the rules).
There is no need to delete trees, as output_tree should only be updated if the conditions are met.


Select2 option leaves thin blue lines when not focused

iOS 14.5 - When a user selects an option from the list of dropdowns, if a user touches outside of this area, thin blue lines appear next to the option element. This can also be reproduced from the doc page.

This sounds like a real issue that shouldn't be closed just because it wasn't attended to quickly (though of course attending to it quickly would be better)


Calculate nursery stats for reports

Add server-calculated mortalityRate and totalPlantsPropagated fields to the
nursery information in reports.

Current dependencies on/for this PR:

main

PR #982

PR #983

PR #985

PR #986

PR #988

PR #989

PR #990

PR #991


"Uncaught ReferenceError: regeneratorRuntime is not defined" in jspsych 7.2.2 with CDN method

Hi jsPsych,
I really appreciate jspsych in helping to code my experiments online. For release 7.2.2, there is a bug with plugins like image-button-response with the CDN method. For instance, the image-button-response demo gives the error in chrome console:
jspsych@7.2.2:1 Uncaught ReferenceError: regeneratorRuntime is not defined
    at r.value (jspsych@7.2.2:1:61308)
    at jspsych-image-button-response-demo1.html:32:15

The error does not appear when I am hosting jspsych 7.2.2 or with 7.2.1. Thank you for your consideration.
Regards,
ZhaoBin

Hi @ZhaoBin-Li,
thanks for reporting this! It's related to the Babel build relying on regeneratorRuntime, which is currently not in any index.brwoser.min.js build artifact. I think the best fix here is to add regeneratorRuntime to the jspsych index.brwoser.min.js build. Looking into this now.

@ZhaoBin-Li We just released<EMAIL_ADDRESS>which fixes this. Thanks again!

Hi all, I know this issue is closed but I'm still getting the regeneratorRuntime error with<EMAIL_ADDRESS>and up when loading via unpkg. Here's how I'm loading scripts:
    <head>
        <title>Experiment</title>
        <!-- More recent versions give me the same error, but 7.2.1 works -->
        <script<EMAIL_ADDRESS>        <script src="https://unpkg.com/<EMAIL_ADDRESS>        <script src="../dist/index.browser.js"></script>
        <link rel="stylesheet"<EMAIL_ADDRESS>type="text/css"/>
    </head>

and here's the error:

In case it's relevant: I'm working on a new plugin using the jspsych-contrib typescript template, which is what I'm loading via ../dist/index.browser.js.
I know @bjoluc said this was fixed in v7.2.3 so I must be doing something silly...

Hi @becky-gilbert, I'm unable to reproduce this – can you provide a repro repo?


Update serializers/parsers with latest protocol tests

This fixed three issues with protocol serialization/parsing:

If a struct is returned as null across the wire in json we should parse that as None, not {}.
If we're serializing to a query string and the value is a map we need to ignore the top level key and pull the map keys up to top level query string params.
If a query string value is a sequence, we need to serialize it as: {"a": ["b", "c"]} -> a=b&a=c.
Honor locationName in query protocol for non flattened lists.

See commit messages for more details.
cc @kyleknap @mtdowling @rayluo @JordonPhillips

:ship:

:ship:


rename S3 prefix on staging-ps2 to ps-staging-v2

Ideally it should be one prefix called e g v1 standing for the storage format version. But to accomplish that we'll need to rename prefixes on all pageservers.
Currently on staging there are two active pageservers, so to simplify that we can rename ps2 prefix to ps3 one to move only ps2 data into ps3 prefix.
Steps to do the ideal variant:

create v1 prefix
copy (can we move rather than copy?) ps2 and ps3 to v1
change configs in ps2 ps3 to point to v1 (they start uploading data that is present locally but missing in s3, remote_consistent _lsn can move backwards which is bad, but safekeepers upload wal to s3 so should be no problem)
check that nothing is present only in old prefix, if there is something missing from newer directory, copy again + restart pageservers so they can sync their internal state

Ideally we should have maintenance option for pageservers so projects are stopped and cannot start until pageserver they're connected to is on maintenance. @ololobus do we have that planned?
We'll need to perform the same dance on prod.

@zoete just to be sure, do we specify single prefix for pageserveers in new regions? To avoid repeating this on other regions...

Ideally we should have maintenance option for pageservers so projects are stopped and cannot start until pageserver they're connected to is on maintenance. @/ololobus do we have that planned?

No, I periodically think about some maintenance mode for projects, but didn't think about storage nodes. We have active flag, setting it to false will prevent scheduling new tenants to it, but old one still can start. We can add another one, like maintenance, but what should we do with already running computes?

No, I periodically think about some maintenance mode for projects,

It will also work. We can set flag in projects based on pageserver they're connected to

but what should we do with already running computes?

Any other options other than shutting them down?

After discussions with Stas we came up with these two options for migration process with decreased downtime period.
Double sync approach.

 Diff should be small. Has benefit of not deviating from standard operating modes. Because we currently do not test scenario when remote storage is disabled for some time and then reenabled.
Disable, copy enable

Disable remote storage, restart pageserver
aws s3 cp <old prefix> <new prefix>
aws s3 sync --dryrun to check that there is no difference
Restart pageserver with changed prefix and enabled remote storage.

This has the potential problem that we dont track pending deletions across restarts. E g if compaction deletes something then after restart this delete will be lost, and pageserver will download this data back during initial sync so it will end up having both compacted and non compacted version of the data at the same time which may cause unexpected issues.
I plan to write a test for that to see how it behaves in this case. Probably better to wait until I get the results before going further.
There is a third obvious variant with shutting down pageserver completely to do all manipulations as it is stated in the issue above. This looks safer to me, but extends downtime period.
Any other variants I missed? Concerns? Other thoughts? @kelvich @hlinnaka @SomeoneToIgnore
I plan to check selected variant on staging and stress env before applying it to prod

Done as part of account migration.


Bump train-test-fixture to 0.1.0

This is bogus and we need to fix the subscription so we don't get these


'error sending data frame: Too many frames in the outbound queue ' transfer of large size data fails

Issue is I have a service which sends data of size almost 1GB I know this is not best practice but what we see is with Istio-proxy over http/1.1 there is no issue but when I switch the protocol to http/2 I see the request fails with below log
Error:
http2/codec_impl.cc:677  [Tags: "ConnectionId":"51000"] error sending data frame: Too many frames in the outbound queue thread=31
[2024-12-03T12:05:05.334Z] "POST /upload HTTP/1.1" 502 UPE upstream_reset_before_response_started{protocol_error} - "-" 685768499 87 3653 - "-" "Go-http-client/1.1" "442a923e-8742-4508-93ff-a76f5a5906c3" "consumer-app-service.shiva.svc.cluster.local:8080" "<IP_ADDRESS>:8080" outbound|8080||consumer-app-service.shiva.svc.cluster.local
I have already checked a lot of issues that are similar to this which didn't help. I guess this issue is with Flow control but need a confirmation if it is ? what can be done?

@wbpcode Yes I have already tried it max_outbound_frames but it didn't solve the issue.


MAP for ES regression on MS MARCO doc slightly different from Lucene values

Follow up to #1167
I ran this:
$ python src/main/python/run_es_regression.py --regression msmarco-doc --input /tuna1/collections/msmarco/doc
...
2020-05-08 14:34:32,376 INFO - [SUCESS] 0.2308 MAP verified as expected!

In the end I got .2308 MAP, but that doesn't actually match the .2310 MAP reported here: https://github.com/castorini/anserini/blob/master/docs/regressions-msmarco-doc.md
@HangCui0510 @eiston

I ran this:
https://github.com/castorini/anserini/blob/master/docs/experiments-msmarco-doc.md
Instead of 0.2310 or 0.2308, I got:

@HangCui0510 hrm... can you debug and see what's going on?

okay

I think the problem is in msmarco-doc config. I am making adjustments on mapping parameters to see what's going on. It takes a very long time for each run.

@eiston Can you please help me with this? I have tried different mappings. they all give the same result 0.2308. I compared output run files among Solrini, Elastirini and Anserini, solrini and anserini are exactly the same, elastirini has the same doc ranking but double the scores.

@HangCui0510 Are the rankings (ordering of the documents) the same? Are the differences only isolated to a few different queries?

@HangCui0510 I am looking into this

@lintool about 1000 out of 5000000 are different on retrieval with topics.msmarco-doc.dev.txt

@lintool the differences are on many topics but only 2-3 rankings are different on these topics.

@lintool Oh, I think I know what the problem is. Please refer to the picture, it's the rounding that makes differences

Ah, I see. The rounding causes scoring ties, and that changes the map ever so slightly. I wonder why this same issue doesn't affect Solr? There, we can replicate results exactly, right?

right, it seems like solr and anserini have the same score scales, they have the same ranking score values. Elastirini's score is higher, nearly double.

@lintool Is this problem fixable? I noticed that elasticssearch with msmarco-passage also has a different value (slightly different) from lucene regression

I don't think there's much we can do about this issue. Good to document, though, for future reference. Closing.


.GetTerms returns empty set for pages with _build: render: never in 0.123

Say, you have some pages with this code:
_build:
  list: local
  render: never

That is, you don't need separate files for these files, but you render these pages elsewhere. However, when you get that page, you get weird results. First up, .GetTerms "tags" for example returns empty set.
Example site. In hugo 0.122 this site shows the following:
WARN  Test Page file tags:
WARN  -- Tag One (Test Page)

In hugo 0.123:
WARN  Test Page file tags:

So, it can't list tags. Also, in some a bit more complex environment (can't yet reproduce in simple site), when I dump subpage from a variable I get not Page(/path/to/page), but Page(nil) for pages having _build: render: never.

I'm not sure about this; it's a complex question involving many use cases. For discussion...
Build options: when should a page's terms contribute to a taxonomy object?

RENDER

always
link
never

LIST
always
:heavy_check_mark:
?
?

local
:heavy_check_mark:
?
?

never
:heavy_check_mark:
?
:x:

The cells that I've filled in are, to me, obvious choices.
If we were starting from scratch, I'd say do this:

RENDER

always
link
never

LIST
always
:heavy_check_mark:
:x:
:x:

local
:heavy_check_mark:
:x:
:x:

never
:heavy_check_mark:
:x:
:x:

The behavior with v0.123.0 is different than v0.122.0, but I think it might be better.

I think that there should be an option to make it work as I describe it: that is, no separate pages are generated, but you can work with these pages, use tags, etc. In our case, we have lists of updates (which a usually just a sentence, and there is no need to make it into a page, but we list all them on some pages). So, we need an ability to render it, but not in separate pages (as it would create about a one hundred thousand unneeded pages).

Rethinking my "if we we're starting from scratch" scenario, I think it should look like this instead:

RENDER

always
link
never

LIST
always
:heavy_check_mark:
:heavy_check_mark:
:x:

local
:heavy_check_mark:
:heavy_check_mark:
:x:

never
:heavy_check_mark:
:heavy_check_mark:
:x:

@TiGR Given my previous comment, I think we should close this.

Yes, I think it works


Redesign CORS middleware implementation

This PR extends the CORS middleware to better cover the specification. The implementation presented here is highly inspired by the rs/cors package.
However, some modifications here made for restQL, most notably that the request handling implementation on rs/cors abort the execution when the origin, method, or request headers to be issued by the client are not allowed and we choose to not abort and return the appropriate headers if possible.
This decision is based on the CORS spec about how the Access-Control-Allow-Methods response header is handled, pointing that if it's not present, then the actual request method will be automatically authorized. Hence, aborting the CORS logic on the server because a method is not allowed cause it to be authorized. This is further reinforced by the lib authors here.
We choose to return all possible header, not only the ones related to methods because as pointed in this issue on the CORS spec repository, the enforcement point in on the client and the restQL as a server participating in the CORS protocol defer any blocking to its client by providing the maximum information possible about the authorized operations.

Related: https://github.com/whatwg/fetch/issues/1588


Add incident marker to BPMN diagram

Incidents shall be shown in red on the diagram

Cool - thanks!

@berndruecker , I hope you like the result.


Wrong aria-current value in navbar

In my Navbar, I have most elements under the "Documentation" menu, and just one component outside of the menu.

This component, called "Dev tracks" is under the docs folder.

Here is how I organised the meta file:

My problem is the "Dev tracks" component is always defined as "aria-current=true".
You can check it here.

Seems you use Nextra 2, update to Nextra 3 first and reply if you still have an issue

@cfranceschi-ledger, you can work around it by creating a placeholder mdx file under pages.
In your case create a pages/dev-tracks.mdx file and leave it empty.

Hello,
@dimaMachina I updated but it did not fix it.
I tried @arno-fukuda's workaround and it does the trick. Even though it is not ideal to have this useless page, it will work for now.
I'm closing the issue.

Will reopen to fix it, ty for update


Update state of the world from the coinbase transaction

Create account if needed.
Add block reward.
Update the transaction Merkle tree.

@zp-sd implemented it in PRs #10 and #49, the only task is to create account if not yet present.


Custom functions on Echarts transform

What problem does this feature solve?
We would like to add line chart that are calculated from the values of other lines charts in the same graph. The calculation formula would be a javascript line of code entered by the user. We believe that the 'transform' function is ideal for that but the documentation only describes the inbuild (sort, filter) functions or the ecstats ones.
What does the proposed API look like?
So we could have a 'custom' type where we can define a custom javascript function that can use some data stored in the 'dataset' using their names.

Heres an example that may help

Hello,
Thanks for the link, but it does not really help because the echarts-simple-transform does not give much explainations on how to build such addon, and the Echart documentation does not either.
Regards.

Heres an example that may help

The example isn't working, likely missing data?

I have a similar task. I want to multiply the input dataset by a constant using transformations. As I understand, there is no built-in map transformation (only sort and filter). Therefore, I would like simple examples of how to do it myself.


Update ci-conan.yml

Merged in https://github.com/userver-framework/userver/commit/468948ddbb2f0f7a9ce8cb8f72fe03945a90b4e7


[EnhancedButton] Fix invalid labelColor prop being passed

Just updated to v0.15.2 and caught this prop still being passed down to <button> :smile:

Whoops, it looks like this fix needed to be made at the RaisedButton level.
Anyways, it looks like this is fixed already on master.


chrisant996.Clink version 1.4.18

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Duplicate of #96485


Add license to bower file.

The bower file didn't have the MIT license mentioned in it. Discovered while I was running bower-license.

Coverage remained the same at 100.0% when pulling eb95548936ab0b39341f8fe0d916b6bbaf7b38f7 on ericjperry:master into 44f6fdbf0b881a2d851e539a9ea2c12f3a4cac0f on omichelsen:master.

Thanks!


Enhance/rework serialize parse

This does a couple of things:

Moves some logic and structures to more logical places: white space structure t cats, gamut bound objects, and flags to gamut.bounds.
Cleans up CSS serializing and parsing. All serialization and parsing are now contained in the css module. This simplifies the color classes and moves all the noise to a dedicated CSS module. This also generalizes and removes duplicate, redundant code.
This picks up some of the changes of #117. This means we will need to rebase that work (or more like rework it). This will make generalizing that logic easier and confine to fewer places than it is currently.

@gir-bot lgtm


Add --with-libtls, --with-libtls-cflags, and --with-libtls-ldflags

Add --with-libtls, --with-libtls-cflags, and --with-libtls-ldflags configure options to support e.g. libtls-standalone, or headers and libraries from LibreSSL libtls on non-default paths.

I need to think about this a bit more. This could result in even more build problems for some people.
Maybe the order should be adjusted so that both the --with-openssl and --with-libtls options are processed together and then the checks for -lcrypto and -ltls happen. At least then there is no issue of --with-libtls replacing the -lcrypto and headers after the repsective configure checks have happened.

Commit 0fd7b2b4d7f00d0b730d3fe640827d1e475391da adds this pull request but at a different spot.


Multi_select filter not working in AA 1.0.0.pre1

Using ActiveAdmin 1.0.0.pre1 and everything was working fine until I tried to add some multiple select filters.  I'm filtering records based on country codes in the form of 2 letter alpha codes via the Countries gem.  If I declare my filter as follows:
  filter :country, as: :select, collection: Country.all

It produces the following source snippet and the filter works as expected a single country:

Country
<select class="select2-input" id="q_country" name="q[country_in]">
<option value="AD">Andorra</option>

With a URI produced as follows:
http://localhost:3000/admin/mymodel?utf8=%E2%9C%93&q%5Bcountry_in%5D=CA&commit=Filter&order=id_desc

However if I try to get it working with multiple select via the following
  filter :country, as: :select2_multiple, collection: Country.all

I end up with an oddly formatted list item in the filter panel and the following source snippet:

Country*
<input name="q[country][]" type="hidden" value="" />
<select class="select2-input" multiple="multiple" id="q_country" name="q[country][]">
<option value=""></option>
<option value="AD">Andorra</option>

The filter does not work at all even for single value selections and I end up with URIs like the following:
http://localhost:3000/admin/mymodel?utf8=%E2%9C%93&q%5Bcountry%5D%5B%5D=CA&commit=Filter&order=id_desc

Any idea  what is causing the huge difference between select2_multiple and the default select2 behaviour?  I am using select2_multiple in my forms and it works fine.

Trying to solve my own problem and it looks like this fork should have solved these issues:
https://github.com/atroppmann/activeadmin-select2/tree/activeadmin-1.0.0
But when I search through the gem it looks like these changes are already incorporated.
I tried changing my gemfile to the following and reinstalled all the gems but it does not appear to make any difference:
gem 'activeadmin-select2', github: 'atroppmann/activeadmin-select2', branch: 'activeadmin-1.0.0'

Having the same issue. It seems that even selecting an option when using :select2_multiple as a filter doesn't work.

+1

Seems like the project is no longer active. not sure how to get this fixed. Right now multiple select doesn't work at all.

So sorry for not dealing with this; flooded with work :(
It appears to be working fine on Pre2 so closing this; please re-open if still having issues

Hi
I'm using AA pre4 but get the following problem:
filter :countries, as: :select, collection: proc { Country.all }, label: "Implementation Country"

works fine!
filter :countries, as: :select2_multiple, collection: proc { Country.all }, label: "Implementation Country"

says, "undefined method `countries' for #Ransack::Search:0x007fc4155967b8"
Any idea why @mfairburn? Help much appreciated!


[ergoCubSN00*/ergoCubGazeboV1*] Add alljoints-inertials to be aligned with real ergoCub

This is the twin of https://github.com/robotology/icub-models-generator/pull/264. In this PR were added:

the .ini files for the inertials for the IMU sensors mounted on the FT of the arms and the legs. The ones of the feet were already added in:

https://github.com/icub-tech-iit/ergocub-software/pull/217
https://github.com/icub-tech-iit/ergocub-software/pull/222)

the alljoints-inertials_wrapper.xml and alljoints-inertials_remapper.xml to wrap up the inertials measurements (I didn't added them to the xml used by the yarprobotinterface by default);
for  ergoCub1.0 models (i.e. ergoCubGazeboV1, ergoCubGazeboV1_minContacts, ergoCubSN000): the arms and legs IMU as XMLBlobs in the .yaml and manually added to the urdf;
ergoCub1.1 models (i.e. ergoCubGazeboV1_1, ergoCubGazeboV1_1_minContacts, ergoCubSN001): the arms and legs IMU as sensors in the .yaml, so the correspondent urdf can be regenerated.

For the time being, I would keep this PR in draft since I want to see if the pose I added as XMLBlobs are correct.
cc @Nicogene @pattacini @traversaro

Awaiting this:

https://github.com/robotology/robots-configuration/issues/636
Before proceeding

Hi @Nicogene, I rebased this PR after solving the conflicts and now I put it ready for review.

Hi @Nicogene, thanks for generating the urdfs. I tried to launch the YRI with those models but I retrieved an error. In particular, there was a typo in a sensor name in alljoints-inertials_remapper. I fixed it here https://github.com/icub-tech-iit/ergocub-software/pull/232/commits/50fe75c72b730d422d16a409684d3a2eaa853f51.

Am I missing something or the added .xml files were not added in the yarprobotinterface .xml file?

Am I missing something or the added .xml files were not added in the yarprobotinterface .xml file?

I didn't add them since in the real robots they were not added to the yri launch file

Sorry, I just noticed that you wrote ths in the original description, I missed this.


Incorrect output paths for dependencies/assets on second and subsequent runs of hologram

I'm seeing an unexpected behaviour with hologram 1.3.0 when running the shell command more than once (as part of our watch task in local development).
The output path for dependencies is incorrect on the second and subsequent runs, nesting the dependencies inside the dependencies directory created on the first run, instead of replacing it (i.e. I get dependency paths like ./docs/build/build/ when I expect ./docs/build/)
Reduced test case
The hologram example repo exhibits this behaviour, though I'm also seeing it in our dev setup too. I had to rename config.yml to hologram_config.yml to get the example repo to work but that's a different PR :)

Clone the example repo: https://github.com/trulia/hologram-example & bundle install
run hologram in shell
run hologram in shell again

What I expected to happen
After the second run of the command I expected the structure of the ./docs/ directory to look exactly the same, with any changes to files in ./build/ reflected in ./docs/build/, i.e.
docs
\-build
	|-css
	\-script

What actually happens
After the second run of the command I get a directory structure like this:
docs
|-build
	|-build
	|	|-css
	|	\-script
	|-css
	\-script

i.e. a newly copied instance of build/ inside the original one.
Running hologram again has the same effect of copying ./build/ to ./docs/build/build/)
PS FWIW this is with ruby 2.1.5 on os x

Can you update your gem and try again (from rubygems, or dev if you like) This should be fixed in the 1.3.1 release.

You're completely right, sorry could have sworn I was running latest. Many thanks...

Thanks! I'm glad to hear it's fixed.

I was looking at this today and think it's still an issue in 1.3.1. I saw the change in 1.3.1 on line 164 of doc_builder.rb to change 'rm' to a recursive 'rm_r', but that's only for the copy_dependencies method. Shouldn't this also be done for the copy_assets method?

It's a good point, I'll take a look at that.


Remote debugger support - x86-64 target

Hi! Love the tool.
The README mentions plans for remote debugging (my personal main use case). Are there concrete plans or design ideas for this in place? If so, could they be shared. I am interested in contributing to this feature in particular.
Thanks,
Ziad

The basic idea here is to extend the ctrl layer to operate on top of N demon layers, rather than just 1 (the local one), and communicate with all such layers with a minimal set of hooks. These hooks could then redirect to either the local demon, or across the network to another demon. Then, correlate each demon instance with "machine" entities in the ctrl and df layers. There are further details that get involved, but that is the general idea.
This will make more sense to do after the Linux port is up and running.


Explore color options for handling plotly graphs

There are some build in options for color customization for plotly graphs. This issue will be to document thoughts and discoveries around this.
https://plotly.com/python/templates/#saving-and-distributing-custom-themes
https://plotly.com/python/colorscales/
https://plotly.com/python/builtin-colorscales/
https://plotly.com/python/styling-plotly-express/

potential color options:
color_discrete_sequence=["#f8dd70", "#c0bc5d", "#8e9b4c" , "#62793d",  "#3c582d" ,"#1c381d"]
["#f5f8c1", "#cdd8a0", "#a5b982" , "#7e9b65",  "#577d4a" ,"#1c381d"]

marker=dict(color=color_seq[5])


Error on log

What is your Quests version / build number (do not say "latest")?
186
Describe the problem and how to replicate it. Any console errors to post using Pastebin.com?
https://hastebin.com/jiluroseco.properties
If applicable, can you provide an example quest from quests.yml using Pastebin.com?

Resolved in 200a10efaac31a053d8a7f837347ae4cd2358691
Use https://ci.codemc.io/job/PikaMug/job/Quests/187/


BOffcanvas doesn't seem to use class for the whole component like sidebar-class on Bootstrap-vue

I'm trying to set a class for the BOffcanvas component:
<BOffcanvas       v-model="show"       placement="end"       body-class="px-0"       header-class="header"       lazy       :backdrop="false"       class="myclass"     />
The style is like this (I'm using SCSS and scoped):
.myclass {   width: 50% !important;   box-shadow: 0 0 1.5rem #6c757d; }
But, the class name is on the rendered component, but the class is not rendered or not applying

It's important to separate that offcanvas and sidebar are two different things. The bootstrap vue sidebar was not officially supported in Bootstrap, only in v5 of bootstrap was offcanvas added. So, your question is more of a Bootstrap question than a bvn question
There is a variable that you can change https://getbootstrap.com/docs/5.3/components/offcanvas/#variables --#{$prefix}offcanvas-width: #{$offcanvas-horizontal-width};


Istio to support Ingressgateway listener to bind on non-<IP_ADDRESS> IP address

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
Istio release-1.10 introduced the bind field in Gateway object, related code is here:
https://github.com/istio/istio/blob/master/pilot/pkg/networking/core/v1alpha3/gateway.go#L81-L84
It looks promising to bind on non-<IP_ADDRESS> IP address but according to the doc, this bind is not available to external gateway clients:
The ip or the Unix domain socket to which the listener should be bound to. Format: x.x.x.x or unix:///path/to/uds or unix://@foobar (Linux abstract namespace). When using Unix domain sockets, the port number should be 0. This can be used to restrict the reachability of this server to be gateway internal only. This is typically used when a gateway needs to communicate to another mesh service e.g. publishing metrics. In such case, the server created with the specified bind will not be available to external gateway clients.

We tried to create below gateway:
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: httpbin-gateway
spec:
  selector:
    istio: ingressgateway # use Istio default gateway implementation
  servers:
  - port:
      number: 8080
      name: http
      protocol: HTTP
    hosts:
    - "httpbin.example.com"
    bind: <IP_ADDRESS>
EOF

But got problem
2021-11-02T02:08:21.528433Z	warn	ads	ADS:LDS: ACK ERROR xxxxx Internal:Error adding/updating listener(s) <IP_ADDRESS>_8080: cannot bind '<IP_ADDRESS>:8080': Address already in use
Here is an explanation for this error: https://stackoverflow.com/a/14388707
So not sure if upstream is going to support this feature in the future and what's the consideration? And actually Envoy supports to bind on non-<IP_ADDRESS> IP address.
Currently the problems we are facing with the wildcard address listener are:

SNI mandatory, if the client doesn't support SNI it will get TLS handshake error.
Port Protocol conflict. If one user creates a HTTPS gateway on port 8082 and another user creates a gateway on 8082 but protocol is HTTP, then the latter one won't work.

Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[X ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

Does your pod have multiple IPs for this use case? Or how exactly does this work?

Thanks @howardjohn for you reply.
In our use case, we have the micro services in mesh. For example we'll create 1k Gateway, 1k VirtualService and 1k Service in the same mesh and there is one host match route in each VirtualService to route traffic to one backend service. However for each Gateway, we'll create a Gateway service with dedicated VIP and those dedicated VIP will serve the ingress traffic from external.
So we got this problem, for those 1k VIPs since envoy is listening on <IP_ADDRESS> not the actual VIP, Istio does the gateway merge which caused the issues like I mentioned:

Client SNI mandatory but we do have some clients don't support SNI.
Port protocol conflict since envoy doesn't support different protocols on same listener.
Idle timeout for downstream connections is not configurable at VIP level and we do have different services need different Idle timeout for downstream connections.

I would like to know if upstream has the plan to extend gateway bind field for this purpose or what is the consideration to not support, thanks in advance.

I don't think that is possible from a Kubernetes perspective, ignoring Istio/Envoy constraints. For example, I created a service with IP <IP_ADDRESS>
Then try to bind to this service IP in the pod:
$ nc -l -p 444 -s <IP_ADDRESS>
nc: bind: Address not available

Its Virtual IP address. Kubernetes will redirect it to :. If the pod is not bound to  (or <IP_ADDRESS> which is a wildcard so includes it), then it would not accept any traffic from the service.

If you want to do this you would need 1 unique target port per Service I think

@howardjohn
In our case, we are using IPVS IPIP tunnel as the L4 loadbalancer which will route traffic to IngressGateway pod through IPIP tunnel, hence the VIPs are configured in IngressGateway pod tun0 interface:
tunl0@NONE: <NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN qlen 1000
    link/ipip <IP_ADDRESS> brd <IP_ADDRESS>
    inet <IP_ADDRESS>/32 scope global tunl0
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/32 scope global tunl0
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/32  scope global tunl0
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/32  scope global tunl0

So in the gateway pod, we'll be able to create a listener and bind to this VIP. And apart for tun0, we can also configure the VIP to ingress gateway pod loopback interface if it's not IPIP tunnel, so there is no gap from Kubernetes perspective based on our implementation.
In our frontend service, we are using Contour as the control plane for the Envoy edge and we got same problem and we extend IngressRoute to support bind listener to different VIP for different IngressRoute:
apiVersion: contour.ufes.io/v1beta1
kind: IngressRoute
metadata:
  name: gateway-443
  namespace: ns
spec:
  http_connection_manager:
    idle_timeout: 600s
    stat_prefix: ingress_http
    use_remote_address: true
  listener:
    bind: <IP_ADDRESS>
    port:
      number: 443

So in the edge envoy config dump, we can see there are multiple listeners bind to different VIPs:
--
    {
     "name": "gw/gw-1-443",
     "active_state": {
      "listener": {
       "@type": "type.googleapis.com/envoy.config.listener.v3.Listener",
       "name": "gw/gw-1-443",
       "address": {
        "socket_address": {
         "address": "<IP_ADDRESS>",
         "port_value": 80
        }
       },
       "filter_chains": [
        {
         "filters": [
          {
--
    {
     "name": "gw/gw-2-443",
     "active_state": {
      "listener": {
       "@type": "type.googleapis.com/envoy.config.listener.v3.Listener",
       "name": "gw/gw-2-443",
       "address": {
        "socket_address": {
         "address": "<IP_ADDRESS>",
         "port_value": 443
        }
       },
       "filter_chains": [
        {
         "filters": [

That why we are looking for similar capability in Istio.

If you want to do this you would need 1 unique target port per Service I think

@howardjohn that's a workaround but doesn't work for all use cases. Currently we are migrating VIPs from hardware loadbalancer to IPVS + Istio,  existing micro-services VIPs with ports are widely being used by many clients, so if we have to assign unique port to different gateway, then all clients need to change their code.
Another workaround is that we can have same gateway port for different VIPs, but in the gateway service we'll allocate a different target port(like the kubernetes service node port), so we'll need a target port allocate mechanism but that's also not elegant if we have multiple mesh clusters.

I see, thanks for the explanation.
So looking at the error again, we actually are not rejecting it at all - its failing due to cannot bind '<IP_ADDRESS>:8080': Address already in use
In my cluster this ends up creating a listener like
       "address": {
        "socket_address": {
         "address": "<IP_ADDRESS>",
         "port_value": 8080
        }
       },

Which seems the same as contour.
Do you have this IP set multiple times maybe so its conflicting?

Thanks @howardjohn, I just tried the gateway bind option and it's now working. I can see the listener for this VIP in envoy config dump but looks like it's still SNI mandatory since there is filter_chain_match. Does it mean there is no way to disable SNI unless we set a * in the gateway host? With individual listener, we are able the configure the wildcard server name for each VIP/listener to achieve this.
    {
     "name": "<IP_ADDRESS>_8443",
     "active_state": {
      "version_info": "2021-12-02T04:45:15Z/359950",
      "listener": {
       "@type": "type.googleapis.com/envoy.config.listener.v3.Listener",
       "name": "<IP_ADDRESS>_8443",
       "address": {
        "socket_address": {
         "address": "<IP_ADDRESS>",
         "port_value": 8443
        }
       },
       "filter_chains": [
        {
         "filter_chain_match": {
          "server_names": [
           "abc.example.com"
          ]
         },

@howardjohn  Probably for security concern, we won't issue cert with wildcard host in the SNI although here the cert SNI can be non-wildcard.
BTW good to know the gateway bind is working. Is this field designed to support the multiple listener case? And at least this feature works for below to issues:

Port protocol conflict
Idle timeout for downstream connections per listener

Certificate SAN and SNI do not need to be identical. You can have a cert
for foo.example.com and have the gateway match *. If you are
already distinguishing by IP instead of SNI/Host then seems reasonable to
use *.

Is this field designed to support the multiple listener case

It was original added mostly to support localhost bind. I think your case
is quite unique in Kubernetes, but glad it works as well...
On Fri, Dec 3, 2021 at 2:46 AM shonecyx @.***> wrote:

@howardjohn https://github.com/howardjohn Probably for security
concern, we won't issue cert with wildcard host in the SNI although here
the cert SNI can be non-wildcard.
BTW good to know the gateway bind is working. Is this field designed to
support the multiple listener case? And at least this feature works for
below to issues:

Port protocol conflict
Idle timeout for downstream connections per listener

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/36282#issuecomment-985415615, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIHTYRQHBHMEQZS2F3UPCNWTANCNFSM5I6C6HRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thanks @howardjohn for you comments, closing this issue now as already supported.


Query URL Generation Does Not Handle Arrays Properly

In RapiDoc v8.4.8, array parameters are no longer handled properly when generating query URLs.
All problems are readily observable in your Built in API console example
Problems

An empty copy of all array-type query parameters is included in the generated "Try" URLs, including those for which no value was specified.
After clicking "Try" all array-type parameters are reset to their example values.  If there is no example value, the parameter is cleared.

The screenshot below is an example of both the generated URL and query parameter values after clicking the "Try" button.  All problems listed above are visible.

this has been partially addressed to not send empty array. (this is there in the the non-released build available at dist/rapidoc-min.js )
The 2nd part where the values inside the input gets reset after clicking TRY may needs more involvement as it is a custom web-component and being used in our other projects. I am keeping this issue open for tracking.
However, no one is working on this, I will love to get a PR if anyone is interested in making an attempt

I can say with certainty that this problem was introduced with commit 4fa451dc58aa0cc7071a088b56b95801f64c0ba7.
For those who don't need the ability to paste comma-separated values into array parameter fields, I've created a variant of RapiDoc based on v8.4.6 that resolves these issues in the short-term by removing support for pasting comma-delimited text into array parameters.  I'm calling it v8.4.7 as that name doesn't appear to have been taken by an official release.

the commit  4fa451d may have also fixed some other issues, apart from enabling comma separated value pasting. for instance it may buggy when initialize the field with multiple values, which is needed to pre-fill multiple example values if provided in the spec.

I'm calling it v8.4.7 as that name doesn't appear to have been taken by an official release.

JSYK - we scrap some releases if they are buggy or route them to a closed source fork if it contains any company specific implementation, so it is always better to name or tag them in an incremental order if you have to for any reason

@mrin9 was this issue fixed somewhere or just dropped?

While @mrin9 has been silent on this—and it wasn't mentioned in the release notes for v9.0.0—this issue appears to have been fully resolved in the release version of v9.0.0.  In my testing, values added to array parameters are no longer reset to their example values when the TRY button is clicked.


Language E2E test / SPA-944

For other E2E tests, we decided to focus on where backend adds value or can influence or cause breakage.
The assumption is that these kinds of tests are in addition to what Stan already is working on, so check with him. E.g. you can register successfully, and the user is logged in.

For E2E purposes, some suggestions related to how we get data from the backend:

Check that the menu is there and populated (even if there is only 1 language right now it's still there I think)
Changing the language refreshes the whole site
** ... but stay on same page/view/screen.
*** In fact if you are in the middle of registering and change the language, your entire form should remain the same.
** Check that the text has changed to target language.

Product details page is a good one to make assertions from, as well as registration page for forms.

Another test: do a browser refresh after switching the currency/language, to make sure the change sticks beyond the explicit change request from the user. (and doesn't fall immediately back to the default)

The backend sampledata provides English, German, Chinese and Japanese.
Note that language and currency e2e tests are similar in scope - see SPA-945.

QA done. Language e2e test works good.


[BEAM-13444][Playground] Add processing of an error

[BEAM-13444] Add processing of an error at RunOutputWriter

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

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

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM
please resolve merge conflicts


moranthomas_181123_210113.935

Type: Incorrect
Summary:
VALID test
Details:
test
Resolution:
test
Affected definitions:

async 2.6.0

You can review the change introduced to the full definition at ClearlyDefined.


:wrench: Upgrade .gitignore

:wrench: Ignore automatic files
Minor .gitignore upgrade:

Remove duplicated folders
Upgrade list of automatically created files that should be ignored
Use GitHub Node.js .gitignore template
Also ignore Emacs automatic files
Use Parse git commit message emoji

Coverage remained the same at 91.925% when pulling 35732ce30a28d12a8a72a4123279d3f8bcf96077 on jpventura:upgrade_git_ignore into 86bd66ffe1bc2c597e2ba4baaf1258ed6fd55e51 on firebase:master.

Coverage remained the same at 91.925% when pulling ff7e4d7c1602d3c3f468e8736a9bbdba86b71e77 on jpventura:upgrade_git_ignore into 86bd66ffe1bc2c597e2ba4baaf1258ed6fd55e51 on firebase:master.

Modifications were added to #156 pull request.


Filter ODL jobs based on user and process name

On my Ubuntu 14.04 based system the previous script was causing
multiple instances of ODL to spawn due to the fact that PID tracking
was searching for karaf process, whereas the the karaf process
spawned a java instance. Hence Upstart tracked a wrong PID and
assumed that ODL job is always stopped. That also caused inability to
stop the service, because PID was incorrect, so upstart was sending
SIGTERM to a wrong process.
With this change, upstart searches for a java process belonging to
user odl in order to determine the PID.

I've just noticed issues with this approach when booting up the machine. I'll close this PR and get back with a fixed change.

@semihalf-kardach-stanislaw - Thanks for the bug description and PR! Looking forward to merging the updated patch. :)

I've updated the patch so that it does not hijack the TTY when booting, although karaf can still spit some logs to stdout (basically anything that lands into data/karaf.out), however it's a minor issue given that now the service process is detected successfully.

@semihalf-kardach-stanislaw Looks good, thanks again!

Ubuntu 14.04 tests are passing, for the record.
Finished in 20 minutes 7 seconds
49 examples, 0 failures


Backend - Refactor Big Services

Interest Area and Post services are too big and do not follow best practices. Big functions should be divided into small functions that have single task.

Create private util functions:

refactor PostService
refactor interest area service
create private util function

Create service to prevent repository-service communication:

create InterestAreaPost service
add methods to InterestAreaPost repository

Some minor logic changes:

delete related entities when interest area deleted
create necessary services to delete interest area related entities

Done! #436


[Parallel intervals] New interval processing

Description
Replaces the logic in gt4py.ir.utils.make_axis_interval and gt4py.frontend.gtscript_frontend.IRMaker. _visit_interval_node to support a new syntax and parallel interval parsing.
First PR in the parallel intervals series.
Changes:

Adds __getitem__ to gtscript.Axis objects so that splitters can be defined, e.g. K[1], and intervals, e.g. interval(K[1:-1]) (this is now supported!)
Adds "unit tests" for the interval calls.
A few unrelated linting fixes.

To do:

[x] Finish removing old interval processing

Resolves #226.
Requirements
Before submitting this PR, please make sure:

[x] The code builds cleanly without new errors or warnings
[x] The code passes all the existing tests
[x] If this PR adds a new feature, new tests have been added to test these
new features
[x] All relevant documentation has been updated or added

Additionally, if this PR contains code authored by new contributors:

[x] All the authors are covered by a valid contributor assignment agreement,
signed by the employer if needed, provided to ETH Zurich
[x] The names of all the new contributors have been added to an updated
version of the AUTHORS.rst file included in the PR

@GridTools/gt4py-core This one is ready for review now.


Help for Shutdown script in Elastigroup doesn't exist

When setting up Elastigroup in Azure, following the link for the documentation about shutdown scripts, it leads to a page that does not exist.

Hi @tobbra, can you please send the URL you used so we can check the issue? Many thanks for reporting this!

Seems to be fixed already. It was this link https://docs.spot.io/elastigroup/features-azure/shutdown-script-in-elastigroup-for-azure. I'll close the issue. Thanks for reaching out!

Just noticed, it's not fixed; this is the link that leads to a non-existing page: https://docs.spot.io/elastigroup-for-azure/shutdown-script-in-elastigroup/. You'll find the link when you create and Elastigroup and navigate to the Compute page. In the "Shutdown script" section there's a "Learn more" link which points to the non-existing page.
I think the correct link should be the one from my previous post

Here's another one that doesn't work: https://docs.spot.io/elastigroup/azure/getting-started/import-an-existing-azure-resource

Hello, we have fixed the two URLs. Thank you for bringing this to our attention.


Extend table component

This PR adds functionality to the table component necessary for completing the ValueSets UI initiative.
Test Steps:

Load up RS locally
Navigate to Admin > Feature Flags
Add "value-sets" to the list
Navigate to Admin > Value Sets (should appear now)
Check out the table in action. Add rows and edit values

Changes

Table can have title
Table can have legend
Table can have a DatasetAction (i.e. the Add Item example button)
Table values can be edited
Table columns can be actionable buttons (not used for ValueSets, check Daily Data for that)

Checklist
Testing

[X] Tested locally?
[X] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[X] (For Changes to /frontend-react/...) Ran npm run lint:write?
[x] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

Fixes #5460

@TomNUSDS

does server api have validation already?
This is what we're waiting to hear. Seth is doing the backend discovery work, so as of now we don't quite know what the validation/cleansing needs are!


Review ServiceAccounts and RBAC policy on the Elemental Operator

Review the access policy for the ServiceAccounts created and in use in the Elemental Operator.

Moved to rancher/elemental-operator repo


Chapter/parallel computing completed

Details
Parallel Computing section is complete. I've removed the "shared memory" section as it is merged in "What is parallel computing" section.
Linked Issues

#6

Thanks for the review, I didn't actually attempt compiling the mdBook before I made the PR, and I should've done it earlier because I can see a lot of things breaking/feature not existing in mdBook.
The contents are ripped straight off the presentation slides with no additional details added - I will add the contents you have mentioned moving forwards .

Log into M3
Copy you file (maybe some SSH/SCP can be done for this as a bonus skill)
Create a Slurm job file for this program that runs on a single machine and single core/thread > and measure the execution time and record it in a file

I will presume that these tasks/challenges are going to be in the M3 section already, so in the parallel computing section, I will assume the reader has the knowledge to perform these tasks (maybe link to the M3 section), does that sound alright?

... I didn't actually attempt compiling the mdBook before I made the PR, and I should've done it earlier because I can see a lot of things breaking/feature not existing in mdBook.

I figured but all good. You can have it running will editing and it will dynamically update.

The contents are ripped straight off the presentation slides with no additional details added - I will add the contents you have mentioned moving forwards .

Awesome, I look forward to seeing what you come up with.

I will presume that these tasks/challenges are going to be in the M3 section already, so in the parallel computing section, I will assume the reader has the knowledge to perform these tasks (maybe link to the M3 section), does that sound alright?

Yes that is correct. Everything from Slurm to loading modules is planned for the M3 chapter while multi-machine and message passing is planned for the Distributed Computing chapter. Links or even just weak references are a good idea as well.
I'll also create the template GitHub project for the recruits now so you and @MonashDeepNeuron/hpc-training can start creating challenges in there. We can break each chapter into different directories and break those down further as need.

@MonashDeepNeuron/hpc-training HPC Training Challenges Template repo is up. 🚀


Document how to use the flag --configuration-file-path

Documentation Request
Can not use the flag configuration-file-path in dotnet-monitor
I try to use the --configuration-file-path to specify the configuration file in dotnet-monitor command. However dotnet-monitor can not recognize the flag.
PS C:\Users\laurence> dotnet monitor collect --configuration-file-path C:\ProgramData\dotnet-monitor\settings.json
Unrecognized command or argument '--configuration-file-path'.
Unrecognized command or argument 'C:\ProgramData\dotnet-monitor\settings.json'.

Description:
  Monitor logs and metrics in a .NET application send the results to a chosen destination.

Usage:
  dotnet-monitor collect [options]

Options:
  -u, --urls <urls>                   Bindings for the REST api. [default: https://localhost:52323]
  --metricUrls <metricUrls>           Bindings for metrics api. [default: http://localhost:52325]
  -m, --metrics                       Enable publishing of metrics [default: True]
  --diagnostic-port <diagnosticPort>  The fully qualified path and filename of the diagnostic port to which runtime instances can connect.
  --no-auth                           Turn off authentication. [default: False]
  --temp-apikey                       Generates a new MonitorApiKey for each launch of the process. [default: False]
  --no-http-egress                    Turn off HTTP response egress [default: False]
  -?, -h, --help                      Show help and usage information

Previous documentation
The configuration mentioned the flag --configuration-file-path
https://github.com/dotnet/dotnet-monitor/blob/main/documentation/configuration.md#configuration-sources

Sorry you ran into this; this command line option is available in 7.0 (which is still in preview) and in the upcoming 6.3 release. We'll update the documentation with these version constraints.

May I know what is the timeline for the 6.3 release? Thanks.

May I know what is the timeline for the 6.3 release? Thanks. This feature allows me to set up multiple dotnet-monitor on a machine for exporting different Dotnet app metrics.

I don't have a specific date, but we plan to have it available this month. You can monitor the releases as it will be published there when it becomes available.

Fixed by #2607


Git repo too big

Please clean up the repo history(or re-create it fresh), the previous commits that had binaries checked in are making it huge and quite slow to clone.

I managed to delete the binaries from the history, bumped the version to the latest and added a Makefile for easier installation. You can see these changes in my fork: https://github.com/cristim/selenium-webdriver-rpm

Thanks for the update!  It has been difficult to find time to work on
this.  I made a force push of your change which has brought the repo back
down to a reasonable size.
On Thu, Mar 12, 2015 at 9:53 AM, Cristian Măgherușan-Stanciu <
<EMAIL_ADDRESS>wrote:

I managed to delete the binaries from the history, bumped the version to
the latest and added a Makefile for easier installation. You can see these
changes in my fork: https://github.com/cristim/selenium-webdriver-rpm
—
Reply to this email directly or view it on GitHub
https://github.com/djhenry/selenium-webdriver-rpm/issues/2#issuecomment-78482967
.


Oracle triggers not visible

Running 4.0.6 on Linux Mint
Can create triggers but not view them afterwards or see the ones which already exist.

Can't reproduce.
Isn't this the same as in #1630?

That is the same issue I am seeing.  A coworker confirmed that he saw the
same issue. Could it be oracle version specific?
On Tue, May 9, 2017, 12:01 PM Serge Rider<EMAIL_ADDRESS>wrote:

Can't reproduce.
Isn't this the same as in #1630
https://github.com/serge-rider/dbeaver/issues/1630?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/serge-rider/dbeaver/issues/1648#issuecomment-300211918,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrJ-5t67yS5d60e6qMKXggMW3tyzzUTks5r4I3NgaJpZM4NVf0i
.

Well, then this is not a bug.
Probably I should change schema triggers node name to make it less confusing.


[ArPow] Default centos images used in CI does not build the ArPow prototype.

The default centos images used in CI, mcr.microsoft.com/dotnet-buildtools/prereqs:centos-7-3e800f1-20190501005343, does not work to build the ArPow tarball prototype.
EXEC : error : Unknown subcommand: get-url [/repos/sb-proto/src/SourceBuild/tarball/BuildSourceBuildTarball.proj]

We'll need to investigate this and either update the centos image or fix the git command to use something that is supported.

[Triage] It should be easy to eliminate the dependency on get-url.  This would be beneficial because it would lower the git version dependency and make source-build more broadly buildable on various environments.

[triage] tarball CI is using a newer fedora image.


improve error message

https://travis-ci.org/github/crate/cloud-getting-started/jobs/664347119?utm_medium=notification&utm_source=github_status
this is what happens when the vale git isn't responding. we could add a better error message here

As we've already moved off Travis CI, can we kondo this?

@amotl I don't think so. this is an issue with the Makefile itself not providing a useful message for the user when there is a network issue that causes the Vale download to fail. this is something that can happen to regular users. it's just that the issue also occurs when the PR checks run too sometimes


[Bug]: Content-Security-Policy blocks access.

What happened?
I guess this is a CORS issue with my React app? But some guidance on this would be helpful.
GET https://cdn.paddle.com/paddle/v2/paddle.js net::ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep 200 (OK)
I've tried modifying my Content-Security-Policy to this:
<meta http-equiv="Content-Security-Policy" content="script-src 'self' https://cdn.paddle.com/; worker-src 'self' blob:;">
But it doesn't seem to help. Any thoughts? Could the code that downloads the script in the package be marked specifically with some modifier that CORS allows? I've seen that done elsewhere.
Steps to reproduce
Use the package via yarn install in a React app that has a strict Content-Security-Policy.
What did you expect to happen?
No response
How are you integrating?
No response
Logs
No response

Hi @zachwhelchel,
We are more than happy to help.
Looking at the error code NotSameOriginAfterDefaultedToSameOriginByCoep, I am guessing you have a Cross-Origin-Embedder-Policy header set as require-corp.
If yes, can you please change it to credentialless along with the Content-Security-Policy change you already had in your question to allow scripts from https://cdn.paddle.com/
if not, please share all the security headers you have in your application so that we can check further.
Thank you.

@vijayasingam-paddle thanks for the response. I set the Cross-Origin-Embedder-Policy as you suggested and it gets further now... but when I try to initialize a checkout the window shows this:

There are no errors given in the console so I'm not sure what to do next.

@vijayasingam-paddle I just checked the documentation for my code base and apparently there are restrictions on the CORS changes I can make:
In addition to the HTTPS requirement, the Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy headers must be set to require-corp and same-origin respectively.
Is there any way around this from your all's end? Does Paddle provide a hosted checkout page? Where I could direct users to with some prefilled options? Any way I try this I can't seem to get paddle to load on my app.

Hi @zachwhelchel,
Sorry, we do not provide hosted checkout pages in Paddle.
Changing CORS headers is a very common approach to include third party scripts (Including Google Analytics or Cookie consent popup providers) to our applications.  So it should be alright to change the CORS headers to allow downloading scripts from our domain.
Unfortunately, I don't see any other option to make it work.

but when I try to initialize a checkout the window shows this:
This is strange, we suspect a firewall or some other issue in your end.

What happens when you open https://buy.paddle.com/ in your browser? it should throw a Something went wrong as it is missing some input not relevant to our test to see if you have a problem on your end.

@vijayasingam-paddle this is what I see when I go to that url. So it seems to load in another tab but in my app it's still giving the "refused to connect" error I posted above. Is there some other security setting that needs to be set that we haven't covered?

@vijayasingam-paddle I thought it might be due to a "frame-src" in the Content-Security-Policy but that doesn't seem to be the case.

I also tried adding this and it didn't change anything:
frame-ancestors 'self' https://sandbox-buy.paddle.com/;

@vijayasingam-paddle welp... it turns out that Safari is still not pleased with my changes to "credentialless". We use the Shared Array Buffer and "credentialless" removes access to it for security purposes.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer
Is there any chance I can set up a developer support call or something? I really want to implement Paddle but I just can't seem to get it working!

Hi @zachwhelchel,
I am sorry to hear that you are getting stuck while integrating with Paddle.
Can you please reach out to us at<EMAIL_ADDRESS>and one of our support specialist will be able to help you with the integration.
Thank you.

@thomasdondorf thanks for jumping in here. Just an update from my end. I was never able to get this working... I had to opt to sending users to a page on my marketing site to process the payment. Not ideal. Would love to see this fixed.

@zachwhelchel Sure, I was happy someone had already reported the problem :)
The only way to solve this currently is to redirect from the "main page" to some special page with the policy disabled...

Hi @zachwhelchel,
I am so sorry, i was with the impression that our support team was working with you to solve the problem. I didn't know that it was still open.
Hi @thomasdondorf,
Thank you for sharing a very detailed report.
I will check with our support team to find why it was not addressed and move the ticket back to engineering to fix this problem.
Thank you for your patience, I am really sorry for the inconvenience.

This one is super interesting for me 😃 I hope we can get it working soon

Hi everyone,
Sorry for the long silence on this issue.
I am working with our security team internally to come with the best solution that works for everyone and will update you once i have something concrete.
Thank you for waiting patiently.

I'm seeing a CSP issue too. Not sure if it's the same problem as that discussed here but I'll report just in case it's related.
I have paddle integrated into an electron app that has the following CSP:
 <meta
            http-equiv="Content-Security-Policy"
            content="default-src 'self' https://describo.github.io https://stamen-tiles-a.a.ssl.fastly.net/ https://api.github.com https://raw.githubusercontent.com https://api.ror.org;
            script-src 'self' https://cdn.paddle.com/paddle/v2/paddle.js https://public.profitwell.com/js/profitwell.js;
            style-src 'self' 'unsafe-inline' https://sandbox-cdn.paddle.com/paddle/v2/assets/css/paddle.css https://cdn.paddle.com/paddle/v2/assets/css/paddle.css;
            connect-src https://www2.profitwell.com;
            img-src * crate-file: data:;
            media-src crate-file:;
            frame-src https://buy.paddle.com https://sandbox-buy.paddle.com;"
        />

In dev, connecting to the paddle sandbox works fine but when the app is built, it refuses to connect to paddle prod.
In the console I see:
[Report Only] Refused to frame 'https://buy.paddle.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors ". Note that '' matches only URLs with network schemes ('http', 'https', 'ws', 'wss'), or URLs whose scheme matches self's scheme. The scheme 'https:' must be added explicitly.
[Report Only] Refused to frame 'https://buy.paddle.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors ". Note that '' matches only URLs with network schemes ('http', 'https', 'ws', 'wss'), or URLs whose scheme matches self's scheme. The scheme 'https:' must be added explicitly.

Hi @marcolarosa,
You are seeing a different error and not related to this GH issue.
As the log says, the message you see is [Report Only] and should not be blocking your request. With that said, we found that our checkout doesn't open within an electron app because of the domain checks.
Our Checkouts can be launched only from approved domains in Production. However, as electron apps do not have a domain, our validation is failing and throwing an error.
I am sorry that you are running into this issue.
I am checking with the team about fixing this issue. Meanwhile, please open a different issue in GH to track this independently.
Thank you.

@vijayasingam-paddle Ahh sorry! Thanks for the advice.

Hi @zachwhelchel / @thomasdondorf / @pedrovgs,
Thank you for being patient while we were looking into this issue.
Unfortunately, I have some bad news. I am afraid we won't be able to make our checkouts work with cross-origin isolation.
Changing the CORS headers in the Paddle side of things was the easier change. However, we quickly found that the problems don't stop there.
In a cross-origin isolated environment, all the iframes loaded into the browser will inherit the same COEP and should either be from the same domain or include appropriate CORS headers. Even though we could fix the headers on our end, we rely on other payment partners and their servers do not send any CORS headers.
Due to this, with the correct CORP and COEP headers we will be able to run Paddle.js and launch checkout. However, it will fail when it reaches the 3DS payments screen with the same error.
There is a proposal to allow iframes to act independently, though browser support is minimal as it works only with Chrome at the moment. We cannot choose this solution as we will have to support all the browsers.
Sadly, there is very little we can do about this issue. We will keep tabs on the proposal and we could get it working once every major browsers start supporting it.
Please let us know if we can help you with anything else.
Thank you

@vijayasingam-paddle would it be possible to allow opt-in for using the credentialless iframes?

Hi @lowkahonn,
That is something we can do. However, we would probably not recommend this for most users because this will hit the conversion rate drastically.
I will get this working in a couple of weeks and maybe we could run some beta tests to see real-world impact.
Thank you.

Hi @reknih,
We would like to keep the library pure and move away from any side effects based on the browser. We won't be auto-detecting this property based on the browser and would like our integrators to pass the value when they need it.
I found this snippet to detect if an element supports a property.
You can use this to detect if iframe supports credentialless and pass it to the new attribute we will add to PaddleJS.
Thank you.

I was able to integrate the payment process relatively smoothly in the following way. I added an exception in my server configuration to not serve the "Cross-Origin" headers for the one page that integrates Paddle.js (/checkout in my example).
Here is my (simplified) nginx config.
location = /checkout {
    try_files /checkout.html =404;
}

location / {
    add_header Cross-Origin-Opener-Policy "same-origin";
    add_header Cross-Origin-Embedder-Policy "require-corp";

    try_files $uri.html =404;
}

Note for Next.js users (like myself): Make sure to use actual links (a instead of Link) and "real" redirects (location.assign/location.replace instead of router.push/router.replace) when linking to the Paddle page as otherwise the headers will not be loaded.
Maybe this helps someone else.

As someone reached out to me for help, I'll give more details below:
You can see it in action here: https://www.chessmonitor.com/pricing, but you have to create a (free) account.
I hope it's okay that I link it here (if you are a chess player, check it out 😉).
Basically there are two pages:

/pricing

This page does not interact with Paddle. It only presents the data to the user.
When the user wants to subscribe to a plan, I call location.assign(`/checkout?plan=${PADDLE_PRICE_ID}`) to send the user to the checkout page.

/checkout

This is the only page in the frontend that interacts with Paddle.
In contrast to /pricing this page is not linked anywhere and users should only be redirected here. If a user opens /checkout on his own, he will simply be redirected back to the pricing page.
The page can do two things:

Users can "order" (via /checkout?plan=[PADDLE_PRICE_ID])
Users can "update their payment information" (via /checkout?_ptxn=[SOME_INTERNAL_PADDLE_DATA])

Case "Order":

The checkout page then initializes Paddle and calls Checkout.open(...) with the priceId from the URL.

Case "Update payment information":

When your user uses the URL provided in data.management_urls.update_payment_method via the subscription API, it will send him to the Default payment link (set in your Checkout Settings), together with a parameter _ptxn. That page is /checkout here. So it looks like this: /checkout?_ptxn=[SOME_INTERNAL_PADDLE_DATA]
In this case, the checkout only initializes Paddle and Paddle.js will take care of the rest. Just make sure you don't open the checkout again if that parameter exists.

And of course, you should setup an event listener to listen to events like checkout.completed/checkout.closed to forward the user back.
Hope that makes it more clear!

import { initializePaddle, Paddle } from '@paddle/paddle-js';

export const PaddleCheckoutButton = ({ user, className }: { user: User, className?: string }) => {
  const [paddle, setPaddle] = useState<Paddle>();
  const email = user.email ?? '';

  useEffect(() => {
    initializePaddle({ environment: process.env.NEXT_PUBLIC_PADDLE_SANDBOX == 'true' ? 'sandbox' : 'production', token: process.env.NEXT_PUBLIC_PADDLE_CLIENT_TOKEN ?? '' }).then(
      (paddleInstance: Paddle | undefined) => {
        if (paddleInstance) {
          setPaddle(paddleInstance);
        }
      },
    );
  }, []);

  const openCheckout = () => {
    paddle?.Checkout.open({
      customer: { email: email }, //after add this line , won't work
      items: [{ priceId: process.env.NEXT_PUBLIC_PADDLE_PAYMENT_PRICE_ID ?? '' }],
    });
  };

  return (
    <Button variant={'default'} onClick={openCheckout} className={className ?? ''} >Add funds</Button>
  );
}

here is my basic Paddle check button to show a overlay checkout , if add customer email it wont't , but if hard code a<EMAIL_ADDRESS>,it's works, mean i cannot pass any parameters to checkout open just because cross-origin issue ?

I've faced the same issue at https://insightvox.net, so I had to disable the CSP for the  where the Paddle iframe is shown.
Since I'm using Ruby on Rails, this method https://api.rubyonrails.org/classes/ActionController/ContentSecurityPolicy/ClassMethods.html#method-i-content_security_policy_report_only
allows setting the CSP as report only.
So in your controller, you would add:
 content_security_policy_report_only only: :new
to ensure only the affect route is disabled.
In my case the subscription page is under authentication, so the risk is limited, but ensure you know what you're doing.
Hope this helps other people landing here!


tsserver picks up hidden files created by emacs

TypeScript Version:  tsserver version: 3.5.1
Search Terms: Tsserver Emacs hidden files
Actual behavior:
Emacs creates hidden files to protect against simultaneous edits. tsserver picks up these files and does lot of work. As these files are created and deleted for each save, these triggers lot of extra work that's unnecessary. This feature is enabled by default in emacs, so most of the users would run against this problem. I have not noticed this behaviour in older versions of tsserver, but I don't know the exact version which introduced this.

Expected behavior:
tsserver should ignore hidden files by default.
reference https://github.com/ananthakumaran/tide/issues/320

We would need to add /.# to ignored paths

@sheetalkamat https://github.com/microsoft/TypeScript/pull/31954


Bug: Download failed

Updater rely on Github API. If it refuses to accept connection, download will fail. Also it is possible that program can't create folder where update will be downloaded. Try to move program to different folder (if its located in Program Files) or drive. Currently there is no logger so I cant tell what exactly gone wrong

Try to move program to different folder (if its located in Program Files)
FancyOSD is well located in the Program Files, sorry for the inconvenience.


Invert the progress

Hi ,
How to invert the progress from left to right TO right to left ?
Thanks

this how I did it
myProgress.setRotation((-value / 100f * 360f) - 90f);
myProgress.setProgress(value);


hi i tried to freeze the model for infrence uses but whenever i tried to run freese graph i get the error

i have frozen the graph till the argmax layer
Traceback (most recent call last):
File "/media/ankit/Data/ML/MVCNN-TensorFlow/test_forzen_graph.py", line 130, in
predictions = sess.run(output_node, feed_dict={input_node:[x],y_:views})
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 778, in run
run_metadata_ptr)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 982, in _run
feed_dict_string, options, run_metadata)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1032, in _do_run
target_list, options, run_metadata)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1052, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: transpose expects a vector of size 6. But input(1) is a vector of size 5
[[Node: import/transpose = Transpose[T=DT_FLOAT, Tperm=DT_INT32, _device="/job:localhost/replica:0/task:0/gpu:0"](_recv_import/im0_0/_1, import/transpose/perm)]]
Caused by op u'import/transpose', defined at:
File "/media/ankit/Data/ML/MVCNN-TensorFlow/test_forzen_graph.py", line 110, in
tf.import_graph_def(graph_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/importer.py", line 308, in import_graph_def
op_def=op_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 2336, in create_op
original_op=self._default_original_op, op_def=op_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1228, in init
self._traceback = _extract_stack()
InvalidArgumentError (see above for traceback): transpose expects a vector of size 6. But input(1) is a vector of size 5
[[Node: import/transpose = Transpose[T=DT_FLOAT, Tperm=DT_INT32, _device="/job:localhost/replica:0/task:0/gpu:0"](_recv_import/im0_0/_1, import/transpose/perm)]]
update::
i think i need to initialise the placeholder variable with some tensor of size 4096 am i correct?

i think i found the answer need to assign the placeholder value equal to value 0.5 which is the initial value of the probabilty used for training.


[feature request] {{open_sensors}} as friendly_name array

Hi,
As the name suggests, I propose an extra state attribute with the friendly names of the current {{open_sensors}} attribute.
Use case: this way smart speakers can announce the reason for the alarm trigger (in case they don't like the notification component or to build bigger trigger scripts).
Thanks

If you want to create a script, then you can also get the friendly name from the entity properties.
I mean states('binary_sensor.my_sensor') will give you all info of the sensor.
Why do you think such properties should be published by Alarmo?

I think the reporting of {{open_sensors}} as a friendly-name array would allow the creation of more powerful scripts than what is currently possible in the Alarmo -> Actions page.
My use case is:
On alarm trigger -> script to play siren on smart speakers + then announce which sensor triggered the alarm.
The script works very well but doesn't have easy access to the friendly name of the sensor that triggered the alarm.
A workaround for me is to create a binary sensor that translates the {{open_sensors}} array into the friendly names but it's not very elegant.
When I try to copy-paste my working script into the Alarmo -> Actions -> yaml editor, I cannot save because it's triggering some errors.

IMO only the entity_id + state is relevant info for the trigger event.
You can easily get all the details you want about the sensors by requesting the state of the entity.
Please check out here: https://www.home-assistant.io/docs/configuration/templating/#states-examples
I'd rather put effort into improving the editor such that it will work with your smart speaker without external scripts.

Ok. In that case, you can close this FR.
For whoever's interested, this is the script I use to ring a siren + announce which sensor triggered the alarm:
alias: Alarm Siren
sequence:
  - service: media_player.play_media
    data:
      media_content_type: sound
      media_content_id: amzn_sfx_scifi_alarm_04
      entity_id: media_player.echo_downstairs
    entity_id: media_player.echo_downstairs
  - service: notify.alexa_media_downstairs
    data:
      title: Intruder Alert!
      message: >
        Intruder Alert!
        {% for open_sensor in state_attr("alarm_control_panel.alarmo", "open_sensors").keys() |list %}
          at {{ state_attr(open_sensor, 'friendly_name') }}
        {% endfor %}
      data:
        method: all
        type: announce
      target:
        - media_player.echo_downstairs
mode: single

(it kinda assumes that usually, only 1 sensor will trigger the alarm. In the case of 2 sensors it will say 'Intruder alert at sensor 1 at sensor 2')

Just to add: Love your custom component!  Keep up the great work


update home link in lode_runner_2020.md

Hi,
Is there a process to identify possible broken or redirected links globally?
Regards,
Patrice

..Is there a process to identify possible broken or redirected links globally? ..

Hi Patrice, thanks for the update. Yes, there is such a process, i.e. there is a script that runs over all links, makes a http request and saves all those where the result of the answer is not success. Then I manually check them all and fix them as good as I can. I do this approximately once per year and have to fix around 5% of all links once per year. Recently I was running the script and was still fixing links (didn't yet get to lode runner).
For code see: https://github.com/Trilarion/opensourcegames/blob/8dbe065781e498d8f424a0ef0b50b62450a30596/code/maintenance_entries.py#L300


arm64: fix compile error in arm64

Summary
arm64: fix compile error in arm64
/home/mi/ssd/vela-trunk/nuttx/include/string.h:192:36: error: inlining failed in call to 'always_inline' 'memcpy': target specific option mismatch
192 | fortify_function(memcpy) FAR void *memcpy(FAR void *dest,
|                                    ^~~~~~
This was introduced by:
https://github.com/apache/nuttx/pull/12049
Impact
CI
Testing
CI

[Experimental Bot, please feedback here]
This PR appears to partially meet the NuttX requirements, but is missing crucial information.
Here's a breakdown:
Strengths:

Summary: Identifies the problem (compile error on arm64) and links a related PR. This helps establish context.

Weaknesses:

Summary:  Lacks a clear explanation of how the fix works. What was changed in the code to address the error? Simply stating "fix compile error" is insufficient.  What functional part of the code is affected?
Impact:  Saying "CI" is too vague.  While CI failures indicate a problem, they don't describe the impact of the change.  Address all the impact points explicitly (even if the answer is NO).  Does this fix affect any users? Does it change the build process beyond fixing the error? Does it affect any specific hardware or drivers? Does it have security implications? Does it impact compatibility?
Testing:  "CI" is not acceptable as testing logs.  Provide actual build logs or test output, even if it's just a successful compilation.  Specify the host system used for building and the target platform. "CI" doesn't tell us which CI environment and configuration were used.

To improve this PR:

Elaborate on the fix: Explain the code changes implemented to resolve the compile error. What specific lines were modified, and what is the logic behind the changes?

Detailed Impact Assessment:  Address all impact points individually, even if they are not applicable (mark them as "NO").  This demonstrates thorough consideration.  For example:

Impact on user: NO
Impact on build: YES (Fixes a compile error on arm64 introduced by PR #12049)
Impact on hardware: NO
... (and so on)

Provide real testing logs: Include relevant snippets from build logs or test output, both before and after the change.  Show that the code now compiles successfully and that the intended behavior is preserved.  Be specific about the build host and target:

Build Host(s):  Linux (Ubuntu 22.04), x86_64, GCC 11.3.0
Target(s):  QEMU-AARCH64 (virt board config)
Testing logs before change: (Show the compile error)
Testing logs after change: (Show successful compilation)

By addressing these points, the PR will be much more informative and easier to review, increasing the likelihood of a swift and positive outcome.


seems it does not work

Can you provide more info please?

it's fine now for i forget to set up defaultProfile. So request to close this issue


Migration engine leaves dead code

Running the migration engine over the logging package produces the following code:
set level(Level? value) {
  if (hierarchicalLoggingEnabled && parent != null) {
    _level = value;
  } else {
    /* if (parent != null) {
      */ throw new UnsupportedError(
        'Please set "hierarchicalLoggingEnabled" to true if you want to '
            'change the level on a non-root logger.'); /*
    } */
    _rootLevel = value;
  }
}

The if statement is deleted because the field parent is marked as being non-nullable. However, because the body of the if ends with a throw statement, the statement following the if is now dead code which ought to also be removed.

@stereotype441

I think I have enough information to know what needs to be done here:

Add logic to the EdgeBuilder to record whether the code following an if statement is dead (by consulting flow analysis).
Add logic to the FixBuilder to check whether the code following an if statement will be dead after migration (by consulting flow analysis).
Add logic to the FixBuilder to recognize that if the code following an if statement was not dead prior to migration, and is dead now, then the code following the if should be deleted.

This all depends on getting the FixBuilder to work, which is the subject of #38472.

This has been obsoleted by the need to keep "dead" code in place for weak checking.


Use fabric instead of paramiko to SSH connections

Fabric is a python module to handle SSH connections. It can handle parallel processing as well as asking for passwords in the middle of scripts(though not both at the same time).
Moving to this model made the code easier for me to digest, as well as made the inventory configuration file a little easier to understand. Instead of trying all credentials against a target, the username can be specified for the targets and the credentials for that username can be specified in the credentials line. However, if you don't want to include credentials in a file, you can leave that line blank, change the run_parallel line to False, and Fabric will ask for credentials as it needs them(login passwords and sudo passwords). If ssh keys and sudoers is setup with NOPASSWD properly, you don't need to change run_parallel to False. This was the main impetus for me to make these changes as I wanted to test out this script, but didn't want to create a service account and didn't want to put my password in the inventory configuration file.
I also updated the README.md file with the full sudoers configuration thats needed to allow the script to work.

Hi agbrook, thanks for submitting this. We are in process of testing this against multiple use cases before we look into merging this.

I'm not sure this is necessary or even wise at this point. I also don't want to go through and fix the conflicts. Closing this request.


Roll Flutter Engine from f721db653dd1 to<PHONE_NUMBER>dc (1 revision)

https://github.com/flutter/engine/compare/f721db653dd1...8903904389dc
2022-11-01<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from Y30GJYiorAEkSGP_l... to HIyR3VT4K1bz5xMC_... (flutter/engine#37189)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from Y30GJYiorAEk to HIyR3VT4K1bz
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


How to have keyboard show up when view loads

I looked at #211 , but this solution animates the keyboard popping up after the view is done loading.  If I try putting [self.inputToolbar.contentView.textView becomeFirstResponder]; in viewWillAppear or viewDidLoad, they keyboard will be over the textview because the textview never repositioned itself above the keyboard

Any word on this feature request? I'd love to have the keyboard up when the view loads.

This worked for me once I called it from viewDidAppear()

Fixed by 752fd38aa8b899cbe2e21b6595de58920977bfc2