Empty file links are not themeable

Compare link color to welcome page on the right
Version: 1.55.0-insider
Commit: 8437d38d364ba93b53c1e659c20b1c86f710ec28
Date: 2021-03-24T08:10:36.007Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.3.0

We use the editor link color to be aligned with what how editor styles links.
So if you compare this link to any other link in the editor I think we are fine.
Anyways let me know what you think, and if you prefer the welcome color let me know the name of that one.

Do you have an example of where we use that editor link color? I don't think I've seen it.

Have a link in the editor
Hover over it and hold the cmd key

Ah, ok I see that now. I think because this text isn't style like editor text (it's not monospace) then I think it's better for it to be styled like regular links. Using textLink.foreground should work here.

That makes sense. Assigning to April to clean it up then.


MSID: 98283 Version: 1 DOI: 10.1101/2<IP_ADDRESS>0874

MSID: 98283
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>0874
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98283
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>0874

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98283v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>0874
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98283/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Authors want to do a press release; eLife's Press team have suggested 23 July

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c79) has a publication-type='other'. Is that correct?


New extra: Docker

I've been enjoying using gulp-starter with my Rails app. The rest of my project uses Docker, and I wanted to be able to use gulp-starter under docker-compose in development, and to build my assets when I deploy my containers to production.
The only change I had to make to the stock gulp-starter was to update the clean task. I wanted to mount my src and public folders as volumes, but when you do that, the clean task inside the container can't rm the public folder. I modified the task to delete the contents of public but not the folder itself.
Thanks again for gulp-starter, it has been invaluable for me. Hope you find this useful!

Sorry for all the duplicate requests yesterday, all tests are passing now.

Thanks!

You're welcome, thanks for letting me contribute. Happy Holidays!


--onevent PROGRAM

Program called onevent parameters becoms zombie, this behavior creates long list zombies after long time using librespot

Solution:
change .spawn() to .status() in src/player_event_handler.rs line 11.

Hi @leszekb could you submit a pull request for this?

The pull request (No. 221) about this error is waiting 21 days for acceptance :-)

The pull request (No. 221) about this error is waiting 21 days for acceptance :-)

#221

Opps, Sorry about that.

Pull request #254 fixes this without blocking.

This seems to be fixed, I'd request the issue to be closed


Attribute.Value is empty

Hi,
I'm trying to use Method.Attributes.Value and it's returning an empty string. It seems to be a new bug as I had code using it before that worked.
The code below is my test setup.
string GetAttribute(Method m) {
		if (m.Attributes.Any()){
			return string.Join("|",m.Attributes.Select(q=>q.Value));
		}
		return "any";
	}

I have been using this method to determine the return type of my WebApi code, using the "ProducesResponseType" attribute. An example is below.
[ProducesResponseType(typeof(UsageModel), 200)]
public async Task<IActionResult> GetCurrentUsage([FromQuery] SGuid id) {

Is there another work around I could use?

Hi,
I found the issue. There was a compile issue in my code and somehow that was stopping the attribute binding from working.
I couldn't see it before because it was hidden by 100s of TypeWriter errors and even more typescript errors.
It's particularly strange as the error in question was completely unrelated to attributes - I had a property set to the wrong type.
Perhaps the error reporting should be adjusted.


Update actions.md

Fixes Issue # (Delete if not applicable)
Proposed Changes

update docs

A brief summary of what the changes do
<-- Mention how they improve the library and how that happens -->

Again, thank you!


Allow inherit font-size

Fixes https://github.com/bbc/bbc-a11y/issues/268
Arises from https://github.com/bbc/bbc-a11y/pull/266, which was a fix for https://github.com/bbc/bbc-a11y/issues/262 and https://github.com/bbc/bbc-a11y/issues/246

Love seeing this collaboration happen. Cheers both!


Failed to activate the markdown-scroll-sync package

[Enter steps to reproduce:]

...
...

Atom: 1.28.2 x64
Electron: 2.0.5
OS: Mac OS X 10.13.6
Thrown From: markdown-scroll-sync package 2.1.2
Stack Trace
Failed to activate the markdown-scroll-sync package
At Right-hand side of 'instanceof' is not callable

TypeError: Right-hand side of 'instanceof' is not callable
    at /packages/markdown-scroll-sync/lib/main.coffee:38:14
    at Workspace.observeActivePaneItem (/Applications/Atom.app/Contents/Resources/app/src/workspace.js:710:11)
    at MarkdownScrlSync.activate (/packages/markdown-scroll-sync/lib/main.coffee:25:30)
    at Package.activateNow (/Applications/Atom.app/Contents/Resources/app/src/package.js:230:33)
    at measure (/Applications/Atom.app/Contents/Resources/app/src/package.js:206:33)
    at Package.measure (/Applications/Atom.app/Contents/Resources/app/src/package.js:88:25)
    at activationPromise.Promise (/Applications/Atom.app/Contents/Resources/app/src/package.js:200:20)
    at new Promise (<anonymous>)
    at Package.activate (/Applications/Atom.app/Contents/Resources/app/src/package.js:198:38)
    at PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:695:42)
    at config.transactAsync (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:670:36)
    at Config.transactAsync (/Applications/Atom.app/Contents/Resources/app/src/config.js:866:28)
    at PackageManager.activatePackages (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:668:23)
    at PackageManager.activate (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:647:50)
    at loadStatePromise.loadState.then (/Applications/Atom.app/Contents/Resources/app/src/atom-environment.js:871:27)
    at <anonymous>

Commands
     -0:05.6.0 core:copy (atom-notification.fatal.icon.icon-bug.native-key-bindings.has-detail.has-close.has-stack)

Non-Core Packages
language-markdown 0.26.0
markdown-assistant 0.2.0
markdown-image-paste 2.5.2
markdown-pdf 2.2.0
markdown-preview-plus 3.3.3
markdown-scroll-sync 2.1.2
markdown-table-editor 1.1.1
markdown-writer 2.7.4
qiniu-uploader 0.0.5

Has been resolved, please check: https://github.com/vincentcn/markdown-scroll-sync/issues/560


Refactor ChezExpr to support pretty-printing

Fixes #95.

Drops old unused printers
Better distinguishes between syntax and printers
Pretty-prints cond, let, and lambda. Everything else I wasn't sure should be touched or isn't helped
Drops the Prim. module alias
Renames function abstraction/application to make mkFn1/runFn1-like terminology.

This is ready for review.


Error when run project

it sync properly but
When i run project, it give me error
Error:Execution failed for task ':DemoNewNFC:dexDebug'.

com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.7.0_79\bin\java.exe'' finished with non-zero exit value 2

and application not start because of this error

Hi are you sur to compile the right project the prefix is "app"  and not "DemoNewNFC" .

yes

ok can you give the full verbose gradle log


Transform rename not working inside children

PGSync version: pgsync-1.1.26
Postgres version: 11.4
Elasticsearch version: 7.4
Redis version: 5.0.0
Problem Description:
When we used transform (rename) inside a children node, it does not rename the fields.
Transform (rename) working well if we are inside the root node.
Our json :
[     {         "database": "lu",         "index": "zoneslight",         "setting": {},         "nodes": [             {                 "table": "zone",                 "schema": "cassini",                 "columns": [                     "cassini_id",                     "country_code",                     "admin_level"                 ],                 "transform": {                     "rename": {                         "cassini_id": "cassiniId",                         "country_code": "countryCode",                         "admin_level": "adminLevel"                     }                 },                 "children": [                     {                         "table": "zone_light",                         "schema": "cassini",                         "columns": [                             "geometry_json"                         ],                         "label": "polygon",                         "relationship": {                             "variant": "object",                             "type": "one_to_one"                         },                         "transform": {                             "rename": {                                 "geometry_json": "geometry"                             }                         }                     },                     {                         "table": "metadata",                         "schema": "cassini",                         "columns": [                             "key",                             "value",                             "type"                         ],                         "label": "metadatas",                         "relationship": {                             "variant": "object",                             "type": "one_to_many",                             "through_tables": [                                 "zone_metadata"                             ]                         }                     },                     {                         "table": "zone",                         "schema": "cassini",                         "columns": [                             "id",                             "admin_level"                         ],                         "label": "parents",                         "relationship": {                             "variant": "object",                             "type": "one_to_many",                             "through_tables": [                                 "zone_relation_parent"                             ]                         },                         "transform": {                             "rename": {                                 "admin_level": "adminLevel"                             }                         }                     }                 ]             }         ]     } ]
The only transform which work well for us is :
                "transform": {                     "rename": {                         "cassini_id": "cassiniId",                         "country_code": "countryCode",                         "admin_level": "adminLevel"                     }                 },
Other transformations inside the children node have no effect on the renaming
Thanks in advance for your help
EDIT : Impossible to correctly formate code inside github today  (dont know why so i zip the json in attachment for better read)
exemple json transform rename.zip

[     {         "database": "lu",         "index": "zoneslight",         "setting": {},         "nodes": [             {                 "table": "zone",                 "schema": "cassini",                 "columns": [                     "cassini_id",                     "country_code",                     "admin_level"                 ],                 "transform": {                     "rename": {                         "cassini_id": "cassiniId",                         "country_code": "countryCode",                         "admin_level": "adminLevel"                     }                 },                 "children": [                     {                         "table": "zone_light",                         "schema": "cassini",                         "columns": [                             "geometry_json"                         ],                         "label": "polygon",                         "relationship": {                             "variant": "object",                             "type": "one_to_one"                         },                         "transform": {                             "rename": {                                 "geometry_json": "geometry"                             }                         }                     },                     {                         "table": "metadata",                         "schema": "cassini",                         "columns": [                             "key",                             "value",                             "type"                         ],                         "label": "metadatas",                         "relationship": {                             "variant": "object",                             "type": "one_to_many",                             "through_tables": [                                 "zone_metadata"                             ]                         }                     },                     {                         "table": "zone",                         "schema": "cassini",                         "columns": [                             "id",                             "admin_level"                         ],                         "label": "parents",                         "relationship": {                             "variant": "object",                             "type": "one_to_many",                             "through_tables": [                                 "zone_relation_parent"                             ]                         },                         "transform": {                             "rename": {                                 "admin_level": "adminLevel"                             }                         }                     }                 ]             }         ]     } ]

Nested transformations appear to work even with your provided schema.
Can you do an experiment and try a brand new index?
I wonder if it is due to the immutable mapping you already created.

I have tried with dropping all index in elastic search but the result is the same, only root renaming is working. It always not renaming properties specified in children node
Exemple of _search result from ES:
{"took":3,"timed_out":false,"_shards":{"total":5,"successful":5,"skipped":0,"failed":0},"hits":{"total":{"value":4173,"relation":"eq"},"max_score":1.0,"hits":[{"_index":"zonesboundingbox","_type":"_doc","_id":"be1","_score":1.0,"_source":{"cassiniId":"cbe_a9_e4.18971_n50.48131","countryCode":"be","adminLevel":9,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[4.1573282,50.461172599],[4.1573282,50.505174799],[4.2134758,50.505174799],[4.2134758,50.461172599],[4.1573282,50.461172599]]]}"},"metadatas":null,"parents":[{"id":"be1","admin_level":9},{"id":"be2199","admin_level":2}],"_meta":{"zone_boundingbox":{"zone_id":["be1"]},"zone":{"id":["be1","be2199"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be2","_score":1.0,"_source":{"cassiniId":"cbe_a9_e6.13093_n50.50268","countryCode":"be","adminLevel":9,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[6.0631247,50.441321499],[6.0631247,50.570420899],[6.1983499,50.570420899],[6.1983499,50.441321499],[6.0631247,50.441321499]]]}"},"metadatas":null,"parents":[{"id":"be2199","admin_level":2},{"id":"be2","admin_level":9}],"_meta":{"zone_boundingbox":{"zone_id":["be2"]},"zone":{"id":["be2","be2199"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be11","_score":1.0,"_source":{"cassiniId":"cbe_a8_e5.34092_n50.80478","countryCode":"be","adminLevel":8,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[5.2503757,50.769464199],[5.2503757,50.845426799],[5.4076408,50.845426799],[5.4076408,50.769464199],[5.2503757,50.769464199]]]}"},"metadatas":[{"key":"Wikidata","value":"Q499609","type":1},{"key":"BeIns","value":"73009","type":1}],"parents":[{"id":"be11","admin_level":8},{"id":"be532","admin_level":9}],"_meta":{"zone_boundingbox":{"zone_id":["be11"]},"metadata":{"id":[1991,2517]},"zone_metadata":{},"zone":{"id":["be11","be532"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be17","_score":1.0,"_source":{"cassiniId":"cbe_a8_e5.25046_n51.11740","countryCode":"be","adminLevel":8,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[5.2014863,51.095868199],[5.2014863,51.147150499],[5.3008701,51.147150499],[5.3008701,51.095868199],[5.2014863,51.095868199]]]}"},"metadatas":[{"key":"Wikidata","value":"Q736120","type":1},{"key":"BeIns","value":"71034","type":1}],"parents":[{"id":"be17","admin_level":8},{"id":"be866","admin_level":9}],"_meta":{"zone_boundingbox":{"zone_id":["be17"]},"metadata":{"id":[153,1375]},"zone_metadata":{},"zone":{"id":["be17","be866"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be32","_score":1.0,"_source":{"cassiniId":"cbe_a8_e4.14757_n50.74419","countryCode":"be","adminLevel":8,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[4.071963,50.705588999],[4.071963,50.789806999],[4.2025124,50.789806999],[4.2025124,50.705588999],[4.071963,50.705588999]]]}"},"metadatas":[{"key":"Wikidata","value":"Q646037","type":1},{"key":"BeIns","value":"23064","type":1}],"parents":[{"id":"be731","admin_level":9},{"id":"be32","admin_level":8}],"_meta":{"zone_boundingbox":{"zone_id":["be32"]},"metadata":{"id":[542,1230]},"zone_metadata":{},"zone":{"id":["be32","be731"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be37","_score":1.0,"_source":{"cassiniId":"cbe_a9_e5.20590_n49.79270","countryCode":"be","adminLevel":9,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[5.1807574,49.7715331],[5.1807574,49.827957499],[5.2330684,49.827957499],[5.2330684,49.7715331],[5.1807574,49.7715331]]]}"},"metadatas":[{"key":"BeIns","value":"84009D","type":1}],"parents":[{"id":"be2199","admin_level":2},{"id":"be37","admin_level":9}],"_meta":{"zone_boundingbox":{"zone_id":["be37"]},"metadata":{"id":[1179]},"zone_metadata":{},"zone":{"id":["be2199","be37"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be39","_score":1.0,"_source":{"cassiniId":"cbe_a8_e4.65617_n51.10713","countryCode":"be","adminLevel":8,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[4.6051395,51.075206599],[4.6051395,51.135209499],[4.7005561,51.135209499],[4.7005561,51.075206599],[4.6051395,51.075206599]]]}"},"metadatas":[{"key":"BeIns","value":"12002","type":1},{"key":"Wikidata","value":"Q723774","type":1}],"parents":[{"id":"be924","admin_level":9},{"id":"be39","admin_level":8}],"_meta":{"zone_boundingbox":{"zone_id":["be39"]},"metadata":{"id":[1922,2202]},"zone_metadata":{},"zone":{"id":["be39","be924"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be45","_score":1.0,"_source":{"cassiniId":"cbe_a10_e4.70272_n50.87000","countryCode":"be","adminLevel":10,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[4.6986468,50.868317099],[4.6986468,50.872145399],[4.7077214,50.872145399],[4.7077214,50.868317099],[4.6986468,50.868317099]]]}"},"metadatas":[{"key":"Wikidata","value":"Q17153542","type":1}],"parents":[{"id":"be839","admin_level":9},{"id":"be45","admin_level":10}],"_meta":{"zone_boundingbox":{"zone_id":["be45"]},"metadata":{"id":[370]},"zone_metadata":{},"zone":{"id":["be45","be839"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be46","_score":1.0,"_source":{"cassiniId":"cbe_a8_e2.83029_n50.77549","countryCode":"be","adminLevel":8,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[2.7130028,50.708256199],[2.7130028,50.827323299],[2.9605015,50.827323299],[2.9605015,50.708256199],[2.7130028,50.708256199]]]}"},"metadatas":[{"key":"Wikidata","value":"Q822755","type":1},{"key":"BeIns","value":"33039","type":1}],"parents":[{"id":"be2199","admin_level":2},{"id":"be46","admin_level":8}],"_meta":{"zone_boundingbox":{"zone_id":["be46"]},"metadata":{"id":[598,920]},"zone_metadata":{},"zone":{"id":["be2199","be46"]},"zone_relation_parent":{}}}},{"_index":"zonesboundingbox","_type":"_doc","_id":"be58","_score":1.0,"_source":{"cassiniId":"cbe_a9_e5.23241_n49.74819","countryCode":"be","adminLevel":9,"polygon":{"geometry_json":"{\"type\":\"Polygon\",\"coordinates\":[[[5.1982444,49.7166064],[5.1982444,49.7759271],[5.2686507,49.7759271],[5.2686507,49.7166064],[5.1982444,49.7166064]]]}"},"metadatas":[{"key":"BeIns","value":"85011F","type":1}],"parents":[{"id":"be2199","admin_level":2},{"id":"be58","admin_level":9}],"_meta":{"zone_boundingbox":{"zone_id":["be58"]},"metadata":{"id":[620]},"zone_metadata":{},"zone":{"id":["be2199","be58"]},"zone_relation_parent":{}}}}]}}

This is odd. I am simply unable to reproduce this even with your schema. Can you change these lines to the code below and send the output of the first few rows. Or better yet can you print the result of a row before and after transform on this line
pprint.pprint(row)
print('-' * 10)

Hi @toluaina
I have added peace of code you need for better log.
You can find the log inside the following zip:
pgsync.zip
You will find key "Pkeys before:" and "Pkeys after:" in the log.
I hope it will help you.

Hmm, still not enough to tell what's going on.
Can you also log the value of nodes[0 here?

Of course, the new log with "Pkeys before nodes[0]" string to log nodes[0]
Hope it's help
pgsync.zip

Thanks for the logging data. This has now been fixed in the master branch

I confirm every renaming work well now on the master branch. Thank you for your reactivity


Unexpected Error

cellphonedb was installed under conda (Miniconda3) on windows server.
I tried to run the sample files and got the errors below.
Can you please advice?
[ ][CORE][29/06/22-21:37:57][INFO] Running Complex Prefilters
[ ][APP][29/06/22-21:37:59][ERROR] Unexpected error
Traceback (most recent call last):
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\cellphonedb\src\api_endpoints\terminal_api\method_terminal_api_endpoints\method_terminal_commands.py", line 66, in statistical_analysis
result_precision
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\cellphonedb\src\local_launchers\local_method_launcher.py", line 55, in cpdb_statistical_analysis_local_method_launcher
result_precision)
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\cellphonedb\src\core\methods\method_launcher.py", line 62, in cpdb_statistical_analysis_launcher
result_precision)
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\cellphonedb\src\core\methods\cpdb_statistical_analysis_method.py", line 41, in call
result_precision)
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\cellphonedb\src\core\methods\cpdb_statistical_analysis_complex_method.py", line 41, in call
cells_names)
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\cellphonedb\src\core\methods\cpdb_statistical_analysis_complex_method.py", line 416, in get_complex_significative
complex_more_significative_protein = pd.Series(data='', index=complex_counts['name_complex'].drop_duplicates())
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\pandas\core\series.py", line 275, in init
raise_cast_failure=True)
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\pandas\core\series.py", line 4149, in _sanitize_array
value, len(index), dtype)
File "C:\ProgramData\Miniconda3\envs\cpdb\lib\site-packages\pandas\core\dtypes\cast.py", line 1201, in construct_1d_arraylike_from_scalar
subarr = np.empty(length, dtype=dtype)
TypeError: Cannot interpret '<attribute 'dtype' of 'numpy.generic' objects>' as a data type

thanks for the prompt response, here is the information.
(base) C:\Users\Administrator>conda activate cpdb
(cpdb) C:\Users\Administrator>pip show pandas
Name: pandas
Version: 0.23.4
Summary: Powerful data structures for data analysis, time series, and statistics
Home-page: http://pandas.pydata.org
Author:
Author-email:
License: BSD
Location: c:\programdata\miniconda3\envs\cpdb\lib\site-packages
Requires: python-dateutil, numpy, pytz
Required-by: CellPhoneDB
(cpdb) C:\Users\Administrator>pip show numpy
Name: numpy
Version: 1.21.6
Summary: NumPy is the fundamental package for array computing with Python.
Home-page: https://www.numpy.org
Author: Travis E. Oliphant et al.
Author-email:
License: BSD
Location: c:\programdata\miniconda3\envs\cpdb\lib\site-packages
Requires:
Required-by: pandas

I'm afraid those aren't the right ones for CellPhoneDB.
Could you please try installing the compatible version explicitly: pip install pandas==1.1.4 numpy==1.19.5 and then trying once more?

Thanks a lot, that resolved the problem.
I also got the warnings about R_HOME and R_USER which I managed to resolve by installing rpy as described here:
https://anaconda.zendesk.com/hc/en-us/articles/360023857134-Setting-up-rpy2-on-Windows


[SMALLFIX]Add java doc for integration/yarn/src/test/java/alluxio/yarn/Containe…

…rAllocatorTest.java

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15416/
Test PASSed.

@aaudiber Thanks for your review, updated.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15573/
Test PASSed.


Support Read-Only Slaves/Writable Master

Sequel supports Read-Only Slaves/Writable Master (http://sequel.jeremyevans.net/rdoc/files/doc/sharding_rdoc.html, but current CloudController is not using it yet (https://github.com/cloudfoundry/cloud_controller_ng/blob/master/lib/cloud_controller/db.rb#L39), could CloudController to support this? this could improve the CloudControler performance dramatically for CloudFoundry production environment with CCDB master/slave cluster.

@JimmyMa this is an interesting feature, however, our team doesn't have time to prioritize in the near term. Would you consider making a PR to allow these various configurations?

we'd probably still accept this as a contribution, but we're going to close this due to inactivity.
thanks!


option to serialize attributes in camelCase

This PR resolves closes #188.
This PR includes an option to serialize/deserialize attributes as camelCase instead of kebab/dash notation.
public static void Register(HttpConfiguration config)
{
    // ...

    var jsonApiConfig = new JsonApiConfiguration
    {
        PropertyNameConverter = new CamelCasePropertyNameConverter()
    };
    config.ConfigureJsonApi(jsonApiConfig);

    // ...
}

@joukevandermaas I'll do some more work on this over the weekend.  Have you considered creating a Gitter for this repo?  It's a nice way for consumers and contributors to collaborate on open source projects.  Here's a Gitter for a json api repo for rails.

@barsh I had not considered it, but I'm definitely open to it. Thanks for the suggestion, I'll take a look.

❗ not ready to merge

@joukevandermaas my original goal for this PR was to allow attributes be renamed like this:
Attribute(nameof(Person.FirstName), renameAs: "firstName")
I realized significant effort would be required to make that work, because sorting and filtering does not work if you rename an attribute to something other than the camelCase, PascalCase, or kebab-case equivalent of the original attribute name.
So I have reworked this PR for the purpose of providing an option to serialize attributes with camelCase.
I'm submitting this for reivew, bc I think my work is done here.

@joukevandermaas this PR is ready for review, including documentation and unit tests.

@joukevandermaas my last commit should address the backwards compatibility issues.  Let me know if you see anything else.


Only one contact email address in "To:" Field

Hi,
i'm using rainloop with the owncloud contact app and not with the local rainloop contact feature. Most of my contacts have more than one email address but rainloop only shows one of them in the "To:" field so i can't choose one of the other addresses. Please fix this, so that i can choose another email address when i am typing a name in the "To:"-field. Thanks.

Well, it is an ownCloud bug.
https://github.com/owncloud/core/blob/master/apps/dav/lib/CardDAV/AddressBookImpl.php#L216
Fast fix:
foreach ($vCard->children as $property) {
	if (isset($result[$property->name]) && 'EMAIL' === strtoupper($property->name)) {
		if (!is_array($result[$property->name])) {
			$result[$property->name] = array($result[$property->name]);
		}
		$result[$property->name][] = $property->getValue();
	} else {
		$result[$property->name] = $property->getValue();
	}
}

Hi,
thanks for the fix, now it's working. Hope they fix this bug in next owncloud release.

Did one of you file a bug for this at Owncloud? If not, it will probably not be fixed :)


Uninstalling statamic-bard-text-color without breaking existing YAML content?

How do I properly remove the extension without breaking existing YAML content? I can't use 3.x because it breaks exising YAML content and I can't remove the addon alltogether because it breaks the BARD in the backend.
 Please help me.

I think this is a general Bard / TipTap problem and should be tackled by Statamic (or TipTap) itself.
Other addons that uses custom TipTap marks will likely have the same problem. These are just two of those addons:
https://github.com/new-data-services/statamic-bard-color-picker
https://github.com/OptimoApps/statamic-bard-text-align
You could switch from this addon to the Bard Color Picker plugin, which uses the 'color' attribute. But uninstalling that would cause the same problem.
It would be nice if Statamic Bard could just ignore marks that can't be rendered (anymore)..

Hi!
Thank you both for contributing to this repo.
I wish I could've done more to address incoming issues with the package, but I've been way too busy lately.
I've merged @heidkaemper 's PR and will merge yours too. Right now it has conflicts.
Thanks again for contributing, I've added you to the readme as you've contributed to active development.
If you have any ideas on which direction to take this in and want to contribute faster/easier, I can gladly add you as contributors here, so you can make the experience of using this plugin a more pleasurable one.
Just let me know.


Benchmark drm fails

The following command fails:
npm run bench -- -c benchmark/drm/config.yaml -n network/fabric-v1.1/dev/fabric-node.json
Context

Expected Behavior

Actual Behavior
(node:76178) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 226715)
(node:76178) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'toString' of undefined
at Fabric.queryState (/Users/nima/caliper2/caliper/src/adapters/fabric/fabric.js:213:82)
at Blockchain.queryState (/Users/nima/caliper2/caliper/src/comm/blockchain.js:162:33)
at Object.module.exports.run (/Users/nima/caliper2/caliper/benchmark/drm/query.js:36:19)
at runFixedNumber (/Users/nima/caliper2/caliper/src/comm/client/local-client.js:140:26)
at
Possible Fix

Steps to Reproduce

Existing issues

[ ] Stack Overflow issues
[ ] GitHub Issues
[ ] Rocket Chat history

Context

Your Environment

Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):
Link to your project:

@nimaafraz  Can you run npm run bench -- -c benchmark/drm/config.yaml -n network/fabric-v1.1/2org2peergoleveldb/fabric-node.json ?,

@nimaafraz Can you run npm run bench -- -c benchmark/drm/config.yaml -n network/fabric-v1.1/2org2peergoleveldb/fabric-node.json ?,

Not really, this is the error I get:
(node:11724) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 459883)
(node:11724) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'toString' of undefined
at Fabric.queryState (/home/connect1/caliper/src/adapters/fabric/fabric.js:213:82)
at Blockchain.queryState (/home/connect1/caliper/src/comm/blockchain.js:162:33)
at Object.module.exports.run (/home/connect1/caliper/benchmark/drm/query.js:36:19)
at runFixedNumber (/home/connect1/caliper/src/comm/client/local-client.js:140:26)
at

@nimaafraz The callback passes undefined as the id parameter. Did you successfully run the publish round of the benchmark? It is required before the query round.

It seems that the Test round 1 does not go through.

<EMAIL_ADDRESS>bench /home/connect1/caliper
node ./scripts/main.js "-c" "benchmark/drm/config.yaml" "-n" "network/fabric-v1.1/2org2peergoleveldb/fabric-node.json"

info: [bench-flow.js]: ####### Caliper Test #######
info: [bench-flow.js]: Executing command: docker-compose -f network/fabric-v1.1/2org2peergoleveldb/docker-compose.yaml up -d;sleep 3s
1.1.0: Pulling from hyperledger/fabric-ca
1.1.0: Pulling from hyperledger/fabric-ca
1.1.0: Pulling from hyperledger/fabric-orderer
1.1.0: Pulling from hyperledger/fabric-peer
1.1.0: Pulling from hyperledger/fabric-peer
info: [create-channel.js]: Creating mychannel...
info: [create-channel.js]: Created mychannel successfully
info: [create-channel.js]: Sleeping 5s...
info: [join-channel.js]: Joining channels...
info: [join-channel.js]: Joining organization org1 to channel mychannel...
info: [join-channel.js]: Successfully joined peerOrg1's peers to mychannel
info: [join-channel.js]: Joining organization org2 to channel mychannel...
info: [join-channel.js]: Successfully joined peerOrg2's peers to mychannel
info: [join-channel.js]: Successfully joined mychannel
info: [install-chaincode.js]: installing all chaincodes......
info: [install-chaincode.js]: Installing chaincode marbles...
info: [packager/Node.js]: packaging Node from /home/connect1/caliper/src/contract/fabric/marbles-norichquery/node
info: [install-chaincode.js]: Installing chaincode marbles...
info: [packager/Node.js]: packaging Node from /home/connect1/caliper/src/contract/fabric/marbles-norichquery/node
info: [install-chaincode.js]: Installed chaincode marbles successfully in all peers
info: [install-chaincode.js]: Installing chaincode simple...
info: [packager/Node.js]: packaging Node from /home/connect1/caliper/src/contract/fabric/simple/node
info: [install-chaincode.js]: Installing chaincode simple...
info: [packager/Node.js]: packaging Node from /home/connect1/caliper/src/contract/fabric/simple/node
info: [install-chaincode.js]: Installed chaincode simple successfully in all peers
info: [instantiate-chaincode.js]: Instantiating chaincodes...
info: [e2eUtils.js]: The chaincode instantiate transaction was valid.
info: [instantiate-chaincode.js]: Instantiated chaincode marbles successfully
info: [e2eUtils.js]: The chaincode instantiate transaction was valid.
info: [instantiate-chaincode.js]: Instantiated chaincode simple successfully
info: [instantiate-chaincode.js]: Sleeping 5s...
info: [bench-flow.js]: Started monitor successfully
info: [bench-flow.js]: ####### Testing 'publish' #######
info: [bench-flow.js]: ------ Test round 1 ------
info: [bench-flow.js]: ####### Testing 'query' #######
info: [bench-flow.js]: ------ Test round 2 ------
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
info: [demo.js]: [Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0


Add support for go symbol names to uaddr

This is needed to support Go symbol names in uaddr.
Technically, Go's symbol names can also contain unicode code points. If you'd like to support all Go symbols then I would recommend just removing the regex check from check_symbol.

This should be good to merge.


[Request] Link to paper

Hi Rick,
I am interested in your paper (MorphPool: Efficient Non-linear Pooling & Unpooling in CNNs). Can you share the PDF?
Thanks.

Hi Bishshoy,
Thanks for your interest!
There is no link to the paper available yet, since BMVC will make public the accepted papers in their proceedings. BMVC is held 21-24 November this year. I expect they will make available the papers during or shortly after this period.
In the mean time, I am finalizing the public code to upload it by the time the papers go live.
I will comment on your issue (with a link to the paper) as soon as BMVC publishes their proceedings.
Best regards,
Rick

Hi Bishshoy, here is the link to the paper: https://bmvc2022.mpi-inf.mpg.de/56/


Transforms the ISSUE_TEMPLATE disclaimer into a comment

I've seen so many issues in the past days that didn't remove the disclaimer on top and it kinda annoys me personally ;)

Yeah, too many people are ignoring Cut Here for some reason.


Unable to compile on Linux

If I'm trying to compile this tundra plugin on linux it gives me error
CMake Error at cmake/ModuleSetup.cmake:131 (add_library):
  Cannot find source file:

    /usr/local/src/webrtc/src/build/Release/obj/global_intermediate/protoc_out/webrtc/audio_processing/debug.pb.h

  Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
  .hxx .in .txx
Call Stack (most recent call first):
  src/fiware-cloud-rendering-renderer/CloudRenderingPlugin/CMakeLists.txt:237 (build_library)

-- Build files have been written to: /usr/local/src/tundra

debug.pb.h is in direcyory /out/Release/gen/protoc_out/webrtc/audio_processing/debug.pb.h

We don't officially support linux at time point. Windows and Max releases for the renderer were done in FIWARE.
The WebRTC library has gone forward so much since our code was written that it probably does not build on any platform anymore. Unfortunately the webrtc svn revision information was not marked when the releases were made, so I cant help out with that either.
I can do some digging on my work PC if I could find it for you though.
P.S. I'm not certain that the debug protocol buffer file (debug.pb.h) is mandatory for the build. Those .pb file(s) should be generated by the webrtc project when you build it.


fix spec

address failing tests due to deprication in active support
https://github.com/rails/rails/blob/d684778a000cdcfcac53f6390c565c6a91a3391e/activesupport/lib/active_support/multibyte/chars.rb#L79

cc @jeremy is it the right way to fix the problem? I don't really remember how ruby 1.8 deals with encodings, but I hope it's correct. Tests are green again.

restarted build due to https://github.com/mikel/mail/pull/1306


Update version to 1.1.22-0 on staging

Update version to 1.1.22-0

🚀 Deployed to staging by @OSBotify in version: 1.1.22-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @sketchydroide in version: 1.1.22-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Response: Unauthorized

Still getting the annoying response Unauthorized, any ideas why?
Here is it :
jsonCallback({"validationErrors":null,"response":null,"exception":{"exception":false,"errorMsg":"Unauthorized","httpStatus":"401","errorCode":"300"}});
I couldn`t find the errorCode explained in the docs.

This means that the API keys you are using are expired or incorrect. Can you check with<EMAIL_ADDRESS>and see if your keys are valid?

It happens otn 1% of the orders (we have hundreds now), others work fine. I was thinking about some caching, but its been weeks since we changed from sandbox to live and it works in most of the cases, but we leak sales with this Unothorized message.
I`m writing to tech support now, hope they help

Hey @stefanikolov, were you able to get this issue resolved? The API keys or environment you're targeting were more than likely the issue, definitely let us know though so we can help if need be.
Thanks,
Caleb

I'm getting the unauthorised error.  I've had in depth discussions from the two checkout people and they say it;s nothing on their end. Some orders work, some don't.  Any resolutions?


Update Chinese translation

Add missing Chinese strings

@yinyue200 there is one new string missing, can you add it, please?

@tom-englert of course 😁


Question: does this (great) wrapper handle virtual slides?

I tried using the parameters indicated on http://idangero.us/swiper/api/#virtual, but I can't make it work.
But is it supposed to work? The example app doesn't show the virtual option.
Best regards.

This wrapper just basically initializes Swiper and updates it when ever configuration changes. So this wrapper should not have any effect on how Swiper works and what features works. All should work normally.

Thanks @sconix for your reply as it encourages me to try again, since I now know it should work.

Sure no problem and sorry that I can not be for more help since I have not used the virtual slides myself. The most common problems when using Swiper with Angular comes from the async nature of updating the DOM so often things get fixed by calling the Swiper's update function after DOM is ready. But not sure if that info is any help with virtual slides.

Has anybody solved this problem?

Hey guys, I'm currently with ngx-swiper-wrapper": "^8.0.2 version (but I think even earlier versions handle virtual slides without any issues) and this is how I managed to make virtual slides work.
in my component.html:

	{{ slide}}

and then in the component.ts
import { SwiperConfigInterface } from 'ngx-swiper-wrapper';

...

activeSlide: number = 0;
swiperConfig: SwiperConfigInterface = {};
swiperVirtualSlides: any[] = ['Slide 1', 'Slide 2', 'Slide 3', 'Slide 4', 'Slide 5', 'Slide 6', 'Slide 7', 'Slide 8'];  virtualData: any = { slides: [] };

ionViewDidEnter() {
   const _self = this;

   this.swiperConfig = {
      slidesPerView: 1,
      navigation: false,
      pagination: false,
      scrollbar: false,
      roundLengths: true,
      virtual: {
        slides: _self.swiperVirtualSlides,
        renderExternal(data) {
          _self.virtualData = data;
        }
      }
    };
}

The key into making this work is to use right reference to the component, because this returns the swiper instance but not the component class, when you are trying to assign the virtual data to the local variable.

I implemented it in ngAfterViewInit(), in Angular 8.

I also am using this without _self, because at compilation angular knows to declare it automatically to const _this = this.

I rewrote renderExternal to use an arrow function, as recommended by tslint.

  ngAfterViewInit(): void {
    this.swiperConfig = {
      slidesPerView: 1,
      navigation: false,
      pagination: false,
      scrollbar: false,
      roundLengths: true,
      virtual: {
        slides: this.swiperVirtualSlides,
        renderExternal: data => {
          this.virtualData = data;
        }
      }
    };
  }

It doesn't work in ngOnInit or constructor, you get the Angular error:

Expression has changed after it was checked


Duplicate packages in listing

Schema and Sessions seem to be duplicates of their lower case counterparts in the packages page.

Thanks for the report. That's definitely new. Let me check into it.

Addressed in 16b4009.


Canceling payment leads to 500 status code

Summary
When customer cancels Mollie payment, the order is canceled too. Somehow Mollie tries to create a new payment, which leads to an ApiException "Cannot create a new payment for order ord_6ljr39 when the order status is "canceled"".
Shopware Version: <IP_ADDRESS>
Mollie Plugin Version: 3.6.0
Reproduce

Add a product to cart, go to checkout and select Mollie Giropay
Confirm order.
=> The order state is now "open".
=> You are redirected to Mollie https://www.mollie.com/checkout/test-mode?method=giropay&token=...
On the bottom left click on the back to shop button
=> You're redirected first to https://www.mollie.com/checkout/test-mode/cancel
=> then to http://shop.test/mollie/payment/235b2bef5e28416d8e3fc5aef1e95bbb

The order is correctly canceled but an error is displayed.
Should be
You should not see an error page. Instead there should be a page where you can change your Mollie payment method or retry again. If you choose to retry, the order status should change back to open, and then a new payment should be created.
More Details and Background
We're currently trying to upgrade the shop from <IP_ADDRESS> to <IP_ADDRESS> and with it, the Mollie plugin from 3.1.0 to 3.6.0. In the old version there was no problem when you cancel the payment. I'm not sure what could've caused it, but from current analysis it looks like the plugin tries to create a new payment when it should not do (yet). In the old version the order status and payment was changed on URL /mollie/payment/retry/...
Exception trace on URI "/mollie/payment/247eb01c16bf4bd4bbffc2dd379c7cb6":
Mollie\Api\Exceptions\ApiException:
[2023-05-03T13:58:04+0000] Error executing API call (422: Unprocessable Entity): Cannot create a new payment for order ord_6ljr39 when the order status is "canceled".. Documentation: https://docs.mollie.com/overview/handling-errors

  at vendor/kiener/mollie-payments-plugin/src/Service/MollieApi/Client/MollieHttpClient.php:151
  at Kiener\MolliePayments\Service\MollieApi\Client\MollieHttpClient->parseResponseBody('{"status":422,"title":"Unprocessable Entity","detail":"Cannot create a new payment for order ord_6ljr39 when the order status is \\"canceled\\".","_links":{"documentation":{"href":"https://docs.mollie.com/overview/handling-errors","type":"text/html"}}}', 422, null)
     (vendor/kiener/mollie-payments-plugin/src/Service/MollieApi/Client/MollieHttpClient.php:96)
  at Kiener\MolliePayments\Service\MollieApi\Client\MollieHttpClient->send('POST', 'https://api.mollie.com/v2/orders/ord_6ljr39/payments', array('Accept' => 'application/json', 'Authorization' => 'Bearer test_AUkVDeHtFrTEUxafJ8rMavVknDv3xu', 'User-Agent' => 'Mollie/2.40.1 PHP/8.1.18 Curl/* Shopware/<IP_ADDRESS> MollieShopware6/3.6.0', 'X-Mollie-Client-Info' => 'Linux ec57c4208abe 5.15.0-70-generic #77-Ubuntu SMP Tue Mar 21 14:02:37 UTC 2023 x86_64', 'Content-Type' => 'application/json'), null)
     (vendor/mollie/mollie-api-php/src/MollieApiClient.php:538)
  at Mollie\Api\MollieApiClient->performHttpCallToFullUrl('POST', 'https://api.mollie.com/v2/orders/ord_6ljr39/payments', null)
     (vendor/mollie/mollie-api-php/src/MollieApiClient.php:494)
  at Mollie\Api\MollieApiClient->performHttpCall('POST', 'orders/ord_6ljr39/payments', null)
     (vendor/mollie/mollie-api-php/src/Endpoints/EndpointAbstract.php:76)
  at Mollie\Api\Endpoints\EndpointAbstract->rest_create(array(), array())
     (vendor/mollie/mollie-api-php/src/Endpoints/OrderPaymentEndpoint.php:72)
  at Mollie\Api\Endpoints\OrderPaymentEndpoint->createForId('ord_6ljr39', array(), array())
     (vendor/mollie/mollie-api-php/src/Endpoints/OrderPaymentEndpoint.php:55)
  at Mollie\Api\Endpoints\OrderPaymentEndpoint->createFor(object(Order), array(), array())
     (vendor/mollie/mollie-api-php/src/Resources/Order.php:511)
  at Mollie\Api\Resources\Order->createPayment(array())
     (vendor/kiener/mollie-payments-plugin/src/Facade/MollieOrderPaymentFlow.php:114)
  at Kiener\MolliePayments\Facade\MollieOrderPaymentFlow->process(object(OrderTransactionEntity), object(OrderEntity), object(Order), 'de12e3e170b54d33aa7fbc4caebaa359', object(Context))
     (vendor/kiener/mollie-payments-plugin/src/Facade/Controller/PaymentReturnFacade.php:176)
  at Kiener\MolliePayments\Facade\Controller\PaymentReturnFacade->returnAction('247eb01c16bf4bd4bbffc2dd379c7cb6', object(Context))
     (vendor/kiener/mollie-payments-plugin/src/Controller/Storefront/Payment/ReturnController.php:43)
  at Kiener\MolliePayments\Controller\Storefront\Payment\ReturnController->payment(object(SalesChannelContext), '247eb01c16bf4bd4bbffc2dd379c7cb6')
     (vendor/symfony/http-kernel/HttpKernel.php:163)
  at Symfony\Component\HttpKernel\HttpKernel->handleRaw(object(Request), 1)
     (vendor/symfony/http-kernel/HttpKernel.php:75)
  at Symfony\Component\HttpKernel\HttpKernel->handle(object(Request), 1, true)
     (vendor/symfony/http-kernel/Kernel.php:202)
  at Symfony\Component\HttpKernel\Kernel->handle(object(Request), 1, true)
     (vendor/symfony/http-kernel/HttpCache/SubRequestHandler.php:86)
  at Symfony\Component\HttpKernel\HttpCache\SubRequestHandler::handle(object(Kernel), object(Request), 1, true)
     (vendor/symfony/http-kernel/HttpCache/HttpCache.php:479)
  at Symfony\Component\HttpKernel\HttpCache\HttpCache->forward(object(Request), true)
     (vendor/symfony/http-kernel/HttpCache/HttpCache.php:452)
  at Symfony\Component\HttpKernel\HttpCache\HttpCache->fetch(object(Request), true)
     (vendor/symfony/http-kernel/HttpCache/HttpCache.php:346)
  at Symfony\Component\HttpKernel\HttpCache\HttpCache->lookup(object(Request), true)
     (vendor/symfony/http-kernel/HttpCache/HttpCache.php:224)
  at Symfony\Component\HttpKernel\HttpCache\HttpCache->handle(object(Request), 1, true)
     (vendor/shopware/core/HttpKernel.php:156)
  at Shopware\Core\HttpKernel->doHandle(object(Request), 1, true)
     (vendor/shopware/core/HttpKernel.php:81)
  at Shopware\Core\HttpKernel->handle(object(Request))
     (public/index.php:85)

I think I found the culprit: With #520 the new setting automaticCancellation has been introduced which is enabled per default. When the customer cancels payment, he is redirected to shop and the order state changes to cancelled in https://github.com/mollie/Shopware6/blob/v3.6.0/src/Facade/MollieOrderPaymentFlow.php#L73. This triggers the CancelOrderSubscriber, which also cancels the mollie order. However, MollieOrderPaymentFlow continues to execute and tries to create a new payment in https://github.com/mollie/Shopware6/blob/v3.6.0/src/Facade/MollieOrderPaymentFlow.php#L114 which then fails.
As workaround I can disable automatic cancellation in shop settings.

@boxblinkracer No problem. We were using an old version before, at that time auto cancellation did not exist yet. ;) I'm glad that the disable setting exists, so there's no pressure.

fun fact...that did always exist, i actually didnt know of it either when we took over :D
but could be we fixed it one day haha

@ts-mothership the mollie orders API does not allow to cancel payments within order and you cannot create new payments if there is already one which is open.
we will move at some point all payment methods to payments API where we can handle the payment in a better way


grub configuration changed when rebuilding the lsm

Before it was grub-mkconfig -o /boot/grub/grub.cfg
Now it's changed to sudo update-grub2 because previous one did not take any effect on the lsm.
So I changed this to grub2 and now it's working.
Note: Tested on Linux ubuntu 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

@vadorovsky Is there any other any other comments or feedback you have or is it good to merge?


Copy-edit

The intro section had repeated text on visiting the community page. Refactored this content.
Minor changes to content.
Added links to Slack and the SIG docs mailing list.

/assign @castrojo
Do we want to link to the new contributor site instead of to the community site? The current link (in this PR) is https://deploy-preview-10966--kubernetes-io-master-staging.netlify.com/community/

/lgtm
/approve


Update mockito-scala-cats, ... to 1.16.15

Updates

org.mockito:mockito-scala-cats
org.mockito:mockito-scala-scalatest

from 1.14.8 to 1.16.15.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito" } ]

labels: test-library-update, semver-minor

Superseded by #89.


elapsed time

I would be pleased if it displays elapsed time from program execution to the end.

Do you mean how long VS Code is running or how long a task ran for or something else?

how long a task ran

duplicate of https://github.com/microsoft/vscode/issues/67094


Fail links in compute-device-assignment.md

Update the links in compute-device-assignment, Fix issue(#26382).

Signed-off-by: ydFu<EMAIL_ADDRESS>

Thanks.
/lgtm
/approve


Token decoding

Certain identity providers (looking at you Azure AD) may have multiple public keys in use simultaneously, which is why Token#decode! iterates over these public keys, attempting to decode and validate the given token. If no public key applied, an error will be raised.
Passing :skip_verification is supported by the internal OpenID connect client to skip validating signatures altogether.
Note that this includes PR #24 as it relies on it.

Don't merge this yet, going to fix that begin/rescue-ception.

This is ready for merging now :smile:


feat(app): wire up location conflict modal for ODD

closes RAUT-673
Overview
This PR wires up the location conflict modal for the ODD and changes the modal to match ODD designs. Additionally, the ProtocolSetupModules folder and component is renamed to ProtooclSetupModulesAndDeck
Test Plan
Test on an ODD, go to protocol setup and with a location conflict for fixture and module, click the row to reveal the modal. Make sure the modal works and looks as expected.
Changelog

change ProtocolSetupModules component to ProtocolSetupModulesAndDeck
add code to the location conflict modal to include ODD styling
wire up the modal to the 2 list view components for the ODD
add test coverage

Review requests
see test plan
Risk assessment
low

nit
maybe using gripGap makes the code easy to read.
<Flex flexDirection={} gridGap={SPACING.spacing32}>
  <StyledText>{description}</StyledText>
  <Flex>
    <StyledText>Slot {}</StyledText>
    <ListItem />
    <ListItem />
  </Flex>
  <Flex>
    <SmallButton />
    <SmallButton />
  </Flex>
</Flex>

sorry mistakenly click close instead of comment.


Event system properties

Event system properties is not listed which creating data ingestion connection from Azure Data explorer database. Was it removed .

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

ID: 448ddad1-243c-af54-3395-7d022f83dff7
Version Independent ID: 664d2223-1612-874c-ff23-1bc14aaa339a
Content: Ingest data from IoT Hub into Azure Data Explorer
Content Source: articles/data-explorer/ingest-data-iot-hub.md
Service: data-explorer
GitHub Login: @oflipman
Microsoft Alias: oflipman

@zainuvk Thanks for the feedback! We are currently investigating and will update you shortly.

@zainuvk Please elaborate on your question. We can definitely see the Event system properties like defined in the document section with screen shot  -
https://docs.microsoft.com/en-us/azure/data-explorer/ingest-data-iot-hub#connect-azure-data-explorer-table-to-iot-hub
We also created our own resource and we are able to see this as well. Please check screenshot-

Hope this helps or get back to us with your questions.

@zainuvk We are going ahead and closing this thread if there are no further questions. Please get back to us if you have any.


[REQ] upgrade all packages without scanner input

What kind of request is this?
New feature
What is your request or suggestion?
It would be interesting to have copa to patch all packages without needing input from scanners. This would be equivalent of apt update && apt upgrade.
For distroless, copa might need to get list of packages first, since we don't have the package manager tooling.
Are you willing to submit PRs to contribute to this feature request?

[ ] Yes, I am willing to implement it.

@ashnamehrotra this is a good issue to pick up too

upgrade all feature complete, #592 will be follow up


Update header subtitle styles for thread (child) reports

Details

Updates the header parentNavigationSubtitle to use this styling:

Requirements:

Room is blue
Entire line is clickable

Fixed Issues

$ https://github.com/Expensify/App/issues/22641
Tests / QA Steps

[ ] Verify that no errors appear in the JS console

Step 2: Open a thread report from a DM.

[ ] QA Style matches the following:

[ ] Format is From <DM report title>
[ ] Only room title is blue
[ ] Entire row is still clickable (NOT A BUG)

Step 2: Open a thread report from a Workspace Room.

[ ] QA Style matches the following:

[ ] Format is From <DM report title> in <workspace name>
[ ] Only room title is blue
[ ] Entire row is still clickable (NOT A BUG)

PR Author Checklist

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

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

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

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

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

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

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

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

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@s77rt getting my emulators up to get screenshots on all platforms now, so that shouldn't block C+ review, thank you!

@s77rt ready for another review

Reviewer Checklist

[X] I have verified the author checklist is complete (all boxes are checked off).
[X] I verified the correct issue is linked in the ### Fixed Issues section above
[X] I verified testing steps are clear and they cover the changes made in this PR

[X] I verified the steps for local testing are in the Tests section
[X] I verified the steps for Staging and/or Production testing are in the QA steps section
[X] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[X] I included screenshots or videos for tests on all platforms
[X] I verified tests pass on all platforms & I tested again on:

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

[X] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I verified that this PR follows the guidelines as stated in the Review Guidelines
[X] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

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

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

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

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@s77rt pushed your suggestions, thank you.
A friendly suggestion for next time, let's aim to keep to PRs moving smoothly by avoiding blocking them on NAB changes for internal PRs. Thanks again for your review! 😊

Sorry for that. Should I have approved the PR back then? There was only this remaining suggestion.

Some onyx reports (e.g. task reports) seems to have parentReportID stored as a number. This is unrelated to this PR.

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

@makiour I think you are commenting in the wrong PR. Did you meant https://github.com/Expensify/App/pull/22467?

@grgia  Seems a regression from this PR
https://expensify.slack.com/archives/C049HHMV9SM/p1691035111039979

🚀 Deployed to staging by https://github.com/srikarparsi in version: 1.3.50-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.50-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/srikarparsi in version: 1.3.51-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.51-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


cannot find toka command in OSX

using npm i -g toka is ok but cannot find the command toka
but git clone this repo and npm link works

fixed using vim to modify bin/toka.js and type :set ff=unix


Update Deep CFR implementations to implement Policy

The player_id argument is not need, but still needs to be present in order to implement Policy. For example without it PolicyBot breaks as it passes three arguments (self, the game state and the player id).

Thanks!
I am off on vacation at the moment but will take a look when I get back.
(Note: the test failure seems unrelated.. cause by a backward incompatibility in numpy the we have to fix)

Great, looking good! 👍
(The test failing is something we have to fix in our side.)


make shipping respect email settings

shipment email sending is now handled in the ShipmentHandler in spree 2-4-stable
I tried to test against this, but it seems difficult.

Thanks @jormon


unix,windows: add uv_get_passwd()

This commit adds the uv_get_passwd() function, which returns a subset of the current effective user's password file entry.
Refs #731

OK, I think this is ready for another round.

@saghul would you mind taking a look?

will do.

@bnoordhuis I updated the Unix side to use a single malloc/free. Would you mind taking a quick look at that portion before I make the Windows updates.

@cjihrig UNIX implementation LGTM.

@bnoordhuis, @saghul I think I've addressed all of your comments.

A couple of nits, LGTM otherwise, great work!
One last thing (if you feel like it): maybe add this to the output of test-platform-output? As a happy coincidence this would help us catch those who run the tests suite as root and run into problems as a result :-)

Thanks @saghul. Addressed the nits. Updated test-platform-output.
CI: https://ci.nodejs.org/job/libuv+any-pr+multi/293/

LGTM with a comment.

I withdraw my last comment. Feel free to land it, great work Colin!

Thanks for the reviews. Landed in 217f81b6a18f52322ddfdaf704e9057005e3d10d.


Vim9: E1012 not raised at compile time

Describe the bug
In Vim9 script, sometimes an E1012 error is not raised at compile time.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
        var d: dict<string> = #{ k: '' }
        d = #{ k1: true, k2: function('len') }
    enddef
    defcompile
EOF
)

No error is raised.
Expected behavior
E1012 is raied:
E1012: Type mismatch; expected dict<string> but got dict<any>

Environment

Vim version: 8.2 Included patches: 1-1862
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(360)

Additional context
The error is correctly raised at runtime:
vim9script
def Func()
    var d: dict<string> = #{ k: '' }
    d = #{ k1: true, k2: function('len') }
enddef
Func()

E1012: Type mismatch; expected dict<string> but got dict<any>

If this is working as intended, then why is E1012 correctly raised in the following snippet at compile time?
vim9script
def Func()
    var d: dict<string> = #{ k: '' }
    d = #{ k1: true, k2: 0z12 }
enddef
defcompile

E1012: Type mismatch; expected dict<string> but got dict<any>

The only difference with the original snippet is the second key assigned to the dictionary.  It's a funcref in the original snippet, while it's a blob in the second one.
This is inconsistent.  Either E1012 should not be raised at compile time for any snippet, or it should be raised for both.

Vim version: 8.2 Included patches: 1-1862

There is a typo; I'm on 8.2.1864.

Describe the bug
In Vim9 script, sometimes an E1012 error is not raised at compile time.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
        var d: dict<string> = #{ k: '' }
        d = #{ k1: true, k2: function('len') }
    enddef
    defcompile
EOF
)

No error is raised.
Expected behavior
E1012 is raied:
E1012: Type mismatch; expected dict<string> but got dict<any>

In this case the erorr is only detected at runtime.  It's going to be
quite difficult to detect this at compile time.
If you remove the second dict entry "k2: function('len')" then the error
is reported at compile time.

Environment

Vim version: 8.2 Included patches: 1-1862
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(360)

Additional context
The error is correctly raised at runtime:
vim9script
def Func()
    var d: dict<string> = #{ k: '' }
    d = #{ k1: true, k2: function('len') }
enddef
Func()

E1012: Type mismatch; expected dict<string> but got dict<any>

If this is working as intended, then why is E1012 correctly raised
in the following snippet at compile time?
vim9script
def Func()
    var d: dict<string> = #{ k: '' }
    d = #{ k1: true, k2: 0z12 }
enddef
defcompile

E1012: Type mismatch; expected dict<string> but got dict<any>

The only difference with the original snippet is the second key
assigned to the dictionary.  It's a funcref in the original snippet,
while it's a blob in the second one.
This is inconsistent.  Either E1012 should not be raised at compile
time for any snippet, or it should be raised for both.

The "function()" call is not considered a constant.  Perhaps when
digging much deeper this can be made to work, but I don't see a good
reason to dig into that now.
--
Bare feet magnetize sharp metal objects so they point upward from the
floor -- especially in the dark.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

The "function()" call is not considered a constant.

I see, thank you for the explanation.  I found this while I was trying to understand why E1036 was shadowing E1012 in https://github.com/vim/vim/issues/7160:
vim9script
def Func()
    var menu_winid = popup_menu('', {})
    var opts = #{ key: '' }
    opts = popup_getoptions(menu_winid)
    eval opts.line - 1
enddef
Func()

But you're right; it's not that important.


Fix filename (uploaded file isn't a path-able object)

Fixes the bug currently in the app

Thanks @blackary


disk/list snapshots doesn't respect "resource_group"

Most list() calls (such as compute.virtual_machines.list) accept resource group name as input. disks and snapshots list() methods don't.

Yes there is :)

https://docs.microsoft.com/en-us/python/api/azure.mgmt.compute.v2017_03_30.operations.disksoperations?view=azure-python#list-by-resource-group
https://docs.microsoft.com/en-us/python/api/azure.mgmt.compute.v2017_03_30.operations.snapshotsoperations?view=azure-python#list-by-resource-group

It's just that list is per subscription, and list-by-resource-group per RG


Words within <> brackets are not rendered in the app despite being visible in web view

Steps to reproduce
I have noticed that words are missing entirely from the text and when compared to the webpage it can be deducted that anything written with <> will not be displayed, nor the brackets.
Expected behavior
Web page displays the following text:
"[Fables from Nebula < Hongik > are observing < Kim Dokja's Company >!]"

Actual behavior
Text displayed in the reader:
"[Fables from Nebula are observing !]"

LNReader version
2.0.0
Android version
Android 14
Device
Nothing Phone (1)
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 2.0.0.
[X] I will fill out all of the requested information in this form.

The issue has already been fixed.
I think this is what resolves it: #1049
The fix will be available in an upcoming release.

Any idea when this release will be rolled out?
On Sun, 7 Jul 2024, 9:43 am Elfing, @.***> wrote:

The issue has already been fixed.
I think this is what resolves it: #1049
https://github.com/LNReader/lnreader/pull/1049
The fix will be available in an upcoming release.
image.png (view on web)
https://github.com/LNReader/lnreader/assets/106489440/5e93864e-0fef-4aef-acae-f62324f932db
—
Reply to this email directly, view it on GitHub
https://github.com/LNReader/lnreader/issues/1123#issuecomment-2212357155,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3ABGI4JBNLEV7GKROMVRHLZLDWSVAVCNFSM6AAAAABKEFTMUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJSGM2TOMJVGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Same, one of the LNs I'm reading is super affected by this.

Closing this issue as it should be resolved in the v2.0.0-beta.2 release.


Plugin don't work Apex 5

i tried to install plugin and get error Invalid Plug-in File.

Please provide more information:

What is your environment (database edition, database version, APEX version, web browser) ?
Which plugin did you try to install?
What steps did you follow to install it?
What error message did you get?

About problem:

Apex 5.1 Oracle Database 11g Express Edition 11.2 Chrome browser
Execute PL/SQL and Return Content plugin
In Shared components of Application - Plugins - Import - Choose file - Next - Next
Error "Invalid Plug-in File" "File is not a valid Application Express plug-in export file."

And which file are you trying to import? It should be the "dynamic_action_plugin_muledev_server_region_refresh.sql" file:
https://github.com/mortenbra/apex-plugins/blob/master/execute-plsql-and-return-content-dynamic-action/plugin/dynamic_action_plugin_muledev_server_region_refresh.sql

Yes, I use this file

I re-download file and everething Ok. Thank you.


EXCEPTION_ACCESS_VIOLATION when listing ports on windows

Hi,
Trying to list serial ports on Julia 1.4.1 on Windows 10(guest) on a Virtualbox 6.1/Ubuntu 20.04(host) I get the following error message (LIBSERIALPORT_DEBUG environment variable was set).
julia> get_port_list()
sp: sp_list_ports(000000001DE1F1C0) called.
sp: Enumerating ports.
sp: Opening registry key.
sp: Querying registry key value and data sizes.
sp: Iterating over values.
sp: Found port COM3.
sp: sp_get_port_by_name(COM3, 000000001ED2A4B0) called.
sp: Building structure for port COM3.

Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
Exception: EXCEPTION_ACCESS_VIOLATION at 0x7ffcbf8607d3 -- RtlGetCurrentServiceSessionId at C:\Windows\SYSTEM32\ntdll.dll (unknown line)
in expression starting at REPL[5]:1
RtlGetCurrentServiceSessionId at C:\Windows\SYSTEM32\ntdll.dll (unknown line)
RtlFreeHeap at C:\Windows\SYSTEM32\ntdll.dll (unknown line)
free at C:\Windows\System32\msvcrt.dll (unknown line)
get_usb_details at /workspace/srcdir/libserialport-0.1.1\windows.c:340 [inlined]
get_port_details at /workspace/srcdir/libserialport-0.1.1\windows.c:468
sp_get_port_by_name at /workspace/srcdir/libserialport-0.1.1\serialport.c:109
list_append at /workspace/srcdir/libserialport-0.1.1\serialport.c:316
list_ports at /workspace/srcdir/libserialport-0.1.1\windows.c:535
sp_list_ports at /workspace/srcdir/libserialport-0.1.1\serialport.c:350
sp_list_ports at C:\Users\User\.julia\packages\LibSerialPort\d8jfU\src\wrap.jl:155 [inlined]
#get_port_list#4 at C:\Users\User\.julia\packages\LibSerialPort\d8jfU\src\high-level-api.jl:138
get_port_list at C:\Users\User\.julia\packages\LibSerialPort\d8jfU\src\high-level-api.jl:138
unknown function (ip: 000000001D62D0B3)
jl_apply at /cygdrive/d/buildbot/worker/package_win64/build/src\julia.h:1700 [inlined]
do_call at /cygdrive/d/buildbot/worker/package_win64/build/src\interpreter.c:369
eval_value at /cygdrive/d/buildbot/worker/package_win64/build/src\interpreter.c:458
eval_stmt_value at /cygdrive/d/buildbot/worker/package_win64/build/src\interpreter.c:409 [inlined]
eval_body at /cygdrive/d/buildbot/worker/package_win64/build/src\interpreter.c:799
jl_interpret_toplevel_thunk at /cygdrive/d/buildbot/worker/package_win64/build/src\interpreter.c:911
jl_toplevel_eval_flex at /cygdrive/d/buildbot/worker/package_win64/build/src\toplevel.c:814
jl_toplevel_eval_flex at /cygdrive/d/buildbot/worker/package_win64/build/src\toplevel.c:764
jl_toplevel_eval at /cygdrive/d/buildbot/worker/package_win64/build/src\toplevel.c:823 [inlined]
jl_toplevel_eval_in at /cygdrive/d/buildbot/worker/package_win64/build/src\toplevel.c:843
eval at .\boot.jl:331
eval_user_input at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.4\REPL\src\REPL.jl:86
macro expansion at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.4\REPL\src\REPL.jl:118 [inlined]
#26 at .\task.jl:358
jl_apply at /cygdrive/d/buildbot/worker/package_win64/build/src\julia.h:1700 [inlined]
start_task at /cygdrive/d/buildbot/worker/package_win64/build/src\task.c:687
Allocations: 1740597 (Pool: 1740157; Big: 440); GC: 2
PS C:\Users\User>

The same error occurs when I try to do anything else with the, e.g. open.
Any clues on why this is happening?
The c-library libserialport has received many commits since version 1.1.0 was released four years ago, it might be nice to build from master in libserialport_jll ? ( https://sigrok.org/gitweb/?p=libserialport.git;a=shortlog )
Thx

Can you check whether this is resolved by #61?
pkg> add LibSerialPort#ama/fix-read-methods

This has remained open for some time in part due to lack of testing on Windows. Perhaps you can help us here.
I agree that we should update the C library. I'd like to get #61 merged first.

I've tested your branch, but the same segfault occurs.
Looking more at the code that throws I might be bitten by: https://github.com/sigrokproject/libserialport/commit/02c8a1424d06cb97061a7ebf96231bdb08673b01#diff-23ba024365564263bc3bb4665d30db3d as I'm using an USB  ACM device...
Thanks for effort!

@andrewadare
I verified that building from libserialport-master solves my problem, and I guess other issues too (#22). If you don't mind I'll propose a PR to Yggdrasil to update the jll, so that extended testing can occur (I only tested on win64 and linux64)
Here is the updated build script:
https://github.com/laborg/libserialport_jll.jl

Heres the PR: https://github.com/JuliaPackaging/Yggdrasil/pull/1100

@laborg thanks for your contribution to update the jll in Yggdrasil. How do I use the new version 0.1.2 in LibSerialPort.jl (at least to test with)? On my PR branch, I tried changing to libserialport_jll = "0.1.2" in Project.toml and updating the package, but I still see
julia> sp_get_package_version_string()
"0.1.1"

@andrewadare  The PR hasn't been merged, because this would lead to the problem that every user of LibSerialPort.jll v0.0.4 package would receive the update to the build from libserialport_jll, but that might cause unexpected problems I didn't dare to force on all users. For this to be tested the compat section in Project.toml needs to be changed from "0.1.1" to "=0.1.1", because only the latter definition guarantees LibSerialPort to get exactely 0.1.1 of libserialport, instead of an widely untested build from master. What complicates this is, that the compat section change needs to be manually changed in the General Registry of Julia...

@andrewadare What you could do is: Pkg.dev LibSerialPort.jl and replace the dependency of libserialport_jll to my build https://github.com/laborg/libserialport_jll.jl . With this I get:
julia> sp_get_lib_version_string()
"1:0:1"

The PR hasn't been merged

I'm a bit confused: to me it looks like https://github.com/JuliaPackaging/Yggdrasil/pull/1100 was merged. Are you referring to a different PR?

The PR hasn't been merged

I'm a bit confused: to me it looks like JuliaPackaging/Yggdrasil#1100 was merged. Are you referring to a different PR?

I'm confused too, because yesterday, the PR was cancelled on my request by @giordano immediately after I created it...

I also see
julia> sp_get_lib_version_string()
"1:0:1"

as you do, even though I still have
sp_get_package_version_string()
"0.1.1"

I closed https://github.com/JuliaRegistries/General/pull/15584. You can add master of https://github.com/JuliaBinaryWrappers/libserialport_jll.jl to get libserialport 0.1.2

Thanks, I was confused about the split between build recipe, build artifact and the general registry.
@andrewadare As giordano said, you'll get the new libserialport build if you ] add libserialport_jll#master (the version string won't change because its still 0.1.1 on the master).
Here's my environment on which I verified the fixes on Windows and Linux:
(debuglibserialport) pkg> st
Status `~/debuglibserialport/Project.toml`
  [a05a14c7] LibSerialPort v0.3.0
  [220460dc] libserialport_jll v0.1.2+0 #master (https://github.com/JuliaBinaryWrappers/libserialport_jll.jl)

I added master of libserialport_jll as recommended, and see the same package status entry as you.

(the version string won't change because its still 0.1.1 on the master)
This is helpful; I was hung up on the unchanged version number.

All the tests continue to pass for me on the PR branch (#61), and the example scripts work as expected. I guess I was expecting something to break somewhere, but it all works on my system (macOS with a simple loopback device).
Given that this doesn't seem to break anything (yet), and it fixes major Windows issues, it's a shame we can't get this in without the risk of an uncontrolled dependency change.

Remember that compat bounds can be changed retroactively in the register, if there are problems. It doesn't matter what's written in Project.toml

I think we should switch to using a jll from libserialport master, then. I am willing to continue maintaining the Julia wrapper if there are API updates in the future. Depending on life, I may not get to it immediately, but I'll try to stay engaged.

If you believe the new version of libserialport_jll is fine I can just reopen the pull request for the general registry

+1 from me. @laborg is it okay with you to reopen the registry PR?

Yes of course, but I'm not that invested into LibSerialPort.jl, I just want to use it for one specific simple use case on multiple platforms. Do you know of others that could at least test their work on master before the PR is finally merged?

I am confident we can find additional testers. My request is to reopen and merge JuliaRegistries/General#15584, then I'll switch to the v1.2 jll in #61, which we can test before merging to master.

Done, JuliaRegistries/General#15584 is now merged

Thanks!

Just verified that the bug is now fixed and LibSerialPort works well on Linux and Windows! Thanks!


Update buying power model interface for better messaging

The HasSufficientBuyingPowerForOrder method has been updated to return a result object including the reason the order cannot be executed.
The SetHoldings method has also been updated to display a message if CalculateOrderQuantity returns zero.
Fixes #1576

Approving and merging under the agreement that we'll come back and collate these error strings into a common place for reuse and consistency purposes.


[Fix] Remove the legacy hack function for monocular dataset browsing

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Remove the legacy hack function for monocular dataset browsing.
Modification
Please briefly describe what modification is made in this PR.
Only remove an unused function.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

There are some other imports like here, here, here and here


What are the challenges of FOSS voice assistants on Android devices?

@tadashi-hikari has some interesting insights into the challenges of developing a voice assistant to run natively on Android.
Most voice assistants that run on Android are just a client, they don't run natively. Building a voice assistant that can run completely natively on Android is a very interesting topic. I personally would love to know more about this in hopes the community can collectively help solve some of the challenges.
Challenges
So far, as I understand (and my understanding of Android development is very limited):

Audio processes are the hardest
Android doesn't use standard C libraries, therefore it is harder to get the stuff that can run in Linux working in Android, and many NLP solutions are made in Python, which can present further challenges to getting it to run on Android

@sheosi is also working on a voice assistant that can run natively on Android, he works using Rust, perhaps this can help?

Resources are more limited and a developer needs to think about battery life
Getting processes (ie wake word) to run constantly in the background is poorly documented and can be a challenge

@tadashi-hikari from what I understand, you have solved this problem, would it be possible to get documentation for this?

What other challenges are there? How can we solve these problems?
Opportunities

TinyML data collection

Passive data collection: A user records a lot of data on their phone through many apps, if a user could run a native voice assistant that could access this data (without sharing the data: the user owns their own data), the voice assistant could aid the user in a much more personal and intelligent way.

Accessibility: There are many people with Android phones world wide and installing an app is much easier than installing a FOSS voice assistant on a device (such as a raspberry pi) that many people don't even own.

Resources
Sapphire Assistant Framework
Lily

NLP is really a problem on phones (take into account that I'm going to include both iOS and Android). First, there's the language problem, short story: the language must be compiled.
WARNING -- This is the explanation for before and is long, if the short story is good enough, just skip it --

Long story: On Android. anything that is JIT (like .NET or JS, basically any non-compiled language that claims to be fast) will make the start-up time much worse (relevant when the OS decides to stop some service, I don't know exactly how often this happens, but to me seems like an issue). This is even worse on iOS were JIT is completely forbidden (this seems like a trend, game consoles are following this too, and wouldn't be surprised if macOS ended up doing the same). Interpreted languages (like Python) are slower and still they must support Android directly (CPython, the standard version of Python, doesn't). So, again we are left with pretty much compiled languages, and we need the compilers to support Android/iOS.

So pretty much we are left with Rust and C++ as serious competitors and  Go, and Kotlin/Native (or standard Kotlin for Android) and .NET [NativeAOT](https://github.com/dotnet/runtimelab/tree/feature/NativeAOT (or however they decide to call it now).
I know snips-nlu-rs (Rust), but that's only the inference part (the runner, so to say), the part that actually trains and creates the model for use is written in Python, meaning can't be used in Android/iOS.
I've found https://github.com/keon/awesome-nlp, I'd love to see if @AmateurAcademic thinks that anything under C++/Rust (maybe Kotlin) looks good. If not our other options are: using something that's platform dependent (like something in Java for Android, and something else for Swift) or porting any system to Rust or C++.