You have exceeded the maximum rate limitation allowed on your subscription plan

Hi Team,
This is mani i have some issue from currency layer like below
The chain resulted in 1 exception(s): Exchanger\Exception\Exception: You have exceeded the maximum rate limitation allowed on your subscription plan. Please refer to the "Rate Limits" section of the API Documentation for details.
but in my account my api usage is like 4% (10 / 250)

Hi @msquareM, we are just returning errors from the provider so I suggest to contact the provider to see if they can debug the issue on their side.


Inherit Folder from MPTTModel instead of using mptt.register().

The preferred way to do model registration is via model inheritance and mptt.AlreadyRegistered is deprecated since django-mptt 0.4
https://django-mptt.readthedocs.io/en/latest/upgrade.html?highlight=mptt.register#use-model-inheritance-where-possible

Codecov Report

Merging #1068 into master will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1068      +/-   ##
==========================================
+ Coverage   70.98%   71.01%   +0.02%
==========================================
  Files          63       63
  Lines        3102     3098       -4
  Branches      444      444
==========================================
- Hits         2202     2200       -2
+ Misses        747      745       -2
  Partials      153      153

Impacted Files
Coverage Δ

filer/models/foldermodels.py
76.04% <100.00%> (+0.53%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 37e5719...ff44810. Read the comment docs.

@jrief @FinalAngel how about merging this?


Broken sites/stylesheets, PhantomJS version woes

The following sites seem consistently broken in a way that suggest unloaded stylesheets (and maybe more):
New York Times: http://www.pastpages.org/site/new-york-times/
Bloomberg: http://www.pastpages.org/site/bloomberg/
SVT: http://www.pastpages.org/site/svt/
Seattle Times: http://www.pastpages.org/site/seattle-times/
NPR: http://www.pastpages.org/site/npr/
Denver Post: http://www.pastpages.org/site/denver-post/
International New York Times: http://www.pastpages.org/site/international-nyt/
I'll investigate further when I have a chance but when I run phantomjs archive/tasks/images.js with PhantomJS v2.0.0 on these sites locally, they work fine, so a few initial thoughts about possible differences:
-The bundled phantom in PP is v1.8.1.  If I run the script with that version instead, I get all kinds of new errors.  In some cases, like the International NYT, it crashes without rendering at all.  The results don't match up exactly with what's on the PP site so I'm not sure this is the full explanation, but there's definitely a big discrepancy between the versions, so an upgrade might be worth a shot.
-Server IP - maybe certain resource servers have flagged the live PP server as an unwanted crawler? Seems unlikely but I guess it's possible.

Upgrading a great idea.


Python: Support existing virtual environments?

This issue is to open the discussion for the scenario where a user would like to use their pre-existing virtual environment for a new Python Functions Project.
We don't quite understand how users use venv, especially in the case for Functions.  Futhermore, we don't know if it makes sense for the user to Browse to the root of the venv folder or to the activate script that is used to enable the venv.

Holding off on this until we hear from customers

Closing this as it's been about half a year and we haven't received feedback related to existing venvs since then, plus the experience has changed already.


Installing azure-cli 2.39 on RHEL 8 fails if python39 is not found

Installing azure-cli 2.39 on RHEL 8 fails if python39 is not found
This item has been moved from MicrsoftDocs/azurecli #3253.Azure CLI version being used
2.39.0
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux
Description
`Error:
Problem: cannot install the best candidate for the job
nothing provides python39 needed by azure-cli-2.39.0-1.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)`
Suggested fix
Options.
Current doc says required python is 3.6. request reflect python 3.9 as a dependency, or fix the dependency in the package to 3.6, as is documented.

Thank you for opening this issue, we will look into it.

For centos7, CLI requires python3 package, which is python3.6.
For RHEL 8, CLI requires python39 package, which is python3.9.


Crash with 5.89

Custom modpack, just updated both rftools, compatlayer and mcjtyLib
Here is top message, pastebin below:
There was a severe problem during mod loading that has caused the game to fail
net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from RFTools (rftools)
Caused by: net.minecraftforge.fml.relauncher.ReflectionHelper$UnableToFindMethodException: java.lang.NoSuchMethodException: net.minecraft.block.Block.getSilkTouchDrop(net.minecraft.block.state.IBlockState)
Forge <IP_ADDRESS>9
http://pastebin.com/bK0XmRZK

Same here:
crash-2017-03-20_13.03.56-client.txt
Minecraft: 1.10.2
Forge Mod Loader: 1.10.2-<IP_ADDRESS>9
CompatLayer: 1.10-0.2.5
McJtyLib: 1.1x-2.3.11
RFTools: 1.1x-5.89

Yep. Glad I'm not the only one getting this error.
Forge version: <IP_ADDRESS>4
Crash Report

Also getting the same crash.
http://pastebin.com/dwdNncy6

Same here. :c

same

Hey everyone. Instead of saying "same" hit that subscribe button over on the right to get notified if any new and relevant info has been posted. Don't comment unless you have new or relevant information.

"Same..."  hahahaha
https://gist.github.com/Endmateria/9edea3e3285f5465a6382112f9a99dc8#file-crash-3-20-17

Same 😛
http://paste.feed-the-beast.com/view/5c563c71

Fixed in 5.90


Native context menu for TextField

Use case
The TextField widget lacks support for native context menu, such as translation or sharing (In my case of Android)
Screenshot of a native app(Google) running on a Pixel 6 Pro emulator with API 33.

Screenshot of a native app running on my Xiaomi smartphone with MIUI 14 and Android 13.

Screenshot of my Flutter app running on a Pixel 6 Pro emulator with API 33, showing a text field with only default context menu of Flutter and without native context menu like translate or share.

I couldn't find any packages to solve my problem.

Proposal
Add support for native context menu on all platforms.

Hi @ansjdev, this is being tracked in https://github.com/flutter/flutter/issues/107578.
Kindly subscribe to the original issue for updates.
Closing from here as duplicate.
Thank you


Fix rebase issues

CONFLICT (content): Merge conflict in scripts.d/25-freetype.sh
! [remote rejected] master -> master (refusing to allow a GitHub App to create or update workflow .github/workflows/pr.yml without workflows permission)

First issue was fixed by reverting SourceForge commit, and it's probably better to drop that commit entirely by an interactive rebase.

4c4ae2ad37b8cd266ab2d09bfc82ca74ae1e0605 was changed because the sourceforge URLs were sometimes not working. But since upstream seems to be working fine with them now, I've dropped that commit.


Take a look at JS implementation

I just found a JavaScript implementation, https://github.com/aredridel/lotsawa, which may be of some interest.
/cc @jeffreykegler

@aredridel and @iarna are supporters of my work from the very early days.  IIRC correctly this implementation didn't reach the point where it was ready for uses.

Yeah, I don't see them traversing the tree.  However they do some building of prediction bitsets and other things that might have value.  I find it pretty hard to read cweb sources so I can't easily tell whether that was cribbed from MARPA's source.

Indeed, I did not get that far— life intervened and I've not had the deep thought available to come back to it. (And the js ecosystem moved funny; I'd probably use WASM for core parts, the way marpa has some core parts separate from the user interface layer)

But any code in that repo that's useful I am happy to hand off to whoever can use it.

Not gonna happen, I think.


Packet type; Conversion support for packet related types

Closes: #95

For contributor use:

[ ] Updated the Unreleased section of CHANGELOG.md with the issue.
[ ] If applicable: Unit tests written, added test to CI.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

Merging #399 (0cd0f77) into master (b1b37f5) will increase coverage by 20.9%.
The diff coverage is 63.3%.

@@            Coverage Diff            @@
##           master    #399      +/-   ##
=========================================
+ Coverage    13.6%   34.6%   +20.9%
=========================================
  Files          69     152      +83
  Lines        3752    9893    +6141
  Branches     1374    3595    +2221
=========================================
+ Hits          513    3427    +2914
- Misses       2618    6221    +3603
+ Partials      621     245     -376

Impacted Files
Coverage Δ

modules/src/events.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/events.rs
0.0% <ø> (ø)

modules/src/ics02_client/msgs.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/raw.rs
0.0% <0.0%> (ø)

modules/src/ics03_connection/error.rs
13.6% <0.0%> (-19.7%)
:arrow_down:

modules/src/ics04_channel/error.rs
75.0% <ø> (+50.0%)
:arrow_up:

modules/src/ics04_channel/msgs/acknowledgement.rs
0.0% <0.0%> (ø)

modules/src/ics04_channel/msgs/recv_packet.rs
0.0% <0.0%> (ø)

modules/src/ics04_channel/msgs/timeout.rs
0.0% <0.0%> (ø)

modules/src/ics04_channel/packet.rs
0.0% <0.0%> (ø)

... and 283 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 62d405a...0cd0f77. Read the comment docs.


[Event Request] Table 81 SetUpNewLine

I Would like to request an event as shown bellow so we can initialize a specific field:
Table 81 - SetupNewLine

This would be nice. I will follow this one.


[Feature Request] upload "limit" reached, I hope it can replace the old file when i reselect file.

Existing Component
Yes
Component Name
EL-UPLOAD
Description
when i set "limit" to uplaod. I think there may be a switch to set that I can replace the old file when i reselect file, otherwise response nothing.
like https://jsfiddle.net/1bntk75u/12/

Sorry, we have no plan to support this. You can implement it like your demo.


OSS Whitepaper

Description

Related Issue(s)

Checklist

[ ] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

@Yndira-E @Hasmin-AC I appreciate the iteration. I think it would serve the content if there's additional visual aids to drive some points. Would you be able to read the content and think of such  visuals?


Support for cg-angular Yeoman Generator

For the front-end module, use 'generator-cg-angular' yemoan generator instead of angular-slush.
https://github.com/cgross/generator-cg-angular
Benefits of cg-angular :-

Configuration to use UI-Router if needed and not just standard ngRouter.
The generator genrates both Gruntfile ang gulpfile.
Subgenerators for module,filter,service,partial,directive.
the dist have simple unglified js with template cached -> no htmls - lesser no. of files for browser to get.

Personally I don't use Yeoman at all, so I'm not going to change this behaviour at this moment. Feel free to generate your own version of frontend side with Yeoman. And if you make this to separated repo I'll add information about that to README.MD.
This is one of the main points of separation of back- and frontend, so that users can make new frontends as they like.


Fun & games with AWS Identity center

I'm using AWS, setting up a custom service provider as a lambda to be fed by the IAM Identity Center.  I'm having lots of fun, but the final bug/issue is that AWS is failing OneLogin::RubySaml::SamlMessage.valid_saml?
In order to get to this point, there are a few things to beware:

You need to configure the attribute mapping for your provider to map subject to ${user:subject}.  I use the emailAddress format.  Others have said transient.
AWS (and Google) say that their messages are base64.  Use Base64.decode64(CGI.unescape(saml_response)).

It should not matter, but we use Google Workspace as our primary IdP.  AWS IIC is reflecting from there.  All identities in AWS IIC are emails.
I would rather not copy the message in here, as I get too much spam anyway.  If you're not in a position to set up your own experiment quickly, perhaps we could communicate the message out of band.

Sorry, not sure what kind of support you are looking for.
Are you able to see why valid_saml? is failing? you should check on errors.
The toolkit should be compatible with Google and AWS as well, let me know if you experience any issue.

Sorry for not being clear.

The failure is the schema validation.  Errors is: ["Invalid SAML Response. Not match the saml-schema-protocol-2.0.xsd"]
It would be useful to see if someone else has had success with the AWS, and if there is any magic that they used.

Line: 41 | Column: 0  --> Element '{urn:oasis:names:tc:SAML:2.0:assertion}AttributeStatement': Missing child element(s). Expected is one of ( {urn:oasis:names:tc:SAML:2.0:assertion}Attribute, {urn:oasis:names:tc:SAML:2.0:assertion}EncryptedAttribute ).

Which is not very helpful, as the response has 41 lines.
I'm going to X out the sensitive stuff & try to paste in useful details
<?xml version='1.0' encoding='UTF-8'?><saml2p:Response Destination='https://XXX.lambda-url.us-east-1.on.aws/XXX' ID='XXX' IssueInstant='2023-08-18T16:28:27.712Z' Version='2.0' xmlns:ds='http://www.w3.org/2000/09/xmldsig#' xmlns:enc='http://www.w3.org/2001/04/xmlenc#' xmlns:saml2='urn:oasis:names:tc:SAML:2.0:assertion' xmlns:saml2p='urn:oasis:names:tc:SAML:2.0:protocol'><saml2:Issuer Format='urn:oasis:names:tc:SAML:2.0:nameid-format:entity'>https://portal.sso.us-east-1.amazonaws.com/saml/assertion/XXX</saml2:Issuer><ds:Signature xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/>
<ds:SignatureMethod Algorithm='http://www.w3.org/2001/04/xmldsig-more#rsa-sha256'/>
<ds:Reference URI='XXX'>
<ds:Transforms>
<ds:Transform Algorithm='http://www.w3.org/2000/09/xmldsig#enveloped-signature'/>
<ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/>
</ds:Transforms>
<ds:DigestMethod Algorithm='http://www.w3.org/2001/04/xmlenc#sha256'/>
<ds:DigestValue>XXX</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
XXX
</ds:SignatureValue>
<ds:KeyInfo><ds:X509Data><ds:X509Certificate>XXX</ds:X509Certificate></ds:X509Data></ds:KeyInfo></ds:Signature><saml2p:Status><saml2p:StatusCode Value='urn:oasis:names:tc:SAML:2.0:status:Success'/></saml2p:Status><saml2:Assertion ID='XXX' IssueInstant='2023-08-18T16:28:27.712Z' Version='2.0'><saml2:Issuer Format='urn:oasis:names:tc:SAML:2.0:nameid-format:entity'>https://portal.sso.us-east-1.amazonaws.com/saml/assertion/XXX</saml2:Issuer><ds:Signature xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/>
<ds:SignatureMethod Algorithm='http://www.w3.org/2001/04/xmldsig-more#rsa-sha256'/>
<ds:Reference URI='XXX'>
<ds:Transforms>
<ds:Transform Algorithm='http://www.w3.org/2000/09/xmldsig#enveloped-signature'/>
<ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/>
</ds:Transforms>
<ds:DigestMethod Algorithm='http://www.w3.org/2001/04/xmlenc#sha256'/>
<ds:DigestValue>XXX</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
XXX
</ds:SignatureValue>
<ds:KeyInfo><ds:X509Data><ds:X509Certificate>XXX</ds:X509Certificate></ds:X509Data></ds:KeyInfo></ds:Signature><saml2:Subject><saml2:NameID Format='urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress' SPNameQualifier='audience'>XXX</saml2:NameID><saml2:SubjectConfirmation Method='urn:oasis:names:tc:SAML:2.0:cm:bearer'><saml2:SubjectConfirmationData NotOnOrAfter='2023-08-19T04:28:27.713Z' Recipient='https://XXX.lambda-url.us-east-1.on.aws/base'/></saml2:SubjectConfirmation></saml2:Subject><saml2:Conditions NotBefore='2023-08-18T16:23:27.713Z' NotOnOrAfter='2023-08-19T04:28:27.713Z'><saml2:AudienceRestriction><saml2:Audience>audience</saml2:Audience></saml2:AudienceRestriction></saml2:Conditions><saml2:AuthnStatement AuthnInstant='2023-08-18T16:28:27.713Z' SessionIndex='_d2fd6c31-3e90-46f1-8df6-ce92f0a32d34' SessionNotOnOrAfter='2023-08-19T04:28:27.713Z'><saml2:AuthnContext><saml2:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport</saml2:AuthnContextClassRef></saml2:AuthnContext></saml2:AuthnStatement><saml2:AttributeStatement/></saml2:Assertion></saml2p:Response>

I note that the examples here are all for samlp responses, but your tests match the saml2p of the message.

Just for fun, I posted the above as well.  I got a bunch of invalid base64 warnings, an invalid id warning, and the attribute complaint from the above.  So I'm guessing that the problem actually is with the empty attribute statement.

And... adding a mapped attribute to the settings in AWS Identity center results in response.is_valid? being true.
So back to your "What do you want?" above...

Change the logic in https://github.com/SAML-Toolkits/ruby-saml/blob/c9685a98a9c00c38af65364e70a7315eb49a2222/lib/onelogin/ruby-saml/saml_message.rb#L88 to identify and unescape CGI escaped base64 strings.
Either loosen the validation to permit <saml2:AttributeStatement/> or document that some providers are known to fail this validation unless attributes are mapped.

Saml2Responses with empty AttributeStatement
<saml2:AttributeStatement/>

are not allowed according to the standard. They should either contain other elements or be non existing all together.
From Scott Cantor, one of the authors of SAML spec:

Under the situation described above, shouldn't the IdP send a SAML assertion with an empty AttributeStatement instead of no
AttributeStatement at all?
Scott: As Chad said, no, that's not allowed.

See: https://lists.internet2.edu/sympa/arc/shibboleth-dev/2009-03/msg00008.html
See also:

http://www.datypic.com/sc/saml2/e-saml_AttributeStatement.html

@pitbulk I can accept that AWS is violating the SAML standard.  They are also double-encoding their data, which also causes problems.  What I find difficult to accept is a situation where a major use case of the gem is going to fail unless adjustments are made, and there is no documentation of this fact.  If you want to be strict with the spec, I can totally support that, but please have pity on the poor user who wants to use this gem specifically because they don't want to have to become an expert on SAML or SAML implementations.  A clear mention in the documentation, along with the workaround I found, is going to save such a user quite a bit of time and effort.

@NathanZookCH can you raise a ticket with AWS here? They are usually pretty good about fixing issues.


D3VAE: overwrites timestamps?

Hi,
I came across something weird in the D3VAE code. In data_loader.py, line 93, you just manually overwrite the timestamps of the data:
df_stamp = pd.date_range(start='4/1/2018',periods=border2-border1, freq='H')
data_stamp = time_features(df_stamp, timeenc=self.timeenc, freq=self.freq)
Can you tell me why that is?

hi,
This is to read in some data sets with irregular time formats. We have tested that this operation does not affect the experimental results.


Change rbx_reflection_database to support loading from FS

As part of the effort to get the reflection database loadable locally, it's probably a good idea to have a central place that decides locations for the entire ecosystem. This will prevent consumers like Lune and Rojo from having to re-implement this logic.
The obvious choice for this, in my opinion, is rbx_reflection_database. It's a requirement for everything that uses the reflection database already, and its public API can be extended to take things from the file system into account without any issues. I've implemented it and documented it thoroughly in the README for rbx_reflection_database.
However, it also sacrifices the 'purity' of the module because it fundamentally alters its purpose. I'm okay with that, but I understand not everyone will be. Please be honest with your thoughts.
I know for sure this works on Windows and Linux. I'm assuming it will also work on MacOS, but I don't own a machine I can use for testing. I don't know how to test this in CI, so we'll just have to be mindful of changes.

Allowing the database to be replaced once it's initialized is complicated because it involves mutating a static variable, so for the time being I'm going to ignore it. Tools like Rojo and Lune can work out solutions without that.


Simplify, error handling, and specs

:hand: Hi.
I added and fixed some codes to your mizzy/specinfra#459 :

Organized one (for reducing nested cond-statement)
Raise error if unknown protocol
Add specs.

:hand: Hi!
Thanks for that! That was the quickest solution I could find yesterday night :smile:


[Vert.x] Runtime information section: fix wording around vertx maven plugin

The guide currently says:

Reference vertx-maven-plugin as a dependency for your application.

this is inaccurate and should be changed to:

Reference vertx-maven-plugin as a plugin to be used for packaging your application.

NOTE: this is the prescribed way of packaging apps developed with RHOAR, but i is by no means a the only way:)

resolved in PR #853

fixed in #853


[Issue 14485] .front of empty filtered zip range is accessible

Also fixed filterBidirectional while I was at it.

Auto-merge toggled on


How does naudiodon feed PCM data to portaudio? Interleaved or non-interleaved?

Hey there!
Hoping someone can clear this up for me, I've only just got into naudiodon and portaudio. Reading the portaudio c documentation, it says that it reads in multichannel pcm as interleaved or non-interleaved samples and 'automatically performs conversion where necessary'. I'm a bit confused how this concept applies within naudiodon.
Are we required to feed our multichannel files as interleaved or non-interleaved samples? I.e [chan1sampl0,chan2sampl0,chan3sampl0, chan1sampl1,chan2sampl1, chan3sampl1] or [chan1sampl0,chan1sampl1,chan2sampl0,chan2sampl1, chan3sampl0, chan3sampl1]?
Doing some tests, I see interleaving 8 bit samples seems to do the trick.
Now, when streaming more than 8 bit samples, how do we fill a buffer with the correct bytes for each sample? For instance, a 16 bit word, do we fill the buffer [upper16chan1sampl0,lower16chan1sampl0,upper16chan2sampl0,lower16chan1sampl0,...  Etc ] or some other way?
Would appreciate any guidance with this!

Hi tonetechnician,
naudiodon doesn't attempt to do any kind of formatting of the audio data to or from portaudio. It expects interleaved samples for multichannel streams with the bit depth of each sample corresponding to the sample format specified in the options object. I think your 16-bit example looks about right - though you might need to check your endianness.
Good luck!

Thanks so much for the reply here.
Yes, I think there is a problem with my endianness. Have tried the above example and just get a nasty screech. Will look into it and post here once I've found out in case anyone else is wanting to know.


[Bug][Dashboard][Manager] The whitelist input format of binlog source need to be optimized

What happened
The correct input format is as follows:
#5050
What you expected to happen
Given the right input format, and some instructions about the format.
How to reproduce
Using whitelist
Environment
No response
InLong version
master
InLong Component
InLong Dashboard
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

After confirmation, the Debezium engine used in the Agent will take the intersection of the database name whitelist and the table name whitelist.
In order to facilitate user understanding and configuration, it is recommended to only open the configuration of the table name whitelist.
This means that the databaseWhiteList field needs to be removed in the dashboard module, leaving only the tableWhiteList parameter.


Get rid of setup

Description
Changes proposed in this pull request:

get rid of the Default func
move chartConfig func to the Reconcile

Related issue(s)

https://github.com/kyma-project/serverless-manager/issues/219

/test pre-serverless-operator-build

/test all

/retest

/retest


Extend "Cancel and close unpaid orders" to include expired orders

https://tasks.mechanic.dev/cancel-and-close-unpaid-orders-after-two-days
Right now, this task queries for financial_status:pending. I think this additional should be optional (open to discussion on that one), but I'd like it to include support for financial_status:expired as well. (The "expired" state feels like a substate of "pending", to me.)

I am presuming this update is in part related to this thread?
Adding the expired financial status filter as an option to the task is simple enough, but I wonder if doing so will properly assist the merchant making the request in that thread. From what I understand of Matt S' note, there doesn't seem to be a way to support restocks while using the REST API cancel method, and the refundCreate mutation requires that a captured transaction be refunded.
The typical approach here would be to just test all of this in a dev shop, but there doesn't seem to be a way to set an authorization as expired, and authorizations that auto-expire after 7 days using the Shopify Payments gateway don't seem to get switched to expired status in dev shops (I'll need to wait 7 days to reconfirm this). [They certainly don't when using the Bogus Gateway]
Perhaps in the interim there should be a note in the task docs indicating that restocks on expired orders are not supported? Assuming of course that there is potential for value to merchants in having this task cancel/close expired orders without restocks.
Thoughts?

It's unrelated [to that thread], actually! A merchant wrote in about this, because they've got expired orders that they'd like to have cleared out, along with the sort of pending orders that we're used to seeing.
I am really glad that I posted this up first, before just implementing it myself, because I would have missed this detail about restocking. :)
Bringing that relevant detail into this thread, to collect the context:

I tried then to affect the order after it changed from "Pending payment" to "Expired" by changing the task code but it turns out I can't void payment or restock items when the status of the order is "Expired" so that doesn't work either.

I'll check in with the merchant who requested this, and see what their take on this is.

Going to close this out for now; the merchant who requested this appears to have moved on. :)

I think this may be related: https://usemechanic.slack.com/archives/CURE65U2W/p1663026975975529?thread_ts=1662998578.587339&cid=CURE65U2W

Per earlier comments in this thread, there isn't a clear way to address the issues presented by the Shopify APIs when trying to cancel and restock expired orders. Ideas welcome.
Also, it doesn't seem like test payment authorizations can be expired in dev shops, so we might need to collaborate on testing with a merchant who has expired orders in their shop.

hi @tekhaus and @mattsodomsky , I have a few clients who have this issue. Shall I add you as collaborators? Whats the best way to do this. I think this is quite an important feature as many of my clients are facing the same issue.


Enhance UI for "Meet our Friends Here" Section #1067

Enhance the "Meet our Friends Here" section's UI by replacing the previous rectangular design with more suitable styling, aligning it with UI standards and improving the overall user experience.

Before:

After:


Bug: scope and options should be read-only

Description
I am looking for the code so I can PR but I can't seem to find it.
Anyway ...
t: <T = string>(scope: Scope, options?: TranslateOptions) => string | T;

Should be
t: <T = string>(scope: ReadOnly<Scope>, options?: TranslateOptions) => string | T;

This will allow us to have a construct
t`mykey`

Which is being prevented by typescript because Scope's array form is mutable.
  /**
   * Translator function.
   * @param scope
   * @param options
   */
  t(scope: Readonly<Scope>, options?: TranslateOptions) : string;

What I did was create a wrapper as well
  const t = useCallback(
    (scope: Scope, options?: TranslateOptions) => {
      // this conditional allows for the short form.
      if (Array.isArray(scope)) {
        return i18n.t(
          scope.filter((p) => p.length > 0),
          options
        );
      } else {
        return i18n.t(scope, options);
      }
    },
    [i18n, locale]
  );

This allows for something like
const loginButtonText = useMemo(() => username.length > 0 ? t`loginAs${{ username }}` : t`login`, [t, username])

The filter was needed because
t`loginAs${{ username }}`

translates to add an empty string.
t ( ["loginAs", ""], { username })

I don't want to explicitly add support to templated strings as it's too complicated. I think creating a wrapper, as you did, is the way to go.

You don't have to create an explicit support for it, but the more correct typing is to make it ReadOnly

Ah okay so the JS code is in https://github/fnando/i18n

It's all good. I don't mind handling those issues here as well. :)

I was trying to figure out where the JS code was since I couldn't find it in this repo (with the -js suffix)

There's history there. i18n-js repo used to have both Rails/Ruby code and the JS code. I broke both apart but didn't want to get riddle of the history of this repo, so in short, it's a mess. hahahaha


Fix hidden code

Code is hidden when scroll is active

👍
This solution worked for me as well.
Thank you.

Thanks!


Camel case property names

Please add the option to choose camel case property names while serializing to JSON.

This issue will be fixed by merging the #13 pull request.
I have added the JsonSerializerSetting to the extension methods to makes it possible to configure serializer settings.


onKeyboardWillHide and onKeyboardWillShow not properly respecting maxHeight

The only visible part shown should be the height of the textInput (which isn't possible to pass textInputHeight right now).  Basically if I have buttons below my messenger, like a hamburger icon to go to a settings menu - then it won't respect the height of the hamburger icon container.  Therefore when keyboard is shown, stuff like this happens:

I think it is a better approach to have another component for textInput instead ()

if you still have this issue, can you submit a PR please

been struggling with this as well, the best solution i found was to hide the bottom tabbar menu when loading the messenger. Which looking at other apps seems to be best practice (FB messenger, Instagram, Skype, Whatsapp etc)


TypeError: get_hash() missing 1 required positional argument: 'use_fast_tokenizer'

I generated some predictions for fetaqa task. Then I tried to run its evaluator on the output results (predictions_predict.json). I get the following error for bertscore metric.
File "/home/pouramini/anaconda3/envs/uni/lib/python3.7/site-packages/datasets/metric.py", line 402, in compute
    output = self._compute(predictions=predictions, references=references, **kwargs)
  File "/home/pouramini/.cache/huggingface/modules/datasets_modules/metrics/bertscore/ad3c901af4d4f2c58af08db5c6aae5af2a3668edcf7c8f3fa9419c22807ad482/bertscore.py", line 147, in _compute
    use_custom_baseline=baseline_path is not None,
TypeError: get_hash() missing 1 required positional argument: 'use_fast_tokenizer'

There could be a mismatch between datasets metrics and bertscore, however I tried to install the versions in yaml.

Hi,
Did you build dependencies as shown in here?
It seems a problem caused by huggingface-datasets version.
Hope these information helpful!
Thanks!

Yes, you didn't specified any version for datasets in the yaml file. Mine is 1.11.0.  The bert-score version you specified is 0.3.10 however.
Which version should be used?

Oh I see the problem.
Actually we didn't specify the version in yaml file because we want to avoid conflict during conda env create -f py3.7pytorch1.8.yaml(there are so many metrics, datasets and reliance...), and after that command is finished, you need to run pip install datasets==1.14.0 specially to install the datasets v 1.14.0 as we used.
Please try that and see if it can solve your problem.
Thanks!

Thanks, before reading your comment I tried datasets 1.18.3 and the problem was resolved, I will try the version you said

Okay, feel free to re-open this if you encounter further problem in the future.


Fix Issue 21178 - It is not explained what is "unknown"

Added an example of using an opaque enum (and also an error in using it).

Also, could you please have some information in the commit message? "Fix Issue 21178" does not offer any information.
At the very least you could put the title of the issue in the commit message.


Make profile override option for robots match profile management

The ui field for 'Ignore Robots' in H3 profile overrides for a Target don't match the ui in the main profile management.
Profile override

Main profile management

Change the profile override screen to use the checkbox. The checkbox is simpler and less ambiguous.

Fix has been merged.


CASMCMS-8110: Clarify documentation regarding intermediate BOS datastructures

Description
Addresses customer concern regarding the name of a created configmap for how BOS v1 controller creates intermediate configmaps. This clarification allows customers to perform a more thorough clean-up job for boot sessions launched under BOS v1.
Checklist Before Merging

[X] If I added any command snippets, the steps they belong to follow the prompt conventions (see [example][1]).
[X] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in [Cray-HPE][2].
[X] My commits or Pull-Request Title contain my JIRA information, or I don't have a JIRA.

configmap is more appropriate than config map, IMO, but am willing to change it if that makes more sense.

configmap is more appropriate than config map, IMO, but am willing to change it if that makes more sense.

I think the capitalization is what was throwing it off.

/backport main release/1.2 release/1.0


Updating model from controller does not update control

$scope.time = '12:00';
Does not cause the control to update. Seems it's one-way binding.
Is there are fix for this?
Thanks

Fixed using this code:
               scope.$watch(attrs['ngModel'], function (newTime) {
                    scope.initTime = newTime;
                    reinitTime();
                });

Glad you solved it, perhaps ngModel.$render = function () ... would be better, I think.


non-deterministic ordering from "range" results in unnecessary deployments

Hi,
We have a template which iterates over a range of key value pairs and creates environment config for them.
{{- if $.Values.config }}
{{- range $key := keys $.Values.config }}
      - name: {{ $key }}
        valueFrom:
          configMapKeyRef:
            name: {{ $appName }}
            key: {{ $key }}
{{- end }}
{{- end }}

We noticed that we're getting rolling deployments of an app when nothing had actually changed.  Digging into diffs between the deployments, we noticed that the environment variables were ordered differently (resulting in a patch).
102c102
<           - name: AT_CONFIDENTIAL_SEARCH_ONE_CLIENT_AUTH
---
>           - name: AT_CONFIDENTIAL_ATD_UK_PAF_PASSWORD
105c105
<                 key: AT_CONFIDENTIAL_SEARCH_ONE_CLIENT_AUTH
---
>                 key: AT_CONFIDENTIAL_ATD_UK_PAF_PASSWORD
107c107
<           - name: AT_CONFIDENTIAL_ATD_UK_PAF_PASSWORD
---
>           - name: AT_CONFIDENTIAL_SEARCH_ONE_CLIENT_AUTH
110c110
<                 key: AT_CONFIDENTIAL_ATD_UK_PAF_PASSWORD
---
>                 key: AT_CONFIDENTIAL_SEARCH_ONE_CLIENT_AUTH

So it feels like the range function doesn't iterate over items in the order in which they're loaded from .Values.config.
Is there anything that can be done about this?  Both short term fix (some way to order range by key name pershaps?) and also a longer term one?

The recommended pattern is to use keys and sortAlpha, and then fetch each value by key. There's an example here: http://masterminds.github.io/sprig/dicts.html

Brilliant
Thanks Matt
On Mon, 23 Jul 2018, 6:35 pm Matt Butcher<EMAIL_ADDRESS>wrote:

The recommended pattern is to use keys and sortAlpha, and then fetch each
value by key. There's an example here:
http://masterminds.github.io/sprig/dicts.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/4375#issuecomment-407139381, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABaviTBq-rLrm8iCLtOk5DUNsjACjG9_ks5uJglNgaJpZM4Va9iJ
.

Hey @Stono,
I'm facing the exact same problem. Did you fix yours by using sortAlpha?
My Template looks like this:
{{- $keys := keys .Values.deployments | uniq | sortAlpha -}}

{{ range $keys }}

apiVersion: apps/v1
kind: Deployment
metadata:
  name: "{{ . }} || {{ $keys }}"
...

{{ end }}

My values.yaml:
deployments:
  bar: {...}
  foo: {...}

When I run helm template it results in either one of the following...
... false:
# Source: chart/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: "foo || [bar foo]"
--
# Source: chart/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: "bar || [bar foo]"

... correct:
# Source: chart/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: "bar || [bar foo]"
--
# Source: chart/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: "foo || [bar foo]"

Helm version:
$ helm version
version.BuildInfo{Version:"v3.0.1", GitCommit:"7c22ef9ce89e0ebeb7125ba2ebf7d421f3e82ffa", GitTreeState:"clean", GoVersion:"go1.13.4"}

I can't figure out why the range-context seems to change on every helm template-run, while the $keys-list is always in the same - and correct - order.
Any help is greatly appreciated!
Regards,

Yup, sortAlpha works fine for me.
{{- range $key := (keys $.Values.config | uniq | sortAlpha) }}

I've tried your snippet, somehow it's not working as expected either.
Do you happen to have an idea? I'm at my wit's end... <.<

No idea at all i'm afraid, works fine for me :(

For future seekers of truth:
When running helm with a chart of your choice, helm itself sorts the generated k8s-manifests by filepath. Since I've defined multiple deployments in one yaml-file, the generated deployment-specs are not ordered deterministic.
In my specific case I was using a helm-operator which ships with it's own sorting-logic on top of helm's by using hook-annotations. Thanks to the hooks that come with helm, I can enforce a deterministic ordering of my generated k8s-manifests.


New version: LinwoodCloud.Butterfly.Nightly version 2.2.0-beta.3

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978334972
2024-09-09 09:43:00.092 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.40.33810.0

Automated error analysis suggests -1978334972 may mean This package has a dependency missing from your system.
(Automated response - build 895.)


MINIFI-310: Changing MiNiFi docker image to use Alpine linux.

Thank you for submitting a contribution to Apache NiFi - MiNiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically master)?

[X] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi-minifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under minifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under minifi-assembly?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

reviewing

Change and build looks good!  Thanks for taking the time to improve this.  Will get this merged.


Fix #3437 & #3186 - Airflow lineage Task Group & Tests

Describe your changes :

This PR fixes #3186 & #3437
The main issue reported by a user was that a ton of change events were being generated during each pipeline run. That was happening because we weren't properly handling Task Groups and the lineage backend was continuously adding and deleting the tasks. This has been fixed in this PR

@harshach, considering that we will only be creating events the first time we see a task, IDK if we want to lose this information in the versions in case there are updates in the DAGs. On this note, I thought that by commenting out the recordChangeList in the PipelineRepository would have stopped the changes but the rest should still be functional. Is that correct? Or did I mess up the testing there. Thanks!
Thanks!

Type of change :

[x] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@pmbrull yes by removing the recordChange it won't generate changeEvent.
However its important to track a task change for example, if the DAG contains 3 task and someone accidentally deletes a task we might want to catch that as change event and notify users of the DAG.


Problem loading yolov4 model

Discussed in https://github.com/AxisCommunications/acap-computer-vision-sdk-examples/discussions/62

Originally posted by **JENNSHIUAN ** August  2, 2022
Hi, I have the same issue when I loaded my own tflite model.
I have already replaced the path to my model in the Dockerfile.model and env.aarch64.artpec8:
Dockerfile.model:
# Get custom model
ADD ./models/yolov4/train-608_best.tflite models/
ADD ./models/yolov4/labels.txt models/

env.aarch64.artpec8:
MODEL_PATH=/models/train-608_best.tflite
OBJECT_LIST_PATH=/models/labels.txt
INFERENCE_SERVER_IMAGE=axisecp/acap-runtime:aarch64-containerized
INFERENCE_SERVER_ARGS="-m /models/train-608_best.tflite -j 12"

There is the error I encountered:

error message:

ERROR in Inference: Failed to load model train-608_best.tflite (Could not load model: Asynchronous connection has been closed)
<_InactiveRpcError of RPC that terminated with:
object-detector-python_1  |     status = StatusCode.UNAVAILABLE
object-detector-python_1  |     details = "failed to connect to all addresses"
object-detector-python_1  |     debug_error_string = "{"created":"@1659425957.027178280","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3217,"referenced_errors":[{"created":"@1659425957.027173640","description":"failed to connect to all addresses","file":"src/core/lib/transport/error_utils.cc","file_line":165,"grpc_status":14}]}"

Environment

Axis device model: P3265-LVE
Axis device firmware version: 10.11.76 (also tried 10.10.73 but didn't work)
SDK VERSION: 1.2.1
docker daemon with Compose: 1.2.3

Please help me, thanks in advance.
Originally posted by @JENNSHIUAN in https://github.com/AxisCommunications/acap-computer-vision-sdk-examples/issues/50#issuecomment-1202143368

We concluded the investigation with the problem of this model.
For hardware limitations, we do not support models that have convolutions that have input and output in fp32 and kernel in int8.
The quantization is not done properly to work on the hardware accelerator.


Switch to gatsby-background-image for background images

partly done in f84d664

Apparently the fetching of gatsby-plugin-ghost-images isn't working properly with Tag pages. I'll dig deeper.


Cleanup handler plugin API

We did not clean up things with the plugin API yet as well as we should.
AC:

[ ] Handlers don't need Authorize or LoadKeys method
[ ] Handlers have minimal set of (or have cleaned up) fields
[ ] Connection managers use the same constructor as handlers/listeners
[ ] EventNotifier should ideally be fully in the plugin manager.

This issue is moot after the recent changes - closing the issue now.


dataset is too large

I'm running into difficulty uploading the dataset to github, which is probably to be expected. Specifically, it's too large (313 MB). Some ways around this:

The error message suggests using Git Large File Storage: https://git-lfs.github.com Has anyone used this? Does it require the downloader to also install this? I don't want to create added steps for anyone using ML5.
We could assume that a third party will generally host datasets, and then write scripts or functions so that users can download and process the data from those sites. The downside of this is keeping the scripts updated, and not necessarily having data that ML5 can always refer to/control, especially for use with any examples that use it.

Thoughts?

We could also make any included datasets super small toy datasets, which would probably be anything <1000 images.

I've used git lfs a couple of times. It works, but the downside is that it has quotas and you need to pay to get more. Often doing git lfs pull will throw:
batch response: This repository is over its data quota. Purchase more data packs to restore access.

Another option, if the files are just 313MB, is to partition them in 4 files and then have a script that rearrengenes them into one file.
You can use something like:
 split -C 20m --numeric-suffixes input_filename output_prefix

creates files like output_prefix01 output_prefix02 output_prefix03 ... each of max size 20 megabytes.

What about the following?

We include smaller "toy" versions of the datasets on github.
We host the larger datasets via some cloud based thing and include shell scripts that download the datasets automatically in github with instructions for how to run the shell scripts?

I think managing the giant files in github may end up being more of a hassle than its worth and not really what git/github is intended for?
Would an S3 bucket do? We can use ITP's account!

I think that makes sense! I agree that we don't want giant files in github. The whole point is ease and simplicity, so I'll cut the dataset to a more manageable size for now, and we can talk about the logistics of hosting the larger datasets next week!


Filter and RT management

Filters are doing immediate render target rendering. In fact the whole RT arch needs a little care to be very effective. We have excellent results here with what we hint:
The RT should be
1- pooled by size
2- and double buffered
Bonus :
3- accessed and finished rendering before main scene would be a must
Super bonus :
Scene resize,event, translation should work with h2d.Mask so that we can send scene to an rt very easily. We made dirty patches so we know this can work. This would make deferred rendering trivial giving us a Biiiiiiig conceptual power.

not relevant as a general way of working for heaps as is, I close.


how to detect xdg-open event?

Good day, i`am trying to do some actions when page.on('load',...)  event is detected. But if i open page with xdg-open that event never detects. Is there option to detect and answer to xdg-open window?
Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.3.0
Platform / OS version: ubuntu 16.04
URLs (if applicable):
Node.js version: v8.8.1

What steps will reproduce the problem?
headless: true with await page.setRequestInterception(true);
open page with such code "",
its not a typo "httk://google.com', when such redirect is presented, it tries xdg-open(in headless=false, or real browser). And i cant detect page.on('load',...) event.
What is the expected result?
i expect to get some event of xdg-open, or page.on('load',...)

Is there option to detect and answer to xdg-open window?

@RuslanTT the xdg-open is the extension point for third-party apps to handle URL navigations. These are outside of WebPlatform, so this functionality is not exposed through pptr.
If you need this functionality for testing, the way to go would be to setup an environment with a custom xdg-open handler that will report requests to your testing framework.
Hope this helps.


Revert this?

https://github.com/cresset-template/cresset/blob/8cf80400f849384a0b6a30f15ca483f09344ad02/Dockerfile#L100-L101

Maybe revert to prepending /opt/conda/bin to $PATH? It turns out that this is not the problem when compiling PyTorch.

The problem was CMAKE_PREFIX_PATH, which has been commented out. Also, the update-alternatives paradigm is already available elsewhere in the project.


Update 2023-08-01-preview swagger for workspaceRP

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@rkmanda is it possible to get this PR reviewed? it's been in the queue for many days, thanks~

      "description": "Url for the discovery service to identify regional endpoints for machine learning experimentation services",

consider + format uri

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/workspaceRP.json:3393 in 9019e04. [](commit_id = 9019e049fc9e841c20a412f0b93dfecfc225ce56, deletion_comment = False)

/pr RequestMerge

SDL Changes still need to be approved here.

/pr RequestMerge


cleaning up the UI

files changes are in SCNNode+Text  and ViewController

I can't merge this but it LGTM. please transfer the repo to me (settings > general > transfer > 'stevemart') and I can then transfer it to github.com/IBM.


Reuse the same module to display images that are not wallpapers. Adde…

Reuse the same module to display images that are not wallpapers. Added a new config param to select if the module is used as wallpaper or simple image.
See usage example in the attached image. The module is used for both the wallpaper and the bottom left image. It's pulling images from a web server where I have security cameras. It's pulling every 2 seconds.

My configuration for this double use:
{
	module: "MMM-Wallpaper",
	position: "fullscreen_below",
	config: { // See "Configuration options" for more information.
		source: "http://localhost:1080/Mountain?crop=144,130,2700,1520",
		updateInterval: 10 * 1000,
		filter: "none",
		addCacheBuster: true,
		crossfade: false,
		wallpaper: true,
	}
},
{
	module: "MMM-Wallpaper",
	position: "bottom_left",
	config: { // See "Configuration options" for more information.
		source: "http://localhost:1080/FrontDoor?crop=0,0,460,360&rotate=270",
		updateInterval: 10 * 1000,
		filter: "none",
		addCacheBuster: true,
		crossfade: false,
		wallpaper: false,
	}
},

The wallpaper uses is still the default one and should work as before. For the new image use, you need to set wallpaper: false in the config file.

I've been wanting to be able to do this for a while, but I think I want to implement it in a different way.  Can you check out the fillRegion branch and see if that works for you?  I think if you just change the instance you have in bottom_left to fillRegion: false, it will do what you want, since you're already getting a 360x460 image.

Yeah it look similar, the idea being that we want a div that does set absolute position/dimensions.

Solved in a different way


Since 2021-02-24, disk_alarm_threshold does not accept integer values anymore

Hi Connor (@coro),
In your commit bd07ab63 dated 2021-02-24, you have implement some restrictive regexp validation to the rabbitmq-server.disk_alarm_threshold property of the rabbitmq-server job.
The problem is that Integers were properly supported for this setting before (as advertised in the job's spec), and aren't anymore. Line 24 of the new 10-clusterDefaults.conf.erb file, the threshold.match invocation will break if threshold is an integer.
I know mem_relative is recommended in the Pivotal Tile, but in BOSH-Lite environments at our company, we don't want to specify this threshold as a relative percentage of the total RAM, because we don't wan't this settings to depend on what amount of RAM has actually been allocated to the overall to BOSH-Lite environment.
Could you please update this ERB file in order to accept integer values for rabbitmq-server.disk_alarm_threshold? Thanks!
Best

Any news on this?

Hi @bgandon, this went under our radar, I'll bring it up to the team.

Hello @bgandon , apologies for missing this and thanks to @Zerpet for bringing it up. Could you give me an example of a value of this field that no longer works? The commit was intended to be backwards compatible, i.e. if you previously provided a value that doesn't match the mem_relative regex like 500Mi, it would be applied to the config as disk_free_limit.absolute - 500Mi. In your case, an integer should be mapped to this absolute value, as in the example configs at https://www.rabbitmq.com/disk-alarms.html#configure.

In case that's not clear - here is a unit test demonstrating what I mean. If you were specifying just an integer here, it should be mapped to disk_free_limit.absolute.
https://github.com/pivotal-cf/cf-rabbitmq-release/blob/3a4aab87796ef9d2fc98415a521f5936c5246783/spec/unit/templates/10-clusterDefaults_spec.rb#L67-L77

I'm closing this issue as it's been stale a while. Please let us know if the snippet above doesn't help you.


Link to the flight-manual instead of duplicating documentation

Description of the Change
The documentation in the flight-manual is the same as this and the flight-manual is the preferred place to have documentation in. This changes the documentation to just be a link to the flight-manual.
/cc: @laurmurclar This answers your question about preferred location for documentation 🙂
Benefits
Not duplicating documentation but leave the old document in place in case there are links or bookmarks to it.

Thanks for taking care of this @Ben3eeE :bow:


Toolchain selection

Fixes #756

Haven't looked at code in any detail as I'm doing this on my phone. I assume you have included a valid state where there is no toolchain.
Instead of checking do we have a toolchain everywhere why don't you create two stages to the extension initialisation one for the toolchain and one for the rest. At initialisation if you have no toolchain you are forced through the select toolchain UI and the rest of the extension doesn't initialize until a toolchain is either downloaded or selected.

Haven't looked at code in any detail as I'm doing this on my phone. I assume you have included a valid state where there is no toolchain.
Instead of checking do we have a toolchain everywhere why don't you create two stages to the extension initialisation one for the toolchain and one for the rest. At initialisation if you have no toolchain you are forced through the select toolchain UI and the rest of the extension doesn't initialize until a toolchain is either downloaded or selected.

Fair point. I've made it so that the WorkspaceContext doesn't even get created if there's no available toolchain. This allows us to keep relatively the same behaviour as before this patch. However, the command registration now takes an optional WorkspaceContext and will display the toolchain error message if commands are invoked without a WorkspaceContext. I've also moved some of the functionality that doesn't require a toolchain outside of the WorkspaceContext (e.g. the reload extensions notification).

So far tested this on macOS (Although I didn't test with multiple Xcode's installed) and works quite well. One minor issue, if you have a local toolchain and then select a new toolchain but set it globally you are still using the original local toolchain. I think you should probably clear the local setting here, or add another dialog to ask do you want to clear it.
I'll do a code review later, but I did see a lot of the code is still dealing with possibility of an undefined toolchain, folder context etc, which should be unnecessary now given your description of the changes you made.

So far tested this on macOS (Although I didn't test with multiple Xcode's installed) and works quite well. One minor issue, if you have a local toolchain and then select a new toolchain but set it globally you are still using the original local toolchain. I think you should probably clear the local setting here, or add another dialog to ask do you want to clear it.
I'll do a code review later, but I did see a lot of the code is still dealing with possibility of an undefined toolchain, folder context etc, which should be unnecessary now given your description of the changes you made.

So, I did some more investigation into this. It appears that settings for individual workspace folders are actually ignored for swift.path. I've removed the option to configure workspace folder settings and added a warning about workspace settings taking precedence over user settings.
@adam-fowler could you take one more look at the code and see if we're good?


python code updated to python 3

I updated autoPlay.py (Chapter 5, serialOrgan) for python 3 (and skipped the serialorgansongs.jottit.com lines since that site no longer exists) and added some notes for figuring out the current serial port. Thanks so much for this wonderful book!
## Scripting in python to drive the serial-port organ

## So far, the "protocol" is simple.
## Python routine sends a note, waits for a return character, then sends next, etc.
## Organ listens for notes, when it gets one sends an 'N' to say it's ready

import serial

def playString(noteString, serialPort):
  for letter in noteString:
    print(letter)
    serialPort.write(letter.encode())
    returnValue = serialPort.read(1)

if __name__ == "__main__":

  import time
  from urllib.request import urlopen

  ## Need to consider alternatives for Mac / Windows
  ## list all serial ports being used: python -m serial.tools.list_ports
  PORT = "/dev/cu.usbserial-14130" # Change this to the current serial port being used
  BAUD = 9600

  s = serial.Serial(PORT, BAUD)
  s.flush()
  ## flush clears the buffer so that we're starting fresh
  ## More on serial buffers later.

  ## An intentional example.    You can just type stuff and see what comes out.
  playString("hello there, this is a random string turned into 'music'", s)
  input("Press enter for next demo\n")

  ## Website no longer alive... skipping:
  ## A really frivolous example.  Play websites!
  ## Bonus points for first person to tweet themselves a song.
  #print ("Downloading song data from http://serialorgansongs.jottit.com/...")
  #import re
  #contentFilter = re.compile(r'<p>(.*?)</p>')
  #songSite = urlopen("http://serialorgansongs.jottit.com/").read()
  #songText = contentFilter.findall(songSite)[0]
  #playString(songText, s)

  ## Or interactive
  mySong = input("\nType in your own song: ")
  playString(mySong, s)

I updated Chapter 6's bossButton.py for python 3. The only changes were to add the parenthesis to change the response logic from:
if response = 'X'
to:
if response = b'X'
## Simple demo
## Sits forever listening to serial port
## When you press button, opens website of your choosing.
## Extend this to many buttons and you'll have a physical
##  web-launcher.

BOSS_SITE = "http://www.cartalk.com/content/boss-redirect"
## or perhaps more topical...
XKCD = "http://xkcd.com/353/"

SERIAL_PORT = "/dev/cu.usbserial-14130"
BAUD_RATE = 9600

import serial
import webbrowser

sp = serial.Serial(SERIAL_PORT, BAUD_RATE, timeout = 5)
sp.flush()
print("Boss Button")

while(1):                 # Sit and wait forever
    response = sp.read(1) # get one byte
    if response == b'O':
        print("Got OK Byte.  Waiting for button press.")
    elif response == b'X':
        print("Got Boss Byte!  Alarm!")
        webbrowser.open(BOSS_SITE)
    else:
        print("Got nothing.  Still waiting.")

I updated Chapter 6's bossButton.py for python 3. The only changes were to add the parenthesis to change the response logic from:
if response = 'X'
to:
if response = b'X'
## Simple demo
## Sits forever listening to serial port
## When you press button, opens website of your choosing.
## Extend this to many buttons and you'll have a physical
##  web-launcher.

BOSS_SITE = "http://www.cartalk.com/content/boss-redirect"
## or perhaps more topical...
XKCD = "http://xkcd.com/353/"

SERIAL_PORT = "/dev/cu.usbserial-14130"
BAUD_RATE = 9600

import serial
import webbrowser

sp = serial.Serial(SERIAL_PORT, BAUD_RATE, timeout = 5)
sp.flush()
print("Boss Button")

while(1):                 # Sit and wait forever
    response = sp.read(1) # get one byte
    if response == b'O':
        print("Got OK Byte.  Waiting for button press.")
    elif response == b'X':
        print("Got Boss Byte!  Alarm!")
        webbrowser.open(BOSS_SITE)
    else:
        print("Got nothing.  Still waiting.")

Chapter 7's serialScope.py updated for python 3:
import serial

def readValue(serialPort):
    return(ord(serialPort.read(1)))

def plotValue(value):
    """ Displays the value on a scaled scrolling bargraph"""
    leadingSpaces = "-" * int(value*(SCREEN_WIDTH-3) / 255)
    print(f"{leadingSpaces} {value:03}")

def cheapoScope(serialPort):
    while(1):
        newValue = readValue(serialPort)
        plotValue(newValue)

if __name__ == "__main__":

    PORT = '/dev/cu.usbserial-14230'
    BAUDRATE =  9600
    TIMEOUT = None
    SCREEN_WIDTH = 80

    ## Take command-line arguments to override defaults above
    import sys
    if len(sys.argv) == 3:
        port = sys.argv[1]
        baudrate = int(sys.argv[2])
    else:                        # nothing passed, use defaults
        print ("Optional arguments port, baudrate set to defaults.")
        port, baudrate = (PORT, BAUDRATE)

    serialPort = serial.Serial(port, baudrate, timeout=TIMEOUT)
    serialPort.flush()
    cheapoScope(serialPort)

Chapter 7's serialScope.py updated for python 3:
import serial

def readValue(serialPort):
    return(ord(serialPort.read(1)))

def plotValue(value):
    """ Displays the value on a scaled scrolling bargraph"""
    leadingSpaces = "-" * int(value*(SCREEN_WIDTH-3) / 255)
    print(f"{leadingSpaces} {value:03}")

def cheapoScope(serialPort):
    while(1):
        newValue = readValue(serialPort)
        plotValue(newValue)

if __name__ == "__main__":

    PORT = '/dev/cu.usbserial-14230'
    BAUDRATE =  9600
    TIMEOUT = None
    SCREEN_WIDTH = 80

    ## Take command-line arguments to override defaults above
    import sys
    if len(sys.argv) == 3:
        port = sys.argv[1]
        baudrate = int(sys.argv[2])
    else:                        # nothing passed, use defaults
        print ("Optional arguments port, baudrate set to defaults.")
        port, baudrate = (PORT, BAUDRATE)

    serialPort = serial.Serial(port, baudrate, timeout=TIMEOUT)
    serialPort.flush()
    cheapoScope(serialPort)

Hiya!  That's lovely!  I'll roll those into the code.
(I haven't been doing as much maintenance on this codebase as I probably should.  Thanks for helping out.)

Hiya!  That's lovely!  I'll roll those into the code.
(I haven't been doing as much maintenance on this codebase as I probably should.  Thanks for helping out.)


Redis module for command bumper has wrong default prefix

Tiny bug. While traversing your code I visually spotted that the default prefix in the command bumper for redis is still set to "aggregatelock". You probably want something like "commandbumper" instead.
(Off-topic: Aside from that, GREAT work on all of your cqrs-related modules, @adrai! For broad acceptance and understanding you'll need plenty more documentation, but it's getting there. I would suggest making some visuals instead of just text, to more easily spot how everything interacts. I can try to help out at some point when I can.)

For sure! Thanks!
ANY type of contribution is helpful! :-)
Il giorno 24-dic-2015, alle ore 10:13, Hilke Heremans <notifications<EMAIL_ADDRESS>ha scritto:
Tiny bug While traversing your code I visually spotted that the default prefix in the command bumper for redis is still set to "aggregatelock" You probably want something like "commandbumper" instead
(Off-topic: Aside from that, GREAT work on all of your cqrs-related modules, @adraihttps://github.com/adrai! For broad acceptance and understanding you'll need plenty more documentation, but it's getting there I would suggest making some visuals instead of just text, to more easily spot how everything interacts I can try to help out at some point when I can)

Reply to this email directly or view it on GitHubhttps://github.com/adrai/node-cqrs-domain/issues/64.


Rewords teos to use RWLocks

This basically add RWLocks to:

Gatekeeper
Responder
Watcher

Before this PR, the InternalAPI has a RWLock to guard the access to the backend. However, two threads are running for each of the main backend components (Watcher and Responder), meaning that, theoretically, their do_watch method could crash with the user data feeding (add_appointment and handle_breach). This tries to fix that.
For the Gatekeeper:
The writer lock is acquired for the data addition/update (add_update_* and update_outdated_users_cache) and deletion (delete_appointments). The reader lock is acquired for data querying (authenticate_user, has_subscription_expired and  get_outdated_users).
For the Responder:
The writer lock is acquired for add_tracker (called by handle_breach) and for a part of do_watch and handle_reorgs. Notice that the whole do_watch cannot be covered in a single piece since handle_reorgs may call handle_breach and lead to a deadlock.
For the Watcher:
The writer lock is acquired for the most part of add_appointment and do_watch, whereas the reader lock is acquired for get requests.
Given the Watcher is the entry point to the backend, and it interacts with the Responder and the Gatekeeper to get data, it acquires their locks for that directly (given there are no getters).
The Watcher's block cache is maintaining is own RWLock, even though it could be  arguably removed.

@bigspider this may be a bit tricky to review

Yeah, I was trying to avoid adding getters for those, but I guess it actually makes sense from a cleaner design POV.


Update the read me.

Hey, maybe you can update the release version on the readme. Nice work otherwise.

Thank you!  I have updated it.


Release of v1.0.5

Coverage decreased (-0.07%) to 68.62% when pulling 9b5ae06dd955775a70c63430ed00c353bba0dedc on releases into acc0e67d14214a758491d6ea282880695a98d4c0 on develop.


Devs want to create public interfaces for EngagementLauncher

Jira issue:
https://glia.atlassian.net/browse/MOB-3588
What was solved?

Create interfaces for EngagementLauncher
Create a basic ConfigurationManager that should hold all the init configs

Release notes:

[ ] Feature
[x] Ignore
[ ] Release notes (Is it clear from the description here?)
[ ] Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

[ ] Is the feature sufficiently tested? All tests fixed? Necessary unit, acceptance, snapshots added? Check that at least new public classes & methods are covered with unit tests
[ ] Did you add logging beneficial for troubleshooting of customer issues?
[ ] Did you add new logging? We would like the logging between platforms to be similar. Refer to Logging from Android SDKs → Things to consider for newly added logs in Confluence for more information.

Screenshots:

[!IMPORTANT]
I made several important changes.

I added a public interface for EntryWidget because I think it is important to have it at this stage so that we can understand our architecture clearly.
Changed implementation  a bit

!squash


Skuznets/bump upstream

/retest

/retest

/retest

@dinhxuanvu Hmmm...  It passes upstream, and I had my stuff downstreamed for testing in #570 and #571, where those changes successfully passed the e2es. So, not sure what's happening. I did see some of the original e2e's failing because we couldn't deploy on EC2.

@dinhxuanvu I think I know what's going on... and it's due to the combination of #570 and #571 not being tested together.
Downstream sets a value via the CLI, which effectively changes the default value; and that isn't handled properly.

@dinhxuanvu I think I know what's going on... and it's due to the combination of #570 and #571 not being tested together.
Downstream sets a value via the CLI, which effectively changes the default value; and that isn't handled properly.

I see. Just a reminder is that ClusterOperator API is a downstream API (OpenShift specific) so this type of problems usually won’t surface on upstream.

Let put a hold here until Todd resolves this issue fully.
/hold

I see. Just a reminder is that ClusterOperator status is a downstream API (OpenShift specific) so this type of problems usually won’t surface on upstream.

It was packageserver, which is an upstream component, that's crash looping.

I see. Just a reminder is that ClusterOperator status is a downstream API (OpenShift specific) so this type of problems usually won’t surface on upstream.

It was packageserver, which is an upstream component, that's crash looping.

Yes the component in trouble was packageserver but the error that blocked the test was from ClusterOperator API which reported packageserver was not ready.

But if packageserver wasn't crashing in the first place....
But, packageserver has been fixed upstream, so @stevekuznetsov should re-run the script.

Haha. I wasn't contradicting you on the root cause, only on the way the error surfaced up.
Anyway, the issue should be resolved now so rebase this PR and continue.

See #573

/close


[UI] MesheryFilters/FilterCard  : Add Download Button to Filter Card

Notes for Reviewers
This PR fixes #CU-85ztd2m9f
Added Button to download wasm binary .

Signed commits

[x] Yes, I signed my commits.

Task linked: CU-85ztd2m9f Create a download button for the wasm binaries

@aabidsofi19 did you include support for dark mode, too?

Does this grid's responsiveness include an update for this new button?

Related: Please make sure that the Clone button maintains aspect ratio on smaller screen widths, @aabidsofi19

@ritiksaxena124 is this the right set of colors?

@aabidsofi19 any reason that this button deviates from the existing icon? Let's avoid the potential confusion this will mean for users.

@aabidsofi19 did you include support for dark mode, too?

working fine , btn turns teal and fill is white

@aabidsofi19 any reason that this button deviates from the existing icon? Let's avoid the potential confusion this will mean for users.

This looked a bit better as this is a big btn , if it's confusing let's avoid it ..

@leecalcote  @@senali-d  I left the button grid unmodified since it has five columns. However, it's not fully responsive on mobile devices, causing the button text to overflow even without adding a new button. Considering that we will likely have a maximum of three buttons ("publish/unpublish," "download," and "clone"), I suggest using three columns for mobile devices.

@aabidsofi19 we will have more than three buttons. Make the card responsive. Don't allow spill over.

@aabidsofi19 we will have more than three buttons. Make the card responsive. Don't allow spill over.

@leecalcote  then should we truncate text on mobile as well  .

do it: remove the text

https://github.com/meshery/meshery/assets/65964225/1e8cab47-d3b5-435c-b241-bf6920cb232b

@aabidsofi19 looks to me, small changes

The color that we are using for the text "Modified on: July 7, 2023 10:34 AM" i.e., #607d8b is not our brand color could you update it to color Hoki (#677E88) please? Other colors used are good
On smaller screens the download icon is not in center

@aabidsofi19 looks good to me, small changes

The color that we are using for the text "Modified on: July 7, 2023 10:34 AM" i.e., #607d8b is not our brand color could you update it to color Hoki (#677E88) please? Other colors used are good
On smaller screens the download icon is not in center
Don't import icons from Material UI instead use the JS version of the SVG

3rd change will need refactoring of more than 10-15 components , lets do it in a separate pr .

@ritiksaxena124  we are using primary  for modifed on subheading :confused

@ritiksaxena124 we are using primary for modifed on subheading :confused

Yes, the Hexcode for primary needs to be updated

@ritiksaxena124 we are using primary for modifed on subheading :confused

Yes, the Hexcode for primary needs to be updated

in the theme/app.js

@ritiksaxena124 what should be the main , dark and light variant for it

we are using blueGrey for both dark and light and we can replace it with "Hoki". it will work in both dark and light mode as the current color and hoki has a very slight difference

there is no Hoki color exported from mui :

@ritiksaxena124

there is no Hoki color exported from mui :

Don't use MUI colors, @aabidsofi19. Use our theme colors. Import the theme.

there is no Hoki color exported from mui :

Don't use MUI colors, @aabidsofi19. Use our theme colors. Import the theme.

@leecalcote  thats right ,@ritiksaxena124   asked to change the primary color in theme from blueGreen to "hoki" . But I can't find the color anywhere .. rest assured we are not importing colors from mui in these components .

@ritiksaxena124 we are using primary for modifed on subheading :confused

Yes, the Hexcode for primary needs to be updated

fixed it .


Track 'Failed analysis' event

It would be really interesting tracking when an analysis fails and relating it with the user.
This new segment event should include (if possible) all the common event attributes in addition to these specific ones:

analysis_id: Id of analysis (at present is same as natural id but it will change in the future)
analysis_natural_id: Id of análysis as seen by user (allows to identify the analysis pipeline)
analysis_type: type of performed analysis
failure_cause: reason of failure (I don't know if we can get this info)
vis_id: id of the derived visualization
object_created_at: visualization creation timestamp
lifetime: lifetime of map (in days)
privacy: privacy of map
type: always 'derived' for this type of event

cc'ed @xavijam, @gfiorav

@rochoa is this still a good approach?

Stale issue. Closing 👋


Uses existing keys if none provided again on load for json data

Finishes #1652
Frankly, I think I might agree with @aendrew's comment in that forcing the user to specify every time might actually be preferable... but I was looking for a way to get involved in the project so I picked this one up. 😆

[Current coverage][cc-pull] is 64.16%

Merging [#1748][cc-pull] into [master][cc-base-branch] will increase coverage by 0.11%

@@             master      #1748   diff @@
==========================================
  Files             1          1
  Lines          4400       4403     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2818       2825     +7
+ Misses         1582       1578     -4
  Partials          0          0

Powered by Codecov. Last updated by [223404a...0ec5643][cc-compare]
[cc-base-branch]: https://codecov.io/gh/c3js/c3/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/c3js/c3/compare/223404a79246c61d150d8a209dbdc81f6955083b...0ec56436cb22bd93fa4ecf59a4be719c53fccc23
[cc-pull]: https://codecov.io/gh/c3js/c3/pull/1748?src=pr


[Bug]: There is a duplicate functionality for closing the message input which is not required

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
@subinoybiswas There is a duplicate functionality for closing the message input which is not required and any one can be eliminated. (the cross icon or the close button)
Expected behavior
any one close option can be eliminated
Add ScreenShots

On which device are you experiencing this bug?
Windows
Record

[X] I have read the Contributing Guidelines
[X] I want to work on this issue

Sure go ahead and fix it


Make MetastoreRelation#hiveQlPartitions lazy val

Merged build triggered.

Merged build started.

Test build #37625 has started for   PR 7466 at commit d0bb9d6.

Test build #37625 has finished for   PR 7466 at commit d0bb9d6.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class UnsafeProjection extends Projection
case class FromUnsafeProjection(fields: Seq[DataType]) extends Projection
abstract class BaseProjection extends Projection
    class SpecificProjection extends $
    class SpecificProjection extends $

Merged build finished. Test PASSed.

Covered by #7421


Utils Playground

Adding a new utils path for the site where I'll add some simple tools.


update readme with sample app features

there are some booleans on the left pane which obviously have some effect on the video, which I dont know about. as you can see in the picture.

so it would be great if we can know the details of them hence we can decide when and how we should use them in our apps , or should all of them just be pushed to true?

I understand what exact seek for exact frame does, it extracts frame exactly at the spot of the playing video, and if off then a random frame is picked right? But I dont understand what other toggles are doing, all of those passthrough toggles and allow Iyuv Video Output?

For the frame grabber, you always have to specify a position. The sample uses the playback position, but in code you can specify any position. If you set Exact Seek to false, then the frame grabber will grab the next key frame before that position. This will be very fast, but it is usually not exactly the position you gave it. If you set it to false, it will decode from the key frame until it reaches the exact position you specified. This means it has to decode mutliple frames until it reaches the exact position. This can be quite a lot slower, depending on the file and codec. For most use cases (including seek preview), it will be better to set this to "false".
All other options should be left at default. Passthrough means that the lib does not decode this format with ffmpeg and passes the encoded packets to the MF engine instead. This allows MF to do hardware decoding if possible, which is a lot faster if available. It makes sense to add settings in your app to disable passthrough for specific formats, since some PCs might have problems with hardware decoding.
Passthrough for audio usually does not make sense, except if you run on a phone which might have a HW decoder for MP3 or AAC.

@lukasf  so what does passthrough actually means? it means tht for that format it will try to use hardware acceleration? yes these options can be provided in the app, but a normal user of a media app will not know wht to do with these settings, so I think as developer we need to know wht should be the best for most use case scenarios? so we can set them accordingly in code behind. so the default values as in the sample app are best for most use cases right? and in code behind we can check if device is phone then we can passthrough the audio decoders as well.

I mean user may understand mp4, mkv extensions but they usually don't know wht H264 etc means

The defaults are set to what makes sense for most users. It depends a bit on your target audience if you want to expose ways to change this. There are also technically advanced users who want to fine-tune app settings, and they will sure know what H264 or HEVC means.  But if you add this, you should probably put it in some "expert settings" area or whatever. Users should only touch them if they know what they are doing.

perfect thanks for clarification @lukasf

BTW, the sample is just for developer purposes, so there is no point in being overly user friendly, these properties match the ffmpeg config object.


Handle context cancellation

#7  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @vegarsti and the rest of your teammates on  Graphite


xxd: crash with higer number of column

xxd writes the data into a buffer before printing. Unfortunately the buffer doesn't consider the space consumed by the escape sequences used to change the color of the character.
BEFORE:
$ xxd -Ralways -c 256 /etc/passwd
Segmentation fault (core dumped)
AFTER:
$ ./xxd -Ralways -c 256 /etc/passwd
00000000: 726f 6f74 3a78 3a30 3a30 3a72 6f6f 743a 2f72 [...]
To solve this issue I had to increase the size of the buffer considering for each byte of data 11 further characters for the color escape sequence.

thanks, makes sense.


Validation attribute "on" only accept a string not a symbol

According http://mongoid.org/en/mongoid/docs/validation.html you can do something like
validates :foo, presence: true, on: :create
validates :bar, presence: true, on: :update

what is in consistence with the behaviour of active record. But in my case (mongoid-4.0.1) it failed. After fiddling around I found out that it works with strings.
validates :foo, presence: true, on: 'create'
validates :bar, presence: true, on: 'update'

So in my honest opinion,  I state this as a minor bug. When I have time, I'll fix it but in the mean this ticket should be a hint for other users stepping in this trap.

Turned out that this wasn't the problem. Strings does not work so it don't validate then and create and update are dependent. I guess no create without an update or something else.


feat: initial escrowing example

Initial escrow flow showcasing one way to address #5864
Replaces the blacklist token with an escrowable blacklist token. Additional tests cases of escrowing should be created to showcase the usage better in separate PR's.

#6632  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @LHerskind and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

app_circuit_proving_time_in_ms (Token:transfer): 53,991 (+26%)
protocol_circuit_proving_time_in_ms (private-kernel-reset-small): 43,628 (+74%)
protocol_circuit_size_in_gates (private-kernel-reset-small): 2,097,152 (+100%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256
5,712
1,551
712
774
776 (+1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,464
9,464
9,452

l1_rollup_execution_gas
616,105
616,105
616,093

l2_block_processing_time_in_ms
1,360 (+1%)
5,070 (-1%)
10,087

l2_block_building_time_in_ms
47,715 (+3%)
188,806 (+2%)
377,470 (+2%)

l2_block_rollup_simulation_time_in_ms
47,546 (+3%)
188,169 (+2%)
376,202 (+2%)

l2_block_public_tx_process_time_in_ms
25,550 (+3%)
106,374 (+2%)
217,595 (+2%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
9,939 (-1%)
15,166 (-1%)

node_database_size_in_bytes
14,463,056
21,364,816

pxe_database_size_in_bytes
18,071
29,868

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Circuit
protocol_circuit_simulation_time_in_ms
protocol_circuit_witness_generation_time_in_ms
protocol_circuit_proving_time_in_ms
protocol_circuit_input_size_in_bytes
protocol_circuit_output_size_in_bytes
protocol_circuit_proof_size_in_bytes
protocol_circuit_num_public_inputs
protocol_circuit_size_in_gates

private-kernel-init
160 (+1%)
3,732 (+2%)
22,098
20,502 (+3%)
63,846 (+3%)
88,768 (+2%)
2,707 (+2%)
1,048,576

private-kernel-inner
620 (+3%)
4,285 (+2%)
47,789 (-1%)
91,422 (+3%)
63,846 (+3%)
88,768 (+2%)
2,707 (+2%)
2,097,152

private-kernel-tail
543 (+3%)
2,859 (+1%)
35,930 (+1%)
88,701 (+2%)
77,949 (+2%)
10,624
265
2,097,152

base-parity
6.58
1,343 (+10%)
2,920 (+1%)
128
64.0
2,208
2.00
131,072

root-parity
49.5
54.4 (-14%)
43,912
27,084
64.0
2,720
18.0
2,097,152

base-rollup
806 (+5%)
2,331
73,742 (-1%)
119,578
756
3,648
47.0
4,194,304

root-rollup
114 (-1%)
65.9 (+1%)
19,279 (-2%)
25,297
620
3,456
41.0
1,048,576

public-kernel-app-logic
535 (+3%)
2,832 (-1%)
47,566
105,453 (+2%)
86,814 (+2%)
118,880 (+2%)
3,648 (+2%)
2,097,152

public-kernel-tail
1,201 (+2%)
25,620
154,038 (-1%)
395,898 (+1%)
7,490
10,624
265
8,388,608

private-kernel-reset-small
592 (+3%)
2,247
:warning: 43,628 (+74%)
119,965 (+2%)
63,846 (+3%)
88,768 (+2%)
2,707 (+2%)
:warning: 2,097,152 (+100%)

merge-rollup
28.6 (-1%)
N/A
N/A
16,534
756
N/A
N/A
N/A

public-kernel-setup
635
N/A
N/A
105,453 (+2%)
86,814 (+2%)
N/A
N/A
N/A

public-kernel-teardown
537 (+1%)
N/A
N/A
105,453 (+2%)
86,814 (+2%)
N/A
N/A
N/A

private-kernel-tail-to-public
N/A
9,370 (-4%)
82,931 (+1%)
N/A
N/A
118,880 (+2%)
3,648 (+2%)
4,194,304

Stats on running time collected for app circuits

Function
app_circuit_proof_size_in_bytes
app_circuit_proving_time_in_ms
app_circuit_size_in_gates
app_circuit_num_public_inputs

SchnorrAccount:entrypoint
16,640 (+3%)
46,082
2,097,152
453 (+4%)

Token:transfer
16,640 (+3%)
:warning: 53,991 (+26%)
2,097,152
453 (+4%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
11.5 (+1%)
18.5
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.667 (+1%)
0.569
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
52.4 (-2%)
80.9
264 (+1%)
504 (-1%)
990 (-1%)
1,960
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.536 (-2%)
0.499
0.480 (+1%)
0.471 (-1%)
0.470 (-1%)
0.468
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
62.6
119
376 (-1%)
741
1,471 (-1%)
2,928
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
106
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.543
0.537
0.511
0.510
0.510 (-1%)
0.510
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
67.1

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
107

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.596

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
84,297 (+2%)
665,199

Transaction size based on fee payment method
| Metric |  |
| - |  |
Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
12,187 (+10%)
4,296 (+2%)
63,446 (+10%)

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
8 public data writes

tx_sequencer_processing_time_ms
3,251 (+2%)
2,174 (+2%)
6,127 (+1%)
2,316
2,596 (+1%)

Docs Preview
Hey there! 👋 You can check your preview at https://6659ca0b37abf63056ca2167--aztec-docs-dev.netlify.app

https://link.excalidraw.com/l/918xh05mbiS/AIKmHUXcmiH
For those trying to understand what's happening with all these comments and scenarious

The consensus seems to be that we won't be following this direction as it can be handled at the  app-layer instead and that it might just introduce "too" much complexity for usual transfers.


Conflict with Nodes Template (Foundational right click menu)

Noticed in the latest update of MixLab that the "Node template" right click feature is not available when MixLab is enabled and it becomes available when it is disabled. I think the recent update to the package broke this core functionality. Can you please fix it right away since I use MixLab quite a bit now but Node Templates are critical to my workflow?

Noticed in the latest update of MixLab that the "Node template" right click feature is not available when MixLab is enabled and it becomes available when it is disabled. I think the recent update to the package broke this core functionality. Can you please fix it right away since I use MixLab quite a bit now but Node Templates are critical to my workflow?

Try downloading the latest version from the main repository? This issue has been fixed before.

Hi - I tried that, but unfortunately it's the same issue - see attached video:
https://github.com/shadowcz007/comfyui-mixlab-nodes/assets/142545094/204065fd-df9c-4495-bcc1-a340f4f0ddaf

This issue has been fixed


Resource icons

Great mod! However, the first games I've played with it active have two-to-four icons for a single resource. Is this a known bug, or something on my end? It's really distracting to have say iron but then also have niter, uranium, and copper icons as well. I can post a screenshot if it helps.

This is addressed in this issue: #180 (Fixed in Pull request #181)

In other words, the best way to solve this issue is updating CQUI to the latest nightly. If you're still having issues, consider checking if your game install is up to date or if another mod you've installed is introducing any incompatibilities

Cheers! I'll try the nightly; CQUI is the only mod I'm running currently.


Don't publish too much of ClientApp

CC @mikeharder who noticed this.

@ryanbrandenburg: You might also need to revert:
https://github.com/aspnet/Templating/commit/d95f9716932cae55933c0a4700fec3513c55c92f#diff-7d3194c7a47f8f21106bbc7fe3c1ee29L56

I tested it manually on my machine and we also have tests of the publish scenario so I'd say we're save if you don't have any concerns.

@ryanbrandenburg : No concerns from my side.


Timeout for stack creation

The timeout value for the stack create/update should be cutomizable.
This should be a non mandatory parameter

Hi @mridhul  - Please review this PR - https://github.com/intuit/cfn-deploy/pull/18

Hi @mridhul  - any updates on this?

@codemii . this is closed


Fix co-worker task delegation failure

Oh interesting, I was not aware of this, so this is to make sure the agent being delegated can use the tasks tools?

The problem I was trying to fix is of AgentTools (Delegate work to coworker and Ask question to coworker) not being loaded because of being appended to the task in this method: https://github.com/crewAIInc/crewAI/blob/2fe79e68cde0067b56b8aaf5901cfa50f664238a/src/crewai/crew.py#L733
... causing delegation to not work.

After going through the docs and code again, I realized that delegation is meant for only hierarchical processes and I was trying delegation with a sequential process. That's why it didn't work. Feel free to close this PR if it's not a use-case you want to or makes sense to support.

Oh it was supposed to work on sequential as well, I'll run some tests locally

Just ran into this exact issue, the docs say that delegation should work for Sequential but I was never seeing coworkers being used.
Looking at the proposed change, I think it might read better if _prepare_agent_tools was removed which adds the delegation tasks to the task's tool list (which is a bit weird given allow_delegation is a property of an Agent not a task).
Instead, we can move the manager tool setup into the if self.process == Process.hieracchical in _execute_tasks, and then for the Sequential case use the union logic to join task.agent.tools, task.tools, and task.agent.get_delegation_tools().

Hey @charl3sj!
Thanks so much for the pull request!
Could you take a moment to check if the changes are still valid? We've made quite a few updates since July. If they still apply, I’d be more than happy to help you get everything sorted and make it happen! 😊


urlProp could be optional?

https://github.com/authorizerdev/authorizer-react/blob/1d5f8f345c318dcfa5672e63bfe55d01d71d569a/src/components/AuthorizerBasicAuthLogin.tsx#L23
Do you think urlprops would be optional? so that I can use the component without assign them?

Sure makes sense,
I will fix that in upcoming release

#37 fix here

@kdichev @peter-wd-1 I have released this as part of<EMAIL_ADDRESS>