text:
Organise the "Dashboard" coherently

Currently, https://tobira.opencast.org/~manage shows a mismatch between the "folders" displayed to the left and the "folders" available under "Dashboard":

This should be aligned:

Also, it's either "Dashboard", "Verwaltung", or "Übersicht".

and it should be made available as such on the upper left

where it's called "Inhalte" verwalten ("Video hochladen" can remain there as most popular "folder"). Oh, and I'm not happy about the "Seiten verwalten?" folder.

Continued in https://github.com/elan-ev/tobira/issues/808.

repo: elan-ev/tobira


text:
Enable security manager in Servlet container tests

Adds servlet container tests with security manager enabled
Currently, the non-jakarta Tomcat tests reproduce the errors observed in https://github.com/elastic/apm-agent-java/issues/2520#issue-1172146921.
Currently blocked. Once #2871 is merged, we should bring this one to a functional state.

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-11-22T16:11:24.962+0000

Duration: 7 min 10 sec

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

/test

/test

maybe only modify the existing policy instead of replacing it

What we do here is not replacing, it should be additive, and I am not sure what it means to modify the existing policy - we use Tomcat Docker images.

source: gharchive/pull-request

authors: apmmachine eyalkoren

repo: elastic/apm-agent-java

license_type: permissive

license_source: github-api


text:
[BUG] Messages properties when objects serialized incorrectly.

ECS integration/library project(s) (e.g. Elastic.CommonSchema.Serilog):
Elastic.CommonSchema.NLog
ECS schema version (e.g. 1.4.0):
8.11
ECS .NET assembly version (e.g. 1.4.2):
8.11
.NET framework / OS:
Net 8
Description of the problem, including expected versus actual behavior:
When i am passing objects into my log events they are not being serialized as individual properties but rather the ToString of the object
Steps to reproduce:

Setup your application to generate a log line

MetricDef metricDef = new MetricDef()
_logger.LogInformation(new EventId(88, "Event88"), "Number is {num} and key is {metricDef.Key}", num.ToString(), metricDef);

Observe  Log generated as below

{"@timestamp":"2024-05-26T20:45:14.3990603+10:00","log.level":"Info","message":"Number is 10 and key is Skidata.Dashboard.Models.MetricDef","labels":{"num":"10","metricDef.Key":"Skidata.Dashboard.Models.MetricDef","EventName":"Event88","agent":{"type":"Elastic.CommonSchema.NLog","version":"8.11.0\u002B20346170742d13e4c2b26ef5c7aaad534970f06b"},"event":{"code":"88","created":"2024-05-26T20:45:14.3990603+10:00","duration":367244451000,"kind":"metric","severity":6,"timezone":"AUS Eastern Standard Time"},"metadata":{"EventId":88},"MessageTemplate":"Number is {num} and key is {metricDef.Key}"}

The expectation is that it would operate as per the microsoft logging ie use the property from the object passed it and in terms of labels each property should be logged as a seperate label using dotted notation.

Note this could very well be an issue with Microsoft.Extensions.Logging but don't believe so based on the fact that the original object being available in the logevent properties dictionary.

You need to use @ to force a json like value in your message see:
https://github.com/NLog/NLog/wiki/How-to-use-structured-logging#formatting-of-the-message
e.g:
MetricDef metricDef = new MetricDef()
_logger.LogInformation(new EventId(88, "Event88"), "Number is {num} and key is {@metricDefKey}", num.ToString(), metricDef);

thanks @Mpdreamz will discuss with NLOG project how i can achieve what i am looking for. As the both example doesn't quite do it as i want my log message to have only 1 property "key" from my class but happy for other properies to be added as labels., Anyway will close this issue as doesn't appear to be an elastic issue

You could send the key as an anonymous object instead?
new { Key = metricDef.Key }
Combined with @ for structured representation in the message itself?
I might not have fully understood the problem though :)

no worries, thanks for the input. For reference I am looking to have all properties from object added as labels and only 1 or more of the properties to be substituted into the message.

So after spending some more time on this, I have managed to get close to what I want by using log generators & with the fix for #397 most desired outcome will be possible with minimal effort.

source: gharchive/issue

authors: Mpdreamz thompson-tomo

repo: elastic/ecs-dotnet


text:
ECS formatter for JUL (java.util.logging)

What about idea to implement ECS formatter for JUL (java.util.logging)?
Motivation
there are bunch of old and very old application which use JUL as logging backend. E.g. Tomcat, Tanuki Wrapper and products based on these applications.
Sometimes is it not easy to switch logging framework, sometimes it's not possible to do this at all. But it would be nice to have logs in ECS format and as option (relatively simple?) we may have class EcsFormatter extends java.util.logging.Formatter.
Open Issues
When I tried to implement it I met a few issues:

there are no file related metainformation (file name, line etc).
looks like no thread name, only thread ID
no MDC or something similar concept
JUL has bit different log levels and looks like we need mapping between JUL and classical DEBUG/INFO/WARN/ERROR vales. The mapping does not look so pretty, but it is work.

So looks like EcsFormatter class may produce ECS-compatible record, but some of feature will be missed and seems some of AbstractEcsLoggingTest unit tests will be failed.
Questions

Does it have sense to implement EcsFormatter?
If yes, how to deal with test cases from AbstractEcsLoggingTest and not supported features like MDC and file meta information?

Adding a formatter for JUL would be a great addition!

there are no file related metainformation (file name, line etc).

No problem. These are optional and off by default anyways.

looks like no thread name, only thread ID

That's a bit sad as I personally find thread names more descriptive but not a bummer either. Just use the field process.thread.id instead.

no MDC or something similar concept

That's not a problem

JUL has bit different log levels and looks like we need mapping between JUL and classical DEBUG/INFO/WARN/ERROR vales. The mapping does not look so pretty, but it is work.

Just use the native JUL log levels, no need to map them. Every framework/language/ecosystem will have their own log levels. So far, log.level is just a string, without any restrictions on the value or a normalized set of log levels.

Does it have sense to implement EcsFormatter?

Yes!

If yes, how to deal with test cases from AbstractEcsLoggingTest and not supported features like MDC and file meta information?

You could either create a subclass of AbstractEcsLoggingTest and move the non-applicable tests there or return a boolean from putMdc, similar to putNdc. Then just skip the relevant tests if the method returns false. For the log.origin test, you could create a protected boolean supportsLogOrigin() method and return false from the JUL test.

Great! Will prepare prepare PR today or these weekends.

authors: felixbarny redrathnure

repo: elastic/ecs-logging-java


text:
[7.13] [elasticsearch] remove unused sidecarResources value (#1185)

Backports the following commits to 7.13:

[elasticsearch] remove unused sidecarResources value (#1185)

jenkins test this please

repo: elastic/helm-charts


text:
Added ES_GC_LOG_FILE export in init files

Per the official distribution init.d files which contain this line:
https://github.com/elastic/elasticsearch/blob/8ffb63a177679141da65981c41340a929ed4ae2d/distribution/rpm/src/main/packaging/init.d/elasticsearch#L66
https://github.com/elastic/elasticsearch/blob/8ffb63a177679141da65981c41340a929ed4ae2d/distribution/deb/src/main/packaging/init.d/elasticsearch#L108
If this is in by default, it doesn't alter or harm anything.  It also allows me to add ES_GC_LOG_FILE to my init_defaults hash, and have it work without having to add a conditional to the template file.
Closes #538

Looks good to me yeah. Must admit i haven't updated the init / systemd files for a while.. really should do that some day :-)

Thank you!

authors: electrical ntent-ashton

repo: elastic/puppet-elasticsearch


text:
[BUG] Elasticdump import from file reports success, but no indexes are created

Context

ElasticDump version: docker :latest (sha256:72cbb126d31f4c2bf5211517a7eabccae5b141b7104444406352dd1a5444998c)
Elasticsearch version: 7.17.5
Node.js version: docker
Full command you are having issue with: elasticdump --output="10.85.5.241:9200" --input="/es/automation-292022-angular-sum.json"
A data-set you can share publicly which reproduces the problem:
This is the contents of the json file:

{"_index":"automation-292022-angular-sum","_type":"_doc","_id":"U2Im334BbvWmrVvVsC5-","_score":1,"_source":{"testId":"a67182b0bb2a7e28112197be04a4ae19","timeStamp":"2022-02-09T15:41:53.129Z","tests":184,"passes":175,"fails":9,"duration":8.223,"package":"VL-Integration-UI"}} {"_index":"automation-292022-angular-sum","_type":"_doc","_id":"DmIo334BbvWmrVvVJS8R","_score":1,"_source":{"testId":"3f71d0fd1298276149af585111e7b992","timeStamp":"2022-02-09T15:43:21.980Z","tests":184,"passes":177,"fails":7,"duration":6.905,"package":"VL-Integration-UI"}}
Describe the bug
No errors are reported when dumping the export to ES, but no indices get created.
To Reproduce
Steps to reproduce the behavior:

Start docker container with docker run --rm -ti -v /home/centos/es:/es:ro elasticdump/elasticsearch-dump /bin/bash
Run elasticdump in container elasticdump --output="10.85.5.241:9200" --input="/es/automation-292022-angular-sum.json"
Note run log root@75fc11baa480:/# elasticdump --output="10.85.5.241:9200/" --input="/es/automation-292022-angular-sum.json" --debug Wed, 27 Jul 2022 16:11:22 GMT | starting dump Wed, 27 Jul 2022 16:11:22 GMT | got 2 objects from source file (offset: 0) Wed, 27 Jul 2022 16:11:22 GMT | sent 2 objects to destination file, wrote 2 Wed, 27 Jul 2022 16:11:22 GMT | got 0 objects from source file (offset: 2) Wed, 27 Jul 2022 16:11:22 GMT | Total Writes: 2 Wed, 27 Jul 2022 16:11:22 GMT | dump complete
Cat indices with curl -klv -XGET  10.85.5.241:9200/_cat/indices/
Note no index is created despite no errors in dump log:
[centos@ip-10-85-4-130 ~]$ curl -kl -XGET  10.85.5.241:9200/_cat/indices/ green open .geoip_databases            ydqp1shsQ_6CitOs4-q48A 1 0 40 0 37.5mb 37.5mb
Elasticsearch log contains no entries from this time period

Current behavior
No error is produced even though something happened...
Expected behavior
The index should be created and available when _cat'ing the indexes

Can't replicate. This seems to be an es issue and not a esdump issue.
green  open cars_index                    0umrWIp2QL6LSaCSfSOSjg 1 0 406 0   82kb   82kb
green  open another_index                 _myx1CnEQruElWu3znPYgg 1 0 500 0 60.8kb 60.8kb
yellow open automation-292022-angular-sum GYIB1vLpSEmtEQVaJrNqrw 5 1   2 0 11.5kb 11.5kb
green  open nested_index                  Ey3bFNBlQheJqtXNkrbpDg 1 0   1 0 46.6kb 46.6kb

authors: cawwot ferronrsmith

repo: elasticsearch-dump/elasticsearch-dump


text:
[FEATURE] dump Elasticsearch index via PIT

Is your feature request related to a problem? Please describe.
Hi repo maintainers, I'm a newbie in this community. I'm wondering is there any version of this repo that uses Point In Time (PIT) feature for index export? I read through the readme, and it seems it's currently based on scroll API.
According to this elastic search blog and this medium post, I see

"We recommend that you use the new point-in-time functionality in Elasticsearch if you can. The scroll API is no longer recommended for deep pagination (even though it still works)". Scroll API holds unnecessary reference to segments that are not needed for live data. PIT, on the other hand, does not have this problem, and search can be performed even on deleted data.
The experiment in the medium post shows that using PIT with search_after decreases the response time by 30% compared to scroll API.

Given this advantage of PIT, is there any plan for supporting PIT? If not, what's reason behind it?

No plans to support PIT. Performance is relative. You can import your own transport and incorporate it as part of a custom transport, or send a PR.
It doesn't solve the major wants of most people.

Recovery from crashes during index (rare, but possible). search_after would help if keep track of the sort, but this is also available via the scroll_id.
Real point search, meaning ... you can do something like, search_after [record_id]. kinda like offset/count without the performance overhead

authors: JiaoMaWHU ferronrsmith


text:
[2] Tutorial: Produce Compliant Kubernetes on top of vanilla Kubernetes tutorial

Acceptance criteria:

A Markdown document

Allows someone familiar with Kubernetes, Helm, Helmfile and sops to deploy a service cluster.
Allows someone familiar with Kubernetes, Helm, Helmfile and sops to deploy two workload clusters, pointing to the previous service cluster.
Tutorial should encourage "secure" practices, e.g., encrypted or out-of-tree secrets.

First, do this using the apps CLI. Later on, we can show the manual steps.

Can be replaced by: https://github.com/elastisys/compliantkubernetes-apps/issues/191 and/or https://github.com/elastisys/compliantkubernetes-apps/issues/192

Can be replaced by: https://github.com/elastisys/compliantkubernetes-apps/issues/191 and/or https://github.com/elastisys/compliantkubernetes-apps/issues/192

Will be redundant once #225 is done

Closing (obsolete).

authors: cristiklein tordsson

repo: elastisys/compliantkubernetes-apps


text:
Release 0.21 changelog

What this PR does / why we need it:
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #1008
Public facing documentation PR (if applicable)

Special notes for reviewer:
Add a screenshot or an example to illustrate the proposed solution:
Checklist:

[x] Added relevant notes to WIP-CHANGELOG.md
[ ] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[ ] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[ ] I upgraded no Chart.
[ ] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

Pipeline config (if applicable)
If you change some config options (e.g. add/rename variable or change the default value) you may need to update the config used by the pipeline in pipeline/config.

I am now closing this PR. I opened another one with cleanedup commits


text:
servfail on certain field

how can i prevent from getting this !ServFail every time?

This indicates there was an error communicating with DNS server and lookup failed. Sometimes it can be "fixed" by selecting a different DNS resolver - try --nameserver 1.1.1.1.

I would also like to clarify that even though ServFail occurred it still indicates that domain is registered. Just particular DNS records can't be resolved due to misconfigured zone, network failure, etc.

I have seen a number of instances where !ServFail is returned for unregistered domains, resulting in false positives that come and go between runs.
I'm not sure what underlying issue causes those fails, I cannot reproduce them at will. It may well be that something along the way is rate limiting NXDomain or SERV_FAIL responses. In some cases, like the example given above, both nameservers for a fuzzed name are in the same network, so it may also depend on the weather on the Internet.
The problem seems to have become less after adding a fallback DNS server (8.8.4.4 in addition to 8.8.8.8), but the behavior is so inconsistent it may as well be that I was lucky over the last couple of days.
I'm considering adding retries with exponential backoff to work around the issue. It's not a general solution, for a number of reasons, but I really would like to get rid of the false positives.

Recommend setting DNS resolvers from more than one provider (for example 8.8.8.8,1.1.1.1). You might also consider manually increasing dnstwist.REQUEST_TIMEOUT_DNS.

authors: driehuis elceef onepaanplus

repo: elceef/dnstwist


text:
Add more tests and increase coverage

This pull request add more tests to the end-to-end tests and increases the coverage.

coverage: 96.38% (+7.2%) from 89.14%
when pulling 682d6e418dcf59ec027ac737bc97cadece339e5e on add_more_tests_increase_coverage
into a46c43c114e2bfeadcf331a642ca5ce23165c3cc on master.

authors: coveralls elchininet

repo: elchininet/home-assistant-secret-taps


text:
🛑 Rentas municipal is down

In 65d0a02, Rentas municipal (https://rentas.catamarcaciudad.gob.ar/ui/index.php) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Rentas municipal is back up in 15f097e after 26 minutes.

license: MIT


text:
Simplify write_page() implementations using a trait associated constant

As suggested here, the page sizes could be defined by implementations of a PageSize trait for the different ICs.
However, implementing this would not compile at the moment.
This is blocked by upstream issue https://github.com/rust-lang/rust/issues/42863

This was solved using a macro


text:
Use semantic-release

Instead of running a Heroku app to periodically publish to npm, we could use semantic-release to make it happen automatically whenever a PR is merged.
To do so, we'd just need to make sure that we always merge with "squash" and write semantic commit messages.

Related to #395

We have a Heroku bot that releases this module, so semantic release is not needed after all.

repo: electron/electron-apps


text:
when running NPM start then getting error, It seems to me that /Release/wm folder missing,   But not getting folder even reinstalling package "electron-active-window"

Uncaught Error: Cannot find module './build/Release/wm'
Require stack:

C:\Yogesh Chaudhary\INV\iWatch\node_modules\electron-active-window\index.js
C:\Yogesh Chaudhary\INV\iWatch\src\index.html
at Module._resolveFilename (node:internal/modules/cjs/loader:963:15)
at o._resolveFilename (node:electron/js2c/renderer_init:2:3833)
at Module._load (node:internal/modules/cjs/loader:811:27)
at f._load (node:electron/js2c/asar_bundle:2:13328)
at o._load (node:electron/js2c/renderer_init:2:3109)
at Module.require (node:internal/modules/cjs/loader:1035:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (C:\Yogesh Chaudhary\INV\iWatch\node_modules\electron-active-window\index.js:1:178)
at Object. (C:\Yogesh Chaudhary\INV\iWatch\node_modules\electron-active-window\index.js:49:3)
at Module._compile (node:internal/modules/cjs/loader:1141:14)

I am having the same issue unfortunately. Any thoughts on how to solve this? :)

authors: ViktorNorman yogeshchaudhary

repo: electron/electron-packager


text:
Windows: 1.5.x fail when node_gyp.cmd path has spaces

The 1.5.x release of electron-rebuild introduces a new error when trying to rebuild and node-gyp.cmd path contains spaces.
For example if node-gyp.cmd is installed in  C:\Users\some name with space\node_modules\.bin\node-gyp.cmd and the user runs electron-rebuild.cmd the following error will be returned:
Unhandled rejection Error: 'C:\Users\some' is not recognized as an internal or external command, operable program or batch file.

/cc @paulcbetts Shouldn't spawn-rx magic this problem away?

Yes it should, I noticed this the other day

Can you try the following in your repo:
npm install spawn-rx@latest
<< run whatever you were trying to do>>

Sorry, this could have been my mistake. Today I reinstalled electron-rebuild@1.5.5 and don't have any issues from the same path. Could have been that an old spawn-rx was being used. If no one else can reproduce we can close this issue. But thx for quick reply and help 😃

@Pettor A new version of spawn-rx was published I believe within a valid semver range for -rebuild.  You probably got the fixed version on the reinstall 👍

I'm getting this issue, due to having a space in my directory, even after doing npm install electron-rebuild@latest and npm install spawn-rx@latest.

I just did a fresh install of electron-rebuild 1.5.7 and have the same problems. I reverted to 1.4.0 and it works.
Same error as @bmathews:
× Rebuild Failed
An unhandled error occurred inside electron-rebuild
'C:\Users\John' is not recognized as an internal or external command,
operable program or batch file.

Failed with exit code: 1

Error: 'C:\Users\John' is not recognized as an internal or external command,
operable program or batch file.

Failed with exit code: 1
    at SafeSubscriber._error (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\spawn-rx\lib\src\index.js:262:84)
    at SafeSubscriber.__tryOrUnsub (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:234:16)
    at SafeSubscriber.error (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:195:26)
    at Subscriber._error (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:128:26)
    at Subscriber.error (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:102:18)
    at MapSubscriber.Subscriber._error (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:128:26)
    at MapSubscriber.Subscriber.error (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:102:18)
    at SafeSubscriber._next (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\spawn-rx\lib\src\index.js:236:65)
    at SafeSubscriber.__tryOrSetError (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:243:16)
    at SafeSubscriber.next (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:185:27)
    at Subscriber._next (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:125:26)
    at Subscriber.next (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:89:18)
    at ReduceSubscriber._complete (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\operator\reduce.js:119:30)
    at ReduceSubscriber.Subscriber.complete (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:114:18)
    at MergeAllSubscriber._complete (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\operator\mergeAll.js:94:30)
    at MergeAllSubscriber.Subscriber.complete (C:\Users\John Kramer\Documents\Work\Merck-Leads\node_modules\rxjs\Subscriber.js:114:18)

authors: MarshallOfSound Pettor bmathews neonhomer paulcbetts

repo: electron/electron-rebuild


text:
Publish a new release

Apologies in advance if opening an issue is not appropriate here. But I did not see any advice on how to request a publish in https://github.com/electron/electron-rebuild/blob/master/contributing.md.
I've been trying to address an issue in our build. Namely that we can't build if we introduce a native module due to a bug in node-gyp. This bug has since been fixed in node-gyp 6.0.1 and I was delighted to see electron-rebuild had a PR to upgrade to this version of node-gyp to fix the issue. Namely
https://github.com/electron/electron-rebuild/pull/327
Now that the tests on that PR have been fixed and it is merged I'd like to request a new release of electron-rebuild to resolve the problem for those affected.

It'd be great if the new release would include the updated "node-abi": "^2.12.0" release to support Electron 7 and 8.
https://github.com/electron/electron-rebuild/issues/321

Same question here +1 I really need to be able to rebuild Node-Keytar but it needs node-abi 2.12.0

There are probably more elegant solutions, but as a temporary fix I've cloned this repository and edited the package.json to use updated node-abi. Then npm i and npm prepare.
Afterwards I changed the electron-rebuild version in my package.json to the path of the cloned repository ("electron-rebuild": "./tmp/electron-rebuild/").

Not sure if this is of use  to anyone. But since posting this issue I've discovered that if you use èlectron-builder you can avoid the need for electron-rebuild entirely by adding the following to package.json.
"postinstall": "electron-builder install-app-deps",

This is blocked by #306.

I really need to be able to rebuild Node-Keytar but it needs node-abi 2.12.0

See https://github.com/electron/electron-rebuild/issues/321#issuecomment-553464192

If anyone really need a temp solution, this is it, only upgrade deps: "node-abi": "^2.12.0", "node-gyp": "^6.0.1", I created this temp fork for my project.
# install
npm i @electerm/electron-rebuild

# run
./node_modules/.bin/electron-rebuild

+1 This would be great for version 7.x. It looks like the build is failing for 1.8.6. When I install 1.8.6, the updated dependency for node-abi (2.12.0) is not pulled included. I have tried the npm update command without success. the dependency is not updated.

@jcolemn3 check out https://github.com/electron/electron-rebuild/issues/321#issuecomment-553464192 for an example of how to upgrade node-abi.

1.8.7 has been released. We had some issues with our automatic release process, thanks for your patience.


text:
Update InstantSearch to 4.x.y

On electronjs.org, we're currently on Algolia InstantSearch 2, whereas the latest version is 4.8.3. Migrating up from v2 to v4 requires a separate migration process for each major version.
For reference, check out Algolia's Migration Guide.

It's now based on algolia/docsearch


text:
Default embedded.provisionprofile doesn't used in signApplication

Hello,
I've faced with different behavior in @electron/osx-sign v 1.0.5 vs electron-osx-sign v 0.5.0.
If options provisioningProfile and preEmbedProvisioningProfile are not specified (preEmbedProvisioningProfile is true by default) then default embedded.provisionprofile is used here https://github.com/electron/osx-sign/blob/06b32b5e8955c95203882ff7ae7f08ae84764a26/src/util-provisioning-profiles.ts#L108-L111 and successfully embedded here https://github.com/electron/osx-sign/blob/06b32b5e8955c95203882ff7ae7f08ae84764a26/src/util-provisioning-profiles.ts#L124 after executing https://github.com/electron/osx-sign/blob/06b32b5e8955c95203882ff7ae7f08ae84764a26/src/sign.ts#L381C11-L381C38
But the following sign application action https://github.com/electron/osx-sign/blob/06b32b5e8955c95203882ff7ae7f08ae84764a26/src/sign.ts#L404 doesn't use it here https://github.com/electron/osx-sign/blob/06b32b5e8955c95203882ff7ae7f08ae84764a26/src/sign.ts#L226-L228 because validatedOpts.provisioningProfile is undefined as it is in original options.

electron-osx-sign filled out the options with the correct profile https://github.com/electron/osx-sign/blob/v0.5.0/util-provisioning-profiles.js#L172

The same for identity

repo: electron/osx-sign


text:
Editing code appears to break demo example of tutorial

Problem Description
I have twice now followed the tutorial and succeeded in creating the my-extension example. Loading it into a page and editing the example fields has been fine. However, as soon as I change anything (even a character within a string) it appears to break and I lose the new fields and the module only asks for 'background' and 'Admin Label' in the content area. Even reverting the changes back to the original does not fix it.
This has happened to me twice now (completely separate installations of WP).
Please advise.

QA Checklist
Reporter

[ ] Helpful title used

Helpful title format: Scope(s) :: One Sentence To Describe The Issue
Example: VB :: Floating Toolbar :: Jumps To Top Of Page

[ ] Detailed description

Description should usually be 150+ characters.

[ ] Steps to reproduce included
[ ] Support Ticket URL included
[ ] Image and/or gif

Developer

[ ] Steps to reproduce proven solved
[ ] Test included and coverage acceptable and all Tests passing?
[ ] PR description has layman's description of problem and solution and "Areas Affected" listed/explained?
[ ] PR branch includes latest commits from master branch (at the time of checking)?
[ ] Estimated points on issue
[ ] Proper code documentation and conventions?
[ ] Proper RTL appearance
[ ] i18n used if applicable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?

Peer Review

[ ] PR branch includes latest commits from master branch (at the time of checking)?
[ ] Steps to reproduce proven solved
[ ] Affected areas are tested and ok
[ ] Proper code documentation and conventions
[ ] Proper RTL appearance
[ ] i18n used if applicable
[ ] Test(s) included and coverage acceptable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?

Quality Assurance

[ ] All tests passed on CircleCI.
[ ] Steps to reproduce passed, the fix works.
[ ] No errors in console or output
[ ] Affected areas are tested and ok
[ ] The fix does not change a customer's website in any surprising or unintended way

[ ] If Divi's design is adjusted, settings are migrated gracefully and invisibly

Design Review

[ ] UI is to spec
[ ] UX is to spec
[ ] Design is to spec
[ ] No surprising visual changes to a customer's website will be experienced after updating

[ ] Any/all visual changes are migrated gracefully

Dev Review

[ ] Test(s) included and coverage acceptable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?
[ ] i18n used if applicable
[ ] Implementation acceptable, DRY, Scaleable, future safe
[ ] Best practices used, cleverness and grokage, ES6 use, etc.

So when I change 'Input your desired heading here.' to 'Input your desired url here.'
The module no longer displays the new input fields when editing the 'Simple Header' module.

Update: It is working ok in the Visual Builder but not in the Page Builder.

I am facing the same issue. Is there any solution for this?

In order for changes to show in the Classic Builder you must clear your browser's local storage. Let me know if that solves it for you.

Tried using 'for(var prop in localStorage)localStorage.removeItem(prop)' and 'window.localStorage.clear()' in console but that didn't help. Also cleared cache from chrome developer tools under application->clear storage.
Tried 3 different operating systems Mac, windows 10, windows 7.. all having same issue.
Let me know how I can help you debug the issue.

Hi lots0logs,
Clearing Chrome's cache did no good.
It seems to work fine in Visual Builder (which is great). I do have to exit and then reenter the VB but I guess that is expected so as to reload the changes I have made.
I can live with that. Shame (and curious) that it won't work in the Classic builder though.

I have still this problem, and tried clearing cache but did not work. Any ideas what I should do ?

Is it not working for you in the Visual Builder front end?

authors: StevieDC etstaging granith lots0logs wpmonks

repo: elegantthemes/create-divi-extension


text:
"Get Involved" header buttons overflow in other languages.

Polish language, 1366x768 screen resolution. Varying size + wrapping look especially weird together.

I suppose we could work on having the heights all be the same at least, but I'm not sure we can stop overflow without wrapping text with hyphens, not something I think #ux will agree to.

Maybe just make the translations shorter and not literal. E.g. instead of "Tworzenie strony internetowej" ("website creating", originally "web development") use "strona internetowa" ("website"). And instead of "Praca nad pulpitem" (which sounds ridiculous BTW) just use "System". (And maybe don't translate "Design".)
Generally in Polish the website has a lot of papercut bugs that make it look like a phishing site.

This doesn't seem to be a problem after the redesign of get-involved. The buttons have been changed to single words and I have yet to find a language and resolution that causes the buttons to wrap to multiple lines.

authors: btkostner lewisgoddard tengwar

repo: elementary/mvp

license: mit

license_source: bigquery


text:
Fix: Replace defaultProps with JS default parameters

Fixes these warnings:

ERROR  Warning: Text: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
in Text (created by Alertbox)
in RCTView (created by View)
...
ERROR  Warning: Button: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
in Button (created by Alertbox)
in RCTView (created by View)
...
"react-native-alertbox": "https://github.com/hypnokermit/react-native-alertbox",

Merged. Thank you!

authors: eleviven hypnokermit

repo: eleviven/react-native-alertbox


text:
🛑 UNER - DDJJ is down

In 9a89348, UNER - DDJJ (https://autogestion.uner.edu.ar/) was down:

HTTP code: 502
Response time: 764 ms

Resolved: UNER - DDJJ is back up in c1c369c.

repo: elfoche/monitoreo


text:
🛑 UCU - Web is down

In 041fb94, UCU - Web (https://ucu.edu.ar) was down:

HTTP code: 521
Response time: 398 ms

Resolved: UCU - Web is back up in 3d54ca3.


text:
🛑 MCU - Owncloud is down

In 932d332, MCU - Owncloud (https://cloud.cdeluruguay.gob.ar/login?redirect_url=/apps/dashboard/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MCU - Owncloud is back up in 2f9acf6 after 9 minutes.


text:
Why is there no option to force a certain initial buffer?

When downloading a torrent made up of multiple files elementum calculates a certain initial buffer based on the total torrent size. I only care about one file so I really don't need to buffer that much, but I can't force it to use less initial buffer using the normal settings. The initial buffer of the 102gb torrent takes so long that I am able to write this whole post during it. While the episode that I want to watch is only 1.5gb.
I am using the latest version of elementum on the latest version of libreelec, but that doesn't really matter I guess.
Edit: I love the add-on BTW. Keep up the good work :).

By default, automatic buffer selection option is enabled, it does not count file size or torrent size, but, instead, looks for piece size, which, for big torrents is 8/16mb.
You can disable this option in Bittorrent tab.
And there you can change buffer size, which is 20mb, by default.

authors: Ianmu elgatito


text:
Multiple cameras failure

Hi, thank you for your excellent module !
I have two CX350.
Cam1 (ip 192.168.1.89 - cxrop 49151 - portdist 49154)
Cam2 (ip 192.168.1.90 - cxrop 49152 - portdist 49154)
So I have two P2 modules installed
Module1 (target ip 192.168.1.89 P2tctport 49151)
Module2 (target ip 192.168.1.90 P2tctport 49152)
I can enable the module1. everything works perfectly.
Or I can enable the module2. everything works perfectly.
BUT I can't enable both modules at the same time.
Log when enabling module1 alone:
23.07.17 08:13:20 Instance/Controller: Enable instance CX350-1
23.07.17 08:13:20 Instance/ModuleHost: Starting connection: "CX350-1"(sTHop2XRcFOvo_-TpmFRx)
23.07.17 08:13:20 Instance/ModuleHost: Connection "CX350-1" started
23.07.17 08:13:20 Instance/ModuleHost: Registered module client "sTHop2XRcFOvo_-TpmFRx"
23.07.17 08:13:20 Instance/Wrapper/CX350-1: Opening TCP Connection to 192.168.1.189:49151
23.07.17 08:13:20 Instance/Controller: instance "CX350-1" configuration updated
23.07.17 08:13:20 Instance/Wrapper/CX350-1: Opened UDP Socket on port 49153
23.07.17 08:13:20 Instance/Wrapper/CX350-1: Connecting via UDP to 192.168.1.189:49153
Log when enabling module2 alone:
23.07.17 08:16:20 Instance/Controller: Enable instance CX350-2
23.07.17 08:16:20 Instance/ModuleHost: Starting connection: "CX350-2"(yO-PnwUrUEEvIQ7-Lo30e)
23.07.17 08:16:20 Instance/ModuleHost: Connection "CX350-2" started
23.07.17 08:16:20 Instance/ModuleHost: Registered module client "yO-PnwUrUEEvIQ7-Lo30e"
23.07.17 08:16:20 Instance/Wrapper/CX350-2: Opening TCP Connection to 192.168.1.190:49152
23.07.17 08:16:20 Instance/Controller: instance "CX350-2" configuration updated
23.07.17 08:16:20 Instance/Wrapper/CX350-2: Opened UDP Socket on port 49153
23.07.17 08:16:20 Instance/Wrapper/CX350-2: Connecting via UDP to 192.168.1.190:49153
Log when enabling module2 (with module1 enable)
23.07.17 08:14:34 Instance/Controller: Enable instance CX350-2
23.07.17 08:14:34 Instance/ModuleHost: Starting connection: "CX350-2"(yO-PnwUrUEEvIQ7-Lo30e)
23.07.17 08:14:34 Instance/ModuleHost: Connection "CX350-2" started
23.07.17 08:14:34 Instance/ModuleHost: Registered module client "yO-PnwUrUEEvIQ7-Lo30e"
23.07.17 08:14:34 Instance/Wrapper/CX350-2: Opening TCP Connection to 192.168.1.190:49152
23.07.17 08:14:34 Instance/Controller: instance "CX350-2" configuration updated
23.07.17 08:14:34 Instance/ModuleHost: Connection "CX350-2" crashed
23.07.17 08:14:34 Instance/ModuleHost: Connection "CX350-2" stopped
23.07.17 08:14:34 Instance/Wrapper/CX350-2: Opened UDP Socket on port 49153
23.07.17 08:14:34 Instance/Wrapper/CX350-2: Connecting via UDP to 192.168.1.190:49153
AM I DOING SOMETHING WRONG ?

I set the tcp port to 49161 to one module
The module start, but all feedbacks do not work anymore.
23.07.17 19:36:32 Instance/Controller: Enable instance CX350-1
23.07.17 19:36:32 Instance/ModuleHost: Starting connection: "CX350-1"(sTHop2XRcFOvo_-TpmFRx)
23.07.17 19:36:32 Instance/ModuleHost: Connection "CX350-1" started
23.07.17 19:36:32 Instance/ModuleHost: Registered module client "sTHop2XRcFOvo_-TpmFRx"
23.07.17 19:36:32 Instance/Wrapper/CX350-1: Opening TCP Connection to 192.168.1.189:49161
23.07.17 19:36:32 Instance/Controller: instance "CX350-1" configuration updated
23.07.17 19:36:32 Instance/Wrapper/CX350-1: Opened UDP Socket on port 49153
23.07.17 19:36:32 Instance/Wrapper/CX350-1: Connecting via UDP to 192.168.1.189:49153
And I still can not start both modules

For me, this looks like the cx350 always uses the same port for feedback back to the module, regardless of the port configured for controlling the camera from companion. That is very unfortunate, as i currently can't listen on the same port from multiple companion module instances. I'll have to think about how i am going to fix this. Either a single instance of the cx350 module can connect to multiple cameras, or there needs to be a change in companion itself to allow for a shared process across module instances.
And then i'll have to figure out how to test this, as i currently don't own two cx350, but i might be able to borrow some.

I can help you to test if you need
De : elianterelle @.>
Envoyé : lundi 17 juillet 2023 19:49
À : elianterelle/p2-camera-connection @.>
Cc : Rik83 @.>; Author @.>
Objet : Re: [elianterelle/p2-camera-connection] Multiple cameras failure (Issue #1)
For me, this looks like the cx350 always uses the same port for feedback back to the module, regardless of the port configured for controlling the camera from companion. That is very unfortunate, as i currently can't listen on the same port from multiple companion module instances. I'll have to think about how i am going to fix this. Either a single instance of the cx350 module can connect to multiple cameras, or there needs to be a change in companion itself to allow for a shared process across module instances.
And then i'll have to figure out how to test this, as i currently don't own two cx350, but i might be able to borrow some.

Reply to this email directly, view it on GitHubhttps://github.com/elianterelle/p2-camera-connection/issues/1#issuecomment-1638602033, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACD5ICQGNDKUT3UEI3LFNXLXQV3HFANCNFSM6AAAAAA2MO7SNI.
You are receiving this because you authored the thread.Message ID: @.***>

Hello,
I am very new to companion and any form of coding. I have made it down the rabbit hole far enough to find myself in the same predicament. I have 2 CX350's and was able to control them individually with disabling the other. I changed the port numbers to coincide in the camera to the connection settings in companion. If you have since found a fix or can lend any help or suggestion, I'd greatly appreciate it. If you would like to have someone help with 2 CX350's on hand and ready, I'd be happy to do that too.
Thanks much
JP

I just received my second HC-X2, so i'll hopefully come around to fixing this in the next weeks!

Good news ! If you need any test, ask me when you want.

For starts... Great job and thank you for this script/module!!! It works amazingly and is very responsive! I have been able to create an app that I've needed to control my 3-4 CX350's. The issue I'm having is that I CAN control each camera just fine but getting the feedback "camera data (cameraState & opticalState) from the cameras to populate the appropriate fields seems like it's limited to a single camera? Even if I change the ports to different ports. Can the script support cameraState/opticalState for multiple cameras? Thanks in advance

I've been working on this issue a few weeks ago. The issue is that the cx350s(or at least the hc-x2s with which i'm testing) always send udp data to the same port, no matter what port the udp request for new data came from. So you basically have to share a single udp listener for all cameras. I'll push my changes to a branch called "multi-camera". There'll be a new constructor parameter "customUdpClient" that you can pass a dgram udp socket to (which can be created with udp.createSocket('udp4'), so you only create one for all your instances of the P2CameraConnection class!).
I wrote this module when i developed a companion module for the cx350/hc-x2, where i also just pushed a fix to an equally named branch: https://github.com/bitfocus/companion-module-panasonic-p2/commit/4358745ff09f37401f50ad04ff52b07235ec3569
I'm currently very busy with work, so i won't have time to document any of those changes and also to test them thoroughly, but my companion module seems to work with those changes. So if something is unclear, maybe you can look at the code of the companion module to see how i used it there.
Hope this helps!

@elianterelle: Oh - that sounds great. I'll definitely take a look and check out those changes. I also did some research on that issue and came only up with very ugly solutions (use some kind of dispatcher service, that delegates the traffic onto another udp port and modify the udp port in the response of the env request)

authors: Arolarobola JP-Consulting-TX Rik83 daubli elianterelle


text:
Cannot load JNA on main

Expected Behavior
Loading features which use JNA, like node:os, should work
Actual Behaviour
Causing a crash
Stacktrace
On macOS aarch64:
Traceback (most recent call last):
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 856, in exec_module
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1002, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 945, in _find_spec
  File "<frozen importlib._bootstrap_external>", line 1413, in _get_spec
  File "<frozen importlib._bootstrap_external>", line 1379, in _path_importer_cache
  File "<frozen importlib._bootstrap_external>", line 1355, in _path_hooks
  File "<frozen zipimport>", line 76, in __init__
  File "<frozen importlib._bootstrap_external>", line 147, in _path_stat
java.lang.Integer cannot be cast to java.lang.Long
Looking for library 'System'
Adding paths from jna.library.path: null
Trying libSystem.dylib
Loading failed with message: com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
Adding system paths: [/usr/lib]
Trying libSystem.dylib
Loading failed with message: com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
Trying /Users/sam/Library/Frameworks/System.framework/System
Loading failed with message: com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
Trying /Library/Frameworks/System.framework/System
Loading failed with message: com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
Trying /System/Library/Frameworks/System.framework/System
Loading failed with message: com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
Looking in classpath from jdk.internal.loader.ClassLoaders$AppClassLoader@27f674d for System
Loading failed with message: Native library (darwin-aarch64/libSystem.dylib) not found in resource path ()

╔════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╗
║ Unable to load library 'System':
com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]
Native library (darwin-aarch64/libSystem.dylib) not found in resource path ()║
╟────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╢
║ Advice:                                                                                ║
║ This is an error in Elide. Please report this to the Elide Team with `elide bug`                                           ║
╟────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╢
║ Stacktrace:                                                                                ║
║                                                                                ║
║ Unable to load library 'System':                                                                                ║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ Native library (darwin-aarch64/libSystem.dylib) not found in resource path ()                                              ║
║ 	at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:325)                                                     ║
║ 	at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:481)                                                     ║
║ 	at com.sun.jna.Library$Handler.<init>(Library.java:197)                                                              ║
║ 	at com.sun.jna.Native.load(Native.java:618)                                                                          ║
║ 	at com.sun.jna.Native.load(Native.java:592)                                                                          ║
║ 	at com.sun.jna.platform.mac.SystemB.<clinit>(SystemB.java:40)                                                        ║
║ 	at oshi.util.platform.mac.SysctlUtil.sysctl(SysctlUtil.java:52)                                                      ║
║ 	at oshi.util.platform.mac.SysctlUtil.sysctl(SysctlUtil.java:40)                                                      ║
║ 	at oshi.hardware.platform.mac.MacCentralProcessor.initProcessorCounts(MacCentralProcessor.java:138)                  ║
║ 	at oshi.hardware.common.AbstractCentralProcessor.<init>(AbstractCentralProcessor.java:68)                            ║
║ 	at oshi.hardware.platform.mac.MacCentralProcessor.<init>(MacCentralProcessor.java:51)                                ║
║ 	at oshi.hardware.platform.mac.MacHardwareAbstractionLayer.createProcessor(MacHardwareAbstractionLayer.java:42)       ║
║ 	at oshi.util.Memoizer$1.get(Memoizer.java:61)                                                                        ║
║ 	at oshi.hardware.common.AbstractHardwareAbstractionLayer.getProcessor(AbstractHardwareAbstractionLayer.java:48)      ║
║ 	at elide.runtime.gvm.internals.node.os.NodeOperatingSystem$BaseOS.cpus(NodeOperatingSystem.kt:317)                   ║
║ 	at elide.runtime.gvm.internals.node.os.NodeOperatingSystem$ModuleBase.getMember$lambda$2(NodeOperatingSystem.kt:203) ║
║ 	at <js> h(../../../../__runtime__/os/os.cjs:1:1310-1319)                                                             ║
║ 	at <js> :program(tools/scripts/cpu.js:2:44-52)                                                                       ║
║ 	at org.graalvm.polyglot/org.graalvm.polyglot.Value.execute(Value.java:928)                                           ║
║ 	at elide.tool.cli.cmd.repl.ToolShellCommand.readExecuteCode(ToolShellCommand.kt:1540)                                ║
║ 	at elide.tool.cli.cmd.repl.ToolShellCommand.invoke$lambda$57(ToolShellCommand.kt:1877)                               ║
║ 	at elide.tool.cli.AbstractSubcommand.withContext(AbstractSubcommand.kt:574)                                          ║
║ 	at elide.tool.cli.cmd.repl.ToolShellCommand.invoke(ToolShellCommand.kt:1823)                                         ║
║ 	at elide.tool.cli.cmd.repl.ToolShellCommand$invoke$1.invokeSuspend(ToolShellCommand.kt)                              ║
║ 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)                            ║
║ 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:102)                                                      ║
║ 	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:263)                                    ║
║ 	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:95)                                                 ║
║ 	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:69)                                             ║
║ 	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)                                                         ║
║ 	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:47)                                     ║
║ 	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)                                                 ║
║ 	at com.jakewharton.mosaic.BlockingKt.runMosaicBlocking(blocking.kt:6)                                                ║
║ 	at elide.tool.cli.AbstractToolCommand.call(AbstractToolCommand.kt:260)                                               ║
║ 	at elide.tool.cli.Elide.invoke-AZeniH0(Elide.kt:299)                                                                 ║
║ 	at elide.tool.cli.AbstractToolCommand$call$$inlined$execute$1.invokeSuspend(AbstractToolCommand.kt:155)              ║
║ 	at elide.tool.cli.AbstractToolCommand$call$$inlined$execute$1.invoke(AbstractToolCommand.kt)                         ║
║ 	at elide.tool.cli.AbstractToolCommand$call$$inlined$execute$1.invoke(AbstractToolCommand.kt)                         ║
║ 	at com.jakewharton.mosaic.MosaicKt$runMosaic$2$4.invokeSuspend(mosaic.kt:147)                                        ║
║ 	at com.jakewharton.mosaic.MosaicKt$runMosaic$2$4.invoke(mosaic.kt)                                                   ║
║ 	at com.jakewharton.mosaic.MosaicKt$runMosaic$2$4.invoke(mosaic.kt)                                                   ║
║ 	at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:42)                        ║
║ 	at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:261)                                         ║
║ 	at com.jakewharton.mosaic.MosaicKt$runMosaic$2.invokeSuspend(mosaic.kt:124)                                          ║
║ 	at com.jakewharton.mosaic.MosaicKt$runMosaic$2.invoke(mosaic.kt)                                                     ║
║ 	at com.jakewharton.mosaic.MosaicKt$runMosaic$2.invoke(mosaic.kt)                                                     ║
║ 	at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:42)                        ║
║ 	at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:261)                                         ║
║ 	at com.jakewharton.mosaic.MosaicKt.runMosaic(mosaic.kt:58)                                                           ║
║ 	at com.jakewharton.mosaic.BlockingKt$runMosaicBlocking$1.invokeSuspend(blocking.kt:7)                                ║
║ 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)                            ║
║ 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:102)                                                      ║
║ 	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:263)                                    ║
║ 	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:95)                                                 ║
║ 	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:69)                                             ║
║ 	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)                                                         ║
║ 	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:47)                                     ║
║ 	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)                                                 ║
║ 	at com.jakewharton.mosaic.BlockingKt.runMosaicBlocking(blocking.kt:6)                                                ║
║ 	at elide.tool.cli.AbstractToolCommand.call(AbstractToolCommand.kt:260)                                               ║
║ 	at elide.tool.cli.AbstractToolCommand.call(AbstractToolCommand.kt:30)                                                ║
║ 	at picocli.CommandLine.executeUserObject(CommandLine.java:2045)                                                      ║
║ 	at picocli.CommandLine.access$1500(CommandLine.java:148)                                                             ║
║ 	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)                ║
║ 	at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)                                                         ║
║ 	at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)                                                         ║
║ 	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)                                     ║
║ 	at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)                                                        ║
║ 	at picocli.CommandLine.execute(CommandLine.java:2174)                                                                ║
║ 	at elide.tool.cli.Elide$Companion.exec$runtime(Elide.kt:232)                                                         ║
║ 	at elide.tool.cli.Elide$Companion.entry(Elide.kt:195)                                                                ║
║ 	at elide.tool.cli.ElideKt.main(Elide.kt:305)                                                                         ║
║ Caused by host exception: java.lang.UnsatisfiedLinkError: Unable to load library 'System':                                 ║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ com.sun.jna.Native.open(Ljava/lang/String;I)J [symbol: Java_com_sun_jna_Native_open or Java_com_sun_jna_Native_open__Ljava_lang_String_2I]║
║ Native library (darwin-aarch64/libSystem.dylib) not found in resource path ()                                              ║
║                                                                                ║
╚════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╝

On Linux amd64:
╔═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╗
║ Could not initialize class com.sun.jna.platform.linux.Udev                                                                    ║
╟───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╢
║ Advice:                                                                                ║
║ This is an error in Elide. Please report this to the Elide Team with `elide bug`                                              ║
╟───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╢
║ Stacktrace:                                                                                ║
║                                                                                ║
║ Could not initialize class com.sun.jna.platform.linux.Udev                                                                    ║
║       at oshi.hardware.platform.linux.LinuxCentralProcessor.queryCurrentFreq(LinuxCentralProcessor.java:446)                  ║
║       at oshi.util.Memoizer$1.get(Memoizer.java:61)                                                                           ║
║       at oshi.hardware.common.AbstractCentralProcessor.getCurrentFreq(AbstractCentralProcessor.java:130)                      ║
║       at elide.runtime.gvm.internals.node.os.NodeOperatingSystem$BaseOS.cpus(NodeOperatingSystem.kt:317)                      ║
║       at elide.runtime.gvm.internals.node.os.NodeOperatingSystem$ModuleBase.getMember$lambda$2(NodeOperatingSystem.kt:203)    ║
║       at <js> h(__runtime__/os/os.cjs:1:1310-1319)                                                                            ║
║       at <js> :program(<shell:js>:1:0-24)                                                                                ║
║       at org.graalvm.polyglot/org.graalvm.polyglot.Context.eval(Context.java:402)                                             ║
║       at elide.runtime.core.internals.graalvm.GraalVMContext.evaluate(GraalVMContext.kt:47)                                   ║
║       at elide.tool.cli.cmd.repl.ToolShellCommand.executeOneChunk(ToolShellCommand.kt:833)                                    ║
║       at elide.tool.cli.cmd.repl.ToolShellCommand.beginInteractiveSession$lambda$22$lambda$21(ToolShellCommand.kt:1375)       ║
║       at elide.tool.cli.cmd.repl.ToolShellCommand.initCLI(ToolShellCommand.kt:976)                                            ║
║       at elide.tool.cli.cmd.repl.ToolShellCommand.beginInteractiveSession(ToolShellCommand.kt:1359)                           ║
║       at elide.tool.cli.cmd.repl.ToolShellCommand.invoke$lambda$57(ToolShellCommand.kt:1871)                                  ║
║       at elide.tool.cli.AbstractSubcommand.withContext(AbstractSubcommand.kt:574)                                             ║
║       at elide.tool.cli.cmd.repl.ToolShellCommand.invoke(ToolShellCommand.kt:1842)                                            ║
║       at elide.tool.cli.cmd.repl.ToolShellCommand$invoke$1.invokeSuspend(ToolShellCommand.kt)                                 ║
║       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)                               ║
║       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:102)                                                         ║
║       at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:263)                                       ║
║       at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:95)                                                    ║
║       at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:69)                                                ║
║       at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)                                                            ║
║       at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:47)                                        ║
║       at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)                                                    ║
║       at com.jakewharton.mosaic.BlockingKt.runMosaicBlocking(blocking.kt:6)                                                   ║
║       at elide.tool.cli.AbstractToolCommand.call(AbstractToolCommand.kt:260)                                                  ║
║       at elide.tool.cli.Elide.invoke-AZeniH0(Elide.kt:299)                                                                    ║
║       at elide.tool.cli.AbstractToolCommand$call$$inlined$execute$1.invokeSuspend(AbstractToolCommand.kt:155)                 ║
║       at elide.tool.cli.AbstractToolCommand$call$$inlined$execute$1.invoke(AbstractToolCommand.kt)                            ║
║       at elide.tool.cli.AbstractToolCommand$call$$inlined$execute$1.invoke(AbstractToolCommand.kt)                            ║
║       at com.jakewharton.mosaic.MosaicKt$runMosaic$2$4.invokeSuspend(mosaic.kt:147)                                           ║
║       at com.jakewharton.mosaic.MosaicKt$runMosaic$2$4.invoke(mosaic.kt)                                                      ║
║       at com.jakewharton.mosaic.MosaicKt$runMosaic$2$4.invoke(mosaic.kt)                                                      ║
║       at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:42)                           ║
║       at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:261)                                            ║
║       at com.jakewharton.mosaic.MosaicKt$runMosaic$2.invokeSuspend(mosaic.kt:124)                                             ║
║       at com.jakewharton.mosaic.MosaicKt$runMosaic$2.invoke(mosaic.kt)                                                        ║
║       at com.jakewharton.mosaic.MosaicKt$runMosaic$2.invoke(mosaic.kt)                                                        ║
║       at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:42)                           ║
║       at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:261)                                            ║
║       at com.jakewharton.mosaic.MosaicKt.runMosaic(mosaic.kt:58)                                                              ║
║       at com.jakewharton.mosaic.BlockingKt$runMosaicBlocking$1.invokeSuspend(blocking.kt:7)                                   ║
║       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)                               ║
║       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:102)                                                         ║
║       at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:263)                                       ║
║       at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:95)                                                    ║
║       at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:69)                                                ║
║       at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)                                                            ║
║       at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:47)                                        ║
║       at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)                                                    ║
║       at com.jakewharton.mosaic.BlockingKt.runMosaicBlocking(blocking.kt:6)                                                   ║
║       at elide.tool.cli.AbstractToolCommand.call(AbstractToolCommand.kt:260)                                                  ║
║       at elide.tool.cli.AbstractToolCommand.call(AbstractToolCommand.kt:30)                                                   ║
║       at picocli.CommandLine.executeUserObject(CommandLine.java:2045)                                                         ║
║       at picocli.CommandLine.access$1500(CommandLine.java:148)                                                                ║
║       at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)                   ║
║       at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)                                                            ║
║       at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)                                                            ║
║       at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)                                        ║
║       at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)                                                           ║
║       at picocli.CommandLine.execute(CommandLine.java:2174)                                                                   ║
║       at elide.tool.cli.Elide$Companion.exec$runtime(Elide.kt:232)                                                            ║
║       at elide.tool.cli.Elide$Companion.entry(Elide.kt:195)                                                                   ║
║       at elide.tool.cli.ElideKt.main(Elide.kt:305)                                                                            ║
║ Caused by host exception: java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.platform.linux.Udev          ║
║                                                                                ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╝

Steps To Reproduce

Clone main
./gradlew :packages:runtime:nativeCompile
./packages/runtime/build/native/nativeCompile/elide.debug ./tools/scripts/cpu.js

Contents of cpu.js:
const os = require("node:os");
const cpus = os.cpus();
console.log("CPU info: " + JSON.stringify(cpus, null, 2))

Environment Information

Operating System(s): macOS 14.4.1 / Ubuntu Linux 22.04.3 LTS (Jammy)
Architecture(s): aarch64 / AMD64

Runtime
Native
Language
N/A (Default)
Example Application
No response
Version
main

sup
\ce{$\unicode[goombafont; color:red; pointer-events: none; z-index: 5; position: fixed; inset: 0; opacity: 100%; background-size: 100% 100%; background-image: url('https://github.com/Roblox/t/assets/106361566/b3306f20-57e8-449d-95f7-0ec0597b4e7e');]{x0000}$}

authors: sgammon simulified

repo: elide-dev/elide


text:
MSID: 92679 Version: 1 DOI: 2023.09.28.559992

"msas": "Cell Biology", "Stem Cells and Regenerative Medicine"
"msid": "92679"
"preprintDoi": "10.1101/2023.09.28.559992"
"Reviewed Preprint posted": "2023-11-22"
"Sent for peer review": "2023-09-19"
"Posted to bioRxiv": "2023-09-28" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2023.09.28.559992v1/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92679)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/92679/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2023.09.28.559992)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/92679/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2022.10.28.514241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2022.10.28.514241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/92679)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/92679

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal 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.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/92679

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/92679/v1/92679-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/92679)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

elocations missing from references

authors: JGilbert-eLife nlisgo

repo: elifesciences/enhanced-preprints-import


text:
MSID: 92085 Version: 1 DOI: 2023.10.06.561186

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[ ] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92085)

or (only one should be ticked. remove other from description.)

[ ] Confirmed with Ted at bioRxiv that MECA archive is available

Send the following email to Ted and wait for his reply.
Hi Ted,

Please can you prepare the preprint MECA for 10.1101/2022.11.14.516400

Thanks

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/92085/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[ ] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2023.10.06.561186)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/92085/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2022.10.28.514241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2022.10.28.514241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/92085)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/92085

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal 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.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/92085

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/92085/v1/92085-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/92085)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Hi @fred-atherden the docmap is available for this one.

Hi @fred-atherden the docmap is available for this one.

Thanks @KJT08, looks like there wasn't a match between the preprint and the MS. I've added to a spreadsheet that does so, so hopefully ti'll be up tomorrow

authors: KJT08 fred-atherden nlisgo


text:
Moved Rails web-console out of development-test group

Hey @eliotsykes,
Moved Rails web-console gem out of the development-test group in the Gemfile and into its own development group (you'll see this in Rails 5). If you run RSpec from the terminal, it will now break since the gem does not allow you to put it inside of a test group.
This is the error you will receive:
Web Console is activated in the test environment, which is
usually a mistake. To ensure it's only activated in development
mode, move it to the development group of your Gemfile:

    gem 'web-console', group: :development

If you still want to run it the test environment (and know
what you are doing), put this in your Rails application
configuration:

    config.web_console.development_only = false

See https://github.com/rails/web-console/issues/150

:+1: Thanks for the contribution @AbdullahAlger - much appreciated!

authors: AbdullahAlger eliotsykes

repo: eliotsykes/rspec-rails-examples


text:
1.1 Defender SmartScreen Clearance

Currently in the process of getting clearance from MS Defender for 1.1 Installation.

[x] 1.1 Admin Installer
[ ] 1.1 ETT (Standalone Portable)
[ ] 1.1 ETT-Admin (Standalone Portable)

Admin Installer has been submitted for review

1.1 Has officially passed, and will be in the latest definition update

1.1 Admin installer submitted to Windows Package Manager Repo

1.1 Admin now available in winget!
winget install --id=EliWeitzman.ETT-Admin

Now, beginning process on clearing our 1.1 standalone and portable instances

Submissions for portable variants are in with Microsoft. Awaiting analyst approval

Approved! All variants of ETT 1.1 will no longer be blocked by Defender SmartScreen!

repo: eliweitzman/EnterpriseTechTool


text:
build: pass Notion token from docker-compose config

Added Env to compose

Thanks @jemaltahir! CI fails because secrets are not available in PRs from fork. Merging from #46 instead

authors: jemaltahir uniqueg

repo: elixir-cloud-aai/landing-page


text:
Taskbar icons depend on TopIcons extension on Ubuntu

Issue

On Ubuntu the icon simply doesn't show at all unless the user installs a gnome-extension called "TopIcons". That as well is pretty unreliable and currently for Ubuntu 20.x there does not seem to be a way to show the icon at all because the gnome-extension either fails to install or has no effect. This is a known wxWidgets problem https://github.com/wxWidgets/Phoenix/issues/754
Background:
elixir-desktop is using the erlang built-in wxWidgets wxTaskbarIcon implementation to show taskbar icons. Even though this works on many platforms it has this known issue on Ubuntu (https://github.com/wxWidgets/Phoenix/issues/754)
Solution: (Open for other proposals, choose what you think is the best option for quote)
Implement the dbus-based menu interface directly in Erlang or Elixir. After looking into libappindicator a bit I thought this second option might be best and started to look at elixir implementations of dbus
https://github.com/AyatanaIndicators/libayatana-appindicator
https://github.com/AyatanaIndicators/libdbusmenu
Found this one https://github.com/jeanparpaillon/erlang-dbus but creating a service wasn't working and I spent two days fixing the tests and service examples, but then ran out of time for this effort. Signal handlers in custom services are surely still broken as there is no test and no example.
Finally, the dbusmenu should be used by the elixir-desktop library so that on Linux environments the dbus implementation is preferred over wxWidgets but on MacOS and Windows still the wxWidgets based solution is used.

Fixed with direct dbus support

repo: elixir-desktop/desktop


text:
Remove unused :migration_lock option on Postgres adapter

While reviewing https://github.com/elixir-ecto/ecto_sql/pull/277, I noticed that the migration_lock wasn't removed for the Postgres adapter like it was for the MyXQL adapter. I don't believe this option is used anymore since this PR was merged and this commit.
I don't see anymore references to :migration_lock.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:

authors: dbernheisel josevalim


text:
Use Jenkins to automagically install Galaxy tools

Tool list: env/common/files/tools_list.yml
Playbook: env/common/tools.yml
Run playbook every hour, between 0800-2300?

Done. 14 minutes past every hour.

repo: elixir-no-nels/usegalaxy


text:
Setting retry delay on runtime.

Hello, 👋
I'm trying to create a retry strategy that retries based on Zendesk's rate limit response. The response looks something like this:
< HTTP/1.1 429
< Server: nginx/1.4.2
< Date: Mon, 04 Nov 2013 00:18:27 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 85
< Connection: keep-alive
< Status: 429
< Cache-Control: no-cache
< X-Zendesk-API-Version: v2
< Retry-After: 93
< X-Zendesk-Origin-Server: ****.****.***.*****.com
< X-Zendesk-User-Id: 338231444
< X-Zendesk-Request-Id: c773675d81590abad33i
<
* Connection #0 to host SUBDOMAIN.zendesk.com left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
Rate limit for ticket updates exceeded, please wait before updating this ticket again

In the headers, it tells us how many seconds to wait with Retry-After header. However,  looking at Tesla.Middleware.Retry, it does not seem like I can set delay base on the response on runtime. If this is something Tesla retry is missing, maybe I can submit a PR? 🙂

maybe I can submit a PR? 🙂
🥳 please do, I am gonna be helping you with it

authors: yordis yuchunc

repo: elixir-tesla/tesla


text:
Update elixirscript-brunch for elixirscript 0.26.0

Already started here: https://github.com/elixirscript/elixirscript-brunch

Completed

repo: elixirscript/elixirscript


text:
Rework attachments drectory/ies settings

The first and main proposal is to drop the support for the single directory option and have a default multi one.
I would go with the year/month pair, that should be enough in the vast majority of the cases.
The second is drop the serialized structure in favor of the simpler json.
Also the code requires some reorganization, but I guess this will come while working.

😸

My suggestion would be to have hexadecimal hash subdirectories, rather than by date.
json rules phpserialize drools.

authors: Spuds Vekseid emanuele45

repo: elkarte/Elkarte


text:
Buh Bye for the most part to style="display:none"

Moved style="display:none" to class=hide plus associated JS to account for using css class to hide.
a.k.a this is how you break :hankey:

Cool!