MRTK Demo Scenes not preconfigured with Profiles

Describe the bug
Opening any MRTK v2 Eye Tracking example demo scene, (reproducible with the Assets/MixedRealityToolkitExamples/Demos/EyeTracking/Scenes/mrtk_eyes_02_TargetSelection.unity, or MRTK_eyes_03_Navigation.unity, or any other demo scene) opens a dialog that says "No Active Toolkit Found." You must select the correct Configuration Profile for the Eye Tracking scene, in this case, "EyeTrackingDemoConfigurationProfile," if it is in the list. If it is not in the list, you can clone a preconfigured Default configuration, but with this configuration, the scene will not build to a working demo, because the configuration does not fulfill all requirements.
To reproduce
Steps to reproduce the behavior:

With Unity Hub, create a New Project, name it and give it a location, select Unity 2018.3.14f1
Import the MRTK v2 Foundation as a custom package (v2.0.0-RC1-Refresh)
Import MRTK v3 Example as a custom package (v2.0.0-RC1-Refresh)
Navigate to Assets/MixedRealityToolkitExamples/Demos/EyeTracking/Scenes and open "mrtk_eyes_02_TargetSelection.unity"
Press the import button on the dialog about Text Mesh Pro
See error dialog about "No Active Toolkit Found" "There is no active Mixed Reality Toolkit in your scene. Would you like to create one now?"
You must circle-select a Configuration Profile that is the correct profile for your scene, in this case "EyeTrackingDemoConfigurationProfile," if it is in the list.
Alternatively: If the MRTK v2 packages are imported in the wrong order (Examples before Foundation), the profiles will not show up in this list. Then the developer must clone and configure a new Input System Settings / Input System Profile.

Expected behavior
Mixed Reality Toolkit should already be in the Eye Tracking demo scenes with "EyeTrackingDemoConfigurationProfile" already configured.
Screenshots

Your Setup

Unity Version: 2018.3.14f1
MRTK Version: v2.0.0

Target Platform

HoloLens 2

I don't think that any of the eye scenes #1-5 are designed to actually be opened up directly themselves, and that this is an artifact of the level of support for multi scene work.
@sostel, I believe the only supported way of using these scenes is to open the root scene. Can you comment on what you expect here? We should have a README in this folder (in addition to some doc updates here) to give some instructions on how to use these scenes.

This is by design. There's a base ET scene, while the rest are designed to be loaded additively. This information can be found in the ET Examples documentation: https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/EyeTracking/EyeTracking_ExamplesOverview.html#setting-up-the-mrtk-eye-tracking-samples

+1 to what Kurtis said.
It would probably be good to add some info text that is only rendered in the Editor to let the user know to load the root scene.
Why did we do it like that? This was mainly due to the circumstance that MRTK did not handle switching scenes using the default scene loader. Loading scenes additively worked though.

Checked again and single scene loading is still not supported. Please also see here: #4530

Just to conclude: The scenes are still set up as additive loading, but I've added some instructions to the sub scenes to make it more clear that the base scene has to be loaded.


[BUG] ism query triggers stream of StackOverflowError errors - hangs server

Describe the bug
I applied some ISM conditions to various indexes.  Now whenever I do almost any ISM operation the server spews a steady stream of StackOverflowError messages and needs to be killed with SIGKILL to stop.
To Reproduce
Steps to reproduce the behavior:

curl -X GET "https://SERVER/_plugins/_ism/explain/beat-"

Expected behavior
Return information about the indexes.
Plugins
[2022-07-05T13:49:00,844][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-alerting]
[2022-07-05T13:49:00,845][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-anomaly-detection]
[2022-07-05T13:49:00,845][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-asynchronous-search]
[2022-07-05T13:49:00,845][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-cross-cluster-replication]
[2022-07-05T13:49:00,846][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-index-management]
[2022-07-05T13:49:00,846][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-job-scheduler]
[2022-07-05T13:49:00,847][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-knn]
[2022-07-05T13:49:00,847][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-ml]
[2022-07-05T13:49:00,848][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-notifications]
[2022-07-05T13:49:00,848][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-notifications-core]
[2022-07-05T13:49:00,849][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-observability]
[2022-07-05T13:49:00,849][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-performance-analyzer]
[2022-07-05T13:49:00,850][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-reports-scheduler]
[2022-07-05T13:49:00,850][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-security]
[2022-07-05T13:49:00,851][INFO ][o.o.p.PluginsService     ] [os-sea01.nwra.com] loaded plugin [opensearch-sql]

Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: Almalinux 8.6
Version: 2.0.1

https://forum.opensearch.org/t/opendistro-1-13-2-to-opensearch-1-2-4-migration-issues/8747
os.log

Thanks for reporting this.
In ISM explain API, we are checking whether the caller has managedindex permission (doc) in a recursive way across all the explained indices one by one.
https://github.com/opensearch-project/index-management/blob/main/src/main/kotlin/org/opensearch/indexmanagement/indexstatemanagement/transport/action/explain/TransportExplainAction.kt#L377-L382
So if the caller doesn't have that managedindex permission to many of explained, due to the poorly written recursive way, we suspect it causes this stack overflow exception.

Looks like this previously reported issue is similar to this https://github.com/opensearch-project/index-management/issues/414
few more details on the security plugin exception, code points and stack trace added in the above issue.

Thanks @petardz for fixing this!


How can I get gsm-gpl relation in multi-gpls gse.

Thank you for great project. It is very convenient to me.
My interested dataset has multi-GPLs GSE. I want to find specific GPL's samples. But I can not find where the relations are.
In this case,
>>> gse = GEOparse.get_GEO("GSE6532", destdir='data/',
            annotate_gpl=True, include_data=True, silent=True)
>>> print(gse.gpls)
{'GPL570': <PLATFORM: GPL570>,
 'GPL96': <PLATFORM: GPL96>,
 'GPL97': <PLATFORM: GPL97>}
>>> print(len(gse.gsms))
741

How can I filter GPL570's samples?

Hi,
Relations are stored in the metadata attribute called "platform_id" for each gsm. From there you can build a mapping eg.
import GEOparse
gse = GEOparse.get_GEO("GSE6532", destdir='.', annotate_gpl=True, include_data=True)
for gsm_name, gsm in gse.gsms.iteritems():
    print gsm_name, gsm.get_metadata_attribute("platform_id")

GSM151199 GPL97
GSM151198 GPL97
GSM151195 GPL97
...
GSM151342 GPL570
GSM151227 GPL97
GSM151339 GPL570
GSM151338 GPL570

Best

I didn't think that would be in metadata_attributes.
Thank you for great project!
Regards,
Hyungyong Kim


Use import() instead of require.ensure for async split

https://webpack.js.org/guides/code-splitting-async/

Thanks for the PR. I've currently been holding off due to https://github.com/webpack/webpack/issues/4636#issuecomment-301920118, but will take another look through related discussions and see if there's been any improvement.

I believe you can consider this now @davezuko :)


Get travis to deploy to GitHub Releases

@jayfor-lang/developers anyone know how to do this?

GitHub Releases just work on tagging, no? So Travis-CI isn't really related. Just use tags properly and Releases will work fine.
Also note from the link above that you can retroactively tag commits, if you want to add a few version points to past commits. Don't forget to use semantic versioning.

I have no idea how it works, but you can setup Travis to deploy binaries to your releases section of your GitHub, unless GitHub already does this, but I don't think it does, eh?

Ah. Well you can just add a simple HTTP POST with the binary, but Travis makes it easy.


Use java.time instead of joda.time

Er zit nog een probleem in het testen "BetweenTimestamps".
Volgens mij heeft dit te maken met de manier waarop timestamps worden geconverteerd naar strings en de strings worden vergeleken met <= en >=
Ik heb gekozen om ZonedDateTime te gebruiken omdat deze het dichts bij DateTime zit qua implementatie.

Could you do this pull-request for the 'axon-3.x' branch? This is a major api change and shoukd be included in the next major release.
In 3.x, timestamps will be represented using a long (millis since epoch) by default.

I can. I have it ready, but using strings with timezone.
Are timezones obsolete in 3.x, for timestamps? Using UTC all the way?

For Axon 3, the default will be a long (millis since epoch). A 'legacy mode' will be available to keep support for the 2.x storage format. There, it is best to have the TimeZone configurable.
On Sat, May 23, 2015 at 11:27 AM, Roald Bankras<EMAIL_ADDRESS>wrote:

I can. I have it ready, but using strings with timezone.
Are timezones obsolete in 3.x, for timestamps? Using UTC all the way?
Reply to this email directly or view it on GitHub:
https://github.com/AxonFramework/AxonFramework/pull/144#issuecomment-104872906

Sounds really good, but I guess I don't have the feeling voor de code-base to make that change happen.

I agree that the step of switching to longs is another step. For now, ISO8601 strings are fine. Can you switch the PR to merge with the axon-3.x branch?
Thanks!


Implement big red button

Requirement: Easy way to stop any requests from being made to the matrix service.
Unresolved: Should we cancel all currently running lambda/batch jobs?

Script that makes the bucket private and disables all the lambdas. Undeploy the API stage.  Validate with Tony.


[#29317] [$1000] Double click enter to select value on pronouns and timezone edit pages navigates "back" twice

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

Action Performed:

Go to avatar > settings > profile > pronouns
Search for a value that matches i.e "He / Him"
Double tap enter to select the value
Observe you're navigated back to the Settings page (i.e two pages in the nav stack)

Note: Same results on the timezone edit selection page.
Expected Result:
Use should only navigate back the one page in the nav stack when making a selection on the edit page.
Actual Result:
"Multi-tapping" is recognised and navigates back as many pages as you press enter. E.g twice = two pages, three times = three pages etc.
Workaround:
unknown
Platforms:

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

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[X] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.47-3
Reproducible in staging?: Y
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43995119/400af392-12ad-4ced-9220-681b9b876da6
Expensify/Expensify Issue URL:
Issue reported by:  @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690794214667299
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01fd11cd8ee50c8dff
Upwork Job ID:<PHONE_NUMBER>344474112
Last Price Increase: 2023-08-14
Automatic offers:

huzaifa-99 | Contributor | 26238925

Proposal
Please re-state the problem that we are trying to solve in this issue.
Double enter click to select value on pronouns and timezone navigates user to main page/main settings page
What is the root cause of that problem?
https://github.com/Expensify/App/blob/024d210bc0b5a0454b62a72de60057af67cdd045/src/components/SelectionListRadio/BaseSelectionListRadio.js#L190-L205
When click Enter key, its calling callback of useKeyboardShortcut every times.
Some components are doing update action on clicking Enter key and trying to run Navigation.goBack. So its trying to go back everytimes.
What changes do you think we should make in order to solve the problem?
Wrap callback of useKeyboardShortcut by _.debounce
    useKeyboardShortcut(
        CONST.KEYBOARD_SHORTCUTS.ENTER,
        _.debounce(() => {
            const focusedOption = flattenedSections.allOptions[focusedIndex];

            if (!focusedOption) {
                return;
            }

            props.onSelectRow(focusedOption);
        }, 500),
        {
            captureOnInputs: true,
            shouldBubble: () => !flattenedSections.allOptions[focusedIndex],
        },
    );

What alternative solutions did you explore? (Optional)
N/A

Ah, this got assigned to me while I was OoO. Sorry for the delay! I can reproduce this one on desktop as well, so ticked that platform off and removed the needs reproduction label.
I'd quite like an opinion from @mountiny on the expected result here. I don't really see the real world use of "multi-tapping" enter to go back multiple pages in the nav stack, whether that be two, three or ten pages. So IMO, we should just go back the once (because that's the behaviour after the selection on the page you're pushed to). What do you think?

Bump @mountiny, maybe @shawnborton you have an opinion on this one as well. :)

"App should go back once on twice enter click to select value on pronouns or timezone page" - I don't think I understand what this means?

😅 TL;DR
If you're a few pages deep in the nav, open up a push to page edit screen. "double tap" enter to select the value and it will navigate you back two pages in the app stack. If you triple tap, it goes back three pages etc.
IMO, we should just go back the once (because that's the behaviour after the selection on the page you're pushed to) however gung-ho you are with the enter button to make the selection.

Got it. Yup, I agree with that.

Cool, nice! Updated the OP to reflect that and moved this on.

Here is my Updated Proposal

@parasharrajat I added some explanations

@parasharrajat Please check updated proposal

LEts make sure the solution is applied to any place we navigate after enter ideally

debouncing was that I already proposed in the beginning.

@mountiny, does this work for you? https://github.com/Expensify/App/issues/24074#issuecomment-1684143811

Sounds good to me

Cool, updated the title to reflect that!

@parasharrajat https://github.com/Expensify/App/pull/29317 has been closed. What's the deal now?

Bump @parasharrajat? https://github.com/Expensify/App/issues/24074#issuecomment-1823025176

@parasharrajat can we close this? Whatever we're waiting on is super unclear and it's low value, so I vote we just close it.

@huzaifa-99 are you able to address the comments in the PR next week?

👋 Can we get an update on this, please? Thanks!

@huzaifa-99 there are conflicts in the PR to resolve. :)

What's going with this PR? It hasn't been touched for over a month and it has a bunch of conflicts.

How'd that go?

Wowie, 👴 shots from the past

@huzaifa-99 QA mentioned that some parts of this bug were not resolved https://github.com/Expensify/App/pull/25604#issuecomment-2139412505

👋 checklist time!

@huzaifa-99 @parasharrajat can you bring the discussion back here from the PR please, what are the next steps?

Any luck?

@parasharrajat have you got around to this?

@huzaifa-99 how are you getting on here?

Merged, lets be on a look out to verify correct behaviour here, thanks!

Is this not on prod yet? 😕

I believe it just got deployed to production

Checklist time!

Okay and confirming one regression?

I am fine with keeping the full price on this one. This issue was created in August 2023, and it's been a long battle. There were regressions and I think we are still trying to find the ideal solution, but @huzaifa-99 's solution got us into a better place and it was lots of work and effort to do so $1000 seems fair.

For the regression tests, I think we just need one page like PronounsPage -> /settings/profile/pronouns and make sure the tester clicks really fast to see if the page opens/ navigates mulitple times.
I dont think its viable to test all these pages

Alright, so payment summary as follows:

$1,000 to @parasharrajat for the C+ review (go ahead and request)
$1,000 to @huzaifa-99 for the fix (offer sent!)

As for the regression test, I agree with suggesting 1. Can you make this more readable and standardised in a format of numbered steps that a tester can repeatably follow if we were to add this to TestRail, @parasharrajat?

But I can't list down steps for each page as each has separate functionality.

I thought we agreed on just the one, so we can focus on pronouns or something?

I think we just need one page like PronounsPage -> /settings/profile/pronouns

Cool done, closing!

Hi @trjExpensify, @mountiny, @parasharrajat is this issue eligible for reporting bonus?

Oh yeah, this is old and I didn't spot the reportedBy. So yes, I believe this is still eligible for $50 for the bug report. Are you still on Upwork?

Thanks @trjExpensify, Yes I am still on upwork, here is my profile link
https://www.upwork.com/freelancers/~016c7b8ae165dc0bda
Actually the issue was created before 31st August 2023 (the deadline after which we changed reporting bonus from 250 to 50 dollars) but at this stage of the project, I will be happy with whatever you decide.

Yep, that makes sense. We honour those.
Payment summary as follows:

$250 to @dhanashree-sawant for the bug report

Offer sent!

Many Thanks @trjExpensify, I have accepted the offer.

Paid, closing.

$1,000 approved for @parasharrajat


Customize adapter

It will be really great if we can set something depending on lines.
For example: at Gitskarios i'm gonna use this lib to show content, and commits diff, so sometimes i need to add comments in a line

Implemented in 1.1.0.

Great!
Please, update README with adapter customization 🎉

Updated. I also added a Github diff (custom adapter) as nice use case in library, so you can see usage in README and how it looks in screenshots.

:tada: great!


Fixing setup.py

Closes #21.

Coverage remained the same at 90.93% when pulling 7bc4d118a1c6c30aff45f8845ac1226316680651 on fix-setup into 071de5b8fd8045559af73387f6615aa013a892f8 on master.


DSC v6.3.2 provider and consumer POST /api/ids/description

I am trying to manage a communication between DSC provider and consumer for a “localhost” setup with the DSC version 6.3.2. I am having problems with the POST /api/ids/description call of the API on consumer side requesting provider self description.
I have used Fraunhofer certificates, the latest version of the DSC and the following docker-compose file:

version: '3.5'
services:
provider:
image: ghcr.io/international-data-spaces-association/dataspace-connector:latest
ports:
- 8080:8080
networks:
- local
volumes:
- ./config_provider.json:/config/config.json
- ./testidsa9.p12:/conf/testidsa9.p12
environment:
- SERVER_SSL_ENABLED=false
- CONFIGURATION_PATH=/config/config.json
restart: always
consumer:
image: ghcr.io/international-data-spaces-association/dataspace-connector:latest
ports:
- 8081:8080
networks:
- local
volumes:
- ./config_consumer.json:/config/config.json
- ./testidsa10.p12:/conf/testidsa10.p12
environment:
- SERVER_SSL_ENABLED=false
- CONFIGURATION_PATH=/config/config.json
restart: always
networks:
local:
driver: bridge

PROVIDER steps carried out

Offer:  POST /api/offers
{
"title": "Sample Resource",
"description": "This is an example resource containing weather data.",
"keywords": [
"weather",
"data",
"sample"
],
"paymentModality": "fixedPrice",
"publisher": "https://openweathermap.org/",
"language": "EN",
"license": "http://opendatacommons.org/licenses/odbl/1.0/",
"sovereign": "https://openweathermap.org/",
"endpointDocumentation": "https://example.com",
"key": "value"
}

http://localhost:8080/api/offers/e0724fbf-fd3a-45a3-969b-dd4ae513cda0

Catalog: POST /api/catalogs
{"title": "Example Catalog", "description": "This is an example catalog containing weather data"}
http://localhost:8080/api/catalogs/62af5255-3515-42c1-a4a6-838e8cacc1b6

Add the resource to the catalog -> POST /api/catalogs/{id}/offers

Rule: POST /api/rules
{"title": "Example Rule Provide Access", "description": "This is an example rule containing a provide access usage policy", "value": "{ "ids" : "https://w3id.org/idsa/core/\", "idsc" : "https://w3id.org/idsa/code/\"},\"@type\": "ids:Permission", "@id": "https://w3id.org/idsa/autogen/permission/1c680cc6-3d64-4cbe-9508-b32681bc6c33\", "ids:description": [ { "@value": "provide-access", "@type": "http://www.w3.org/2001/XMLSchema#string\" } ], "ids:title": [ { "@value": "Allow Data Usage", "@type": "http://www.w3.org/2001/XMLSchema#string\" } ], "ids:assignee": [], "ids:assigner": [], "ids:postDuty": [], "ids:constraint": [], "ids:action": [ { "@id": "idsc:USE" } ], "ids:preduty": []}"}

http://localhost:8080/api/rules/6255e3e6-f8ae-45b2-b850-161bbb8efb86

Contract: POST /api/contracts
{"title": "Contract","description": "This is an example contract","provider": "http://localhost:8080/","start": "2021-10-21T09:23:13.239Z","end": "2023-10-21T09:23:13.239Z"}
}
http://localhost:8080/api/contracts/263c8c58-2e04-4ed0-b381-2d139451c069

Add the rule to the contract -> POST /api/contracts/{id}/rules

Artifact: POST /api/artifacts
{"title": "Example Artifact","value": "Hello World","automatedDownload": true}

http://localhost:8080/api/artifacts/8c8a102d-5eed-4cbd-8563-ff0211f38cba

Representation: POST /api/representations
{"title": "Example Representation"}

http://localhost:8080/api/representations/afb9fb7b-d99b-48e5-91d9-808edcb0f2e1

Add the artifact to the representation -> POST /api/representations/{id}/artifacts
Add the representation to the resource -> POST /api/offers/{id}/representations
Add the contract to the offer -> POST /api/offers/{id}/contracts

CONSUMER steps
Message description: POST /api/ids/description
http://provider:8080/api/ids/data
Element ID empty
Response body: OK

{
"@context" : {
"ids" : "https://w3id.org/idsa/core/",
"idsc" : "https://w3id.org/idsa/code/"
},
"@type" : "ids:BaseConnector",
"@id" : "http://provider.com",
"ids:version" : "6.3.2-SNAPSHOT",
"ids:description" : [ {
"@value" : "IDS Connector with static example resources hosted by the Fraunhofer ISST",
"@type" : "http://www.w3.org/2001/XMLSchema#string"
} ],
"ids:title" : [ {
"@value" : "Dataspace Connector",
"@type" : "http://www.w3.org/2001/XMLSchema#string"
} ],
"ids:hasDefaultEndpoint" : {
"@type" : "ids:ConnectorEndpoint",
"@id" : "https://w3id.org/idsa/autogen/connectorEndpoint/4c8ae983-13de-4a7b-af55-1debb0e65777",
"ids:endpointDocumentation" : [ ],
"ids:accessURL" : {
"@id" : "http://provider:8080/api/ids/data"
},
"ids:endpointInformation" : [ ]
},
"ids:hasEndpoint" : [ ],
"ids:resourceCatalog" : [ {
"@type" : "ids:ResourceCatalog",
"@id" : "http://provider:8080/api/catalogs/62af5255-3515-42c1-a4a6-838e8cacc1b6",
"ids:offeredResource" : [ ],
"ids:requestedResource" : [ ]
} ],
"ids:hasAgent" : [ ],
"ids:securityProfile" : {
"@id" : "https://w3id.org/idsa/code/BASE_SECURITY_PROFILE"
},
"ids:extendedGuarantee" : [ ],
"ids:maintainer" : {
"@id" : "https://www.isst.fraunhofer.de/"
},
"ids:curator" : {
"@id" : "https://www.isst.fraunhofer.de/"
},
"ids:inboundModelVersion" : [ "4.2.0", "4.1.2", "4.2.1", "4.0.0", "4.1.0", "4.2.2", "4.2.3" ],
"ids:outboundModelVersion" : "4.2.3"
}

Message description: POST /api/ids/description
http://provider:8080/api/ids/data
http://provider:8080/api/catalogs/62af5255-3515-42c1-a4a6-838e8cacc1b6
Response body: NOK
I am receiving the following:

This is the response in the terminal of provider DSC:

This is the response in the terminal of consumer DSC:

I am not obtaining the offered resource of the provider DSC, so I am not able of doing Step 2: Query Provider - Request Resource Metadata
https://international-data-spaces-association.github.io/DataspaceConnector/CommunicationGuide/v6/Consumer#step-2-query-provider---request-resource-metadata
Is there something wrong with my deployment or the followed steps? Or is it a problem with this version of the DSC?
Thanks in advance,

Please use our official Docker image v6.5.0. Does the problem still exist?


Attitude with Entity that spawn with exEntitySpawner.SpawnRecord is broken

When you try to make aggressive an entity that have been spawned with exEntitySpawner.SpawnRecord, it will not attack you.
it show it as Hostile, red color and all, but its just turn around you without attack.
Same TweakDB record spawned with preventionSystem works perfectly so I assume it's related to exEntitySpawner.SpawnRecord.

This part of code was made by @0xSombra and I have a feel it is bit of a white box. Hope they'll react in some way.


SingleChoice Dialog no checkbox placeholders except selected one

[x] I have verified there are no duplicate active or recent bugs, questions, or requests
[x] I have verified that I am using the latest version of Material Dialogs.
[x] I have given my issue a non-generic title.
[x] I have read over the documentation (before asking questions on how to do something).

Include the following:

Material Dialogs version: <IP_ADDRESS>
Device OS version: 7.1.1
Device Manufacturer: Google
Device Name: Nexus 5X

mDialog = new MaterialDialog.Builder(getContext())
                .title(R.string.sort_type_title)
                .items(sortTypes)
                .itemsCallbackSingleChoice(0, (dialog, itemView, which, text) -> {
                    Utils.doToast(getContext(), "test");
                    return true;
                })
                .show();

I have single choice dialog with multiple items. I remember that the last time the I used it, checkbox's placeholders were shown. Now only the selected one is shown but the others don't have a placeholder, it's just a text.

Hmmm, I haven't experienced this problem before.

Unable to reproduce.

Adding #ffffff - white color, in the theme, will cause this bug. Turns out this will change the color of the unselected items in the dialog.


Custom semantic validation

This is fairly closely related to #139 and is another good thing to keep in mind as you're walking through the code thinking about documentation, but I figured it deserves its own issue.
The documentation in #139 would essentially create a Swagger styleguide, but different organizations often have customized styleguides. Consider, for example, GitHub vs jQuery javascript styleguides, or the many configuration options for Rubocop.
I think it would be great if organizations can start with the built-in semantic rules for validating their Swagger docs, but can tweak the validation via parameters or by registering their own javascript callbacks.
A simple example - validating the operation "summary" based on OpenStack conventions:

It should be in sentence case (e.g. "Create server", not "Create Server" or "create server")
It should be short, perhaps even shorter than the minimum suggested by Swagger (e.g. 80 vs 120 characters)

Not something that needs to be done soon, but something to keep in mind if you need to revisit the validation code.

I'm not against this but I have to tell you, semantic validation isn't really a style.  Either your Swagger document is valid per the documented specification or it is not, there is not any gray area.  I do think we could extend the plan behind #28 (semantic validation for vendor extensions) and figure out a way to use that same process to register style checkers.  Thoughts?

tl;dr: "API Warnings" in the current output are a gray area and are more closely related to style guides than to a strict specification. They are associated with suggestions rather than absolute requirements in the Swagger specification.
I somewhat agree, but I think the warnings that you already implemented for https://github.com/apigee-127/swagger-tools/issues/1 are really style rules. The check for "API operation summary is greater than 120 characters" is a great example.
In general I think semantic validation against the specification, a vendor extension, a custom rule, or a style guide are just variations of the same general concept. You might want to keep track of which standard you're validating but they should all share pretty much the same validation mechanism. I'll just refer to them generically as "checkable rules".
I think the most important thing is really the requirement level. The top of the Swagger specification says it uses the keywords for requirement levels defined in RFC 2119. Those keywords are:

Absolute requirements: MUST, MUST NOT
Suggested requirements: SHOULD, SHOULD NOT
Optional requirements: MAY, OPTIONAL

It's pretty easy to map these keywords to "error" and "warning" level errors for a checkable rule. Since the specification contains some suggested requirements there are some "gray areas. The requirement "this field SHOULD be less than 120 characters" is a good example.
A styleguide or organizations specific standards would probably be mostly suggest requirements or "warning" level validation errors, but it is possible for them to have absolute requirements as well. The Swagger specification requires a license but does not limit the choices. A specific organization may have a set of approved licenses or even just a single license used by the entire organization. So an organization may want to enforce the rules: "The license name MUST be 'Apache 2.0'. The license url MUST be 'http://www.apache.org/licenses/LICENSE-2.0.html'"
I do think it may be useful to group validation errors by type, but mostly for summarizing the results for the users. I think tools should be more concerned with error levels than error types. If I was setting up a CI build to screen changes to a Swagger document before merging a PR, I would set it up to fail changes that introduce errors of any type, but would probably allow warnings.
So I think they should all work the same, but you might want to capture the type (basically the document a rule is associated with) so you could display a summary that looked something like this:
$ swagger-tools validate OS-KSS3-admin.json

Swagger Errors:

  #/paths/~1v2.0~1users~1{userId}~1OS-OS-KSS3~1credentials~1s3credentials~1{type}/get: API requires path parameter but it is not defined: type

OpenStack Conventions for Swagger Errors:

  #/license/name: License must be Apache 2.0

Enhanced Examples Extension Errors:

  #/paths/~1v2.0~1users~1{userId}~1OS-OS-KSS3~1credentials~1s3credentials~1{type}/get/x-examples[3]/request: Example does not comply with the request schema

Swagger Warnings:

  #/definitions/Pet: Definition is defined but is not used: #/definitions/Pet

3 errors and 1 warning

I get your point.  Warnings are there (now) to tell you that you've either violated the Swagger Specification in some way that does not have a real impact on the API, like the summary length exceeding 120 characters, or to warn you that you might had made a mistake, like defining a model and not referencing it.  I don't think those are stylistic but I also can see why someone might want to impose some style checks so I'm not disagreeing with you on the benefit of having it.

By the way, checkout the new Swagger Validation part of the documentation.  It's a work in progress but it gives you an idea of what semantic validations occur.  I'll start looking into extendible/configurable validations soon.

@maxlinc If you look at the link above, you'll see the validations I'm manually doing.  Do you mind telling me which validations you'd like to change or have it be configurable to have their type changed?
As for fully customizable semantic validation, to me that means registering extra validators and that sounds very similar to #28.  I'd love your opinion on how you'd see this done.  I'm all for implementing this and #28 together but I would really like to know how you'd like to see the consumption side of this.

I have moved #28 to this.  I think if we create a validation framework of sorts where people can opt-in to the validation of document paths, we can solve both this and the need for vendor extension validation.

Thanks. Everything looks good so far.

I'm in the process of designing this right now and I was wondering how you'd want to use something like this.  How would you expect to register a validator and ensure that the validator only runs against the appropriate locations in the document, or do you see a different usage model?  I've got some ideas but of course you're the user so I'd love any feedback you have.

What about something like this:
registerValidator(someRegex, function (node, parent, root) {
  // Do your validation here
});

someRegex would be a regular expression that is matched against the JSON Pointer equivalent of the path to the node being processed.  So for the get operation of the /pets path, your someRegex regular expression would be applied to #/paths/~1pets.
The idea would be having a way to process a node, check to see if the node has any registered/matching validators and then invoke the validator(s) only if necessary.  Document node name would not be enough and so that's why I was thinking of a regular expression.  I guess we could use a glob for something simpler as well.


chore: bring in more template dev tooling

Fixes #3.
Most of this tooling comes from https://github.com/JoshuaKGoldberg/template-typescript-node-package. I tried to list the main things in DEVELOPMENT.md. The documentation is shuffled a bit to focus on Next.js before the myriad of other tools. If anything is missing from the docs, we should add it in!
LMK if any of these tools aren't apparent, I'm very open to changing this around!

@allcontributors add @JoshuaKGoldberg for content ideas maintenance platform projectManagement tool

@allcontributors add @blackgirlbytes for content ideas maintenance platform projectManagement tool

@allcontributors add @JoshuaKGoldberg for content ideas maintenance platform projectManagement review tool

@allcontributors add @blackgirlbytes for content ideas maintenance platform projectManagement review tool


Long text in picker not wrapping to next line in android and the selected text doesn't wrap in either android/ios

I have gone through these following points

[x] Check latest documentation: https://docs.nativebase.io/
[x] Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x] Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[] Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[] For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[] For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description
I am using Picker from React https://docs.nativebase.io/Components.html#picker-def-headref but I have long text in the list which gets truncated on both ios and android after selection whereas on the picker it gets truncated on android. I have tried flexWrap, flexShrink but they don't help. I have latest react native and native base versions.
Expected behaviour
Text should wrap to new line in case of lengthy text
Actual behaviour
Text gets truncated
Steps to reproduce
I created a simple Picker with two picker options from documentation:
import React, { Component } from "react";
import { Container, Header, Content, Picker, Form } from "native-base";
export default class PickerExample extends Component {
constructor(props) {
super(props);
this.state = {
selected: "key1"
};
}
onValueChange(value: string) {
this.setState({
selected: value
});
}
render() {
return (

<Picker.Item label="Wallet" value="key0" />
<Picker.Item label="LongTextLongTextLongTextLongTextLongTextLongTextLongTextLongTextLongTextLongTextLongTextLongTextLongText" value="key1" />

);
}
}
Screenshots:-
Picker on ios(Text gets wrapped to next line as expected)

Selected value on ios(Text gets truncated)

Picker on android(Text gets truncated)

Selected value on android(Text gets truncated)

Is the bug present in both iOS and Android or in any one of them?
both

Hi @Aayushi1301 , Text is supposed to be truncated on both iOS and android after selection whereas on the picker it gets truncated on android because its Native behavior is inherited from 'react-native'.


Chart skeletons

Fixes #901
This PR adds chart skeleton UI components for the fallback/loading components for analytics charts.
These changes follow the skeleton approach used for QR codes in the app where it uses the clouds class for styling.
The dimensions for each skeleton component were sourced from the underlying dimensions in @/components/charts for each corresponding chart component.
Note that in order to test this locally, I had to apply the following patch to disable SSR to really see the skeletons load. Without this, the real chart components seemed to be loaded via SSR and I never saw the fallback/loading component in the browser.
diff --git a/pages/referrals/[when].js b/pages/referrals/[when].js
index 4748910..cf5b997 100644
--- a/pages/referrals/[when].js
+++ b/pages/referrals/[when].js
@@ -14,7 +14,8 @@ import { whenToFrom } from '@/lib/time'
 import { WhenComposedChartSkeleton } from '@/components/charts-skeletons'

 const WhenComposedChart = dynamic(() => import('@/components/charts').then(mod => mod.WhenComposedChart), {
-  loading: () => <WhenComposedChartSkeleton />
+  loading: () => <WhenComposedChartSkeleton />,
+  ssr: false
 })

 const REFERRALS = gql`
diff --git a/pages/rewards/[...when].js b/pages/rewards/[...when].js
index 43ce346..b27a654 100644
--- a/pages/rewards/[...when].js
+++ b/pages/rewards/[...when].js
@@ -12,7 +12,8 @@ import { dayMonthYear } from '@/lib/time'
 import { GrowthPieChartSkeleton } from '@/components/charts-skeletons'

 const GrowthPieChart = dynamic(() => import('@/components/charts').then(mod => mod.GrowthPieChart), {
-  loading: () => <GrowthPieChartSkeleton />
+  loading: () => <GrowthPieChartSkeleton />,
+  ssr: false
 })

 export const getServerSideProps = getGetServerSideProps({
diff --git a/pages/rewards/index.js b/pages/rewards/index.js
index ff97768..53e3d1a 100644
--- a/pages/rewards/index.js
+++ b/pages/rewards/index.js
@@ -22,7 +22,8 @@ import { useData } from '@/components/use-data'
 import { GrowthPieChartSkeleton } from '@/components/charts-skeletons'

 const GrowthPieChart = dynamic(() => import('@/components/charts').then(mod => mod.GrowthPieChart), {
-  loading: () => <GrowthPieChartSkeleton />
+  loading: () => <GrowthPieChartSkeleton />,
+  ssr: false
 })

 const REWARDS_FULL = gql`
diff --git a/pages/stackers/[when].js b/pages/stackers/[when].js
index 453fbc0..e11e45d 100644
--- a/pages/stackers/[when].js
+++ b/pages/stackers/[when].js
@@ -10,13 +10,16 @@ import PageLoading from '@/components/page-loading'
 import { WhenAreaChartSkeleton, WhenComposedChartSkeleton, WhenLineChartSkeleton } from '@/components/charts-skeletons'

 const WhenAreaChart = dynamic(() => import('@/components/charts').then(mod => mod.WhenAreaChart), {
-  loading: () => <WhenAreaChartSkeleton />
+  loading: () => <WhenAreaChartSkeleton />,
+  ssr: false
 })
 const WhenLineChart = dynamic(() => import('@/components/charts').then(mod => mod.WhenLineChart), {
-  loading: () => <WhenLineChartSkeleton />
+  loading: () => <WhenLineChartSkeleton />,
+  ssr: false
 })
 const WhenComposedChart = dynamic(() => import('@/components/charts').then(mod => mod.WhenComposedChart), {
-  loading: () => <WhenComposedChartSkeleton />
+  loading: () => <WhenComposedChartSkeleton />,
+  ssr: false
 })

 const GROWTH_QUERY = gql`

Sample screenshots of the UI skeletons:

Summary by CodeRabbit

New Features

Introduced skeleton components for Pie Chart, Composed Chart, Area Chart, and Line Chart to improve visual feedback during data loading.

Enhancements

Updated referral, rewards, and stackers pages to utilize new chart skeleton components, enhancing user experience by replacing generic loading messages with chart-specific placeholders.

@huumn Can you take a look at the screenshots in the description to see if this is what you're looking for? Let me know of any adjustments desired!

@huumn friendly bump in case the above comment was overlooked with all the recent activity. I'm looking for a 👍 / 👎 on the UI screenshots in the PR description.

I'm sorry I missed the mention! I think the screenshots look good!

Without this, the real chart components seemed to be loaded via SSR and I never saw the fallback/loading component in the browser.

Hmmm odd. Maybe just cached?

Works great! Awesome job!


Dist build?

Hi,
I just found the 1.04 update but it looks like the dist file was not updated since October 2015 and it's not npm neither. Is it on purpose?
Thank you ;)

It is a mistake, i should have automated it with an npm preversion script.

@nfroidure No problem 😉
By the way it looks like the prepublish process was updated for npm 4 if you use it! http://iamakulov.com/notes/all/npm-4-prepublish/
npm 4 is splitting the prepublish script into two new: prepare and prepublishOnly.

prepare will have the same behavior that prepublish has now. Commands in this script will run both before publishing and on npm install.
prepublishOnly, as seen from its name, will run only before publishing the package.
Also, prepublish will receive a warning about the changes

Decide based on what your package needs.

If your package’s prepublish script contains commands that should only be run before npm publish, rename the script into prepublishOnly. Examples of such commands are npm test and eslint.
If your package’s prepublish script contains commands that should run both before npm publish and on npm install, rename the script to prepare. Examples of such commands are commands that build your package (e. g. webpack or babel).
If you don’t know, rename the script to prepublishOnly – this is the behavior most people expect. (As another option, you can leave everything as-is, but there’s no point: it will just delay the decision, but not remove it.)

package.json: "build": "browserify src/SVGPathData.js -o dist/SVGPathData.js -s SVGPathData",
The build script is shadowed by an internal "npm build" command. See https://stackoverflow.com/questions/29939697/npm-build-doesnt-run-the-script-named-build-in-package-json
I'm guessing this is not the intention...

Updated the browserify-ed version both in the npm repository and here. Added npm run build to prepublish script. https://github.com/nfroidure/SVGPathData/commit/6c0368a53f8a338080f8b681b8c09ae18fd8d694


State storage auth

Different way of test authentication. - StorageState
Less code, a slightly worse performance. Like 0.1s per test. So really nothing,
I will explore one more approach before deciding whether merge or revert.

Abandoning for API alternative called from a fixture


add alert related API

Implementation of #5407

Coverage increased (+0.05%) to 33.867% when pulling e6354bbad5e70355678956a8d664723198745d37 on suiguoxin:alert-api into 8e5f4103c5ac2d9121e37fe11ecfe5ff6d2acbe7 on microsoft:master.


Check for 'unknown' sensor values in ecobee

Description:
When the sensor is unavailable / offline, the ecobee API returns 'unknown' for temp value.  This fix will check for that while simplifying the logic a bit.
Related issue (if applicable): #
1897

Example entry for configuration.yaml (if applicable):

Checklist:
If code communicates with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Looks good! :dolphin:


Prohibit certain variable names that are reserved for Lua keywords

https://www.lua.org/manual/5.3/manual.html#3.1

Sounds like we might need a better transpileIdentifier(), that's a lot of refactoring.

Closed in favor of #171


Add GA event when clicking the Billing Docs link

Description
Add GA event when a customer clicks ~the "How Linode Billing Works" button~ all documentation buttons. ~To do this I added support for a callback function on DocsLink.~
~It's technically not exactly a callback since the passed function is called before the link is opened in a new tab, so I'm open to suggestions on the naming/method.~

@Jskobos addressed your feedback... now these events are reported when a user clicks any documentation button.


Remove setup-ffmpeg from Github workflows, test cases, tutorials

The setup-ffmpeg Github action we're using is incompatible with macos-latest (really to Apple M1 silicon): https://github.com/federicocarboni/setup-ffmpeg/issues/21
We have test cases that create .mp4, but they're all skipped with @pytest.mark.skip. The one reference to .mp4 in the tutorials doesn't actually save the file (it is commented out).
We could restore our macos-latest builds by changing the tests to create .apng or .gif (and removing the @pytest.mark.skip) and remove the .mp4 reference from the tutorials.
See https://github.com/search?q=repo%3AC2QA%2Fbosonic-qiskit .mp4&type=code for places .mp4 is found in the bosonic-qiskit code.

It may be best to support Apple Silicon considering its prevalence instead of .mp4 format.
We can update the version of the ffmpeg GitHub workflow if it ever supports Apple Silicon or we can explore using a different workflow if .mp4 has major support.


Allow custom vfs implementations

It would be nice if rusqlite had an official way to hoop up a custom VFS. This is frequently needed when using sqlite in "unusual" environments, such as wasm.
There is a crate that allows specifying a vfs: https://github.com/rkusa/sqlite-vfs . I am currently trying to get sqlite to work in the browser with persistence (not just memory), and I have adapted it to my own needs here: https://github.com/rklaehn/sqlite-vfs
In https://github.com/rusqlite/rusqlite/pull/1010, there is also a new vfs impl to make the wasm target work.
I think something like https://github.com/rkusa/sqlite-vfs, but with no assumptions about the target environment (e.g. no usage of std stuff that is not available in the wasm environment) would be quite nice.

Here is a first draft of the traits:
https://github.com/rklaehn/sqlite-vfs/blob/wasm/src/lib.rs#L27
https://github.com/rklaehn/sqlite-vfs/blob/wasm/src/lib.rs#L43
Compared to the original, these allow you to specify how to generate randomness and current time. This is important for being able to support wasm.

I've been very interested in doing this to add support for it running over something like https://docs.rs/vfs/latest/vfs/. I was testing out implementing a VFS using https://github.com/jalcine/sqlite-hypercore/ since rusqlite forwards libsqlite3 so one could attempt building a vfs. But having a nice wrapper would be a great add. I'd be happy to contribute from what I have to this repo.
(Originally published at: https://jacky.wtf/2022/5/007a)

Yeah, I think this is actually a really important feature to add to rusqlite eventually (although it's going to be wildly unsafe). That said, it's worth noting that what SQLite considers a VFS is a bit more involved than what the vfs crate considers.
That said, it would probably not be no_std as you mention would be desirable in that link. Most of rusqlite uses std, and making that optional... I'm not sure. I guess it could reuse the VFS abstractions for some of them, if they existed, but it's tricky. Either way, it would be a lot of work, and I don't really have the time to do it. Already rusqlite is a project maintained in my spare time, and while I can't say if the same is true for gwenn, I suspect it is.
That said, for a VFS abstraction I have a few reasons I could justify it for work related things in the next year, so that's more plausible.

I've begun working on a PR to first provide an inline set of traits, similar to what is available at https://github.com/rkusa/sqlite-vfs to rusqlite. Then I can work on a separate project that attempts to bridge https://docs.rs/vfs/latest/vfs/ generically. Like you mentioned, there's definitely some stuff that SQLite expects, and I'll see what I can do to work with it as safely as possible; most likely, I'd need to implement an additional trait to get those values and see if I can convince upstream to add those (and if not, then it's an auxiliary trait for people to implement to work with SQLite's VFS, which I think, is fair enough, it's an extension). This is personally critical to some stuff I have going on (but also it's a side project, so this is also a learning experience for me). I can spend about an hour or so each day on this, since it's that tied up with the things I'm working on.
(Originally published at: https://jacky.wtf/2022/7/c3Wq)

Okay. It's a very good feature, but they're pretty hard to write correctly (aside ones that just forward to other SQLite VFS's), both in terms of memory safety[^2] and avoiding database corruption[^1]
In general, I think support for custom SQLite VFS's is something that we'd merge, but probably not integration with the vfs crate. You should just publish your own crate that integrates the two if you need it, though.
If it would help, I'm reasonably familiar with SQLite's VFS layer and am usually around in the rusqlite discord (link in README), and can answer questions if you have any about safety and SQLite's expectations the like. It might be worth doing this to make sure the API is okay before you implement too much, to avoid needing large changes, but it's your call.
[^1]: For example, the vfs crate you link doesn't have any notion of file synchronization or locking, both of which which are usually needed to avoid corruption except in read-only cases.
[^2]: Despite the name, it's basically SQLite's entire OS abstraction, not just the filesystem.

this is dead in the water? Would love to implement a VFS on top of this

@danthegoodman1 If you're brave enough, you can pick up where I left off with https://github.com/jalcine/rusqlite/pull/1. It's still in rough shape but with enough logging to make it viable. It's not an easy task and I'm not the best with unsafe code (currently!) so beware.

Unfortunately my rust is likely an order of magnitude too weak to be helpful there :/


Create popup component, show it when profile changes is saved

Details
Notification pops up when a user make a change in their profile and saves it.
Changes

I have created reusable PopUpNotification component. It has 3 types (success, error, warning) and swipe or click to dismiss feature.
I added profilePage.popupMessageOnSave to en.js
I added an icon to show warnings and error popups  /assets/images/exclamation.svg

Fixed Issues
Fixed: #2812
Tests
Tested in all 5 platforms. I will attach videos below.
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots
Web
https://user-images.githubusercontent.com/11542415/118337321-fa739780-b52c-11eb-983a-2e0bbc6ae73d.mov
Mobile Web
https://user-images.githubusercontent.com/11542415/118337803-f6944500-b52d-11eb-9b75-2402d23f1de8.mov
Desktop
https://user-images.githubusercontent.com/11542415/118337836-0e6bc900-b52e-11eb-8cc0-bc793204426a.mov
iOS
https://user-images.githubusercontent.com/11542415/118338167-de70f580-b52e-11eb-9de5-0842b8570ffb.mov
Android
https://user-images.githubusercontent.com/11542415/118338394-77a00c00-b52f-11eb-9ccc-4f2bbe180dd5.mov

Awesome, thanks for all of the changes. Could we also see the growl notification when there is at least two lines of text?

Awesome, thanks for all of the changes. Could we also see the growl notification when there is at least two lines of text?

With default (19px) line height

With 24px line heigth

Which one would you like me to commit?

A line height of 20 would be great and matches what we use elsewhere. Thanks!

Can we rename PopUpNotification to GrowlNotification?

Can we rename PopUpNotification to GrowlNotification?

Sure

@kakajann It looks like you've got a merge conflict on this pull request

Also, since this is your first time contributing to Expensify.cash (and we're thrilled to have you, by the way 😁), please be sure to read over the Contributor License Agreement and digitally sign it when you get a chance. Thanks!

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

All yours @alex-mechler

Whoops, I didn't mean to dismiss the review. I just approved this suggestion.

I don't want to leave a full review here, but noticed we are not capitalizing types for JSDoc @param
Style guide here if anyone needs them

@roryabraham @alex-mechler put a hold on this since @thienlnam brought to my attention that the author has not been hired.

Merging since it looks like Marcs latest comment was resolved and both Rory and I have approved

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

@kakajann Congrats on getting your first Expensify.cash pull request merged! Great job 🎉

@kakajann Congrats on getting your first Expensify.cash pull request merged! Great job 🎉

Thank you, it was a great experience for me to work with you.


Playing alot of small sounds stops after some time

When i play lots of ~0.5sec voice files, the system stops working.
In general, i get no error message just the loudspeaker keep silent.
But right now i get this (and i use this to ask for help):
sounddevice.PortAudioError: Invalid stream pointer
The code im using can be seen here (but its similar to the "play_file" example):
https://github.com/LocutusOfPenguin/picochess/blob/master/talker/picotalker.py
As said, this effect is after some "moves" , and each move is around 1-3 small voice files.

Can you please give step-by-step instructions how to reproduce this?
Or even better, could you create a stand-alone runnable example that produces the error?
You could e.g. create a Gist including the necessary sound files.

its abit hard for me..
I tried to write a script sending lots of my sounds to the soundsystem..And y can guess, that is working.
But....if y checkout picochess , and start it with
"picochess -c -uvoice en:al -cvoice de:janniclas" and play a few moves y can come to the error..
=> its so often, y wont miss it...but its not always at same place.
I changed my code to be absolute sure, the code is not called by two threads at same time (cause i thinked that was the cause), but it doesnt helped to fix this problem.
I saw when two threads calling "play" at same time, iresulting in "keep silent" afterwards
If y dont /cant do "checkout picochess" and do enter moves, perhaps y give me a hint, how to find out the cause (=narrow the search) - see above.
Jürgen

Yes, in general you should be very careful with multiple threads. This page about PortAudio says:

At the moment, the thread safety of PortAudio is technically unspecified and hence platform/implementation dependent

It is surely the safest bet just to avoid multiple threads accessing PortAudio.
I am willing to try to install your stuff, but only if you give me step-by-step instructions. I don't have a RaspPi, BTW.

You dont need a rasp (i have this stopped voice at my ubuntu too)..and at best, y dont need a dgt chess board - just in this case need to type in moves on console (which is not too user friendly).
But y need to play chess...can y? if not , y might try to enter "lever:w" instead of yr move (switching sides) ...but this only using one (out of two) voices.
git clone https://github.com/LocutusOfPenguin/picochess.git
install a virtual env (not really needed - but keep yr system clean)
pip3 install --upgrade -r requirements.txt
then y should have a working picochess system NOW:
python3 picochess.py -c -uvoice en:dgt -cvoice en:al -l debug -lf picochess.log
starts a picochess in console mode.
moves are typed in like "e2e4" or "e1g1" for 0-0 and after each move need to give "go" ...same if y get a move from chess engine (type "go"). This part is only useful, if y know the chess rules ;-)
If y dont know chess y can only type "lever:l" & "go" and again and again ...(always switch sides)
$$$$
I see now, it even only speaks the first part of the move , say "n","f","3" only "n" spoken ...hmmm

OK, I tried it:
$ python3 picochess.py -c -uvoice en:dgt -cvoice en:al -l debug -lf picochess.log
Traceback (most recent call last):
  File "picochess.py", line 888, in <module>
    main()
  File "picochess.py", line 475, in main
    args.engine = el[0]['file']  # read the first engine filename and use it as standard
IndexError: list index out of range

pls run
./build_engines.py

no change, same error

hmmm....what platform (x86_64?) y running on?
y can try to see on engines.py  @ read_engine_ini what yr system is doing.
another way is to give the engines path with "-e" inside...but i think, yr path are not ok (right now)

Yes, x84_64 Linux (Debian testing), Python 3.5.2
If you want me to try this, you'll have to tell me what to do.
If the play() function doesn't work for you, you could try writing your own callback function. This way you could avoid stopping and starting the PortAudio stream over and over again.

pull again
copy the dgt/test/x86_64/* inside yr engines/x86_64
try again
if y have "ogg123" installed ...y must deactivate it in talker/picotalker.py , otherwise it not use yr system

I've changed my strategy because it's too confusing to test this within such a complicated application.
I just tried this:
for _ in range(150):
    sd.play(some_array, 44100)

Every once in a while this creates the "invalid stream pointer" error you mentioned.
Sometimes it just freezes, which is probably similar to the case where you hear no output and see no errors (because probably one of your threads freezes).
So I guess I found a way to reproduce your errors, now let's try to find and solve the problem behind them!

Great.
Taking picochess is indeed lot of code (irrelevant to this issue).
Hope, y find the cause.

@LocutusOfPenguin Can you please try if #54 fixes your problem?

@LocutusOfPenguin Any news?

@LocutusOfPenguin Did you have a chance to test #54?

I've just merged #45 which hopefully closes this issue.
If not, please re-open it!


[update] adds initial work for updating more props

Proposed Changes

Fixes #412

Read about referenced issues here. Replace words with this Pull Request's context.

The issue described in #412 was solved by providing an array to the update function (which I don't fully understand).
This solution accepts an object directly to the update function because there is only ever one instance of props associated with any sticky instance... noice :)


Añadir los datos para análisis

Sandra buscará los datos de RNASEQ

@manuparra, @brjmoreira, @lmontosah, @DomiRojas,
He tenido un problema subiendo al repositorio RNA-SEQ-Team el fichero de datos que contiene todas las secuencias de RNASEQ que se usarán para crear la Base de Datos.
El FASTA file pesa 109 MB y solo puedo subir hasta 25 MB.
¿Qué se hace en estos casos?

Y comprimido? Cuando ocupa como .zip?
On Wed, 20 Apr 2022 at 13:55, Sandra Martínez-Turiño <
@.***> wrote:

@manuparra https://github.com/manuparra, @brjmoreira
https://github.com/brjmoreira, @lmontosah https://github.com/lmontosah,
@DomiRojas https://github.com/DomiRojas,
He tenido un problema subiendo al repositorio RNA-SEQ-Team el fichero de
datos que contiene todas las secuencias de RNASEQ que se usarán para crear
la Base de Datos.
El FASTA file pesa 109 MB y solo puedo subir hasta 25 MB.
¿Qué se hace en estos casos?
—
Reply to this email directly, view it on GitHub
https://github.com/SandMT/RNA-SEQ-team/issues/1#issuecomment-1103845851,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVVE22C7ZJOEOITFB566EDVF7WCRANCNFSM5T3TY4GQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Manuel Parra-Royón, Ph.D.
Researcher on Data Mining & Artificial Intelligence in Cloud Computing
Research Group on Soft Computing and Intelligent Systems  (SCI2S)
Dept. of Computer Science and Artificial Intelligence,
University of Granada, Granada, Spain.
https://sci2s.ugr.es/

This email and any file attached to it (when applicable) contain(s)
confidential information that is exclusively addressed to its
recipient(s). If you are not the indicated recipient, you are informed
that reading, using, disseminating and/or copying it without
authorisation is forbidden in accordance with the legislation in effect.
If you have received this email by mistake, please immediately notify
the sender of the situation by resending it to their email address.
Avoid printing this message if it is not absolutely necessary.

Lo he zipeado y se queda en 27.3 MB.
Subiré un ZIP de otro FASTA con el que nunca he trabajado. Espero que se compile bien la DB a partir de ellos

Sí la idea es que el contenedor lo descomprima y luego siga las operaciones.
Saludos.
On Wed, 20 Apr 2022 at 15:14, Sandra Martínez-Turiño <
@.***> wrote:

Lo he zipeado y se queda en 27.3 MB.
Subiré un ZIP de otro FASTA con el que nunca he trabajado. Espero que se
compile bien la DB a partir de ellos
—
Reply to this email directly, view it on GitHub
https://github.com/SandMT/RNA-SEQ-team/issues/1#issuecomment-1103918627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVVE2ZRQAFRAGWWWXBE5ELVF77MDANCNFSM5T3TY4GQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Manuel Parra-Royón, Ph.D.
Researcher on Data Mining & Artificial Intelligence in Cloud Computing
Research Group on Soft Computing and Intelligent Systems  (SCI2S)
Dept. of Computer Science and Artificial Intelligence,
University of Granada, Granada, Spain.
https://sci2s.ugr.es/

This email and any file attached to it (when applicable) contain(s)
confidential information that is exclusively addressed to its
recipient(s). If you are not the indicated recipient, you are informed
that reading, using, disseminating and/or copying it without
authorisation is forbidden in accordance with the legislation in effect.
If you have received this email by mistake, please immediately notify
the sender of the situation by resending it to their email address.
Avoid printing this message if it is not absolutely necessary.


Improve cover

Improve the coverage as exposed using coverage and coveralls

Coverage increased (+6.8%) to 94.979% when pulling f19638c227a0d04e2fcba6f5ca8878c00c09cb73 on pbvarga1:improve_cover into 9ef8a417abd578252a6790a5516f998f342a3964 on planetarypy:master.


Change how prismjs is loaded.

Load minified code (3kB vs 30kB)
Add prism autoloader so that we get highlighting for languages we
use.
Hardcode exact prism version.  Perhaps this is controversial, but it
saves a redirect for each request, shaving off 30ms on a fast
connection.

Load minified code (3kB vs 30kB)

Aw yiss.

Add prism autoloader so that we get highlighting for languages we use.

Oh this is pretty cool, thanks for pointing this out.

Hardcode exact prism version.

We're already using 1.2 instead of 1.x.x, so changing to the exact version makes sense here too.
I'm good with this @jakewies :D

Great additions! I didn't realize there was an autoloader 🤯

@kentnek do you have merge perms? I think you should. If you do go ahead and merge this in and you can add @jlebar as a contributor using the @all-contributor command! If you don't have merge perms let me know and I'll figure out what to do to get you them. 😄

Awesome stuff @jlebar thank you for contributing!

@jakewies Oh cool let me do that!

@all-contributors please add @jlebar for code.


Let the nerdtree window move to current vim dir

We know that cd let the vim moves to the nerdtree dir.
We need Let the nerdtree window move to current vim dir, too.
For example:
:cd ~
In nerdtree window, Press Q, the nerdtree root is moved to ~

This functionality has been implemented. See :h NERDTree-CD for more information.


Added Storybook setup procedure for local environment

Description

I have added basic steps to follow, in order to start storybook locally.
I have also created an automated gitpod-config(.gitpod.yml) file for someone who uses gitpod for development.

Related issue(s)
Resolves #6

I have done the following changes @mcturco
You can take a look.

Love that we're going with Storybook from the beginning 👏


yarn plugin add yarn version

Is your feature request related to a particular plugin or theme? If so, specify it.

is for Yarn Plugin
Is your feature request related to a problem? Please describe.

There is no alias for yarn version
Describe the solution you'd like

add an alias for yarn version
Describe alternatives you've considered

Additional context

Closing, please do not open an issue if you have a PR ready.


Autotrigger full example

Hi, sorry for opening an issue for this, but I can't find a complete example how to set up an autotrigger snippet. Everything on autotrigger in the manual is about the json parsing (I'm adding snippets in a lua style).
Maybe someone could provide a small (but complete) example (which should be added somewhere in the Readme/Doc in my opinion).

Yeah, comprehensive examples are sorely lacking :sweat_smile:
All you have to do is call
add_snippets(filetype, snippets, {type = "autosnippets"})

There's a short mention of that here, but it should probably be included in the first section of the doc (Basics).
There's also some stuff in the Examples

Hm is it not working or have I misunderstood autotrigger?
My config + snippets:
ls.config.set_config {
    history = true,
    enable_autosnippet=true,
}
-- from example page
-- set type to "autosnippets" for adding autotriggered snippets.
ls.add_snippets("all", {
    s("autotrigger", {
        t("autosnippet"),
    }),
}, {
    type = "autosnippets",
    key = "all_auto",
})

-- own test
ls.add_snippets("all", {
    s("testing", fmt([[hello world]], {}), {type="autosnippets"})
})

Produces:

Snippet from the example is not working (not sure if type="autosnippets" is right as an argument to add_snippets), and my testing snippet (type="autosnippets" as an argument to s()) should autoexpand (as far as I understand it), but still needs tab to get expanded.

Ahh, just a typo: enable_autosnippet->enable_autosnippets

Hm, behavior doesn't change (still no completion for autotrigger and tab is still needed for testing). Not quite sure what I'm doing wrong.  Does the example run on your side? (if no the error should be somewhere in my config I guess)

Just so we're on the same page, I just tested this, and it works:
ls.config.set_config {
    history = true,
    enable_autosnippets=true,
}

-- from example page
-- set type to "autosnippets" for adding autotriggered snippets.
ls.add_snippets("all", {
    ls.s("autotrigger", {
        ls.t("autosnippet"),
    }),
}, {
    type = "autosnippets",
    key = "all_auto",
})

Just so we're on the same page
Could you maybe make a video/gif of the behavior you get with this? (maybe I just understand autotrigger false (or otherwise I'll need to check config and start removing plugins to get a minimal config))

Yeah, ofc:
https://user-images.githubusercontent.com/41961280/167564972-92f9d9d4-a191-4992-bfc3-40b71e048667.mp4
You can make sure the option enable_autosnippets=true works by checking the output of au InsertCharPre. It should show one autocommand from group "luasnip".

Sounds good :+1:
You can also check the snippet is indeed registered via :lua print(#ls.get_snippets("all", {type = "autosnippets"})) (check the doc if it doesn't work exactly, but I think this should be it. Also make sure the queried filetype matches the one you're adding snippets to)

Also make sure the queried filetype matches the one you're adding snippets to)
Already used all for that reason.

Well just noticed it works now. I think I only tested my testing snippet where the autotrigger type is set at the wrong position after correcting enable_autosnippet to enable_autosnippets (or I had a simple typo when testing the trigger) :see_no_evil:
Thanks for your help (sorry for the mistake creating confusion in the end) :+1:

Aaahhh alright xD
You're welcome :D

Hi, one small follow up: Any possibility to set the autotrigger optoion when loading snippets with the lua-loader (specified for the specific snippets)? (shouldn't become a full discussion in this dead/closed issue, if necessary, I'll make a new one)

Take a look here, you'll need to return autosnippets in a second table.
There's an issue for adding an autotrigger to the snippet-options, #482, but it'll be a while till I get to that

Ah right thanks :+1:


Merge pull request #85 from PennLINC/main

back to template for atlas

Changes proposed in this pull request

Documentation that should be reviewed

different template PNC, NKI, MN6, MN9, OASIS, T1w and native
#79 #78 #85  #68


Unable to downvote articles

Reactjs.org does not allow to down vote or does not give feedback on down vote.
Example:
https://reactjs.org/blog/2020/12/21/data-fetching-with-react-server-components.html
Expected
Down vote should work, just like up vote.

I guess I can work on this.


add option that COMMAND_LINE_CPU_FREQUENCY is invalid

If parse_command_line isn't able to identify the processor frequency, the function get_command_line_cpu_frequency will return None instead of a invalid frequency.
In addition, the frequency measurement with PIT is able to fail. In this case, we just guess a frequency of 2Ghz. For tests is guessing a good workaround.

bors r+


Decompression could be optimized (would be 5x to 20x faster)

Hi,
LZW decompression could be optimized to be somewhat faster by not using the classic build-a-stack-then-reverse-it technique but rather using references in the read buffer.
I have implemented this in a GIF reader a while ago. If that's of interest I could try working on a patch.
Cheers,
Robert.

feel free to send a PR

I did some preliminary investigation; this is a bit trickier for the general case than for the GIF case (because a code may refer to a position that is no longer in the current buffer whereas for a GIF image you can keep the whole image in memory) but I think it can be done.

I don't think it's doable because the whole decoded buffer isn't kept in memory.
https://github.com/vapier/ncompress/issues/27 has a decoder that basically stores each string in a flat array in their full form. This is doable. But my problem with this is that the worst case memory usage is unknown. It has to be bounded since the code is bounded to 16bits but I'm not sure what that bound is and it may turn out to be quite high.
Here's mixed approach that uses bounded memory but is faster than the current dict where strings are represented as <prefix_index, last_char> pair: Use <prefix_index, last_chars[N]> instead. Storing multiple chars per "node" in the linked-list results in less pointer hops and larger "payload" per hop.
With N set to 32, the decompression dict memory usage will be roughly >2MiB while being about 10x faster on large chains. Making this change on ncompress is a bit difficult though, the code is quite... ahem, let's say say "ancient" and difficult to modify.

But my problem with this is that the worst case memory usage is unknown.

I did a bit of math-ing today and TLDR is that the worst case is roughly 2 gigs.

Longer explanation: worst case would always make sure the new code is larger than the previous. And the only way to do that is to repeat the last code as the prefix + a new byte. In other words, a large run of the same byte will do the trick.
So what we have here is basically an arithmetic progression where each term increases by 1. Using the sum formula we get: (2^16 * (1 + 2^16)) / 2 == ~2GiB. (Note that this is slightly larger than the actual worst case due to not accounting the first 255 pre-filled codes).
I also tested out the theory and the result came out as expected, just short of 2GiB:
$ </dev/zero head -c<PHONE_NUMBER> | ./compress -C | ./compress -d >/dev/null
Dict str usage: 1.984 GiB

So yeah, the strategy presented in https://github.com/vapier/ncompress/issues/27 is not really usable unless you want the decompression worst case memory usage to go up to 2Gigs.


Validate fails with Vue-MultiSelect when using multiple rules

Versions:

VueJs: 2.5.13
Vee-Validate: 2.0.9

Description:
Vue-Multiselect required works as per a JS fiddle previously created (#701). But when combined with another rule it seems to fail on that rule.
Steps To Reproduce:
An augmented fiddle that extends the previous..
http://jsfiddle.net/s1hLue65/3/

This fiddle uses vee-validate 2.0.0-rc.8 which is a very old version.
Vue multiselect assigns an object to the v-model. Which is incompatible with most rules. You can to either select primitive values or add new rules that handles objects.

@logaretm  The fiddle uses an old version but I believe the latest version which I am implementing has the same effect (2.0.9) for the reason you state most likely.
When you say add new rules that handles objects you are simply referring to creating custom rules: https://baianat.github.io/vee-validate/guide/custom-rules.html#creating-a-custom-rule ?

Yep, I'm referring to custom rules.
Most built in rules deal with only primitive values.
On Tue, 30 Oct 2018, 17:13 attack68<EMAIL_ADDRESS>wrote:

@logaretm https://github.com/logaretm The fiddle uses an old version
but I believe the latest version which I am implementing has the same
effect (2.0.9) for the reason you state most likely.
When you say add new rules that handles objects you are simply referring
to creating custom rules:
https://baianat.github.io/vee-validate/guide/custom-rules.html#creating-a-custom-rule
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/baianat/vee-validate/issues/1679#issuecomment-434340251,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-KSkcEkjmokSdzwiRF6Cl5Pc7vcqoBks5uqGyrgaJpZM4X_gai
.


Preload REST API calls

Feature Description
Currently when the editor loads, it calls the REST API to get data.

These calls are

Load media ( Video and images ) for library.
Load post ( story ) from editor.
Load list of fonts to display fonts.

When the documents panel is active, two more calls are made.

These calls are

Load a list of Post statuses,
Load of list of users.

We currently load from data into the editor via config which is a js variable on the page. This could be expanded to include some or all data listed above.
Or we could use rest_preload_api_request, which preloads from REST API before the editor is loaded.

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

What data should be preloaded
How should it be preloaded

QA Instructions

Need to identify which parts we'd like to preload.
For example, fonts API will be made obsolete in #1348
Media & the current story seem like a good start.


Connect to the TIPC framework

PR types

New TIPC tests can be performed.
Benchmark Profiling log is printed.

PR changes

[[download_dataset.py] is enriched with some print of hints.
[solver. __solve_dynamic()] is modified to generate 'ips', 'batch_cost' and so on.
add [test_tipc] folder at [PaddleScience/test/], including some shell scripts for analyzing the logging, ReadMe doc, and one configuration file of txt format.

Describe

Complying with the latest benchmark test norms (TIPC), one proper example named [train_2d_unsteady_continuous.txt] can be run. Generally, other examples can follow this standard as well.

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


Pagefind wasn't able to build an index

Same on vitejs 4.5
⚠ Pagefind wasn't able to build an index

Hi @br0wsa, can you share the full logs and the directory structure you're running Pagefind over?
Usually this error means there are no HTML files for Pagefind to crawl.

I had the same issue, but after adding data-pagefind-body to my content div it's working.


Updating sign up link on soundscapes/index.md and contact page

As an evergreen Library product, what's the most appropriate strategy for links back to your personal site? I'm thinking we point from soundscapes/index.md to the contact page, and update contact page with options for signing up with Labs, or visiting your personal website, following on social media, etc, with clear demarcations between your web properties and the Library's.
For reference, experiments page currently says -
Sign up for our Lost Enclaves distribution list to hear about project releases and events by sending us an email at<EMAIL_ADDRESS>You can also follow #SeeingLostEnclaves on social media - @LC_Labs and @jywarren on Twitter, and @librarycongress and @unterbahn on Instagram.

at https://jywarren.github.io/seeing-lost-enclaves/#contact -- right? OK! Doing this now.


Why is FileResourceStore.jsonld not generated?

On 3931d5f6642c8ce8aaa8116a369ccaa1c0d494f6, I get:
$ find components/ | grep Store
components/storage/RepresentationConvertingStore.jsonld
components/storage/PassthroughStore.jsonld
components/storage/PatchingStore.jsonld
components/storage/SimpleResourceStore.jsonld
components/storage/LockingResourceStore.jsonld

Why doesn't components/storage/FileResourceStore.jsonld exist?

Because it's not exported yet in index.ts. (And the reason for that is that I usually only bother adding it when it's integrated, but there's no actual reason so can be added).

Thanks; makes sense. I am just experimenting with it for https://github.com/solid/community-server/milestone/1, so no need to change.

I'll create an FAQ, since I also ran into this problem myself before.


Added a Compiler ctor that takes IR as raw array and count

This avoids the need to construct a temporary std::vector on the application side just to create a Compiler instance if application itself doesn't use STL containers.

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