text:
Repeated function definitions in the REPL trigger an ICE

Version: 0.2.0
After I typed the same function definition two times, the REPL crashed and reported an ICE.
> def f() = ()
f: () => Unit
> def f() = ()
Exception in thread "main" PlainTextError(Internal Compiler Error: Cannot find symbol for IdDef(f),None,Error)
        at effekt.util.messages$CompilerPanic$.apply(Messages.scala:37)
        at effekt.util.messages$ErrorReporter.panic(Messages.scala:97)
        at effekt.util.messages$ErrorReporter.panic$(Messages.scala:76)
        ...

Hey, thanks for reporting! This looks like a duplicate of #77

authors: b-studios waterlens

repo: effekt-lang/effekt


text:
🛑 CDN-Mikrotik-2 is down

In 7995ace, CDN-Mikrotik-2 (http://118.179.50.70) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CDN-Mikrotik-2 is back up in 2b153d8 after 10 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
surf: patch out gcr

as mentioned in #87

Thank you!

source: gharchive/pull-request

authors: ehawkvu hovercats

repo: ehawkvu/kiss-xorg


text:
Suggestion: Option to shorten video using FFMPEG

After running this program, I have separately been running an FFMPEG command which removes duplicate frames. This brings a 10 minute Sentry video down to about 2 minutes typically.
There are a couple ffmpeg commands that can remove duplicate frames.  What I like about the one I use is that it doesn't cut the video to the action, it takes out the intermediate frames.  This means I can watch the timestamp go through the full time of the video, but when there is no motion on screen, the timestamp runs very quick; when there is motion, the time runs at normal speed.
The ffmpeg command I use is:
ffmpeg -i "fileIN.mp4" -vf mpdecimate,setpts=N/FRAME_RATE/TB "fileIN-shortened.mp4"

I'm thinking this would add a tesla_dashcam argument of --shorten.  I'm not an ffmpeg expert, but I think this could be run concurrently with the concatenation (this would be the fastest if possible), or after the concatenation is complete.
Thanks for all the work you put into this!

Just tried that mpdecimate on a few of my clips and the result is fantastic. I would really like to see this added as well.
Just one issue I am seeing is that the clip is still reported as 10min long. Not sure if this is a bug or working as intended. So for example if it’s reduced to a 30sec clip. The progress bar and if you try to skip will only work on the first 5% of progress. The other 95% contains no data and will just end playback if you try to skip into it. From my perspective, the expected result would be a clip reported as a normal 30sec one, or 10min where you skip into the correct real life time and only playback time is sped up and slowed down.

@PiscisSwimeatus My clips report the new length.  My clips also don't have 95% without any data.  Can you provide more information on how you ran it?

I used the same command as above on some already merged clips.
For example
ffmpeg -i "2019-09-19T09-15-53_2019-09-19T09-26-08.mp4" -vf mpdecimate,setpts=N/FRAME_RATE/TB "2019-09-19T09-15-53_2019-09-19T09-26-08-shortened.mp4"
The original video is 9:51 long
The shortened video is 1:15 long
However both mediainfo, VLC and other players I tried reports the shortened video as still 9:51 long.

Which results in the progress stopping here in the players I tried:

My previous statement about 95% without data, just means trying anything after the 1:15 marks ends the video/no data.
I’ve uploaded the file here if you want to have a look:
https://ufile.io/2nk461em

Release 0.1.14 is out now including this enhancement. Issue that was mentioned here with chapters is resolved in this.

authors: PiscisSwimeatus ehendrix23 supRy


text:
What is the application version?

I am working on a Catalina 10.15.4.
When I tried to run this command:
docker build -f application/Dockerfile --build-arg JAR_FILE=application-*.jar -t ehrbaseorg/ehrbase:latest .
I replaced the application version with 0.13.0, as seen here:
docker build -f application/Dockerfile --build-arg JAR_FILE=application-0.13.0.jar -t ehrbaseorg/ehrbase:latest .
However, I got this result:
Sending build context to Docker daemon   30.4MB
Step 1/9 : FROM adoptopenjdk:11-jre-openj9
---> c0256f774b32
Step 2/9 : ARG JAR_FILE
---> Using cache
---> cc5639afc540
Step 3/9 : ENV AUTH_TYPE="BASIC"
---> Using cache
---> 132255153805
Step 4/9 : ENV AUTH_USER="ehrbase-user"
---> Using cache
---> 21a056a1bdd1
Step 5/9 : ENV AUTH_PASSWORD="SuperSecretPassword"
---> Using cache
---> 0defeb1133d9
Step 6/9 : COPY application/target/${JAR_FILE} app.jar
COPY failed: stat /var/lib/docker/tmp/docker-builder234823719/application/target/application-0.13.0.jar: no such file or directory
Did I key in the wrong application version? Thank you!

Hey @glenda-wee ! It looks like you were just trying to build the docker image locally, without building the application jar itself beforehand. So that's the reason the jar couldn't be found.
The most convenient solution would be to just use our pre-build docker image. Have a look here in the readme and here on docker hub.
Feel free to ask more questions or tell us how it worked out for you :)
Also, if you specifically want to continue to build the image locally, have a look here in the readme.

Hi @jakesmolka ! Thanks for your quick reply, I have followed the instructions and it appears to be running on the Docker desktop.
However, upon running the build EHRbase (executing the command mvn package), I encountered this error:
I'm rather new to OpenEHR, can I get your advice on this? Thanks a ton! :)

You need to build without executing the tests, as they need an additional test database.
Try running mvn -DskipTests package.
However, I think it would be more convenient to move the jar building to docker as well. To keep the image size reasonable small, the building container and the container for the final jar file could be separated.

@glenda-wee I would recommend to not build EHRbase locally, if you just want to use it (compared to developing). So I wouldn't execute anything with maven or java directly.
There are some approaches to get an EHRbase docker setup running. But the basic architecture is, that you will need the the postgres database and the EHRbase image to run configured containers with them.
For instance, in the docker hub link from above it states the following two commands:
First, to start the database:
docker run --name ehrdb --network ehrbase-net -d -p 5432:5432 -e POSTGRES_PASSWORD=postgres -e EHRBASE_USER=ehrbase -e EHRBASE_PASSWORD=ehrbase ehrbaseorg/ehrbase-postgres:latest
And second, to start EHRbase itself:
docker run --name ehrbase --network ehrbase-net -d -p 8080:8080 -e DB_URL=jdbc:postgresql://ehrdb:5432/ehrbase -e DB_USER=ehrbase -e DB_PASS=ehrbase -e SYSTEM_NAME=local.ehrbase.org ehrbaseorg/ehrbase:latest
Using those two should result in a running setup.
To verify that you could either peek into the docker logs or use a REST-tool like Postman or Insomia, to create a simple HTTP POST request pointing at http://localhost:8080/ehrbase/rest/openehr/v1/ehr. This should create an EHR.
From that point on you're in the realm of openEHR. Maybe have a look at our Getting Started page to learn more. If you're completely new to openEHR the concepts can be overwhelming. So if you stuck somewhere or just want to see a simple running example, ping us again. We are also in the process of extending our SDK documentation with a tutorial application, which I could give a sneak peak at.

Hi! I used the commands that you sent me and managed to get something up, but it showed a bad request:

May I know what the 'subject id' and 'subject namespace' parameters are? thank you!

You need to build without executing the tests, as they need an additional test database.
Try running mvn -DskipTests package.
However, I think it would be more convenient to move the jar building to docker as well. To keep the image size reasonable small, the building container and the container for the final jar file could be separated.

I tried this, but it resulted in the same error :(

I consider this issue as resolved. Please let me know if this is incorrect, then we can open again.

authors: Geisterfalle glenda-wee jakesmolka nr23730

repo: ehrbase/ehrbase


text:
Abort running suites using DELETE request

Applicable Issues

fixes: https://github.com/eiffel-community/etos/issues/209

Description of the Change
The change implements the handling of DELETE requests at the endpoint:
/etos/<suite_id>
Upon receiving a request to this endpoint, ETOS API deletes the corresponding Kubernetes job. If no job is found for the given suite id, a 404 response is returned.
Alternate Designs
Possible Drawbacks

etosctl needs to be adapted for this change to prevent infinite waiting loop when its suite is aborted

Sign-off
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
Signed-off-by: Andrei Matveyeu, andrei.matveyeu@axis.com

This is a new PR with the same changes as here: https://github.com/eiffel-community/etos-api/pull/55
A new PR due to conflicts/rebase errors.

repo: eiffel-community/etos-api


text:
All test do not run on Scala.js with Scala 3.0.0-M3

See https://github.com/lampepfl/dotty/issues/11276

Fixed in Scala 3.0.0-RC2

repo: ekrich/sjavatime


text:
Passing in separate values for tooltip padding not working

Setting tooltip_padding to a number works fine, but setting it to a list with two numbers does not work.
        ...
        self._tooltip_padding = None

    def _show_tooltip(self, x, y):

        if self._tooltip_padding is None:
            if isinstance(self.tooltip_padding, int):
                self._tooltip_padding = [self.tooltip_padding] * 2

            elif not (isinstance(self.tooltip_padding, list) and len(self.tooltip_padding) >= 2):
                logger.warning("Invalid tooltip padding. Defaulting to [4, 4]")
                self._tooltip_padding = [4, 4]

It looks like you are missing the case where the tooltip_padding input is correct and copied into _tooltip_padding.

Thanks for spotting that. Have submitted a fix.

authors: DeeeeLAN elParaguayo

repo: elParaguayo/qtile-extras


text:
Implement new command line option to optionally skip module tags

This is very useful for couple of reasons:

In Haskell almost always module names and file names are the same, e.g. module A.B.C is in A/B/C.hs etc. This makes finding modules very easy and tags are usually not necessary.

There's a very old bug that still effects my workflow: https://github.com/ctrlpvim/ctrlp.vim/issues/92 Because of this I need to be very careful with tags with same names. In Haskell we often have modules that define types with same names, e.g. TypeRep.hs defines the type TypeRep etc. This patch helps with avoiding the linked bug in these cases.

Thanks for fixing the build, not sure how that made it in :/
I actually use module tags when I want to get to a module but don't want to type the complete path.
Would it be simpler to filter the output of processFile rather than not generate the tags in the first place?  I worry about accumulation of config flags being passed everywhere.  It would also then be really easy to generalize to a "include only these types" flag... though let's not do that unless you can think of a good reason.

How does it look now? Tried to make it easier to extend.

I'd just filter directly, but I'll just merge now rather than micromanage you to death :)

repo: elaforge/fast-tags

license_source: bigquery


text:
external statement

(This ticket is a placeholder, just to ensure that this is covered in the new compile implementation, in case there are not any existing tests for system calls). There are two valid forms:
external pause(300) // for external procedure calls'
external random(1,6) into x //for external function calls (which might not be safe)
For this usage, x must be pre-defined as a variable of suitable type.
Changes to existing library functions
All methods defined previously in SystemAccessors and in Procedures' (though there seems to be a couple of duplications there which should be removed) should now be combined so that they all may be accessed only through the externalsyntax.  Withexternal` it is the responsibility of the user to know whether or not the method returns anything, and of what type - because (eventually) they may be accessing JavaScript methods. So we might as well adopt this practice for our own 'external' methods.
The runtime system should attempt to convert the type returned by the method into the type required. This can fail at run-time, and a suitable error thrown.

This specification is no longer valid.  See #407 instead

repo: elan-language/IDE


text:
Fixing eventlet tests

TFW you have no idea why the tests are failing...

:broken_heart: Tests Failed

Expand to view the summary

Build stats

Build Cause: [Pull request #890 opened]

Start Time: 2020-07-20T20:37:32.482+0000

Duration: 25 min 51 sec

Test stats :test_tube:

Test
Results

Failed
2

Passed
10649

Skipped
7859

Total
18510

Test errors
Expand to view the tests failures

Name: Initializing / Test / Python-python-3.9-rc-4 / test_transaction_with_eventlet – tests.contrib.test_eventlet

Age: 1
Duration: 10.274
Error Details: IndexError: list index out of range

Name: Initializing / Test / Python-pypy-3-1 / test_transaction_with_eventlet – tests.contrib.test_eventlet

Age: 1
Duration: 10.904
Error Details: IndexError: list index out of range

Steps errors
Expand to view the steps failures

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.7 eventlet-newest

Duration: 0 min 27 sec

Start Time: 2020-07-20T20:50:45.891+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.9-rc eventlet-newest

Duration: 0 min 29 sec

Start Time: 2020-07-20T20:50:01.497+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.9-rc eventlet-newest

Duration: 0 min 28 sec

Start Time: 2020-07-20T20:50:46.639+0000

log

Name: Error signal

Description: Python-python-3.9-rc-eventlet-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-07-20T20:51:15.033+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 eventlet-newest

Duration: 1 min 25 sec

Start Time: 2020-07-20T20:56:37.725+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 eventlet-newest

Duration: 1 min 27 sec

Start Time: 2020-07-20T20:58:40.623+0000

log

Name: Error signal

Description: Python-pypy-3-eventlet-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-07-20T21:00:07.709+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 django-1.11

Duration: 3 min 15 sec

Start Time: 2020-07-20T20:45:11.180+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 django-2.2

Duration: 3 min 23 sec

Start Time: 2020-07-20T20:45:04.850+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.9-rc-aiohttp-newest

Duration: 0 min 0 sec

Start Time: 2020-07-20T21:02:20.620+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-07-20T21:02:04.232Z] tests/instrumentation/redis_tests.py                         81     79      4      0     2%
[2020-07-20T21:02:04.232Z] tests/instrumentation/requests_tests.py                      92     90      0      0     2%
[2020-07-20T21:02:04.232Z] tests/instrumentation/sqlite_tests.py                        83     77      4      0     7%
[2020-07-20T21:02:04.232Z] tests/instrumentation/transactions_store_tests.py           251    211     22      0    15%
[2020-07-20T21:02:04.232Z] tests/instrumentation/urllib3_tests.py                      107     94      8      0    11%
[2020-07-20T21:02:04.232Z] tests/instrumentation/urllib_tests.py                       129    109      8      0    15%
[2020-07-20T21:02:04.232Z] tests/metrics/__init__.py                                     0      0      0      0   100%
[2020-07-20T21:02:04.232Z] tests/metrics/base_tests.py                                 107     90     16      0    14%
[2020-07-20T21:02:04.232Z] tests/metrics/breakdown_tests.py                            180    168     58      0     5%
[2020-07-20T21:02:04.232Z] tests/metrics/cpu_linux_tests.py                             56     43     10      0    20%
[2020-07-20T21:02:04.232Z] tests/metrics/cpu_psutil_tests.py                            27     22      4      0    16%
[2020-07-20T21:02:04.232Z] tests/middleware/__init__.py                                  0      0      0      0   100%
[2020-07-20T21:02:04.232Z] tests/middleware/tests.py                                    32     25      2      0    21%
[2020-07-20T21:02:04.232Z] tests/processors/__init__.py                                  0      0      0      0   100%
[2020-07-20T21:02:04.232Z] tests/processors/tests.py                                   145    111     12      0    22%
[2020-07-20T21:02:04.232Z] tests/transports/__init__.py                                  0      0      0      0   100%
[2020-07-20T21:02:04.232Z] tests/transports/test_base.py                               161    128     14      0    19%
[2020-07-20T21:02:04.232Z] tests/transports/test_urllib3.py                            201    164      8      0    18%
[2020-07-20T21:02:04.232Z] tests/utils/__init__.py                                       2      1      2      0    25%
[2020-07-20T21:02:04.232Z] tests/utils/cgroup_tests.py                                   7      3      0      0    57%
[2020-07-20T21:02:04.232Z] tests/utils/cloud_tests.py                                   30     21      0      0    30%
[2020-07-20T21:02:04.232Z] tests/utils/compat.py                                         4      3      2      0    17%
[2020-07-20T21:02:04.232Z] tests/utils/compat_tests.py                                  36     19      2      0    45%
[2020-07-20T21:02:04.232Z] tests/utils/encoding/__init__.py                              0      0      0      0   100%
[2020-07-20T21:02:04.232Z] tests/utils/encoding/tests.py                               124     99      8      0    19%
[2020-07-20T21:02:04.232Z] tests/utils/json_utils/__init__.py                            0      0      0      0   100%
[2020-07-20T21:02:04.232Z] tests/utils/json_utils/tests.py                              26     14      2      0    43%
[2020-07-20T21:02:04.232Z] tests/utils/stacks/__init__.py                               10      7      4      0    21%
[2020-07-20T21:02:04.233Z] tests/utils/stacks/tests.py                                 127    100     10      3    22%
[2020-07-20T21:02:04.233Z] tests/utils/test_disttracing_header.py                       42     31      0      0    26%
[2020-07-20T21:02:04.233Z] tests/utils/tests.py                                         69     45      2      0    34%
[2020-07-20T21:02:04.233Z] tests/utils/threading_tests.py                               37     31      2      0    15%
[2020-07-20T21:02:04.233Z] tests/utils/wsgi/__init__.py                                  0      0      0      0   100%
[2020-07-20T21:02:04.233Z] tests/utils/wsgi/tests.py                                    47     32      0      0    32%
[2020-07-20T21:02:04.233Z] -------------------------------------------------------------------------------------------
[2020-07-20T21:02:04.233Z] TOTAL                                                     10836   8076   1759    134    24%
[2020-07-20T21:02:04.233Z]
[2020-07-20T21:02:04.233Z] ============ 2 passed, 27 skipped, 459 deselected in 46.14 seconds =============
[2020-07-20T21:02:04.233Z] + cleanup
[2020-07-20T21:02:04.233Z] + '[' -n 1 ']'
[2020-07-20T21:02:04.233Z] + ./scripts/docker/docker-summary.sh
[2020-07-20T21:02:04.233Z] *******************************************************
[2020-07-20T21:02:04.233Z] ***************Docker Containers Summary***************
[2020-07-20T21:02:04.233Z] *******************************************************
[2020-07-20T21:02:04.233Z] CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
[2020-07-20T21:02:04.233Z] + PYTHON_VERSION=
[2020-07-20T21:02:04.233Z] + docker-compose down -v
[2020-07-20T21:02:04.811Z] Removing network tests_default
[2020-07-20T21:02:05.072Z] Removing volume tests_pypgdata
[2020-07-20T21:02:05.072Z] Removing volume tests_pymongodata30
[2020-07-20T21:02:05.072Z] Removing volume tests_pymongodata32
[2020-07-20T21:02:05.072Z] Removing volume tests_pymongodata34
[2020-07-20T21:02:05.072Z] Removing volume tests_pymongodata36
[2020-07-20T21:02:05.072Z] Removing volume tests_pyesdata7
[2020-07-20T21:02:05.072Z] Removing volume tests_pyesdata6
[2020-07-20T21:02:05.072Z] Removing volume tests_pyesdata5
[2020-07-20T21:02:05.072Z] Removing volume tests_pyesdata2
[2020-07-20T21:02:05.072Z] Removing volume tests_pycassandradata3
[2020-07-20T21:02:05.072Z] Removing volume tests_pymssqldata
[2020-07-20T21:02:05.072Z] Removing volume tests_mysqldata
[2020-07-20T21:02:05.072Z] + [[ -n '' ]]
[2020-07-20T21:02:05.207Z] Running in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-890/src/github.com/elastic/apm-agent-python
[2020-07-20T21:02:05.628Z] + chmod 755 docker-logs.sh
[2020-07-20T21:02:05.943Z] + ./docker-logs.sh Python-pypy-3-graphene-2 docker-compose.yml
[2020-07-20T21:02:05.975Z] Archiving artifacts
[2020-07-20T21:02:06.012Z] Recording test results
[2020-07-20T21:02:06.504Z] Stashed 1 file(s)
[2020-07-20T21:02:08.744Z] Post stage
[2020-07-20T21:02:09.060Z] + pip3 install --user coverage
[2020-07-20T21:02:10.443Z] Collecting coverage
[2020-07-20T21:02:11.015Z]   Downloading https://files.pythonhosted.org/packages/db/19/ad8f558e885a11a68111300ee23a632cc46a5ef6aaed875ba56460076fa7/coverage-5.2-cp36-cp36m-manylinux1_x86_64.whl (229kB)
[2020-07-20T21:02:11.015Z] Installing collected packages: coverage
[2020-07-20T21:02:11.015Z] Successfully installed coverage-5.2
[2020-07-20T21:02:11.042Z] Running in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-890/src/github.com/elastic/apm-agent-python
[2020-07-20T21:02:20.698Z] Error when executing always post condition:
[2020-07-20T21:02:20.698Z] hudson.AbortException: No such saved stash ‘coverage-python-3.9-rc-aiohttp-newest’
[2020-07-20T21:02:20.698Z] 	at org.jenkinsci.plugins.workflow.flow.StashManager.unstash(StashManager.java:159)
[2020-07-20T21:02:20.698Z] 	at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:76)
[2020-07-20T21:02:20.698Z] 	at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:63)
[2020-07-20T21:02:20.698Z] 	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
[2020-07-20T21:02:20.698Z] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[2020-07-20T21:02:20.698Z] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[2020-07-20T21:02:20.698Z] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[2020-07-20T21:02:20.698Z] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[2020-07-20T21:02:20.698Z] 	at java.lang.Thread.run(Thread.java:748)
[2020-07-20T21:02:20.698Z]
[2020-07-20T21:02:20.835Z] Stage "Building packages" skipped due to earlier failure(s)
[2020-07-20T21:02:20.928Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-07-20T21:02:21.017Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2020-07-20T21:02:21.214Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-07-20T21:02:21.255Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-07-20T21:02:21.347Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-07-20T21:02:21.437Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-07-20T21:02:22.118Z] Running on Jenkins in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-890
[2020-07-20T21:02:22.429Z] [INFO] getVaultSecret: Getting secrets
[2020-07-20T21:02:22.513Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-07-20T21:02:23.385Z] + chmod 755 generate-build-data.sh
[2020-07-20T21:02:23.385Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-890/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-890/runs/1 FAILURE 1490631
[2020-07-20T21:02:23.635Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-890/runs/1/steps/?limit=10000 -o steps-info.json
[2020-07-20T21:02:26.864Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-890/runs/1/tests/?status=FAILED -o tests-errors.json

Threw some sleeps in here because I cannot figure out what might have changed in our nightly builds. But even here, the sleeps are just making it fail in a flakey manner across a bunch of different matrix builds. It appears to be limited to py3.6+ and pypy-3.
Anyway, I'm probably going to ditch this problem for a couple of weeks until @beniwohli is around again.

authors: apmmachine basepi

repo: elastic/apm-agent-python


text:
VMExtensionProvisioningError deployment error

Hello,
I tried to deploy using powershell based on the supplied example, with the following parameters object:
$clusterParameters = @{
"esClusterName" = "elastic-weus1"
"xpackPlugins" = "No"
"dataNodesAreMasterEligible" = "Yes"
"adminUsername" = "admin"
"adminPassword" = "********************"
"securityAdminPassword" = ""
"securityReadPassword" = ""
"securityKibanaPassword" = "**********"
"location" = "westeurope"
}
Deployment of all data node VMs failed with the following error:
statusCode:Conflict statusMessage:{"status":"Failed","error":{"code":"ResourceDeploymentFailure","message":"The resource operation completed with terminal provisioning state 'Failed'.","details":[{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'script'. Error message: "Enable failed: failed to execute command: command terminated with exit status=2"."}]}}

Note that deployment of Kibana VM succeeded.

Please assist,
Ilya

Hmm this looks off exit code 2 is reserved for showing help:
https://github.com/elastic/azure-marketplace/blob/master/src/scripts/elasticsearch-ubuntu-install.sh#L169
Next week we are going to have another pass over the template and fixing outstanding issues. We'll definitely take this one on board.

Same issue here, not possible to deploy from within portal or using ARM.

Thanks for reporting @Ilya128 and @tibbing. I'm looking at this now.
Do you have additional deployment details for the failure, either from the portal or from the deployment log on the VM? The portal deployment details can be found by navigating via

The deployment log for the template can be found on the VM deployed to at
/var/log/arm-install.log

respectively

One thing that will cause it to fail is that admin is not an allowed Admin Username. See this list for invalid admin usernames. I'm fairly sure this gets caught before the deployment script runs though, upon provisioning the VM, so wouldn't cause the VMExtensionProvisioning error you saw.
I just ran a deployment with the following parameters:
$templateVersion = "c0664f94de618501c0662d50c89c008cd69906e1"
$elasticTemplate = "https://raw.githubusercontent.com/elastic/azure-marketplace/$templateVersion/src/mainTemplate.json"
$location = "westeurope"
$resourceGroup = "vm-provisioning"
$name = $resourceGroup

$clusterParameters = @{
  "artifactsBaseUrl"="https://raw.githubusercontent.com/elastic/azure-marketplace/$templateVersion/src"
  "esClusterName" = $name
  "xpackPlugins" = "No"
  "dataNodesAreMasterEligible" = "Yes"
  "adminUsername" = "russ"
  "adminPassword" = "Password1234"
  "securityAdminPassword" = ""
  "securityReadPassword" = ""
  "securityKibanaPassword" = ""
  "location" = "westeurope"
}

Write-Host "[$(Get-Date -format 'u')] Deploying cluster"
New-AzureRmResourceGroup -Name $resourceGroup -Location $location
New-AzureRmResourceGroupDeployment -Name $name -ResourceGroupName $resourceGroup -TemplateUri $elasticTemplate -TemplateParameterObject $clusterParameters
Write-Host "[$(Get-Date -format 'u')] Deployed cluster"

c0664f94de618501c0662d50c89c008cd69906e1 is the git commit prior to a PR that was just merged in. This failed with exit code 1
{
  "status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "DeploymentFailed",
        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
        "details": [
          {
            "code": "Conflict",
            "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"VMExtensionProvisioningError\",\r\n        \"message\": \"VM has reported a failure when processing extension 'script'. Error message: \\\"Enable failed: failed to execute command: command terminated with exit status=1\\\".\"\r\n      }\r\n    ]\r\n  }\r\n}"
          }
        ]
      }
    ]
  }
}

Digging into the details on the VM, it isn't clear why this failed. I suspect it's due to the security* passwords being empty and the parameter values not being quoted when passed to the bash deployment script. Re-running the same script replacing $templateVersion value with "master", which does quote security* password values, the cluster successfully deploys.
@Ilya128, would you be able to try your deployment again, targeting $templateVersion = "78ed10d63b2f5fe040015c6feb954f39e8c3698f" (latest master at this time)?
@tibbing, The portal always deploys with X-Pack plugins installed and security passwords are enforced to be required in the Portal UI, so the above issue would not affect a portal deployment. Could you provide more detail on the error message you get in the portal, and the parameters that you're using?

(colleague to @tibbing)
Error messages reported when deploying via portal:
{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
"details": [{
"code": "Conflict",
"message": {
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [{
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'script'. Error message: " Enable failed: failed to execute command: command terminated with exit status = 2"
}
]
}
}
}
]
}
]
}
}
Summary of the parameters :
Basics
Subscription
hidden
Resource group
hidden
Location
West Europe
User name
hidden
Password

Cluster Settings
Elasticsearch version
v5.1.2
Cluster name
hidden
Virtual network
es-net
subnet
es-subnet
subnet address prefix
10.3.0.0/24
Nodes Configuration
Hostname prefix
vm-
Number of data nodes (if not using dedicated masters, >= 3 data nodes)
3
Data node VM size
Standard DS1 v2
Data nodes are master eligible
No
Master node VM size
Standard D1
Number of client nodes
2
Client node VM size
Standard D1
User Configuration
(es_admin or elastic) password

es_read Password

es_kibana Password

External Access Control
Install Kibana?
Yes
Kibana VM size
Standard D1
Use a jump box?
No
Load balancer type
External
User Information
Company
hidden
Email address
hidden
First name
hidden
Last Name
hidden
Job title
IT Executive (CIO, CTO, VP Engineering, etc.)
Country
SWEDEN

The script works only when xpackPlugins is set to "No", however we would like to use X-Pack, any idea how we can make it work?

Thanks for the details for the portal deployment, @funrockstefan. I'm looking at this now.
With the template deployment, what parameters are you using?

Template parameters when it fails:
(If we change xpackPlugins to "No" it works fine)
$templateVersion = "c0664f94de618501c0662d50c89c008cd69906e1"
$parameters.Add(“artifactsBaseUrl”, "https://raw.githubusercontent.com/elastic/azure-marketplace/$templateVersion/src")
$parameters.Add(“esVersion”, "5.1.2")
$parameters.Add(“esClusterName”, [hidden])
$parameters.Add(“azureCloudPlugin”, "No")
$parameters.Add(“xpackPlugins”, "Yes")
$parameters.Add(“esAdditionalPlugins”, "")
$parameters.Add(“loadBalancerType”, "internal")
$parameters.Add(“vNetNewOrExisting”, "new")
$parameters.Add(“vNetName”,  "$clusterName-net")
$parameters.Add(“vNetClusterSubnetName”, "$clusterName-subnet")
$parameters.Add(“vNetLoadBalancerIp”, "10.3.0.4")
$parameters.Add(“vNetExistingResourceGroup”, $resourceGroupName)
$parameters.Add(“vNetNewAddressPrefix”, "10.3.0.0/16")
$parameters.Add(“vNetNewClusterSubnetAddressPrefix”, "10.3.0.0/24")
$parameters.Add(“kibana”, "Yes")
$parameters.Add(“jumpbox”, "No")
$parameters.Add(“vmSizeDataNodes”, "Standard_DS2_v2")
$parameters.Add(“vmDataNodeCount”, 3)
$parameters.Add(“dataNodesAreMasterEligible”, "No")
$parameters.Add(“vmHostNamePrefix”, "eaavm")
$parameters.Add(“vmSizeMasterNodes”, "Standard_D2_v2")
$parameters.Add(“vmClientNodeCount”, 2)
$parameters.Add(“vmSizeClientNodes”, "Standard_D1_v2")
$parameters.Add(“vmSizeKibana”, "Standard_D1_v2")
$parameters.Add(“adminUsername”, [hidden])
$parameters.Add(“authenticationType”, "password")
$parameters.Add(“adminPassword”, [hidden])
$parameters.Add(“securityAdminPassword”, [hidden])
$parameters.Add(“securityReadPassword”, [hidden])
$parameters.Add(“securityKibanaPassword”, [hidden])
$parameters.Add(“location”, "westeurope")
$parameters.Add(“userCompany”, [hidden])
$parameters.Add(“userEmail”, [hidden])
$parameters.Add(“userFirstName”, [hidden])
$parameters.Add(“userLastName”, [hidden])
$parameters.Add(“userJobTitle”, "IT Executive (CIO, CTO, VP Engineering, etc.)")
$parameters.Add(“userCountry”, "Sweden")

Thanks @funrockstefan.
I ran a few deployments from the portal earlier with the portal parameters you provided, and they all deployed successfully. I'm keen to get to find out what the issue is here though; with a failed portal deployment, would you be able to ssh into one of the failed VM script deployment boxes and provide the (obsfucated out sensitive data)  contents of /var/log/arm-install.log?
Could you try your parameters above targeting master i.e.
$templateVersion = "master"

and let me know the outcome?

Good news: Script and Template now works, thanks for your help @russcam

That's good to hear @funrockstefan 😃
@Ilya128, could you also try with $templateVersion = dec7dde7cbdf49f611dea778e9f479edd51cd335 (latest master) ?

Closing this as no additional feedback received.
Feel free to reopen if the problem still exists 👍

authors: Ilya128 Mpdreamz funrockstefan russcam tibbing

repo: elastic/azure-marketplace

license: mit


text:
Install Kibana Shield plugin as part of template

Today, when the template installs, we do not install the Kibana Shield plugin. Mostly, this is ok, however, the following problems are present:

Graph UI does not work. When you click on the search button, you get an "Unauthorized Operation" at the top, and no apparent errors in any logs.

No logout button is available in Kibana. You have to brute force switching users.

I recall a conversation about choosing not to do this because we were going to need to set up SSL. We could either set up SSL, or possibly allow a flag in the config to not require SSL for the plugin.
I would make this a pretty high priority. We want our marketplace offering to match our product offering. Could we model what we do in cloud?

I've just pushed a commit that installs Shield in Kibana for Elasticsearch versions greater than 2.4.0.
In order for shield to work, two settings need to be set in kibana.yml
shield.useUnsafeSessions: true
shield.skipSslCheck: true

this allows shield with Kibana to bypass checking that it's running over HTTPS and also allow it to send the session/authentication cookie over HTTP. I have added a note to the README to highlight that these should be removed  and transport layer security is strongly recommended before going into production.

authors: cjgeode russcam


text:
Scope of Refresh API call when writing

What kind an issue is this?

[x] Bug report. If you’ve found a bug, please provide a code snippet or test to reproduce it below.
The easier it is to track down the bug, the faster it is solved.

Issue description
See the following post
I'm seeing "Read" timeouts with Flush API calls when ingesting to ES using SPARK with the default setting es.batch.write.refresh=true And it doesn't seem to relate to tuning Bulk request size because when I set es.batch.write.refresh=false and index.refresh_interval='30s' I don't get the timeout.

What's the best practice for configuring refresh when writing a Spark ingest job?
When running Spark job, how often does refresh API get called? Is it per Spark job, stage or task? Or something smaller?

I see the following code. Is my understanding correct that Structured Streaming uses EsRDDWriter and the scope of writer (which calls refresh API when closing) is a Spark task?
Is the refresh API call per index (or per shard)?
When multiple tasks finish around the same time, is it possible that the code above is calling refresh API multiple times at the same time? Could it cause performance issue on ES side?
Is there a known performance issue with ES-Hadoop's refresh call when there's a large parallelism?

Steps to reproduce
Code:

Using Spark Structured Streaming, write to Elastic Search.

Strack trace:
19/09/03 20:37:50 TRACE NetworkClient: Caught exception while performing request [<redacted>:9200][/_refresh] - falling back to the next node in line...
java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
	at java.net.SocketInputStream.read(SocketInputStream.java:170)
	at java.net.SocketInputStream.read(SocketInputStream.java:141)
	at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
	at sun.security.ssl.InputRecord.read(InputRecord.java:503)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
	at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930)
	at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
	at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
	at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
	at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
	at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
	at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
	at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
	at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
	at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
	at org.elasticsearch.hadoop.rest.commonshttp.CommonsHttpTransport.execute(CommonsHttpTransport.java:489)
	at org.elasticsearch.hadoop.rest.pooling.TransportPool$LeasedTransport.execute(TransportPool.java:235)
	at org.elasticsearch.hadoop.rest.NetworkClient.execute(NetworkClient.java:115)
	at org.elasticsearch.hadoop.rest.RestClient.execute(RestClient.java:398)
	at org.elasticsearch.hadoop.rest.RestClient.execute(RestClient.java:362)
	at org.elasticsearch.hadoop.rest.RestClient.execute(RestClient.java:366)
	at org.elasticsearch.hadoop.rest.RestClient.refresh(RestClient.java:267)
	at org.elasticsearch.hadoop.rest.bulk.BulkProcessor.close(BulkProcessor.java:550)
	at org.elasticsearch.hadoop.rest.RestRepository.close(RestRepository.java:219)
	at org.elasticsearch.hadoop.rest.RestService$PartitionWriter.close(RestService.java:121)
	at org.elasticsearch.spark.rdd.EsRDDWriter$$anonfun$write$1.apply(EsRDDWriter.scala:60)
	at org.elasticsearch.spark.rdd.EsRDDWriter$$anonfun$write$1.apply(EsRDDWriter.scala:60)
	at org.apache.spark.TaskContext$$anon$1.onTaskCompletion(TaskContext.scala:128)
	at org.apache.spark.TaskContextImpl$$anonfun$markTaskCompleted$1.apply(TaskContextImpl.scala:118)
	at org.apache.spark.TaskContextImpl$$anonfun$markTaskCompleted$1.apply(TaskContextImpl.scala:118)
	at org.apache.spark.TaskContextImpl$$anonfun$invokeListeners$1.apply(TaskContextImpl.scala:131)
	at org.apache.spark.TaskContextImpl$$anonfun$invokeListeners$1.apply(TaskContextImpl.scala:129)
	at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
	at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48)
	at org.apache.spark.TaskContextImpl.invokeListeners(TaskContextImpl.scala:129)
	at org.apache.spark.TaskContextImpl.markTaskCompleted(TaskContextImpl.scala:117)
	at org.apache.spark.scheduler.Task.run(Task.scala:125)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:345)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
19/09/03 20:37:50 ERROR NetworkClient: Node [<redacted>:9200] failed (Read timed out); selected next node [<redacted>:9200]

Version Info
OS:         :  Centos 7
JVM         :  1.8
Hadoop/Spark: 2.3.2
ES-Hadoop   :  6.5.4
ES          :  6.5.4

These are great questions for the forum, which I see you have already posted on. Since I've already responded on there, and this doesn't look like an actual bug, I'll close this issue out and further discussion can take place on the forum. Thanks!

authors: danielyahn jbaiera

repo: elastic/elasticsearch-hadoop


text:
What version of elasticsearch-spark or elasticsearch-hadoop should I use for Spark 1.4.1

Hi,
I was trying to use spark 1.4.1 to connect to elasticsearch 1.4.4
I have use elasticsearch-hadoop-2.1.0.jar and elasticsearch-hadoop-2.1.1.jar
by running spark-shell with the following commands
spark-shell --jars lib/elasticsearch-hadoop-2.1.0.jar --conf spark.es.nodes=[servername] --conf spark.es.port=9200 --conf spark.es.net.http.auth.user=[user] --conf spark.es.net.http.auth.pass=[password] --conf spark.es.nodes.discovery=false --conf spark.es.http.timeout=5m

and run the following commands on shell
import org.apache.spark.SparkContext
import org.apache.spark.SparkContext._
import org.elasticsearch.spark._
sc.esRDD("logstash-2015.09.09/haproxy_http_clf","?q=http_status_code:400")
res0.count
res0.take(1)

but somehow the result returns
scala> sc.esRDD("logstash-2015.09.09/haproxy_http_clf","?q=http_status_code:400")
res0: org.apache.spark.rdd.RDD[(String, scala.collection.Map[String,AnyRef])] = ScalaEsRDD[0] at RDD at AbstractEsRDD.scala:17

scala> res0.count
res1: Long = 2639

scala> res0.take(1)
15/09/18 05:04:04 INFO Version: Elasticsearch Hadoop v2.1.1 [a1fc48457b]
java.lang.NullPointerException
        at org.elasticsearch.hadoop.rest.RestClient.esVersion(RestClient.java:411)
        at org.elasticsearch.hadoop.rest.InitializationUtils.discoverEsVersion(InitializationUtils.java:125)
        at org.elasticsearch.hadoop.rest.RestService.findPartitions(RestService.java:231)
        at org.elasticsearch.spark.rdd.AbstractEsRDD.esPartitions$lzycompute(AbstractEsRDD.scala:61)
        at org.elasticsearch.spark.rdd.AbstractEsRDD.esPartitions(AbstractEsRDD.scala:60)
        at org.elasticsearch.spark.rdd.AbstractEsRDD.getPartitions(AbstractEsRDD.scala:27)
        at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:219)
        at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:217)
        at scala.Option.getOrElse(Option.scala:120)
        at org.apache.spark.rdd.RDD.partitions(RDD.scala:217)
        at org.apache.spark.rdd.RDD$$anonfun$take$1.apply(RDD.scala:1255)
        at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:147)
        at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:108)
        at org.apache.spark.rdd.RDD.withScope(RDD.scala:286)
        at org.apache.spark.rdd.RDD.take(RDD.scala:1250)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:38)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:43)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:45)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:47)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:49)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:51)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:53)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:55)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:57)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:59)
        at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:61)
        at $iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:63)
        at $iwC$$iwC$$iwC$$iwC.<init>(<console>:65)
        at $iwC$$iwC$$iwC.<init>(<console>:67)
        at $iwC$$iwC.<init>(<console>:69)
        at $iwC.<init>(<console>:71)
        at <init>(<console>:73)
        at .<init>(<console>:77)
        at .<clinit>(<console>)
        at .<init>(<console>:7)
        at .<clinit>(<console>)
        at $print(<console>)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
        at org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1338)
        at org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
        at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
        at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
        at org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:857)
        at org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:902)
        at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
        at org.apache.spark.repl.SparkILoop.processLine$1(SparkILoop.scala:657)
        at org.apache.spark.repl.SparkILoop.innerLoop$1(SparkILoop.scala:665)
        at org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$loop(SparkILoop.scala:670)
        at org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply$mcZ$sp(SparkILoop.scala:997)
        at org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
        at org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
        at scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135)
        at org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$process(SparkILoop.scala:945)
        at org.apache.spark.repl.SparkILoop.process(SparkILoop.scala:1059)
        at org.apache.spark.repl.Main$.main(Main.scala:31)
        at org.apache.spark.repl.Main.main(Main.scala)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:665)
        at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:170)
        at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:193)
        at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:112)
        at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)

can someone help me ?
Thanks

Looks like you bumped into a NPE caused by trying to diagnose/log what's wrong in detecting the ES version (incorrect port or response maybe due to a proxy).
Fixed in master and 2.1.x.
Cheers,

Hi ,
I trying to test integration of spark with SearchGuard && ES using Kerberos
is it posible ?
I dont figure out how to pass kerberos information spark conf
thanks for your response

@zooming1983 Please use the dedicated forum for questions not the issue tracker.
Thanks,

authors: andrimirandi costin zooming1983


text:
Update stale examples in the documentation

To avoid further confusion as seen here:
https://github.com/elasticsearch/elasticsearch-net/issues/611
and couple of other issues.
Look into the scribble project that @shiftkey started which can scan the source code (i.e tests) for snippets while generating docs. Last I looked at it was a bit too powershell oriented and my powershell-fu is lacking.

We are working on combining roslyn based literate programming, unit and integration testing all in a single for our 2.0 architecture.
This will solve the stale code in documentation because all the code in the documentation will be actual code :)

We are working on combining roslyn based literate programming, unit and integration testing all in a single project for our 2.0 architecture.

@Mpdreamz Could you give a link to this combination in code of NEST?  I can't find anything like this in docs directory in branch "2.0".  It is interesting especially literate programming with Roslyn but I can't find it in Google.

For now much of it lives here:
https://github.com/elastic/elasticsearch-net/tree/spike/literate-tests/src/Tests/Nest.Tests.Literate
With the actual tooling going over our tests generating documentation from the markdown comments here:
https://github.com/elastic/elasticsearch-net/tree/spike/literate-tests/src/CodeGeneration/Nest.Litterateur
We spiked the whole feedback loop and will move on this sooner then later (and blog about it of course :))

authors: Mpdreamz tkirill

repo: elastic/elasticsearch-net


text:
Apply codegenNames for union parameters

As titled.

Docs failure is unrelated


text:
[5.x] Adds option available in 5.x to use v6 API format

This was added in https://github.com/elastic/kibana/pull/10481

Thanks so much for keeping this in sync with Kibana proper. Does this apply to all 5.x versions?

No problem - trying to come up with a better way to manage this or capture a full list of options but I will update for now.
This option is being added to Kibana in 5.4.

Merged this manually. Thanks again!

https://github.com/elastic/kibana-docker/commit/dc6f87f910a6bb6c9ce37ad6d68653c83b4825d2

authors: jarpy tylersmalley

repo: elastic/kibana-docker


text:
Harmonize wording arch diagrams

What this PR does / why we need it:
This PR aims to use the terminology in our glossary page in the arch diagrams indocumentation.
Which issue this PR fixes
This PR closes #629
Public facing documentation PR
N/A
Special notes for reviewer:
N/A
Add a screenshot or an example to illustrate the proposed solution:
N/A
Checklist:

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

[X] 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):

[X] 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
N/A

@cristiklein the requested changes are now done. Thanks!

repo: elastisys/compliantkubernetes


text:
func AlwaysMitm is a function deal with https, what's the http one?

func AlwaysMitm is a function deal with https, what's the http one?

AlwaysMITM is used only by a request that sends a CONNECT.
It's sent only with HTTPS request, with normal HTTP request it's not present and you directly handle them using the Do() function.

repo: elazarl/goproxy


text:
fix hijack compatibility related to RSA key length and cert common name; add ConnectDialToProxy handler for NewConnectDialToProxyWithHandler

fix hijack compatibility related to RSA key length and cert common name
add ConnectDialToProxy handler for NewConnectDialToProxyWithHandler

@elazarl
Could you please have a review of this PR?
I have projects rely on this PR.
Thanks in advance.


text:
Refactor keyboard support code

#7 This is a bit cleaner

Thank you!

authors: flurmbo xxczaki

repo: elcalc/elcalc


text:
added cart ajax controller

PR Proposal for Ajax service to add/remove products from the cart #253

I don't really like the word AJAX. We should do exactly the same, but

Using REST architecture
with /api prefix

agree :+1:

authors: claretcrab mmoreram

repo: elcodi/bamboo


text:
Major upgrade process

I've been working on implementing a database based on pglite for a little bit, and during this process I updated from 0.1.5 to 0.2.5, after which I received this error (reproduced in a temporary directory, since I lost my original output):
wasm://wasm/postgres.wasm-023f75ca:1

RuntimeError: unreachable
    at postgres.wasm.ValidatePgVersion (wasm://wasm/postgres.wasm-023f75ca:wasm-function[4079]:0x22d00e)
    at postgres.wasm.checkDataDir (wasm://wasm/postgres.wasm-023f75ca:wasm-function[4078]:0x22cda3)
    at postgres.wasm.AsyncPostgresSingleUserMain (wasm://wasm/postgres.wasm-023f75ca:wasm-function[8691]:0x370caa)
    at postgres.wasm.pg_initdb (wasm://wasm/postgres.wasm-023f75ca:wasm-function[13269]:0x522243)
    at Module._pg_initdb (file:///tmp/tmp.SAT8EtxmTE/drizzletest/node_modules/@electric-sql/pglite/dist/postgres.js:10625:109)
    at Ct.As (file:///tmp/tmp.SAT8EtxmTE/drizzletest/node_modules/@electric-sql/pglite/dist/index.js:1:29075)
    at async Ct._e (file:///tmp/tmp.SAT8EtxmTE/drizzletest/node_modules/@electric-sql/pglite/dist/index.js:1:30858)
    at async Ct.query (file:///tmp/tmp.SAT8EtxmTE/drizzletest/node_modules/@electric-sql/pglite/dist/index.js:1:24527)
    at async PgDialect.migrate (file:///tmp/tmp.SAT8EtxmTE/drizzletest/node_modules/drizzle-orm/pg-core/dialect.js:48:5)
    at async migrate (file:///tmp/tmp.SAT8EtxmTE/drizzletest/node_modules/drizzle-orm/pglite/migrator.js:4:3)

This indicates to me that the update to v16 (#112) broke backwards compatibility pretty spectacularly.
It's not an issue for me now (my code hasn't been rolled out yet), but I'd like to continue using pglite for this project, and I'd like to be able to continue updating it; is there any guidance on how to properly upgrade, or any plans to put together such a process?

Hey @demize
Apologies for the confusion on that one. Postgres maintains binary compatibility within each of its major versions, but not access them. And as you noted we upgraded from a v15dev to v16 release.
Until we reach v1.0, minor changes may break compatibility. I hope we can reach a v1 in the next few months, we may have upgraded to PG v17 by then.
After that any time we upgrade to a new major PG version it will be a major version change to PGlite.
To aid in migrations between versions we are working on a WASM build of pg_dump and pg_restore, so that you can take a SQL dump of the old database and import into a new database. We will not move to v1 until we have this, and the plan is this would be available before we upgrade to PG v17, but I don't want to make that a firm promise.
I hope thats enough assurance there is a plan in place.

authors: demize samwillis

repo: electric-sql/pglite


text:
Tidy Up VisualStudio (w/ VGDB) file locations, and update to be functional

Most of the VisualStudio/VisualGDB stuff is fairly out of date.
There are a few things that we should fix while/before updating to the latest BSPs, etc.

.vs/ directory contains some hidden files, and many of the projects cloned from earlier projects have useless data here.
all visual studio related files (.vcxproj, filters, props, xml, etc.) should be able to be neatly relocated in a visualstudio/ directory instead of floating in each directory
the new structure should be set up with latest BSPs in a functional example, and that should be used as the template.

This will happen alongside #110
the new directory is called vs and should match the Template in utils/Template
Ideally with the modifications of the copy/create script we could have an 'update' script that updates the supplementary (non-cpp/h files) with the latest configuration. i.e. adding .vscode and vs dirs and their contents to examples that do not have them yet.

done and added to all existing  examples.

repo: electro-smith/DaisyExamples


text:
chore: update fs-extra to 4

To reduce client node_modules size.
note: I am going to send number of PR and so, when this PR will be accepted, you can postpone publish to npm until all PR will be not accepted.

Totally didn't show up in my notifications till just now 😕
Overally looks fair enough, looked at the changelogs for all bumped modules and it looks OK.  One concern it the adoption of yarn.  No other core repositories (electron, electron-prebuilt, etc.) have adopted yarn yet and in general lock files don't work well cross-platform (so electron dev with yarn is kinda not working too well).  This might just need to be a discussion we have somewhere that says "should we use it".  But for now, if we remove it from this PR I'm happy to approve it.

I just want to speedup installation on CI (according to my experience, yarn works better than npm without global cache (cache on CI doesn't make any sense)). But of course — it depends and for this project doesn't matter. Removed.

didn't show up in my notifications till just now

Yeach... Still no luck to get rid of electron-download-tf because when one my PR is accepted, I need to apply another one :(

@malept Yarn is used only on CI server and doesn't impact local users. yarn.lock removed.

@develar Only thing blocking this rn is the yarn stuff which we don't want to adopt here without a broader discussion, it might make tests slightly faster but it also results in different testing conditions to those people using npm.
A wider discussion needs to be had about supporting yarn with -userland modules, in particular things like cross-platform lock files need to be talked about.  But this PR isn't the place for that, happy to merge this once yarn is moved out and we can open a discussion issue somewhere else RE yarn.

@MarshallOfSound Thanks a lot for breaking the silence. yarn removed on CI servers.

@develar Second time the build timed out on macOS, I reran it the first time.  Any ideas whether the fs bump could have caused the hang?
https://travis-ci.org/electron-userland/electron-download/jobs/270780729

@MarshallOfSound It was ok 16 days ago (and when PR was submitted). I will check.

Stability — electron-builder uses electron-download-tf (this PR and #60 and not yet filed muon support). So, it is widely tested already.

authors: MarshallOfSound develar

repo: electron-userland/electron-download


text:
Allow to install multiple binaries

Related NW.js issue:
https://github.com/nwjs/npm-installer/issues/47
I was wondering if the electron prebuilt could install multiple binaries for different operating systems in a same place, so, by suggestion, by modifying the path of ./electron-prebuilt/dist/ to ./eletron-prebuilt/dist/win32-x64/, ./eletron-prebuilt/dist/win32-ia32/, ./eletron-prebuilt/dist/linux-x64/, ./eletron-prebuilt/dist/darwin-x64/ and so on so it could be dynamically set with process.platform & process.arch.
Please, see my request for NW.js via their npm installer for details about the motivation.
Thank you!

The electron-prebuilt repo is being retired and its code has been moved into the electron/electron repo. For the sake of historical transparency, we will leave GitHub Issues enabled on this repository, but if you are still affected by the issue reported here, please open a new issue on electron/electron repo and reference this issue from it so people can get the full context. The electron repository has a large and active contributor community, so your issue is more likely to get the attention it deserves there. Thanks!

authors: silverkorn zeke

repo: electron-userland/electron-prebuilt


text:
build: update lockfile

Inspiration from @refi64 who submitted another PR for this, but since lockfile changes must come a maintainer, I'm this PR does the same: update the lockfile to avoid WARN old lockfile warnings.
No manual changes; the lockfile updated when I ran npm install with npm 8.6.0:
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile

added 91 packages, and audited 92 packages in 3s

9 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Good day
Do whatever you can on your side for me also for our benefit I give full
permission go ahead.
UK Bhinbahadur
If you can do a file orders extract on me and repopulate that should have
greater day than what shown.
On Wed, 10 Aug 2022, 20:41 Erick Zhao, @.***> wrote:

Merged #601 https://github.com/electron/electron-quick-start/pull/601
into master.
—
Reply to this email directly, view it on GitHub
https://github.com/electron/electron-quick-start/pull/601#event-7166281507,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEXF3XZAIG6XCDPCLHADV2TVYPZUZANCNFSM5UMQPTCA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

authors: BhinbahadurUK ckerr

repo: electron/electron-quick-start


text:
"Error /bin/sh: Not a directory" while trying to run packaged app

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
7.3.0
Electron version
v29.1.1
Operating system
macOS 14.0
Last known working Electron Forge version
No response
Expected behavior

Actual behavior
Error: /bin/sh: /Users/m/code/cycletls-app/out/make/zip/darwin/arm64/cycletls-app.app/Contents/Resources/app.asar/node_modules/cycletls/dist/index-mac-arm64: Not a directory

    at Socket.<anonymous> (/Users/m/code/artic/cycletls-app/out/make/zip/darwin/arm64/cycletls-app.app/Contents/Resources/app.asar/node_modules/cycletls/dist/index.js:89:29)
    at Socket.emit (node:events:514:28)
    at addChunk (node:internal/streams/readable:376:12)
    at readableAddChunk (node:internal/streams/readable:349:9)
    at Readable.push (node:internal/streams/readable:286:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)

Steps to reproduce
git clone git@github.com:mlshv/cycletls-app.git
cd cycletls-app
npm install
npm run make
cd ./out/make/zip/darwin/arm64
unzip cycletls-app-darwin-arm64-1.0.0.zip
./cycletls-app.app/Contents/MacOS/cycletls-app

Additional information
No response

(...) app.asar/node_modules/cycletls/dist/index-mac-arm64(...)

Looks like you have a native module or binaries packed in app.asar. You might want to have that extracted in a directory, like app.asar.unpacked.

repo: electron/forge


text:
🛑 Ombi is down

In a16c14b, Ombi (https://ombi.lepallec.tv) was down:

HTTP code: 403
Response time: 70 ms

Resolved: Ombi is back up in 00b1468.

repo: elepallec/upptime


text:
🛑 UCU - Campus is down

In a2078b5, UCU - Campus (https://moodle.ucu.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UCU - Campus is back up in 3e6a9d6.

repo: elfoche/monitoreo


text:
Elementum is crashing from today not opening on Kodi android tv.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Version used:

Environment name and version:

Operating System and version:

Link to Kodi debug log:

Meybe this would help.
https://github.com/elgatito/plugin.video.elementum/issues/646

@kumar624 Should work fine with latest Elementum version. If not - please, share Kodi log, as issue template is asking to.

authors: elgatito kumar624 pavelmxx


text:
Throws error on storybook 8

As mentioned here https://github.com/storybookjs/storybook/issues/26031 ,
The error I get as follows
node_modules/storybook-addon-deep-controls/index.d.ts:6:8 - error TS2307:
Cannot find module '@storybook/types' or its corresponding type declarations.

6 } from "@storybook/types";

@technbuzz I've added @storybook/types as a peer dependency and published v0.6.3, see justification in #18

Now I get different error on version 0.7.0
ERROR in node_modules/.pnpm/storybook-addon-deep-controls@0.7.0_@storybook+addon-controls@8.2.8_@storybook+types@8.2.8_storybook@8.2.8/node_modules/storybook-addon-deep-controls/index.d.ts:9:8 - error TS2300: Duplicate identifier 'Parameters'.

9   type Parameters = {
         ~~~~~~~~~~

  node_modules/.pnpm/@storybook+core@8.2.8/node_modules/@storybook/core/dist/types/index.d.ts:2:371
    2 export { AnnotatedStoryFn, ArgTypes, ArgTypesEnhancer, Args, ArgsEnhancer, ArgsFromMeta, ArgsStoryFn, BaseAnnotations, Canvas, ComponentAnnotations, ComponentId, ComponentTitle, Conditional, DecoratorApplicator, DecoratorFunction, GlobalTypes, Globals, IncludeExcludeOptions, InputType, LegacyAnnotatedStoryFn, LegacyStoryAnnotationsOrFn, LegacyStoryFn, LoaderFunction, Parameters, PartialStoryFn, PlayFunction, PlayFunctionContext, Renderer, SBArrayType, SBEnumType, SBIntersectionType, SBObjectType, SBOtherType, SBScalarType, SBType, SBUnionType, SeparatorOptions, StepFunction, StepLabel, StepRunner, StoryAnnotations, StoryAnnotationsOrFn, StoryContext, StoryContextForEnhancers, StoryContextForLoaders, StoryContextUpdate, StoryFn, StoryId, StoryIdentifier, StoryKind, StoryName, StrictArgTypes, StrictArgs, StrictGlobalTypes, StrictInputType, Tag } from '@storybook/csf';
                                                                                ~~~~~~~~~~
    'Parameters' was also declared here.

preview compiled with 1 error

@technbuzz I've published 0.7.1, let me know if this resolves your issue

@technbuzz I'll assume no response means the issue is resolved


text:
Add OpenBio

Add OpenBio

Thanks. There's a projects section at the top where all projects mentioned in the repo are listed. Could you add openbio to that please?
Thanks for pr!

Thanks. There's a projects section at the top where all projects mentioned in the repo are listed. Could you add openbio to that please?
Thanks for pr!

Yeah just did


text:
Add the author Suffix value if present to the PubMed deposit.

Fixes https://github.com/elifesciences/elife-pubmed-feed/issues/65.

Coverage remained the same at 100.0% when pulling 8137a0124798ce41a150309bc736adec5154ff29 on feature-author-suffix into 618f47c22afe1f4fc5db2e50f2d533e4f6925795 on develop.

authors: coveralls gnott


text:
MSID: 97706 Version: 1 DOI: 10.1101/2023.06.07.543033

MSID: 97706
Version: 1
Preprint DOI: https://doi.org/10.1101/2023.06.07.543033
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=97706
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2023.06.07.543033

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/97706v1
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/2023.06.07.543033
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/97706/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!

Schematron:
warn: underline element contains more than 20 characters. Is this tracked change formatting that's been erroneously retained?
error: p element contains a junk character '□' which should be replaced or deleted.
error: p element contains a junk character '□' which should be replaced or deleted.
error: p element contains a junk character '□' which should be replaced or deleted.
error: p element contains a junk character '□' which should be replaced or deleted.
error: p element contains a junk character '□' which should be replaced or deleted.
error: p element contains a junk character '□' which should be replaced or deleted.
error: p element contains a junk character '□' which should be replaced or deleted.

authors: fred-atherden nlisgo

repo: elifesciences/enhanced-preprints-import


text:
MSID: 88412 Version: 1 DOI: 2023.04.02.535290

"msas": "Neuroscience"
"msid": "88412"
"preprintDoi": "10.1101/2023.04.02.535290"
"Reviewed Preprint posted": "2023-07-14"
"Sent for peer review": "2023-05-02"
"Posted to bioRxiv": "2023-04-10" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2023.04.02.535290v2")
[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/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=88412)

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

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/88412/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: https://github.com/elifesciences/enhanced-preprints-data/pull/116
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews
Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2023.04.02.535290)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[x] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/88412/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/88412)

[ ] 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/88412

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/88412

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/88412/v1/88412-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/88412)

[ ] 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!

Corresponding author info needs fixing

Fix in https://github.com/elifesciences/enhanced-preprints-biorxiv-xslt/pull/59


text:
SimCity 4 Deluxe Resolutions higher than 1080p in hardware mode

Is there a way to get dxwrapper to play nicely with SimCity 4? All I could get were DDraw errors and defaulting back to software mode. What configuration + .dll files should I be using?
Any help would be wonderful,
many thanks.

Try https://www.pcgamingwiki.com/wiki/SimCity_4#Poor_performance_on_modern_systems

The restriction on resolution is a dx7 one not a sc4 one afaik. I am aware about the tricks on that page, they won't help here unfortunately.

Uh, if we are talking about the usual dx7 limitation then it's should be DDrawResolutionHack=1

SimCity 4 only supports 4 resolutions: 800x600, 1024x768, 1280x1024, 1600x1200
dxwrapper will remove the DirectX 2k limit, but the game does not take advantage of this.  This game will not work on higher resolutions unless the game itself is modified or patched.
You can see that even the GUI does not allow for any more resolutions, as this is a static pre-rednered options page.  There is no room on the page for more resolutions.  Furthermore, my computer supports many more resolutions lower than 2k that are not listed, because the game itself limits the resolution to these 4 resolutions only.
As far dxwrapper working with this game, it works with both the Dd7to9 option in software render mode or with EnableDdrawWrapper with software and hardware rendering.  DDrawResolutionHack is enabled by default if EnableDdrawWrapper is enabled, unless you manually disable it in the ini file.
If course if you are using the Dd7to9 option then DDrawResolutionHack is not needed since the 2k resolution limit only exists on DirectX 1-7 and this option will convert the game to DirectX 9.
dxwrapper.zip

Thanks for your input, I'll have to mess around a bit more with the options.
One thing to note though is SimCity 4 does infact natively support widescreen resolutions through the use of command-line arguments. The game crashes however when going bigger than about 1920x1440 due to what I believe is a constraint of dx7, of which I was hoping to circumnavigate with the wonderful tools available in this repo. The game itself can render in software mode above the limit mentioned however this introduces many rendering bugs and isn't conducive to gameplay.
Thanks again for your information on the configuration above though, I'll definitely keep persevering :).

Ok, I just realized that there is a command line option that allows you to specify any resolution.  I tested dxwrapper and 4k resolutions work fine.
Command line option is:
"SimCity 4.exe" -CustomResolution:enabled -r3840x2160x32

Here is a screenshot of it running at 4k.

I can confirm that it does now work in hardware rendering above the previous limit! I appreciate your help with this! This repo is truly wonderful for breathing life into some new games!

Sorry to ressurect a closed thread, Thanks to @Durfsurn 's kind sharing, I started to try dxwrapper as well, but have no luck in running SC4 with dedicated card, here is my tests's result: https://community.simtropolis.com/forums/topic/759351-raymonds-newbie-thoughts/?do=findComment&comment=1737944
I have no idea if there is any chance among the settings, Appreciate any tips on this, i can do any further tests if it's necessary, Thank you @elishacloud for your selfless efforts. at least you bring light of hope to our beloved game. Thanks a million!
Yours Sincerely,
-- Raymond

authors: Durfsurn elishacloud mirh rainman7cn

repo: elishacloud/dxwrapper

license: Zlib


text:
feat(tes & design): improve bundling

Description

Right now Design & TES are using tsup to generate the build the problem is that there is only one file generated globally in the build. Apply tree shaking to it so that the user can import the individual components & reduce there overall build size & loading time. Tree shaking is a popular solution for that & can be implemented in tsup like this https://tsup.egoist.dev/#tree-shaking
Possible solution(s)

Additional context

We might want to look into writing custom scripts. Especially considering there is no bundler that will build our components to support React out of the box.

@git-anurag-hub, I'll go ahead and write a build script using that as a reference, i should be able to get the code splitting to work properly.

authors: SalihuDickson git-anurag-hub

repo: elixir-cloud-aai/cloud-components


text:
Genserver time out crash in long-running pipeline

I wrote a crawler that crawls media galleries to download them and download files uing HTTPoison in a custom pipeline. This seems to work fine for small files as they download quickly but if I try to crawl a really big file like a video, I will almost always get this crash:
12:49:51.241 [error] GenServer #PID<0.471.0> terminating
** (stop) exited in: GenServer.call(Crawly.DataStorage, {:store, KemonoCrawler, %{...}, 5000)
    ** (EXIT) exited in: GenServer.call(#PID<0.468.0>, :stats, 5000)
        ** (EXIT) time out
    (elixir 1.14.0) lib/gen_server.ex:1038: GenServer.call/3
    (elixir 1.14.0) lib/enum.ex:975: Enum."-each/2-lists^foreach/1-0-"/2
    (crawly 0.14.0) lib/crawly/worker.ex:173: Crawly.Worker.process_parsed_item/1
    (crawly 0.14.0) lib/crawly/worker.ex:50: Crawly.Worker.handle_info/2
    (stdlib 4.1) gen_server.erl:1123: :gen_server.try_dispatch/4
    (stdlib 4.1) gen_server.erl:1200: :gen_server.handle_msg/6
    (stdlib 4.1) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Last message: :work
State: %Crawly.Worker{backoff: 10000, spider_name: KemonoCrawler, crawl_id: "e8e7bb02-465f-11ed-85df-3a9adacac61c"}

Is there a setting I can tweak to allow my pipeline to run for much longer? I didn't see anything easily tweakable in the config.

I would suggest firing off a Task instead or moving such heavy data processing to a separate process tree. Pipelines was designed for lightweight data processing.

repo: elixir-crawly/crawly


text:
Add a precision about Ecto's default behaviour with field names

Especially useful when management asks for guarantees that everything will not fall with a dependencies upgrade… ;)

@Kleidukos I have formatted and simplified the sentence, what do you think?

@josevalim perferct! 👍

authors: Kleidukos josevalim

repo: elixir-ecto/ecto


text:
missing constraint type in migration

Elixir version
1.14.3
Database and Version
any
Ecto Versions
current
Database Adapter and Versions (postgrex, myxql, etc)
any
Current behavior
https://github.com/elixir-ecto/ecto_sql/blob/8d4328638aeb5821c1a0fa55454c97cd21171fa0/lib/ecto/adapter/migration.ex#L13-L24
seems to be missing {:create %Constraint{}} and {:drop, %Constraint{}, mode} and co.
Expected behavior
The command type should cover all possible cases.

Thanks for the reports @ruslandoga!


text:
[Question] Linting Elixir code as an Elixir beginner

Q: Is there any interest in more advanced code analysis for this repository?
I tried asking this in the Elixir Discord, but I wasn't really satisfied with the answer. I've also done some research. IIUC mix compile --warnings-as-errors will act as a kind of analyzer, emitting errors for potential code corrections.
From reading about code analysis for Elixir, it looks like projects such as credo and dialyzer (from the Erlang ecosystem?) are used for more advanced code analysis. I also noticed the Elixir repo itself uses dialyzer for code analysis.
I'm using this issue to gauge this project's stance on development tooling and to understand what the recommendation currently is.

Hi @cnpryer, I think the ElixirForum will be a better place for such discussions. I am personally not a big fan of Dialyzer because its error messages often leave to be desired but I have seen both adopted with great success, especially on applications. :)

authors: cnpryer josevalim

repo: elixir-explorer/explorer


text:
Incompatible launch.sh for Almquist Shell (default on Alpine)

Precheck

This issue seems to be reported underneath a different issue: https://github.com/elixir-lsp/elixir-ls/issues/944#issuecomment-1703789963

Environment

Elixir & Erlang versions (elixir --version): Elixir 1.15.4 (compiled with Erlang/OTP 26)
Elixir Language Server version: 0.16.0
Operating system: Alpine Linux 3.18 (index.docker.io/elixir:alpine)
Editor or IDE name (e.g. Emacs/VSCode): VSCode
Editor Plugin/LSP Client name and version: ElixirLS 0.16.0

Current behavior
After the update to 0.16.0 the ElixirLS server fails to start:
Running /root/.vscode-server/extensions/jakebecker.elixir-ls-0.16.0/elixir-ls-release/launch.sh
Preffered shell ash is not supported, continuing in POSIX shell
Looking for ASDF install
ASDF not found
Looking for rtx executable
rtx not found
Installing ElixirLS release v0.16.0
Running in /app
Install complete
/root/.vscode-server/extensions/jakebecker.elixir-ls-0.16.0/elixir-ls-release/launch.sh: line 102: syntax error: unexpected redirection
[Error - 8:00:31 AM] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 8:00:31 AM] The ElixirLS - app server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
[Error - 8:00:31 AM] ElixirLS - app client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 8:00:31 AM] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097

See the reproduction steps at the end of the issue.
Expected behavior
I'd expect the LS just starts without errors.
Cause for the problem?
The startup of the LS is interrupted by the syntax error thrown by ash.
I assume (i was not able to verify that behaviour) that the ash-parser starts parsing the final if-statement of the launch.sh it then stumbles over the bash redirection <<< in line 102 which is parsed as subsequent redirection due to missing support in ash (see this SO post).
Possible solution
I think the safest (in the awareness that there might be n other shells using different parsers) way to handle this is either move shell specific commands into dedicated shell-files. I immediately ran into the next syntax error (for the zsh section).
I would have offered a quick fix but splitting up into different files might touch objections.. :slightly_smiling_face:

I use Docker to work with the ElixirLS, i tried to condense our Dockerfile:
FROM index.docker.io/elixir:alpine as base

ARG ELIXIR_LS_VERSION=v0.16.0
# see https://github.com/elixir-lsp/elixir-ls
ENV LS_DL_URL="https://github.com/elixir-lsp/elixir-ls/releases/download/${ELIXIR_LS_VERSION}/elixir-ls-${ELIXIR_LS_VERSION}.zip"

# Install build dependencies
RUN apk add --no-cache \
    build-base \
    openssh \
    curl \
    unzip \
    npm \
    git

# Prepare the build dir
WORKDIR /app

# Install hex and rebar
RUN mix local.hex --force \
    && mix local.rebar --force

RUN apk add --update-cache \
    && rm -rf /var/cache/apk/* \
    && mkdir /hex-home

RUN apk add --no-cache \
    inotify-tools \
    shadow \
    git \
    git-lfs \
    openssh \
    curl \
    unzip \
    bash \
    openssh \
    && mkdir /elixir-ls \
    && echo "${LS_DL_URL}" \
    && curl -Lo /elixir-ls/elixir-ls.zip "${LS_DL_URL}" \
    && cd /elixir-ls \
    && unzip elixir-ls \
    && rm /elixir-ls/elixir-ls.zip

RUN apk add --update-cache \
    && rm -rf /var/cache/apk/*

ENV PATH="${PATH}:/elixir-ls"

CMD sleep infinity

Building & Starting the container using
docker build -t elixir-ls .
docker run -it elixir-ls sh

Launching the LS in the container
cd /elixir-ls
./launch.sh

Steps to reproduce

So far only zsh and bash shells are supported (fish shell support is coming up). I don't have knowledge of ash nor resources to support it.

I would have offered a quick fix but splitting up into different files might touch objections.. 🙂

Please send a PR. Splitting is probably a good idea and fish script is already extracted

Done - i have the feeling that the handling of fish is somehow special and in my tests i wasn't able to start it using fish. However, i also added a Dockerfile to be able to quickly test stuff.
Let me know what you think.

Thanks a lot @emk - i guess the shell detection is not very robust since it relys on the existence and correctness of the $SHELL environment variable.
It would probably be more robust stick with a process-based approach here, f.e.:
SHELL=`echo $0`

This would be also a good point to add smoke tests for different shells.

@florianb It's weirder than that, because first the script does:
preferred_shell=$(basename "$SHELL")

Then it does the following twice:
if [ "$preferred_shell" = "bash" ]; then

The first time it does this, it recognizes that it is not bash.
The second time it does this, it takes the then branch, thinking it's bash

So either someone has clobbered $preferred_shell, or the script is getting invoked twice, or something else equivalently wild is happening. And I've reproduce this on two different installs now.
Anyway, VS Code users can work around it by changing the first line to #!/bin/bash. I am honestly very confused.

@emk thanks a lot - i didn't dabble a lot with fish.
I guess (sorry i didn't make that clear in my previous post) that the $SHELL-variable isn't set properly for your environment.
I don't actually know why there's a relaunch at all, but probably it has something to do with preserving the current users environment and having the elixir-ls polluting a dedicated one.
However, because of the wrongly set $SHELL (which traditionally might be set by login - as this SO-post claims) i guess the launch scripts take a wrong path. That's why i supposed trying a different shell detection mechanism instead.
You also state in the referenced issue that the launch script prints:
Preffered shell $preferred_shell is not supported, continuing in POSIX shell,

If that's the case we also have an issue with the variable substitution.
Con you verify the contents of your $SHELL variable?
I think about a way to make the launch-procedure more robust in general.

Version 0.17.0 with support for fish and fixes for other shells has been released

Version 0.17.0 with support for fish and fixes for other shells has been released

Running into the exact same problem with version elixir_ls 0.18 in launch.se
Running FreeBSD with fish.
Changing the script to use /usr/local/bin/bash instead of bourne shell solves the problem for me.
Is there a commit related to this issue that I can look at?

@drobban commit history of scripts directory?

authors: drobban emk florianb lukaszsamson

repo: elixir-lsp/elixir-ls


text:
Add code actions for unknown modules and structs

I propose another two code actions that can be applied when we get either:

a compile error because the struct is not defined
a warning because we are calling a function from a module that is not known

Replacing modules
The first code action proposes replacing an unknown module with its full name. For example:
defmodule MyModule do
  def foo do
    %ExampleStruct{}
  end
end

will be replaced with
defmodule MyModule do
  def foo do
    %ElixirLS.LanguageServer.Fixtures.ExampleStruct{}
  end
end

if we have module ElixirLS.LanguageServer.Fixtures.ExampleStruct available. Similarly
defmodule MyModule do
  def foo do
    ExampleDefaultArgs.my_func("text")
  end
end

can be replaced with
defmodule MyModule do
  def foo do
    ElixirLS.LanguageServer.Fixtures.ExampleDefaultArgs.my_func("text")
  end
end

if ElixirLS.LanguageServer.Fixtures.ExampleDefaultArgs is available.
Adding an alias
The second code action adds an alias that is required to make the code work. For example:
defmodule MyModule do
  def foo do
    %ExampleStruct{}
  end
end

will be replaced with
defmodule MyModule do
  alias ElixirLS.LanguageServer.Fixtures.ExampleStruct

  def foo do
    %ExampleStruct{}
  end
end

and
defmodule MyModule do
  def foo do
    ExampleDefaultArgs.my_func("text")
  end
end

will be replaced with
defmodule MyModule do
  alias ElixirLS.LanguageServer.Fixtures.ExampleDefaultArgs

  def foo do
    ExampleDefaultArgs.my_func("text")
  end
end

Notes

We always get 2 code actions (replacement and alias) for every suggested module
There are at most 3 suggested modules (so at most 6 code actions)
Suggested modules that are from the same namespace (first atom from full module name) as the module in which we are doing code action have priority
To find a place for the alias I've used ElixirSense.Core.Metadata.get_position_to_insert_alias/2 function which has two limitations that may affect the usability of the code action:

if there are already aliases in the module, the new alias will be added as the first one so the aliases may stop being ordered alphabetically
if there are no aliases in the module, the new alias will be added as a first directive just below @moduledoc which may not be a perfect place

@lukaszsamson Could you give me some feedback on that feature?

Sorry this is taking time but work on experimental server has stalled. I'm thinking of removing it. What do you think about migrating this PR back to original server code? There was already a PR adding some code action (now reverted due to many problems in implementation) https://github.com/elixir-lsp/elixir-ls/pull/718

@lukaszsamson I see. I can definitely move this PR to the original code. However, I think many additional helpers introduced in the experimental server were very useful for working on AST. What about starting with migrating the existing code actions with all that helpers to the original server before introducing this new code action?

Sure, we should salvage the good stuff

@sheldak #1057 is merged now, would you consider to rework this PR on top of the current master?

authors: lukaszsamson sheldak