pluginManagement{} config from init scripts is not given priority over the "settings.gradle" one

Expected Behavior
When adding a pluginManagement{} configuration in an initialization script, it should be given priority over the pluginManagement{} configuration from the "settings.gradle" file.
In instance Gradle should look in the plugin repositories from the initialization script before the plugin repositories from the "settings.gradle" file.
Current Behavior
When adding a pluginManagement{} configuration in an initialization script, it is not given priority over the pluginManagement{} configuration from the "settings.gradle" one.
In instance Gradle looks in the plugin repositories from the "settings.gradle" file before the plugin repositories from the initialization script.
Context
Same context than #4920:
At our company, we use an internal Artifactory instance for proxying dependencies from public repositories on developer laptops and CI builds. This increases resolution speed and insulates us from potential downtime in the upstream repositories. It also allows us to seamlessly resolve proprietary dependencies alongside public dependencies.
So it is important that our internal repositories have priority over the public ones.
Steps to Reproduce
// settings.gradle
pluginManagement {
    repositories {
        gradlePluginPortal()
    }
}

include ':app'

// init.gradle
settingsEvaluated { settings ->
    settings.pluginManagement {
        repositories {
            maven {
                url "http://<my artifactory url>/artifactory/maven"
            }
        }
    }
}

Your Environment
distributionUrl=https://services.gradle.org/distributions/gradle-4.10.1-all.zip

RepositoryHandler is a NamedDomainObjectCollection, so I suppose you could remove all existing repositories, add yours, then re-add the repositories you initially removed.
We actually do something similar in our init script where we remove all the Maven repositories and add our Sonatype Nexus proxy (we don't re-add repositories afterwards though); and we also warn if there exist other, non-Maven, repositories that we won't be able to proxy through our Nexus.

I think something like @tbroyer suggested is the right thing here.  settingsEvaluated means it runs after the settings script is evaluated.

Clear the existing repositories.
Add your repositories.
Optionally, restore the repositories from step 1.

Thank you @tbroyer and @big-guy for your support.
Following your suggestions, I did the following modifications to my Gradle initialization script:
// init.gradle
settingsEvaluated { settings ->
    settings.pluginManagement {
        // Print repositories collection
        println "Repositories names: " + repositories.getNames()
        // Clear repositories collection
        repositories.clear()
        // Add my Artifactory mirror
        repositories {
            maven {
                url "http://<my artifactory url>/artifactory/maven"
            }
        }
        // Print repositories collection
        println "Repositories names: " + repositories.getNames()
    }
}

So now, the pluginManagement{} config from my initialization scripts is overwriting the "settings.gradle" one.


Feature request: Choose notification tone

Just as the title says. Right now the default notification sound is used. I'd like to customize it so I can better differentiate by sound a task or, for example, an email.

Vote up for this.
Would be really great to have this feature.

Voted up.
Notification tone on my phone is a simple very short sound but my calendar notification tone, for example, is a 4sec long sound so I cannot miss it and can even wake up hearing it.

Duplicate of #124


bug in the UI

I have an issue with the UI of the expression.
if in the DB you see this (off_for=&on_for=IT123):

in the UI I see (off_for=, on_for=IT123):

and if I click on update without updating anything, in the DB it becomes:

and also in the UI it cuts it:

looks like that although in the UI it shows "," - for having it work you need to put ";" (off_for=*;on_for=IT123)
is this a known bug? anyway to fix it?
Thanks

Expression in DB (off_for=&on_for=IT123): is tranformed to (off_for=, on_for=IT123): in the UI
This "issue" seems to be related to multiple init_param. (it's a map). In the DB is serialized with &characters. When displayed in the UI it's separated by ','. Problem occur when parsing the field in the UI it seems.

Switching to SpringJDBC, SameDb, Same Data
ff4j.setFeatureStore(new FeatureStoreSpringJdbc(dbcpDataSource));
ff4j.setPropertiesStore(new PropertyStoreSpringJdbc(dbcpDataSource));
ff4j.setEventRepository(new EventRepositorySpringJdbc(dbcpDataSource));
ff4j.audit(true);

Again ...cannot reproduce BUG....
Am i missing something there ?

Any update on this @amichaiu  ?

Hi.
I will try to do a change on the latest version that fixes the problem and let you know. I did a change on our version (1.3.1) but I think it would be better for the community to have a fixed updated version.
Mainly the fix I did in our version is to show the parameters of the map with “;” between them (like when you pars it) rather than the default “,” that the map uses.
I will do the change on the new version later, see it works and try to create a pull request (or send you the 1 or 2 files with the change)
Thanks
Amichai
From: Cédrick Lunven<EMAIL_ADDRESS>Sent: Sunday, June 18, 2017 9:36 PM
To: clun/ff4j<EMAIL_ADDRESS>Cc: Amichai Ungar<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [clun/ff4j] bug in the UI (#228)
Any update on this @amichaiuhttps://github.com/amichaiu ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/clun/ff4j/issues/228#issuecomment-309294722, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Absmz1As9k7AdrWJMtjheSkERGaUmwqoks5sFW4NgaJpZM4NpTJa.

Hi Cedrik. your sample works great. I guess something in the newer version fixed it. the issue can be closed. thanks a lot!

Great, good news !!


Use a proper Version format

<key>CFBundleShortVersionString</key> <string>3.0.8 :074a131:</string>
Please remove the colons + spaces from the Version string.
For Reference have a look at:
https://en.wikipedia.org/wiki/Software_versioning
http://semver.org/

This is an unfortunate consequence of how the keys in the info.plist are used by standard Apple tools (as an example: crash reports) and the ability to identify a unique revision when using a DVCS (like git) as apposed to something like svn where each revision can be identified by a monotonically increasing number (used by CFBundleVersion).
The best answer to these problems is for Apple to add a CFBundleRevision key to the info plist without the formatting restrictions of CFBundleVersion or to redefine the allowed formatting in CFBundleVersion; in any case I encourage you to file a radar on this subject with Apple as they use the number of duplicate reports to assign priorities.


modify DuIE_Baseline/re_official_evaluation

更新DuIE竞赛评估脚本；并修改基线评估脚本python版本

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 All committers have signed the CLA.


Exposure History Update/Remove Redundant Push

Continues to look good to me !

CI taking a good long look!


Labels configured, but nothing in the UI

I see the "Site and group settings" option in the sensitivity label configuration UI, but the labels are not appearing in the SharePoint Admin Center or when I create a new Team/SP Site. I've contacted Microsoft Support who are saying that I just need to wait for the public preview to hit my tenant. Is this the case or can anything be "pushed" to my tenant to enable the features?

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0d40ac52-6f02-b0f3-0c45-9f359473703b
Version Independent ID: 108355a9-05a3-4d17-c417-c4d5664a4506
Content: Use sensitivity labels with Microsoft Teams, Office 365 groups, and SharePoint sites (public preview)
Content Source: microsoft-365/compliance/sensitivity-labels-teams-groups-sites.md
Service: o365-seccomp
GitHub Login: @KCCross
Microsoft Alias: krowley

Hi, the information from Support is correct. Thanks.

Do you have any target date for this features to be available instead of Public Preview?

The Microsoft 365 roadmap is our authoritative source for coming features. We try to avoid forecasting release dates within documentation because engineering schedules can change. https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=Microsoft Information Protection


Non-Selective Query Error for Opportunity Cascade Delete

This occurs when OPP_CascadeDeleteLookups_TDTM  queries for GAU Allocations where the Opportunity or the Payment's Opportunity is in the set of deleted Opportunities. In orgs with more than 200,000 relevant records or if an index threshold is hit, this error is returned. I believe we might see this one come up more frequently as orgs might be using a default GAU for all of their Opportunities and/or we have orgs with large volumes that could definitely have skewed GAUs.
return [
          SELECT Opportunity__c
          FROM Allocation__c
          WHERE Opportunity__c IN :opportunityIds
               OR Payment__r.npe01__Opportunity__c IN :opportunityIds
      ];
}

We changed this query in 3.148 to also search in the GAU Allocation's Payment's Opportunity; not sure if that exacerbated this issue.
Knowledge Article
https://help.salesforce.com/articleView?id=000323572&type=1&mode=1

Likely Reason #1: "1. You may find that the query in question needs to be more selective in the WHERE clause. According to the Salesforce standards & best practices - the where clause needs to subset 10% or less of the data."
The WHERE clause currently contains Id fields, though it is a composite filter

StackTrace:
CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: npsp.TDTM_RecurringDonation: execution of AfterUpdate caused by: System.DmlException: Delete failed.
First exception on row 0 with id 006xxxxxxxxxxxxxxx;
first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, npsp.TDTM_Opportunity: execution of BeforeDelete caused by: System.QueryException:
Non-selective query against large object type (more than 200000 rows). Consider an indexed filter or contact salesforce.com about custom indexing. Even if a field is indexed a filter might still not be selective when:

The filter value includes null (for instance binding with a list that contains null)
Data skew exists whereby the number of matching rows is very large (for instance, filtering for a particular foreign key value that occurs many times)

Class.npsp.OPP_CascadeDeleteLookups_TDTM.CascadeDeleteLoader.load: line 65, column 1
External entry point Class.npsp.CDL_CascadeDeleteLookups.CascadeDelete.load: line 175, column 1
Class.npsp.CDL_CascadeDeleteLookups_TDTM.runBeforeDelete: line 91, column 1
Class.npsp.CDL_CascadeDeleteLookups_TDTM.run: line 68, column 1
Class.npsp.TDTM_TriggerHandler.runClass: line 193, column 1
Class.npsp.TDTM_TriggerHandler.run: line 113, column 1
Class.npsp.TDTM_Config_API.run: line 92, column 1
Trigger.npsp.TDTM_Opportunity: line 33, column 1: []

The context for the customer Case is a Recurring Donation update causing all related Opportunities to be deleted and reinserted (this happens with any update to fixed-length RDs or if an open-ended RD's Installment Period or Contact changes). Specifically in that Case, this is the initial stacktrace that led to the error above:
Class.npsp.RD_RecurringDonations.handleRecurringDonationUpdate: line 869, column 1
Class.npsp.RD_RecurringDonations_TDTM.run: line 109, column 1
Class.npsp.TDTM_TriggerHandler.runClass: line 193, column 1
Class.npsp.TDTM_TriggerHandler.run: line 113, column 1
Class.npsp.TDTM_Config_API.run: line 92, column 1
Trigger.npsp.TDTM_RecurringDonation: line 33, column 1

Steps To Repeat
Likely the fastest way would be to create an org with 1 GAU and have all >200,000 Opportunities associated with that GAU via GAU Allocations. I ran into this same issue in a test org where I deliberately had skew; the majority of my GAU Allocations were soft deleted and I still ran into this error even when attempting to delete a single Opportunity until I hard deleted the GAU Allocations.

Create GAU
Create 200,000 Opportunities with GAU Allocations for that GAU
Delete 1 or more Opportunities

**lurch: add

Tracking W-037942

Included in beta release 1.0 (Beta 2)


Connection Card match previous styles, fix kebab

Fix kebab misalignment
Add dropshadow to card on hover, remove underline and hyperlink color
Improve aesthetics of card, add padding and increase height
Change check for techPreview and rename tech-preview class in footer to config-required, which makes more sense.

Hover:

fix #249

PR Storybook available here


Fixed the alignment & the darkmode glitch

Related Issue #540

Description
Hello @cleveranu, @Shreyaar12
I have fix page properly and added the darkmode. also Shreyaar12 told me to fix the glitch which was happening when we hover the project card so that issue is also fixed.As well as the footer issue of extra spacing is also fixed.
Card glitch Screenshot-

So eventually I fixed -

Page Alignment Fixed
Darkmode Added
Added font
fixed scrolltotop color
projects card glitch fixed

It is super ready to merge.
Video
Screencast from 06-08-23 08:40:37 PM IST.webm

Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

Good labels are really appreciated.

@cleveranu I think you forgot to review this.


License and open source

Need to decide on a License and add to the project.
We also need to open source - this might require detaching the fork from the original SEDC_FONAG repo (which can be done via some combo of the github chatbot and getting the owner of SEDC_FONAG (Wouter) to take some action.

The fork has been detached, acknowledgements added to the README, repo made public and BSD-3 license file added.


Use YAML stages

Resolves aspnet/AspNetCore#11924 and https://github.com/dotnet/arcade/blob/master/Documentation/CorePackages/YamlStagesPublishing.md for EFCore. @dougbu @JunTaoLuo should I port this to any of the release branches (once I have it working)?
@JohnTortugo @bricelam PTAL
Here's the internal build, which looks to be using stages just fine: https://dev.azure.com/dnceng/internal/_build/results?buildId=300829

New internal build w/ these changes rebased against rel/6.3: https://dnceng.visualstudio.com/internal/_build/results?buildId=301201

New build with the dup'd commits + channel mapping: https://dnceng.visualstudio.com/internal/_build/results?buildId=301574

Internal build looks good. @riarenas @johntortugo any last concerns, or is this good to go?


Support out outbound link tracking

This adds support for Outbound Link Click Tracking. Tests and documentation have been updated. Closes #8 https://github.com/4lejandrito/next-plausible/issues/8.

Looks very good at first glance. I'll fully review and merge soon.
Thanks @IGassmann.

Looks awesome, no changes on my side.
I just published 1.6.0:
npm i<EMAIL_ADDRESS>
Thanks a lot @IGassmann!


Feature request

The additions to the Phil/Celia announcements are awesome, thanks!
Could you add options to include "A trolley service of drinks and light refreshments is available on the train" and similar please?

Duplicate of #220
See my explanation of why it's not yet possible on that page.

Oh, sorry, I assumed this was for live trains. The options will come at the same time I manage to get this working for live trains, which is hopefully in the next 2 weeks.


Unhandled Rejection (TypeError): Cannot read property 'write' of undefined

This is where the error is pointing me:
DerivedLogger.(anonymous function)
/Users/Tom/Desktop/mq/projects/electron-app/node_modules/winston/lib/winston/create-logger.js:45:13
Here is my logger:
window.logger = winston.createLogger({
  level: 'error',
  format: winston.format.json(),
  transports: [
    new winston.transports.File({ filename: 'error.log', level: 'error' }),
    new winston.transports.Console()
  ],
});

Here is where i'm calling it:
try {
....
}
catch (err) {
			window.logger.error(err)
}

https://github.com/winstonjs/winston/pull/1279 should fix this.


kubernetes: upgrade to 1.28.3 to address CVE-2023-44487 and CVE-2023-…

…39325

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

kubernetes: upgrade to 1.28.3 to address CVE-2023-44487
Change Log

Change
Change
Change

Does this affect the toolchain?

NO
Associated issues

#xxxx

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2023-44487

Test Methodology

Pipeline build id: xxxx

can you please link the buddy build, and the other CVE in the description?


Update Kontrolo for Minecraft 1.19

Another Minecraft release! As such, Kontrolo needs updating to the latest version.

Close in #8


Adjust layout and language for Forgot password?

make the Username field shorter (using the standard short/half width same as #68 )
revise heading: "Forgot password?"
revise message below heading: "Please enter your email below and we will send instructions to reset your password."
revise blue notice message after user enters email (screenshot 2): "Notice: You will receive an email with instructions to reset your password in a few minutes."
revise failure message if email address not found (screenshot 3): "There is no account associated with that email address. Please try again or Contact us."
format this message with a yellow bar and "x" icon like other error messages

1 -

2 -

3 -

a couple of small revisions to the messages:

remove "about how" from the success message so the text is as follows: "Notice: You will receive an email with instructions to reset your password in a few minutes."
add an "x" symbol and "Error" to message for incorrect email so the text is as follows: "x Error: There is no account associated with that email address. Please try again or Contact us."

error message is fixed. please just revise the text for the success/Notice message (screenshot below) as follows:

remove "about how" from the success message so the text is as follows: "Notice: You will receive an email with instructions to reset your password in a few minutes."

This message is stored in devise's localized files. I had updated the en_US version but not the en_GB. Will update that one as well

ah, thanks @briri


Order for DependsOnGroups  has changed after TestNg 7.4.0

TestNG Version
7.5 not working
7.4 works
Expected behavior
s3
s1
s2
Actual behavior
s1
s2
s3
Is the issue reproducible on runner?

[ ] Maven
[ ] Eclipse
[ ] IntelliJ

Test case sample
Here is an example for BeforeSuite, but the same problem exists for all configuration methods. The same issue also for dependsOnMethod
    @BeforeSuite(groups = { "g1" })
    public void s3() {
        System.out.println("s3");
    }

    @BeforeSuite(groups = { "g2" }, dependsOnGroups = "g1")
    public void s2() {
        System.out.println("s2");
    }

    @BeforeSuite(groups = { "g2" }, dependsOnGroups = "g1")
    public void s1() {
        System.out.println("s1");
    }

    @Test()
    public void test3() {
        System.out.println("test3");
    }

I have tried to find the commit where the fault was introduced, but my IDE did not like to switch gradle version and I'm new at gradle.

As I understand it When we add back the sorting based on groups we get cyclic dependencies. If the methods are spread out to different classes.
And as I understand it the problem is this method, where a a method dependency is added to solve issues that methods in base classes are executed before the methods in the test classes. And If we add group dependsOn we get duplicated dependencies which give the cyclic dependencies.
MethodInheritance.fixMethodInheritance()
m2.addMethodDependedUpon(MethodHelper.calculateMethodCanonicalName(m1));

@martinaldrin I think you got some part of the design issue.
You can add test cases in a PR if you have some in mind ;)

Hi @juherr, Yes I understand part of the problem now. but I have no clue about how to solve it and I guess I will need your expert help to solve it. Yes I will add more unit tests to my PR.

But after more digging. I actually think the behavior that we try to protect in test.configuration.issue2432.IssueTest is wrong.
Test expect following behaviour:
"prepareConfig",
"uploadConfigToDatabase",
"verifyConfigurationAfterInstall",
"prepareConfigForTest1",
"test1"

I belive that following behaviour is correct:
"prepareConfig",
"prepareConfigForTest1",
"uploadConfigToDatabase",
"verifyConfigurationAfterInstall",
"test1"

both prepareConfig and prepareConfigForTest1 have the group "prepareConfig" and therefor I they should be executed first regardless of which class they are in. If we don't want that that behavior I think the groups between the classes should be different.  otherwise it will not be possible to define groups into different classes.

I created a separate PR where I use my priority implementation to handle the class hierarchy sorting.
But unit test that I showed above needs to be changed, since that will not be possible to solve, without breaking other things.
https://github.com/cbeust/testng/pull/2667

One more PR, showing an alternative solution where I use a different priority to not interfere with the user configurations.
https://github.com/cbeust/testng/pull/2668

@martinaldrin Thanks for all your contributions.

I guess I will need your expert help to solve it.

To be honest, I've no idea how to deal with it because, except for selection, the groups feature is not yet clearly designed and may be difficult to integrate into the current base code.

@juherr I think it works pretty well for everything except for one that was recently implemented after 7.4 release.
With my changes I think groups starts to work as it did before


Performance on NVIDIA GPU (discrete) seems to be much worse than AMD (integrated) GPU - is that expected?

I have an integrated AMD GPU (512 MB dedicated memory and 11.6GB shared memory) and a discreet NVIDIA GPU (6GB dedicated memory and 11.6 GB shared).
Here are the results that were quite unexpected -

When using AMD, mostly shared memory was used (8.3/11.6 GB) but on NVIDIA it was the dedicated memory(5.7/6 GB). I expected the results to be opposite.
I ran Chrome on NVIDIA and Canary on integrated AMD.
(it did seem to me that different models were loaded but I do not have the screenshot for that)

I think the models were the same.
AMD
[System Initalize] Initialize GPU device: WebGPU - amd
[System Initalize] Fetching param cache[81/163]: 2006MB fetched. 49% completed, 22 secs elapsed. It can take a while when we first visit this page to populate the cache. Later refreshes will become faster.
[System Initalize] Loading GPU shader modules[50/54]: 92% completed, 4 secs elapsed.
NVIDIA
[System Initalize] Initialize GPU device: WebGPU - NVIDIA GeForce RTX 3060 Laptop GPU
[System Initalize] Fetching param cache[55/163]: 1372MB fetched. 34% completed, 10 secs elapsed. It can take a while when we first visit this page to populate the cache. Later refreshes will become faster.
[System Initalize] Loading GPU shader modules[46/54]: 85% completed, 3 secs elapsed.
Performance still seems to be much better with integrated GPU than NVIDIA GPU.

You're being bottlenecked by that 6gb of dedicated GPU memory on the Nvidia laptop GPU, which is constantly swapping data to inference the model, the integrated AMD though doesn't have to swap from its shared memory because all of its memory is shared (really the dedicated gpu memory for it is just reserved shared memory)

@Foxlum  I see, is there any way to somehow make this work faster while using NVIDIA gpu or will this always be a problem as long as the VRAM is less than expected?

Are you sure it's even using the Nvidia card? The WebLLM demo loads the model into the Intel UHD integrated GPUs shared memory on my laptop and processes it there super slowly instead of the 3080 discrete GPU I have.

Yes, if you look at the screenshots I have shared above you can see that it uses the NVIDIA card in the left image.

this is likely due to vram issue, the latest update comes with a smaller model that should be faster


Cleanup: Simplify navigateToMostRecentReport function

cc @marcaaron
Details

Part of https://github.com/Expensify/App/issues/40187.
Fixed Issues

$ https://github.com/Expensify/App/issues/40187
PROPOSAL:
Tests

Test 1 (Leaving a group chat):

Go to any report
Create a group chat
Leave the group chat
Verify you are navigated to the previous report

Test 2 (Leaving a room):

Go to any report
Create a room
Leave the room
Verify you are navigated to the previous report

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

Offline tests

Same as Tests
QA Steps

Same as Tests

[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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[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 verified the translation was requested/reviewed 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.js 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] 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/Expensify/App/assets/16493223/723e073e-e8b6-4e77-b0e0-c20a050b550a

Android: mWeb Chrome

Networking issue

iOS: Native

https://github.com/Expensify/App/assets/16493223/60144a36-5b3e-4229-95ef-7272c4c4e6c6

iOS: mWeb Safari

https://github.com/Expensify/App/assets/16493223/79573afc-6c98-4efc-97ac-9a28d4cf829a

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/16493223/2aca9f52-d436-497a-91da-b0f1b218ded4

MacOS: Desktop

https://github.com/Expensify/App/assets/16493223/bfbb5ff3-1bfa-45b0-8ca2-14d767453050

: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.

🚀 Deployed to staging by https://github.com/marcaaron in version: 9.0.4-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/tgolen in version: 9.0.4-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Build error on MacOS

$ make -f cmake-makefile
cmake -DCMAKE_BUILD_TYPE=Release -DCPU_CORES=12 -DYOSYS_CONFIG= \
              -DYOSYS_PATH= -DCMAKE_INSTALL_PREFIX=/usr/local \
              -DCMAKE_RULE_MESSAGES=on -S . -B build
Using Vendored YOSYS
YOSYS_CONFIG: /Users/gus/synlig/third_party/yosys/yosys-config
YOSYS_INCLUDE_DIR: /Users/gus/synlig/third_party/yosys
Building Synlig version v1.82 []
Building Surelog version v1.82 [37ce1bbf98ca26ba2e18603a271b55ac05e121d5]
CMake Error at third_party/surelog/CMakeLists.txt:101 (add_subdirectory):
  add_subdirectory given source "third_party/antlr4/runtime/Cpp" which is not
  an existing directory.

CMake Error at third_party/surelog/CMakeLists.txt:114 (add_subdirectory):
  The source directory

    /Users/gus/synlig/third_party/surelog/third_party/UHDM

  does not contain a CMakeLists.txt file.

CMake Error at third_party/surelog/CMakeLists.txt:116 (get_target_property):
  get_target_property() called with non-existent target "uhdm".

CMake Error at third_party/surelog/CMakeLists.txt:143 (add_subdirectory):
  The source directory

    /Users/gus/synlig/third_party/surelog/third_party/json

  does not contain a CMakeLists.txt file.

-- Python3_EXECUTABLE = /Users/gus/churchroad/.venv/bin/python3.10
CMake Warning at third_party/surelog/CMakeLists.txt:193 (message):
  Using tcmalloc; if this creates runtime issues, configure with
  -DSURELOG_WITH_TCMALLOC=Off

-- Found tcmalloc: /usr/local/lib/libtcmalloc.dylib
-- Found zlib: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.4.sdk/usr/lib/libz.tbd
-- Java_JAVA_EXECUTABLE = /Library/Java/JavaVirtualMachines/jdk-13.0.1.jdk/Contents/Home/bin/java
CMake Error at third_party/surelog/CMakeLists.txt:827 (install):
  install TARGETS given target "antlr4_static" which does not exist.

CMake Error at third_party/surelog/CMakeLists.txt:840 (install):
  install TARGETS given target "capnp" which does not exist.

CMake Error at third_party/surelog/CMakeLists.txt:846 (install):
  install TARGETS given target "uhdm" which does not exist.

CMake Error at CMakeLists.txt:145 (get_target_property):
  get_target_property() called with non-existent target "uhdm".

CMake Error at CMakeLists.txt:152 (add_subdirectory):
  The source directory

    /Users/gus/synlig/third_party/surelog/third_party/googletest

  does not contain a CMakeLists.txt file.

CMake Warning at CMakeLists.txt:190 (message):
  Using tcmalloc; if this creates runtime issues, configure with
  -DSYNLIG_WITH_TCMALLOC=Off

-- Found tcmalloc: /usr/local/lib/libtcmalloc.dylib
SYNLIG CMAKE_CXX_FLAGS:  -D_YOSYS_ -Wno-unused-parameter -std=c++17 -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free
SYNLIG CMAKE_CXX_FLAGS_RELEASE: -O3 -DNDEBUG -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -Wall -Wno-unused-parameter -O3  -DNDEBUG
SYNLIG CMAKE_CXX_FLAGS_DEBUG: -g -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -Wall -Wno-unused-parameter -O0 -g
CMake Error at CMakeLists.txt:280 (add_dependencies):
  Cannot add target-level dependencies to non-existent target
  "antlr4_static".

  The add_dependencies works for top-level logical targets created by the
  add_executable, add_library, or add_custom_target commands.  If you want to
  add file-level dependencies see the DEPENDS option of the add_custom_target
  and add_custom_command commands.

CMake Error at CMakeLists.txt:281 (add_dependencies):
  Cannot add target-level dependencies to non-existent target "capnp".

  The add_dependencies works for top-level logical targets created by the
  add_executable, add_library, or add_custom_target commands.  If you want to
  add file-level dependencies see the DEPENDS option of the add_custom_target
  and add_custom_command commands.

-- Configuring incomplete, errors occurred!
make: *** [run-cmake-release] Error 1

Did you get the sub-modules?
git submodule sync
git submodule update --init --recursive third_party/{surelog,yosys}

I also needed to install 2 libs.
pip3 install orderedmultidict --break-system-packages
brew install libffi


Write sprint #3 user stories

Write user stories for sprint 3

https://github.com/DIT112-V20/group-06/labels/sprint3


task: create system designs

The system designs should include:

class diagrams
UML diagrams
Interaction diagrams
State Machine diagrams
that will support and show how the system was designed and built from ground-up

Resolved, Use Case and Class Diagram have been created and the repo will be updated with them once some modifications suggested by the project's supervisor have been incorporated


PRE RELEASE - TRIAGE JDK17

Release Summary Report for openjdk17-pipeline
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk17-pipeline/279/
Started by upstream project "build-scripts/weekly-openjdk17-pipeline" build number 54 at 1/16/2022, 7:05:14 AM

create_installer_linux ❌ undefined ❌
create_installer_mac ❌ undefined ❌
create_installer_windows ❌ undefined ❌
jdk17u-alpine-linux-x64-hotspot_SmokeTests ❌ FAILURE ❌
jdk17u-linux-ppc64le-hotspot_SmokeTests ⚠ UNSTABLE ⚠
sign_build ❌ undefined ❌
sign_installer ❌ undefined ❌

Test_openjdk17_hs_extended.functional_x86-64_alpine-linux ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_aarch64_linux ❌ ABORTED ❌
Test_openjdk17_hs_extended.openjdk_arm_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_arm_linux_testList_1 ⚠ UNSTABLE ⚠
jdk_vector_2 => deep history 0/3 passed | possible issues
Test_openjdk17_hs_extended.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_0 ⚠ UNSTABLE ⚠
jdk_net_0 => deep history 0/3 passed | possible issues
jdk_tools_0 => deep history 0/3 passed | possible issues
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_1 ⚠ UNSTABLE ⚠
jvm_compiler_0 => deep history 2/3 passed | possible issues
jdk_beans_1 => deep history 0/3 passed | possible issues
jdk_nio_1 => deep history 0/3 passed | possible issues
jdk_net_1 => deep history 0/3 passed | possible issues
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_2 ⚠ UNSTABLE ⚠
jdk_imageio_0 => deep history 0/3 passed | possible issues
jdk_nio_0 => deep history 0/3 passed | possible issues
jdk_tools_1 => deep history 0/3 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-32_windows ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_0 ⚠ UNSTABLE ⚠
jvm_compiler_2 => deep history 0/5 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_1 ⚠ UNSTABLE ⚠
runtime_nestmate_2 => deep history 0/4 passed | possible issues
jdk_jfr_2 => deep history 0/5 passed | possible issues
jdk_vector_2 => deep history 0/4 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_2 ⚠ UNSTABLE ⚠
jdk_nio_2 => deep history 3/5 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-64_alpine-linux ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_x86-64_linux ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_x86-64_linux_testList_1 ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_x86-64_linux_testList_2 ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_x86-64_windows ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-64_windows_testList_0 ⚠ UNSTABLE ⚠
jdk_tools_0 => deep history 0/5 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-64_windows_testList_2 ⚠ UNSTABLE ⚠
jdk_tools_1 => deep history 0/4 passed | possible issues
Test_openjdk17_hs_extended.perf_x86-64_alpine-linux ❌ FAILURE ❌
Test_openjdk17_hs_extended.system_aarch64_linux ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/19 passed | possible issues
OAuthTest_0 => deep history 0/19 passed | possible issues
Test_openjdk17_hs_extended.system_arm_linux ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/20 passed | possible issues
OAuthTest_0 => deep history 0/20 passed | possible issues
Test_openjdk17_hs_extended.system_ppc64_aix ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/22 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues
Test_openjdk17_hs_extended.system_ppc64le_linux ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/21 passed | possible issues
Test_openjdk17_hs_extended.system_s390x_linux ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/22 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues
Test_openjdk17_hs_extended.system_x86-32_windows ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/22 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/11 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues
Test_openjdk17_hs_extended.system_x86-64_alpine-linux ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/8 passed | possible issues
OAuthTest_0 => deep history 0/8 passed | possible issues
Test_openjdk17_hs_extended.system_x86-64_linux ❌ FAILURE ❌
Test_openjdk17_hs_extended.system_x86-64_mac ⚠ UNSTABLE ⚠
ConcurrentLoadTest_5m_0 => deep history 11/12 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues
Test_openjdk17_hs_extended.system_x86-64_windows ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/22 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues
Test_openjdk17_hs_sanity.functional_aarch64_linux ❌ ABORTED ❌
Test_openjdk17_hs_sanity.functional_x86-64_alpine-linux ❌ FAILURE ❌
Test_openjdk17_hs_sanity.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
jdk_lang_1 => deep history 5/11 passed | possible issues
Test_openjdk17_hs_sanity.openjdk_x86-64_alpine-linux ❌ FAILURE ❌
Test_openjdk17_hs_sanity.openjdk_x86-64_windows ⚠ UNSTABLE ⚠
jdk_lang_1 => deep history 5/12 passed | possible issues
jdk_lang_0 => deep history 5/12 passed | possible issues
Test_openjdk17_hs_sanity.perf_x86-64_alpine-linux ❌ FAILURE ❌
Test_openjdk17_hs_sanity.system_arm_linux ⚠ UNSTABLE ⚠
TestJlmRemoteMemoryAuth_2 => deep history 7/10 passed | possible issues
Test_openjdk17_hs_sanity.system_x86-64_alpine-linux ❌ FAILURE ❌
Test_openjdk17_hs_sanity.system_x86-64_linux ❌ FAILURE ❌
Test_openjdk17_hs_special.functional_x86-64_alpine-linux ❌ FAILURE ❌
Test_openjdk17_hs_special.functional_x86-64_linux ❌ FAILURE ❌

x86-64_linux:  Failed for docker ones : no space left.

[ ] Test_openjdk17_hs_extended.openjdk_x86-64_linux ❌ FAILURE ❌

Test_openjdk17_hs_extended.openjdk_x86-64_linux_testList_1 ❌ FAILURE ❌ : test-docker-fedora33-x64-2
Test_openjdk17_hs_extended.openjdk_x86-64_linux_testList_2 ❌ FAILURE ❌ :  test-docker-fedora33-x64-1

[ ] Test_openjdk17_hs_extended.system_x86-64_linux ❌ FAILURE ❌ : test-docker-fedora33-x64-2 in

[ ] Test_openjdk17_hs_sanity.system_x86-64_linux ❌ FAILURE ❌ : test-docker-ubuntu1804-x64-1

[ ] Test_openjdk17_hs_special.functional_x86-64_linux ❌ FAILURE ❌ : : test-docker-ubuntu2004-x64-1

x86-64_windows:

[ ] Test_openjdk17_hs_extended.openjdk_x86-64_windows ⚠ UNSTABLE ⚠

Test_openjdk17_hs_extended.openjdk_x86-64_windows_testList_0 ⚠ UNSTABLE ⚠
jdk_tools_0 => deep history 0/5 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-64_windows_testList_2 ⚠ UNSTABLE ⚠
jdk_tools_1 => deep history 0/4 passed | possible issues

[ ] Test_openjdk17_hs_extended.system_x86-64_windows ⚠ UNSTABLE ⚠

OAuthTest_0 => deep history 0/22 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues

[ ] Test_openjdk17_hs_sanity.openjdk_x86-64_windows ⚠ UNSTABLE ⚠

jdk_lang_1 => deep history 5/12 passed | possible issues
jdk_lang_0 => deep history 5/12 passed | possible issues

x86-64_mac:

[ ] Test_openjdk17_hs_extended.system_x86-64_mac ⚠ UNSTABLE ⚠

ConcurrentLoadTest_5m_0 => deep history 11/12 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues : https://github.com/adoptium/aqa-systemtest/issues/474
OAuthTest_0 => deep history 0/22 passed | possible issues : https://github.com/adoptium/aqa-systemtest/issues/474

x86-64_alpine-linux:

[ ]  Test_openjdk17_hs_extended.functional_x86-64_alpine-linux ❌ FAILURE ❌: test-docker-alpine311-x64-1 : no space left

aarch64_linux:

[ ] Test_openjdk17_hs_extended.openjdk_aarch64_linux ❌ ABORTED ❌ : timeout

[ ] Test_openjdk17_hs_extended.system_aarch64_linux ⚠ UNSTABLE ⚠ : https://github.com/adoptium/aqa-systemtest/issues/474

OAuthTest_0 => deep history 0/19 passed | possible issues
OAuthTest_0 => deep history 0/19 passed | possible issues

[ ] Test_openjdk17_hs_sanity.functional_aarch64_linux ❌ ABORTED ❌ : timeout

arm_linux:

[ ] Test_openjdk17_hs_extended.openjdk_arm_linux ⚠ UNSTABLE ⚠

Test_openjdk17_hs_extended.openjdk_arm_linux_testList_1 ⚠ UNSTABLE ⚠
jdk_vector_2 => deep history 0/3 passed | possible issues

[ ] Test_openjdk17_hs_extended.system_arm_linux ⚠ UNSTABLE ⚠: Test_openjdk17_hs_sanity.system_arm_linux ⚠ UNSTABLE ⚠
TestJlmRemoteMemoryAuth_2 => deep history 7/10 passed | possible issues

OAuthTest_0 => deep history 0/20 passed | possible issues
OAuthTest_0 => deep history 0/20 passed | possible issues

[ ] Test_openjdk17_hs_sanity.system_arm_linux ⚠ UNSTABLE ⚠

TestJlmRemoteMemoryAuth_2 => deep history 7/10 passed | possible issues

ppc64_aix:
Test_openjdk17_hs_extended.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_0 ⚠ UNSTABLE ⚠
jdk_net_0 => deep history 0/3 passed | possible issues
jdk_tools_0 => deep history 0/3 passed | possible issues
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_1 ⚠ UNSTABLE ⚠
jvm_compiler_0 => deep history 2/3 passed | possible issues
jdk_beans_1 => deep history 0/3 passed | possible issues
jdk_nio_1 => deep history 0/3 passed | possible issues
jdk_net_1 => deep history 0/3 passed | possible issues
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_2 ⚠ UNSTABLE ⚠
jdk_imageio_0 => deep history 0/3 passed | possible issues
jdk_nio_0 => deep history 0/3 passed | possible issues
jdk_tools_1 => deep history 0/3 passed | possible issues
Test_openjdk17_hs_sanity.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
jdk_lang_1 => deep history 5/11 passed | possible issues

[ ] Test_openjdk17_hs_extended.system_ppc64_aix ⚠ UNSTABLE ⚠ : known issue https://github.com/adoptium/aqa-systemtest/issues/474

OAuthTest_0 => deep history 0/22 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues

reran OS: [x64Linux:[hotspot], x64AlpineLinux:[hotspot]] as the current run those test jobs hit the out of space issue.
https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk17-pipeline/281/console

PPC64le:
Test_openjdk17_hs_extended.system_ppc64le_linux ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/21 passed | possible issues : known issue

x86-32_windows:
Test_openjdk17_hs_extended.openjdk_x86-32_windows ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_0 ⚠ UNSTABLE ⚠
jvm_compiler_2 => deep history 0/5 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_1 ⚠ UNSTABLE ⚠
runtime_nestmate_2 => deep history 0/4 passed | possible issues
jdk_jfr_2 => deep history 0/5 passed | possible issues
jdk_vector_2 => deep history 0/4 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_2 ⚠ UNSTABLE ⚠
jdk_nio_2 => deep history 3/5 passed | possible issues
Test_openjdk17_hs_extended.system_x86-32_windows ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/22 passed | possible issues : known issue
MiniMix_aot_5m_0 => deep history 0/11 passed | possible issues
OAuthTest_0 => deep history 0/22 passed | possible issues : known issue

if OAuthTest has not passed on jdk17, I think we should exclude if for now for that version (and up).
@joeyleeeeeee97 - is it expected that OAuth test runs against jdk17+?

@smlambert Hi, OAuth should support jdk17+ by design.
I am trying to find out where this failure comes from, most likely some API or function behaves differently in 17+, I will create a PR to fix this as soon as possible

Thanks @joeyleeeeeee97 !  Because its a new test, we won't block the release on it, but having a fix will be great as we will want to include it for jdk17+ going forward.  :)

Release Summary Report for openjdk17-pipeline
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk17-pipeline/281/
Started by upstream project "build-scripts/weekly-openjdk17-pipeline" build number 54 at 1/18/2022, 9:50:27 AM

create_installer_linux ❌ undefined ❌

Test_openjdk17_hs_extended.openjdk_x86-64_alpine-linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-64_alpine-linux_testList_0 ❌ FAILURE ❌
jdk_tools_0 => deep history 0/1 passed | possible issues
Post Test => deep history 0/2 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-64_alpine-linux_testList_2 ❌ FAILURE ❌
Post Test => deep history 0/1 passed | possible issues
jdk_tools_1 => deep history 0/1 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-64_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_security_infra_1 => deep history 1/3 passed | possible issues
Test_openjdk17_hs_extended.openjdk_x86-64_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_security_infra_0 => deep history 1/2 passed | possible issues
Test_openjdk17_hs_extended.system_x86-64_alpine-linux ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/9 passed | possible issues
OAuthTest_0 => deep history 0/9 passed | possible issues
Test_openjdk17_hs_extended.system_x86-64_linux ⚠ UNSTABLE ⚠
OAuthTest_0 => deep history 0/6 passed | possible issues
OAuthTest_0 => deep history 0/6 passed | possible issues
Test_openjdk17_hs_sanity.functional_x86-64_alpine-linux ⚠ UNSTABLE ⚠
cmdLineTester_libpathTestRtfChild_0 => deep history 1/4 passed | possible issues
Test_openjdk17_hs_sanity.openjdk_x86-64_alpine-linux ⚠ UNSTABLE ⚠
jdk_lang_1 => deep history 0/4 passed | possible issues
jdk_lang_0 => deep history 0/4 passed | possible issues
Test_openjdk17_hs_sanity.system_x86-64_alpine-linux ⚠ UNSTABLE ⚠
TestJlmRemoteMemoryNoAuth_1 => deep history 4/5 passed | possible issues

Move to release.


⚠ Bofrost.at has degraded performance

In 6780b75, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1351 ms

Resolved: Bofrost.at performance has improved in d884d3c after 6 minutes.


Black (feat. Norah Jones) by Danger Mouse unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

stripper -> Danger-Mouse-Black

done


Wrong DML in training-with-artificial-data/05_data_4_cache_db.ipynb (CREATE TABLE customer_info)

Currently it is:
CREATE TABLE customer_info (
  customer_id INT,
  gender VARCHAR(1),
  age INT,
  mean_buy_price REAL,
  unique_products_bought INT,
  unique_products_bought_with_coupons: INT,
  total_items_bought: INT,
  mean_discount_received: REAL,
  total_coupons_used: INT
  PRIMARY KEY (customer_id)
);

Note the colon in some column definitions. It is an invalid syntax.
Fix it.

Additionally:
CREATE TABLE coupon_product (
    coupon_id INT,
    product_id INT,
    FOREIGN KEY (coupon_id) REFERENCES coupon_info(coupon_id),
    FOREIGN KEY (product_id) REFERENCES products(product_id)
);

There is no such table as products.


Add Ivan Gonzalez results

Add MD with the article exercice for part2

Hi Ivan,
I only needed the file for the markdown file.
I will accept the Pull request and remove the files related to the other assignments (from my repository only).
Best
Igor


Pass nextState to deepCompareChildren

While attempting to upgrade to 1.11.0 (we're several months behind currently) we sometimes get an exception after submitting a Form.
Uncaught TypeError: Cannot use 'in' operator to search for 'lastSubmitEvent' in undefined
    at n (index.js:5)
    at t.default (index.js:12)
    at o (deep-compare-children.js:59)
    at r.value (form-component.js:183)
    at f.updateComponent (ReactCompositeComponent.js:628)
    at f.performUpdateIfNecessary (ReactCompositeComponent.js:561)
    at Object.performUpdateIfNecessary (ReactReconciler.js:157)
    at s (ReactUpdates.js:150)
    at r.perform (Transaction.js:140)
    at i.perform (Transaction.js:140)
    at i.perform (ReactUpdates.js:89)
    at Object.C [as flushBatchedUpdates] (ReactUpdates.js:172)
    at r.closeAll (Transaction.js:206)
    at r.perform (Transaction.js:153)
    at Object.batchedUpdates (ReactDefaultBatchingStrategy.js:62)
    at Object.o [as batchedUpdates] (ReactUpdates.js:97)
    at dispatchEvent (ReactEventListener.js:147)
    at HTMLFormElement.r (raven.js:295)

It's very hard to reproduce (I have not been able write a standalone test case for it) but it is relatively simple to diagnose. It appears that if a Form's state changes without its props changing then shallowCompare tries to run shallowDiffers(instance.state, nextState) if nextState is not passed to deepCompareChildren then shallowDiffers nextState argument is undefined.
This PR passes nextState through to deepCompareChildren on both Field and Form components (the only two places it wasn't passed.)
It's not clear to me that this can actually happen on Field since it has no state but it seemed to best to never treat these arguments as optional.

Makes sense, thank you!

@davidkpiano Did you mean to close this instead of merging it?

Good catch 😅

@davidkpiano: I have the same problem with controls.


Feature Request: Allow config for multiple variables

Hello, I am wanting to create a PR for a small addition and wanted to make sure that it is something that is needed.
Currently the config/index.js only has a configurable ENV variable. This isn't ideal for running tests while having a dev server running b/c the ports collide.
Proposal: I would like to create a PR to update the cli to generate a config that merges the entire test/dev in config/index.js for the dev key. Also webpack will need to be updated to use the exports correctly.
Please let me know if this is wanted and i'll knock it out.
Thanks!

How would that look from a usage perspective?
I don't see the advantage from how you describe it. Currently, you can add more than one variable to the *.env.js files if you need to. Wouldn't that be enough?

Benefit would be that you could specify different options that are not in the dev.env property of teh index.js.  A good example of things that could change which are not currently updatable are the dev.port or autoOpenBrowser.
For the setup, i would think it would be similar to the current setup only instead of requireing the environment under dev.env we would require it and then merge it on top of the index.js.
So, index.js would then really be more of defaults, and dev/prod/test would be extensions on top of that where you could specify different ports/etc as needed for the different envs.

So this never went on, right? I'm in the last steps of merging #975 which will bring a few new config options for the things you mentioned.
Have a look and open a a new issue if you still think this config can be improved.


setup.py has several usability issues

In fumbling around with python's build commands, I ran into some issues with setup.py and dev_setup.py.
I'm on MacOSX 10.10.5 and everything should be the latest version.

setup.py assumes at least one argument

# I should give it a command, but I forgot:
ergmac:spaCy erg$ [master*] python --version
Python 2.7.10
ergmac:spaCy erg$ [master*] python setup.py
Traceback (most recent call last):
  File "setup.py", line 172, in <module>
    if sys.argv[1] == 'clean':
IndexError: list index out of range

1.a) Same issue for dev_setup.py
ergmac:spaCy erg$ [master*] python dev_setup.py
Traceback (most recent call last):
  File "dev_setup.py", line 116, in <module>
    if sys.argv[1] == 'clean':
IndexError: list index out of range

python setup.py install doesn't work. Is that because the command is supposed to be build_ext?

ergmac:spaCy erg$ [master*] python --version
Python 2.7.10
ergmac:spaCy erg$ [master*] python setup.py install
zip_safe flag not set; analyzing archive contents...
headers_workaround.__init__: module references __file__

Installed /Users/erg/spaCy/.eggs/headers_workaround-0.17-py2.7.egg
running install
...
creating build/temp.macosx-10.10-x86_64-2.7/spacy
clang -fno-strict-aliasing -fno-common -dynamic -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -I/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/include -I/usr/local/include -I/usr/local/opt/openssl/include -I/usr/local/opt/sqlite/include -I/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c spacy/parts_of_speech.cpp -o build/temp.macosx-10.10-x86_64-2.7/spacy/parts_of_speech.o -O3 -Wno-strict-prototypes
clang: error: no such file or directory: 'spacy/parts_of_speech.cpp'
clang: error: no input files
error: command 'clang' failed with exit status 1

My python3 can't find Cython. Not sure who is to "blame" for this one.

ergmac:spaCy erg$ [master*] python3 --version
Python 3.4.3
ergmac:spaCy erg$ [master*] cython --version
Cython version 0.23.1
ergmac:spaCy erg$ [master*] python3 setup.py build_ext
Traceback (most recent call last):
  File "setup.py", line 176, in <module>
    main(MOD_NAMES, use_cython)
  File "setup.py", line 147, in main
    cython_setup(modules, language, includes, compile_args, link_args)
  File "setup.py", line 71, in cython_setup
    import Cython.Distutils
ImportError: No module named 'Cython'

dev_setup.py needs murmurhash3 but doesn't install it?

ergmac:spaCy erg$ [master*] python dev_setup.py build_ext
running build_ext
skipping 'spacy/typedefs.cpp' Cython extension (up-to-date)
skipping 'spacy/strings.cpp' Cython extension (up-to-date)
building 'spacy.strings' extension
clang -fno-strict-aliasing -fno-common -dynamic -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -I/usr/local/lib/python2.7/site-packages/numpy/core/include -I/usr/local/include -I/usr/local/opt/openssl/include -I/usr/local/opt/sqlite/include -I/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c spacy/strings.cpp -o build/temp.macosx-10.10-x86_64-2.7/spacy/strings.o
spacy/strings.cpp:249:10: fatal error: 'murmurhash/MurmurHash3.h' file not found
#include "murmurhash/MurmurHash3.h"
         ^
1 error generated.
error: command 'clang' failed with exit status 1

The command that seems to work for me is:
ergmac:spaCy erg$ [master*] python --version
Python 2.7.10
ergmac:spaCy erg$ [master*] python setup.py build_ext
...
success.

I can't find a working command for dev_setup.py at all.
I'm open to helping fix these issues. Cheers!

How much experience do you have with Python packaging? All I can say is, if you haven't had to do this before, it's harder than you'd assume =/.
The thing is, the setup.py file needs to do many different things. It needs to build the project from source (the .pyx files), but it also needs to install the package from a distribution, i.e. be run by setuptools. That process can't depend on Cython. The distribution ships the .cpp files (which are not in the repository).
The two tasks are almost completely different. For a start, when run by setuptools, the install_requires and setup_requires arguments will be respected, and those dependencies will be downloaded. This isn't done if you just write "python setup.py".
The setup.py also includes lots of work-arounds for various bugs. For instance, install_requires doesn't actually work. If you specify the same package in install_requires and setup_requires, it won't actually be installed. I need the murmurhash and numpy header files during installation, so I made this thing, headers_workaround, that fixes pip installation. But, to just compile the project, you should run "pip install -r requirements.txt" (note that this list of requirements are specified separately --- there's no way to tell pip to just read the requirements from setup.py. Obviously.)
The priority for setup.py is that this:
pip install spacy

Should "just work", provided user has a C compiler installed. It took a lot of very frustrating work to get that to happen, but I'm pleased to say that installation works cleanly on the supported platforms, OSX and Linux. When building the project myself, I use fabric. For instance, this is how I publish a new version:
fab clean make sdist install test publish

This does the following:

Clean .so and .cpp files
Generate .cpp and .so files
Create a distribution tar file, e.g. in dist/spacy-0.90.tar.gz
Install spaCy from the tar file, into the current virtualenv
Run py.test tests/
If all that succeeded, push to master, and upload the new distribution to PyPi.

I just found the git install instructions on http://spacy.io/ and the workflow is completely different from what I've used before.
After trying it that way, there was an error with the C murmurhash3 headers, but I just found out that if I do pip install spacy first then murmurhash3 gets installed to the right place and the git build progresses.
Thank your for the detailed reply! I suppose it's user error on my side, except for possibly the murmurhash issue.

I saw error #2 listed above as well, but only when pip installing spacy with python3.5 (it worked without any issues when installing under python2.7).
clang: error: no such file or directory: 'spacy/parts_of_speech.cpp'
clang: error: no input files
error: command 'clang' failed with exit status 1

I ran pip install --upgrade wheel which successfully uninstalled wheel-0.24.0 and installed wheel-0.29.0. Afterwards, I re-ran pip install spacy and it installed without any problems.
Successfully installed spacy-0.101.0


implement methods needed to support streaming

This PR follows the same patterns used in #986 to delineate async functions by adding s to the beginning of methods that return a Generator instead of the full output. Currently tracing is not supported as the generator is passed directly through to the client.

@agola11 started work on streaming in #986  - we're hoping to merge this in and make an announcement tmrw. thoughts on the implementation there? it uses callbacks, so maybe a bit less direct but more compatible

Unfortunately, #986 doesn't work for my use case as it only streams to stdout. I spent some time trying to make it work by putting the tokens in a Queue, but it polluted global namespace and felt like the wrong abstraction. I'm going to close this PR and keep going with my hack for now!

@orban -> what's your use-case exactly? Implementing streaming with callbacks seemed like the least invasive approach while maintaining access to other callbacks, tracing etc. With on_llm_new_token you can pipe the tokens anywhere (websocket, etc) not just stdout. Happy to discuss more bc we want to make sure it's useful to people!


Update updates.md

Description

Added in changelog for https://konghq.aha.io/features/KP-332

Testing instructions
Preview link:
Checklist

[ x] Review label added

[ ] For unreleased versions: conditional version tags added, if applicable.
For example, if this change is for an upcoming 3.6 release, surround your change in {% if_version gte:3.6.x %} <content> {% endif_version %} tags (or if_plugin_version tags for plugins).

Closing in favor of https://github.com/Kong/docs.konghq.com/pull/6833


az webapp up says it's "creating" AppServicePlan even when the plan already exists

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az webapp up
Describe the bug
When using az webapp up to update a deployment and specifying the --runtime, --resource-group and --name, it re-uses the same AppServicePlan, but the output in the console says:
...
Creating AppServicePlan '[plan_name]' ...
...

This gives the mistaken impression that it is in fact creating a new plan
To Reproduce

run az webapp up --runtime 'PYTHON:3.9' -g my-group-1 --name my-app-1
notice it will tell you it is creating an AppServicePlan
run az webapp up --runtime 'PYTHON:3.9' -g my-group-1 --name my-app-1
notice it will tell you it is creating an AppServicePlan with the same name as above

Expected behavior
Rather than writing "Creating AppServicePlan" to the console
If there are changes to the AppServicePlan then it should say "Updating AppServicePlan"
If there are no changes to the AppServicePlan it should not mention the AppServicePlan at all
Environment summary
Install Method: winget
Shell: PowerShell on Windows 11
Version:
azure-cli 2.37.0
core 2.37.0
telemetry 1.0.6
Extensions:
azure-dev 0.0.1b456
containerapp 0.1.3
rdbms-connect 1.0.2
Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\charris.azure\cliextensions'
Python (Windows) 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 22:57:10) [MSC v.1929 32 bit (Intel)]
Additional context

route to CXP team

Adding Service Team to look into this ask.
@AzureAppServiceCLI @antcp Could you please look into this ask and provide an update ?

thanks for reporting. We will investigate & fix.

It seems that a side effect is that if you have a Policy that puts restrictions on the App Service Plan - for example requiring certain Tags to be present - webapp up will fail with a policy violation.
In other words, it looks like the CLI goes through all the pre-flight checks for actually creating the app service plan - even though it already exists.

closing, linked PR resolves this


Game wont start

latest.log

does it crash without optifine?

yeah it does

I think this is a duplicate issue with issue #2, so I'll close it for now

alrighty


Add a title for the 5 best notes of skills

As a user I want to see a title for the classment of my 5 best skills in order to know what this section means

@MailyLehoux I tried to improvise a little on this, I'd like to check the visual for approbation before creating the PR.

I think you can also add an icon like 🏆 But yes I like this :+1:

Yes ok. We use svg for the specials icons but react icons for the "basics" icons. I love the star icon as wll :+1: I didn't know about the svg as font it seems very interesting for Skillz it's true that I often struggle with svg


Different output than scikit-learn's LASSO on a weird example

Hi !
I am not sure this is the best place to report this, but I noticed a difference in the ouptut produced by your solver and scikit-learn's. I had a really hard time coming up with some minimal example, sorry if the one below is not really informative. I am using Python 3.7.4 and celer development version on Ubuntu.
import numpy as np
import sklearn.linear_model
import celer

X = np.array([[0, 0, 0, 0, 0, 0, 0, 0.001, 0, 0, 0.015, 0, 0, 0.046, 0, 0, 0.061, 0, 0, 0.062]]).T
y = np.array([0.008, 0, 0.001, 0.02, 0, 0.001, 0.024, 0.001, 0.001, 0.023,
              0.006, 0, 0.011, 0.032, 0, 0.002, 0.056, 0.001, 0.001, 0.062])

lasso_sklearn = sklearn.linear_model.Lasso(alpha=1e-4)
lasso_celer = celer.Lasso(alpha=1e-4)

lasso_sklearn.fit(X, y)
lasso_celer.fit(X, y)

So the coefficient I get from scikit-learn's solver is approximately 0.55 (dual gap is 0) and the one I get from your solver is 0 (dual gap is approximately 1e-4).
I know this is a really degenerate use case, so maybe there is no need to worry about it, but I wanted to report this just in case, and ask if there was any reason celer should not be used in such situation.
Thanks in advance for your help !

Hi Romain,
It's the correct place ! I'm very happy to get your feedback.
I think both solvers are right: they return a coef_ which is less than some tolerance (which is rescaled version of clf.tol) away from the optimal one in terms of objective. sklearn does 1 iteration and celer does not (it evaluates the gap before doing any update)
With
true_sol = sklearn.linear_model.Lasso(alpha=1e-4, tol=1e-14).fit(X, y)
In [44]: p_celer = norm(y - X @ celer_sol.coef_ - celer_sol.intercept_) ** 2 / (2 * len(y)) + celer_sol.a
    ...: lpha * norm(celer_sol.coef_, ord=1)

In [45]: p_celer
Out[45]: 0.000165375

In [46]: p_star = norm(y - X @ true_sol.coef_ - true_sol.intercept_) ** 2 / (2 * len(y)) + true_sol.alpha
    ...:  * norm(true_sol.coef_, ord=1)

In [47]: p_star
Out[47]: 0.00010331658481530062

In [48]: p_sklearn = norm(y - X @ sklearn_sol.coef_ - sklearn_sol.intercept_) ** 2 / (2 * len(y)) + sklea
    ...: rn_sol.alpha * norm(sklearn_sol.coef_, ord=1)

In [49]: p_sklearn
Out[49]: 0.00010331658481530062

In [50]: p_celer - p_star
Out[50]: 6.205841518469937e-05

In [51]: p_sklearn - p_star
Out[51]: 0.0

Notice that your objective at 0 is quite low (and the default tolerance is 1e-4):
In [16]: from numpy.linalg import norm

In [17]: norm(y) ** 2 / len(y)  # primal at w = 0
Out[17]: 0.0004869999999999999

If you decrease tol you get the same results:
In [18]: lasso_celer = celer.Lasso(alpha=1e-4, tol=1e-10).fit(X, y)

In [19]: lasso_sklearn = sklearn.linear_model.Lasso(alpha=1e-4, tol=1e-10).fit(X, y)

In [20]: lasso_celer.coef_, lasso_celer.intercept_
Out[20]: (array([0.55034622]), 0.007409297501753958)

In [21]: lasso_sklearn.coef_, lasso_sklearn.intercept_
Out[21]: (array([0.55034622]), 0.0074092975017539565)

Also be aware that both celer and sklearn fit an intercept by default.

Thank you very much for your quick reply ! I'll try to carefully set the tolerance from now on then.

Also be aware that both celer and sklearn fit an intercept by default.

Thanks for pointing this out !

The tolerance should be scaled with respect to norm(y) ** 2 or norm(y) ** / n_samples (as is done in sklearn) to make it easier to set. This has been on my todolist for a while: #125
Keep me posted if there's any feature you're missing. this solver should be must faster than sklearn if your data is high dimensional

The tolerance should be scaled with respect to norm(y) ** 2 or norm(y) ** / n_samples (as is done in sklearn) to make it easier to set. This has been on my todolist for a while: #125

Good to know !

Keep me posted if there's any feature you're missing. this solver should be must faster than sklearn if your data is high dimensional

I actually want to solve problems with a large number of samples in small dimension. I however have to use a weighted l1 norm in the objective, so that's why I am interested in celer, it turns out there are not many packages allowing to do that easily !
Thanks again for your help !


cls

Uninstall not working.  Any ideas?
PS C:\Users\me\adogit\Service-Gold\team-development\srb> Get-Module az -ListAvailable
Directory: C:\Users\me\myplace\Documents\PowerShell\Modules

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands

Script     4.3.0                 Az                                  Core,Desk
PS C:\Users\me\adogit\Service-Gold\team-development\srb> Uninstall-Module Az
PS C:\Users\me\adogit\Service-Gold\team-development\srb> Get-Module az -ListAvailable
Directory: C:\Users\me\myplace\Documents\PowerShell\Modules

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands

Script     4.3.0                 Az                                  Core,Desk

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 19c3b0d7-748f-8dbd-bd90-4011e2df220e
Version Independent ID: b3ce94fa-6e76-4ffe-e70e-07f7a321fcd4
Content: Uninstall Azure PowerShell
Content Source: docs-conceptual/azps-5.4.0/uninstall-az-ps.md
Service: azure-powershell
GitHub Login: @mikefrobbins
Microsoft Alias: mirobb

@JoeBrunsTR -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@JoeBrunsTR -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@JoeBrunsTR - Have you tried following the instructions on the page you have referenced. "Which method you follow depends on how you installed the Az module. If you're not sure of your original installation method, follow the MSI steps for uninstalling first."
https://docs.microsoft.com/en-us/powershell/azure/uninstall-az-ps?view=azps-5.4.0&source=docs#uninstall-the-azurerm-module

@JoeBrunsTR - Have you tried following the instructions on the page you have referenced. "Which method you follow depends on how you installed the Az module. If you're not sure of your original installation method, follow the MSI steps for uninstalling first."
https://docs.microsoft.com/en-us/powershell/azure/uninstall-az-ps?view=azps-5.4.0&source=docs#uninstall-the-azurerm-module

@JoeBrunsTR - Have you tried the above suggested reference ?

@JoeBrunsTR - Have you tried the above suggested reference ?

@JoeBrunsTR -
Since we have not heard back from you we will now proceed to close this thread.
If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.

@JoeBrunsTR -
Since we have not heard back from you we will now proceed to close this thread.
If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


helixstreet grant application / Level 2

Project Abstract
helixstreet is a project to extend the use of Blockchain technology to genomics. helixstreet chose substrate as technology to implement a pallet to store a Merkle tree hash of genomic raw sequencing data. Relationsships ( ancestry ) can be documented in the blockchain based on relationships between genomic data. Currently we are planning to implement helixstreet as parathread.
Ancestry data and personal genomic relationships are today centralized. helixstreet's approach allows the representation of ancestry data in a decentralized manner.
For which grant level are you applying?

[x] Level 2:  Up to $50,000, 3 approvals

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Now signed Contributor License Agreement

Now signed Contributor License Agreement

Thx David for the feedback. The mandatory deliverables are added. The rust program is removed as milestone for the grant application - it would be difficult to test the rust program in a docker image due to the space limitations of docker images.
The storage of the data itself is in the early phase in the hands of the owner of the private key.  Ipfs is for sure in a later stage a good possibility ( either encrypted or public ).

Thanks indeed for the clarification. I added Milestone 2.

Thx for the feedback. I added some details regarding the program and the project. I am quite aware and agree that there are better teams who could realize the blockchain part far quicker. This Level 1 grant proposal is an early stage application specific parathread which extends the use of Polkadot/Kusama ecosystem to a whole new use case and user base.

Hi @helixstreet
Thanks for your application and your interest in the web3 foundation grants program!
Regarding deliverable 1. Substrate module: genomics I'm with @Noc2, I think it's fairly straightforward to implement as you already seem to partly have done here.
Regarding deliverable 2. Program to generate Hashtree, I have a few questions:

(..) store a vector ( or the main root ) of the root hashes automatically in the Blockchain assigned to the private key

So you want to use the merkle hash as entropy for a user's private key, is that correct?

A flag is needed to distinguish between entries made by a machine ( e.g. Sequel II ) or by the identified owner of the DNA raw data

I'm definitively not an expert in that area, but I suppose any DNA sequencing would happen by a machine, right? Also, how would you safely identify the owner of the DNA using a script? In general, I have the impression that the script will just create a hash tree from the DNA raw data and store it on the blockchain, is that fair to say?
Furthermore I'm not sure how your pallet could be used, so it might be helpful if you could come up with some concrete use cases.
To wrap up, I think for the scope of your project (according to my current understanding) the price is too high which is why I'm currently not ready to support it.
Pls let me know if I got something wrong because again, I'm far from an expert in the field and I might be missing something.

Hi

Hi @helixstreet
Thanks for your application and your interest in the web3 foundation grants program!
Regarding deliverable 1. Substrate module: genomics I'm with @Noc2, I think it's fairly straightforward to implement as you already seem to partly have done here.
Well i thing that's just a template and would be far from production ready. I would like to have a pallet which would be production ready in a parathread with correct weights and could accept calls to prove authenticity of Sequencing data.

Regarding deliverable 2. Program to generate Hashtree, I have a few questions:

(..) store a vector ( or the main root ) of the root hashes automatically in the Blockchain assigned to the private key

So you want to use the merkle hash as entropy for a user's private key, is that correct?

A flag is needed to distinguish between entries made by a machine ( e.g. Sequel II ) or by the identified owner of the DNA raw data

I'm definitively not an expert in that area, but I suppose any DNA sequencing would happen by a machine, right? Also, how would you safely identify the owner of the DNA using a script? In general, I have the impression that the script will just create a hash tree from the DNA raw data and store it on the blockchain, is that fair to say?
In the case the blockchain entry is made directly by a machine ( which would be ideal, because, that ensures nobody has changed the data )  the private key would be a "technical" private key. In this case there is the need for a governance to assign the data to a human being who owns the data. It's absolutely clear there is more functionality needed. For the future it is incredible important to know no one has modified anything. The next evolving tech is reverse sequencing -(e.g. TWIST ) creating DNA from the data and recreating life.
Furthermore I'm not sure how your pallet could be used, so it might be helpful if you could come up with some concrete use cases.
The pallet in this basic functionality just ensures to have an immutable record of a sequencing run. Sequencing in HiFi is still expensive - but gets cheaper from year to year ( Moore's Law in genomics )
To wrap up, I think for the scope of your project (according to my current understanding) the price is too high which is why I'm currently not ready to support it. Pls let me know if I got something wrong because again, I'm far from an expert in the field and I might be missing something.

Well - i calculate 30% taxes; Some additional effort at the end to get the grants and still would think it's a very very small subsidy for the project. But i am not doing it for the money - more to get through the process in case i start Level 2 - which would be the interesting because of the badge.

Thx indeed for the hint. I did this ( L2 / 1k ). The tokenomics is removed ( from the menu - the link will work but it's not referenced in the menu )

@helixstreet Thanks for answering the questions.

Once variant calling is done this could be done by identifying a few variant (e.g. eye color is the easiest encoded )

I'm assuming that said eye color will come in the form of a very specific color code, is that correct?
According to my (very limited) understanding of variant calling, this process is very prone to errors, the same goes for the sequencing done by the machine in the previous step. If that's the case, can we still assume that identification of these variants will be accurate? To stay at your example of eye color, let's say the sequencing and/or the variant calling made some errors and identifies the color as colorcode_ABC however, in reality, the color is colorcode_XYZ. In that case, the person will be rejected, right? In general, my question is, how reliable are these processes for identifying a person?
Pls correct me if any of my assumptions are wrong or if I'm missing something.
In general, it's still a bit fuzzy to me how the pallet will be used and what it will do which is why I'm with David here w.r.t. the article. It would be nice to have some more context to understand e.g. who's the target audience for this pallet and how it can be used.
That being said, given the updated price I'm also fine to give it a shot. 👍

@helixstreet Thanks for answering the questions.

Once variant calling is done this could be done by identifying a few variant (e.g. eye color is the easiest encoded )

I'm assuming that said eye color will come in the form of a very specific color code, is that correct?

No. It's not so easy. Several variants play a role.
For example:
https://www.ncbi.nlm.nih.gov/gene/4948
According to my (very limited) understanding of variant calling, this process is very prone to errors, the same goes for the sequencing done by the machine in the previous step. If that's the case, can we still assume that identification of these variants will be accurate? To stay at your example of eye color, let's say the sequencing and/or the variant calling made some errors and identifies the color as colorcode_ABC however, in reality, the color is colorcode_XYZ. In that case, the person will be rejected, right? In general, my question is, how reliable are these processes for identifying a person? Pls correct me if any of my assumptions are wrong or if I'm missing something.
Variant calling is not prone to errors.
Sequencing is - but the errors are not systematic; so multiple reads correct errors

In general, it's still a bit fuzzy to me how the pallet will be used and what it will do which is why I'm with David here w.r.t. the article. It would be nice to have some more context to understand e.g. who's the target audience for this pallet and how it can be used.
That being said, given the updated price I'm also fine to give it a shot. 👍

Thx indeed.

@helixstreet personally I think the distinction between level 1 and level 2 grants is there for a reason, and the badge is only awarded to projects that already have a slight understanding of what they're trying to build because we can't possibly endorse individuals without a team who are at the absolute earliest stage of their crypto journey. We can at most provide some funding, which is what a level 1 grant accomplishes.
So I personally won't approve it and my recommendation is that you change it back to a level 1 grant, in which case it's already approved. Or you can wait in case someone else wants to provide the third approval.

@helixstreet personally I think the distinction between level 1 and level 2 grants is there for a reason, and the badge is only awarded to projects that already have a slight understanding of what they're trying to build because we can't possibly endorse individuals without a team who are at the absolute earliest stage of their crypto journey. We can at most provide some funding, which is what a level 1 grant accomplishes.
So I personally won't approve it and my recommendation is that you change it back to a level 1 grant, in which case it's already approved. Or you can wait in case someone else wants to provide the third approval.

Thx for your feedback - nevertheless i think i have "a slight understanding of what i am trying to build".

Right. Replace that with "a solid understanding" then, my bad.

Right. Replace that with "a solid understanding" then, my bad.

I even think i have quite "a solid understanding" of what i am planning to build.

I am slightly shocked by the arrogance and rudeness here.

@helixstreet I apologise if that's how it came accross.
As evidenced by the fact that you've improved the application several times and pivoted in response to feedback, and given your lack of experience with blockchain technologies, I think it's fair to say you're still trying to figure out exactly how you will accomplish your vision. That's perfectly fine and we're happy to support you along the journey, and I don't think there's anything wrong with me saying it.
If you don't mind, I would be happy to jump on a call to talk about what you want to achieve to give this a positive spin. I've sent you an email so we can find a time.

"give my lack of experience with blockchain technoligies"
Really - is this rudeness the style of W3F or your personal?

@helixstreet I'm sorry, I was just fixing that. You didn't list any experience in your application.

This is an interesting application for blockchain tech that I'd never considered before. I'm curious to see where it goes and will approve.

This is an interesting application for blockchain tech that I'd never considered before. I'm curious to see where it goes and will approve.

Thx indeed. Highly appreciated - also the positive and encouraging attitude.

Hi @helixstreet are you able to provide an update on how your progress is coming along?

Hi, Slow ( very ) but steady. Just doing a deep dive of Polkadot in Buenos Aires - so some more progress coming soon. If i understood correctly there is no deadline.

Thanks for the update @helixstreet, there is no hard deadline per se, however, seeing as this grant has been open for almost a year, we want to make sure that it is still actively being worked on. I noticed that there has been no activity on the repo in quite some time. If you think it will be significantly delayed further we would ask you to submit an amendment to update the timeline. Thank you!

Hi @helixstreet seeing as no work has been done on the project since last August, I think it's probably a good idea to go ahead and terminate the grant, and then you can re-open it when you are ready to work on it. Let me know your thoughts - if we don't hear back from you after 2 weeks, we will go ahead and terminate due to inactivity.


Added DP Basics With CPP and Updated ReadMe

There are some conflicts arising, please compare it with the latest repository.


revert old stereo_cube_map plugin back for backwards compatibility

it's off the menus but old graphs with otoy urls load ok now

lgtm


Add tooltips to database connector templates

Adrian to show Rachel example of how to do this.

moving to done


Leak detection: Avoid unbounded growth of address map

What does this PR do?
Minor update to clear the map at 200000 elements
Notes
To be improved: The sync is not guaranteed between lib and worker.

Closing as we made a better version of this.


⚠ Panel - Hydeos has degraded performance

In 1a05f51, Panel - Hydeos (https://pterodactyl.hydeos.fr) experienced degraded performance:

HTTP code: 200
Response time: 805 ms

Resolved: Panel - Hydeos performance has improved in 44fe76a after 15 minutes.


Ex command ':k(ill)' doesn't work

What did you expect to happen?
After seeing the table at https://github.com/hlissner/doom-emacs/tree/master/modules/editor/evil#custom-ex-commands, execute :k ex command with an open buffer and get that buffer killed.
What actually happened?
When I run :k or :kill the minibuffer shows "Unknown command: 'kill'" and the buffer is not killed
Describe your attempts to resolve the issue
From https://github.com/hlissner/doom-emacs/blob/6bf725837def83acd140d9431d799c8b09abebf3/modules/editor/evil/%2Bcommands.el#L45 it seems that :k(ill) should call 'doom/kill-current-buffer, but that function doesn't exist. Perhaps it should have been kill-current-buffer like normal-mode zx ?
Steps to reproduce

Open DoomEmacs
Open any buffer
In normal mode, type :k or :kill
See the message "Unknown command: 'kill'"

System Information
https://pastebin.com/DKG708ha

The docs are a bit outdated. I'm working on that in the rewrite-docs branch and will fix there shortly. In the meantime, you'll find doom/kill-current-buffer on SPC b k and zx (in normal mode).

So, like I mentioned, doom/kill-current-buffer doesn't exist. Both zx and SPC b k calls kill-current-buffer (without the doom/ prefix). It's probably just a matter of removing the doom/ prefix from the command definition.
Either way I'm glad I found out about zx ;-)

Changing the command definition works. Here's a patch against current master.
doom-kill-ex.txt


mudswitch with converter

Bug type
Component
Component name
MudSwitch
What happened?
The entire webpage frozen,  it seems that converter generated infinity look between binding property and itself.
Expected behavior
To turn on and off switch
Reproduction link
https://try.mudblazor.com/snippet/cEwHPvPJBjWGcmSL
Reproduction steps
Just run the sample code from the link above and the page will frozen immediately.
Relevant log output
No response
Version (bug)
6.10
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Set converter like this:
Converter="@_converter"
...
private BaseTextToBoolConverter _converter = new BaseTextToBoolConverter();

https://try.mudblazor.com/snippet/mYwdlbPzCzQsZSPA
Otherwise you are creating converter on each render

It works, thanks for help.


Incorrect shebang in documentation

[ ] I have read through the manual page (man fzf)
[ ] I have the latest version of fzf
[X] I have searched through the existing issues

The example script found in the wiki under "fzf as dmenu replacement' uses the shebang #!/usr/bin/env sh. However, it also uses disown, which is undefined in POSIX sh. A #!/usr/bin/env bash would be more portable/compatible. (I noticed because I replaced the default /bin/sh symlink to bash with one pointing to the stricter dash shell.)

Thanks for the heads up. The page is maintained by the community and I don't review or test the code people add to it. Write permission to the page is open to everyone, so feel free to edit the code if you think it's incorrect.


downloads.gauge.org is down

Calling gauge install java fails  to download java plugin. It seems like downloads.gauge.org is down.
Expected behavior
Calling command should download and install java plugin
Actual behavior
The following is printed:
Gathering metadata for java
Failed to download java-install.json file: Get https://downloads.gauge.org/plugin/java?l=&p=&o=linux&a=amd64: dial tcp <IP_ADDRESS>:443: getsockopt: connection refused
Failed to install plugin 'java'.
Reason: Invalid plugin. Could not download java-install.json file.

Steps to reproduce
Call the following from the command line:
gauge install java --log-level debug
Gauge version
Gauge version: 1.0.0
Commit Hash: 5a99965

Plugins
-------
No plugins found
Plugins can be installed with `gauge install {plugin-name}`

http://www.isitdownrightnow.com/downloads.gauge.org.html says Downloads.gauge.org is DOWN

https://downloads.gauge.org/plugin actually 404's
# gauge config --list

Key                           	Value
--------------------------------------------------------------------
gauge_repository_url          	https://downloads.gauge.org/plugin
runner_connection_timeout     	30000
runner_request_timeout        	30000
check_updates                 	true
gauge_telemetry_enabled       	true
gauge_update_url              	https://downloads.gauge.org/gauge
gauge_templates_url           	https://downloads.gauge.org/templates
plugin_connection_timeout     	10000
plugin_kill_timeout           	4000
ide_request_timeout           	30000
gauge_telemetry_log_enabled   	false

Thanks for informing. downloads.gauge.org is up again.
Feel free to reopen the issue, if you face it again.


docs(issue-credential): add ext. deps. requirement

Signed-off-by: Karim Stekelenburg<EMAIL_ADDRESS>

@TimoGlastra, feel free to merge if you approve!


Do not buffer rexi messages to disconnected nodes

When messages cannot be sent because the node is disconnected do not buffer
it rexi's buffer for that node. If it is a doit message immediately tell
caller that the node is down so they can make progress and not have to wait
for timeouts.
Also stop all the buffers and rexi servers for disconnected nodes. Previously
buffers and servers were started on nodeup but never stopped.

Close is in favor of a better approach as suggested by @davisp https://github.com/apache/couchdb/pull/838


Remove duplicated and unreachable code.

As a seasonal bonus this should increase test coverage (calcNormalizedDist was previously not covered by tests).
🎁
Edit: turns out it was covered by tests that I had just not noticed yet.

Thanks again :) !
I would like to reserve 'getXY' for "nearly zero effort" operations ... would you mind to rename getShrinkFactor into calcShrinkFactor :) ?

Sure, no problem.


More guidance re: how to create student notebooks

Hi @choldgraf , following your example notebook create_student_notebooks.ipynb I tried to create a student version of a notebook with an answer key on datahub.berkeley.edu but was unsuccessful. It cleared the output but didn't remove the code between ### SOLUTION BEGIN and ### SOLUTION END.  I think my problem stems from this line import connectortools as ct. Neither nbgrader nor connectortools are installed on datahub.berkeley.edu. So my hack-around was to (1) !pip install nbgrader (not sure if that was wise) and (2) cut and paste the content of grading.py into a cell & run it. That created some errors that I attempted to fix. I got the code to run but the output wasn't as I expected. Any tips on how to run your connectortools in jupyter hub appreciated.
thanks, Patty

Hey @pattyf - I think a solution will be for me to create some interact links and make sure the demos work there as well. I'll put some time into this soon

hey all - the connectortools module is now updated and it should work if you click on the interact link that's provided on the connectortools README page. One caveat is that you'll need to install nbgrader in order to get this to work. You should be able to do this with pip install, and I've added a quick helper cell in the index.ipynb notebook to do this on a machine. In the future I think we may add it to the cluster automatically (see #46 )


Add option to test statistics to ignore blank jobs.

I would like to add an option to the test statistic charts to only return results for jobs which contain values.  This would result in a report similar to the Cobertura reports for the dashboard views.

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

Hi...  I made a similar pull request to this one, only I updated the unit tests to use the new constructor, and didn't make a second, fallow, constructor that was used only for the test framework.  Not sure what the admins will want, but probably don't want the extra constructor.
https://github.com/jenkinsci/dashboard-view-plugin/pull/42

Merged version which updated unit tests


update ssdt 2019 doc

Learn Build status updates of commit d0b1360:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/ssdt/release-notes-ssdt-2019.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@WanxuanYe
Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks!
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@microsoft-github-policy-service agree [company="microsoft"]


[SPARK-42653][CONNECT][FOLLOW-UP] Fix Scala 2.13 build failure by explicit Seq conversion

What changes were proposed in this pull request?
This PR proposes to add toSeq to work around Scala 2.13 build at getCrcValues.
Why are the changes needed?
The build in the master branch fails in Scala 2.13 build:
[error] /home/runner/work/spark/spark/connector/connect/client/jvm/src/test/scala/org/apache/spark/sql/connect/client/ArtifactSuite.scala:87:11: type mismatch;
[error]  found   : scala.collection.mutable.Buffer[Long]
[error]  required: Seq[Long]
[error]       .map(_.toLong)
[error]           ^

https://github.com/apache/spark/actions/runs/4323142317/jobs/7546408812
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
CI in this PR should test it out.

cc @hvanhovell

Thanks! Let me merge after https://github.com/HyukjinKwon/spark/actions/runs/4323411173/jobs/7547000388. Should take less then 20 mins.

Merged to master and branch-3.4.