feat(routing): add regex chunking to route regex

What
Add regex chunking to route regex. When loading in massive amounts of routes a singular regex can become to large for PCRE to process. A solution for this is to split it up in multiple separate regexes, this is called chunking. With this PR is should be possible to load in as many routes as you like, as long as your memory can hold it.
In order to facilitate this I needed to rework how we build up the regex, instead of using recursion and having the stack implicitly as a php call stack. I needed to implement it manually such that, when it is detected we require a new chunk, we could rebuild the regex prefix based on the stack and also finish it based on it.
Outstanding debates
RouteMatchingRegexesBuilder performance considerations
I isolated the regex buildin into src/Tempest/Http/src/Routing/Construction/RouteMatchingRegexesBuilder.php and one singular function. This is mostly because of performance reasons.  The inner part of the loop is called so many times, every function call needed to count. So there is a trade-off  between readability and performance. Currently I opted to go slightly more towards the performance side. If you think it should be implemented into multiple methods, do know it comes at a cost. (If needed, we can use the benchmarks to signify the cost of alterations).
This is also the reason for using null as a end marker instead of wrapping all nodes into a VO which also would translate to an end-marker. I saw a performance drop of arround 60%, I went from 120μs to 190μs
PHPunit memory limit
I bumped the phpunit memory limit. I couldn't find a "leak" in the newly added code. And it mainly breaks on the integration part. My expectation is the integration tests are already quite hefty on memory and my changes tipped it over the limit. I used memprof to find any culprits, but I couldn't find any glaring issues, most memory consumption is not in "my" code or even near it.

Great PR 👍

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

71 of 73 (97.26%)  changed or added relevant lines in 5 files are covered.
19 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 82.551%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Tempest/Http/src/Routing/Matching/MatchingRegex.php
11
13
84.62%

Files with Coverage Reduction
New Missed Lines
%

src/Tempest/Console/src/ConsoleApplication.php
7
10.0%

src/Tempest/Http/src/HttpApplication.php
12
0.0%

Totals

Change from base Build<PHONE_NUMBER>8:
0.1%

Covered Lines:
7333

Relevant Lines:
8883

💛  - Coveralls

Do you wanna take a look at the merge conflict? Other than that I'm fine merging this 👍
It's not a blocker for me, but I do like for null to have meaning. So to me it makes more sense that RouteMatch can be nullable instead being notFound.
Look at it from a language perspective: "I have a route match" — that always means that there is a matching route. When you say "I don't have a route match", it means there is no matching route (ie. null).

Do you wanna take a look at the merge conflict? Other than that I'm fine merging this 👍

Done

It's not a blocker for me, but I do like for null to have meaning. So to me it makes more sense that RouteMatch can be nullable instead being notFound.
Look at it from a language perspective: "I have a route match" — that always means that there is a matching route. When you say "I don't have a route match", it means there is no matching route (ie. null).

It is a matter of opinion I changed it to null. I do not like null because you end up with allot of null checks everywhere. While not all nulls are equal. So in our case the Route match was not found. Which is something different than an error (maybe a case for later) or a route that is missing (as in, not completely loaded in). By returning null you will be missing these cases. But as state, it is a matter of opinion, and I do not see any harm in going your way on this. More so because it is a bit more in the "tempest" style.

Thanks! Great PR 💪


add description of ResourceTracker to Readme.md

https://github.com/shimat/opencvsharp/issues/1107

Thank you 👍


[tcgc] support serialized name for body parameter to avoid example mis-mapping

fix: https://github.com/Azure/typespec-azure/issues/1739

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/typespec-azure-resource-manager

The following packages have already been documented:

:white_check_mark: @azure-tools/typespec-client-generator-core

Show changes
@azure-tools/typespec-client-generator-core - fix ✏

support serialized name for body parameter to avoid example mis-mapping

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs

/azp run typespec-azure - Verify PR


Support accessing PII from database via sqlalchemy

Consider hashing from a database instead of from a csv.
Would need to extend the configuration to include information about which columns to select.

I think this will be well covered by having a nice Python api. See #26


Change from DeploymentConfig to Deployment

The latest versions of OpenShift Origin support all of the features of DeploymentConfig in the v1beta1 API.
In working with Istio, I have found that it uses Deployment objects instead of DeploymentConfig. In order to make sidecar injection work in a simple, 2-step process I would like to do the following.
istioctl kube-inject -f .nodeshift/deployment.yml > .nodeshift/deployment.yml
nodeshift --strictSSL=false --nodeVersion=10.x --expose

This should inject all of the Istio sidecar capabilities into whatever deployment config we have for a given project. The istioctl process will merge its stuff with ours. It changes the apiVersion attribute, however, it doesn't change the kind attribute from DeploymentConfig to Deployment and when I run nodeshift with the resulting yaml file, I get this error.
2018-05-22T21:09:25.760Z ERROR {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"DeploymentConfig in version \"v1beta1\" cannot be handled as a DeploymentConfig: no kind \"DeploymentConfig\" is registered for version \"extensions/v1beta1\"","reason":"BadRequest","code":400}
2018-05-22T21:09:25.761Z ERROR Status code 400

I think it might be as simple as changing this but I'm not entirely sure.
This might be a semver major change? I don't know when OpenShift started supporting Deployment and when that schema included all of the attributes of a DeploymentConfig. But some older OpenShift versions might break with this change.

I think this is the part that converts it to a DeploymentConfig, https://github.com/bucharest-gold/nodeshift/blob/master/lib/resource-enrichers/deployment-config-enricher.js#L62
Since we were just doing Openshift stuff, it made sense at the time.  But now, we should probably change it.  I think we would need to figure out if this is just an Openshift deploy or an Istio deploy and then update if needed
I think we might need to also update the Openshift-rest-client. I don't think it knows about the Deployment API's
This will definitely be a semver major change.

Looks like this API is still there in 3.7, https://docs.openshift.com/container-platform/3.7/rest_api/apis-apps/v1beta1.Deployment.html

Closing for lack of movement. May revisit someday.


Event-driven application controlling.

The applications need to be controlled during the run-time, i.e. kill or restart.
Current prototype applications have time-out and a dedicated flag that they are watching.
For more flexible controlling of those apps, maybe we can use event routers.
For example, kafka brokers or message bubbling and on method in textual.
We could somehow use textual or flask or... similar third party packages, or implement them ourselves...?

Idea note from #144
Now Daemon is sending messages to a router directly.
But, maybe it just have a async-generator that yields Messages as it runs.
And Application can use the generator and send the message that it yields instead.

It is already implemented as a message router.


Is the document wrong for IGListSectionController?

In IGListSectionController.h, the comment for
@property (nonatomic, weak, nullable) id <IGListScrollDelegate> scrollDelegate;

is
/**
 An object that handles display events for the section controller. Can be `nil`.

 @return An object that conforms to `IGListDisplayDelegate` or `nil`.

 @note You may wish to return `self` if your section controller implements this protocol.
 */

which is exactly the same as
@property (nonatomic, weak, nullable) id <IGListDisplayDelegate> displayDelegate;

Or is there some difference?
Thanks~

@PhilCai1993 I'm loving your deep dives. Yes! This is wrong. It should be updated and describe the scrolling delegate instead.

😄 We have added IGListKit into our Podfile.
And I have to share it to my partners, so I take a a deep look at it.

Closed by 6e00787


force: package: beta: version: create doesn't use unpackagedMetadata for testing.

Summary
Short summary of what is going on or to provide context.
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc
(Steps 1 through 3 are included in the main branch of the above repository)

Add a new unpackaged folder to the file system, and the sfdx-project.json. Add the unpackagedMetadata attribute to the DreamhouseLWC package definition.

"packageDirectories": [
        {
            "path": "force-app",
            "default": true,
            "package": "DreamhouseLWC",
            "versionName": "Summer '22",
            "versionNumber": "55.0.0.NEXT",
            "unpackagedMetadata": {
                "path": ".\\unpackaged"
            }
        },
        {
            "path": ".\\unpackaged",
            "default": false
        }
    ],

Alter the standardValueSet for contracts by creating the file unpackaged\standardValueSets\ContractStatus.standardValueSet-meta.xml with the following content;

<?xml version="1.0" encoding="UTF-8"?>
<StandardValueSet xmlns="http://soap.sforce.com/2006/04/metadata">
    <groupingStringEnum>ContractStatusCode</groupingStringEnum>
    <sorted>false</sorted>
    <standardValue>
        <fullName>Pending_Approval</fullName>
        <default>false</default>
        Pending Approval
        <groupingString>InApproval</groupingString>
    </standardValue>
    <standardValue>
        <fullName>Contracted</fullName>
        <default>false</default>
        Contracted
        <groupingString>Activated</groupingString>
    </standardValue>
    <standardValue>
        <fullName>Working_Draft</fullName>
        <default>false</default>
        Working Draft
        <groupingString>Draft</groupingString>
    </standardValue>
</StandardValueSet>

Create a new apex test that creates a contract with an unpackaged value:

@IsTest
public class ContractValueTest {
    @IsTest
    public static void test_CustomContractStatus()
    {
        Account a = new Account(Name='testing');
        insert a;

        Contract c = new Contract(AccountId=a.Id);
        Test.startTest();
            c.status = 'Working_Draft';
            insert c;
            System.assertEquals('Working_Draft', c.status, 'Custom contract status is set');
        Test.stopTest();
    }

}

Create a new package; sfdx force:package:beta:create -n DreamhouseLWC -t Unlocked -r .\force-app\
Create a new package version; sfdx force:package:beta:version:create -p DreamhouseLWC -k DreamhouseLWC -c -w 15

Expected result
A new package version should be created.
Actual result
unpackagedMetadata appears to be missing during test execution:
Version create.... Create version status: Error
ERROR running force:package:beta:version:create:  Package version creation failed with unknown error. Apex Test Failure: Class.ContractValueTest.test_CustomContractStatus: line 12, column 1 System.DmlException: Insert failed. First exception on row 0; first error: INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST, Status: bad value for restricted picklist field: Working_Draft: [Status]

System Information
sfdx version --verbose --json
{
  "cliVersion": "sfdx-cli/7.172.0",
  "architecture": "win32-x64",
  "nodeVersion": "node-v16.17.1",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 1.3.1 (core)",
    "@oclif/plugin-commands 2.2.0 (core)",
    "@oclif/plugin-help 5.1.14 (core)",
    "@oclif/plugin-not-found 2.3.3 (core)",
    "@oclif/plugin-plugins 2.1.1 (core)",
    "@oclif/plugin-update 3.0.2 (core)",
    "@oclif/plugin-version 1.1.2 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.6 (core)",
    "@oclif/plugin-which 2.1.0 (core)",
    "alias 2.1.5 (core)",
    "apex 1.2.0 (core)",
    "auth 2.2.13 (core)",
    "community 2.0.3 (core)",
    "config 1.4.21 (core)",
    "custom-metadata 2.0.1 (core)",
    "data 2.1.4 (core)",
    "generator 2.0.5 (core)",
    "info 2.1.9 (core)",
    "limits 2.0.5 (core)",
    "org 2.2.7 (core)",
    "packaging 1.9.4 (core)",
    "schema 2.1.10 (core)",
    "signups 1.2.7 (core)",
    "source 2.0.17 (core)",
    "telemetry 2.0.2 (core)",
    "templates 55.1.0 (core)",
    "trust 2.0.4 (core)",
    "user 2.1.10 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
    "salesforce-alm 54.8.1 (core)"
  ],
  "osVersion": "Windows_NT 10.0.22000",
  "shell": "cmd.exe",
}

Wow!  You get 3 gold stars for this issue.  1 for using the packaging beta commands.  1 for using the release candidate version of the CLI.  And 1 for providing all requested information including repro steps.  Awesome!
That said, I tried a few variations of your steps (mostly modifying file paths) but can't reproduce the problem on a mac.  I'm assuming this is a problem only on Windows OS.  I'll try to reproduce on a Windows box but until then can you:

Try different paths in your repro steps.  E.g., instead of "path": ".\\unpackaged" use "path": "unpackaged" to see if that makes a difference.
Run the packaging command with the doctor.  E.g., sfdx doctor --command "force:package:beta:version:create -p DreamhouseLWC -k DreamhouseLWC -c -w 15" and check the debug log for any output that would help us locate the problem.

We can't reproduce this on a windows box either.  Are there other steps involved?  I created this fork of the dreamhouse-lwc repo and ran the 2 commands you mentioned above and they both worked.

Output from running the commands this morning;

I adjusted the "path" :"unpackaged" as suggested but it made no difference.
I ran the sfdx doctor command; but can't see any mention of unpackaged metadata in the debug output.
I note in your fork you have the ContractValueTest in the unpackaged folder. Whereas in my example fork they are in the force-app/test/classes. My apologies - I had not made the location of the test classes clear.

This is happening in our project as well. We have a package/project that references unpackaged metadata. If we create a new package version using sfdx force:package:version:create with --codecoverage, the package creation process succeeds. All unit tests pass. If we use the  sfdx force:package:beta:version:create command, the package creation process fails due to unit test failures caused by the missing unpackaged metadata.

Sorry for the delay.  I reproduced it now.  We'll get it fixed asap.  Thank you for reporting!

Hi @David-Polehonski - I cloned your fork, and was able to create a package. I then ran the beta commands and saw the same error.
 ➜  sfdx force:package:beta:version:create -p DreamhouseLWC -k DreamhouseLWC -c -w 15
Version create.... Create version status: Error
ERROR running force:package:beta:version:create:  Package version creation failed with unknown error.
(1) Apex Test Failure: Class.ContractValueTest.test_CustomContractStatus: line 12, column 1 System.DmlException: Insert failed. First exception on row 0;

I then tried it with the current packaging commands and saw the same error.
➜  dreamhouse1743 git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sfdx force:package:version:create -p DreamhouseLWC -k DreamhouseLWC -c -w 15
 ›   Warning: We no longer maintain the current implementation of the "force:package:version:create" command. You should instead use the
 ›   "force:package:beta:version:create" command, which is functionally the same. If you run into issues, file a report against the
 ›   "force:package:beta:version:create" command on https://github.com/forcedotcom/cli/issues.
Request in progress. Sleeping 30 seconds. Will wait a total of 900 more seconds before timing out. Current Status='Queued'
Request in progress. Sleeping 30 seconds. Will wait a total of 870 more seconds before timing out. Current Status='Initializing'
Request in progress. Sleeping 30 seconds. Will wait a total of 840 more seconds before timing out. Current Status='Initializing'
Request in progress. Sleeping 30 seconds. Will wait a total of 810 more seconds before timing out. Current Status='Initializing'
Request in progress. Sleeping 30 seconds. Will wait a total of 780 more seconds before timing out. Current Status='Initializing'
Request in progress. Sleeping 30 seconds. Will wait a total of 750 more seconds before timing out. Current Status='Initializing'
Request in progress. Sleeping 30 seconds. Will wait a total of 720 more seconds before timing out. Current Status='Initializing'
Request in progress. Sleeping 30 seconds. Will wait a total of 690 more seconds before timing out. Current Status='Initializing'
Request in progress. Sleeping 30 seconds. Will wait a total of 660 more seconds before timing out. Current Status='Verifying metadata'
Request in progress. Sleeping 30 seconds. Will wait a total of 630 more seconds before timing out. Current Status='Finalizing package version'
ERROR running force:package:version:create:  ContractStatus: field integrity exception: unknown (invalid value)

a git status only shows the sfdx-project.json as being modified
I'm curious if this is passing with the current commands for you?

Results from sfdx force:package:version:create -p DreamhouseLWC -k DreamhouseLWC -c -w 15 on sfdx-cli/7.176.0 win32-x64 node-v18.12.0
 »   Warning: We no longer maintain the current implementation of the "force:package:version:create" command. You should instead use the "force:package:beta:version:create"
 »   command, which is functionally the same. If you run into issues, file a report against the "force:package:beta:version:create" command on
 »   https://github.com/forcedotcom/cli/issues.
Request in progress. Sleeping 30 seconds. Will wait a total of 900 more seconds before timing out. Current Status='Queued'
Request in progress. Sleeping 30 seconds. Will wait a total of 870 more seconds before timing out. Current Status='Verifying metadata'
Request in progress. Sleeping 30 seconds. Will wait a total of 840 more seconds before timing out. Current Status='Verifying metadata'
Request in progress. Sleeping 30 seconds. Will wait a total of 810 more seconds before timing out. Current Status='Finalizing package version'
ERROR running force:package:version:create:  ContractStatus: field integrity exception: unknown (invalid value)

Result from sfdx force:package:beta:version:create -p DreamhouseLWC -k DreamhouseLWC -c -w 15  on sfdx-cli/7.176.0 win32-x64 node-v18.12.0
Version create.... Create version status: Error
ERROR running force:package:beta:version:create:  Package version creation failed with unknown error. Apex Test Failure: Class.ContractValueTest.test_CustomContractStatus: line 12, column 1 System.DmlException: Insert failed. First exception on row 0; first error: INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST, Status: bad value for restricted picklist field: Working_Draft: [Status]

It would appear the unpackaged metadata isn't being processed in either case now.

@WillieRuemmele I've taken another look at this; the integrity exception comes from the StandardValueSet ContractStatus. It appears to be attempting to delete values that aren't included, and this action is not permitted via the API.
I've updated the fork to resolve the issue and re-ran the commands, output is below:
Legacy
sfdx force:package:version:create -p DreamhouseLWC -k DreamhouseLWC -c -w 15
 »   Warning: We no longer maintain the current implementation of the "force:package:version:create" command. You should instead use the "force:package:beta:version:create" command, which is
 »   functionally the same. If you run into issues, file a report against the "force:package:beta:version:create" command on https://github.com/forcedotcom/cli/issues.
Request in progress. Sleeping 30 seconds. Will wait a total of 900 more seconds before timing out. Current Status='Queued'
Request in progress. Sleeping 30 seconds. Will wait a total of 870 more seconds before timing out. Current Status='Verifying metadata'
Request in progress. Sleeping 30 seconds. Will wait a total of 840 more seconds before timing out. Current Status='Verifying metadata'
Request in progress. Sleeping 30 seconds. Will wait a total of 810 more seconds before timing out. Current Status='Verifying metadata'
Request in progress. Sleeping 30 seconds. Will wait a total of 780 more seconds before timing out. Current Status='Verifying metadata'
Request in progress. Sleeping 30 seconds. Will wait a total of 750 more seconds before timing out. Current Status='Verifying metadata'
Request in progress. Sleeping 30 seconds. Will wait a total of 720 more seconds before timing out. Current Status='Finalizing package version'
Request in progress. Sleeping 30 seconds. Will wait a total of 690 more seconds before timing out. Current Status='Finalizing package version'
sfdx-project.json has been updated.
Successfully created the package version [08c8d000000Gnm7AAC]. Subscriber Package Version Id: 04t8d0000009cUEAAY
Package Installation URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t8d0000009cUEAAY
As an alternative, you can use the "sfdx force:package:install" command.

Beta
sfdx force:package:beta:version:create -p DreamhouseLWC -k DreamhouseLWC -c -w 15
Version create.... Create version status: Error
ERROR running force:package:beta:version:create:  Package version creation failed with unknown error. Apex Test Failure: Class.ContractValueTest.test_CustomContractStatus: line 12, column 1 System.DmlException: Insert failed. First exception on row 0; first error: INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST, Status: bad value for restricted picklist field: Working_Draft: [Status]

Result
With the issue out of the way it would appear that the legacy command is including and installing the unpackaged metadata as expected allowing for package creation with code coverage, whereas the beta command is failing to do so.

Running these tests again on 7.177.1 which claims to have resolved this issue.
sfdx force:package:version:create -p DreamhouseLWC -k DreamhouseLWC -w 15 --codecoverage
Runs as expected and running a report on the package show codecoverage values:
=== Package Version

 Name                           Value
 ────────────────────────────── ──────────────────
 Name                           Summer '22
 Subscriber Package Version Id  04t8d0000009f39AAA
 Package Id                     0Ho8d0000008OcSCAU
 Version                        <IP_ADDRESS>
 Description
 Branch
 Tag
 Released                       false
 Validation Skipped             false
 Ancestor                       N/A
 Ancestor Version               N/A
 Code Coverage                  98%
 Code Coverage Met              true
 Org-Dependent Unlocked Package No
 Release Version                56.0
 Build Duration in Seconds      104
 Managed Metadata Removed       N/A
 Created By                     005w00000054XxoAAE

And the beta equivalent:
sfdx force:package:beta:version:create -p DreamhouseLWC -k DreamhouseLWC -w 15 --codecoverage
Also runs as expected and running a report on the package show codecoverage values:
=== Package Version

 Name                           Value
 ────────────────────────────── ──────────────────
 Name                           Summer '22
 Subscriber Package Version Id  04t8d0000009f3EAAQ
 Package Id                     0Ho8d0000008OcSCAU
 Version                        <IP_ADDRESS>
 Description
 Branch
 Tag
 Released                       false
 Validation Skipped             false
 Ancestor                       N/A
 Ancestor Version               N/A
 Code Coverage                  98%
 Code Coverage Met              true
 Org-Dependent Unlocked Package No
 Release Version                56.0
 Build Duration in Seconds      109.0
 Managed Metadata Removed       N/A
 Created By                     005w00000054XxoAAE

Thank you very much for resolving this issue. Keep up the excellent work, and let me know if I can do anything else.


Appropiate installation

Hi there!
First of all, thank you so much for this library! I assume something, I would like to know if am I right or not.
So I assume that if I did everything correctly, then the hce service should appear in the Android settings of services, where we can select the service.
So if I developed well my current app, the service should appear isn't it?
At present the service does not appear. :/
Thank you for your reply.

From my understanding, in Android OS, the HCE service lifecycle starts on card read, and ends when the communication has been ended.
Basically Android is continuously listening for the available NFC devices in the background, and if the card is recognized and the AID match the one defined in aid_list.xml, the OS is starting the specific HCE service (here: the react-native-hce's internal service) to start an APDU exchange.
See the official Android documentation to get more knowledge about that: Host-based card emulation overview


Windows build, fixed duplicate YAJL dir in script

Hi Felipe. I see you recently did this change https://github.com/SpiderLabs/ModSecurity/commit/c917df0f2a8acb0fb31262a5ad222d6d78394fe3 , but I think there might be a problem with the YAJL path. When building via build_modsecurity.bat directly, all is fine, because the path becomes ....\yajl\build\yajl-2.1.0 . But when building via build_release.bat , build_yajl.bat gets invoked, which sets the YAJL_DIR env variable, and so the path becomes ....\yajl\build\yajl-2.1.0\yajl-2.1.0 and the build fails.
Changing build_modsecurity.bat to let YAJL align with the other dependencies, where only the %DEPENDENCIES_DIR% env variable is used, and the rest is hardcoded.

Confirm it fixes the issue with the automated build script.
We might need to adjust the Windows buildbot builds scripts to take this into consideration.

Merged at https://github.com/SpiderLabs/ModSecurity/commit/e97799c9bc5dbf614e317ac3269ce8e7fd6c0176
Thanks! :)


Investigate automatic differentiation

This may drastically simplify basis/kernel composition. Specifically, look into autograd.

Also, can we use this to replace BOBYQA and remove the NLopt dependency completely?


[Feature Request] Native mobile selectboxes

Existing Component
Yes
Component Name
Selectbox
Description
Hi,
I didnt find that it is possible to make selectboxes to use mobile native selector.
Also it would be cool if every component that is usable  on mobile could use native selector.
By native i mean that android has own selectmenu and ios has own. Also other brands have their own.
Or should i use mint ui for that ? If yes then how.

I'm not quite sure what a native selector is. Could you upload a screenshot here?

Hello,
I mean OS own selectboxes and datepickers etc.. But option to enable or disable it for each field, and some global setting also.
Couple images i found from google:

Element is only for desktop websites. So this will not be added.


Domain activation is Failed - AWS Amplify Custom Domain Register

App Id: dr9v9qf2l501
Region: us-east-2
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
Trying to register the amplify custom domain keeps on throwing errors, it says the CNAMEs are already associated with a different resource. which is not correct.
however there is a wildcard for the same domain pointing to a different cloudfront, will that be a issue ?
by basic design is:
wildcard point to cloudfront A.
and this other custom domain ( a different react app ) points to a different cloudfront.
Example
*.domain.com -> cloudfrontA ( not amplify resource)
specific.domain.com -> cloudfrontB ( amplify resource that its failing to register the domain)
Error message
One or more of the CNAMEs you provided are already associated with a different resource.
Note: Be sure to check the message for sensitive information.
Additional information
I have tried manually removing the records myself, deleted the custom domain, and starting over, still getting the same error.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.

We are going to close out this issue, but please feel free to re-open if you still need help.


error with new jobs version

*Detailed description of the issue:
New jobs version cause an error on console sometimes
ERROR (DELETE IF YOU HAVE NO ERROR):
https://pastebin.com/GfUeunxW

Jobs version:
<IP_ADDRESS>
Server Type (Spigot/Paper/etc):
UniverseSpigot 1.20.1 (fork of pufferfish)
Server Version (using /ver):
[13:44:05 INFO]: Checking version, please wait...
[13:44:05 INFO]: This server is running UniverseSpigot version git-UniverseSpigot-"2b5c6fd" (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: 2b5c6fd on ver/1.20.1-stable)
Universe-git-UniverseSpigot-"2b5c6fd" (MC: 1.20.1)

Same issue with Jobs <IP_ADDRESS> on Paper 1.20.1.
Paper version git-Paper-196 (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: 773dd72)

fed6ef13551b6fde928b2ef6a28a01c56779010a


Fix CTF Tests

The CTF tests have been disabled for some time, and so now the files that are present in the repo are no longer usable as breaking changes were made some time back.  These changes were made intentionally, and so the fix is to capture new traces on newer runtimes.  This change captures a 2.2 and a 3.1 trace and runs them against the tests.

@ooooolivia, FYI, this change will re-enable the CTF tests.  Note that it also skips over the kernel metadata document if present because the document doesn't contain any trace information.  This is likely because I'm not collecting any trace data.  So, you may need to modify this as part of your changes to support kernel events to conditionally look at the kernel metadata if kernel events are present.  Let me know if you have questions and we can work through the details.


feat(providers): Introduce Providers Crate for Traits

Overview
https://github.com/anton-rs/kona/pull/569 refactors "online" providers (alloy-backed std providers) out of kona-derive into a new kona-alloy-providers crate since providers are trait abstracted throughout the derivation pipeline. This drastically reduces the amount of feature-flag optional dependencies in kona-derive and isolates the generic pipeline implementation a bit better.
The next step in making traits extensible is to pull trait definitions out of kona-derive and into a new kona-providers crate that can be imported by both kona-derive and `kona-alloy-providers. Effectively, we can represent the dependency graph as follows.
graph TD;
    kona_derive-->kona_providers;
    kona_alloy_providers-->kona_providers;
    kona_alloy_providers-->kona_derive;

kona-providers should mirror how Alloy set up signer crates.

alloy-signer defines the generic Signer trait(s).
alloy-signer-local defines a local signer implementation of the Signer trait.

Fixed in https://github.com/anton-rs/kona/pull/596


dd: basic implementation

Hi. It's initial implementation, Converting blocks and handling other options on the way.
Currently, it has problems with signal handling, doesn't resume copying if interrupted.

Sorry it's taken so long to get back to you, but can you write some tests comparing the behavior to GNU dd?  I am busy with upcoming midterms and essays so I don't have time to compare at the moment.

@Arcterus, what do you exactly mean? Should I add integration tests that run this program on a set of predefined files and compare that everything is correct?

Yeah, that's pretty much what I mean.  Just make sure the behavior is the same as GNU dd.

@Arcterus, could you please clarify by providing examples? I think that GNU's dd's behaviour is pretty standard.

I’m just saying if there are differences between implementations (e.g. GNU and OpenBSD) do whatever the GNU version does.

@Arcterus, it's no longer OpenBSD port anymore.

Changed default block size to 1024, like GNU's dd does.
On BSD's in has stub for handling SIGINFO, which isn't supported by chan_signal yet.
- was already done, changed order of commands.
On SIGINT prints progress and exits - was already done.

Can you still add some basic tests?  Like, for example, dd if=testfile of=otherfile.  It would be good to do so to avoid potential regressions and so on.  Also, why are src/join/join.rs (and other files) marked as changed?

Is this implementation going to make the same major flaw that GNU's dd does? Basically, it has an issue where dd destroys your data if the offset from the start sector overlaps with the end sector. The solution is to write sectors in reverse in those situations, to guarantee that copies aren't overlapping.
Essentially, it will start at the beginning, read N amount of sectors, and then seek to a point before the end sector and obliterate whatever data was written there. Eventually it catches up and starts reading the already-written data and copying that until to end is reached. Any data in the crossfire is lost. Using a simple check, you can avoid that so that you start reading from the end sector, then write to the new end sector, in reverse. No more overlapping reads & writes.

@mmstick this is the sort of issue where I would consider differing in behavior from GNU (or at least provide the ability to change the behavior at compile-time/runtime if we don't differ by default).  In any case, given that this PR hasn't been updated in a couple months, I will likely make some changes to the code and then merge an implementation of dd in the next few weeks.  I will take this issue into consideration when I do that.

It's been over a year for this - is help required?

Is there still an interest to commit this?

closing as it is stuck!
Feel free to reopen


Collect expenses on one screen

Use average values as defaults?

Alternative:
Collect expenses in groups, presenting categories:
Housing, Childcare, Fuel, Furniture and Bedding, Health Costs, Transport, Hire purchase, Fines, Laundry/ Dry cleaning, Telephone/TV/Broadband, Other household items/toiletries and food, clothing and shoes, gifts, charitable donations and religious and cultural actvities,, other,
https://askcpag.org.uk/?id=-216954#:~:text=END NOTES-,Items of expenditure,-HOUSING

This find is great - also explains why the logic also pulled out low expenses because debt advisors are supposed to ask about expenses below normal too.  But it also makes me think we need to ask about all expenses, and then determine which of the expenses can be counted as expenditures.  (Which sorta seems like the interview broke out alcohol and drugs, but the logic didn't exclude from the total.)

How does a debt advisor look at expenses? What do they look at and want to know more? What do they have to provide additional information about? Unreasonably high? Unreasonably low?

can we create flags for unreasonably hight? low? what does that look like and when is it important versus
ex. if they say that they have NO income - a second screen that asks again, lists everything that can be considered incme and presents the opportunity again to add income.


Extend Nexus Allowlist to Support Debian Packages Required for R Package Installation

I would like to propose extending the functionality of the Nexus Allowlist to manage Debian packages that are necessary for installing certain R packages. Many R packages require many (!) system-level dependencies (Debian packages in my case) for successful installation.
I am willing to develop this feature if you find the idea relevant.
How do you currently handle system dependencies required by R packages?

You can configure apt repositories in Nexus.
I think that would be a good feature to add.
In places where I use this project, we have a separate proxy for apt.


#7268: Add Boris as codeowner for models/demos/grayskull

Are there going to be specific models for grayskull? And what does this mean for other models already written?

We want to add grayskull specific demos for T5, Bloom, and Whisper; they will go in this folder.
There are no plans for moving other models at this time.


Support DG2 new device ID

Add new device ID 0x56AF
Tracked-On: OAM-126993

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

SUCCESS: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started MERGE Build for this pr ,Please check the linked Tracked-On issue/Android CI Web  for more details.


Fixed Expression has changed after it was checked

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
The bug fix for Expression has changed after it was checked. Previous value: '0'. Current value: '1'.

That's indeed how I fixed the Expression has changed after it was checked. Previous value: '0'. Current value: '1'. error.
Good job


Fix Grafana apt repo package path and release name

According to the docs, the debian path and release name should be used for Ubuntu:
http://docs.grafana.org/installation/debian/

@alexmuller updated to jessie.

Thanks, looks good to me :+1:


new-repo-disable-projects-and-wikis - Restore feature

close: #6829
Test URLs

github.com/new
https://github.com/new?template_name=browser-extension-template&template_owner=fregante

Screenshot
after:

I always forget to run lint script. 😅

Is there anything else I can do for this project? Maybe you can give me a new feature. I'm glad to do it.

Bugfixes are always welcome. small-tagged features too. There's also small stuff in https://github.com/refined-github/refined-github/issues/6000 that's always helpful.
We also have a couple additional repos with issues:

https://github.com/refined-github/github-url-detection/issues
https://github.com/refined-github/shorten-repo-url/issues


The actual type of the function return value is inconsistent with the expected type

Bug Report

🔎 Search Terms

spread operator, incorrect type check information,
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about TS4.2.3

⏯ Playground Link

Playground link with relevant code
💻 Code

interface ListItem {
  name: string
  age: number
}

function test(): ListItem[] {
  const a = [{
    name: "name",
    age: 18
  }]
  return {
    ...a
  }
}

🙁 Actual behavior

First of all, the expected return value type is an array, but there is no error message when returning an object
Secondly, TypeScript seems to have an array attribute on the return value of the test function, which is a bit abnormal

🙂 Expected behavior

I hope that the type information can be matched correctly, and the corresponding type error message will be given，thanks

Looks like a duplicate of #35778.


training Error: latents not exist

Do I need to train to get the .pt model file myself, or will the MARS program automatically train it?
/DATA_EDS/liuty/ckpts/pretrain/car_nerf/latent_codes_car_van_truck.pt

please download the checkpoints （urls are in the readme） and modify the configs

please download the checkpoints （urls are in the readme） and modify the configs

Thank you zirui，Under your guidance, I resolved the issue after downloading the resources mentioned in the readme


Fix function naming typo

What type of PR is this?
Fix function naming typo from applyPluingSet to applyPluginSet

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
/label tide/merge-method-squash

/ok-to-test

/kind cleanup


Don't strip semi-colons from expressions with non-void type since it …

…can change semantics
Closes #542

Are we sure we're not adding semicolons where they were not before?

I don't think so, the only place this changes is when an expr is wrapped in a ast::Stmt_::StmtSemi which means there was already a semi-colon in the source text (aiui).

Cool!


Migration Guide Update :tada:

Biggest structural change is that the migration guide has been moved to the top, so it doesn't get buried anymore. I also mentioned the ember-cli migrator, talked about custom environments, and updated the api stub instructions.
cc @tehviking

oh whoops, wrong branch! :( let me make a new one


add support for Azure OIDC

Two things are needed to support Azure OIDC:

allow disabling "groups" scope
combine roles with groups

Azure does not support "groups" scope - we need a way to disable it.
There are a number ways of indicating intent: env var, cmd option, based on issuer url. I will leave decision on what is the best approach to Weave Works team.
PR uses env var - helm chart config:

    envVars:
    - name: WEAVE_GITOPS_FEATURE_OIDC_GROUPS_SCOPE
      value: "false"

Azure registered application can be configured to send groups in jwt claim. Issues is that Azure sends group ids (which are uuids) and these are bad candidates for group names on k8s side. Better idea is to setup "App roles" in given Application on Azure side. These come as "roles" array in jwt token - hence update that merges Groups and Roles.
Another idea for handling groups in Azure would be to map between group uuid and group on k8s side (this is how Argo team handled it).

Closes #2507, #2334
In case this is tested with impersonationResources: ["groups"] there is helm chart configuration issue: #2696 that warrants chart and documentation update.

Would be great if a maintainer could have a look at this

This is also relevant to Google OIDC. The groups scope is unsupported, so we can't use Google accounts to sign in to the dashboard.

any chance this get merged any soon? this would be useful for us too

any ETA when this will be merged?

@foot would you be able to take a look at this, please? 🙏🏻

Same issue with AWS Cognito.

In v0.15.0 the custom-oidc-scopes flag has been introduced #3234
This flag is default set to openid,offline_access,email,groups so this can be changed to leave out the groups scope.
I'm able to use Azure OIDC with the following values:
values:
  additionalArgs:
    - --auth-methods=oidc
    - --oidc-client-id={your_id}
    - --oidc-client-secret={your_secret}
    - --oidc-redirect-url=https://{your_gitops_url}/oauth2/callback
    - --oidc-issuer-url=https://login.microsoftonline.com/{tenant_id}/v2.0
    - --custom-oidc-scopes=openid,offline_access,email

Closing. Since https://github.com/weaveworks/weave-gitops/pull/3234 you can override scopes using secret's customScopes or --custom-oidc-scopes=openid,profile,email.
If you use Azure's App Roles you can also use claim's roles as groups just set secret's claimGroups: roles.
Longer version:

In Azure create app role weave-gitops-viewer-role, assign groups/users.
Setup secret (remove groups claim, set claimGroups to roles):

kind: Secret
metadata:
  name: oidc-auth
data:
  customScopes: openid,profile,email
  claimGroups: roles
  claimUsername: email
  clientID: ........-....-....-....-............
  clientSecret: ...
  issuerURL: https://login.microsoftonline.com/.../v2.0
  redirectURL: ...

Update helm chart values

    logLevel: debug
    additionalArgs:
      - "--auth-methods=oidc"
    rbac:
      impersonationResources: [ "groups" ]
      impersonationResourceNames: ["weave-gitops-viewer-role"]

Check logs, you should see {"user": "....", "groups": ["weave-gitops-viewer-role"],...}

Related solution: https://github.com/weaveworks/weave-gitops/issues/2507#issuecomment-1362687065

@LukaszRacon
I tried your solution, but I am stuck with the error
ERROR    gitops.auth-server    auth/server.go:479    failed to parse user info    {"error": "missing \"xxx\" claim in response"}
I tried setting the claimUsername to various things such as email, upn and preferred_username, but they all give the same error. In chrome dev tools I see the cookie containing id_token and access_token. Inspecting them further it shows that the id_token does contain preferred_username while the access token contains email. Any idea what might be wrong?

@audunsolemdal
Double check if authorization request has email in scope. If you use Secret oidc-auth check if you have defined: customScopes: openid,profile,email
Is email associated with Azure AD account that you are using?
Try adding optional claim:

Token Configuration > +Add optional claim > ID > Email > Add.
API Permissions > +Add permission > Microsoft Graph > Delegated permissions > OpenID permissions > Email > Add permission.

Reference:
https://learn.microsoft.com/en-us/azure/active-directory/develop/active-directory-optional-claims
email:  This value is included by default if the user is a guest in the tenant. For managed users (the users inside the tenant), it must be requested through this optional claim or, on v2.0 only, with the OpenID scope. This value isn't guaranteed to be correct, and is mutable over time - never use it for authorization or to save data for a user. ...

Closing. Since #3234 you can override scopes using secret's customScopes or --custom-oidc-scopes=openid,profile,email.
If you use Azure's App Roles you can also use claim's roles as groups just set secret's claimGroups: roles.
Longer version:

In Azure create app role weave-gitops-viewer-role, assign groups/users.
Setup secret (remove groups claim, set claimGroups to roles):

kind: Secret
metadata:
  name: oidc-auth
data:
  customScopes: openid,profile,email
  claimGroups: roles
  claimUsername: email
  clientID: ........-....-....-....-............
  clientSecret: ...
  issuerURL: https://login.microsoftonline.com/.../v2.0
  redirectURL: ...

Update helm chart values

    logLevel: debug
    additionalArgs:
      - "--auth-methods=oidc"
    rbac:
      impersonationResources: [ "groups" ]
      impersonationResourceNames: ["weave-gitops-viewer-role"]

Check logs, you should see {"user": "....", "groups": ["weave-gitops-viewer-role"],...}

Related solution: #2507 (comment)

I just did a test and you can impersonate groups with the following configuration:

In azure configure your app to send the group claim: Token Configuration -> add group claim
Configure the deployment with:

    - --auth-methods=oidc
    - --oidc-client-id={your_id}
    - --oidc-client-secret={your_secret}
    - --oidc-redirect-url=https://{your_gitops_url}/oauth2/callback
    - --oidc-issuer-url=https://login.microsoftonline.com/{tenant_id}/v2.0
    - --custom-oidc-scopes=openid,offline_access,email
    - --oidc-groups-claim=groups

Then it works with groups

@LukaszRacon Thanks for the advice. I tested around a bit, and realized that the email attribute for my profile and a lot of other profiles in the organization is null, as we are external consultants without a valid mailbox. We do have a value at preferred_username and upn which in both cases are the username I login with. I've created other app registrations for AAD auth in the past (oauth2-proxy, Grafana AAD auth) and preferred_username worked fine.
My oidc-auth secret has the following attributes
    "customScopes"  = "offline_access,openid,profile"
    "claimGroups"   = "roles"
    "claimUsername" = "upn"
    "clientID"      = redacted
    "clientSecret"  = redacted
    "issuerURL"     = "https://login.microsoftonline.com/redacted/v2.0"
    "redirectURL"   = "https://redacted.no/oauth2/callback"

and additional args
    additionalArgs:
      - "--auth-methods=oidc"

I've added optional claims for both id_token and access_token for preferred_username and upn
Copy pasting the tokens from developer console into jwt.ms, the required claims are clearly there in both the access AND id tokens. I'm confused as to what the gitops-server is actually seeing, because the logs clearly still state ERROR    gitops.auth-server    auth/server.go:479    failed to parse user info    {"error": "missing \"upn\" claim in response"}

It seems I made the above work by changing the issuerURL to use the v1 AAD endpoint ref. https://github.com/weaveworks/weave-gitops/issues/2507#issuecomment-1362687065
--oidc-issuer-url=https://sts.windows.net/{tenant_id}/
not really sure why this is required, but I am able to sign in using OIDC for the first time, so that's a start!


Enable BigQuery CDC configuration for Python BigQuery sink

Enables the configuration of CDC writes into a BigQuery table by setting the primary key columns to be used in the row mutations.  This change adds the configuration of CDC usage for the BigQueryStorageWriteApiSchemaTransformProvider.
By setting configuration.setUseCDCWritesWithPrimaryKey(List.of("col1", "col2")) on the provider's config, the transform creation will create a BigQuery.Write<Row> transform that will configure the right row mutation information by checking for a Row schema like:
{
  row_mutation_info:{
    mutation_type: "..."              // can be UPSERT or DELETE
    change_sequence_number: "..."     // used for custom insert ordering
  }
  record:{...}                        // actual data to be inserted
}

The implementation also enables the possibility of setting a dynamic destination alongside with CDC usage by using this Row schema:
{
  row_mutation_info:{
    mutation_type: "..."              // can be UPSERT or DELETE
    change_sequence_number: "..."     // used for custom insert ordering
  }
  destination: "..."                  // destination table for the data
  record:{...}                        // actual data to be inserted
}

Note: In case of using dynamic destination and CDC is only supported when all the destination share the same primary key columns.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

fixes #32527

I have a question @ahmedabu98, how to make sure the xlang tests for BQ have run?
This branch test output for the test looks pretty similar to those that ran in master the last time, but in both cases it seems that the BQ StorageWrite transform is not being registered.
Am I looking at the right place or are the IT for xlang run in some other different task?

The test you are referencing is to generate wrappers for external transforms (unrelated here since this wrapper is handwritten).
The workflows testing GCP xlang IOs are in beam_PostCommit_Python_Xlang_Gcp_Dataflow and beam_PostCommit_Python_Xlang_Gcp_Direct. These are post commits so to trigger them you just need to modify their respective target files and push it to this branch:

Direct runner trigger file
Dataflow runner trigger file

Run Java_GCP_IO_Direct PreCommit

Adding reference for successful xlang test executions:

beam_PostCommit_Python_Xlang_Gcp_Dataflow
beam_PostCommit_Python_Xlang_Gcp_Direct

Run Java_GCP_IO_Direct PreCommit

Run Java_Examples_Dataflow PreCommit

FYI @prodriguezdefino we migrated our tests from Jenkins to Github Actions, so tests aren't triggered by comments anymore. I re-ran the Java examples workflow from my side
Check out https://github.com/apache/beam/tree/master/.github/workflows#readme for more info

@ahmedabu98 thanks for launching the test run.
I think I covered the previous comments on the PR, do you think is ready or it needs more work?

Before I merge, can we add a line to CHANGES.md calling out this new feature? (make sure to mention it's specifically for storage write api's at-least-once mode)

Before I merge, can we add a line to CHANGES.md calling out this new feature? (make sure to mention it's specifically for storage write api's at-least-once mode)

Added the changes here: https://github.com/apache/beam/pull/32788 (less tests that need to pass for the change).
Thanks for the review!

SGTM, merging


Separate out tests/expected results from code

It would be nice to separate out the test cases and the expected results for them into a separate file that's parseable outside of Swift. Something like YAML or JSON format. This allows others to implement this in other languages and rely on the same the cases to validate their implementation.

@umgefahren I started extracting test-cases into YAML format https://github.com/cooklang/CookInSwift/pull/10/files#diff-108cc582ddc8fb36abf94aa6a115396b00fe3465cfad02ba7a269e005f3a1429. I'm curious if that what you meant?

Extracted tests, closing the issue.


Running two different models on the same machine

I want to run two different models on the same machine. Right now, I'm declaring two different AsyncLLMEngine objects such that the respective gpu_memory_utilizations add up to 1 but I'm getting CUDA OOM errors.
What would be the right way to do this? Thanks!

Closing this issue as stale as there has been no discussion in the past 3 months.
If you are still experiencing the issue you describe, feel free to re-open this issue.


More on Python support

Current coverage is 100% (diff: 100%)

Merging #9 into master will not change coverage

@@           master    #9   diff @@
===================================
  Files           6     6
  Lines         109   109
  Methods         0     0
  Messages        0     0
  Branches        6     6
===================================
  Hits          109   109
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update c7e4b0c...9b0aaf6


extend bootstrap Tabs with urls (non-ajax content)

The issue:
Bootstrap has two tab styles:

css  http://getbootstrap.com/components/#nav-tabs
js http://getbootstrap.com/javascript/#tabs

The current \yii\bootstrap\Tabs focuses on the JS version. This means you can not have the best of two worlds. Sometimes I dont want a Tab to be loaded by Ajax, but to be at a separate page. Reasons:

you need a tab content to be on a different page because of loading JS/AJAX
you need a tab content to be on a different page because of your specific route architecture

On this separate page you are linking back with a CSS style Tab.
Therefore I would like to suggest to enable the acception of an URL. This would extend the functionality of current Tabs Besides, it would also enable the bootstrap CSS styled Tab, improving disambiquity on this matter.
This is a minor addon, I can do a submit for this.

Nav tabs isn't tabs widget but Nav one.

its not a trigger, its a (menu) link
it is a tab widget as both ajax & links are both possible
using multiple nav-menu is ugly and unnecessary
the solution is (too) easy without disadvantages
it has multiple advantages

Pull request
https://github.com/yiisoft/yii2-bootstrap/pull/11

pull request from the Yii2 repo:
https://github.com/yiisoft/yii2/pull/7284

fixed by https://github.com/yiisoft/yii2-bootstrap/commit/554c3ccf04ee0c5ae699615d2866d8a6826d1ffb


System.IO.FileNotFoundException with UWP and TinyIoC 1.3.0

Create new Xamarin project - UWP
Add TinyIoC 1.3.0 to all projects in solution
Add TinyIoCContainer to App.xaml.cs:
using TinyIoC;
using Xamarin.Forms;
using XFDependencyInjectionTest.Models;
using XFDependencyInjectionTest.Services;
using XFDependencyInjectionTest.Views;

namespace XFDependencyInjectionTest
{
public partial class App : Application
{
public static TinyIoCContainer tinyIoCContainer;
    public App()
    {
        InitializeComponent();
        tinyIoCContainer = new TinyIoCContainer();
        tinyIoCContainer.Register<IDataStore<Item>, MockDataStore>();
        DependencyService.Register<MockDataStore>();
        MainPage = new MainPage();
    }
}

}

Inject object into constructor of viewmodel:
public class AboutViewModel : BaseViewModel
{
public AboutViewModel(IDataStore dataStore) : base(dataStore)
{
Title = "About";
OpenWebCommand = new Command(async () => await Browser.OpenAsync("https://xamarin.com"));
}

Build/run UWP project.

Error: : 'Could not load file or assembly 'XLabs.Ioc.TinyIOC, Version=2.0.5782.12282, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.'
Bin directory contains XLabs.Ioc.dll and XLabs.Ioc.TinyIOC.WP8.dll.  Version numbers for DLLs do not match version in error.

You'll need to define compiler directives, did you do this? Also, we don't set the assembly version anywhere so I'd try and track that down. Are there any build errors or warnings?

Same project doesn't work on Android either.

I'm closing this until my previous questions are answered.

I know this is closed, but I am getting a similar problem.
I am working on an existing Xamarin project and wanted to add TinyIoC.
The steps I have taken:

Existing project builds and runs (UWP)
Add XLabs.IoC.TinyIoC (2.0.5782) to Xamarin Forms & three UI Projects.
UWP project still builds and runs.
Add single line var ioc = TinyIoCContainer.Current; to App.xaml.cs.

When trying to run the UWP app I get the message:
Could not load file or assembly 'XLabs.Ioc.TinyIOC, Version=2.0.5782.12282, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

I have not defined a compiler directive. I am not sure what that means, and I can't find any reference to that in the documentation.

The package that you picked up was built with early mobile platforms in mind and not UWP. If you look at its content it supplies PCL target frameworks that a UWP build might ignore.
Unless you need that specific old build I would look either for a different package (I don't have recent experience with this) or embed the tiny IOC source yourself (what I've been doing for some time).


Improve the display of runner type

Before:

After:

Or make it as two lines

For example

Conflict in  templates/shared/actions/runner_list.tmpl.

@silverwind
CI failed is related to https://github.com/go-gitea/gitea/pull/24377/commits/94da9793b8355b04232c41ababee4ba724e62eba?

Hmm yes, revert to previous? What was //revive:disable-line:exported doing exactly?

If the variable name starts at package name, we will get an lint error.
For example, if the package name is runner, then we can not define any variables like RunnerXXXXX.
Ah, I copied the code from other place, it seems that we don't need this here.

I see. Always use //nolint variant please as those will also error when the directive is unused, which I think is not true for //revive directives.

Please wait for a while, is it fine to make models package depend locale? There are few such usage.

Why not?
The order is models < modules, so models may import modules.
So yes, I'd absolutely say that it is fine…

The order is models < modules, so models may import modules.

If most people agree with it, then I have no objection.
There is still a question:  https://github.com/go-gitea/gitea/pull/24377#discussion_r1182007406
There are still many features shared by user/reop/org/global:

OAuth2 application
WebHook
(maybe more)

Do we want to keep adding these strings again and again?
runners.owner_type.global = Global
runners.owner_type.organization = Organization
runners.owner_type.repository = Repository

https://github.com/go-gitea/gitea/blob/df00ccacc9a4840fe86bed75a77841f8801d11d2/options/locale/locale_en-US.ini#L3437-L3440

@wxiaoguang do you want to block?

@wxiaoguang do you want to block?

Give me a few ours, I will try to edit this PR to see whether we can use unique translation strings.

Hmm ... and one more thing, I am afraid it's better not to use the name Type , it seems BelongsToType is clearer. Other models Typre fields are really the type, so I think Type is not suitable for Runner in this case.
(I will try to rename it together)

What do you think about this one?

https://github.com/yp05327/gitea/pull/2

We can introduce a general OwnerType, then other models can also use it without introducing more translations.


Adding TSort support

Discussion
similarly, ruby has tsort.rb
so it's just convenient  to have tsort for topological sorting

Duplicate of #9922


Updated the Prepositions to Sound More Native

Coverage remained the same at 88.425% when pulling a8cefcd946fe4149b7c0bf165d81aff7c1e6bbea on fadsel:patch-1 into de98cc4f23fd68b92465a494ed456a1d64c5dc52 on moment:develop.


Update running_locally.md

Had to dive quite deep in order to find this missing part in my configuration. Perhaps mentioning it here speeds up the process for others?

I have read the CLA Document and I hereby sign the CLA

Totally fair. We count on chains to be added first to our safe-eth-py package, but it's not mandatory


tested with normalize.css 7?

Version info
Milligram: v1.3.0
Other (e.g. normalize.css, node.js, npm, bower, browser, operating system) (if applicable):
    "imagemin": "^5.2.2",
    "milligram": "^1.3.0",
    "node-sass": "^4.5.2",
    "normalize.css": "^7.0.0"

Expected behavior
work with normalize.css v7.x
Actual behavior
¯_(ツ)_/¯

Hi @chuckreynolds
I understand what you mean. However, you do not need to define the dependency normalize along with Milligram in your project. Only Milligram is enough. Normalize is implicitly defined in dependencies of Milligram so it will be installed in the same way.
Let me know what's new in the new version of Normalize

well, there's this: https://github.com/necolas/normalize.css/blob/master/CHANGELOG.md

@chuckreynoldsI had already seen the changelog. Apparently it's just these changes:
/* Removed */
html {
  font-family: sans-serif;
}

a:active,
a:hover {
  outline-width: 0;
}

fieldset {
  border: 1px solid #c0c0c0;
  margin: 0 2px;
}

/* Updated */
fieldset {
  padding: 0.35em 0.75em 0.625em;
}

Note, you can better visualize the changes from one version to another in this way:
Normalize: v5.0.0 -> v7.0.0
So I have not yet had the opportunity to do something more specific such as the visual regression test that Milligram possesses. I wanted to hear from you. Did you notice anything unusual in Milligram when you upgraded Normalize to version 7?

@chuckreynolds I had already seen the changelog. Apparently it's just these changes:
/* Removed */
html {
  font-family: sans-serif;
}

a:active,
a:hover {
  outline-width: 0;
}

fieldset {
  border: 1px solid #c0c0c0;
  margin: 0 2px;
}

/* Updated */
fieldset {
  padding: 0.35em 0.75em 0.625em;
}

Note, you can better visualize the changes from one version to another in this way:
Normalize: v5.0.0 -> v7.0.0
So I have not yet had the opportunity to do something more specific such as the visual regression test that Milligram possesses. I wanted to hear from you. Did you notice anything unusual in Milligram when you upgraded Normalize to version 7?

I haven't noticed any issues on the small site i'm using this on but i'm deep in dev still.

@chuckreynolds Now Milligram v1.4.0 uses Normalize.css v8.0.1
Thank you for this question.
For now, I will close this issue.
Please, if you need help feel free to reopen or open a new!


Questions about the provided fine-tuning model parameters

Hello author, when I tested the performance of the provided timechat_7b.pth, I found that the measured indicators were lower than the results reported in the paper. I fine-tuned Timechat according to the requirements in the paper, the measured performance was higher than the provided timechat_7b.pth result. I would like to ask if there is something wrong with my fine-tuning/testing phase? Or are there errors in the fine-tuned model parameters provided?
Here are the results I got from testing the provided fine-tuning parameters timechat_7b.pth: (Because some videos are lost, the test data is nearly 20 less, but I guess it will not have a big impact on the results)
[val] gt video nums 396; pred video nums 396 gt video nums 396; pred video nums 396 evaluate data samples:  396 gt file:  paragraph video captioning Para_CIDER 2.5 Para_METEOR 6.7 dense video captioning CIDER 2.4 METEOR 0.9<EMAIL_ADDRESS>26.8<EMAIL_ADDRESS>26.7<EMAIL_ADDRESS>8.9<EMAIL_ADDRESS>9.9<EMAIL_ADDRESS>2.1<EMAIL_ADDRESS>2.9<EMAIL_ADDRESS>0.4<EMAIL_ADDRESS>0.6 Precision_Mean 9.5 Recall_Mean 10.0 F1_Score 8.7 SODA_c_2 0.9 n_preds 7.6 SODA_c_1 -100.0
The following are the results of the fine-tuned checkpoint_2.pth that I reproduced myself:
[val] gt video nums 396; pred video nums 396 gt video nums 396; pred video nums 396 evaluate data samples:  396 gt file:  paragraph video captioning Para_CIDER 2.1 Para_METEOR 8.1 dense video captioning CIDER 2.8 METEOR 1.0<EMAIL_ADDRESS>31.1<EMAIL_ADDRESS>43.5<EMAIL_ADDRESS>11.0<EMAIL_ADDRESS>17.9<EMAIL_ADDRESS>3.4<EMAIL_ADDRESS>6.3<EMAIL_ADDRESS>0.4<EMAIL_ADDRESS>0.8 Precision_Mean 11.5 Recall_Mean 17.1 F1_Score 12.4 SODA_c_2 1.2 n_preds 11.0 SODA_c_1 -100.0

Hi, thanks for your interests.
The zero-shot performance of timechat_7b.pth on YouCook2 (as shown in the following img) should be higher than the results in our paper:

If not, please check that if you correctly transform the video to "youcook2_6fps_224" (see https://github.com/RenShuhuai-Andy/TimeChat/blob/master/docs/DATA.md#compressing-videos)
Which dataset did you use for tine-tuning? TimeIT? If so, I think the results are comparable to the results in our paper.


File path problem

i have modified path in ${TinyBenchmark}/tiny_benchmark/maskrcnn_benchmark/config/paths_catalog.py
But there are still path problems，What should I do？

[error]：No such file or directory:
'/home/$user/TinyBenchmark/dataset/tiny_set/erase_with_uncertain_dataset/annotations/corner/task/tiny_set_train_sw640_sh512_all.json'

I can't see the image you uploaded. I guess your problem may caused by wrong path you have set.
you may need download dataset in section in your disk, assume you download in /home/your_name/TinyBenchmark/dataset/tiny_set, and then you just modify
DATA_DIR = "/home/$user/TinyBenchmark/dataset"
to
DATA_DIR = "/home/your_name/TinyBenchmark/dataset/"


[Tests-Only] Bump commit for oC10APIAcceptanceTests

Includes these oC10APIAcceptanceTests changes from recent days:
https://github.com/owncloud/core/pull/37745 Include trailing slash when matching a suite name
https://github.com/owncloud/core/pull/37746 Refactor listFolder acceptance tests
https://github.com/owncloud/core/pull/37749 use usersHaveBeenCreated & delete UserHelper::createUser
https://github.com/owncloud/core/pull/37751 Add tests for new capabilities
https://github.com/owncloud/core/pull/37752 Skip new lock tests on old ownCloud

475 scenarios (475 passed)
3705 steps (3705 passed)
7m6.82s (22.60Mb)

https://cloud.drone.io/cs3org/reva/2054/4/6


Updated tuning.py so it works with Python >=3.2

Same issue as occurred in   this other Github repo
Essentially, Python3.9 removed the function tostring() and we now need to use  tobytes().
The change also includes a check for the minor version to run the new tobytes() function if we run in 3.2 or higher.
I hope this helps a little and addresses at least this one forum post.

works on my machine

LGTM. Approved.

thank you a lot


Do not error when a service decorates an unknown service.

Fixes #618

I didn't see anything that made it apparent to me that the ServiceMap is intended to validate that services.yml's are well formed with all dependencies met.
Currently the ServiceMap ignores services with an unknown parent, while this change causes us to not attempt to enrich and unknown decorated service (we don't need to ignore the entire service, we just can't provide richer data to the decorated service.)
The ServiceProvider was a final tipping point since we already know nothing about services provided by a ServiceProvider  making this a hard fail would add a dependency that we be able to process ServiceProviders.
I also considered that when $container->get('unknown') is called the NULL from the ServiceMap doesn't appear to be reaching into PHPStan, this means the unknown service are currently treated as MIXED elsewhere.
If we don't want to silently ignore decorators we would likely want to refactor this to at least raise a clear exception instead of an undefined array key access.

Let's silently ignore. I've been trying to find ways to make this "better." The "normal way" would be reading a dumped service container – like Symfony can do. But with Drupal that requires a database and more.


[XABT] Use SortedSets in JCWGenerator.EnsureIdenticalCollections for better performance.

JCWGenerator.EnsureIdenticalCollections ensures that every architecture being built contains the same Java derived types. Because this includes Mono.Android.dll, even the dotnet new android template has ~8500 Java types found. The current implementation uses nested loops and is O(N²). By first sorting the items into SortedSet types and then using SetEquals we can significantly speed up this operation.
Fresh dotnet build of Android template (defaults to 4 architectures), EnsureIdenticalCollections takes:

main
3081 ms

PR
29 ms

I'm going to merge as-is, to better test build performance in 9.


Update to React Hot Loader 3.0 when it ships

This is not a problem of this library but a known issue of React Hot Loader that is used underneath. There is a plan to solve this with the new version as you can see here. I found this problem when I was trying to implement the React Redux template and just posted as some more people could face the same issue.

Thanks! Have amended this issue title to specify what we're going to do.
For anyone else reading, this is a work item we'll do when https://github.com/gaearon/react-hot-boilerplate/pull/61 ships.

5 months later it's not clear if or when gaearon/react-hot-boilerplate#61 will ship. Also I'm unsure what the issue is anyway - AFAIK, HMR works correctly in the ReactReduxSpa template.
I'll close this as it's not clear that there's anything we can do here. But, once React Hot Loader 3 does ship, we will update to it!


1.52.0

A lot of APIs we use in this release!

bors try

I've resolved the handlers.rs conflict by accepting my changes from https://github.com/rust-analyzer/rust-analyzer/pull/8711/files#diff-13acc206c18467a7dbe2876d204fee460c728232fbb677a4d769641e76dd9fe5 and discarding the 1.52 ones, since the parsing function had been changed entirely.
Yet I've done it via the GitHub UI and that apparently introduced the merge commit instead of the rebase: if that's unwanted, we need a proper rebase.

Merge commits will be rejected by CI, so ye we want a proper rebase here instead

Well, I'll take it over since started to mess with it, hope it's fine.

bors try

Well, I'll take it over since started to mess with it

Thanks!

bors r+


build error

I am getting this error while running make docker-build command on a mac environment.
cd build/grpc-health-checker && make install-deps build-x86-64
glide -q install
[WARN]	The name listed in the config file (github.ibm.com/deep-learning-platform/grpc-health-checker) does not match the current location (github.com/IBM/FfDL/etc/dlaas-service-base/build/grpc-health-checker)
rm -rf bin/
CGO_ENABLED=0 GOOS=linux go build -ldflags "-s" -a -installsuffix cgo -o bin/grpc-health-checker
docker build -q -f Dockerfile.ubuntu -t dlaas-service-base:ubuntu16.04 .
sha256:6975b033728017afc0f9a2dd9978e76331411d323fef07c9b8600959cccdbf4a
docker tag dlaas-service-base:ubuntu16.04 docker.io/ffdl/dlaas-service-base:ubuntu16.04
docker build -q -f Dockerfile.alpine -t dlaas-service-base:alpine3.3 .
sha256:9e367f913da06d9758a26936bff18c23587e5eebfd424f9793a0cd488742e75b
docker tag dlaas-service-base:alpine3.3 docker.io/ffdl/dlaas-service-base:alpine3.3
(full_img_name=ffdl-metrics; \
		cd ./metrics/ && (if [ "minikube" = "minikube" ]; then eval $(minikube docker-env); fi; \
			docker build -q -t docker.io/ffdl/$full_img_name .))
Sending build context to Docker daemon  11.26MB
Step 1/6 : FROM dlaas-service-base:ubuntu16.04
pull access denied for dlaas-service-base, repository does not exist or may require 'docker login'
make[1]: *** [.docker-build] Error 1
make: *** [docker-build-metrics] Error 2```

It looks like you are using "minikube" as your build environment. If you want to build and run FfDL on your Minikube's Docker daemon. Then you need to run eval $(minikube docker-env) to point your Docker CLI to the Minikube's Docker daemon.
If you just want to build FfDL on your default Docker daemon, run export VM_TYPE=none to avoid the makefile building FfDL docker images with your Minikube's Docker daemon.

Sounds good. Modifying the developer guide to state that would be useful.

Thanks @visahak, we are still in early stage, so we will have a lot of documentation changes coming soon.

Thanks @visahak - please also submit a PR if you think mentioning this at a certain point in flow would be better.

I am getting error with one pod that gets into CrashLoopBackoff status. I have tried a few times with clean 'helm install' but get the same error.
ffdl-trainingdata-86c5578b75-v884m   0/1       CrashLoopBackOff   5          7m
Any suggestion, how to get past this error and have a clean deployment of this fabric? Thanks

@visahak can this be closed? Still running in build issues?

Resolved in #73


"InvalidArgumentException: Database not configured." 500 Interval Server Error

Hi Luca,
I'm trying to implement an oauth2 server using laravel for practicing. Then I chose the Client Credentials Grant.
Here are my settings.
oauth2.php
    'grant_types' => [
        'client_credentials' => [
            'class' => '\League\OAuth2\Server\Grant\ClientCredentialsGrant',
            'access_token_ttl' => 3600
        ]
    ],

routes.php
Route::post('oauth/access_token', function() {
    return Response::json(Authorizer::issueAccessToken());
});

After I set up and created clients, I tried to post data.
This is my call:

But I got an error message:
InvalidArgumentException in DatabaseManager.php line 246:
Database [webapp] not configured.

1. in DatabaseManager.php line 246
2. at DatabaseManager->getConfig('webapp') in DatabaseManager.php line 157
3. at DatabaseManager->makeConnection('webapp') in DatabaseManager.php line 65
4. at DatabaseManager->connection('webapp') in FluentAdapter.php line 52
5. at FluentAdapter->getConnection() in FluentClient.php line 75
6. at FluentClient->get('1', 'abcd', null, 'client_credentials') in ClientCredentialsGrant.php line 81
7. at ClientCredentialsGrant->completeFlow() in AuthorizationServer.php line 275
8. at AuthorizationServer->issueAccessToken() in Authorizer.php line 80
9. at Authorizer->issueAccessToken() in Facade.php line 207
10. at Facade::__callStatic('issueAccessToken', array()) in routes.php line 24
11. at AuthorizerFacade::issueAccessToken() in routes.php line 24
12. at RouteServiceProvider->{closure}()
13. at call_user_func_array(object(Closure), array()) in Route.php line 157
14. at Route->runCallable(object(Request)) in Route.php line 129
15. at Route->run(object(Request)) in Router.php line 701
16. at Router->Illuminate\Routing\{closure}(object(Request))
17. at call_user_func(object(Closure), object(Request)) in Pipeline.php line 141
18. at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
19. at call_user_func(object(Closure), object(Request)) in Pipeline.php line 101
20. at Pipeline->then(object(Closure)) in Router.php line 703
21. at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 670
22. at Router->dispatchToRoute(object(Request)) in Router.php line 628
23. at Router->dispatch(object(Request)) in Kernel.php line 214
24. at Kernel->Illuminate\Foundation\Http\{closure}(object(Request))
25. at call_user_func(object(Closure), object(Request)) in Pipeline.php line 141
26. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in OAuthExceptionHandlerMiddleware.php line 19
27. at OAuthExceptionHandlerMiddleware->handle(object(Request), object(Closure)) in Pipeline.php line 125
28. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in ShareErrorsFromSession.php line 55
29. at ShareErrorsFromSession->handle(object(Request), object(Closure)) in Pipeline.php line 125
30. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in StartSession.php line 61
31. at StartSession->handle(object(Request), object(Closure)) in Pipeline.php line 125
32. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 36
33. at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in Pipeline.php line 125
34. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in EncryptCookies.php line 40
35. at EncryptCookies->handle(object(Request), object(Closure)) in Pipeline.php line 125
36. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in CheckForMaintenanceMode.php line 42
37. at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in Pipeline.php line 125
38. at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
39. at call_user_func(object(Closure), object(Request)) in Pipeline.php line 101
40. at Pipeline->then(object(Closure)) in Kernel.php line 115
41. at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 84
42. at Kernel->handle(object(Request)) in index.php line 53

Thank you !

Have you created a database named webapp in your config/database.php file and set the correct credentials?

yes, I've solved this problem. I modified database from "webapp" to "default".
oauth2.php
<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Database Connection to use
    |--------------------------------------------------------------------------
    |
    | Set the default database connection to use for the repositories, when
    | set to default, it uses whatever connection you specified in your
    | laravel database config.
    |
    */

    'database' => 'default',

    /*

Thank you again!


Delegator check box not fixed on Lead (javascript is ugly because Phil wrote it) Needs to be cleaned up.

[ ] Keep is doing too much KERI backend should push out notification to tell when its finished.
[ ] Keep is just dispatching actions based on notifications. The logic is in the KERI Rest API not in KEEP.

Phil promises to write prettier javascript 🐮


update authors and mailmap

ping @tianon
immediately regretted starting this, but then couldnt stop
i think i got em all

There is no rule the mail map is for finding duplicates not sending spam

Thanks Jess, must've been a "fun" job :)
Looks good, but I'm not familiar with the way it's used to check for possible issues. Guess that means a "lgtm".

ping @tianon ;)

immediately regretted starting this, but then couldnt stop

that feel, so much familiar
LGTM


Pane.addItem is deprecated.

Pane::addItem(item, 1) is deprecated in favor of Pane::addItem(item, {index: 1})
Pane.addItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:462:14)
StatusBar.onDropTabBar (/Users/t1k1/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:697:12)
onDropTabBar (/Users/t1k1/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:3:59)
HTMLUListElement.<anonymous> (/Users/t1k1/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:353:26)
HTMLUListElement.dispatch (/Users/t1k1/.atom/packages/platformio-ide-terminal/node_modules/jquery/dist/jquery.js:4435:9)
HTMLUListElement.elemData.handle (/Users/t1k1/.atom/packages/platformio-ide-terminal/node_modules/jquery/dist/jquery.js:4121:28)

Same error.

Same here.

Please retest again with platformio-atom-ide-terminal 2.9.0 is using node-pty-prebuilt instead unmaintained and outdated pty.js

Fixed in https://github.com/bus-stop/terminus/commit/4c4adf552586c02608d59702cec7c418691a4644


Our boss thinks flutter_ Blue is slow to connect devices on Android phones. Is there a good solution? I'm getting fired

Our boss thinks flutter_ Blue is slow to connect devices on Android phones. Is there a good solution? I'm getting fired

What do you mean slow??? It's lightning-fast, comparing to other platforms.

What?

The faster I can get to an ESP32 is 1.65Kb/s with MTU500 and Android


Save multiple attendees per account rather than associating account with one attendee

Right now, accounts have names attached and save one attendee profile, but if, for example, you generally sign up as a pair, it doesn't make so much sense for only one of you to be the primary person on the account, and never save the other person's information.
Proposal:
Remove name from user information. Just use email/password for both login and signup.
Save a collection of attendee profiles, with the ability to remove or edit them.
In attendee/pass assignment, you can use existing attendees or create new ones.

As a corollary, stored housing data should be saved as part of the attendee, not as part of the user. This will squash the idea of housemates co-editing a house's information, but that was probably unnecessary anyway.

Also related: #312


about  the  train  code

When I run the train.sh command, I noticed that different datasets require different txt files containing the image lists. Can you provide the corresponding txt files?

The error message that appears is as follows:
FileNotFoundError: [Errno 2] No such file or directory: '/user/guoxia11/cvlshare/cvl-guoxia11/IMDL/REAL/authentic.txt'

I have the same problem with @85zhanghao.Could you please provide the corresponding txt files?

I have also encountered the same problem. Can you provide the corresponding files? Thank you, my email is<EMAIL_ADDRESS>

@85zhanghao @Samarium-Z @GWZ313 sorry for the late reply. you can find txt file in this link, which is just a list of name for all training images.

Thank you for your assistance~
CHELSEA234 @.***> 于2023年10月12日周四 00:56写道：

@85zhanghao https://github.com/85zhanghao @Samarium-Z
https://github.com/Samarium-Z @GWZ313 https://github.com/GWZ313 sorry
for the late reply. you can find txt file in this link
https://drive.google.com/drive/folders/1OIUv7OGxfAyerMnmKvrNnN_5CmIDcNxo?usp=sharing,
which is just a list of name for all training images.
—
Reply to this email directly, view it on GitHub
https://github.com/CHELSEA234/HiFi_IFDL/issues/10#issuecomment-1758109170,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATDHOK4EPGLGU3U6OGZZYFLX63FT7ANCNFSM6AAAAAA3FT6JSA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Migrate view toolbar menus

The theia-trace-extension provides different toolbar buttons for the widget view (where the graphs are loaded). This is Theia specific and doesn't exist in the VsCode version.
To support the same functionality this needs to be added to the vscode-trace-extension.
First, it' needs to be investigated if it's the VsCode APIs allows it to add toolbar buttons. If yes, the functionality can be implemented using VsCode APIs. If not then the functionality needs to be added in a different way (maybe as part of the react-components).
Note: Move as much code to the theia-trace-extension repository in the Theia independent packages (traceviewer-react-components and traceviewer-base-components) for code-re-use purposes.
Trace Viewer widgets

The relevant contribution point to get toolbar items on the toolbar for a webview is the .menus.view/title contribution point with a "when": "view == <view ID>" clause.

The relevant contribution point to get toolbar items on the toolbar for a webview is the .menus.view/title contribution point with a "when": "view == <view ID>" clause.

The middle "webview" panel where the graphs are, is opened programatically and not using the contribution point. We'll have to see if we can add the menu the same way.

With recent VsCode version v1.71 (August 2022) it is possible to add conditional editor menus with activeWebviewPanelId. However, this is not supported when installing the vscode-trace-extension in Theia.
      "editor/title": [
        {
          "when": "activeWebviewPanelId == 'react'",
          "command": "<command>",
          "group": "navigation"
        }
      ]

#96 adds the reset time range button and the open overview button. The others still have to be added. Here is the list:

Undo/Redo button
Help button for short cuts
Marker menus


Mission option if behind a NAT router

In my case, the default config is not working without adding local <local ip> to /etc/openvpn/server.conf

You must be using a very old version of the installer, the local parameter has been included since the year 2019.


www.proteomicsml.org vs proteomicsml.org

Pre-issue creation checklist

[X] No duplicates of this issue have already been created.
[X] This issue does not fit any of the other categories.

Describe your issue

Links to proteomicsml.org don't work, the issue is that the www is required at the moment e.g. see

Links to https://www.proteomicsml.org/ do work. This includes www. so works OK

Suggests DNS record issue that could resolve issues
https://support.duda.co/hc/en-us/articles/4410641737239-Site-not-working-without-WWW
Additional context
No response

I followed the GitHub documentation to validate the hosting DNS settings, and it seems that the apex domain configuration (A file) is working:
❯ dig PROTEOMICSML.ORG +noall +answer -t A
proteomicsml.org.       0       IN      A       <IP_ADDRESS>

And the www subdomain variant is also working (as far as I understand):
❯ dig WWW.PROTEOMICSML.ORG +nostats +nocomments +nocmd
;WWW.PROTEOMICSML.ORG.          IN      A
www.proteomicsml.org.   0       IN      CNAME   proteomicsml.github.io.
proteomicsml.github.io. 0       IN      A       <IP_ADDRESS>
proteomicsml.github.io. 0       IN      A       <IP_ADDRESS>
proteomicsml.github.io. 0       IN      A       <IP_ADDRESS>
proteomicsml.github.io. 0       IN      A       <IP_ADDRESS>

But the AAAA setting does not return any results:
❯ dig PROTEOMICSML.ORG +noall +answer -t AAAA

@edeutsch, could you take a look at the domain hosting and check if the AAAA record is setup correctly according to the GitHub docs? Thanks!

There was no AAAA record, but I think that is only for IPV6, which I suspect is not the problem?
I fussed around with the A record but I'm not optimistic that it did anything
proteomicsml.org/publication.html
seems to work.
https://proteomicsml.org/publication.html
is a little more spotty.
Maybe testing with wget illuminates the issue?
$ wget https://proteomicsml.org/publication.html
--2022-10-07 11:13:50--  https://proteomicsml.org/publication.html
Resolving proteomicsml.org (proteomicsml.org)... <IP_ADDRESS>, <IP_ADDRESS>, 2606:50c0:8000::153
Connecting to proteomicsml.org (proteomicsml.org)|<IP_ADDRESS>|:443... connected.
ERROR: no certificate subject alternative name matches
	requested host name ‘proteomicsml.org’.
To connect to proteomicsml.org insecurely, use `--no-check-certificate'.

$ wget https://www.proteomicsml.org/publication.html
--2022-10-07 11:14:11--  https://www.proteomicsml.org/publication.html
Resolving www.proteomicsml.org (www.proteomicsml.org)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to www.proteomicsml.org (www.proteomicsml.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 45378 (44K) [text/html]
Saving to: ‘publication.html’

publication.html                   100%[===============================================================>]  44.31K  --.-KB/s    in 0.01s

2022-10-07 11:14:11 (3.19 MB/s) - ‘publication.html’ saved [45378/45378]

I'm wondering if maybe it is a SSL cert issue?
I dunno, I've always struggled with getting the root domain to work properly.

So I am seeing this:
wget http://proteomicsml.org/publication.html - redirected and works
wget http://www.proteomicsml.org/publication.html - works
wget https://www.proteomicsml.org/publication.html - works
wget https://proteomicsml.org/publication.html - FAILS

ERROR: no certificate subject alternative name matches
	requested host name ‘proteomicsml.org’.
To connect to proteomicsml.org insecurely, use `--no-check-certificate'.

I don't know how to fix.

Just a quick comment that the reason I logged this issue was that internal links within the proteomicsml.org website/tutorial etc sometimes failed to load webpages, leading to an occasional poor user experience for an awesome resource. I haven't thoroughly tested so don't know the full impact.
As a workaround while the technical issue for links without www is being resolved maybe it's possible to programatically update links to contain www. in all the instances?
I just wanted to flag this for clarity i.e. some internal links within proteomicsml.org sometimes fail due to this issue and there might be a workaround in the meantime. BW

thank you for the reports!
@RalfG would you be able to update the hyperlinks on the page https://www.proteomicsml.org/contributing.html that currently point to proteomicsml.org to point to www.proteomicsml.org instead?

After updating some of the DNS settings, it seems that the issue has been resolved. A redirect from apex to www prevented GitHub's SSL certificate system from working properly. The redirect is now managed by GitHub pages itself and @edeutsch's wget tests seem to work now.
@makingions, thanks for reporting!


Planned Changes for 0.1

This is a thread we can use to plan any changes we want to make before we say we have come to the first stable, functional version of the game.
Ideas:
Accepted Ideas:
Completed Changes:
Any changes that we think warrant further discussion should have their own threads. Let's keep this to setting goals only please.

i was thinking of getting more people on the pixel art.
obviously we cant pay them. but we need a way so we don't "have" to credit them .- maybe just asking them?
the quicker the pixel art is done the faster we can move on to actually making the game.

@prabhjot-dehal  What we need are some quick outlines to be completed (or even just a sprite that says the name of it on it) to be a placeholder while we code the game. These can be replaced and changed as we progress through. This will help us get a basic framework going and better plan where exactly we want to take this game.


Module dependencies and recursive loading modules

Basic Info

Info
Please fill out this column

Issue(s) this addresses
#180

ROS2 version tested on
Humble

Aerial platform tested on
-

Description of contribution in a few bullet points

improved load_module() method, see docs
load_module() now only loads a module if it isn't already loaded
module __deps__ attribute list its module dependencies
load_module() try to load all module dependencies too
go_to_gps new dependency gps
follow_path_gps new dependency gps
New load recursive test

Codecov Report

Merging #181 (5157c8d) into main (374c14f) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 5157c8d differs from pull request most recent head 8424ff4. Consider uploading reports for the commit 8424ff4 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@          Coverage Diff          @@
##            main    #181   +/-   ##
=====================================
  Coverage   3.21%   3.21%
=====================================
  Files         97      97
  Lines       5005    5005
  Branches     451     451
=====================================
  Hits         161     161
  Misses      4706    4706
  Partials     138     138

Flag
Coverage Δ

unittests
3.21% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Can't pretty-print Object.create(null)

Repro steps:
Run the following test in https://benchristel.github.io/try-taste/:
"compares objects with no prototype"() {
    expect(Object.create(null), equals, Object.create(null))
},

Taste crashes with an error t.__proto__ is undefined.

This is fixed in 0.2.1.


Box: Allow zero padding overrides

We currently do not allow for padding to be overwritten when hitting a breakpoint (we do for margin). This is an issue for responsive designs, where we do want that flexibility.
Test Plan

Enter the following code in the playground

<Box
  padding={2}
  mdPadding={0}
  color="green"
>
  <Box width={40} height={40} color="red" />
</Box>

Expected: on small screens we show a padding, on bigger screens we remove the padding

Before

After

@ayeshakmaz updated to propNameHasSecondRow


fix: DevCard component first contribution date format

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description

This PR fixes the date format of the first contribution day on the DevCard component. The initial set-up displays the date in days.
// insights/components/molecules/DevCard/dev-card.tsx
{props.age !== undefined && (

    ...

{props.age}d

)}

This fix leverages the getRelativeDays date utility function as there's a need to address first contributions that are day, month up to year old
// insights/components/molecules/DevCard/dev-card.tsx
{props.age !== undefined && (

    ...

      {getRelativeDays(props.age)}

)}

Related Tickets & Documents

fixes #1317
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
NA
[optional] What gif best describes this PR or how it makes you feel?

@babblebey can you add a before and after screenshot?

LGTM

@babblebey can you add a before and after screenshot?

Done @bdougie


Date-time strings do not contain offset part

Description
As per https://datatracker.ietf.org/doc/html/rfc3339#section-5.6 which is the notation mandated by openapi's date-time format, the date time strings should always contain timezone offset part.
Specmatic generates date-time strings without offset information: e.g. 2023-09-01T14:37:25.347356
Steps to reproduce

define a parameter of type date-time:

schema:
  type: string
  format: date-time

2.run tests
Expected behavior
A valid RFC 3339 date-time string should be generated (for example by appending Z at the end or by appending time offset based on current TZ)

I am encountering the same problem myself. I use the OpenAPI go generator to generate a client SDK and it will parse the generated date-time values with the time.RFC3339 by default.
I tried to look for a way to tell specmatic what value to generate for that one field but it seems that expectations can only be set at the request-response level.

@yntelectual Thanks for reporting the issue. It is indeed a good issue to address. We are bumping this up in our backlog.

@attard-divido Thanks for adding to this thread. Can you please elaborate if you are running your OpenAPI specifications as test or as stub?

@attard-divido Thanks for adding to this thread. Can you please elaborate if you are running your OpenAPI specifications as test or as stub?

Thank you for your reply. I've only tried OpenAPI spec as stub for now. I cannot comment on OpenAPI spec as test for now.

@yntelectual @attard-divido @DapperMongoose Thank you for your patience on this. We have fixed this issue and the same should be part of our upcoming release.


Remove --name flag from helm installation command

As this answer succinctly captures from the Helm v3 docs, the --name tag is no longer used.

Because failed the sign-off test