logical source reference from the core part of the spec

The core description has references to some input data but if we split the logical source and core part of the spec, how should we handle the references of the examples at the core part?
Should we introduce an abstract running example? or should we still have examples for all exemplary data sources?

I don't think we should split the logical source part completely from the core spec. I think you would need at least an abstract / general descpription of what a logical source is and how it works, irrespective of specific reference formulations, to be able to describe the core workings. Then there can be one (or more) separate spec(s) for concrete reference formulations.

so you think that the RML-core should include both the description of the Logical Source and the rest of Triples Map?
Because in past discussions, we were thinking of having a separate spec for the Logical Source accompanied by different notes for different reference formulations.

Well I guess it is question of preference. But I'd say that the logical source is core to the understanding of RML. So I think it would be good to describe it in the core spec. I think it will be hard to describe how a Triples Map generates results without, at least abstractly, describing the logical source.

I think for this we discussed two alternatives:

before the summer holidays, we discussed the option of having these intermediate key-value combinations considered by the core spec and then make this concrete at the other parts of the spec
after the summer holidays, we discussed keeping it as in the case of R2RML being the default behaviour but without the constraints, so we have room to specify different at the other specs.
For instance, default spec would say that the subject can be an IRI (without say only IRI, ie it doesn't exclude other options) and then the star part of the spec can say that the sucbject can also be a star term.

@DylanVanAssche I think it's clear that we are going to have a LogicalSource spec, but... what are the current changes we need to do over the core spec to be adapted and self-contained? any idea? I also agree that at least, an abstract way for describing the logical source in the core is needed.

what are the current changes we need to do over the core spec to be adapted and self-contained?

I would keep rml:logicalSource and rml:logicalTarget in the Core Spec
Move all Logical Source stuff (class, properties, etc.) to the Logical Source Spec.

I also agree that at least, an abstract way for describing the logical source in the core is needed.

I think by keeping rml:logicalSource and rml:logicalTarget we have enough. You can allow any Object here so you don't depend on the Logical Source / Target spec, but they can be used here to have a straightforward integration.

We did what I presented in https://github.com/kg-construct/rml-core/issues/25#issuecomment-1066772897
Let's close this issue since we have a proposal that is implemented.


Secure 'Lint workflows' action

@afcollins would you like to work on this together? I'm new to actions, but interested in learning more and hopefully contribute too

No secrets, scripts are used in the Lint workflows.👍
CODEOWNERS file has the dev team listed as a required PR approver for all code changes. 👍
Workflows is not accessing cloud resources, so OpenID connect does not apply. 👍
Workflows is not using a third-party action.👍
Do we want this action to scope the frontend repo too? If so, we might want to consider securing cross-repo access with github token.

As far as the Amplify App goes, we will combine the frontend and backend repos. Also, github token almost always only works within a single repo.


Update announcements-viva-connections.md

Announcement cannot be edited after it's submitted.

@AtkinE
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Support numpy 1.23, pandas 1.4.{3,4}, pyarrow=4.0.1

Added reverse compatibility for string types in predicates.

[x] Changelog entry

All green except the nightlies, so this is ready for a review/merge.


Add patches for python2

What does this PR do?
Moving here from omnibus-software

Build pipeline is green as well, merging


Fix missing sound when pay invoice

Explanation of Change

Fixed Issues

$ https://github.com/Expensify/App/issues/52792
PROPOSAL: https://github.com/Expensify/App/issues/52792#issuecomment-2487361297
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Same as QA Steps
QA Steps

As User B, send an invoice to User A
As User A,

Open the invoice chat
Pay the invoice
Verify there is a sound played

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/edab7adf-5125-4f66-9487-bc57ec38645f

Android: mWeb Chrome

https://github.com/user-attachments/assets/7b2c4ff7-780d-4967-9281-538acdfdf042

iOS: Native

https://github.com/user-attachments/assets/76efca77-9ae4-41a5-9270-2e406da316e9

iOS: mWeb Safari

https://github.com/user-attachments/assets/116d03be-f9f9-4870-9308-fb698baf7001

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/50f1d30e-a5ee-4bca-bbb0-62be0ccfd21a

MacOS: Desktop

https://github.com/user-attachments/assets/f617e9be-c642-4985-ade5-6d3b668d5282

I also move the playSound to payMoneyRequest. I've tested it and the sounds played, but I can't test for the paying with held expenses case because the pay button doesn't show if we hold an expense after this PR: https://github.com/Expensify/App/pull/51133
I'm not sure how we can send money anymore, so I don't touch sendMoneyElsewhere and sendMoneyWithWallet.

@rushatgabhane what is your eta?

@rushatgabhane how is it looking

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@bernhardoj PR is failing on Android and iOS with this issue https://github.com/Expensify/App/issues/52772
https://utest-dl.s3-accelerate.amazonaws.com/testRunStepMinAttachmentsResult/50195981/1733304108232!ScreenRecording_12-04-2024_12-20-05_1.MP4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20241204T103425Z&X-Amz-SignedHeaders=host&X-Amz-Credential=AKIAJ2UIWMJ2OMC3UCQQ%2F20241204%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Expires=86400&X-Amz-Signature=6246584340a25b449a119786e11f2643399422de5894f3359259afe53de2bfa7

Lets continue on that linked PR

I think the QA is trying to say that the sound is still missing on the hybrid app, which is an existing issue.


Fixes 4046: template date formatted incorrectly

Summary
Fixes the template date format sent in the create / edit template requests. This was inadvertently updated in the last commit.
Testing steps

Creating and editing a template should not fail

https://issues.redhat.com/browse/HMS-4046

Note to self, this is current error:
code=400, message=parsing time "30 Apr 2024" as "2006-01-02T15:04:05Z07:00": cannot parse "30 Apr 2024" as "2006", internal=parsing time "30 Apr 2024" as "2006-01-02T15:04:05Z07:00": cannot parse "30 Apr 2024" as "2006"

Hi
lgtm: Success alert:Content Template "test-pr" created


Update PSBoundParameters later to make sure we pick up all changes

We need to update PSBoundParameters here.
And ProvisionerApplicationSecret and TenantId
TestApplicationOid is also updated later in the script.
BaseName is updated later as well.
As well as ResourceGroupName

Originally posted by @pakrym in https://github.com/Azure/azure-sdk-tools/pull/1175#r518910453

@benbp I'll let you get your work in first so this doesn't conflict. This issue shouldn't regress anything since people clearly weren't using "newly" added parameters, or they'd have been broken before. And my change that needs the $BaseName isn't going in until 1) the Az module is updated on agents, or 2) we have a story for prereq'ing newer Az modules (e.g. az.keyvault@3.0.0).
/cc @weshaggard @pakrym

@heaths, were you intending to close this?

Yes, I fixed it with the latest changes we sync'd. I still kept updating of $PSBoundParameters closer to where we set/overwrote the variables because I still think it's more tenable than trying to remember all the variables we need to overwrite in $PSBoundParameters later, but the intent of this bug was addressed (i.e. I missed at least $BaseName).

I don't think so, there a few that are listed in the issue that are not updated.

I see: https://github.com/Azure/azure-sdk-tools/pull/1175/files#r518911288


Fix vulnerability

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign sohimanshu
You can assign the PR to them by writing /assign @sohimanshu in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: oh-vikramsingh
To complete the pull request process, please assign sohimanshu
You can assign the PR to them by writing /assign @sohimanshu in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
Approval requirements bypassed by manually added approval.
This pull-request has been approved by: oh-vikramsingh
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Design Meeting Notes, 3/4/2022

extends Constraints on infer Type Parameters
https://github.com/microsoft/TypeScript/pull/48112

Was using a separate type alias to constrain an infer type parameter.

Required little to no changes; scope felt small.

Means you can avoid levels of cascading.
// before
type Pair =
    T extends [infer U] ?
        U extends string ? ["string", U] :
        U extends number ? ["number", U] :
        never :
    never;

// after
type Pair =
    T extends [infer U extends string] ? ["string", U] :
    T extends [infer U extends number] ? ["number", U] :
    never;

Could achieve some of this with a type alias
type Is<T extends U, U> = T;

What about a [infer T, infer U extends T]?

It's not that inference fails, it's that maybe the constraint would be violated?

Need to think through whether there's weirdness here.

In theory shouldn't have any weirdness compared to regular type parameters.

Right now the infer parameters are not in scope with respect to each other.

So that means that they can't go circular w.r.t. each other?
Ideally yes. Makes us feel better about this.

Parsing issues that could break existing code?
type X<T> = T extends { x: infer P extends U ? 1 : 0 } ? 1 : 0;
//                         ^^^^^^^^^^^^^^^^^
// now looks like an `infer` type with a constraint

infer in the checked type? wtf does this mean?
Practically nothing except when you're inferred from another conditional type.
😫
Could say "you need to parenthesize infer P"

So there's at least an ambiguity. Could get away with some speculative parsing to disambiguate.

Another test case: make sure that an outer type parameter used in a constraint works.

infer Improvements in Template Literal Types
https://github.com/microsoft/TypeScript/pull/48094

Idea: constrained types with a round-trippable string representation can be inferred for infers in template strings when you enforce a constraint with something like type Is<T extends U, U> = T (or the constraint feature mentioned above).
If you can get away with Is<T extends U, U> = T, do we really need to add syntax?

Well we don't feel good about people having to learn this.
Also, you can avoid those nested conditional checks.

This will be a MASSIVE improvement. I wanted to drop this link to a tangentially-related issue from a while back. Thank you for all of your work!


Modularize and cleanup panel

Description

Clean up breadcrumbs
Remove switchToEditViz becuase it is called in home
Add onEditClick prop that takes the function to call when edit visualization is clicked
Make add visualization popover a component
Change button text to sentence case for event analytics to match rest of Observability
Add cypress tests to check

App panels don't show up in Operational Panels table
App visualizations don't show up in Event Analytics table
App visualizations don't show up in add existing visualization flyout in Operational Panels
Show all visualizations of this application in availability configuration
Empty panel view has working add button in Operational Panels
Empty panel view has working add button in App Analytics

Issues Resolved
[List any issues this PR will resolve]
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #603 (dbe358e) into main (af54d6a) will increase coverage by 19.00%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #603       +/-   ##
=============================================
+ Coverage     53.32%   72.33%   +19.00%
  Complexity      271      271
=============================================
  Files           238       38      -200
  Lines          7748     2136     -5612
  Branches       1581      236     -1345
=============================================
- Hits           4132     1545     -2587
+ Misses         3421      429     -2992
+ Partials        195      162       -33

Flag
Coverage Δ

dashboards-observability
?

opensearch-observability
72.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...lic/components/custom_panels/custom_panel_view.tsx

...onents/custom_panels/panel_modules/empty_panel.tsx

...tom_panels/panel_modules/panel_grid/panel_grid.tsx

...isualization_container/visualization_container.tsx

...ules/visualization_flyout/visualization_flyout.tsx

...ks/components/paragraph_components/para_output.tsx

...tics/components/common/plots/service_map_scale.tsx

...nents/custom_panels/helpers/custom_input_modal.tsx

...mponents/flyout_components/trace_detail_render.tsx

...blic/components/visualizations/charts/vis_types.ts

... and 190 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 af54d6a...dbe358e. Read the comment docs.


fix: Replaced println with logMessage in DriverJar

Replaces System.out.println with logMessage in DriverJar so as to only print out log messages if the driver is in debug mode.

I can understand that - I wonder if it would be possible to print to stderr instead of stdout? This aligns with the unix standard streams practice
My personal use case is in CLI applications when using a remote browser for the automation, this debug message means I cannot pipe my output to other programs.
Originally I changed to logMessage because of the precedent set a few lines below when checking for a remote selenium url:
https://github.com/microsoft/playwright-java/blob/1e8adde480b50474b892992b34443a1fa7b9bab5/driver-bundle/src/main/java/com/microsoft/playwright/impl/driver/jar/DriverJar.java#L80-L83


Update README

Coverage remained the same at 82.974% when pulling 829ea2c8081c8c5f15d871e50c48fb4cb0a3029e on marcwebbie:develop into f4ca2b258cac408f55956f1125c0fc76c29382e5 on knowledge4life:develop.


Fix for the SVG SubPath Issue.

Fix for the SVG SubPath Issue. Now subpaths are rendered correctly.

Subpath bug BEFORE the Fix:

Subpath bug AFTER the Fix

Diff without whitespace changes: https://github.com/praeclarum/NGraphics/pull/62/files?w=1

@praeclarum Frank can you merge this, please? I need to share a project on GitHub with those fixes and I don't want to create a fork with the fix and a separate Nuget.

I don't like accepting changes with all these whitespace breaks - ruins history and blame.

To be fair, the official Microsoft C# coding guidelines, followed by the vast majority of C# developers, recommends using 4-space indents.

Contribution Etiquette
Anyway, these are good changes. If @Emasoft doesn't want to fix this PR then I can use the diffs to hand merge this puppy. I just don't like that @Emasoft would lose the credit.

I would love to fix it, but I don't know how. I just loaded the project in Xamarin Studio, and it uses the Visual Studio code formatting settings by default:

Is there a unix/osx shell script I can use to revert the .cs file to your formatting preferences?
What formatting standard are you using? Is there a specific formatting policy file to use for this project? A mandatory policy file to use would be great for avoiding messing up the formatting.
If you use a specific formatting policy, you can export them from Xamarin Studio -> Policies.. -> Export , like this:

If you export it, I can load it in Xamarin Studio and apply it to the source code. Or you can do this yourself as an additional commit of this pull request. If it is impossible to do, then hand merge it. I'm not happy to lose the credit but at least it will be merged. Thank you!

The problem isn't that your formatting is wrong, it's that you reformatted the whole file. Simply don't do that.
You must have a setting somewhere that reformats the whole document on change. Just turn that off or don't hit that command.
I am not using a formatting policy. Please just look at the file and match what is already being done.

I have the option "Xamarin Studio -> Preferences -> Behaviour -> Format document on save.. " on, because I like my code to be always formatted.  I will switch this off in the future. But for now is there a way to fix this applying a new formatting scheme like the one you use?

Yeah, sorry this project should have a policy in the solution so you can have your auto format be safe. I'll look into this...
I'm afraid the only way to fix this is to rebase from master and apply the changes by hand again.
Sorry for trouble. I do appreciate the work. If you're unwilling to do it, I can merge myself.

@praeclarum I don't disagree with you, I was just playing Devil's Advocate


Distance - Amount shows 0.03 instead of being blank when removing a waypoint offline

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.77-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com
Create a distance expense with three waypoints.
Go to transaction thread.
Go offline.
Click Distance.
Remove the last stop.
Save the new distance.

Expected Result:
The Amount field should be empty while it is still pending (production behavior).
Actual Result:
The Amount field shows 0.03.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/dbf59832-7f01-445d-a249-d1c36acc1da1

View all open jobs on GitHub

@greg-schroeder FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

@nkdengineer @neil-marcellini @akinwale thoughts on https://github.com/Expensify/App/issues/42784#issuecomment-2138052077?

It's late for me now. I'll create a PR to fix this bug in the morning.

Should this continue to be a blocker till @nkdengineer comes back online and fixes it?

Let's remove it from the list of deploy blockers (requires being offline to reproduce, making it pretty low prio), but have @nkdengineer get a fix up tomorrow

@akinwale The PR to fix regression here https://github.com/Expensify/App/pull/42833.

Thanks for being on top of it. @fedirjh, it looks like you're the lucky reviwer.

Nice thanks @nkdengineer!

This happens offline, so not a web deploy blocker.

I will review the PR.

Bump I think @akinwale and also @deetergp on this PR review: https://github.com/Expensify/App/pull/42833

I ended up having nothing to do with that PR. Should @akinwale & @neil-marcellini be on this one?

This was a regression from https://github.com/Expensify/App/issues/41817


FTU Explorer future feature request

@LibbyUX  @bherr2
Changes that could make the FTU explorer look better:

Can we make the FTU library shrinkable?
same with the biomarker section
A clickable icon to zoom in or zoom out from the FTU illustration.

Attached is an image for your reference:

Thank you @supriyabidanta for stopping by my desk and for submitting these details!
Bruce and I will discuss what we can do in 2024. We will keep your feature requests documented here for safekeeping, for now! Thanks for reaching out and getting this conversation started!

Supriya & Libby meeting notes!
Thanks for the great lunch and meeting today, @supriyabidanta!
Zoom feature notes
Check feasibility with Bruce for potential options for zooming into the illustration:

Drag to select zoom area
Magnify button with a plus and minus
Pan on drag on zoomed in image

Other features covered:

Collapse FTU listing to give more space for illustration
Fixed width for right side matrix & source data

Source data collapse or default small logic for small amounts of source data

Potential menu consolidation for embedding illustration, downloading, DOI metadata, and downloading data

Note that download data button should not show if we don't have data for the illustration

@LibbyUX Katy is requesting to add dataset metadata including volume, sex, etc. She is thinking we may need to add more metadata to the bottom right table.

@bherr2 yes, I think we're going to need a filter for the source data table eventually. Below is an early iteration of the entry point. I see this being a modal overlay with filter options for the table. Let me know if that's feasible!

FTUs with FIBI images: 9th release feature request
@supriyabidanta and I discuss adding FIBI images to the FTU Explorer for 9th release:

About 10 FTUs could link to relevant FIBI images (GIF) for analysis
Currently, the FIBI GIFs are hosted elsewhere (see resources below).

Supriya and I discussed routing users to those URLs, but we may want to design/build UI for it. More information is needed.

In the app, this feature request could look like:

An icon button next to the FTU name in the FTU Library list
A picture in picture + button/menu that routes out in the illustration panel

Before more work begins: More information is needed on the UI vision from @katyb. Infrastructure expectations from @bherr2 also must be better understood.
Resources

FIBI image from Supriya: https://ucdavis.app.box.com/s/uud09avu64ebv3uoly8l8jzehzgwdxx9/file/1662710560707

Low fidelity mockups


Make shuffle reproducible

This way we still get different orders on different client machines,
preventing long lived connections from all hitting the first or second
server, but also for reloads we get a consistent ordering that does not
invalidate the HAProxy state file (which assumes your backends don't
change order).

@minkovich this will help a lot with conflicts during synapse reloads/restarts. I asked on the HAProxy mailing list and Baptiste pointed me towards the server id option, which we can totally use to make it work 100% I believe (even if the order does shift around).
That change is a bit ... more involved though, so I was thinking of doing that change separately from this one. Or I can group them together, which do you prefer?

@jolynch That makes sense. I'm in favor of smaller changes.

@minkovich I oopsed and fixed the whole problem. I believe that the solution in this pull request should make things work 100% with the state file since we remember the id that we assigned backends last go around.
I'm slightly concerned with how this potentially conflicts between haproxy_server_options and haproxy_server_id ... but ... I think it's fine.
This should fix many of the issues brought up in #238 (not the DOWN part, but it should make the HAProxy state file actually work) . @StephanErb heads up

@minkovich I like the reverse map because it also paves a way forward for supporting minimal reload synapse. Right now it doesn't quite work, but I think it would be relatively easy to pre-allocate a bunch of servers, stop writing out the names, and just go by id. We can change the socket commands to use the "#puid" variant (instead of "name" and we're in business.
So basically we'd pre-allocate a bunch of servers and then dynamically set server <backend>/<#puid> addr and we never have to restart ever again heh.

@jolynch Is the plan still to merge this PR then make the larger refactor? We are blocked from rolling out some of the new feature of HAProxy (#238).

I'm going to merge this tomorrow, just getting back from a trip.

@minkovich @StephanErb can you guys build from a sha or do you need a release? I wanted to roll it out here first and make sure it works before cutting a release but I can cut one if you need it.

Thanks a lot for the patch!
Testing this one out before cutting a release sounds fine to me.

We recently upgraded synapse and now haproxy cannot be loaded:
2017-09-14T03:02:21.040206+00:00 localhost.localdomain user.notice [ALERT] - 256/030220 (20806) : parsing [/etc/haproxy/haproxy.cfg:10313] : 'server i-xxx:yyyy' : 'id' : custom id 2 already used at /etc/haproxy/haproxy.cfg:10292 ('server i-zzz:yyyy')

@darnaut can you supply the HAProxy backend that is affected (server lines) and the synapse watcher configuration for that backend? Thanks :-)
Also you might want to make an issue report instead of commenting on this PR, up to you.

Turned out I had to rollback a few more commits for downgrade to work.
Would appreciate if new features such as time came disabled by default so rollout can be separated from upgrades.

@darnaut this change should be fully backwards compatible (fwiw it was with our config). Previously Synapse was not managing server ids and the change should prefer ids provided in server_options (the only way previously to provide a server id). If you provide the info from ^^ I can help you debug what's going on :-)

@jolynch Sorry, I'm confused. You are saying this is not enabled by default?

@darnaut It is enabled by default, but it should be fully backwards compatible with previous configs
(specifically if someone was previously setting server ids, this change should respect those settings over the generated ones).
This change fixes a bug (that the ordering of servers changes per reload and that we don't give HAProxy servers consistent ids through reloads). It is should not provide breaking functionality. If Synapse was outside a 0.X release this would be a "minor" version bump. If it broke your config then clearly I made a mistake, but having some more details will help fix it so that future folks don't have an issue :-)

@jolynch Thanks for the explanation. Well, it clearly broke for us. Also our config has several hundred services, so will take a while to isolate that and pinpoint exactly what is causing the config to break. Also, and more pressing, there is some other problem in master branch that causes several haproxy instances after synapse is restarted due to disabled backends disappearing from haproxy config.

@darnaut The line that you posted has the line number of the HAProxy config that is invalid, if you can include that server line's backend (all the servers in the enclosing backend) and the relevant synapse service watcher config, I can try to figure out what went wrong (possibly need the synapse state file's entry for that service watcher as well but we'll see).


Add container-related words

https://code.visualstudio.com/remote/advancedcontainers/add-nonroot-user

devcontainer
NOPASSWD

Thanks!


proxying only some versions of crates from crates.io

Hi,
I'm trying to setup kellnr 5.1.1 to use as a proxy for crates.io, however, when I try to run cargo fetch I get the following error:
$ cargo fetch
    Updating `kellnr-cratesio` index
error: failed to select a version for the requirement `ahash = "^0.8"`
candidate versions found which didn't match: 0.4.0, 0.3.8, 0.3.7, ...
location searched: `kellnr-cratesio` index (which is replacing registry `crates-io`)
required by package `sqlx-core v0.7.0`
    ... which satisfies dependency `sqlx-core = "=0.7.0"` of package `sqlx v0.7.0`
    ... which satisfies dependency `sqlx = "^0.7"` of package `config-rest-service v2024.1.28 (/home/pcampbell/projects/tasyn/main/crates/services/config-rest-service)`
    ... which satisfies path dependency `config-rest-service` of package `tasyn v2024.1.28 (/home/pcampbell/projects/tasyn/main/crates/main)`
perhaps a crate was updated and forgotten to be re-vendored?

This works when my ~/.cargo/config is unmodified and is contacting crates.io directly.
When I add the following to ~/.cargo/config I get the error as above:
[registries]
kellnr = { index = "sparse+https://********:443/api/v1/crates/", token = "***" }
[source.crates-io]
replace-with = "kellnr-cratesio"
[source.kellnr-cratesio]
registry = "sparse+https://********:443/api/v1/cratesio/"

When I inspect the cratesio_index table within the sqlite database, I can see that only the first ~49 versions of the ahash crate have been added to the database.

Hi @kemitix!
I tried to reproduce the issue but failed, as ahash is correctly pulled on my machine. Can you describe your setup of kellnr for me, such that I can replicate it?
Do you use Kellnr on bare metal or as a container? Do you use the sqlite or postgresdb backend?

Hi @secana
Here is my docker-compose.yml:
version: "3.3"
services:
  kellnr:
    image: ghcr.io/kellnr/kellnr:5.1.1@sha256:50ed600736e1b561eaf2c1bf960f7d320e5d4525ae0c6574d380f8d033526f8a
    restart: unless-stopped
    volumes:
      - ./data:/opt/kdata
    ports:
      - 8089:8000
    environment:
      KELLNR_ORIGIN__PROTOCOL: https
      KELLNR_ORIGIN__HOSTNAME: crates.***.net
      KELLNR_ORIGIN__PORT: 443
      # KELLNR_LOG__LEVEL: trace
      KELLNR_REGISTRY__MAX_CRATE_SIZE: 1000
      KELLNR_PROXY__ENABLED: true
      KELLNR_DOCS__ENABLED: true
      KELLNR_DOCS__MAX_SIZE: 1000

It is hosted behind Caddy as a reverse proxy:
https://crates.***.net:443 {
    reverse_proxy :8089
}

@kemitix I still fail to reproduce the issue. Can you please run kellnr with the log level "trace" and provide the logs? Maybe there is a hint, why not all versions are pulled from crates.io

@secana I believe I've found the problem. I have a squid proxy that I use with HTTPS_PROXY and HTTP_PROXY environment variables. I suspect my proxy isn't resolving my kellnr instance's hostname. I can look into that myself. :)
The logs that led me that that were these, when I tried a cargo build from a shell that we using the squid proxy:
crates-kellnr-1  | 2024-02-04T18:08:34.460860Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/num-traits
/num-traits-0.2.16.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
crates-kellnr-1  | 2024-02-04T18:08:34.492042Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/utf8parse/
utf8parse-0.2.1.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
crates-kellnr-1  | 2024-02-04T18:08:34.492020Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/taglib/tag
lib-1.0.0.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
crates-kellnr-1  | 2024-02-04T18:08:34.493168Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/taglib-sys
/taglib-sys-1.0.0.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
crates-kellnr-1  | 2024-02-04T18:08:34.496635Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/quote/quot
e-1.0.33.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)

I unset HTTPS_PROXY and unset HTTP_PROXY, then tried cargo build again, and this time it worked.
Thanks for you help, but the problem does appear to be with my own networking.


step-ca: fix hash

Description of changes
For whatever reason, I see a hash mismatch for step-ca. Did they update the tag?
# nix build github:nixos/nixpkgs/82ecf9f777f0482e479d1318232c0a0845a2fe63#step-ca
error: hash mismatch in fixed-output derivation '/nix/store/12jk4y5jdl3r292fyh59ci7dwk2xdhry-source.drv':
         specified: sha256-G+oahvBbMW8vs1DublFAC1rREmQ7Q1r7rNNS0+gnfPE=
            got:    sha256-byVWNab6Q3yryluhMomzLkRNfXQ/68pAq+YGFjbvX1o=
error: 1 dependencies of derivation '/nix/store/w5pq2wxcici3p01xvilzrj0qmi7pqvix-step-ca-0.27.2.drv' failed to build

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 330616 run on aarch64-darwin 1

1 package built:

step-ca

I've asked in the smallstep discord to see if there was a re-tag

I asked, and there was no re-tag. Also, https://github.com/NixOS/nixpkgs/pull/326657 happened after the latest release was created on GitHub, so there is relatively high confidence there is no re-tag.


search not working

hi,
i've deployed docker-registry-frontend as documented, but search doesn't seem to work, i have those kind of error in my logs:
[Sat May 02 13:28:14.333742 2015] [proxy:error] [pid 32:tid<PHONE_NUMBER>99840] [client <IP_ADDRESS>:38711] AH00898: DNS lookup failure for: http: returned by /v1/search, referer: http://localhost:8787/

here how my docker container works:
0509177dde48        docker_registryfrontend:latest    "/bin/sh -c $START_S   5 hours ago         Up 5 hours          443/tcp, <IP_ADDRESS>:8787->80/tcp   docker_registryfrontend_1
047fd208f3cd        registry:0.9.1                    "docker-registry"      5 hours ago         Up 5 hours          <IP_ADDRESS>:5000->5000/tcp          docker_registry_1

they are linked together
if i try a request using wget/curl from the container 0509177dde48 it works:
root@0509177dde48:/# wget http://registry:5000/v1/search
converted 'http://registry:5000/v1/search' (ANSI_X3.4-1968) -> 'http://registry:5000/v1/search' (UTF-8)
--2015-05-02 15:15:06--  http://registry:5000/v1/search
Resolving registry (registry)... <IP_ADDRESS>
Connecting to registry (registry)|<IP_ADDRESS>|:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 90 [application/json]
Saving to: 'search'

search                                     100%[========================================================================================>]      90  --.-KB/s   in 0s

any clues about why using the webui it doesn't work ?

What happens if you execute wget http://localhost:8787/v1/_ping or wget http://localhost:443/v1/_ping. Those two request should forward directly to http://registry:5000/v1/search or https://registry:5000/v1/search respectively.
Please let me know how you've started your containers? The docker-registry-frontend won't simply work with implicit linking. Instead it is designed to work with environment variables where you can specify hostnames/ip addresses and ports.

hi ,
tried both URL and i have a 502 error (quite the same message as before), i use docker-compose to start.
here is the yml file:
registry:
image: registry:0.9.1
ports:
- "5000:5000"
environment:
- SEARCH_BACKEND=sqlalchemy
- SETTINGS_FLAVOR=local
- STORAGE_PATH=/registry
registryfrontend:
#build: docker-registry-frontend
image: konradkleine/docker-registry-frontend
links:
- registry:registry
ports:
- "8080:80"
environment:
- ENV_DOCKER_REGISTRY_HOST=http://registry
- ENV_DOCKER_REGISTRY_PORT=5000
any tips maybe ?

Hi,

registryfrontend:
#build: docker-registry-frontend
image: konradkleine/docker-registry-frontend
links:

registry:registry
ports:
"8080:80"
environment:
ENV_DOCKER_REGISTRY_HOST=http://registry
ENV_DOCKER_REGISTRY_PORT=5000

My first guess: get rid of the links section and the http:// for the host env as it will be added automatically.

if i remove the links, then the name registry won't be resolved by the container :(
second guess is a nice tip, i'll try it and let you know

Sorry about that. I thought the name registry was resolvable even without the link. I suggest you keep the link and only remove the http://.

no worries :) just tried without the "http://" and it works perfectly !
thanks a lot


Get TBB and TRF loopback working

Only TX loopback not working, but that's possibly because Tim doesn't have an antenna hooked up yet.  ;)

Proof of our successful loopbacks:

Note that we need to stay at a low samplerate (because setting CGEN too high causes problems a la https://github.com/JuliaComputing/xtrx_julia/issues/41), and that the TRF loopback should be done on a low frequency for now, to avoid needing to switch TX band.


Make EthereumClient timeouts configurable

Closes #713
More info on https://gnosis-py.readthedocs.io/en/latest/quickstart.html#gnosis-eth

Coverage remained the same at 88.304% when pulling 85ab4f7b6e77c6953307ae545c1c50d6025df8d0 on configure-rpc-timeout into 28b0846e78e2df23509b75ebe967c08a9ddabda4 on master.


Add mid-song instruments change for MIDI importing

Is your feature request related to a problem? Please describe.
When importing a MIDI file with channels changing instruments mid-song, the program only use one instrument by channel for the whole song (except for percussion (10th) channel).
Describe the enhancement you'd like
Make that the program can recognize and perform mid-song instruments change when importing a midi.
I think it may be possible, as it already exists for the percussion channel (10th).

Duplicate of #179


Improve error handling for verified user bypass

skip_for_now.click() is raising an ElementNotInteractableException for me.

Thanks @hudcap and @burkematthew ! :)


Community::SSO::AssignmentGroup needs version number bump

This Pull Request shows that the code for Community::SSO::AssignmentGroup was updated to upgrade it from node 14 to node 20.
https://github.com/org-formation/aws-resource-providers/pull/139
However the sso/assignment-group/package.json file wasn't updated to bump the version number so it is still on version 0.3.1
The other providers I use had a version bump to 1.0.0 in their package.json files in the same pull request and they all upgraded okay.
But without a bump to the version for the SSO assignment group provider, org-formation can't tell there was a change to deploy it.
AWS has stated the following:

Extensions using Node.js 14 and Python 3.7 cannot be registered in additional regions or accounts starting January 9, 2024. You can continue to publish updates to the existing extension until February 8, 2024, at which time you will no longer be able to update the extension without first updating to a supported runtime.

The Feb 8th date is fast approaching and I was hoping to have this provider upgraded before then.

updated the specific provider to have version: 1.0.0 in its package JSON.
in my expectation the package would have been updated regardless of this version number.
Is there something in specific that made you believe it did not update when updating the URL to the package?
or just seemed the right thing to doL have the package version bumped to reflect the change.
I am asking out of curiosity, no more.

Is there something in specific that made you believe it did not update when updating the URL to the package?

I didn't change the URL to the package because it doesn't change if the version number hasn't changed does it?
It remained as s3://community-resource-provider-catalog/community-sso-assignmentgroup-0.3.1.zip
When I bumped the versions of my other providers, the relevant part of the pipeline looked as follows:
INFO: Executing: include tasks/register-types/tasks.yml.
INFO: Executing: register-type Community_Organizations_EbsEncryptionDefaults.
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>74/us-east-1 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>04/us-east-1 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>86/us-east-1 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>04/ap-southeast-4 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>86/ap-southeast-4 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>86/ap-southeast-2 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>74/ap-southeast-2 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>74/ap-southeast-4 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>83/ap-southeast-2 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>04/ap-southeast-2 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>34/us-east-1 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>37/ap-southeast-4 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>83/ap-southeast-4 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>83/ap-southeast-2 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>34/ap-southeast-2 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>83/us-east-1 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>83/us-east-1 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>34/ap-southeast-4 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>83/ap-southeast-4 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>37/ap-southeast-2 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>10/us-east-1 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>61/us-east-1 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>61/ap-southeast-4 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>10/ap-southeast-4 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>22/us-east-1 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>22/ap-southeast-4 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>37/us-east-1 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>22/ap-southeast-2 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>10/ap-southeast-2 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>61/ap-southeast-2 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>52/us-east-1 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>52/ap-southeast-4 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Workload Community_Organizations_EbsEncryptionDefaults in<PHONE_NUMBER>52/ap-southeast-2 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Task Community_Organizations_EbsEncryptionDefaults execute successful.
INFO: Executing: register-type Community_Organizations_NoDefaultVPC.
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>04/us-east-1 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>04/ap-southeast-4 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>74/us-east-1 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>86/us-east-1 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>74/ap-southeast-4 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>04/ap-southeast-2 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>86/ap-southeast-4 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>86/ap-southeast-2 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>74/ap-southeast-2 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>83/ap-southeast-2 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>83/us-east-1 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>37/ap-southeast-2 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>83/ap-southeast-4 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>83/us-east-1 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>34/us-east-1 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>83/ap-southeast-2 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>34/ap-southeast-4 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>37/ap-southeast-4 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>34/ap-southeast-2 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>83/ap-southeast-4 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>37/us-east-1 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>61/us-east-1 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>10/us-east-1 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>10/ap-southeast-4 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>22/ap-southeast-4 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>22/us-east-1 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>10/ap-southeast-2 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>61/ap-southeast-4 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>22/ap-southeast-2 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>61/ap-southeast-2 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>52/us-east-1 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>52/ap-southeast-4 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Workload Community_Organizations_NoDefaultVPC in<PHONE_NUMBER>52/ap-southeast-2 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Task Community_Organizations_NoDefaultVPC execute successful.
INFO: Executing: register-type Community_S3_PublicAccessBlock.
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>74/us-east-1 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>86/ap-southeast-4 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>04/ap-southeast-4 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>86/us-east-1 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>74/ap-southeast-2 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>74/ap-southeast-4 update successful.<PHONE_NUMBER>74 = AnalyticsAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>04/ap-southeast-2 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>86/ap-southeast-2 update successful.<PHONE_NUMBER>86 = CallCentreAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>83/ap-southeast-2 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>04/us-east-1 update successful.<PHONE_NUMBER>04 = Dev-healthengineAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>83/us-east-1 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>34/us-east-1 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>83/us-east-1 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>83/ap-southeast-4 update successful.<PHONE_NUMBER>83 = FreddyHollowAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>34/ap-southeast-4 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>37/ap-southeast-2 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>37/ap-southeast-4 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>83/ap-southeast-2 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>34/ap-southeast-2 update successful.<PHONE_NUMBER>34 = HealthEngineAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>83/ap-southeast-4 update successful.<PHONE_NUMBER>83 = HealthEngineBackupsAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>10/ap-southeast-4 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>22/us-east-1 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>61/us-east-1 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>10/us-east-1 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>37/us-east-1 update successful.<PHONE_NUMBER>37 = HealthEngineSecurityAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>22/ap-southeast-4 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>61/ap-southeast-4 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>10/ap-southeast-2 update successful.<PHONE_NUMBER>10 = SharedServicesAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>22/ap-southeast-2 update successful.<PHONE_NUMBER>22 = PatienCubeAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>61/ap-southeast-2 update successful.<PHONE_NUMBER>61 = SharedComplianceAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>52/ap-southeast-4 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>52/ap-southeast-2 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Workload Community_S3_PublicAccessBlock in<PHONE_NUMBER>52/us-east-1 update successful.<PHONE_NUMBER>52 = ManagementAccount)
INFO: Task Community_S3_PublicAccessBlock execute successful.
INFO: Executing: register-type Community_SSO_AssignmentGroup.
INFO: register-type workload Community_SSO_AssignmentGroup already up to date.
INFO: Task Community_SSO_AssignmentGroup execute successful.
INFO: Task RegisterTypes execute successful.

Here you see Community_Organizations_EbsEncryptionDefaults, Community_Organizations_NoDefaultVPC, and Community_S3_PublicAccessBlock being updated.
However for Community_SSO_AssignmentGroup it just says:
INFO: Executing: register-type Community_SSO_AssignmentGroup.
INFO: register-type workload Community_SSO_AssignmentGroup already up to date.
INFO: Task Community_SSO_AssignmentGroup execute successful.

Then I checked if they've been updated using: aws cloudformation list-types --query 'TypeSummaries[].{TypeName:TypeName,LastUpdated:LastUpdated}' and get:
[
    {
        "TypeName": "Community::Organizations::EbsEncryptionDefaults",
        "LastUpdated": "2024-01-31T02:41:58.570000+00:00"
    },
    {
        "TypeName": "Community::Organizations::NoDefaultVPC",
        "LastUpdated": "2024-01-31T02:49:11.202000+00:00"
    },
    {
        "TypeName": "Community::S3::PublicAccessBlock",
        "LastUpdated": "2024-01-31T02:56:11.850000+00:00"
    },
    {
        "TypeName": "Community::SSO::AssignmentGroup",
        "LastUpdated": "2021-09-22T01:50:13.494000+00:00"
    }
]

So the last updated date for Community::SSO::AssignmentGroup is still in 2021 while the others were updated when the pipeline ran.
My tasks/register-types/tasks.yml file referenced above looks like the following:
Parameters:
  <<: !Include ../../parameters.yml

# Community resource type to enable EC2 EBS encryption by default
Community_Organizations_EbsEncryptionDefaults:
  MaxConcurrentTasks: 10
  OrganizationBinding:
    Account: '*'
    IncludeMasterAccount: true
    Region: !Ref allRegions
  ResourceType: Community::Organizations::EbsEncryptionDefaults
  SchemaHandlerPackage: s3://community-resource-provider-catalog/community-ec2-ebsencryptiondefaults-1.0.0.zip
  Type: register-type

# Community resource type to facilitate removing the default VPC.
Community_Organizations_NoDefaultVPC:
  MaxConcurrentTasks: 10
  OrganizationBinding:
    Account: '*'
    IncludeMasterAccount: true
    Region: !Ref allRegions
  ResourceType: Community::Organizations::NoDefaultVPC
  SchemaHandlerPackage: s3://community-resource-provider-catalog/community-organizations-nodefaultvpc-1.0.0.zip
  Type: register-type

# Community resource type to facilitate blocking public S3 access.
Community_S3_PublicAccessBlock:
  MaxConcurrentTasks: 10
  OrganizationBinding:
    Account: '*'
    IncludeMasterAccount: true
    Region: !Ref allRegions
  ResourceType: Community::S3::PublicAccessBlock
  SchemaHandlerPackage: s3://community-resource-provider-catalog/community-s3-publicaccessblock-1.0.0.zip
  Type: register-type

Community_SSO_AssignmentGroup:
  MaxConcurrentTasks: 10
  OrganizationBinding:
    Account: '*'
    IncludeMasterAccount: true
    Region: !Ref allRegions
  ResourceType: Community::SSO::AssignmentGroup
  SchemaHandlerPackage: s3://community-resource-provider-catalog/community-sso-assignmentgroup-0.3.1.zip
  Type: register-type

So I don't know if I should be doing something differently here?
Thanks for bumping the version. I'll update the line that installs it to use version 1 and I should be good to go.

Closing this as resolved as the version number was bumped quite some time ago.


Catalan Number Python Scripts

Created two scripts for this sequence,
One imports python's math module for factorials. The other calculates factorials 'manually'.
Wasn't sure which one would be preferred so here is both.

I think it's good to have both so people have access to more options.


Exchange

Working exchange contract + many other updates.
Please merge this before it drifts further from master.

for Exchange contracts, suppose the collateral ratio=1.5, for a exchange/Federal Reserve in order to lend $4 dollar to users, exchange should have eos which worth at least $6


[url_launcher] A problem occurred configuring project ':url_launcher_android'

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I just intalled url_launcher package and i'm getting errors at the compilation.
Expected results
I expect a successfull compilation with my apk.
Actual results
Ther compilation doesn't works.
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:url_launcher/url_launcher.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int phoneNumber =<PHONE_NUMBER>;

  void _call() async {
    Uri phoneUri = Uri.parse("tel:$phoneNumber");
    if (!await launchUrl(phoneUri) && mounted) {
      showDialog(context: context, builder: (_) => const Text("Error"));
    }
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text('Phone number:'),
            Text(
              '$phoneNumber',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _call,
        tooltip: 'Call',
        child: const Icon(Icons.phone),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':url_launcher_android'.
> Could not load compiled classes for build file 'C:\Users\Asmitta\AppData\Local\Pub\Cache\hosted\pub.dev\url_launcher_android-6.2.0\android\build.gradle' from cache.
> Failed to notify project evaluation listener.
   > Could not get unknown property 'android' for project ':url_launcher_android' of type org.gradle.api.Project.
   > Could not get unknown property 'android' for project ':url_launcher_android' of type org.gradle.api.Project.

Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.13.2, on Microsoft Windows [version 10.0.19045.3570], locale fr-FR)
    • Flutter version 3.13.2 on channel stable at C:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ff5b5b5fa6 (2 months ago), 2023-08-24 08:12:28 -0500
    • Engine revision b20183e040
    • Dart version 3.1.0
    • DevTools version 2.25.0

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at C:\Users\Asmitta\AppData\Local\Android\sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[X] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[X] Visual Studio - develop Windows apps
    X Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[√] Android Studio (version 2021.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[√] VS Code (version 1.83.1)
    • VS Code at C:\Users\Asmitta\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.74.0

[√] Connected device (2 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [version 10.0.19045.3570]
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 118.0.2088.76

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Additional info
Android_manifest.xml :
<manifest xmlns:android="http://schemas.android.com/apk/res/android">

    <queries>
        <intent>
            <action android:name="android.intent.action.VIEW" />
            <data android:scheme="https" />
        </intent>
        <intent>
            <action android:name="android.intent.action.VIEW" />
            <data android:scheme="tel" />
        </intent>
    </queries>

    <application
        android:label="test"
        android:name="${applicationName}"
        android:icon="@mipmap/ic_launcher">
        <activity
            android:name=".MainActivity"
            android:exported="true"
            android:launchMode="singleTop"
            android:theme="@style/LaunchTheme"
            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
            android:hardwareAccelerated="true"
            android:windowSoftInputMode="adjustResize">
            <!-- Specifies an Android theme to apply to this Activity as soon as
                 the Android process has started. This theme is visible to the user
                 while the Flutter UI initializes. After that, this theme continues
                 to determine the Window background behind the Flutter UI. -->
            <meta-data
              android:name="io.flutter.embedding.android.NormalTheme"
              android:resource="@style/NormalTheme"
              />
            <intent-filter>
                <action android:name="android.intent.action.MAIN"/>
                <category android:name="android.intent.category.LAUNCHER"/>
            </intent-filter>
        </activity>
        <!-- Don't delete the meta-data below.
             This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
        <meta-data
            android:name="flutterEmbedding"
            android:value="2" />
    </application>
</manifest>

android/build.gradle:
buildscript {
    ext.kotlin_version = '1.7.10'
    repositories {
        google()
        mavenCentral()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:7.3.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

tasks.register("clean", Delete) {
    delete rootProject.buildDir
}

android/gradle.properties:
org.gradle.jvmargs=-Xmx1536M
android.useAndroidX=true
android.enableJetifier=true

Hi @Asmitta-01. Thanks for filing this. Can you upgrade to the latest versions of flutter and of the package and try building again?
Also, Can you share the full logs received when you attempt to build if issue persists?

I've updated Flutter
...
Downloading windows-x64/font-subset tools...                       987ms

Flutter 3.13.9 • channel stable • https://github.com/flutter/flutter.git
Framework • revision d211f42860 (9 days ago) • 2023-10-25 13:42:25 -0700
Engine • revision 0545f8705d
Tools • Dart 3.1.5 • DevTools 2.25.0

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.13.9, on Microsoft Windows [version 10.0.19045.3570], locale fr-FR)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[X] Visual Studio - develop Windows apps
    X Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2021.3)
[√] VS Code (version 1.83.1)
[√] Connected device (2 available)
[√] Network resources

Then flutter clean and flutter build apk --debug.
PS C:\Users\Asmitta\StudioProjects\test> flutter build apk --debug
Resolving dependencies... (3.9s)
  collection 1.17.2 (1.18.0 available)
  flutter_lints 2.0.3 (3.0.0 available)
  lints 2.1.1 (3.0.0 available)
  material_color_utilities 0.5.0 (0.8.0 available)
  meta 1.9.1 (1.11.0 available)
  stack_trace 1.11.0 (1.11.1 available)
  stream_channel 2.1.1 (2.1.2 available)
  test_api 0.6.0 (0.6.1 available)
  web 0.1.4-beta (0.3.0 available)
Got dependencies!

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':url_launcher_android'.
> Could not load compiled classes for build file 'C:\Users\Asmitta\AppData\Local\Pub\Cache\hosted\pub.dev\url_launcher_android-6.2.0\android\build.gradle' from cache.
> Failed to notify project evaluation listener.
   > Could not get unknown property 'android' for project ':url_launcher_android' of type org.gradle.api.Project.
   > Could not get unknown property 'android' for project ':url_launcher_android' of type org.gradle.api.Project.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 7s
Running Gradle task 'assembleDebug'...                              9,0s
Gradle task assembleDebug failed with exit code 1

Same result

Up.
I even tried to use old package, it is the same error.

Thanks for your response. I created a new flutter project on my end, added this package and I couldn't reproduce this. Can you try out the suggested solutions here https://stackoverflow.com/questions/57439197/could-not-get-unknown-property-android-for-root-project-android-of-type-org to see if any works in your case?

I followed your link but the solutions there doesn't match my needs(or i don't know how to apply it). I ran again the build --debug but verbose(-v) this time, here are the logs: https://pastebin.com/Dk7FSJcn.
If it is working on your sample project can you please share your build.gradle files ? It might be useful.

Right there are the same. I really don't know the problem. I will look for an alternative to url_launcher.
Thanks

Thanks for your response. You might want to also try creating an entirely new flutter project, add the url_launcher package and see if this issue still exists, so you could narrow down where the conflict could be in the existing app.
Also, you can see https://flutter.dev/community for resources and ask more questions on this,
you may also get some help if you post it on Stack Overflow.
Closing, as this doesn't seem to be an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Add support for new metadata

Feature Request
Desired behaviour
Need to support metadata change from dct to schema.org with http://www.commonwl.org/user_guide/17-metadata/ as an example

i.e. we should read author information from one or the other, depending on which one is available


Annotate base.html strings for translation.

I found out recently that apparently the word wrapping in these files has no significance whatsoever. I'm going to have to figure out how to get it to stay consistent later so I stop getting these giant diffs for no reason.

Thanks for the reviews!


bug: Time Picker can't display midnight (12:00AM)

Type: bug
Ionic Version: 2.x
Platform: mobile webview
Whenever I open a time that is set to midnight (12:00AM), it seems that the time picker switches to 1:00AM instead.
To reproduce, make an ion-datetime showing time in the HTML
<ion-datetime displayFormat="h:mm A" pickerFormat="h mm A" [(ngModel)]="startDate"></ion-datetime>
bind it to a variable in the TS:
startDate: String = new Date().toISOString();
Then run it, and select midnight as the time then, and then immediately tap the field again to edit the time, and when the time picker opens it up shows 1AM instead of midnight. It happens regardless of what the minutes are set to (12:00AM through 12:59AM exhibits this behavior).
I've also posted the issue here in the forum:
https://forum.ionicframework.com/t/ionic-2-bug-time-picker-cant-show-midnight/86000
Is there a fix?
Thanks!
Jacob

I am seeing this behavior, as well. From my analysis, the time picker can select midnight, and it does update the backing variable correctly. However, when you open the picker, it initializes to 1AM as described above. All other hours seem to work as expected.

This is still a problem in the 3.x releases.

Is anybody working on this?  I cannot imagine this is a particularly complex problem to solve.


Fixed sym issue in "Find Percent Change" tool #496

Layer file reference was on "Activity with PercentChange" dataset object; removed from this object and added it to the "Output Percent Change" dataset object.
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.

@elinz
Unfortunately I've checked out the changes to Incident Analysis Tools_10.4.tbx and the symbology still isn't being picked up. I know it isn't something you did and if I look at the model I can see that the "output" variable has the correct .LYR associated. But somehow it's still not being used.....

@elinz
Then again if I look closer ... the LYR is pointing to:
D:\GitHub\solutions-geoprocessing-toolbox\patterns\data\layers\PercentChange.lyr
which doesn't exist.
It should (when I open it) be pointing to:
D:\GitHub\solutions-geoprocessing-toolbox\patterns\toolboxes\layers\PercentChange.lyr
and then...

@elinz Go ahead and delete your el-find-percent-change-sym-issue branch.


if-examples

It would be nice if there were an example or two of how to use the if link option.  I have been trying a few things, but they never seem to work.  I'm probably over thinking it, but a simple example may help me and others get it right,

Ah makes sense, there is no if example in the README. Thanks for pointing this out!
A tl;dr on if is that it executes what follows in the shell, and it looks at the return value. You can see some examples in the PR: https://github.com/anishathalye/dotbot/pull/173
Btw, happy to try to help you out with your particular config file (it could help me learn how the readme needs to be modified, too). Feel free to post your config file / the particular example you're trying to get working, if you'd like.

Example added in 8667b75a7338a773ae2d91d7185e29197613ee36.


Ability to read particular length from stream

Hi.
I think it's would be great to have possibility to read chunks with specified length since commonly dealing with binary protocols looks like
$lengthBytes = fread($fd, 4); // read Int32 Length
$length = unpack('Llength', $lengthBytes)['length'];
$packet = fread($fd, $length);

Not sure about possibility to make InputStream behave like public function read(?int $length = null): Promise;, but maybe some buffering class similar to LineReader would be useful, for example:
class LengthReader
{
    public function __construct(InputStream $inputStream);

    public function readLine(int $length): Promise;
}

We didn't include any length in the stream read operation on purpose, because it would complicate all stream implementations and will be less efficient if it didn't buffer internally, due to many small reads.
For our Http2Parser we use a custom function, but it also uses a \Generator based parser instead of using promises. For simply uses a wrapper class could also directly offer readInt32 and similar methods.
I think we already have such an implementation somewhere, I just don't remember where.

I created my own buffered stream implementation for MadelineProto, still gotta split it from the main project aaaa

I would like to suggest something like following:

class BinaryBuffer
{
    public function __construct(InputStream $inputStream);

    public function read(int $length) : string

    public function unpack(array $format) : Promise<array>
}

Which is inpired by https://github.com/clue/php-socks/blob/a9cd68376de2edb97278dbefc994f679e9360248/Socks/StreamReader.php#L19-L42
And it could be used like:
$buffer = new BinaryBuffer($stream);

try {
    yield $buffer->read(4); // some padding bytes
} catch (UnexpectedStreamClosedException $e) {
    // stream was closed unexpectedly
} catch (NotEnoughInputException $e) {
    // stream was ended before 4 bytes were received
}

try {
    ['length => $length, 'magic' => $magic, 'version' => $version] = yield $buffer->unpack([
        'length' => 'L',
        'magic'  => 'C',
        'version' => ['a', 16], // well, I know it's looks not well. need some better idea
    ]);

    [$packet] = yield $buffer->unpack([
        ['a', $length]
    ]);
} catch (UnexpectedStreamClosedException|NotEnoughInputException $e) {
    // the same as before
}

You can now use BufferedReader in v2.x.


Extension of the window object no longer works in 1.0.0-beta.17

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.17
node: 6.9.1
os: win32 x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
No, it was created using the CLI

The log given by the failure.

Normally this include a stack trace and some more information.
run-time error is "window.myAPI undefined."

Mention any other details that might be useful.
It appears that the extension of the window object no longer works in the new version.
I have a myAPI.js file that looks like this...
var myAPI = myAPI || {};
(function(myAPI) {
...
...
}(myAPI));
window.myAPI = myAPI;
I have a myAPI.d.ts file that has this interface defined in it (nothing else).
interface Window {
myAPI: any;
}
In my Typescript code i used to be able to write window.myAPI.XXX and it would work fine, i recently updated to the above version and it's not working anymore.
The error message is that window.myAPI is undefined.
This was the ng --version details from the version where this was previously working.
angular-cli: 1.0.0-beta.10
node: 6.3.0
os: win32 x64
Was something changed that stops this sort of thing from working between 1.0.0-beta.10 and 1.0.0-beta.17?

Thanks! We'll be in touch soon.

The issue was this:
Due to the modularization introduced with the newer version it was not bootstrapping the "myAPI.d.ts" file that had the interface defined in it.
In order to resolve this, the interface definition needed to be added to a module, component or service that was then imported and declared in "app.module.ts".
Once this was in place it worked as expected.


[14.0x] ISPN-14740 Reuse EMPTY Metadata when lifespan and maxIdle are not pro…

…vided
https://issues.redhat.com/browse/ISPN-14740

Closed per https://github.com/infinispan/infinispan/pull/10779#issuecomment-1497703482


403 when accessing the docs

There seems to be something wrong when accessing the docs, I have a 403 at https://docs.sciml.ai/NeuralOperators/stable/.

The link should point to https://sciml.github.io/NeuralOperators.jl/dev.


Add support for completions within the endpoint context

Purpose

Resolves #4944

Goals

With this improvements, we add the support of content suggestions inside the endpoint definition
scope. This includes the constraint scope and the connector init scope.

Approach

Shall we remove functions as completion items in endpoint constraint.


Fix builds for ruby 2.3.x

Apparently a gem update --system is needed in order to install
binman ~> 5.1.0. Moreover, I've also specified the exact binman
version that we want just in case.
Finally, I've also taken the chance to update the ruby versions being
tested to their latest patch-level releases. The ruby versions being used
for SLE12 and openSUSE are left untouched.
Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

lgtm


Add sni support for https

Depends on https://github.com/esp-rs/esp-idf-svc/pull/136 and https://github.com/espressif/esp-idf/pull/9833

Depends on #136
Isn't this the other way around? As in #137 depending on this one?

Also, shouldn't we wait until https://github.com/espressif/esp-idf/pull/9833 is merged first?

No and yes :)
#136 adds the https server itself, and this pr extends that with support for sni. This pr is actually based on that pr, and is a superset of that one.
Yes, espressif/esp-idf#9833 needs to be merged before this can work, but I wanted this opened so it can be reviewed and used by others looking for sni support.

rebased on the merge https server. It fixes a few issues with build on idf master as well.

@axos88 I have not forgotten about this one, but I hope you don't mind I'll review & merge this post-release of the current esp-idf-svc crate. Release is due in a matter of a couple of days actually. We'll issue a subsequent incremental release with your changes then.

Thanks @ivmarkov, the upstream changes to esp IDF have been merged, but as I started to use the changes here, i realized a lot of stuff need to be done in a different/better way. I'll need to update this pr before it's worth to spend time reviewing it

Thanks @ivmarkov, the upstream changes to esp IDF have been merged, but as I started to use the changes here, i realized a lot of stuff need to be done in a different/better way. I'll need to update this pr before it's worth to spend time reviewing it

Np, I'll wait.


Adds the CodeIgniter package type: 'theme'

Hi, write test, please. Example:
https://github.com/composer/installers/blob/master/tests/Composer/Installers/Test/InstallerTest.php#L105
https://github.com/composer/installers/blob/master/tests/Composer/Installers/Test/InstallerTest.php#L231


ListSettingsObject has private constructor

I would like to extend ListSettingsObject and override getValueHumanReadable() method, but I can't call super(builder) in constructor.

fixed in 1.1.4

Thank you!


refactor: Endorsement flow (BE)

[x] Modify request schema endorsement API
[x] Modify sign and submit functionality for w3c schema endorsement

This task is completed.


fix(plugin-form-builder): use escapeHTML on submission data in serializeLexical

Description
Fixes #8109
Note this should also be merge in payload/beta!

[X] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[X] Existing test suite passes locally with my changes

The CI tests are failing on the v3 PR https://github.com/payloadcms/payload/pull/9799 with these changes. I am going to revert this to give pause on the changes without further testing and understanding.


The handling of the authentication token for helmi is changing, and i…

…t will require the jobs to run with a login shell. Add -l to the example ahead of time
Adding -l forces the job to read ~/.bashrc, and that is required to find the project-specific authentication token.

Close, not relevant anymore.


[$250] App crashes when try to open workspace manage members page after login from deeplink url reported by @0xmiroslav

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login to any account
Go to Settings -> Workspaces -> select any workspace -> Manage members page
Copy url link
Logout
Visit copied url link
Login to same account

Expected Result:
Manage members page shows
Actual Result:
App crashes
Workaround:
unknown
Platform:

Where is this issue occurring?

Web

Version Number: 1.2.23-7
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/199802418-d4749c1b-f8b8-4a1a-9606-82a82923fe34.mp4
https://user-images.githubusercontent.com/43996225/199802451-bb84f9ca-7fa8-48cd-aa53-8bce55e0709f.mov
Expensify/Expensify Issue URL:
Issue reported by: @0xmiroslav
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1667468386668709
View all open jobs on GitHub

👍 reproducible

Job posting: https://www.upwork.com/jobs/~01449e67e1aa0a0f9d

Proposal
Problem
In https://github.com/Expensify/App/blob/533e63ce8b13e573024784836cef0bb7e859e937/src/pages/workspace/WorkspaceMembersPage.js#L294
we get the details from personalDetails, but when we visit this page directly after login, personalDetails is undefined (response from service has not been returned yet)
Solution
We need to check personalDetails is undefined. if yes we'll fallback to using the default default value
-            const details = this.props.personalDetails[email] || {displayName: email, login: email, avatar: Expensicons.FallbackAvatar};
+            const details = (this.props.personalDetails && this.props.personalDetails[email]) || {displayName: email, login: email, avatar: Expensicons.FallbackAvatar};

https://user-images.githubusercontent.com/113963320/199895066-4a4f1e60-a3ed-4824-a573-480d137c8fef.mp4

Thanks for looking into it @tienifr. Proposal looks good but can you please share an updated proposal using lodashGet

FullPageNotFoundView can be seen at other pages too.
If you follow the steps below can see this at workspace initial page
Steps:-
1.Go to settings
2. Go to to workspaces > open a workspace
3. Copy the URL
4. Sign out > paste the URL and press enter
5. Now login
I don't think displaying the loading indicator at only workspace members page will do any good.
@NikkiWines, should we deal with this issue here?

Updated proposal
Solution
We need to check personalDetails is undefined. if yes we'll fallback to using the default default value
-            const details = this.props.personalDetails[email] || {displayName: email, login: email, avatar: Expensicons.FallbackAvatar};
+            const details = lodashGet(this.props.personalDetails, 'email') || {displayName: email, login: email, avatar: Expensicons.FallbackAvatar};

@thesahindia Thank for your review, I updated my proposal above.

@thesahindia bump on reviewing @tienifr's updated proposal ☝ thanks!

I am waiting for @NikkiWines thoughts at https://github.com/Expensify/App/issues/12435#issuecomment-1304359257

Sorry for the delay @thesahindia, I've been OOO.

I don't think displaying the loading indicator at only workspace members page will do any good.
@NikkiWines, should we deal with this issue here?

While both are definitely problems, I think we should handle them in separate issues. The app crashing issue is specific to the workspace members page, but the momentary "Hmmm...it's not here"  issue is a problem for all workspace pages.
In which case, the expectation for the correct behavior for this issue would be that the "Hmm... it's not there" page shows briefly before the manage members page loads as expected.

Posted the other issue on slack.
Let's fix the crash.
@tienifr, you aren't using the lodashGet correctly.

@NikkiWines, let's assign @tienifr since they proposed a working solution we just need to use lodashGet
C+ reviewed 🎀👀🎀

@thesahindia You're right, change to use lodashGet like:
const details = lodashGet(this.props.personalDetails, email, {displayName: email, login: email, avatar: Expensicons.FallbackAvatar}); is the best solution. Thanks

Umm, my bad. I didn't look at the console.
@NikkiWines, let's assign @0xmiroslav ? As their proposal will also fix console errors.
C+ reviewed 🎀👀🎀

Yep, sounds good. Agreed we want to fix console errors. @NicMendonca can you hire @0xmiroslav for this role, please? Thanks!

@0xmiroslav please apply for the job here

Can we make sure to always hire the Contributor on the GH itself next time @NicMendonca ?

This is due for payment on Nov 22, but we need to address the BZ checklist. Sorry I didn't have time to get to it before going OOO.

Asked in #bug-zero about the placement for the regression test

Invites sent to the New Upwork job as the old one expired.

Yep! Had that noted, reminders never hurt though!

@MitchExpensify, I didn't get the 50% bonus. It also applies to the C+ reviewer

Fixed and paid 50% bonus for both now, thanks!


Make wandb:output available as an assert variable

Not sure what the operations which will be needed to support generic assertions on output lines
regex match is probably the first useful thing... but do we need logic operators then?  do we need multiline regex?

Done.  added in 0.7.14


Vulnerability roundup 73: pango-1.42.4: 1 advisory

search, files

[ ] CVE-2019-1010238 (nixos-19.03)

Scanned versions: nixos-19.03: 31d476b8797. May contain false positives.

Fixed long ago by https://github.com/NixOS/nixpkgs/commit/451edb5f11d4f1672f33c20659261b0c70b69e2e


🐛Bug: Select inside dialog causes dialog to close when an item is selected

Describe the bug
Selecting an item from a Select component inside a dialog causes the dialog to close (I suppose due to the way the outsideClick logic is handled). This also happens with any element outside the dialog (e.g. an always on display bottom navbar with a hamburguer button that opens the dialog (and changes to a X button to close it when the dialog is open).
To Reproduce
Steps to reproduce the behavior:

Go to https://www.sveltelab.dev/2kezbln53cyozjz
Click on 'Open Dialog' button
Select a flavor from the Select inside the Dialog
See error (dialog closes)

Expected behavior
Dialog shouldn't close when selecting a item from a Select component inside the dialog

Thanks for raising this issue! @buhodev since there are two bugs, please create a separate issue for the second bug 😄

Thanks for raising this issue! @buhodev since there are two bugs, please create a separate issue for the second bug 😄

Done https://github.com/melt-ui/melt-ui/issues/452 :wink:

https://stackblitz.com/edit/kit-ts-tw-melt-mclbpf?file=package.json seems to be still an issue on 0.39.0

https://stackblitz.com/edit/kit-ts-tw-melt-mclbpf?file=package.json seems to be still an issue on 0.39.0

0.39.0 does not try to address this issue, this is expected.

The same happens inside of a Popover. It appears the select isn't respecting any portal parent's and is always portalling to the body, even when portal: null

The same happens inside of a Popover. It appears the select isn't respecting any portal parent's and is always portalling to the body, even when portal: null

Interestingly though, when you "fix" this by providing portal: selector, to the dialog portal element, it now nests inside correctly, yet the closing on select issue persists


Mention initial copyright year

I am not a lawyer but according to http://www.copyright.gov/circs/circ01.pdf (See screenshot of relevant section below) , listing the first year of publication in the copyright is a good thing

:+1: