Add OAuth to the swipe template

I work in an organization where story maps are often developed in an intranet environment. It seems most other story map templates have OAuth 2.0 authentication so that we can just register an app and then place the registration key in the index.html file, which allows our intranet environment to communicate with AGOL. From what I have been told by Esri tech support, authentication is not included in the swipe/spyglass template. Can you add that?
Thanks,
Mark

Hey Mark,
Yes, I just updated the repo to include support for using OAuth.

Wow Mark, that was fast! You're awesome - thanks for the quick turnaround!


in_http: Verify Authroization token on HTTP headers

Signed-off-by: Hiroshi Hatake<EMAIL_ADDRESS>
Which issue(s) this PR fixes:
Fixes https://github.com/fluent/fluentd/issues/3193
What this PR does / why we need it:
in_http plugins does not provide Authorization header verification.
This PR adds Authorization headers handling in in_http plugin.
And this logic can be handle not only basic authentication but also other types of authentications.
ref: https://developer.mozilla.org/ja/docs/Web/HTTP/Headers/Authorization
Docs Changes:
Related doc PR is: https://github.com/fluent/fluentd-docs-gitbook/pull/382
Release Note:
Same as title.

Using a fixed Authentication header is almost nonsense, it seems that you need to learn the basis and purpose of authentication.
I think implementing basic auth and using it with TLS is enough for current Fluentd. In it, multi-user should be acceptable.
Implementation for it will be completely different from this patch, so I close this.

Hey @ashie while this may not be the proper approach, I would ask that you still be respectful in feedback/comments. Please refer to the CNCF code of conduct that we use for the Fluentd project (https://github.com/cncf/foundation/blob/master/code-of-conduct.md)

Sorry, I didn't mean to hurt your feelings.
BTW we did further discussion about it at private chat how to resolve your requirements.

Ah, it would be nice if we had done more discussing why this PR should be rejected.
But now, I didn't hurt for the declined decision. I didn't notice this PR is not fully implemented Digest authentication type and lack of considering like Log4jShell shocks.

So why was this PR denied? Looks like a valid feature to me.

This PR wasn't fully considered for digest authentication. The "fixed" authentication credentials makes vulnerabilities for the attackers. We wouldn't want to introduce such fragile feature.

In addition, it doesn't support multi-users.
If we merge this it once, we need to keep backward compatibility persistently.
But proper implementation will conflict with this, so we will need to add switching mechanism and keep both implementations.
It's quite stressful for us.

Yes these auth features generally need to delegate the handling of the presented credentials to some pluggable handler (basic and digest auth) or an identity provider (bearer tokens). I stumbled onto this when looking for an ingestion endpoint for JSON based logs. I need to secure the http endpoint with some form of key that is unique to each log producer. The keys need to be manageable without restarting the endpoint process. Sort of like Slunk HEC or the thing that the others like logz.io or logdna do. Thanks for clarifying the reason!

For splunk hec we do have https://github.com/calyptia/fluent-plugin-in-http-splunk-hec if that helps


Can we use bacth as block when find markers for each cluster

Hi,
In scran's findMarkers(), users can set batch as the 'block' in the model, so marker identification will not be influenced by batch effect (https://rdrr.io/bioc/scran/man/findMarkers.html, I found this really useful).
Can I do similar things in scanpy? Thanks!
I tried using anndata2ri to convert anndata to SingleCellExperiment, so as to still use scran's findMarker(), but always got this error:
ValueError: Converting pandas "Category" series to R factor is only possible when categories are strings.

I have checked several columns in my adata.obs, but cannot find the cause.
Thanks in advance,
BP

Hi,
Currently using covariates in sc.tl.rank_genes_groups() is not implemented. In the Wilcoxon and t-test versions this is also not possible. However, in logistic regression this could be added. As a coarse approximation you could correct for batch using sc.pp.combat() and then use the corrected data instead of adata.raw (which is the default) to calculate marker genes. However, generally I would not recommend performing statistical analysis on batch-corrected data for other tests.
Regarding your anndata2ri error... you could also check adata.var columns to see if any are categorical, but numeric.

Hi @LuckyMD,
Thank you for your rapid reply!
In mnnCorrect's paper, the authors claimed that ComBat cannot be applied to some single-cell RNA sequencing data, since there are always multiple different cell types in each dataset, how do you think about that?
Maybe, ComBat cannot handle well with the cases where different cell types are influenced by the batch effect in different ways or levels.
I am afraid that batch effects are not accurately corrected, and I am still puzzled about which method may give better results, i.e., calculating marker genes basing on batch-corrected data or including batch as a covariate in the raw data. (Is there any available paper discussing this problem?)
In addition, I will check adata.var soon.
Thanks,
BP

Hi @LuckyMD,
Thank you for your rapid reply!
In mnnCorrect's paper, the authors claimed that ComBat cannot be applied to some single-cell RNA sequencing data, since there are always multiple different cell types in each dataset, how do you think about that?
Maybe, ComBat cannot handle well with the cases where different cell types are influenced by the batch effect in different ways or levels.
I am afraid that batch effects are not accurately corrected, and I am still puzzled about which method may give better results, i.e., calculating marker genes basing on batch-corrected data or including batch as a covariate in the raw data. (Is there any available paper discussing this problem?)
In addition, I will check adata.var soon.
Thanks,
BP

Hi @genecell,
We have a review paper on current best-practices in scRNA-seq analysis which is coming out soon in Molecular Systems Biology that discusses this a bit. The issue with batch correction in scRNA-seq data isn't that batch affects different cell types differently, but rather that if cell type compositions change between batches, then transcriptional differences between the cell types that differ between the batches confound the technical batch effect estimation. So you end up correcting for more than just the technical effect. This means that you can use Combat if the cell type compositions are expected to be similar between batches. Indeed, ComBat is shown to outperform MNN for simple batch correction scenarios (kBet paper).
Inspite of the above argument, the better way to do things is definitely to include batch as a covariate. That way you don't underestimate your background variance. In the case of marker gene detection, this is not quite so problematic as:

It is an easy problem, as cell-type differences tend to be very pronounced so you should always detect a signal even with non-optimal methods.
The p-values you calculate from marker gene detection are inflated anyway and therefore not meaningful.

We discuss the above points in our manuscript. I'm not aware whether using corrected data for differential expression testing is discussed anywhere else though. If you email me, I could forward you a copy of the manuscript, but it should be available in MSB in the next weeks. The issue with inflated p-values is also discussed is a few other places like here.

Hi @LuckyMD,
Thank you for your detailed reply! Your explanation of the issue with batch correction in scRNA-seq data is very straightforward.
In kBET paper, the performance of ComBat in simple batch correction scenarios is impressive. (I have once used kBET, but found it very slow.)
In addition, with your help, I have solved the problem of using scran's findMarkers() function:
tmp_cluster=adata.obs['leiden'].astype(int)

%%R -i tmp_cluster -i adata -o tmp_allMarkers
tmp_allMarkers<-scran::findMarkers(adata,clusters=tmp_cluster,block=adata$batch,direction="up")
tmp_allMarkers<-as.list(tmp_allMarkers)

You could even make that easier, by not passing tmp_cluster at all, but using pData(adata)$leiden directly in the function. But great that it works for you!


Add hpo ingest

To address #48

@justaddcoffee Is this ready for review?

@deepakunni3 yep review away (I promise I'll stop committing to this branch)

@deepakunni3 thanks! Answers a lot of questions that I had, but didn't ask. Will update PR soon

Thanks @deepakunni3 ! All sensible suggestions, should be fixed now, have a look

Thanks @justaddcoffee. Looks good! 👍

thanks @cmungall ! Just updated this with a nano-PR


[BUG] Presets is incorrectly spelled in the Plugin Configurator section of the... Config

Description
Presests, should be Presets
Reproduction
Options > Plugin Config > Plugin Configurator > Configure > Look up > "Presests"
Installed plugins

Plugin Configurator
ultrapain, angry, style editor although all of these are irrelevant

Extra

Since it is a visual bug will release it with the next update but will not make a specific one for this alone

fair enoug


Crash in - (void)updateBindings:(NSArray *)bindingPayload

When receiving list of bindings updateBindings is called. It loops through json objects and creates new collection of  MPEventBinding instances. It is possible that this
MPEventBinding *binding = [MPEventBinding bindingWithJSONObject:bindingInfo];
results in nil so application crashes when trying to add that object to collection.
In our case we just renamed one view controller which was table view delegate, so translation from json was not possible because class was not found.
I am not sure if this should crash as it is now or we should just ignore that binding?

Merged a fix for this. It will be 2.9.4

Cool, thanks!


regressionAdd spark to read doris predicate pushdown case

Proposed changes
Issue Number: close #xxx
Add spark to read doris predicate pushdown case

run buildall


TagHelpers attribute targeting - part 3

Issue - #2195
@NTaylorMullen @dougbu

:shipit:

:shipit: after quick fixes and conversation w/ @DamianEdwards


skip next ui workaround - client

-client check on interaction for wesker's desk, leon's desk and press room drawer
-add missing locations related to hiding place film, allowing them to be randomized
-reworks existing locations related to hiding place film, allowing them to be randomized
-rookie's table is now able to be randomized
works on my side, but my testing was done on a older versions of the game, might want to double check at least one of those places (rookie's table is the easiest one)

These changes look straightforward too :+1:
I'll need to test this along with the other PR when I get a chance, my testing notes are here: https://github.com/FuzzyGamesOn/RE2R_AP_World/pull/25#issuecomment-2442401113


Use CSS will-change judiciously for performance

See http://dev.opera.com/articles/css-will-change-property/
I may borrow terminology for 0.2's performance hints (willChangeOpacity/willTransform?).

These should be the preferred flag methods for this in 0.2.


feat: added send icon

ADO Story or GitHub Issue Link
https://dev.azure.com/Kyndryl/Shidoka - Bridge Design System/_workitems/edit/1939476
Figma Link
https://www.figma.com/design/ZNudJzPCnqRpzUEnDatcMb/Shidoka-Icon-Library?node-id=557-917&node-type=section&m=dev
Notes

Added send icon, Monochrome, category functional

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


SetSync don't work

The code run like
Step 1 -> Step 3 -> Step 2
I need to know the TypeArq content after reading the file, ie synchronous manner.
However, the contents of TypeArq return anything.
The Code:
var TypeArq = ""
alert("Step 1");
FileReaderJS.setSync(true);
FileReaderJS.setupInput(document.getElementById('input'), {
readAsDefault: "Text",
on: {
load: function(e, file) {
TypeArq = e.target.result.substring(1,8);
console.log("Funcionou--->" + e.target.result.substring(1,8));
alert("Step 2");
}
}
});
alert("Step 3");
alert(TypeArq)

It's synchronous once the user begins the input (not on initialization).  So there is an async gap between the code that sets up the reader and the user actually selecting a file.  You can read more about this FileReaderSync object on MDN.
In your case, you could move 'step 3' and any logic within it into the load event and things would execute in the order you want.


Fix java non-vectorized path

This PR includes various improvements and fixes to the java implementation.
It includes several fix issues in the non-vectorized path, bringing it back up to speed with the vectorized path:

#134
#131
#130

And in includes two general encoding features that were missing:

#132
#127

Additional changes, that don't have corresponding tickets:

Fixed the Delta encoding in the non-vectorized path to support RLE without multiple passes
Make the spotless check run faster (avoids running builds and tests and just does the formatting check)
Fixes a small bug in the vectorized path where the signed boolean was incorrect
Makes the benchmark timer in the encode and decode tools quiet by default and now behind an option
Adds additional error detail when unsupported encodings are encountered at runtime
Comments some unused code
Renames some code to match naming better between the vectorized and non-vectorized path

This is now passing on CI and ready for review. Its a big one, but hopefully is still reviewable. The PR description has a summary to orient the reader.

Here is an overall status report of which paths works for which tiles. A ✔ means that a tile can be encoded and decoded without exceptions.


[REVIEW] init branch-0.6

Signed-off-by: Peixin Li<EMAIL_ADDRESS>initiate branch-0.6 w/ cudf  0.20-SNAPSHOT,

bump up plugin version to 0.6-SNAPSHOT
bump up cudf version to 0.20-SNAPSHOT
updated Doc to use new versions plugin and cudf
removed cudf classifier from pom

and there are still some CUDA_CLASSIFIER configs left under jenkins folder,
this will be cleaned up later after we finish adjusting our pipelines' setup
Please help review, thanks!
NOTE: currently some test cases are still failing
I may just skip CI and merge this one if it looks OK to unblock the following pipelines setup work
actually passed tests w/ latest cudfjni

build

build

build

build

build

the CI platform suffers from some network issue. I will re-trigger later

build

I have seen some discussion in the PR about what version of cuda we are going to support.
That really is a question about what we are going to do for the cudf 0.20 release. Is the plan to try and compile cudf against 11.2 and statically link in the cudf runtime so we can have compatibility with all versions of cudf 11?

That really is a question about what we are going to do for the cudf 0.20 release. Is the plan to try and compile cudf against 11.2 and statically link in the cudf runtime so we can have compatibility with all versions of cudf 11?

That is the plan so far, but as I mentioned earlier, I don't think we can drop the classifier in all cases.  We might be able to drop it in 0.20 since the plan is to only have one classifier (cuda11), but I'd rather keep educating users about the classifier if we have to add it back in for cudf 0.2x that supports CUDA 11 and CUDA 12 and we can't use the same jar for some reason.  In other words, keep the classifier until we know we will never have a classifier again.

I have seen some discussion in the PR about what version of cuda we are going to support.
That really is a question about what we are going to do for the cudf 0.20 release. Is the plan to try and compile cudf against 11.2 and statically link in the cudf runtime so we can have compatibility with all versions of cudf 11?

I have setup the nightly pipeline to build cudfjni against cuda 11.2.2 and use the dynamic link there, I haven't tests in all scenarios but looks like it is compatible w/ cuda 11.0, 11.1 and 11.2

bring all classifiers back to doc

build

build

keep classifier and bring some doc change for CSP back.
Going to merge this one to unblock pipeline setup, we can submit following PRs to update those if require additional changes


Illegal Constructor in Android 4.x

Creating events via a constructor is an Illegal constructor type error in the Android 4.x stock browser.
new Event("focusout") and others are throwing.

Can you post the full polyfill-service url you are using and the browser user-agent string you are seeing this issue on please? Is this issue inside a polyfill or inside application code?

This is most easily reproducible when setting unknown to polyfill and passing an unsupported UA to get all the polyfills (gated). We use a local version like this incase the PolyFill CDN request fails (due to adblocker or any other reason)
But I've also seen it happen on the the latest CDN, here's a CDN link from a Sentry error report with the exact UA that caused it:
https://cdn.polyfill.io/v2/polyfill.min.js?features=default,fetch,performance.now,Symbol,Array.prototype.find,Array.prototype.findIndex,Array.prototype.includes,Promise|always|gated&unknown=polyfill&flags=gated&callback=polyfill&ua=Mozilla/5.0 (Linux; U; Android 4.1.2; fr-fr; GT-I8190 Build/JZO54K) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 [FB_IAB/FB4A;FBAV/<IP_ADDRESS>.72;]
Mozilla/5.0 (Linux; U; Android 4.1.2; fr-fr; GT-I8190 Build/JZO54K) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 [FB_IAB/FB4A;FBAV/<IP_ADDRESS>.72;]

The error is at line 56:2253, an Event is attempted to be contructed new Event("focusin", ...
but the stock Android browser (<=4.4) does not support creating events with a constructor.

The only place we call new Event is inside the CustomEvent polyfill and only if the user-agent does not support document.createEvent.
Could you try loading only customEvent polyfill in that browser?
https://cdn.polyfill.io/v2/polyfill.js?features=CustomEvent&unknown=polyfill&flags=gated&callback=polyfill&ua=Mozilla/5.0 (Linux; U; Android 4.1.2; fr-fr; GT-I8190 Build/JZO54K) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 [FB_IAB/FB4A;FBAV/<IP_ADDRESS>.72;]

Android browser throws an Illegal Constructor error when initiating an object of native Event. The event polyfill is not being applied on Android Browser due to the if (typeof global.Event === 'function') return true; check, which is true.
https://github.com/Financial-Times/polyfill-service/blob/master/polyfills/Event/detect.js#L4
new Event is used in the following polyfills

CustomEvent
Event.focusin
Event.hashchange
XMLHttpRequest

Can we remove the above line from the Event polyfill?


FfiCallbackMetadata::kPageSize should be target::kOSPageSize or similar?

https://github.com/dart-lang/sdk/blob/main/runtime/vm/ffi_callback_metadata.h#L200
We've ended up replicating this logic in other places (we use this thunk/stub trick in a few more places) and copying those constants.  They have little to do with FFI and seem like they belong in some central location?   They appear to represent the minimum page allocation size (rather than target::kPageSize which represents Heap's preferred allocation size).
I'm about to write a patch to move ours to page.h, but maybe they belong in runtime_api.h?  In any case, mostly what I'm looking for is taste from @mraleph or @dcharkes.  Happy to send patches up your way once we've done the move ourselves.  Presumably target::kPageSize also should be renamed to target::kHeapPageSize, since it's specific to the Dart heap, not the target's default allocation size.  This new constant would be target::kOSPageSize or similar?

Right, FfiCallbackMetadata::kPageSize
https://github.com/dart-lang/sdk/blob/bfe68f9ff552e3a11dcc218ee502feeee6299340/runtime/vm/ffi_callback_metadata.h#L205-L216
Could be reused for other things that require a memory block which is at least as large as a page on both host and target.
Moving it to a place where it is reuseable and renaming it sgtm if there's a use for that.

target::kPageSize also should be renamed to target::kHeapPageSize

@rmacnak-google is the one to say something about that.
Maybe @rmacnak-google can also suggest a good name if we move FfiCallbackMetadata::kPageSize to be reusable (as a page-size that is at least as large as host and target).
fyi @liamappelbe

For now I've also just made all our classes just depend on FfiCallbackMetadata::kPageSize, which is fine.  You're welcome to close this if there is no use upstream, thanks.

target::kPageSize also should be renamed to target::kHeapPageSize

No, kHeapPageSize refers to the size of a normal Dart heap chunk. Parts of the GC assume these chunks are also aligned to this value. This value is bigger than the OS page size. The overloading of the term "page" is unfortunate, but common.

I think the real footgun here is that there is a "global" dart::kPageSize (everything is in namespace dart) and then various classes intentionally shadow that kPageSize and end up with confusing (or sometimes wrong) code if they get the wrong size not understanding the shadow.
In any case, we've worked around this by just using FfiCallbackMetadata::kPageSize with our own alias that is named uniquely from kPageSize so there is no risk of getting the wrong one.
We've solved this for us for now, so please feel free to close if not useful to the wider project.

@rmacnak-google is there any actionable item here in terms of moving FfiCallbackMetadata::kPageSize and making a host and target version of it ?


Implement enum serialization and deserialization.

Enums are serialized as strings or arrays. The example shows
how an enum with some values is serialized.
enum MyEnum {
    A, // serialized as "A"
    B(u8), // serialized as ["B", 42]
    C(u8, bool), // serialized as ["C", 43, false]
    D { x: u8, y: u8 }, // serialized as ["D", {"x": 2, "y": 3}]
}

Closes #7

Coverage decreased (-27.1%) to 62.801% when pulling 579f50db98c0d86639fc9f039323af22617a9919 on enums into 3b3bed9e12a69d0d0c33b8936e28354307f82c51 on master.


idea: Quick logout icon

I am wondering, if a Quick logout icon could be placed next to settings Gear. Or closing window is a logout equivalent?

I think that closing windows is the fastest way to logout from app


avoid storing full keys in leafs

We have an application where we store lots of URIs and map them to integer IDs. Since almost all URIs start with the same prefix, we decided to use the ART trie to do this mapping. Unfortunately, I realised that ART still keeps a complete copy of the key in its leaf nodes - wouldn't it be possible to dynamically reconstruct keys by traversing the trie from the root when needed (e.g. for the iteration)? In our case this would safe tremendous amounts of main memory.

I need insert about 1,000,000,000 node, and the size of ART will like B Tree and the height of tree is much more than B Tree.

We have an application where we store lots of URIs and map them to integer IDs. Since almost all URIs start with the same prefix, we decided to use the ART trie to do this mapping. Unfortunately, I realised that ART still keeps a complete copy of the key in its leaf nodes - wouldn't it be possible to dynamically reconstruct keys by traversing the trie from the root when needed (e.g. for the iteration)? In our case this would safe tremendous amounts of main memory.

How many urls do you store and how much memory is used？


feat: Selects Best and Worst GPT Simplification Sentences Using SARI and Calculates Final SARI per Dataset

Implements the selection of the best and worst simplification sentences generated by GPT using the SARI metric.
Creates an file with the best sentences and another with the worst sentences. Also, identifies the most influential source files in the
selection, and calculates the final SARI for museu and porsimplessent dataset with best and worst simplification sentences generated by GPT.

I added the worst calculation and corrected the path. @scalercio


Repo sync for protected CLA branch

The pull request is created from master637483392372824034 to master to fix git push error for protected CLA branch

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


Upgrade jbuilder to dune

Because it will be deprecated in a few days.

Thanks for the reminder! I'll try to take care of it this week.


Link NIH LIVD power tool on ReportStream website for senders

Problem statement
Sender: It can be time-consuming and confusing to use the HHS LIVD table to determine the correct values to enter into my test data.
ReportStream: Senders might not know there's a LIVD power tool available from NIH.
What you need to know

NIH created a LIVD power tool which allows users to a) select a test and then b) the correct device identifier and other corresponding values auto-generate
See [Slack thread] originated by Rick Hawes (https://agilesix.slack.com/archives/C025F5W5Q7L/p1646760171763349)

Acceptance criteria

[ ] Add a reference to the NIH LIVD power tool on ReportStream website

To do

[ ] ...

@drew-usds assigning this new ticket to you just for the time being until we refine.

Open questions:

does this tool cover all tests in CDC's livd table? the NIH tool says "at-home tests"
if just a slice of all tests, can NIH update this tool to cover all tests?
how often does NIH maintain this table?

Other questions:

Do the OTC test info between both lookups match completely?
Does NIH have a page that links to this at all? Is there any other NIH info about this tool? Who created it? (since the URL isn't an NIH one, it has some other powerbi .us domain)

For our AC

Do we add a link underneath our other boilerplate LIVD text? What other explanation do we need to help folks use this?
Do we need a separate LIVID-related callout/section to help with LIVD lookups?

Closing this ticket as NIH tool does not include all devices in CDC"s livd table


tab styling error with name 'button'

Link to reproduction
No response
Describe the Bug
When naming a tab 'button' it get de wrong styling. See screenshot:

To Reproduce
Create a tab named 'button'.
Payload Version
2.0.13
Adapters and Plugins
No response

Hi @silveltman - wow nice catch! This has been fixed and will be in our next release.


action to amend commit message with custom prefix

In some of the unicode-org projects and repos (CLDR & ICU) we require commit messages to start with a specific type of text (project plus Jira ticket number, for cross-linking Jira<->PR). For accepting dependabot changes it would be great if there was an action like @dependabot message prefix my_custom_prefix which used git commit --amend to apply the prefix (and add a space between the prefix and the original message). It could be sticky per repo, for convenience. (We would change it to a different prefix / different Jira ticket number every so often.)
For example, see CLDR & ICU commits:

https://github.com/unicode-org/cldr/commits/master
https://github.com/unicode-org/icu/commits/master

I believe this has been addressed by https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#commit-message

I believe this has been addressed by https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#commit-message

Yes, mostly, I think. It looks like we would need to configure a prefix with our usual pattern and some Jira ticket/issue, and remember to update the prefix with a new Jira ticket/issue each time we publish a release and start work on the next one.
With the prefix, the dependabot commit messages should automatically be right. Without a per-pull-request override command,  we might still need to manually work around undesirable Jira tickets near release time.
Thanks!

  Since the prefix would need to be configured before the commit message is initially written, you'd need to maintain it in your dependabot.yml file and change it when you switch milestones (maybe using a github action that runs on a milestone or release event?)
The only other option I can think of would be to write a github action that runs each time a PR is created by dependabot and calls git commit --amend -m "new message" && git push --force to overwrite the message that dependabot created.   Your github action could use whatever logic you want to determine the proper commit message to use.

@srl295 Yes, this is a known issue (#4652) - @dependabot recreate is a bit of a misnomer.  It should really be called @dependabot force-rebase.  The only difference between recreate and rebase is that rebase fails if there are any additional commits in the branch, while recreate skips that check.
Neither rebase nor recreate actually "recreate" the PR, so the title, labels, etc aren't impacted.  The prefix functionality is only called when the PR is initially created.

Many thanks @mwaddell for chiming in here.
I'm going to close because:

At this point, I think the original request is mostly addressed.
I broke out the idea of clarifying recreate as force-rebase into #6204.
We don't currently have a mechanism for completely rebuilding old PR's with a new config... and it happens rarely enough that I don't see us building that out anytime soon. If it starts being a common user request, then we're happy to re-evaluate.

What's not addressed yet (though we are glad to have dependabot!) is a way to handle that change of targetted ticket and thus commit message, around release time.
I think the reason I thought @dependabot recreate did what I wanted is that the re-analysis sometimes causes a PR to be closed as 'superseded'.  That actually gives the desired behavior.


ObjectWrapper implementation

I need an ObjectWrapper, which can be used to create class lines, like Class and UserError. So I won't need the ClassBuilder, and such stuff.
The core of the problem with those class lines is that we have great cloning and merging functions, but we cannot use them in a different context.
What I need is
var o = {};
var o2 = new ObjectWrapper(o, {
    x: function (){
        this.a = 1;
        this.y();
    },
    y: function (){
        this.b = 2;
    }
});
o2.x();
console.log(o); // {a:1, b:2}

this way I don't have to copy methods on native objects.

it is not possible to implement a thing like this.
the problem that we cannot merge properties from the wrapper and the context and give the context to other objects as reference. we cannot have both and sometimes we need both.
e.g. by cloning and merging Object and Error with meta we'll need a meta property which will be an ObjectWrapper property to avoid writing native objects. after that we'll need to set reference to the Object and Error as superClasses.
hmm if we don't support the superClass stuff, then it can be solved...


Icons in small buttons are too big and misaligned with Clarity v5

Describe the bug
I noticed with latest Clarity Angular (compared to v4) the small buttons with images has changed. The images are larger and misaligned. In v4 there was a style for the images in small buttons fixing this, but this style seems gone in v5.
How to reproduce
A simple small button with an icon. It seems the style for the small icon changed to only support cds-icon:
v4:
.btn-sm:not(.btn-link) clr-icon, .alert-app-level .alert-item .btn:not(.btn-link) clr-icon  {
}
v5:
.btn-sm:not(.btn-link) cds-icon, .alert-app-level .alert-item .btn:not(.btn-link) cds-icon {
}
Expected behavior
Support both cds-icon and clr-icon
Versions
Clarity project:

[ ] Clarity Core
[x] Clarity Angular/UI

Clarity version:

[ ] v3.x
[ ] v4.x
[x] v5.x

Framework:

[x] Angular
[ ] React
[ ] Vue
[ ] Other:

Framework version:
Angular 11

Fixed with #5835. Will be shipped with the next release.


[error] compared path is not set

Original message: Oops, something went wrong while comparing
System Info
Editor version: 1.73.1
Extension version: 0.20.1
OS: darwin 21.6.0
Stack
Error: compared path is not set
at PathContext.get comparedPath [as comparedPath] (/Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/context/path.js:19:19)
at PathContext.getPaths (/Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/context/path.js:32:37)
at Object. (/Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/services/comparer.js:115:67)
at Generator.next ()
at /Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/services/comparer.js:27:71
at new Promise ()
at __awaiter (/Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/services/comparer.js:23:12)
at Object.compareFolders (/Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/services/comparer.js:109:12)
at CompareFoldersProvider. (/Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/providers/foldersCompareProvider.js:107:48)
at Generator.next ()
at /Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/providers/foldersCompareProvider.js:27:71
at new Promise ()
at __awaiter (/Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/providers/foldersCompareProvider.js:23:12)
at CompareFoldersProvider.refresh (/Users/apple/.vscode/extensions/moshfeu.compare-folders-insider-0.22.1/out/providers/foldersCompareProvider.js:105:30)
at s._executeContributedCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:92:111375)
at s.$executeContributedCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:92:112079)
at l._doInvokeHandler (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:102:13680)
at l._invokeHandler (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:102:13362)
at l._receiveRequest (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:102:12132)
at l._receiveOneMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:102:11033)
at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:102:8941
at h.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:145)
at v.deliver (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:2266)
at g.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:1844)
at r.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:70:16515)
at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:118:17104
at h.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:145)
at v.deliver (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:2266)
at g.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:1844)
at r.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:70:16515)
at o._receiveMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:70:21327)
at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:70:18770
at h.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:145)
at v.deliver (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:2266)
at g.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:61:1844)
at g.acceptChunk (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:70:13346)
at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:70:12476
at Socket.i (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:70:24594)
at Socket.emit (node:events:526:28)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at Socket.Readable.push (node:internal/streams/readable:228:10)
at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)

Thank you for the issue 🙏
Can you describe what are the steps you did before you got this error?


Board visibility, posting and file types are not enabled by default

Hi there!
It seems there's a mistake and in board confing (or 'Update' as it's called) these things are not enabled by default. Adding them would save a lot of time and make the process of creating new boards much easier. Also I think there should be some selection of default filetypes like ["image/jpeg","image/png","image/gif","video/webm","audio/webm"] so the user wouldn't have to enter them manually. Hope you'll fix this!

Disabled by default board visibility is correct. Board should not be visible until you intentionally turn it on. The same goes for the file types. It would be nice to add tooltips with examples to the fields in future.

Disabled by default board visibility is correct. Board should not be visible until you intentionally turn it on. The same goes for the file types. It would be nice to add tooltips with examples to the fields in future.


fix warning during doc build

fix #4617

Bug fix
New feature
Improvement (improvement to code, performance, etc)
Test update
Documentation update

Description
$ python -m sphinx -T -E -b html -d _build/doctrees -D language=en . ~/html
Running Sphinx v7.2.6
myst v2.0.0: MdParserConfig(commonmark_only=False, gfm_only=False, enable_extensions=set(), disable_syntax=[], all_links_external=True, url_schemes=('http', 'https', 'mailto', 'ftp'), ref_domains=None, fence_as_directive=set(), number_code_blocks=[], title_to_header=False, heading_anchors=0, heading_slug_func=None, html_meta={}, footnote_transition=True, words_per_minute=200, substitutions={}, linkify_fuzzy_links=True, dmath_allow_labels=True, dmath_allow_space=True, dmath_allow_digits=True, dmath_double_inline=False, update_mathjax=True, mathjax_classes='tex2jax_process|mathjax_process|math|output_area', enable_checkboxes=False, suppress_warnings=[], highlight_code_blocks=True)
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 124 source files that are out of date
updating environment: [new config] 124 added, 0 changed, 0 removed
reading sources... [100%] write_first_app
looking for now-outdated files... none found
pickling environment... done
checking consistency... /Users/theholygrail/hyperledger/fabric/docs/source/build_network.rst: WARNING: document isn't included in any toctree
/Users/theholygrail/hyperledger/fabric/docs/source/github/github.rst: WARNING: document isn't included in any toctree
/Users/theholygrail/hyperledger/fabric/docs/source/msp-identity-validity-rules.rst: WARNING: document isn't included in any toctree
/Users/theholygrail/hyperledger/fabric/docs/source/policies.rst: WARNING: document isn't included in any toctree
/Users/theholygrail/hyperledger/fabric/docs/source/raft_bft_migration.md: WARNING: document isn't included in any toctree
/Users/theholygrail/hyperledger/fabric/docs/source/tutorial/installxcode.md: WARNING: document isn't included in any toctree
done
preparing documents... done
copying assets... copying static files... done
copying extra files... done
done
writing output... [100%] write_first_app
generating indices... genindex done
highlighting module code...
writing additional pages... search done
copying images... [100%] images/AppConceptsOverview.png
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded, 6 warnings.

The HTML pages are in ../../../../html.

Only warnings related to inclusion of document in toctree left

@mergifyio backport release-2.5


Review the workflow for geospatial file cleanup

Workflow attached below.
WorkflowD1&2_v5.drawio (1).pdf

Please comment once you have reviewed the process.

Done

Finished

Done


Ignore unexpected method type

Fixes https://github.com/sbt/zinc/issues/688
There's a long-standing issue about method type warning showing up with the following code:
object X {
  final case class Y(private[X] val i: Int) extends AnyVal
}

To validate this pull request against other sbt modules, please visit this link.

But why does method type shows up here, and is the API information loosing information ?

The error message looks like
[warn] sbt-api: Unhandled type class scala.reflect.internal.Types$MethodType : ($this: example.X.Y)Int

and running scalac -Xprint:typer src/main/scala/example/Hello.scala you get
package example {
  object X extends scala.AnyRef {
    def <init>(): example.X.type = {
      X.super.<init>();
      ()
    };
    final case class Y extends scala.AnyVal with Product with Serializable {
      <synthetic> <stable> <caseaccessor> def i$access$0: Int = Y.this.i;
      <caseaccessor> <paramaccessor> private[this] val i: Int = _;
      <stable> <accessor> <paramaccessor> private[X] def i: Int = Y.this.i;
      def <init>(i: Int): example.X.Y = {
        Y.super.<init>();
        ()
      };
      <synthetic> def copy(i: Int = i): example.X.Y = new Y(i);
      <synthetic> def copy$default$1: Int = Y.this.i;
      override <synthetic> def productPrefix: String = "Y";
      <synthetic> def productArity: Int = 1;
      <synthetic> def productElement(x$1: Int): Any = x$1 match {
        case 0 => Y.this.i$access$0
        case _ => throw new IndexOutOfBoundsException(x$1.toString())
      };
      override <synthetic> def productIterator: Iterator[Any] = scala.runtime.ScalaRunTime.typedProductIterator[Any](Y.this);
      <synthetic> def canEqual(x$1: Any): Boolean = x$1.$isInstanceOf[example.X.Y]();
      override <synthetic> def hashCode(): Int = Y.this.i.hashCode();
      override <synthetic> def equals(x$1: Any): Boolean = x$1 match {
  case (_: example.X.Y) => true
  case _ => false
}.&&({
        <synthetic> val Y$1: example.X.Y = x$1.asInstanceOf[example.X.Y];
        Y.this.i.==(Y$1.i)
      });
      override <synthetic> def toString(): String = scala.runtime.ScalaRunTime._toString(Y.this)
    };
    <synthetic> object Y extends scala.runtime.AbstractFunction1[Int,example.X.Y] with Serializable {
      def <init>(): example.X.Y.type = {
        Y.super.<init>();
        ()
      };
      final override <synthetic> def toString(): String = "Y";
      case <synthetic> def apply(i: Int): example.X.Y = new Y(i);
      case <synthetic> def unapply(x$0: example.X.Y): Option[Int] = if (x$0.==(null))
        scala.None
      else
        Some.apply[Int](x$0.i$access$0);
      <synthetic> private def readResolve(): Object = example.X.Y
    }
  }
}

I haven't dug into the exact code path getting to the MethodType, but I'd guess it happens due to a synthetic methods created with the mix of value class, case class, and the package-private field.
Since the relationship is within a class, from Zinc's perspective we can safely ignore it since nothing is escaping the confines of case class Y.

The $this thing looks like what the extension method phase generate, so -Xprint:typer won't help, normally the API phase should run right after pickler so -Xprint:pickler is the way to go.

Since the relationship is within a class, from Zinc's perspective we can safely ignore it since nothing is escaping the confines of case class Y.

If it's in the public API of the class, it matters to Zinc. If it's not in the public API, then the API extraction phase should not even be looking at it! Otherwise we might ever get worse performance, or overcompilation issues. In any case, I don't think that simply silencing the warning is the way to go.

Yea. I should've included $ scalac -Xprint:extmethods src/main/scala/example/Hello.scala output probably? You get these..
    <synthetic> object Y extends scala.runtime.AbstractFunction1[Int,example.X.Y] with Serializable {
      def <init>(): example.X.Y.type = {
        Y.super.<init>();
        ()
      };
      final override <synthetic> def toString(): String = "Y";
      case <synthetic> def apply(i: Int): example.X.Y = new Y(i);
      case <synthetic> def unapply(x$0: example.X.Y): Option[Int] = if (x$0.==(null))
        scala.None
      else
        Some.apply[Int](x$0.i$access$0);
      <synthetic> private def readResolve(): Object = example.X.Y;
      final <synthetic> <stable> <caseaccessor> def i$access$0$extension($this: example.X.Y): Int = $this.i;
      final <synthetic> def copy$extension($this: example.X.Y)(i: Int): example.X.Y = new Y(i);
      final <synthetic> def copy$default$1$extension($this: example.X.Y): Int = $this.i;
      final <synthetic> def productPrefix$extension($this: example.X.Y): String = "Y";
      final <synthetic> def productArity$extension($this: example.X.Y): Int = 1;
      final <synthetic> def productElement$extension($this: example.X.Y)(x$1: Int): Any = {

The next step would be to add some tracing code to see what path the api extraction phase takes to end up finding a MethodType, even something as simple as running Thread.dumpStack when the warning is printed might help.

Maybe it could be finding this method type while traversing the types of an structural type? @smarter

Yes maybe, but there shouldn't be any structural type here

Closing this since it's been addressed as part of https://github.com/sbt/zinc/pull/874


Azure Pipelines Deployment Group Agent artifact has different icon

[Low Priority]
It looks like the Azure Pipelines Deployment Group Agent artifact (windows-deploymentgroup) has a different icon than the other Pipline Agent-related tasks. Was that done on purpose?

Thanks,
--Neno

Please look at this commit for the changes to the artifactfile.json where we now reference the correct icon.


Feeback Communication - Suggested Enhancement

MIDI feedback back is not supported is it?  The communication is one way, correct?
It would be great if the user could created a set of faders to change channel volumes in a DAW and also have those faders respond to changes made directly in the DAW.
If it's possible, how do I implement?  If not, I would love to the the enhancement.
Thanks and thanks again for adding pitch bend!

I believe that the functionality you describe is more of an OSC type protocol. Midi is usually one way, if I'm not mistaken. So, something like touchOSC might be what you need.
OSC is implemented using webserial in the browser over here https://manicken.github.io/# for an example. This won't help you besides being an example. It doesn't currently have a "Feedback loop" working but if it did it would basically be two way OSC.

MIDI is one way per port, but if TouchMIDI added INPUT ports, the new ports would allow data to flow back to the web apps.  Then when changes were made in the DAW those changes would be reflected in the onscreen faders, buttons, and encoders.


Is the package still being maintained?

Hello,
I am trying to use your package and I can see there are deprecated dependencies. I could help with this. Are you still maintaining this package?
Thanks!

No, this package is unmaintained. Apologies for the confusion. I plan to close all open issues and archive this repo.


Deprecate mace mlp recipes

Summary of Changes
Closes #1972 by adding support for 'mace-mp-0' and adding a deprecated warning for 'mace' in the mlp recipe.
Adding 'mace-mp-0':

Added as a Literal in the arguments for static_job() and relax_job() in core.py, phonon_flow() in phonons.py, and pick_calculator() in _base.py
Added an elif conditional for 'mace-mp-0' in pick_calculator() in _base.py
Added 'mace-mp-0 as a Literal for tests in test_core_recipes.py in mlp_recipes test folder.

Deprecating 'mace':

Added 'import deprecated from monty.dev' in _base.py
Updated pick_calculator() docstring with deprecation warning according to NumPy docstring standard in _base.py
Added mace_warning() with 'deprecated' decorator invoked in pick_calculator() in _base.py

Additional:

Changed 'from ase.calculator.calculator' to 'from ase.calculators.calculator' in _base.py in mlp recipe to match ase documentation and other recipes.

Checklist

[X] I have read the "Guidelines" section of the contributing guide. Don't lie! 😉
[X] My PR is on a custom branch and is not named main.
[X] I have added relevant, comprehensive unit tests.

Can one of the admins verify this patch?

Thank you, @jackpm14! I'm setting this to auto-merge. 👍

Seems like there's a temporary bug with GitHub Actions. I'll wait a bit and try again.


Allow user to select color by series for axischarts

New Pull Request
User can add a color prop to a series which will take priority over colors passed into the chart options.
Fixes #276 https://github.com/apexcharts/apexcharts.js/issues/276
Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

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

Thank you for your contribution.
I have made some more changes as markers and colors in tooltip were not affected.
Here are the changes if you want to take a look - https://github.com/apexcharts/apexcharts.js/commit/d49fc060109d48da032cb269812c1d9028539ce8


Enh/add zendesk key interpolation

Hi @sharonmaybergtailor, I see that you haven't attached any Trello card, let me help you with that...

 ember-cli-zendesk - Enh/add zendesk key interpolation


unable to install Microsoft Remote Dekstop

$ mas signin
$ mas install 715768417
opens the appstore dialog, i enter the password, click 'buy'
returns: Unknown Error.

fixed...had to set AppStore settings free download to save password


Card Spacing: Multilink & Promo

Card Spacing: Multilink & Promo
Corrected spacing for multilink and promo cards

Card
Size

Promo
standard, narrow, wide

Multlink
standard, narrow, wide

Example

mentioned in #637

This is fine, thanks


Rasa always falling back

Rasa version: 2.1.3
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant):
Python version: 3.7.9
Operating system (windows, osx, ...): WIN 10
Issue:
I didn't why my rasa bot always fall back. Intent classification is good but the replying ones is not correct
Error (including full traceback):
This is what I am getting
![Screenshot (19)](https://user-images.githubusercontent.com/61022690/101970110-7e5be780-3c4e-11eb-8ecd-b43b3d8799a5.png)

This was earlier screenshot when it is working fine
![Screenshot (20)](https://user-images.githubusercontent.com/61022690/101970112-8025ab00-3c4e-11eb-9ef5-f3c94ee725db.png)

Command or request that led to error:

Content of configuration file (config.yml) (if relevant):

# Configuration for Rasa NLU.
# https://rasa.com/docs/rasa/nlu/components/
language: en

pipeline:
# # No configuration for the NLU pipeline was provided. The following default pipeline was used to train your model.
# # If you'd like to customize it, uncomment and adjust the pipeline.
# # See https://rasa.com/docs/rasa/tuning-your-model for more information.
#   - name: WhitespaceTokenizer
#   - name: RegexFeaturizer
#   - name: LexicalSyntacticFeaturizer
#   - name: CountVectorsFeaturizer
#   - name: CountVectorsFeaturizer
#     analyzer: char_wb
#     min_ngram: 1
#     max_ngram: 4
#   - name: DIETClassifier
#     epochs: 100
#   - name: EntitySynonymMapper
#   - name: ResponseSelector
#     epochs: 100
#   - name: FallbackClassifier
#     threshold: 0.3
#     ambiguity_threshold: 0.1

# Configuration for Rasa Core.
# https://rasa.com/docs/rasa/core/policies/
policies:
# # No configuration for policies was provided. The following default policies were used to train your model.
# # If you'd like to customize them, uncomment and adjust the policies.
# # See https://rasa.com/docs/rasa/policies for more information.
  - name: MemoizationPolicy
#   - name: TEDPolicy
#     max_history: 5
#     epochs: 100
  - name: RulePolicy

Content of domain file (domain.yml) (if relevant):

session_config:
  session_expiration_time: 60
  carry_over_slots_to_new_session: true
intents:
- greet
- what_is_supported
- eligibility_criteria
- goodbye
- bot_challenge
- how_to_apply_supported
- fetch_can
entities:
- supported
- can_number
- email
- mobile
- name
slots:
  can_number:
    type: text
    influence_conversation: false
  email:
    type: text
    influence_conversation: false
  mobile:
    type: text
    influence_conversation: false
  name:
    type: text
    influence_conversation: false
  supported:
    type: text
    influence_conversation: false
responses:
  utter_greet:
  - text: Hey! How are you?
  utter_ask_can_number:
  - text: Enter can bro
  utter_default:
  - text: Falled back
actions:
- action_what_is_supported
- action_eligibility
- action_ask_can_number
- action_ask_name
- action_ask_mobile
- action_ask_email
- action_apply_supported
- action_fetch_can
- form_fetch_can
forms:
  form_fetch_can:
    can_number:
    - type: from_text
    email:
    - type: from_text
    mobile:
    - type: from_text
    name:
    - type: from_text

version: "2.0"

stories:

- story: stories for what is supported
  steps:
  - intent: what_is_supported
  - action: action_what_is_supported

- story: story for eligibility criteria
  steps:
  - intent: eligibility_criteria
  - action: action_eligibility

- story: story for applying
  steps:
  - intent: how_to_apply_supported
  - action: action_apply_supported

- story: fetching can
  steps:
  - intent: fetch_can
  - action: utter_ask_can_number
  - action: form_fetch_can
  - active_loop: form_fetch_can

debug message:
Your input ->  what is income certificate
2020-12-12 09:21:56 DEBUG    rasa.core.lock_store  - Issuing ticket for conversation 'fd95b907d632406e860e44b1d917e1dd'.
2020-12-12 09:21:56 DEBUG    rasa.core.lock_store  - Acquiring lock for conversation 'fd95b907d632406e860e44b1d917e1dd'.
2020-12-12 09:21:56 DEBUG    rasa.core.lock_store  - Acquired lock for conversation 'fd95b907d632406e860e44b1d917e1dd'.
2020-12-12 09:21:56 DEBUG    rasa.core.tracker_store  - Could not find tracker for conversation ID 'fd95b907d632406e860e44b1d917e1dd'.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Starting a new session for conversation ID 'fd95b907d632406e860e44b1d917e1dd'.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Policy prediction ended with events '[]'.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Action 'action_session_start' ended with events '[<rasa.shared.core.events.SessionStarted object at 0x000001B49DBF6DC8>, <rasa.shared.core.events.ActionExecuted object at 0x000001B359AEB608>]'.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Current slot values:
can_number: None
email: None
mobile: None
name: None
supported: None
requested_slot: None
2020-12-12 09:21:56 DEBUG    rasa.nlu.classifiers.diet_classifier  - There is no trained model for 'ResponseSelector': The component is either not trained or didn't receive enough training data.
2020-12-12 09:21:56 DEBUG    rasa.nlu.selectors.response_selector  - Adding following selector key to message property: default
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Received user message 'what is income certificate' with intent '{'id': -7096267651852178878, 'name': 'what_is_supported', 'confidence': 0.9999905824661255}' and entities '[{'entity': 'supported', 'start': 8, 'end': 14, 'confidence_entity': 0.9511626958847046, 'value': 'income', 'extractor': 'DIETClassifier'}]'
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Current slot values:
can_number: None
email: None
mobile: None
name: None
supported: income
requested_slot: None
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Logged UserUtterance - tracker now has 5 events.
2020-12-12 09:21:56 DEBUG    rasa.core.policies.memoization  - Current tracker state:
[state 1] user intent: what_is_supported | user entities: ('supported',) | previous action name: action_listen
2020-12-12 09:21:56 DEBUG    rasa.core.policies.memoization  - There is no memorised next action
2020-12-12 09:21:56 DEBUG    rasa.core.policies.rule_policy  - Current tracker state:
[state 1] user intent: what_is_supported | user entities: ('supported',) | previous action name: action_listen
2020-12-12 09:21:56 DEBUG    rasa.core.policies.rule_policy  - There is no applicable rule.
2020-12-12 09:21:56 DEBUG    rasa.core.policies.ensemble  - Predicted next action using policy_1_RulePolicy.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Predicted next action 'action_default_fallback' with confidence 0.30.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Policy prediction ended with events '[]'.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Action 'action_default_fallback' ended with events '[BotUttered('Falled back', {"elements": null, "quick_replies": null, "buttons": null, "attachment": null, "image": null, "custom": null}, {"template_name": "utter_default"},<PHONE_NUMBER>.4180608), <rasa.shared.core.events.UserUtteranceReverted object at 0x000001B345C6EB48>]'.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Current slot values:
can_number: None
email: None
mobile: None
name: None
supported: None
requested_slot: None
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Predicted next action 'action_listen' with confidence 1.00.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Policy prediction ended with events '[]'.
2020-12-12 09:21:56 DEBUG    rasa.core.processor  - Action 'action_listen' ended with events '[]'.
2020-12-12 09:21:56 DEBUG    rasa.core.lock_store  - Deleted lock for conversation 'fd95b907d632406e860e44b1d917e1dd'.
Please help me asap I'm in a hurry

You should either add more stories or in Rasa V2 you can add it as a rule.
On Sat, 12 Dec, 2020, 7:51 am Boyinapalli Sandeep Dora, <
<EMAIL_ADDRESS>wrote:

Rasa version: 2.1.3
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant):
Python version: 3.7.9
Operating system (windows, osx, ...): WIN 10
Issue:
I didn't why my rasa bot always fall back. Intent classification is good
but the replying ones is not correct
Error (including full traceback):
This is what I am getting

This was earlier screenshot when it is working fine

Command or request that led to error:
Content of configuration file (config.yml) (if relevant):
Configuration for Rasa NLU.# https://rasa.com/docs/rasa/nlu/components/language: en
pipeline:# # No configuration for the NLU pipeline was provided. The following default pipeline was used to train your model.# # If you'd like to customize it, uncomment and adjust the pipeline.# # See https://rasa.com/docs/rasa/tuning-your-model for more information.#   - name: WhitespaceTokenizer#   - name: RegexFeaturizer#   - name: LexicalSyntacticFeaturizer#   - name: CountVectorsFeaturizer#   - name: CountVectorsFeaturizer#     analyzer: char_wb#     min_ngram: 1#     max_ngram: 4#   - name: DIETClassifier#     epochs: 100#   - name: EntitySynonymMapper#   - name: ResponseSelector#     epochs: 100#   - name: FallbackClassifier#     threshold: 0.3#     ambiguity_threshold: 0.1
Configuration for Rasa Core.# https://rasa.com/docs/rasa/core/policies/policies:# # No configuration for policies was provided. The following default policies were used to train your model.# # If you'd like to customize them, uncomment and adjust the policies.# # See https://rasa.com/docs/rasa/policies for more information.

name: MemoizationPolicy#   - name: TEDPolicy#     max_history: 5#     epochs: 100
name: RulePolicy

Content of domain file (domain.yml) (if relevant):
session_config:
session_expiration_time: 60
carry_over_slots_to_new_session: trueintents:

greet
what_is_supported
eligibility_criteria
goodbye
bot_challenge
how_to_apply_supported
fetch_canentities:
supported
can_number
email
mobile
nameslots:
can_number:
type: text
influence_conversation: false
email:
type: text
influence_conversation: false
mobile:
type: text
influence_conversation: false
name:
type: text
influence_conversation: false
supported:
type: text
influence_conversation: falseresponses:
utter_greet:

text: Hey! How are you?
utter_ask_can_number:
text: Enter can bro
utter_default:
text: Falled backactions:

action_what_is_supported
action_eligibility
action_ask_can_number
action_ask_name
action_ask_mobile
action_ask_email
action_apply_supported
action_fetch_can
form_fetch_canforms:
form_fetch_can:
can_number:

type: from_text
email:
type: from_text
mobile:
type: from_text
name:
type: from_text

version: "2.0"
stories:

story: stories for what is supported
steps:

intent: what_is_supported
action: action_what_is_supported

story: story for eligibility criteria
steps:

intent: eligibility_criteria
action: action_eligibility

story: story for applying
steps:

intent: how_to_apply_supported
action: action_apply_supported

story: fetching can
steps:

intent: fetch_can
action: utter_ask_can_number
action: form_fetch_can
active_loop: form_fetch_can

Please help me asap I'm in a hurry
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/RasaHQ/rasa/issues/7531, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIE7VUQM6YHQXHDDITZGELLSULHR7ANCNFSM4UXSJGVQ
.

Thanks for the issue, @melindaloubser1 will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

Hi @LEAGUEDORA I don't think this is a bug, I'd recommend posting your question on the forum with the screenshots that aren't displaying here.

Hey @LEAGUEDORA, I'm not 100% sure about the details of the MemoizationPolicy but I think that the story you have in your training data does not exactly match the story you have in Rasa X because of the entity supported
If you look at the log:
2020-12-12 09:21:56 DEBUG rasa.core.policies.memoization - Current tracker state:
[state 1] user intent: what_is_supported | user entities: ('supported',) | previous action name: action_listen
2020-12-12 09:21:56 DEBUG rasa.core.policies.memoization - There is no memorised next action
You can see that the supported entity is in the tracker state.
So, you have a few options:

Use the TED Policy, it should be able to handle that
Add a story like this for the Memoization Policy to work:

- story: stories for what is supported
  steps:
  - intent: what_is_supported
    entities:
    - supported: xyz
  - action: action_what_is_supported

Set use_entities to [] in your domain file for the what_is_supported intent (you may or may not want that depending if the behavior should be different if the entity is not there):

intents:
- ...
- what_is_supported:
  use_entities: []

Use rules

I would recommend using the TED Policy because the Memoization Policy and Rule Policy won't generalize.

Closing as this is not a bug.

Closing as this is not a bug.

I get a similar error while trying to implement Two Stage Fallback. Can someone please guide on how to resolve this?
Error -
sh-4.2$ rasa train
/home/ec2-user/anaconda3/envs/JupyterSystemEnv/lib/python3.6/site-packages/rasa/shared/nlu/training_data/formats/markdown.py:56: FutureWarning: NLU data in Markdown format is deprecated and will be removed in Rasa Open Source 3.0.0. Please convert your Markdown NLU data to the new YAML training data format.
docs=DOCS_URL_MIGRATION_GUIDE_MD_DEPRECATION,
2021-08-16 09:39:58 INFO     rasa.model  - Data (core-config) for Core model section changed.
2021-08-16 09:39:58 INFO     rasa.model  - Data (nlu-config) for NLU model section changed.
2021-08-16 09:39:58 INFO     rasa.model  - Data (nlg) for NLG responses section changed.
Training NLU model...
InvalidConfigException: The pipeline configuration contains errors. The component 'FallbackClassifier' requires 'IntentClassifier' to be placed before it in the pipeline. Please add the required components to the pipeline.
config.yml file -
Configuration for Rasa NLU.
https://rasa.com/docs/rasa/nlu/components/
language: en
pipeline:
other components

name: FallbackClassifier
threshold: 0.7

policies:

name: RulePolicy

Hi @AneeshaaSC , please post your question on https://forum.rasa.com/, as Github is used for bug reports & feature requests, not general usage questions.


Support frameworks in source paths

This adds support for users passing pre-compiled frameworks in as a
source file of a target, and correctly adding it to the copy frameworks
build phase. Previously it would be added to the copy resources build
phase.

This would always embed those frameworks. Is that ok?

Yea I think that's safe since you still have to explicitly add them to your sources paths.
--
Keith Smiley

On May 16, 2018, at 18:43, Yonas Kolb<EMAIL_ADDRESS>wrote:
This would always embed those frameworks. Is that ok?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok. I guess for some this may be a breaking change, if they were manually embedding the framework via dependencies before. Now it might be embedded twice.
I want to make some framework embedding changes anyway though

I think anyone who's currently adding a framework to a source path is actually accidentally bloating their binary size for no reason. Just because they have it as a dependency doesn't mean it'll be in the sources right?

@yonaskolb so do you think we're good to merge this?

Yeah, it's only people who accidentally had frameworks in their sources (which was bloating their binary as you say) and also added that explicit framework path as a dependency. I don't think anyone would do that however.
I think this is good to merge

Thanks!
--
Keith Smiley

On May 23, 2018, at 23:26, Yonas Kolb<EMAIL_ADDRESS>wrote:
Yeah, it's only people who accidentally had frameworks in their sources (which was bloating their binary as you say) and also added that explicit framework path as a dependency. I don't think anyone would do that however.
I think this is good to merge
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Added a gemfile and installation instructions

Based on #138 but I think I did the Wrong Thing so I don't think I can update that pull request further :/
This one removes the excess  spacing.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.


Update LeanIX connector module name, Package.md and Ballerina.toml in slalpha5

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

$title
Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation github4.tests

Unit github4.tests

Code coverage information

Integration github4.tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

There is an issue after renaming the module in this PR. Hence closing it.


MXR for PMPs, not just paging?

MXR is currently defined to affect only paging.  I think we need to define MXR to affect PMPs, not just paging.  If a PMP marks a region is U-mode execute-only, it is currently impossible to use the MPRV mechanism alone to emulate that instruction.

Note this would make M-mode X-only PMPs effectively useless (except on M-only implementations, where the MXR bit does not exist).

My thought earlier was that MXR would be honored only when MPRV was in effect (ideally, R-only pages would fault when accessed under MXR+MPRV)

That makes it less likely for software to make MXR-related bugs, but doesn't close the M-mode X-only hole (as you can set MPRV=1, MXR=1, MPP=M).

Plan is to leave it as defined (only affects paging, not PMPs), and see what happens.


Improve accuracy of cupy.around

Closes https://github.com/cupy/cupy/issues/3532
This PR improves the accuracy of cupy.around for complex arguments a little.
import cupy as cp
import numpy as np

print(cp.around(0.1234567,decimals=4))
print(np.around(0.1234567,decimals=4))

print(cp.around(0.1234567+0.1234567j,decimals=4))
print(np.around(0.1234567+0.1234567j,decimals=4))

Output (current implementation):
0.1235
0.1235
(0.12350000000000001+0.12350000000000001j)
(0.1235+0.1235j)

Output (this PR):
0.1235
0.1235
(0.1235+0.1235j)
(0.1235+0.1235j)

Jenkins, test this please.

Jenkins CI test (for commit 0c750414a6080cde095fbeafd2c522fb5eb0e43c, target branch master) succeeded!

LGTM.


Add metrics to the collector

This adds an in-process metrics server using the prometheus exporter
gem and records an error metric each time an exception is caught
in the collector loop.

@carbonin pls review


[v1.14] Add generated files for enterprise v3.5.2

Description
Missed this in the previous PR #1244

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[x] Milestone set according to targeted release.
[x] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

/merge-when-ready delete-branch

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and delete the branch after I've merged it.

I'm sorry but I failed delete the branch after merging the pull request.


Added flytectl in end2end

TL;DR

Replace kind with flytectl sandbox
Run test against latest release

Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
fix: flyteorg/flyte#1474
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

Created a clean pr https://github.com/flyteorg/flyteadmin/pull/293


Upgrade FS-UAE to v2.6.2

Thank you for the contribution. It was merged directly as 7466228ba55e31f2dbc56fb4fbdf85701d7b1b54 to keep commit history cleaner. Your contribution is still credited to you.


Acornfile builds actually uses docker credentials

From user slack:

I pushed images to ACR and logged into it through Acorn. When I run an Acornfile that pulls images from ACR, I see the below error -

[+] Building 0.5s (3/3) FINISHED
 => [internal] load build definition from acorn-dockerfile-786940309          0.1s
 => => transferring dockerfile: 95B                                           0.1s
 => [internal] load .dockerignore                                             0.1s
 => => transferring context: 2B                                               0.0s
 => ERROR [internal] load metadata for acornreg.azurecr.io/comic-backend:v1   0.3s
------
 > [internal] load metadata for acornreg.azurecr.io/comic-backend:v1:
------
Error: failed to solve: failed to fetch anonymous token: unexpected status: 401 Unauthorized

@ibuildthecloud:

Okay, there’s a crappy issue right now. Acornfile builds actually uses docker credentials right now. We will fix this. So if you do “docker login” it should work.

Possibly related - https://github.com/acorn-io/acorn/issues/479

Should be addressed. We moved all aspects of the build server side. Will only use the credentials you log into acorn with


[FLINK-1391] Add support for using Avro-POJOs and Avro types with Kryo

With this change, users can use POJOs generated from Avro Schemas with Flink.
Either the entire POJO as a GenericType or with the POJO serializer.
I also added support for using GenericData.Record, which is a container that checks the types using a schema. Its extremely inefficient to use that. I guess the only realistic usecase for that is local prototyping.

Looks like a good fix to me. One comment/question inline, otherwise good to merge.

I will make this change part of a new pull request for https://issues.apache.org/jira/browse/FLINK-1417.


Updated dependencies for less install confusion

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #xyz

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (minor / major / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

Other information:

Pull Request Test Coverage Report for Build 1464

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.986%

Totals

Change from base Build 1460:
0.0%

Covered Lines:
1726

Relevant Lines:
1897

💛  - Coveralls


BNT-3: Sample App - ICRC-1 Compliant Payment Flow

Sample App: ICRC-1 Compliant Payment Flow
Overview

Status: Open
Project Type:  Multiple - Multiple applicants can get selected to work on the tasks and get paid.
Time Commitment: Weeks
Experience Level: Intermediate
Size: USD 1'000 in ICP (at time of distribution)

Description
One of the advantages to deploy a service on a blockchain platform is to be able to receive payments without the usage of a 3rd party service provider which can be a huge cost factor. In this bounty, you'll implement a sample application that showcases the implementation of the ICRC-1 payment flow to buy some digital good.
The base ICRC-1 standard supports the client-orchestrated transfer/notify flow, i.e. the client (payer) transfers the token to the service-designated subaccount and notifies the service (payee) about the transfer.
High-level flow diagram

Notes

The client would utilize agent-js to perform (transfer and notify) calls.
The invoice and its relation to a subaccount will probably need to be standardized at some point, allowing for different compatible payer and payee implementations. We hope that this implementation will inform a potential standardization.

Acceptance Criteria

Interesting and sensible use case
Clean and well-structured code
Unit and E2E tests
Documentation
MIT or Apache-2.0 License
PR to samples at https://github.com/dfinity/portal

Further Information
The eventual goal is to make it as easy as possible for developers to integrate a payment flow into their applications. Hence, we see the development of sample applications as a first step to implementing ready-to-use client and canister libraries which could be funded by a follow-up bounty or grant.
The ICRC-1 token standard is in its early days and many details and extensions have not been fully fleshed out. It would be great if you'd provide your implementer's feedback to the Ledger & Tokenization Working Group.
How to apply?
Add a comment to this issue or respond to the forum thread. Please provide some background on your experience and give an outline of your project plan.
References

Agent-js repository
JS/TS client libraries
ICRC-1 specification

@developerfred is taking on this bounty

@domwoe I'm going to build with react and typescript, I believe that this reduces the learning curve for new Dapps developers.

Do you already know what language you'll be using for the canister (Service canister)? Motoko or Rust?

@developerfred Just noticed that I missed the "confirm payment" arrow after "show invoice" due to removing a part of the flow. I'll update the flow diagram tomorrow.

@developerfred any updates?

@domwoe  https://github.com/developerfred/icrc-one-payment-flow

Completed, see https://forum.dfinity.org/t/dfinity-bounty-3-sample-app-icrc-1-compliant-payment-flow/15508

Thanks for letting me know, I'll update the posting with the rest of the
features after this weekend.
Have a good weekend,
Ashton Engberg
On Fri, Jul 28, 2023 at 4:24 AM Dominic Wörner @.***>
wrote:

Completed, see
https://forum.dfinity.org/t/dfinity-bounty-3-sample-app-icrc-1-compliant-payment-flow/15508
—
Reply to this email directly, view it on GitHub
https://github.com/dfinity/grant-rfps/issues/7#issuecomment-1655263082,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZT4U43US5IT3KUCHEP56TXSNZLPANCNFSM6AAAAAAQQDITGA
.
You are receiving this because you commented.Message ID:
@.***>


Parse multiple URLs at once

i.e. Let the user do wcag whatever.com anotherwebsite.com foo.com.
I'm not even sure what the output would look like.

I prefer this module to check one URL at the time.
It is quite trivial to create another module for looping and depend on this for the actual checking. Here's one example https://github.com/zrrrzzt/webquality-dashboard
Small focused modules ftw!

Works for me! I support any decision that makes my life easier.


Adds sbomqs tests

While the exercise was interesting to see if we can beat the scores by making up some supplier and cpe strings, this is not a feature I would like to include in cdxgen.


Implement bootstraping code for submessage support inside templates (part2).

What this PR does / why we need it:
NOTE Please read the entire description before reviewing. I can bet that it will help in the review.
This PR implements code generation of template bootstraping code (code that gets compiled in Mixer. It instantiates instances and types from config for all templates and dispatches them to adapter). Previous part 1 PR  was responsible for generating definitions of instance and type constructs from templates with sub-messages. This PR is responsible for instantiating those generated artifacts based on user config. It finishes the submessage support work.
To support submessages, the generated code is restructured in this PR so that we can do recursions. Changes are in the following generated functions : InferType and ProcessCheck, ProcessQuota and ProcessReport. The new layout is something like this :
// This function creates an instance from config and dispatches to the adapter
ProcessCheck (config, adapter) {
   // Main function that build the instance. It might call into other Build functions to build sub instances for
   // the sub-messages
   BuildTemplate = func(config InstanceParam) Instance {
     var resultInst Instance
     resultInst.Value = Eval(config.Value)
     ..
     if (typeOf config.subMsgField is ResourceMessage) // this is a submessage
        instance.subMsgField = BuildSubMsg(config.subMsgField)
     }
     return resultInst
   }
   BuildSubMsg = func(config SubMsgInstanceParam) SubMsgInstance {
     var resultInst SubMsgInstance
     resultInst.field1 = Eval(config.field1)
     ..
     if (typeOf config.anotherSubMsgField is ResourceMessage) // this is a submessage
        instance.anotherSubMsgField = BuildAnotherSubMsg(config.anotherSubMsgField)
     }
     return resultInst
   }

   inst := BuildTemplate(config)

   ..
   adapter.Handle... (inst, ...)
}

NOTE: This PR is tricky to review because it is hard to visualize the diff of golang template file and the corresponding generated code. I recommend start reviewing the tests first and the baseline generated code after that (sample test files (check.proto, quota.proto and report.proto) and baseline generated file is AllTemplate.go.golden).
Also NOTE : There are two types of tests that are implemented in this PR:

Baseline test under /tools/codegen/pkg/bootstrap which just compares the generated code with baseline view.
Other is run-time test for the generated code and it lives inside /template/sample/template.gen_test.go

Release note:
support sub messages in Mixer template

@guptasu: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.
Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ee4f5f33e54c472a4e282b670e60a6a07430afc2
link
/test istio-presubmit

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

@ozevren @geeknoid @douglas-reid @mandarjog  friendly ping

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
af764d72ddf8637acd799a4af48d8ac49ff813c3
link
/test istio-presubmit

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

@geeknoid friendly ping

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
bcba3d8ff3ba3947ddd228fb998f88803df2e086
link
/test istio-presubmit

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

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
5017640b5e0d83d6d5ed6cffaafe8a863106f180
link
/test istio-presubmit

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

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
6410f932866daf3e86f52a4a657e584ecfb9cc17
link
/test istio-presubmit

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

@geeknoid @ozevren re-lgtm please. I have addressed linter issues + added .gen.go files.


Restore packages at the beginning of the build

if you clone the repo the build won't work.
This restores all NuGet packages at the beginning.

Thanks!


base-files: Add check in welcome-connagtive and prettify

Add a check in welcome-connagtive.sh script that displays the onboarding state to prevent referencing non-existing files before the first provisioning.
Also change the formatting and add some colors for a better visual experience.

LGTM


dmon-controller query conversion to csv broken

CSV conversion of dmon-controller based es query broken.

Elasticsearch-py module is strictly linked with the version of elasticsearch used. Upgraded to version 2.2.0 of the module to match elasticsearch server version. Updated requirements txt file.


Using Quasar UI like a main UI for gekko

Thanks for your big work!
Please correct documentation part for "Compile for replacing the original Gekko-UI"
it should be one more step after (6):
Edit ~line 87 in web -> server.js:
replace
app
  .use(cors())
  .use(serve(WEBROOT + 'vue/dist'))
  .use(bodyParser())
  .use(require('koa-logger')())
  .use(router.routes())
  .use(router.allowedMethods());

with
app
  .use(cors())
  .use(serve(WEBROOT + 'vue'))
  .use(bodyParser())
  .use(require('koa-logger')())
  .use(router.routes())
  .use(router.allowedMethods());

Gekko v. 0.6.5

Thanks for the hint. Actually the UI should'nt be working at all with Gekko > 0.6.5 because of massively changed events and API. I will get to this as soon as I have some time to update everything to the new 0.6+ events-api.

Udated to work with 0.6 Gekkos.

Udated to work with 0.6 Gekkos.

I don't know it's a bug or feature but there is no live tradings on dashboard - https://ibb.co/mgacaK
Gekko v0.6.6
Gekko-quasar-ui v0.5.24

@elmankross please try to pull the latest version - I've made some changes in the meantime.

@H256 it works 👍


Rename fh-Kempten.txt to hs-kempten.txt

E-Mail Adress has changed.

Duplicate: https://github.com/leereilly/swot/blob/master/lib/domains/de/hs-kempten.txt. Closing.


DependsOnMethods made parallel class use several threads

TestNG Version

6.9.12 and <IP_ADDRESS>

Expected behavior
When setting TestNG to run tests in parallel by class, all the tests in a single class should be run in the same thread.
Actual behavior
If one of the test method depends on another, a new thread is created, which is really annoying for Selenium case for instance (BeforeClass open the browser, AfterClass kill it)
Test case sample
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="main" parallel="classes" thread-count="2" verbose="0" group-by-instances="false">
    <test name="all">
        <classes>
            <class name="TestFoo"/>
        </classes>
    </test>
</suite>

import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Test;

public class TestFoo {

  @BeforeClass
  public void navigateTo() {
    System.out.print("BeforeClass - ");
    printThread();
  }

  private void printThread() {
    System.out.println(Thread.currentThread().getName());
  }

  @AfterClass
  public void die() {
    System.out.print("AfterClass - ");
    printThread();
  }

  @Test
  public void t1() {
    System.out.print("T1 - ");
    printThread();
  }

  @Test(dependsOnMethods = "t1")
  public void t2() {
    System.out.print("T2 - ");
    printThread();
  }

}

BeforeClass - pool-1-thread-1
T1 - pool-1-thread-1
T2 - pool-1-thread-2
AfterClass - pool-1-thread-2

What I've tried:

singleThreaded = true
group-by-instance="true"

Is it working as expected without the dependsOnMethods?

@juherr yes, only 1 thread was used when I removed dependsOnMethods from the example above:
BeforeClass - pool-1-thread-1
T1 - pool-1-thread-1
T2 - pool-1-thread-1
AfterClass - pool-1-thread-1

It's working fine also if I set thread-count to 1.

Yes, the problem is located in GraphThreadPoolExecutor/DynamicGraph. But I don't know how to fix it for the moment.
Don't expect a quick fix, sorry.

@juherr At least it's already good to know where the issue come from. Except remove the dependsOnMethods and refactor a bit my class, do you see a workaround?

In fact, dependsOn with parallel class can not work together. If it worked before, it was a side effect of another issue :/

I don't understand why you said dependsOn with parallel class cannot work together. Indeed, in this paralell mode, all the test methods inside a class has to be run in the same thread, so it does not affect the dependsOn, this is the theory.
Perhaps, you said it cannot work because the code does not allow it?

Perhaps, you said it cannot work because the code does not allow it?

In the current state, yes. But it is supposed to work ;)

Hi @juherr
Any update on this? I'm facing the same problem due to parallel execution with dependsOnMethod. I had a look to graph/GraphThreadPoolExecutor.java but it looks like my basic knowledge won't be enough here.
Thank you!

@mathias21 Nope, nothing new for the moment. Sorry.

Hi @thibaut-sticky
I think I've found a workaround to solve this problem. It takes 2 dependencies: with the max amount of devices you are going to use at the same time, and also forcing you to release the session during @AfterClass method, but apparently it works. If you specify in your suite XML file "thread-count='2'", then you can define your suite as following:

<test name="Test cases2" >
    <classes>
        <class name="packageB.TestClass1"/>
        <class name="packageB.TestClass2"/>
    </classes>
</test>

It is not the best solution, but apparently runs your tests with proper sorting.

@mathias21 Thx you for your workaround, but sadly in my case I cannot apply it. But at least I can see I'm not the only one using parallel and dependsOnMethod features 👍

i have the same problem with parallel=classes & using dependsOnMethod in one classe, and i do some prepare work using localThread var :(. it takes me a long time to find out the thread change. hope this bug could be fixed soon :)

The similar problem happens when using priority. Described in #1066

@juherr
I am quite impacted by this issue as well, and saw you self-assigned the ticket.
Does that mean you're actively working on a resolution? What kind of priority is this for you?
This rather high for us...
Thanks

Hi all
Do we know if this is not happening in a concrete version? I'm also using 6.9.12. I believe this is a structural issue, not a punctual bug or typo, am I right?

@sylvainbouxin "actively" is not the good word but it is on the top of the list and I planned to work on it unless someone has enough motivation.
And I'm open to any help! 😉
@mathias21 Exactly! There are some similar issues and the root cause is often DynamicGraph which manages the order of methods and the group of methods when parallel is used. So, just one of the most important part of TestNG which generate test regression each time I have to modify it! 😨

@juherr nice challenge, indeed...
I'm currently looking into this: I really need this fixed or write my own framework to manage the order of methods and classes with parallel execution.

@sylvainbouxin Nice! Feel free to send me emails if you need to exchange some extra things.

@juherr, you said:

Yes, the problem is located in GraphThreadPoolExecutor/DynamicGraph.

Can you elaborate on what the problem is exactly?

@cbeust due to the edge between methods, dependsOn* methods are no more together in the free nodes list. Now, they are free one by one.

@juherr
Hello Any update on when the issue will get fixed.

Can you please prioritize this issue-fix @juherr

@nevilp88 - Its not that this issue is not a priority. Its just that, we haven't gotten around to fixing this, mainly due to lack of sufficient time. Trust me, this is one of the biggest issues that still is in our plate for fixing. But since this is also a problem in the core of TestNG, its a bit tricky to change behavior and ensure that we don't break anything.
If you would like to take a go at it, and help provide a PR, we would be more than happy to help review it and get it merged.
There's just a handful bunch of us (to be honest, currently just me and @juherr currently) who are juggling with all issues and trying our best to get them fixed.  Thanks for your understanding

Hi, I'm just one more guy facing this issue

Hi! Any updates?

Any plans to fix this?

Thx for the fix. The current changelog of the future release is pretty big. Can we expect quickly a new version?

@thibaut-sticky I'm not sure we will release quickly because it will be a major release and we want to take enough time to change/break everything we want/need without waiting for the next major release.

If I am not mistaken issue was fixed. But I am still able to reproduce it in 7.0.0-beta1.

I dont think this was ever fixed, however 7.0.0 reverts whichever fix you attempted to do.
We moved away from testng as our testsuite was growing and we couldnt afford not being able to use parallel exeuction.
I did test our old codebase that was still using testng with 7.0.0 and the issues keeps happening.

@andrei-kotau-epam @ryudice
When using TestNG 7.0.0-beta1 am assuming that you folks are enabling this feature by passing the JVM argument -Dtestng.thread.affinity=true. Only when this JVM argument is passed would thread affinity be guaranteed. Please retry and let me know how it goes.
If even after doing that this issue is still occurring, please help share a sample that can be used to reproduce this issue.

@krmahadevan works for me with -Dtestng.thread.affinity=true (7.0.0-beta1) . Thank you!
cc: @ryudice

I have come across an issue.
When i tried this (on both beta7 and beta1)  :
`import org.testng.annotations.Test;
public class TestClass2 {
@Test()
public void test0(){
    System.out.println("TestClass2 - test0. Thread " + Thread.currentThread().getId());
}

@Test
public void test1() {
    System.out.println("TestClass2 - test1. Thread " + Thread.currentThread().getId());

}

@Test(dependsOnMethods = "test1")
public void test2() {
    System.out.println("TestClass2 - test2. Thread " + Thread.currentThread().getId());

}

@Test(dependsOnMethods = "test2")
public void test3() {
    System.out.println("TestClass2 - test3. Thread " + Thread.currentThread().getId());
}

@Test()
public void test4(){
    System.out.println("TestClass2 - test4. Thread " + Thread.currentThread().getId());
}

}
and then tried to run through xml like this :

<test  name="testNG tests" parallel="classes" thread-count="50" >
    <classes>
        <class name="ie.kbc.qa.seleniumT24.debugs.TestClass2"/>
    </classes>
</test>

`
I got an exception :
`Exception in thread "TestNG-test=testNG tests-1" java.lang.NullPointerException
TestClass2 - test0. Thread 9
at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
at org.testng.internal.thread.graph.GraphThreadPoolExecutor.handleThreadAffinity(GraphThreadPoolExecutor.java:156)
at org.testng.internal.thread.graph.GraphThreadPoolExecutor.afterExecute(GraphThreadPoolExecutor.java:102)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

TestClass2 - test1. Thread 9
TestClass2 - test4. Thread 9
Process finished with exit code 1
`
This exception is thrown when there is more then one test with no dependOnMethods

@mstancl - Thanks for sharing that sample. Since this is a problem that has arose out of the thread affinity feature that I introduced into TestNG, I have created a new bug for this https://github.com/cbeust/testng/issues/2110
Please track this issue with #2110

Hi! I have another issue that is related to this topic. Maybe it's just a misuse of TestNG from my part, but I feel it could be a problem on TestNG's side. So basically the problem is that the thread affinity feature only works when you test a single class (from what I've tested). Here I have two classes with the same exact methods:

And here I have my xml file with a only one of them, which gives me the following result:

Which is the correct behaviour! Although, if I run my two classes in parallel, this is where it gets funky:

Again, it may be me not understanding how to write a proper xml file...
Also, here's what happens when I don't use -Dtestng.thread.affinity=true (just to prove that I am using it):

Thank you!

@FredVaugeois - I would suggest that you please open up a new issue and include a sample that can be used to reproduce the problem.


guild caching

hopefully fix guild caching and change it from 5 minutes to 24 hours

(fastest review time in the history of SkyCrypt)

https://sky.shiiyu.moe/stats/Bannu/Banana2f89
43c239d3400ba608700cbf81fc40
pls fix


:4200/beta/vendor.js:43724 ERROR TypeError: Cannot read property 'pipe' of undefined     at MatSelect.ngAfterContentInit (:4200/beta/vendor.js:119926)

Closing this issue as it does not follow the issue template. Please file a new issue that follows the template, which gives the team the information needed to investigate.