[🐞Bug]: place-items-center is not working when attributifying grid and flex

UnoCSS version
latest
Describe the bug
Below is not working for place-items-center. It should be supported in both grid and flex, just like justify-center, items-center, justify-items-center and content-center
<div h-50vh grid="~ place-items-center">
  Should be centered, but doesn't work
</div>

<div h-50vh grid="~ justify-items-center items-center">
  justify-items-center and items-center works
</div>

Reproduction
https://unocss.dev/play/?html=DwEwlgbgBAFgtAVgAwRlA5gJzCAvAIgD8oAHAGwEMBjAUzjABcaBbAZzloDsnN8A%2BAFBQoAZRgB7AK5kQUAEY0oXHjRAAaeZIZQQ4mq04BybQHdxmANYDgAenARB1%2B7EQo0WHAWIArSawZgAGYAnvRMbBw03DSYUIws7Mox-EJQvv5BofERSbEUnLLZiVE8UGaWrNZ2kIJAA&config=JYWwDg9gTgLgBAbwFBzgEwKYDNgDsMDCEuOA5gDQpxhQYDOGMAqrhJajfYwIIwxTAARgFcYwLAE8kAXzhYoEEHADkw1gGM6dZUlCRY1WgxgAlDCAAqEAAoAPOQqXKAAmoia6Aek7GAtLRBfGAhfMFsdJCQMW314TCwAQ2EAGzjsPEJiMgAKZA4jRjoALjgAbSp8rmZWbIBKdlRDKt5%2BIVFxCTqqAF0ZWqQgA&css=PQKgBA6gTglgLgUzAYwK4Gc4HsC2YDCAyoWABYJQIA0YAhgHYAmYcUD6AZllDhWOqgAOg7nAB0YAGLcwCAB60cggDYIAXGBDAAUKDBi0mXGADe2sGC704AWgDuCGAHNScDQFYADJ4Dc5sAACtMLKAJ5gggCMLPK2ABR2pPBIcsoAlH4WAEa0yADWTlBYqEw2yFjK3Bpw5LxxAOTllVDoYpSMYgAs3vUZ2gC%2BmsBAA&options=N4IgTgpgzgDg9gOygSwG4RALgGYEMA2UEANCAC5i5LZxgC2AEmXflnoSeZdbXQMIBXKGTj8AymLYEiAXyA
System Info
N/A
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

https://unocss.dev/play/?html=DwEwlgbgBAFgtAVgAwRlA5gJzCAvAIgD98oAHAGwEMBjAUzjABdaBbAZzjoDtnMA%2BAFBQoAZRgB7AK7kQUAEa0o3XrRAAaeZMZQQ42my4BybQHdxmANYDgAenARB1%2B7EQo0WHAUJQAVpLaMYABmAJ4MzOyctDy0mFBMrBzKsfiCwn4BwWEJkclxlFyyOUnRvFBmlmzWdpCCQA&config=JYWwDg9gTgLgBAbwFBzgEwKYDNgDsMDCEuOA5gDQpxhQYDOGMAqrhJajfYwIIwxTAARgFcYwLAE8kAXzhYoEEHADkw1gGM6dZUlCRY1WgxgAlDCAAqEAAoAPOQqXKAAmoia6Aek7GAtLRBfGAhfMFsdJCQMW314TCwAQ2EAGzjsPEJiMgAKZA4jRjoALjgAbSp8rmZWbIBKdlRDKt5%2BIVFxCTqqAF0ZWqQgA&css=PQKgBA6gTglgLgUzAYwK4Gc4HsC2YDCAyoWABYJQIA0YAhgHYAmYcUD6AZllDhWOqgAOg7nAB0YAGLcwCAB60cggDYIAXGBDAAUKDBi0mXGADe2sGC704AWgDuCGAHNScDQFYADJ4Dc5sAACtMLKAJ5gggCMLPK2ABR2pPBIcsoAlH4WAEa0yADWTlBYqEw2yFjK3Bpw5LxxAOTllVDoYpSMYgAs3vUZ2gC%2BmsBAA&options=N4IgTgpgzgDg9gOygSwG4RALgGYEMA2UEANCAC5i5LZxgC2AEmXflnoSeZdbXQMIBXKGTj8AymLYEiAXyA

@Simon-He95 Yeah I got the idea it's working when standalone, but

I prefer to group corresponding utilities into a set e.g. (flex, grid)
It doesn't make sense that place-items is the only one that's not supported. i.e. either we support it, or we should drop support for others too (items-*, justify-*, etc.)
⚠There's a current bug in JSX preventing me using that standalone syntax without ="": https://github.com/unocss/unocss/issues/3471

So I believe this is truly a BUG / Feature Request, which should not be closed.

Got it～，I'll check it out later

I do want to send a PR but unfortunately I can't really understand how attributify actually works in a short period😥.
I'll learn from how this is being resolved. ☺

@Simon-He95 Emm, so, the attributify is just modifying the extractor but nothing else right? For why flex="items-center" works, it's because className="flex-items-center also works.
In other words, for a given key="value" pair, it's the same as key-value or key:value (based on separators or rules defined) in string format right?
If I'm correct with above, it then makes a lot of sense how it works. I was trying to find how to fix it in the preset-attributify package but essentially that's not where it should be. 🤣

flexGridJustifiesAlignments
The reason I modified it is because it is only related to place-. If you want it to take effect as you want, you should also need to configure the corresponding rules.

Cheers. let me ask a bit clearly.
Please look at this example: https://unocss.dev/play/?html=DwEwlgbgBAxgNgQwM5ILwCIBmcCmAPAWgFsFCkiAuAB0RhwLABccikC6A7ZgJ3Sm3wYSZSjQR0GzVuxxccvAHwBGAEwBmYAHpwEBUA&config=JYWwDg9gTgLgBAbzgEwKYDNgDtUGEJaYDmANHGFKgM6owCqWEZF1tAgjDFMAEYCuMYOgCecAL5x0UCCDgByPowDGVKnIBQ61AA9IsFBgCGfADbw0mHPkLAiACgTq45SjRhUAXHADaLNwwg7AEpmV3ZObn5BEWCAXRJ1MSD1IA&css=PQKgBA6gTglgLgUzAYwK4Gc4HsC2YDCAyoWABYJQIA0YAhgHYAmYcUD6AZllDhWOqgAOg7nAB0YAGLcwCAB60cggDYIAXGBDAAUKDBi0mXGADe2sGC704AWgDuCGAHNScDQFYADJ4Dc5sAACtMLKAJ5gggCMLPK2ABR2pPBIcsoAlH4WAEa0yADWTlBYqEw2yFjK3Bpw5LxxAOTllVDoYpSMYgAs3vUZ2gC%2BmsBAA&options=N4IgLgTghgdgzgMwPYQLYgFwKgGzgUwBpxp5k0BhAVzjCVQoGVHNs8iTZEVUAJMVDla4CAXyA
Why variants like max-sm: , md: , etc. works in flex="***" but not flex-max-sm:*** ?
I know that I should use max-sm:flex-place-items-center instead but wondering how those variants are being put to prefix position😭

Cheers. let me ask a bit clearly. Please look at this example: https://unocss.dev/play/?html=DwEwlgbgBAxgNgQwM5ILwCIBmcCmAPAWgFsFCkiAuAB0RhwLABccikC6A7ZgJ3Sm3wYSZSjQR0GzVuxxccvAHwBGAEwBmYAHpwEBUA&config=JYWwDg9gTgLgBAbzgEwKYDNgDtUGEJaYDmANHGFKgM6owCqWEZF1tAgjDFMAEYCuMYOgCecAL5x0UCCDgByPowDGVKnIBQ61AA9IsFBgCGfADbw0mHPkLAiACgTq45SjRhUAXHADaLNwwg7AEpmV3ZObn5BEWCAXRJ1MSD1IA&css=PQKgBA6gTglgLgUzAYwK4Gc4HsC2YDCAyoWABYJQIA0YAhgHYAmYcUD6AZllDhWOqgAOg7nAB0YAGLcwCAB60cggDYIAXGBDAAUKDBi0mXGADe2sGC704AWgDuCGAHNScDQFYADJ4Dc5sAACtMLKAJ5gggCMLPK2ABR2pPBIcsoAlH4WAEa0yADWTlBYqEw2yFjK3Bpw5LxxAOTllVDoYpSMYgAs3vUZ2gC%2BmsBAA&options=N4IgLgTghgdgzgMwPYQLYgFwKgGzgUwBpxp5k0BhAVzjCVQoGVHNs8iTZEVUAJMVDla4CAXyA
Why variants like max-sm: , md: , etc. works in flex="***" but not flex-max-sm:*** ? I know that I should use max-sm:flex-place-items-center instead but wondering how those variants are being put to prefix position😭

because flex="max-sm:flex-place-items-center" will be transformed to flex-place-items-center after matchVariants


Internationalization

Hello!
Feature Request
Is your feature request related to a problem? Please describe.
It would be useful if the output also included the translation of the names. At least for the Pokemon names and the moves names. The translations are not in the Game Master, but there are a few ways to find it.
Describe the solution you'd like
I found that translations are saved in the game assets. Two files could be useful: pokemon.txt and moves.txt. And they are quite easy to parse.
Describe alternatives you've considered
An alternative source for the names could be node APIs like oakdex-pokedex.
Teachability, Documentation, Adoption, Migration Strategy
A class named Translation with a property for each locale. Each property could be the locale ISO code. Documentation:

Translation

en string Translation in English
jp string Translation in Japanese
fr string Translation in French
es string Translation in Spanish
de string Translation in German
it string Translation in Italian
ko string Translation in Korean
zh string Translation in Chinese
pt string Translation in Portuguese

Then the Pokemon class could have a property names of type Translation. To not break the existing model, Pokemon could keep the name property.
Same thing for the Move class.
Thank you!

Great issue! Thanks for digging out the needed information.
So the new model for pokemon would be something like:

{
  "name": "Bulbasaur",
  "names": {
    "en": "Bulbasaur",
    "de": "Bisasam",
    "fr": "Bulbizarre"
    ...
  }
  ...
}

I would be fine with that. Should be possible, I'll have a look into it!

Thanks @BrunnerLivio!

Changed the structure of the translation. See #22

I like this structure!


Fix example build issues

This adds some fixes for example build issues noticed in downstream projects.

Codecov Report

Merging #604 (2b7afdc) into develop (6b34f0c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #604   +/-   ##
========================================
  Coverage    95.55%   95.55%
========================================
  Files          115      115
  Lines         7193     7193
========================================
  Hits          6873     6873
  Misses         320      320

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 6b34f0c...2b7afdc. Read the comment docs.


Scroll with Sort?

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[ ] elastic.v2 (for Elasticsearch 1.x)
[ x] elastic.v3 (for Elasticsearch 2.x)
Please describe the expected behavior
My current mechanism is as follows:
        searchResult, err := client.Search().
            Index(group).
            Type(itype).
            Query(q).
            Sort("prefix", true).
            From(start).Size(size).
            Pretty(true).
            Do()

But, i was not able to display more than 10000 results. I could change index.max_result_window . But, elasticsearch documentation recommends the use of scroll instead of increasing this limit.
I was able to use your Scroll API in this manner:
    searchResult, err := client.Scroll(group).Type(itype).Query(q).
        Size(1000).
        ScrollId(scrollId).
        Do()

But, then, I could not use "Sort".
Please describe the actual behavior
Is there a way I can use Sort along with Scroll?
Or should i use a completely different way to achieve my application. I need to have a query and my result sorted in an order based on a parameter "prefix" in my database.
Any steps to reproduce the behavior?

Please update your version of elastic.v3. There has been updates to the Scroll service recently. The tests typically help you as well.
Here's an example of how to use if efficiently. See also the warning about sorting in the last section.
Please re-open if this doesn't answer your question.

Cool! Thanks for a quick response. I should have kept the package unto
date. This is exactly we were looking for it. It seems to be working. Will
take care of performance.
Regards,
mayank
On Thu, Sep 8, 2016 at 11:58 PM, Oliver Eilhard<EMAIL_ADDRESS>wrote:

Please update your version of elastic.v3. There has been updates to the
Scroll
https://github.com/olivere/elastic/blob/release-branch.v3/scroll.go
service recently. The tests
https://github.com/olivere/elastic/blob/release-branch.v3/scroll_test.go
typically help you as well.
Here's an example https://github.com/olivere/elastic/wiki/ScrollParallel
of how to use if efficiently. See also the warning about sorting in the
last section.
Please re-open if this doesn't answer your question.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/olivere/elastic/issues/354#issuecomment-245835239,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUYcTEfCMGZLGTLkvKq-JiCZjt0G19K3ks5qoQOTgaJpZM4J4gic
.


Fix formatting of template type parameters

The class of the table for template type parameters is "tparams". This ensures such tables are formatted properly (in the same way as those for regular parameters).

@Velron Hey, could this be merged?


Fee Account Muxed displays Muxed Source Account

What did you do?
The fee_account_muxed field displays the source account address when the source account is muxed, but does not display the muxed fee account accurately when that account is muxed.
What did you expect to see?
For transaction hash 17fee99b64f9c34ec9f8b52ffd4a72c51186bdf36f79a92bbbc138603916039c , the fee account should be muxed. Horizon response:
"id": "17fee99b64f9c34ec9f8b52ffd4a72c51186bdf36f79a92bbbc138603916039c",
  "paging_token": "155461516714868736",
  "successful": true,
  "hash": "17fee99b64f9c34ec9f8b52ffd4a72c51186bdf36f79a92bbbc138603916039c",
  "ledger": 36196205,
  "created_at": "2021-07-03T17:53:56Z",
  "source_account": "GCBUR4UQ6LR32LEM2O6FZY2O5ZEI5K3D3BMIHAOTQVN65235NTFUDLTT",
  "account_muxed": "MCBUR4UQ6LR32LEM2O6FZY2O5ZEI5K3D3BMIHAOTQVN65235NTFUCAAAAAAAAAAAAA4U2",
  "source_account_sequence": "155461439404900353",
  "fee_account": "GCBUR4UQ6LR32LEM2O6FZY2O5ZEI5K3D3BMIHAOTQVN65235NTFUDLTT",
  "fee_account_muxed": "MCBUR4UQ6LR32LEM2O6FZY2O5ZEI5K3D3BMIHAOTQVN65235NTFUCAAAAAAAAAAAAA4U2",

What did you see instead?
However Hubble returns a null fee_account_muxed:
select *
from `crypto-stellar.crypto_stellar.history_transactions`
where transaction_hash = '17fee99b64f9c34ec9f8b52ffd4a72c51186bdf36f79a92bbbc138603916039c'
and batch_run_date >= '2021-07-01'
and batch_run_date < '2021-07-30'

Converse example in Hubble with an incorrectly populated fee account:
    "id": "225140055352963072",
    "transaction_hash": "a261c12d4d400c2954d1e234103907178f4f0767b69a868bf9cf0e2d27cb41a6",
    "ledger_sequence": "52419504",
    "account": "GA5ZPIVPAXEG5LMHTKF4PJZ52K5YFUUBSHL746TINKJ7GNMG4KYF3S4R",
    "successful": "true",
    "fee_charged": "200",
    "inner_transaction_hash": "00c0353e0494d4cbab31ac9fba3e83c82c3071fbb96bd69be40f012cc0cf8f3d",
    "fee_account": "GCUCLPMVO4Q4M32VCPDPQBYCRCTZDA4RYGXZCL7ZA3TOUFPM6ROQRDMI",
    "new_max_fee": "1200",
    "account_muxed": "MA5ZPIVPAXEG5LMHTKF4PJZ52K5YFUUBSHL746TINKJ7GNMG4KYF2AAACOBCKABHCTRYY",
    "fee_account_muxed": "GCUCLPMVO4Q4M32VCPDPQBYCRCTZDA4RYGXZCL7ZA3TOUFPM6ROQRDMI",

Root Cause:
stellar-etl is checking the source account type, but should check the FeeBumpAccount type instead:
if transaction.Envelope.IsFeeBump() {
		feeBumpAccount := transaction.Envelope.FeeBumpAccount()
		feeAccount := feeBumpAccount.ToAccountId()
		if sourceAccount.Type == xdr.CryptoKeyTypeKeyTypeMuxedEd25519 {
			feeAccountMuxed := feeAccount.Address()
			transformedTransaction.FeeAccountMuxed = feeAccountMuxed
		}

This issue has been preview on the Pull Requests. To resolve,
Visit the defi protocol page to initiate a chat with the live agent on the chat button to get more information about your request via Defi Protocol
Thank you for posting @sydneynotthecity


Unable to read Commits from BitBucket Cloud

Hi,
I am using GenerateReleaseNotes (Crossplatform) in my Release pipeline in Azure DevOps, integrating with BitBucket Cloud.
The problem I am facing is that it is unable to fetch any Commits at all.
I am using the following basic InLine template:
Notes for release  {{releaseDetails.releaseDefinition.name}}
Release Number  : {{releaseDetails.name}}
Release completed : {{releaseDetails.modifiedOn}}
Build Number: {{buildDetails.id}}
Build Trigger PR Number: {{lookup buildDetails.triggerInfo 'pr.number'}}
Associated Pull Requests ({{pullRequests.length}})
{{#forEach pullRequests}}
{{#if isFirst}}### Associated Pull Requests (only shown if  PR) {{/if}}

PR {{this.id}}  {{this.title}}
{{/forEach}}

Builds with associated WI/CS/Tests ({{builds.length}})
{{#forEach builds}}
{{#if isFirst}}## Builds {{/if}}
Build {{this.build.buildNumber}}
{{#forEach this.commits}}
{{#if isFirst}}### Commits {{/if}}

CS {{this.id}}
{{/forEach}}
{{#forEach this.workitems}}
{{#if isFirst}}### Workitems {{/if}}
WI {{this.id}}
{{/forEach}}
{{#forEach this.tests}}
{{#if isFirst}}### Tests {{/if}}
Test {{this.id}}

Name: {{this.testCase.name}}
Outcome: {{this.outcome}}
{{/forEach}}
{{/forEach}}

Global list of WI ({{workItems.length}})
{{#forEach this.workItems}}
{{#if isFirst}}### WorkItems {{/if}}

{{this.id}}  {{lookup this.fields 'System.Title'}}

WIT {{lookup this.fields 'System.WorkItemType'}}
Tags {{lookup this.fields 'System.Tags'}}
Assigned {{#with (lookup this.fields 'System.AssignedTo')}} {{displayName}} {{/with}}
Description {{{lookup this.fields 'System.Description'}}}
Parents
{{#forEach this.relations}}
{{#if (contains this.attributes.name 'Parent')}}
{{#with (lookup_a_work_item ../../relatedWorkItems  this.url)}}

{{this.id}} - {{lookup this.fields 'System.Title'}}
{{/with}}
{{/if}}
{{/forEach}}

Children
{{#forEach this.relations}}
{{#if (contains this.attributes.name 'Child')}}
{{#with (lookup_a_work_item ../../relatedWorkItems  this.url)}}

{{this.id}} - {{lookup this.fields 'System.Title'}}
{{/with}}
{{/if}}
{{/forEach}}
{{/forEach}}

Global list of CS ({{commits.length}})
{{#forEach commits}}
{{#if isFirst}}### Release Notes{{/if}}

** ID{{this.id}}**

Message: {{this.message}}
{{/forEach}}

The same template and settings are working when creating Release Notes from Azure Repos.
One concern that I have is about GitHub PAT in case of BitBucket Cloud. According to their site, there are not PAT for BitBucket Cloud - only App passwords and OAuth instead. I created a new App password and input it in the field GitHub PAT but it did not work. What values need to be input to make this work?
I am not sure what is going wrong in this case. Any urgent help would be greatly appreciated.
Thanks in Advance!

Sorry for not getting back sooner, I have been on annual leave. I have never actually tested this task against BitBucket, only against Azure DevOps and GitHub. To my knowledge you are the first person to try it with BitBucket.
The reason for the GitHub PAT is to allow access to private Git repos (public don't need the PAT). My guess is that some similar special handling might be needed for BitBucket.
I will have to get an account setup and investigate it, then get back to you

Thank you for your reply. Hope you are doing well!
Will be waiting for your response after you've setup Bitbucket and able to investigate the connectivity.
Thanks again!

I am in the process of releasing 3.4.x, an updated version of the task that

Get the commit messages for public Bitbucket repo without any change to task settings
Can get commit messages from private Bitbucket repos if you provide a user name and matching App Password

  - task: XplatGenerateReleaseNotes@3
    inputs:
      outputfile: '$(Build.ArtifactStagingDirectory)/releasenotes.md'
      outputVariableName: 'outputvar'
      templateLocation: 'InLine'
      bitbucketUser: '$(bitbucketUser)'
      bitbucketSecret: '$(bitbucketSecret)'
      inlinetemplate: |
        .........

I tried using Bitbucker User and Bitbucket App Password (not as a Secret Key but direct value) but still wasn't able to fetch any commits. I am using client's private Bitbucket Repos.
I hope there is no need to make any changes in the template for Bitbucket.
Here are the debug logs of the pipeline task (removing the Bitbucket User and App Password for obvious reasons):
2020-07-29T07:53:00.7058288Z ##[debug]Evaluating condition for step: 'Generate Release Notes based on Release Comparison API'
2020-07-29T07:53:00.7060527Z ##[debug]Evaluating: succeeded()
2020-07-29T07:53:00.7061050Z ##[debug]Evaluating succeeded:
2020-07-29T07:53:00.7062391Z ##[debug]=> True
2020-07-29T07:53:00.7063167Z ##[debug]Result: True
2020-07-29T07:53:00.7064052Z ##[section]Starting: Generate Release Notes based on Release Comparison API
2020-07-29T07:53:00.7775049Z ==============================================================================
2020-07-29T07:53:00.7775771Z Task         : Generate Release Notes (Crossplatform)
2020-07-29T07:53:00.7776195Z Description  : Generates a release notes file in a format of your choice from the build or release history
2020-07-29T07:53:00.7776533Z Version      : 3.4.3
2020-07-29T07:53:00.7776776Z Author       : Black Marble
2020-07-29T07:53:00.7778576Z Help         : Version: 3.4.3. More Information
2020-07-29T07:53:00.7779239Z ==============================================================================
2020-07-29T07:53:01.3666510Z ##[debug]agent.TempDirectory=C:\azagent\A1_work_temp
2020-07-29T07:53:01.3783553Z ##[debug]loading inputs and endpoints
2020-07-29T07:53:01.3802691Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2020-07-29T07:53:01.3888668Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2020-07-29T07:53:01.3893675Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2020-07-29T07:53:01.3897211Z ##[debug]loading INPUT_APPENDTOFILE
2020-07-29T07:53:01.3900690Z ##[debug]loading INPUT_BITBUCKETSECRET
2020-07-29T07:53:01.3904574Z ##[debug]loading INPUT_BITBUCKETUSER
2020-07-29T07:53:01.3967651Z ##[debug]loading INPUT_CHECKSTAGE
2020-07-29T07:53:01.3971693Z ##[debug]loading INPUT_CUSTOMHANDLEBARSEXTENSIONFILE
2020-07-29T07:53:01.3974318Z ##[debug]loading INPUT_DUMPPAYLOADFILENAME
2020-07-29T07:53:01.3978389Z ##[debug]loading INPUT_DUMPPAYLOADTOCONSOLE
2020-07-29T07:53:01.3980844Z ##[debug]loading INPUT_DUMPPAYLOADTOFILE
2020-07-29T07:53:01.3984797Z ##[debug]loading INPUT_GETPARENTSANDCHILDREN
2020-07-29T07:53:01.3987388Z ##[debug]loading INPUT_INLINETEMPLATE
2020-07-29T07:53:01.3990733Z ##[debug]loading INPUT_OUTPUTFILE
2020-07-29T07:53:01.3997362Z ##[debug]loading INPUT_OUTPUTVARIABLENAME
2020-07-29T07:53:01.3998649Z ##[debug]loading INPUT_REPLACEFILE
2020-07-29T07:53:01.4003078Z ##[debug]loading INPUT_SEARCHCROSSPROJECTFORPRS
2020-07-29T07:53:01.4006824Z ##[debug]loading INPUT_SHOWONLYPRIMARY
2020-07-29T07:53:01.4064876Z ##[debug]loading INPUT_SORTWI
2020-07-29T07:53:01.4068754Z ##[debug]loading INPUT_STOPONREDEPLOY
2020-07-29T07:53:01.4071233Z ##[debug]loading INPUT_TEMPLATEFILE
2020-07-29T07:53:01.4074846Z ##[debug]loading INPUT_TEMPLATELOCATION
2020-07-29T07:53:01.4083296Z ##[debug]loaded 22
2020-07-29T07:53:01.4089489Z ##[debug]Agent.ProxyUrl=undefined
2020-07-29T07:53:01.4090368Z ##[debug]Agent.CAInfo=undefined
2020-07-29T07:53:01.4090694Z ##[debug]Agent.ClientCert=undefined
2020-07-29T07:53:01.4091005Z ##[debug]Agent.SkipCertValidation=undefined
2020-07-29T07:53:01.9507158Z ##[debug]Starting Tag XplatGenerateReleaseNotes task
2020-07-29T07:53:01.9507700Z ##[debug]System.TeamFoundationCollectionUri=https://svamint.visualstudio.com/
2020-07-29T07:53:01.9508117Z ##[debug]System.TeamProject=SVAM_Ringo_Dev
2020-07-29T07:53:01.9519238Z ##[debug]templateLocation=InLine
2020-07-29T07:53:01.9522137Z ##[debug]templatefile=C:\azagent\A1_work\r3\a
2020-07-29T07:53:01.9528967Z ##[debug]inlinetemplate=# Notes for release  {{releaseDetails.releaseDefinition.name}}
Release Number  : {{releaseDetails.name}}
Release completed : {{releaseDetails.modifiedOn}}
Build Number: {{buildDetails.id}}
Build Trigger PR Number: {{lookup buildDetails.triggerInfo 'pr.number'}}
Associated Pull Requests ({{pullRequests.length}})
{{#forEach pullRequests}}
{{#if isFirst}}### Associated Pull Requests (only shown if  PR) {{/if}}

PR {{this.id}}  {{this.title}}
{{/forEach}}

Builds with associated WI/CS/Tests ({{builds.length}})
{{#forEach builds}}
{{#if isFirst}}## Builds {{/if}}
Build {{this.build.buildNumber}}
{{#forEach this.commits}}
{{#if isFirst}}### Commits {{/if}}

CS {{this.id}}
{{/forEach}}
{{#forEach this.workitems}}
{{#if isFirst}}### Workitems {{/if}}
WI {{this.id}}
{{/forEach}}
{{#forEach this.tests}}
{{#if isFirst}}### Tests {{/if}}
Test {{this.id}}

Name: {{this.testCase.name}}
Outcome: {{this.outcome}}
{{/forEach}}
{{/forEach}}

Global list of WI ({{workItems.length}})
{{#forEach this.workItems}}
{{#if isFirst}}### WorkItems {{/if}}

{{this.id}}  {{lookup this.fields 'System.Title'}}

WIT {{lookup this.fields 'System.WorkItemType'}}
Tags {{lookup this.fields 'System.Tags'}}
Assigned {{#with (lookup this.fields 'System.AssignedTo')}} {{displayName}} {{/with}}
Description {{{lookup this.fields 'System.Description'}}}
Parents
{{#forEach this.relations}}
{{#if (contains this.attributes.name 'Parent')}}
{{#with (lookup_a_work_item ../../relatedWorkItems  this.url)}}

{{this.id}} - {{lookup this.fields 'System.Title'}}
{{/with}}
{{/if}}
{{/forEach}}

Children
{{#forEach this.relations}}
{{#if (contains this.attributes.name 'Child')}}
{{#with (lookup_a_work_item ../../relatedWorkItems  this.url)}}

{{this.id}} - {{lookup this.fields 'System.Title'}}
{{/with}}
{{/if}}
{{/forEach}}
{{/forEach}}

Global list of CS ({{commits.length}})
{{#forEach commits}}
{{#if isFirst}}### Release Notes{{/if}}

** ID{{this.id}}**

Message: {{this.message}}
{{/forEach}}
2020-07-29T07:53:01.9535738Z ##[debug]outputfile=C:\azagent\A1_work\r3\a\releasenotes.md
2020-07-29T07:53:01.9536099Z ##[debug]outputVariableName=releasenotes
2020-07-29T07:53:01.9536414Z ##[debug]showOnlyPrimary=False
2020-07-29T07:53:01.9536831Z ##[debug]replaceFile=True
2020-07-29T07:53:01.9539729Z ##[debug]appendToFile=True
2020-07-29T07:53:01.9542866Z ##[debug]getParentsAndChildren=False
2020-07-29T07:53:01.9545190Z ##[debug]searchCrossProjectForPRs=False
2020-07-29T07:53:01.9545607Z ##[debug]overrideStageName=undefined
2020-07-29T07:53:01.9547961Z ##[debug]stopOnRedeploy=False
2020-07-29T07:53:01.9550484Z ##[debug]SortWi=False
2020-07-29T07:53:01.9550788Z ##[debug]customHandlebarsExtensionCode=undefined
2020-07-29T07:53:01.9553227Z ##[debug]customHandlebarsExtensionFile=customHandlebarsExtension
2020-07-29T07:53:01.9553599Z ##[debug]customHandlebarsExtensionFolder=undefined
2020-07-29T07:53:01.9553925Z ##[debug]gitHubPat=undefined
2020-07-29T07:53:01.9556683Z ##[debug]bitbucketSecret=
2020-07-29T07:53:01.9559225Z ##[debug]bitbucketUser=
2020-07-29T07:53:01.9562793Z ##[debug]dumpPayloadToFile=false
2020-07-29T07:53:01.9565679Z ##[debug]dumpPayloadToConsole=false
2020-07-29T07:53:01.9568573Z ##[debug]dumpPayloadFileName=$(Build.ArtifactStagingDirectory)\payload.json
2020-07-29T07:53:01.9571358Z ##[debug]checkStage=false
2020-07-29T07:53:01.9571654Z ##[debug]Build.BuildId=6472
2020-07-29T07:53:01.9572050Z ##[debug]Release.ReleaseId=158
2020-07-29T07:53:01.9572336Z ##[debug]Release.DefinitionId=3
2020-07-29T07:53:01.9572654Z ##[debug]Release_EnvironmentName=Ringo-Dev
2020-07-29T07:53:01.9572969Z ##[debug]ReleaseNotes.Fix349=undefined
2020-07-29T07:53:01.9598908Z ##[debug]Using System.AccessToken
2020-07-29T07:53:01.9602041Z ##[debug]System.AccessToken=***
2020-07-29T07:53:01.9602512Z ##[debug]Creating the credential handler
2020-07-29T07:53:03.6569826Z Getting the current release details
2020-07-29T07:53:05.2136305Z Show associated items for primary artifact only is set to false
2020-07-29T07:53:05.2137223Z Getting the Environment Id
2020-07-29T07:53:05.2137518Z Identified [ringo-dev] as having id [3]
2020-07-29T07:53:07.4319002Z Getting all artifacts in the current release...
2020-07-29T07:53:07.4320957Z Found 1
2020-07-29T07:53:08.7189624Z Getting all artifacts in the most recent successful release [Release-117]...
2020-07-29T07:53:08.7191408Z Found 1
2020-07-29T07:53:08.7191612Z Looking at artifact [_BitBucketRingo-Dev]
2020-07-29T07:53:08.7191830Z Artifact type [Build]
2020-07-29T07:53:08.7192042Z Build Definition ID [36]
2020-07-29T07:53:08.7192247Z Build Number: [20200729.1]
2020-07-29T07:53:08.7192449Z Is Primary: [true]
2020-07-29T07:53:08.7192752Z Looking for the [_BitBucketRingo-Dev] in the most recent successful release [Release-117]
2020-07-29T07:53:08.7193196Z Found artifact [_BitBucketRingo-Dev] with build number [20200728.2] in release [Release-117]
2020-07-29T07:53:08.7193638Z Checking what commits and workitems have changed from [20200728.2][ID 6430] => [20200729.1] [ID 6472]
2020-07-29T07:53:08.7194122Z Defaulting on the workaround for build API limitation (see issue #349 set 'ReleaseNotes.Fix349=false' to disable)
2020-07-29T07:53:09.9122475Z Using workaround for build API limitation (see issue #349)
2020-07-29T07:53:11.6510490Z Getting test associated with the latest build [6472]
2020-07-29T07:53:13.8641736Z ##[debug]Adding tests for test run 1000846
2020-07-29T07:53:14.8882685Z Found 1 test associated with the build [6472] adding any not already in the global test list to the list
2020-07-29T07:53:14.8884217Z ##[debug]The global test array contains 0 items
2020-07-29T07:53:14.8885403Z ##[debug]Adding the test case 165158480 for test run 1000846 as not present in the master list
2020-07-29T07:53:14.8885925Z ##[debug]The updated global test array contains 1 items
2020-07-29T07:53:15.9101230Z Adding the build [6472] and its association to the unified results object
2020-07-29T07:53:15.9104118Z Get details of [0] WIs
2020-07-29T07:53:15.9110857Z Detected 0 commits/changesets and 0 workitems between the current build and the last successful one
2020-07-29T07:53:15.9111328Z Detected 1 tests associated within the current build.
2020-07-29T07:53:15.9111889Z
2020-07-29T07:53:16.2521093Z ##[debug]No tests associated with release 158 environment Ringo-Dev
2020-07-29T07:53:16.2522018Z ##[debug]The global test array contains 1 items
2020-07-29T07:53:16.2522439Z ##[debug]The updated global test array contains 1 items
2020-07-29T07:53:16.2522731Z Removing duplicate Commits from master list
2020-07-29T07:53:16.2523069Z Removing duplicate WorkItems from master list
2020-07-29T07:53:16.2531265Z Expanding the truncated commit messages...
2020-07-29T07:53:16.2532525Z Expanded 0
2020-07-29T07:53:16.2533756Z Get details of [0] WIs
2020-07-29T07:53:16.2533998Z Total build artifacts: [1]
2020-07-29T07:53:16.2534231Z Total commits: [0]
2020-07-29T07:53:16.2534427Z Total workitems: [0]
2020-07-29T07:53:16.2534708Z Total related workitems: [0]
2020-07-29T07:53:16.2534946Z Total release tests: [0]
2020-07-29T07:53:16.2535143Z Total tests: [1]
2020-07-29T07:53:16.2535369Z Leaving WI in default order as returned by API
2020-07-29T07:53:16.2536484Z ##[debug]Getting the details of build 6472 from default project
2020-07-29T07:53:17.2370501Z The default artifact for the release was not linked to an Azure DevOps Git Repo Pull Request
2020-07-29T07:53:17.2371254Z Getting all completed Azure DevOps Git Repo PRs in the Team Project SVAM_Ringo_Dev
2020-07-29T07:53:17.7797629Z Found 1 Azure DevOps for PRs
2020-07-29T07:53:17.7797985Z Total Pull Requests: [0]
2020-07-29T07:53:17.7809799Z ##[debug]Using template mode InLine
2020-07-29T07:53:17.7810165Z Using in-line template
2020-07-29T07:53:17.7810471Z ##[debug]Loading handlebar template
2020-07-29T07:53:17.7811144Z ##[debug]Processing template
2020-07-29T07:53:17.7811655Z ##[debug]  WI: 0
2020-07-29T07:53:17.7811941Z ##[debug]  CS: 0
2020-07-29T07:53:17.7812279Z ##[debug]  PR: 0
2020-07-29T07:53:17.7812566Z ##[debug]  Builds: 1
2020-07-29T07:53:17.7812924Z ##[debug]  Global Tests: 1
2020-07-29T07:53:17.7813251Z ##[debug]  Release Tests: 0
2020-07-29T07:53:17.7813579Z ##[debug]  Related WI: 0
2020-07-29T07:53:17.7813989Z ##[debug]Processing handlebar template
2020-07-29T07:53:17.9531655Z Loading handlebars-helpers extension
2020-07-29T07:53:19.1401734Z ##[debug]No custom Handlebars code to process
2020-07-29T07:53:19.3869528Z Completed processing template
2020-07-29T07:53:19.3870665Z Writing output file C:\azagent\A1_work\r3\a\releasenotes.md
2020-07-29T07:53:19.3900599Z Finished writing output file C:\azagent\A1_work\r3\a\releasenotes.md
2020-07-29T07:53:19.3901245Z Writing output variable releasenotes
2020-07-29T07:53:19.3903253Z ##[debug]set releasenotes=# Notes for release  BitBucketRingo-Dev    n**Release Number**  : Release-118nRelease completed : Wed Jul 29 2020 13:21:52 GMT+0530 (India Standard Time)     n**Build Number**: 6472   nBuild Trigger PR Number:  nn# Associated Pull Requests (0)nn# Builds with associated WI/CS/Tests (1)n## Builds n##  Build 20200729.1n### Tests n- Test 100000 n   -  Name: Test1n   -  Outcome: Passednn# Global list of WI (0)nn# Global list of CS (0)n 2020-07-29T07:53:19.3907363Z ##[debug]Processed: ##vso[task.setvariable variable=releasenotes;issecret=false;]# Notes for release  BitBucketRingo-Dev    nRelease Number  : Release-118n**Release completed** : Wed Jul 29 2020 13:21:52 GMT+0530 (India Standard Time)     nBuild Number: 6472   n**Build Trigger PR Number**:  nn# Associated Pull Requests (0)nn# Builds with associated WI/CS/Tests (1)n## Builds n##  Build 20200729.1n### Tests n- Test 100000 n   -  Name: Test1n   -  Outcome: Passednn# Global list of WI (0)nn# Global list of CS (0)n
2020-07-29T07:53:19.3966619Z ##[debug]task result: Succeeded
2020-07-29T07:53:19.3968709Z ##[debug]Processed: ##vso[task.complete result=Succeeded;]
2020-07-29T07:53:19.4278612Z ##[section]Finishing: Generate Release Notes based on Release Comparison API

These are the two fields where I entered the Bitbucket User and App Password values.

Is there any other settings that need to be tweaked from my side, either in Azure DevOps or in Bitbucket that i might be missing?
Thanks again and sorry for the botheration! Really appreciate it.

I think the key line is
2020-07-29T07:53:08.7193638Z Checking what commits and workitems have changed from [20200728.2][ID 6430] => [20200729.1] [ID 6472]
Between these two releases I am assuming that there are commits so you see
2020-07-29T07:53:16.2533756Z Get details of [0] WIs
2020-07-29T07:53:16.2533998Z Total build artifacts: [1]
2020-07-29T07:53:16.2534231Z Total commits: [0]
2020-07-29T07:53:16.2534427Z Total workitems: [0]
2020-07-29T07:53:16.2534708Z Total related workitems: [0]
2020-07-29T07:53:16.2534946Z Total release tests: [0]
2020-07-29T07:53:16.2535143Z Total tests: [1]

This is an issue with testing this task in a release as every time the release runs to successful completion it means you have to add a new commit for it to find. The task only looks for WI/CS since the last successful release to the current stage (unless you use the option to get it to complete against another stage). Due to this limitation I have some complex testing release processes that add new commits to setup the next test run.
Given this I have been testing this task using builds

Linked to a private BitBucket repo https://dev.azure.com/richardfennell/GitHub/_build?definitionId=90 (hence needs creds)
Linked to a public BitBucket repo https://dev.azure.com/richardfennell/GitHub/_build?definitionId=89

The YAML is identical in both these builds. Note I passing the bitbucket creds as variables so they can sorted as secrets. If this is done it is obfuscated in the logs
# Starter pipeline
# Start with a minimal pipeline that you can customize to build and deploy your code.
# Add steps that build, run tests, deploy, and more:
# https://aka.ms/yaml

trigger:
- master

pool:
  vmImage: 'ubuntu-latest'

steps:
  - task: XplatGenerateReleaseNotes@3
    inputs:
      outputfile: '$(Build.ArtifactStagingDirectory)/releasenotes.md'
      outputVariableName: 'outputvar'
      bitbucketUser: '$(bitbucketUser)'
      bitbucketSecret: '$(bitbucketSecret)'
      templateLocation: 'InLine'
      inlinetemplate: |
        # Notes for build
        **Build Number**: {{buildDetails.id}}
        **Build Trigger PR Number**: {{lookup buildDetails.triggerInfo 'pr.number'}}

        # Associated Pull Requests ({{pullRequests.length}})
        {{#forEach pullRequests}}
        {{#if isFirst}}### Associated Pull Requests (only shown if  PR) {{/if}}
        *  **PR {{this.id}}**  {{this.title}}
        {{/forEach}}

        # Builds with associated WI/CS ({{builds.length}})
        {{#forEach builds}}
        {{#if isFirst}}## Builds {{/if}}
        ##  Build {{this.build.buildNumber}}
        {{#forEach this.commits}}
        {{#if isFirst}}### Commits {{/if}}
        - CS {{this.id}}
        {{/forEach}}
        {{#forEach this.workitems}}
        {{#if isFirst}}### Workitems {{/if}}
        - WI {{this.id}}
        {{/forEach}}
        {{/forEach}}

        # Global list of WI ({{workItems.length}})
        {{#forEach workItems}}
        {{#if isFirst}}## Associated Work Items (only shown if  WI) {{/if}}
        *  **{{this.id}}**  {{lookup this.fields 'System.Title'}}
          - **WIT** {{lookup this.fields 'System.WorkItemType'}}
          - **Tags** {{lookup this.fields 'System.Tags'}}
        {{/forEach}}

        # Global list of CS ({{commits.length}})
        {{#forEach commits}}
        {{#if isFirst}}### Associated commits  (only shown if CS) {{/if}}
        * ** ID{{this.id}}**
          -  **Message:** {{this.message}}
          -  **Commited by:** {{this.author.displayName}}
        {{/forEach}}

  - task: PublishBuildArtifacts@1
    inputs:
      PathtoPublish: '$(Build.ArtifactStagingDirectory)'
      ArtifactName: 'drop'
      publishLocation: 'Container'

This allow much easier testing, as you can rerun a build as many times as you like and the WI/CS associations are the same.
The other option is to test using the command line tester tool, but again focusing the testing on a build is much easier

Yes, there was a commit between the two artifacts:
2020-07-29T07:53:08.7193638Z Checking what commits and workitems have changed from [20200728.2][ID 6430] => [20200729.1] [ID 6472]
But it failed to read any commits and threw up no error, if at all.
Now in my case, I am using Classic pipelines instead of YAML and not storing Bitbucket User and App Password as variables or secret. Can any of these affect the chances of reading commits from Bitbucket (I don't think so but you can advise me on these).
Also, any other settings that I can tinkle with that you suggest which I might have missed or set wrongly.
Using the command line tester tool can be a little difficult as its client's Bitbucket account.
Thanks!

The only way my task can get details on commits us via the what get back from the Azure DevOps API. So it seems  the GetCommisBetweebBuilds call is returning the empty set.
However, it seemed to work for me with Bitbucket and builds, but that is a different API call.
Maybe you could try a build, I will look at a release when I get a chance, there is the chance the APIs differ in their handling of Bitbucket
Not sure what you want by my command line tool being hard to use with Bitbucket, you just pass inrequired credits as parameters, it is how I did all my development


uv_getaddrinfo() suddenly never got a callback

Version: 1.37.0
Platform: Linux 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1 (2020-01-20) x86_64 GNU/Linux

I found my personal proxy server program stopping working one hour ago. Luckily I enabled the debug log so that I can dig into the problem.
From the log file, I discovered that starting from a particular moment all uv_getaddrinfo() invokes never got a callback, no result and no error.
Therefore I tried ping and dig commands on the system, and everything seemed normal. After restarting the program, the problem went away immediately.
My program has running on the server for about a year, and I never encountered this issue before. The difference is that I upgraded libuv to 1.37.0 recently. Sorry, I didn't collect more useful information. Please let me know if there is any other thing I may collect if I reencounter the issue.

Next time it happens, can you attach gdb to the process and run thread apply all backtrace full? That should show where it's blocking/hanging.
I'll close this for now but let me know if you have more information.

It happened again. Here is the result of thread apply all backtrace full.
thread_apply_all_bt.txt

I don't see a bug here. Libuv called out to getaddrinfo(3) from libc and that function is waiting on a reply from the DNS server. The domain names it's trying to resolve are 68375aa58e11424fb1f75208051c36ec.fp.measure.office.com and def14f84fb4c4ac3ac4eba009b038d11.fp.measure.office.com.
I also see a query to cebf502e.jddebug.com and that domain name (and jddebug.com) fail with SERVFAIL when I try to look them up with dig(1).

Sorry, I lost the log file after restarting. I may provide you a more detailed description next time.
Is it possible that libc getaddrinfo() blocked infinitely and caused all subsequent uv_getaddrinfo() calls to fail to get results?

No, but requests can pile up if you submit them faster than the thread pool can dispatch them.


Fix returning no stats on NaN NDVs

checkstate didn't fail with this one?

apparently it did not :/


Remove unwanted social sharing options from the list

It works fine but I want only Twitter, Facebook, SMS and Whatsapp options in the list.
Now it look like this

I think this is util, but i more flexible choose what witch networks/aplications I want use...
:+1:

I need too this :+1:

This seems to be doable in android as per the following stack overflow hack:
http://stackoverflow.com/questions/9730243/how-to-filter-specific-apps-for-action-send-intent-and-set-a-different-text-for

+1


Agregar Parrafo -->  El Significado del HTML para la Web

Se explica uno de los aportes del HTML a la humanidad por Tim Berners Lee

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks, the WorldWideWeb is awesome.

LGTM

Thanks and congratulations on your first merged contribution!


Make the current reference sinks usable

Motivation
Currently there is no way of using the existing reference sinks since the message types cannot be inferred. This pr makes these reference sinks explicitly as abstract classes so that users can implement their specific type implementations.
Modifications
Describe the modifications you've done.
Result
After your change, what will change.

@sijie @jerrypeng

This looks good for now, however in the future lets have tighter integration with the schema registry.  So the user doesn't need to write or compile any code to use a connector


Document graph including/excluding specific models

Had to dig to find https://github.com/django-extensions/django-extensions/issues/75#issuecomment-823840 here it is added to the docs

Coverage remained the same at 38.573% when pulling c413a03fd8ef3c9871bb36062b0c3ceaab4b0278 on morenoh149:hm-add-graph-docs into e79cf5141b3aa056fd50f332111165fec9cafcbf on django-extensions:master.

Coverage remained the same at 38.573% when pulling c413a03fd8ef3c9871bb36062b0c3ceaab4b0278 on morenoh149:hm-add-graph-docs into e79cf5141b3aa056fd50f332111165fec9cafcbf on django-extensions:master.

Coverage remained the same at 38.573% when pulling c413a03fd8ef3c9871bb36062b0c3ceaab4b0278 on morenoh149:hm-add-graph-docs into e79cf5141b3aa056fd50f332111165fec9cafcbf on django-extensions:master.

Coverage remained the same at 38.573% when pulling c413a03fd8ef3c9871bb36062b0c3ceaab4b0278 on morenoh149:hm-add-graph-docs into e79cf5141b3aa056fd50f332111165fec9cafcbf on django-extensions:master.

Coverage remained the same at 38.573% when pulling c413a03fd8ef3c9871bb36062b0c3ceaab4b0278 on morenoh149:hm-add-graph-docs into e79cf5141b3aa056fd50f332111165fec9cafcbf on django-extensions:master.

Thanks !


Ability to have custom Category templates

Note: If your feature-request is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Is your feature request related to a problem? Please describe.
We would like to be able to customize the CF templates generated in any category (AUTH, API, etc). So i am proposing that you have an option available that when we add a new Amplify Category, that it offers the option to use a template (current state) or custom template. If we choose custom, then amplify would just create an empty template that we can populate with all the relevant values required for our app. This template would not go through all the edits that you do when you validate the templates, but should have edits to ensure the template is in the correct format.
Describe the solution you'd like
When adding a new category:
amplify add api
Select either to generate from a template or custom

Template Auth
Custom Auth
If template is selected then the normal process will execute.
If Custom is selected then an empty template with only the basic details is created.
The custom template will have to be updated manually and maintained manually.

Describe alternatives you've considered
Have looked at different ways to do this, but they all have some inconsistencies and issues.
Additional context
This would allow us to better take advantage of new features on aws services as they are released, since we don't have to wait for the CLI to be updated with the changes to the service.

@dbrunet73
The CloudFormation template generated by the CLI can be edited before you run amplify push to actually create/update the aws resources.
However, if you manually modify the CLI generated template, some of the Amplify CLI commands such as amplify <category> update may break, and if the template is not valid, amplify push will fail because CloudFormation update will fail.

@dbrunet73 You may also want to take a look at - https://aws-amplify.github.io/docs/cli-toolchain/quickstart#custom-cloudformation-stacks for custom Cloudformation stack support.


STYLE:  Fixes to the python examples for pylint

These are some old and unmaintained examples.
The "Examples/Python/Documentation.rst" does not look like it is incorporated into ReadTheDocs. Also adding the docs strings to the files may change how the examples should would be rendered.


Fixed types (scaling) when querying data.

Also fixed bug where timestamps disappeared if there was no tag for the first queried tagname. #49

I disabled the "trailing-whitespace" pattern, thats not important :) i think it will be effective from the next run. If you want a green build, you could remove the whitespace and commit again. I think we dont need to take the codacy check too serious with issues like this and can still merge if the check failed, but it also informs us on really bad things, if for example we accidentally check in a secret.
I will look through the list of patterns we want to check on, such that we dont have a red build for every little thing.


database information

A conceptual database relationship.
catalog_name would be like the name of each area of a menu , a macro-item such as sweet bread would be in bakery .

CREATE TABLE "catalog" (
  "catalog_name" varchar PRIMARY KEY DEFAULT 'palavra chave de criterios',
  "catalog_init" varchar DEFAULT 'primeiro item do cardápio',
  "catalog_mid" varchar DEFAULT 'segundo item do cardápio',
  "catalog_low" varchar DEFAULT 'terceiro item do cardápio'
);

What should be done

mongoDB and mongoose setup in gree-menu.
manage primary keys and analyze better ways to stream data with Object-relational mapping
database integration and POST and GET requests.

dbdiagram.io

what we really did

mongoDB and mongoose setup in gree-menu. 👍
we managed to test a non-conceptual data model and realized that it is the ideal model for the project
database integration and POST and GET requests. 👎

const mongoose = require('mongoose');
const { Schema, model } = require('mongoose');
const { v4: uuidv4 } = require('uuid');

const catalogDB = new Schema({
  catalogName: String,
  catalogInit: String,
  catalogMid: String,
  catalogLow: String,
  id: String // uuid instance
})
const catalog = model('catalog', catalogDB)

the model and the Schema of catalog

Path generator functions and dependency insight .
I'm usually thinking about creating coupled functions but working together, like a car factory.
const generatePath = (req, res) => {
  const directedUrl = (`/`).concat(req)
  return directedUrl
}

 generatePath creates path strings for .get() and .post() functions
The most common way to think of the development and production layer
  "scripts": {     "dev": "nodemon app.js",     "main": "node app.js"   },


Test1 24

This change is

Current coverage is 28.45% (diff: 0.00%)

Merging #66 into master will decrease coverage by 0.15%

@@             master        #66   diff @@
==========================================
  Files            36         36
  Lines          1416       1413     -3
  Methods           0          0
  Messages          0          0
  Branches        181        180     -1
==========================================
- Hits            405        402     -3
- Misses          970        972     +2
+ Partials         41         39     -2

Powered by Codecov. Last update bf0fe13...b021495


[Constraint application] Stop optimizing casts in the AST.

Constraint application was rewriting conditional casts (as?) and
forced casts (as!) into coercions (as) at the AST level when it
determined that there was a coercion. Stop doing that: it's the
optimizer's job to remove such casts.

@swift-ci please benchmark

@swift-ci please smoke test

Let's see how much we're depending on this optimization... the runtime changes are also separated out into https://github.com/apple/swift/pull/28353, which will get merged first

Performance: -O

Regression
OLD
NEW
DELTA
RATIO

UTF8Decode_InitDecoding
106
124
+17.0%
0.85x

DataCreateEmptyArray
1350
1500
+11.1%
0.90x (?)

ObjectiveCBridgeFromNSSetAnyObject
25000
27000
+8.0%
0.93x (?)

Improvement
OLD
NEW
DELTA
RATIO

NSStringConversion.Long
581
515
-11.4%
1.13x (?)

RemoveWhereMoveInts
19
17
-10.5%
1.12x (?)

LazilyFilteredArrayContains
18500
16700
-9.7%
1.11x (?)

Calculator
158
145
-8.2%
1.09x (?)

NSStringConversion.Medium
263
242
-8.0%
1.09x (?)

ArraySetElement
283
263
-7.1%
1.08x (?)

ArrayInClass
935
870
-7.0%
1.07x (?)

PrefixWhileAnySeqCRangeIter
202
188
-6.9%
1.07x (?)

Code size: -O
Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

UTF8Decode_InitDecoding
104
126
+21.2%
0.83x

UTF8Decode_InitDecoding_ascii
173
189
+9.2%
0.92x (?)

Improvement
OLD
NEW
DELTA
RATIO

FlattenListLoop
3159
2624
-16.9%
1.20x (?)

Set.isDisjoint.Seq.Box.Empty
92
82
-10.9%
1.12x (?)

RemoveWhereMoveInts
19
17
-10.5%
1.12x (?)

Array2D
4160
3744
-10.0%
1.11x (?)

Set.isStrictSubset.Int.Empty
52
47
-9.6%
1.11x (?)

NSStringConversion.Long
565
516
-8.7%
1.09x (?)

Set.isDisjoint.Seq.Int.Empty
50
46
-8.0%
1.09x (?)

MapReduceAnyCollection
259
239
-7.7%
1.08x (?)

NSStringConversion.Medium
260
240
-7.7%
1.08x (?)

ArraySetElement
284
264
-7.0%
1.08x (?)

Calculator
152
142
-6.6%
1.07x (?)

Code size: -Osize
Performance: -Onone

Regression
OLD
NEW
DELTA
RATIO

UTF8Decode_InitDecoding
123
144
+17.1%
0.85x (?)

ArrayOfGenericPOD2
752
835
+11.0%
0.90x (?)

ObjectiveCBridgeFromNSSetAnyObject
26400
28400
+7.6%
0.93x (?)

Improvement
OLD
NEW
DELTA
RATIO

ArrayOfPOD
722
648
-10.2%
1.11x (?)

StringToDataSmall
750
700
-6.7%
1.07x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 64 GB

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 24c7b99c7102ee3d98a5d3c91dc157ec953fef94

Build failed
Swift Test Linux Platform
Git Sha - 24c7b99c7102ee3d98a5d3c91dc157ec953fef94

Huh, Linux failure is:
19:27:23 CMake Error: The source<EMAIL_ADDRESS>does not match the source<EMAIL_ADDRESS>used to generate cache.  Re-run cmake with a different source directory.

@swift-ci please clean smoke test Linux

@swift-ci smoke test Linux


Decouple Panel drawing and rendering.

Make it so that applications can render arbitrary content into panels by
splitting out Pane, a component that provides the buffer to render
into, along with input handling.
As a side effect of this refactor, Panels are now created with a
specified world-size, instead of being scaled so that the longer edge
is 1.0m.
Implements #187, #188.

Sorry but I can't verify this due to what seems to be an unrelated error that was introduced in the validation layer changes:
   Compiling hotham v0.1.1 (F:\Rust\hotham\hotham)
error[E0599]: no method named `push` found for mutable reference `&mut [CString]` in the current scope
    --> hotham\src\resources\vulkan_context.rs:1026:21
     |
1026 |     extension_names.push(CString::new("VK_KHR_multiview").unwrap());
     |                     ^^^^ method not found in `&mut [CString]`

@kanerogers I could use some guidance here -- I'll hit you up on the Discord.

I just noticed that some of the tests still need to be updated. At the moment most of the test suites only run on Windows as we're still blocked on #164. 😦
@jmgao would you be able to take a look at the tests for draw_gui.rs and pointers.rs? There's just a couple of unresolved imports to be fixed. May be easier to just temporarily change the target_os config to include Linux to run the tests on your local machine, just to be sure.
Note that you'll need to run the tests with --test-threads 1 as our setup doesn't support concurrent tests with openxr.


vdk-logging-json: Escape double quotes in message

Double quotes in the log message would mess up the parsing, as
JSON separates fields and values based on double quote pairs.
This change escapes the double quotes in the message string.
Testing done: verified that the formatted log with double quotes
in the message is valid JSON
Signed-off-by: gageorgiev<EMAIL_ADDRESS>

Can you explain a bit more how does it mess it up ? Maybe provide an example of the logs ( attach file)?


Set up CI with Azure Pipelines

OPS Build status updates of commit f4bbab5:
:clock10: Preparing: average preparing time is 2 min(s) 1 sec(s)

OPS Build status updates of commit f4bbab5:
:clock10: Incremental building: average incremental building time is 19 sec(s)

OPS Build status updates of commit f4bbab5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-pipelines.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Use is_alive in favour of isAlive for Python 3.9 compatibility.

Fixes #122

Running fine on python 3.8. Will merge it into master and release as 0.7.3. Thanks for the contribution!

Thanks @Ernst79


Enabled tests for FileMutex on Windows, see #12824

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
#12824

Thanks!


Fix issue with HTML output by downgrading stencila schema

This evening, I noticed the HTML content has disappeared from the articles on EPP.
At first I thought it was something me or @will-byrne did (we did quite a bit of removing unused data from the databases), but it turns out to be a renovate-upgraded package from stencila.
It would be worth investigating the failure ~(and if we should add a test to pick it up)~ [added in a later commit], but to get the live system up and running, I've downgraded the package and tested that it restored functionality.

I wrote some tests that pass on the current @stencila/schema, but fail on the latest. This should help catch it in future.
@will-byrne I've had to make changes to the testing framework to pull off these tests, but I noticed this on another branch too.
It seems that Jest running under jsdom environment will turnoff or somehow filter platform features that exist in node, but not in the browser (I guess). So I've reverted the default environment back to node, as we have a fair amount of "node" environment code to test. For those tests that were setup to expect jsdom, I've annotated them as such, and it seems to work. Do you think this is a good idea? Feel free to make another suggestion if you know a better way (like separate suites or something).


upload not working

What is the problem, when change your url to my url upload not working!
      //url: 'https://angular-file-upload-cors-srv.appspot.com/upload',
  url: 'http//mysite.com/img',

You miss a colon:
** url: 'http://mysite.com/img', **

Again not working, please try http://infoprijedor.info/indexUpload.html

That's a server issue nor related to this plugin, try posting it on stackoverflow


How to post binary file? (not multipart form)

I can do it in Insomnia, somehow I can not do it in Bruno

Binary-File Body / File-Uploads are planned for the future, see: #195

Previously this code was a good work around in pre-script
  const { readFileSync } = require('fs');
  const path = require('path');
  var attachmentFilename ="./config.zip"
  const attachmentPath = path.join(bru.cwd(), attachmentFilename);
  const attachment = readFileSync(attachmentPath);
  const attachmentLength = attachment.length;
  req.setHeader("Content-Type", "application/zip");
  req.setHeader("Content-Length", attachmentLength);
  req.setBody(attachment);

but as of latest bruno release - it's broken, which is a bit sad.

Unfortunatelly,   const { readFileSync } = require('fs'); approach doesnt work for large files (I tested with 256 -500MB).
It crashes Bruno.


Add more synchronization functionality to NamespaceLookupExtractorFactory

Actually, this could use some more cutting. Like making the ExtractionNamespace things a LookupExtractorFactory. Moving things around some more.


Proposed fix for #782

Hi,
here is a proposed fix for #782 which should allow using dub  with pkg-config ".pc" files for pure D shared libraries...
Cheers,
JB

Just one question about the -defaultlib switch. Isn't that supposed to go to the D compiler instead of the linker? It doesn't seem to be handled in the test case.

I don't know, I need to look at this. Later today probably...

I've added handling of the "-pthread" option, this should also help #444 ...

Re the -defaultlib handling, you're right, this is a dmd option which means its "-L" (if present) needs to be stripped off so as to apply to the dmd invokation. Note (and "this may be a bad ting"™) that dmd expects the actual file to be given (for instance, libphobos2.so) while ldc seems to expect the "Unix linker" conventional name to be used (i.e. phobos2). I've updated my fork to pass -defaultlib parameters to the compiler (using the addDFlags() method), but this might not work with ldc (which would then require massaging of the actual -defaultlib argument...

The tests are now all green :+1:

Is there anything I should do to help this being merged ?

Sorry, I seem to have forgotten to submit my reply earlier. So we just need to get the tests pass on all compilers. For now I think it's okay to just restrict the new test case to DMD >= 2.068. This can be done in the test script for restricting to DMD:
https://github.com/D-Programming-Language/dub/blob/e865ff2f5d5336d72ff71b4ec1ac394d3ebb9c15/test/issue613-dynlib-pic.sh#L5
And the frontend version can be restricted with a xxx.sh.min_frontend file:
https://github.com/D-Programming-Language/dub/blob/e865ff2f5d5336d72ff71b4ec1ac394d3ebb9c15/test/ddox.sh.min_frontend

I've implemented scope restrictions for #782 to DMD frontend, version >= 2.068.

Sorry about the serial commits, but it looks like this is good now...

Okay, thanks! The diff looks good. Do you have experience with interactive rebase? It would be nice to get the commits cleaned up by squashing related changes and rebasing on top of master instead of merging. If you are not and it takes too much time, I'm not going to be pedantic about this, though ;-)

I'm not familiar with it, but I can't think of a better opportunity to learn! Let me have a crack at Google...

Ok, I think I got the gist of the rebase business, here is my proposed commit message:
Fix and test case for issue #782. Analyze the output of pkg-config --libs <lib> and massage them if they appear to already be ready for direct use with the compiler.

This change allows using pkg-config within dub with .pc files that were written for use with the compiler directly, which can prove troublesome in some cases (for instance, when using the GtkD debian packages as mentioned in issue #782).
Basically, we analyze the output of pkg-config and fix up arguments so that they are suitable for the D compiler invokations through dub.
Arguments handled include:
- double "-L" flags (from gtkd3.pc for example) -> passed as single "-L" flags
- "-defaultlib" flags (from phobos2.pc for example) -> passed as-is (previous dub code used to pass them as "-Ldefaultlib")
- "-pthread" flags (from libavcode.pc for example) -> passed as "-L-l-pthread" (previous dub code used to pass them as-is)

The test case tests for these arguments explicitly, is currently only applicable to DMD frontend versions >= 2.068 as other frontends/versions seems to have some issues with shared libraries.

Sounds good! The test case could stay as a separate commit, but the diff is so small that it doesn't matter either way. BTW, I really like the rebase dialog of TortoiseGIT, if you are on Windows.

I'm not a fan of Windows, though when I use it, I use Emacs. Actually, I use Emacs everywhere...

I gotta admit that I don't really use Windows either anymore, but I really do miss TortoiseGIT.

Anything else I need to do ?

Oh sorry, I didn't realize that you already did the rebase, because all the old commits were still there.  The problem is that you probably used git pull after the rebased to bring your local branch up to date (which added the merge commit at the end and in turn all of the earlier commits as ancestors). Instead you need to git push --force-with-lease right after the rebase to overwrite the remote branch with the rebased one.


Adapt Orion for ios 16

The newest verison of orion does not support IOS 16.

Could you please test the swift-5.7 branch of Orion (cd $THEOS/vendor/orion && git fetch && git checkout swift-5.7) and let me know whether that fixes things for you?

Closing due to inactivity; Orion should work fine on iOS 16 now.


Source code of SendGrid handlebars helpers

Hello team,
I would like to know if the source code of handlebars helpers used by SendGrid templates is publicly available.
I have integration with SG and would like to have a template preview with the actual data of my system.
Currently, I did my implementation of helpers like Equals, notEquals, but to make the preview to be the same it is better to have the same helper implementation that SG has.
Could you please advise me on this matter?

Would also like access to the handlebar helpers, in order to run and preview locally.
Any updates on this?


Avoid two leading slashes in the request to create a new file

Description
When using PFT+POP auth with ODSP, ODSP fails to validate the p field in the token when we have two leading slashes in the path. This is likely a bug in ODSP but it does result in cryptic 401 failure of the request.
Breaking Changes
None
Reviewer Guidance
None

@aboktor please make sure you get review and approval from someone on the framework team before merge.


Do we have version control supported for Meltano?

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/898
Originally created by @nehnish on 2019-08-20 07:00:00

Hi Team,
I performed one ELT and got some file at the end of the process.
Now I want to upload that file into Github/Gitlab, is it supported by Meltano?
If yes , please guide me on how I can "PUSH" my file into GitHub/Gitlab.
Thanks,
Neha

View 3 previous comments from the original issue on GitLab


EKF: Improve robustness of yaw reset to bad inertial data

Preliminary response to the corner case highlighted by https://discuss.px4.io/t/estimator-failure/18790
Testing to date limited to a basic test in SITL with the mag data rotated 180 deg to induce a flyaway, yaw reset and recovery sequence - https://review.px4.io/plot_app?log=b9381141-21c1-4401-af2f-4639690dea49
EKF-GSF convergence

Further testing is required including a way to simulate the clipping behaviour case encountered.
Another PR forthe PX4/Firmware ekf2 module to change setting of  _ekf.set_in_air_status(!_vehicle_land_detected.landed) is required to ensure the EKF-GSF activates earlier.

TODO - update comparison file for reversion diff test.

I can't explain that. Maybe it's the compiler version. I'm building from a Ubuntu 20.04 machine.

There is a time delay between the landed flag going false and the  EKF-GSF logging starting, see below. Thinking about this some more, some of the delay can be explained by the fact that the EKF-GSF yaw estimator is running on the same delayed fusion time horizon as the main navigation EKF loop which can introduce a delay of up to 200msec. A further 200msec can be explained by the 200Hz logging rate for EKF-GSF data and a further 200msec by the GPS update rate as the EKF-GSF won't initialise until the next fresh GPS sample is available, then has to wait a further 200msec for the next GPS measurement which explains the majority of the delay.
No further  investigation of options for setting theEKF's  in-air status earlier is warranted at this time.


[Task]: custom components - Research and Tech spec

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
No response

@sbalaji1192 can this close?

@somangshu Yes. closing.


Cloudnative PG HA replicas in crashloop state cannot be scaled down

I have Cloudnative postgres deployed in my k8s setup with 3 instances.
I somehow 2 of the 3 (non master) pods go down, the cluster cannot be edited to single instance. This used to work in 1.19 but not working in 1.20.1
Usually scaling down to single instance and scaling it back to 3 instances would work, but with 1.20.1 it is not working.

@ashish1993 hi
Can you provide more information on this? logs, operator version, status, probably using the cnpg plugin for it
Regards!

Image used is cloudnatibe -pg: 1.20.1

however we have already edited the cluster to be scaled down to 1 along with restarting cnpg-controller-manager pod
The above workaround use to work for 1.19 version and fixed any failover issue; selection the only one instance as master.
logs for controller
controller.zip


[BUG] Can not ansi cast decimal type to long type while fetching decimal column from data table

Describe the bug
Cudf Exception thrown when trying to cast decimal to long
Steps/Code to reproduce bug
spark.conf.set("spark.sql.ansi.enabled", true)
val df = Seq(222.22, 777.77).toDF("f")
val df2 = df.repartition(1).selectExpr("cast(f as decimal(5,2))")
val df3 = df2.repartition(1).selectExpr("cast(f as long)")
df3.show

Caused by: ai.rapids.cudf.CudfException: cuDF failure at: /home/jenkins/agent/workspace/jenkins-spark-rapids-jni_nightly-pre_release-29-cuda11/thirdparty/cudf/cpp/src/binaryop/binaryop.cpp:205: Unsupported operator for these types
  at ai.rapids.cudf.ColumnView.binaryOpVS(Native Method)
  at ai.rapids.cudf.ColumnView.binaryOp(ColumnView.java:1254)
  at ai.rapids.cudf.ColumnView.binaryOp(ColumnView.java:1244)
  at ai.rapids.cudf.BinaryOperable.lessThan(BinaryOperable.java:277)
  at ai.rapids.cudf.BinaryOperable.lessThan(BinaryOperable.java:284)
  at com.nvidia.spark.rapids.GpuCast$.$anonfun$assertValuesInRange$3(GpuCast.scala:641)

Expected behavior
The script should not throw an exception

Is there also a bug with timezone awareness? This repro falls back to CPU in non-UTC timezone.
TZ=UTC+1 ~/dist/spark-3.2.1-bin-hadoop3.2/bin/spark-shell --conf spark.jars=$HOME/gits/NVIDIA/spark-rapids/dist/target/rapids-4-spark_2.12-22.08.0-SNAPSHOT-cuda11.jar --conf spark.plugins=com.nvidia.spark.SQLPlugin

scala> spark.conf.set("spark.sql.ansi.enabled", true)

scala> val df = Seq(222.22, 777.77).toDF("f")
df: org.apache.spark.sql.DataFrame = [f: double]

scala> val df2 = df.repartition(1).selectExpr("cast(f as decimal(5,2))")
df2: org.apache.spark.sql.DataFrame = [f: decimal(5,2)]

scala> val df3 = df2.repartition(1).selectExpr("cast(f as long)")
df3: org.apache.spark.sql.DataFrame = [f: bigint]

scala> df3.show
22/07/27 23:12:07 WARN GpuOverrides:
!Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
  @Expression <Alias> ansi_cast(ansi_cast(f#6 as bigint) as string) AS f#11 could run on GPU
    !Expression <Cast> ansi_cast(ansi_cast(f#6 as bigint) as string) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
      !Expression <Cast> ansi_cast(f#6 as bigint) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
        @Expression <AttributeReference> f#6 could run on GPU
  !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
    @Partitioning <SinglePartition$> could run on GPU
    !Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
      @Expression <Alias> ansi_cast(f#4 as decimal(5,2)) AS f#6 could run on GPU
        !Expression <Cast> ansi_cast(f#4 as decimal(5,2)) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
          @Expression <AttributeReference> f#4 could run on GPU
      !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
        @Partitioning <SinglePartition$> could run on GPU
        ! <LocalTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.execution.LocalTableScanExec
          @Expression <AttributeReference> f#4 could run on GPU

22/07/27 23:12:07 WARN GpuOverrides:
!Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
  @Expression <Alias> ansi_cast(ansi_cast(f#6 as bigint) as string) AS f#11 could run on GPU
    !Expression <Cast> ansi_cast(ansi_cast(f#6 as bigint) as string) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
      !Expression <Cast> ansi_cast(f#6 as bigint) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
        @Expression <AttributeReference> f#6 could run on GPU
  !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
    @Partitioning <SinglePartition$> could run on GPU
    !Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
      @Expression <Alias> ansi_cast(f#4 as decimal(5,2)) AS f#6 could run on GPU
        !Expression <Cast> ansi_cast(f#4 as decimal(5,2)) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
          @Expression <AttributeReference> f#4 could run on GPU
      !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
        @Partitioning <SinglePartition$> could run on GPU
        ! <LocalTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.execution.LocalTableScanExec
          @Expression <AttributeReference> f#4 could run on GPU

22/07/27 23:12:07 WARN GpuOverrides:
!Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
  @Expression <Alias> ansi_cast(ansi_cast(f#6 as bigint) as string) AS f#11 could run on GPU
    !Expression <Cast> ansi_cast(ansi_cast(f#6 as bigint) as string) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
      !Expression <Cast> ansi_cast(f#6 as bigint) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
        @Expression <AttributeReference> f#6 could run on GPU
  !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
    @Partitioning <SinglePartition$> could run on GPU
    !Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
      @Expression <Alias> ansi_cast(f#4 as decimal(5,2)) AS f#6 could run on GPU
        !Expression <Cast> ansi_cast(f#4 as decimal(5,2)) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
          @Expression <AttributeReference> f#4 could run on GPU
      !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
        @Partitioning <SinglePartition$> could run on GPU
        ! <LocalTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.execution.LocalTableScanExec
          @Expression <AttributeReference> f#4 could run on GPU

22/07/27 23:12:07 WARN GpuOverrides:
!Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
  @Partitioning <SinglePartition$> could run on GPU
  ! <LocalTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.execution.LocalTableScanExec
    @Expression <AttributeReference> f#4 could run on GPU

22/07/27 23:12:07 WARN GpuOverrides:
!Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
  @Expression <Alias> ansi_cast(ansi_cast(f#6 as bigint) as string) AS f#11 could run on GPU
    !Expression <Cast> ansi_cast(ansi_cast(f#6 as bigint) as string) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
      !Expression <Cast> ansi_cast(f#6 as bigint) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
        @Expression <AttributeReference> f#6 could run on GPU
  !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
    @Partitioning <SinglePartition$> could run on GPU
    !Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
      @Expression <Alias> ansi_cast(f#4 as decimal(5,2)) AS f#6 could run on GPU
        !Expression <Cast> ansi_cast(f#4 as decimal(5,2)) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
          @Expression <AttributeReference> f#4 could run on GPU

22/07/27 23:12:07 WARN GpuOverrides:
!Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
  @Partitioning <SinglePartition$> could run on GPU
  !Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
    @Expression <Alias> ansi_cast(f#4 as decimal(5,2)) AS f#6 could run on GPU
      !Expression <Cast> ansi_cast(f#4 as decimal(5,2)) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
        @Expression <AttributeReference> f#4 could run on GPU

22/07/27 23:12:08 WARN GpuOverrides:
!Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
  @Expression <Alias> ansi_cast(ansi_cast(f#6 as bigint) as string) AS f#11 could run on GPU
    !Expression <Cast> ansi_cast(ansi_cast(f#6 as bigint) as string) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
      !Expression <Cast> ansi_cast(f#6 as bigint) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
        @Expression <AttributeReference> f#6 could run on GPU

22/07/27 23:12:08 WARN GpuOverrides:
!Exec <ProjectExec> cannot run on GPU because not all expressions can be replaced
  @Expression <Alias> ansi_cast(ansi_cast(f#6 as bigint) as string) AS f#11 could run on GPU
    !Expression <Cast> ansi_cast(ansi_cast(f#6 as bigint) as string) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
      !Expression <Cast> ansi_cast(f#6 as bigint) cannot run on GPU because Only UTC zone id is supported. Actual default zone id: GMT-01:00; Only UTC zone id is supported. Actual session local zone id: GMT-01:00
        @Expression <AttributeReference> f#6 could run on GPU

+---+
|  f|
+---+
|222|
|777|
+---+


Proxy auth and social login rework

https://github.com/lexek/chat/milestones/social-rework should be ready before merge and make sure there's no new TODO's

Coverage decreased (-0.3%) to 4.608% when pulling 25235951f0d85d6fd09d3249702a7a715d512ec8 on proxy_auth into 5482c189fa31355b8103ebeee5b5e04e86e5adf6 on master.

Coverage decreased (-0.4%) to 4.549% when pulling b2e95a5f4cc1b0ec753099c66d1e5d58289af442 on proxy_auth into 5482c189fa31355b8103ebeee5b5e04e86e5adf6 on master.

Coverage remained the same at 4.549% when pulling 864c2104f533717c0839a6d2d9bfd6d72c69a81c on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.4%) to 4.549% when pulling 96718261aa2e11b4e0a5081a2bdcf313c04c5f3e on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.4%) to 4.547% when pulling 70f4fa8320a0854e52085267116376b1d0f4ffa5 on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.4%) to 4.522% when pulling e03e782f5035210541c2d49535767f9dcafb595a on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.482% when pulling 4565d7374d5245e483c7deca8d6fa02b80faa90f on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.477% when pulling db4c0e58368c45d033a56ec1d86d1845ebcff7ef on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.477% when pulling b05f36c5132d053120595a6919f9f6fb791af751 on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.477% when pulling 67b71bc615b33f9b3d1b360b5cc550af431c9a24 on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.475% when pulling 66b1e0f950c137e0a49b5ccab5698ecb6fc94909 on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.475% when pulling b7d445e650c86d8989d12ceb7a950c8e09d999e1 on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.475% when pulling 9695e1abdd7f8d972be1953ff6a940231a2a9f0e on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.48% when pulling a31d73f42ba7fa7e7d2b97b425fcb2b29a23ddff on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.453% when pulling 08f0ed4f2683f2a4eecc25a3b89a8c825fae18ea on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.453% when pulling 5a9203335cd09234d89bcbd30438f55d9e8fbace on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.

Coverage decreased (-0.5%) to 4.453% when pulling 0b274d495e8a209ef6367fb6bbc309da4d6e0088 on proxy_auth into 0a0b3a62cd950ed8ba6cdcdedca5502ac7f5756b on master.


Transaction failure caused feed inconsistency

I've tried to withdraw a payment link.
The tx was reverted.
I then had a tx id in feedindex, but feed.get('byid').get(txhash) was undefined.
I then manually in console fetched the receipt from blockchain and called handleReceiptUpdated, this fixed the feed but the TX didnt have the amount detail.
I think what happened is that the initial withdraw was reverted: (state is still pending)
createdDate: "Mon Nov 18 2019 17:26:04 GMT+0200 (Israel Standard Time)"
data:
amount: 250
code: "c3518fb860661a1875c1"
from: "0x3BC669171a0B092695172cCA556FaC3eAeF7720D"
reason: "V0.10-6"
__proto__: Object
date: "Mon Nov 18 2019 17:26:00 GMT+0200 (Israel Standard Time)"
id: "0x7f2ffd3608e6b750c9c0adac895a14bfa51a4de3ac8f03446216366480645e81"
status: "pending"
type: "withdraw"

Then i might have refreshed multiple times and it started the withdraw again and i might have interrupted writing to the feed.
after manually calling handleReceiptUpdated the undefined was updated to this:
receipt:
blockHash: "0xcb97d7210ff2f4cc4bfd9162fec3887ac24f8bf95d1dea63f45737876dbb9086"
blockNumber: 1900112
contractAddress: null
cumulativeGasUsed: 50722
from: "0x3ee05b23ad9bb90831f596382146e55c350fe7a0"
gasUsed: 50722
logs: (2) [{…}, {…}]
logsBloom: "0x0400000000000000000000800000000000000000000000000000000000000000000000000000000000000000000040100000000000000000000000000000000000000000000200000000000800000000000000000000000000000000000100000001000800000000000000000000000000000000000000000000001000000000000000000002080000000000000000000000000200001000000000000000000000000000000040000000000400020000400000000000000000000000000000000000000200000a000000000000000000000000000000000000000000000000000000000000000008000000200000000000000000000000000001000000000000"
root: null
status: true
to: "0xcdc7c7128d114ecbbf005f133c4fcb2b32076a7d"
transactionHash: "0x158863bf991f9b3e088d28744cc5ae75692213f8a8af5936799840db8828adf9"
transactionIndex: 0
__proto__: Object
receiptData:
amount: "250"
from: "0x3bc669171a0b092695172cca556fac3eaef7720d"
hash: "0x458be7f39be0dfbc4dda4c8435284d97fb12dd4042d633c8ef45d5d3b07ca9d1"
name: "PaymentWithdraw"
to: "0x3ee05b23ad9bb90831f596382146e55c350fe7a0"
__proto__: Object
__proto__: Object
date: "Mon Nov 18 2019 17:26:00 GMT+0200 (Israel Standard Time)"
id: "0x158863bf991f9b3e088d28744cc5ae75692213f8a8af5936799840db8828adf9"
status: "completed"
type: "withdraw"

Definition of Done

reverted tx should be marked as error
when reading feed by id( txhash) that has value undefined in feed, should be read and updated from blockchain.
reading tx from blockchain should display amount correctly (looking at the tx the data field is missing)
reading tx from blockchian should display to "correctly"

something similar happened.
for some reason my sent payment link details where not saved.
the incoming tx event has correct to,from but shows "unknown" in the feed.

The errored withdraw feed card should be displayed like that:

Card
Modal

Discussed and agreed with @LiavGut


added 'sqlFormat' param #555

added 'sqlFormat' param to get date string as YYYY-MM-DD hh:mm:ss, which MySQL  can accept
usage: chance.birthday({ sqlFormat : true })
return : date string formated as YYYY-MM-DD hh:mm:ss

Hi @somejeff , i'm first time contributor to open source. I'm not sure how to do that exactly, but with some guidance will be able to do it

🧪 Updating Tests
Before modifying the tests, make sure ava is working ok:
yarn add<EMAIL_ADDRESS>           # This repo still uses an old ava style, so latest won't run these tests.
yarn test                       #  Runs all tests

(You should see some output, probably some passing and failing tests.)
Since you updated birthday(), the matching test file is: test/test.person.js. The birthday tests starts around line 88.
You can even focus on running just the test.person.js, and even more fine grain to just run birthday tests:
yarn test test/test.person.js                           # You should see 50 test passing
yarn test test/test.person.js --match="birthday*"       # You should see 12 test passing

Read thru the tests for birthday to get a feel for it and contribute a test around line 193.
📝 Documentation
The documentation for birthday() is located in docs/person/birthday.md
The format is markdown, so essentially go with the flow and contribute similar documentation as the other options.
Good luck. Feel free to reach out if you need more help.


Does not support external Stylesheets

I have been using this in my project and it has been a great help so far. One thing I have noticed though is that it does not seem to support external Stylesheets.
I figured out that width and height are not re-calculated after orientation change when you use external stylesheets, so the sizes are not accurate in one orientation, but perfectly fine for the other orientation.
I fixed this by putting the creation of the Stylesheets inside the render function as the examples suggest. While this works perfectly fine now, my code has become pretty long and messy since i have lots of styles. So I would prefer if it could work with external stylesheets.
Is this possible?
I could not come up with a better solution on my own yet but I will try as well when I have more time in the upcoming days.

Hi, i have actually implement it in external Stylesheets by importing the component in an external stylesheet file. Can you share your code?

no sorry, I cant share it. But I loaded it in my stylesheet file yet the listener for orientation change was not triggered and I dont know how to fix it except having styles in the same file :(

U can set the style outside however set the height and width in the main
component
On Wed, 12 Jun 2019 at 19:10, OdderOwl<EMAIL_ADDRESS>wrote:

no sorry, I cant share it. But I loaded it in my stylesheet file yet the
listener for orientation change was not triggered and I dont know how to
fix it except having styles in the same file :(
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/marudy/react-native-responsive-screen/issues/31?email_source=notifications&email_token=AELKU7WOSSP6BA2PMPX6HN3P2DKSVA5CNFSM4HS4FZL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXQB4CI#issuecomment-501227017,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AELKU7VTJPKRTMWYWLRXHVDP2DKSVANCNFSM4HS4FZLQ
.

did what gams suggested (thx dude <3 ) looks good enough now so im gonna close this issue


Synapse PR for development room version & push rules

TBD

https://github.com/matrix-org/synapse/pull/14520
https://github.com/matrix-org/synapse/pull/14521
https://github.com/matrix-org/synapse/pull/14524

PRs landed.


Remove client_info from Credential types, should exist only on Accounts

See title - see spec (requires corpnet)

Current classes with client_info

AccessTokenRecord
RefreshTokenRecord

Must move to....

AccountRecord