text:
Feature/multiarch

Enable building of multiarch images.
Moves to a multi target docker file and using buildx.
Updates image to centos 8.
Draft, for review and comment

@ax3ghazy I'm having problems rebasing this on master due to the addition on cugr. It's including statically built libraries for x86 that are in the rsyn project that is included..

@ax3ghazy I'm having problems rebasing this on master due to the addition on cugr. It's including statically built libraries for x86 that are in the rsyn project that is included..

@robtaylor: Yes, I have noticed this issue. Boost doesn't have to be statically built though, so the following modification on top of your commits works:
 ################# Boost and SWIG ###################
@@ -73,7 +73,7 @@ RUN wget https://dl.bintray.com/boostorg/release/1.72.0/source/boost_1_72_0.tar.
 RUN tar -xf /boost_1_72_0.tar.bz2 && \
     cd boost_1_72_0 && \
     ./bootstrap.sh && \
-    ./b2 install --with-iostreams --with-test link=shared -j $(nproc) && \
+    ./b2 install --with-system --with-filesystem --with-program_options --with-iostreams --with-test link=shared -j $(nproc) && \
     cd .. && \
     rm -rf boost_1_72.0

@@ -113,7 +113,10 @@ RUN git clone https://github.com/ax3ghazy/cu-gr cugr_12012021 \

 WORKDIR cugr_12012021

-RUN python scripts/build.py -o release
+RUN sed -i 's/set(Boost_USE_STATIC_LIBS ON)/# set(Boost_USE_STATIC_LIBS ON)/g' src/CMakeLists.txt
+
+RUN python3 scripts/build.py -o release
+

@robtaylor: Yes, I have noticed this issue. Boost doesn't have to be statically built though, so the following modification on top of your commits works:
 ################# Boost and SWIG ###################
@@ -73,7 +73,7 @@ RUN wget https://dl.bintray.com/boostorg/release/1.72.0/source/boost_1_72_0.tar.
 RUN tar -xf /boost_1_72_0.tar.bz2 && \
     cd boost_1_72_0 && \
     ./bootstrap.sh && \
-    ./b2 install --with-iostreams --with-test link=shared -j $(nproc) && \
+    ./b2 install --with-system --with-filesystem --with-program_options --with-iostreams --with-test link=shared -j $(nproc) && \
     cd .. && \
     rm -rf boost_1_72.0

@@ -113,7 +113,10 @@ RUN git clone https://github.com/ax3ghazy/cu-gr cugr_12012021 \

 WORKDIR cugr_12012021

-RUN python scripts/build.py -o release
+RUN sed -i 's/set(Boost_USE_STATIC_LIBS ON)/# set(Boost_USE_STATIC_LIBS ON)/g' src/CMakeLists.txt
+
+RUN python3 scripts/build.py -o release
+

@robtaylor: Can we rebase this on master, because develop is now obsolete.

authors: agorararmard ax3ghazy robtaylor

repo: efabless/openlane


text:
🛑 Nodo Monte Castro is down

In 03c84cc, Nodo Monte Castro (https://nodomontecastro.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo Monte Castro is back up in 1fa55cc after 10 minutes.

source: gharchive/issue

repo: efecear/upptime

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 Tierra Firme is down

In de59c3a, Tierra Firme (https://www.tierrafirmenodoutt.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tierra Firme is back up in 3dbf85e.


text:
🛑 Tierra Firme is down

In e34f547, Tierra Firme (https://www.tierrafirmenodoutt.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tierra Firme is back up in 7a1d296.


text:
🛑 Almacén BioPandora is down

In 6250830, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in 4ec9698.


text:
🛑 Tierra Firme is down

In e095ba2, Tierra Firme (https://www.tierrafirmenodoutt.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tierra Firme is back up in e7c4640.


text:
🛑 La Semilla Que Crece is down

In 96e149a, La Semilla Que Crece (https://www.lasemillaquecrece.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: La Semilla Que Crece is back up in 2537a41.


text:
add requests to requirements

$ grep -r "import requests" .
./processing/esmarc.py:import requests
./processing/ldj2rdf.py:import requests
./enrichment/sameAs2id.py:import requests

Thanks!

source: gharchive/pull-request

repo: efre-lod/efre-lod-elasticsearch-tools


text:
add expires?

Need to add expiration time option.

We can't expire data in localStorage 😕

maybe simply add an option expire and when it expired we just delete that store.

To set a timestamp and check it when data updated

authors: egoist geekplux

repo: egoist/vue-persist


text:
Extend script to take a nonce for styles

Exactly as described in #33. Extends the script to take a nonce which is included with the generated elements to permit their inline styles to be applied by the browser in the presence of a CSP. If no nonce is specified, the generated element is unaffected:

If a nonce (e.g. QVd4OVVMODdkQ0xm) is specified (as an entry in options) however, we get this:

Now our CSP can specify style-src: nonce-QVd4OVVMODdkQ0xm and our inline styles will work just fine. This nonce must be a cryptographically secure random value >=128 bits in length to prevent prediction/guessing.

Thanks, @lambdacasserole !

authors: ehpc lambdacasserole

repo: ehpc/bootstrap-waitingfor

license: mit

license_source: bigquery


text:
Setup alert manager basic part

We already have installed prometheus with prometheus helm chart. Add the alermanager alertmanager module to our stack
Some docs about it : https://www.digitalocean.com/community/developer-center/how-to-set-up-alerts-and-notification-using-alertmanager-in-doks-cluster
For the other tasks about this subject, see #376

make sure it's compliant with prod env

repo: eimis-ans/eimis-synapse


text:
Encapsulate IO exceptions in Monad IO m, MonadError e m

I'm actually not sure whether this is an issue, or if it fits the project goals at all, but I keep wondering why we can't have an encapsulation of core exceptions from IO actions (since they are far too common) under a more type-safe approach such as MonadError e m.
What I'm thinking about is something like
import Control.Monad.Except
import Control.Exception (Exception (..), try)

liftErrorIO :: (Exception e, MonadIO m, MonadError e m) => IO a -> m a
liftErrorIO = liftIO . try >=> either throwError return

liftedBracket :: (Exception e, MonadIO m, MonadError e m) =>
                 m a
              -> (a -> m b)
              -> (a -> m c)
              -> m c
liftedBracket acquire release comp = do
  resource <- acquire
  result <- catchError (comp resource) (\e -> release resource >> throwError e)
  _ <- release resource
  return result

Control.Exception steps well outside of the language extensions that the mtl has used to date and would tie the library very closely to GHC.

Closing this out based on our discussion on IRC.

authors: Denommus ekmett

repo: ekmett/mtl


text:
Unable to Open Wand Inv

I am unable to open the wand inv on both the test server and my own server. Any advice?

Test server, like mine.elmakers.com ? You are pressing the Q button, right?
If you mean your own servers and you have custom wand configs, there are some properties you may need to add, see MIGRATION.md for details.

Specifically here, if it's a config issue:
https://github.com/elBukkit/MagicPlugin/blob/master/Magic/MIGRATION.md#65

Thanks! it works now

authors: NathanWolf lBerZerKl

repo: elBukkit/MagicPlugin


text:
Swipe to dismiss toast

Is your feature request related to a problem? Please describe.
At the moment it is only possible to dismiss a toast by tapping on it.
Describe the solution you'd like
It would be nice if we could dismiss it by swiping (up|down) depending on where it is located on the screen.

Hey @lukepistrol ,
This is definitely a feature that I will add to AlertToast but currently, I don't have enough time to work on that.
I'm closing this issue and reopen it once it becomes more relevant.


text:
Implemented AWS lambda spec changes

[x] Fixes https://github.com/elastic/apm-agent-java/issues/2346
[x] Implements https://github.com/elastic/apm-agent-java/issues/2394

Change transaction.name for API Gateway-triggered Lambda functions: To be consistent with other HTTP-based instrumentations include the low-cardinality resourcePath into the name.
Respect setting for use_path_as_transaction_name: If use_path_as_transaction_name is enabled use the full HTTP path for the transaction.name in API Gateway-triggered Lambda functions.
Respect service_name and service_version agent config options: If service_name and/or service_version are explicitly configured use the configured values instead of the derived ones.
Use the full domain name of the API Gateway as service.origin.name
Replaced service.id metadata field with new transaction-level field faas.id: To being able to capture different Lambda function ARN values (semantically correct) under one APM service umbrella (for the scenario of consolidating multiple lambda functions in one APM service).

[ ] Send empty request with flushed=true query param on Lambda data flush (https://github.com/elastic/apm-agent-java/issues/2305)

:broken_heart: Tests Failed

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

Expand to view the summary

Build stats

Reason: null

Start Time: 2022-01-27T08:54:37.657+0000

Duration: 19 min 7 sec

Commit: 9fd7dd39c8f8d874223f25251f7c6511e6f3f81d

Test stats :test_tube:

Test
Results

Failed
1

Passed
829

Skipped
0

Total
830

Test errors
Expand to view the tests failures
testCloudProvider_ForAWSLambda_fromEnvVariables – co.elastic.apm.agent.impl.metadata.MetaDataTest

Expand to view the error details

expected: "function-name"
 but was: ""

Expand to view the stacktrace
 org.opentest4j.AssertionFailedError:

expected: "function-name"
 but was: ""
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at co.elastic.apm.agent.impl.metadata.MetaDataTest.testCloudProvider_ForAWSLambda_fromEnvVariables(MetaDataTest.java:88)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
	at org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
	at org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
	at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
	at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
	at org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
	at org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
	at org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
	at org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:214)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:210)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:135)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:66)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
	at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:41)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:155)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
	at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:41)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:155)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
	at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
	at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.submit(SameThreadHierarchicalTestExecutorService.java:35)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor.execute(HierarchicalTestExecutor.java:57)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestEngine.execute(HierarchicalTestEngine.java:54)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:220)
	at org.junit.platform.launcher.core.DefaultLauncher.lambda$execute$6(DefaultLauncher.java:188)
	at org.junit.platform.launcher.core.DefaultLauncher.withInterceptedStreams(DefaultLauncher.java:202)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:181)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:128)
	at org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invokeAllTests(JUnitPlatformProvider.java:150)
	at org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:124)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
	at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)

Steps errors
Expand to view the steps failures

Shell Script

Took 2 min 1 sec . View more details here
Description: #!/bin/bash                      set -euxo pipefail                      ./mvnw test

:bug: Flaky test report
:grey_exclamation: There are test failures but not known flaky tests.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

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

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

authors: AlexanderWert apmmachine

repo: elastic/apm-agent-java


text:
Capture Python  request.urlopen runtime metrics

Python agent can capture  requests.get /  requests.post runtime metrics . but  request.urlopen can not capture  runtime metrics
Thanks

Hi @EricYqd
I assume you mean urllib2.urlopen() (Python 2) and urllib.request.urlopen (Python 3) from the standard library? We do indeed not currently instrument these calls, but it's a good idea to add them :)

Thank you for your quick feedback and look forward to python agent improvement.
在 2019-04-23 20:25:47，"Benjamin Wohlwend" notifications@github.com 写道：
Hi @EricYqd
I assume you mean urllib2.urlopen() (Python 2) and urllib.request.urlopen (Python 3) from the standard library? We do indeed not currently instrument these calls, but it's a good idea to add them :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

authors: EricYqd beniwohli

repo: elastic/apm-agent-python


text:
Use public docker image instead of building on every run

What does this pull request do?
Replaces the building of the docker image with the usage of the public docker image.
Will only work after https://github.com/elastic/apm-pipeline-library/pull/2174 is merged.

Related issues

Depends on https://github.com/elastic/apm-pipeline-library/pull/2174

How will this work for PRs? Is this only for nightly tests?
I think what @beniwohli was requesting in https://github.com/elastic/observability-robots/issues/1623 was that we still create the docker image on each test run, but we do it up front and use the same image for each of the matrix runs (as we currently build it in every matrix run individually). But I don't think https://github.com/elastic/apm-pipeline-library/pull/2174 is creating images for every commit pushed to a PR, so I'm not sure it solves the problem.
But I could be missing something! Thanks for your work on this!

@basepi these base images don't really change from PR to PR. Updating them daily or even weekly is fine (to pick up changes in the underlying Python base images). We still execute a pip install -r reqs-base.txt on every run, so if a PR adds a new test dependency, it'll be installed.

@basepi
I'm with you here. This setup is not the most ideal.
My preferred setup would be utilising the --cache-from option of the docker build command. This way we would benefit from caching the image and the ability to rebuild the image on every commit if there are changes.
However, we have this limitation that we cannot use secrets in workflows that are triggered on forked PRs.
Hence, we cannot do a docker login and won't be able to push the image.
As @beniwohli mentioned the base image does not change that much. But this setup will surely create discrepancy when you want to test changes on the docker image itself.
Let me experiment a bit more and I will try to figure out if I can somehow GitHub's artifacts API to achieve the desired caching behavior.

@basepi and @beniwohli
I think I got something intereseting here in https://github.com/elastic/apm-agent-python/pull/1793 which is inspired by https://depot.dev/blog/docker-layer-caching-in-github-actions
In this run you can see the building utilizes the docker layer cache and its time is reduced to ~16 seconds.
cc @elastic/observablt-ci

Alright, I think I got a good balance now.
We can build the images daily and publish it dockerhub like suggested in https://github.com/elastic/apm-pipeline-library/pull/2174.
Here, we can utilise the --cache-from option, which will speed up the build significantly, but you will still be able to make changes to the docker image for individual commits, if necessary.

Looking at a bunch of build logs, it looks like we're still spending a lot of time in docker RUN commands that should be cacheable, e.g. https://github.com/elastic/apm-agent-python/actions/runs/4617102660/jobs/8162941988?pr=1792#step:3:125. Am I misunderstanding something?

Looking at a bunch of build logs, it looks like we're still spending a lot of time in docker RUN commands that should be cacheable, e.g. https://github.com/elastic/apm-agent-python/actions/runs/4617102660/jobs/8162941988?pr=1792#step:3:125. Am I misunderstanding something?

Yes. I still need to get following PRs merged to see the result.

https://github.com/elastic/apm-agent-python/pull/1794
https://github.com/elastic/apm-pipeline-library/pull/2174

In the latest run attempt it's still not utilising the cache as expected.
https://github.com/elastic/apm-agent-python/actions/runs/4617333116?pr=1792
But the images are definitely accessible from https://hub.docker.com/r/elasticobservability/apm-agent-python-testing/tags
Will need to debug a little further.

Okay, I give up. I tried multiple approaches and multiple combinations of using --cache-from without success.
Locally, it was working just fine. It seems like it just won't work in a GH Actions workflow.
Nevertheless, in it's current state the workflow run time decreased from ~10 minutes to ~4 minutes.
However, the ability to create changes in the docker set up for a specific commit is not given.
@basepi @beniwohli let me know what you think and if we can merge it for now.
If changing the docker setup frequently becomes a necessity, let's revisit it in the future.
WDYT?

authors: basepi beniwohli reakaleek


text:
proxy filtered-groups: Populate Region field API calls

Description
Populates the new Region field on all of the filteredgroupapi calls.
Related Issues
Requires https://github.com/elastic/cloud-sdk-go/pull/144 to be merged
Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Refactoring (improves code quality but has no user-facing effect)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation

Readiness Checklist

[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] All new and existing tests passed

I'm merging this since I need it for my PR

authors: karencfv marclop

repo: elastic/ecctl


text:
Custom OTel Metrics dashboard

Related to https://github.com/elastic/apm-agent-dotnet/issues/2118 and #58, we should design a bespoke portable dashboard for OTel metrics that can be swapped in based on the agent sending the data.

Relates to #58

I have designed an initial OTel dashboard based on process and runtime metrics. These instrumentations are not enabled when using the vanilla SDK, but our distro brings in the contrib libraries and enables them. This means that the OTel dashboard will be empty when data is sent from the vanilla .NET OTel SDK. We are currently using the contrib runtime metrics, which will at some point (hopefully .NET 9) be replaced with runtime native metrics, conforming to a new proposed semantic convention for CLR runtime metrics.
In the future, we will need more control in the Kibana code to enable switching out the dashboard based on agent name and potentially the distro version, runtime version and framework. This would allow finer control of more specific dashboards using the expected available metrics.
This is an example of the planned panels for the initial version:

Next steps:

A PR into the Kibana repo to register the portable dashboard for OTel runtime metrics.

This has been merged.

repo: elastic/elastic-otel-dotnet


text:
NEST requires explicit installation of System.Diagnostics.DiagnosticSource nuget.

NEST/Elasticsearch.Net version:
7.0.1
Elasticsearch version:
7.2.0
Description of the problem including expected versus actual behavior:
In case of any issues in request to elastic search if no System.Diagnostics.DiagnosticSource installed in project explicitly then UnexpectedElasticsearchClientException is thrown instead of correct exception.
If explicitly add System.Diagnostics.DiagnosticSource v4.5.1(or later) in project then behavior is correct. System.Diagnostics.DiagnosticSource doesn't install automatically with the NEST package.
Steps to reproduce:

Install NEST 7.0.1 on clean .Net standard 2.0 project.
Send any request to elastic which produces error.

Provide DebugInformation (if relevant):
Elasticsearch.Net.UnexpectedElasticsearchClientException: Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=4.0.3.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=4.0.3.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Opened #3948 to address in the next release

authors: LbISS russcam

repo: elastic/elasticsearch-net


text:
Trying Sort by Script. Kibana worked but GoLang failed on JSON parsing, "_script"

Hi,
My ElasticSearch version is 6.4
and I am using olivere's client in GoLang
I am trying to sort the result by a custom script which is introduced here:
https://www.elastic.co/guide/en/elasticsearch/reference/6.4/search-request-sort.html#_script_based_sorting
Here's my GoLang search code:
func (s *ElasticSearchClient) Search(ctx context.Context,
	index string, searchType string,
	search string) (*elastic.SearchResult, error) {
	return s.es.Search(index).Type(searchType).Source(search).Do(ctx)
}

And here's my query:
 {
  "query": {
    "bool" : {
      "must" : [
        {
          "term" : { "latestEvent" : "AAA" }
        },
        {
          "range" : {
          "latestEventDate" : { "gte" : "2023-11-10T17:40:50.07Z" }
          }
        }
      ]
    }
  },
  "sort": [
    {
      "_script": {
        "type": "number",
        "order": "desc",
        "script": {
          "source": """
            def value = {some kind of calculation}
            return value;
          """,
          "params": {
            "mean": 1,
            "sd": 2,
            "currentTimestamp": 1699943316141
          }
        }
      }

    }
  ],
  "_source": [
    "latestEvent",
    "latestEventDate"
  ]
}

I wrote my query like above and confirmed it worked well in Kibana.
But I started having issues within the code.
I am facing an error because _parse is not a JSON friendly key.
"elastic: Error 400 (Bad Request): [28:21] [_script] failed to parse field [script] [type=x_content_parse_exception]"

I spent days to figure out how I can fix this but there was no luck. Can someone please help me to either

forcing JSON parsing allowing underscored keys like _script and _source
find another way to sort the result by script value

Thanks in advance!

Hello @9tontruck
Unfortunately we do not provide support for Oliver's client.
If you decide to switch to the official client I can help you rewrite your query with the TypedAPI.

@Anaethelion
Thanks for your comment. I updated my ES client so my app is using "github.com/elastic/go-elasticsearch/v7/esapi"
And my search function is something like this now:
func (e ElasticSearchClient) Search(ctx context.Context,
	index string,
	searchType string,
	search map[string]interface{},
) (*esapi.Response, error) {
	jsonString, _ := json.Marshal(search)
	return e.es.Search(
		e.es.Search.WithContext(context.Background()),
		e.es.Search.WithIndex(index),
		e.es.Search.WithBody(strings.NewReader(string(jsonString))),
		e.es.Search.WithTrackTotalHits(true),
		e.es.Search.WithContext(ctx),
	)
}

But I am still having JSON parsing errors when I add _script inside of the Sort field.
ref- https://www.elastic.co/guide/en/elasticsearch/reference/6.4/search-request-sort.html#_script_based_sorting
The version of my ElasticSearch is 6.4
Would you guide me to use scrip-sort using the go-elasticsearch client?

Created a new thread as it's closed
https://github.com/elastic/go-elasticsearch/issues/764

repo: elastic/go-elasticsearch


text:
Update catalog-info file with correct system property

Relates: https://github.com/elastic/ingest-dev/issues/3398

Looks like the process step failed so I retried it.

/test

test

Ok to merge since Olga opened a follow-up issue

repo: elastic/go-grok


text:
Install plugins?

initContainers doesn't seem to be exposed. Is there a way to install plugins with this chart?

Hi!
The recommended way to install plugins into our docker images is to create a custom docker image.
The Dockerfile would look something like:
ARG elasticsearch_version
FROM docker.elastic.co/elasticsearch/elasticsearch:${elasticsearch_version}

RUN bin/elasticsearch-plugin install --batch repository-gcs

And then updating image: in values to point to your custom image.
There are a couple reasons we recommend this.

Tying the availability of Elasticsearch to the download service to install plugins is not a great idea or something that we recommend. Especially in Kubernetes where it is normal and expected for a container to be moved to another host at random times.
Mutating the state of a running docker image (by installing plugins) goes against best practices of containers and immutable infrastructure.

I see. Thank you!
My next question was going to be how to insert values into the elasticsearch keystore, but it sounds like the answer all-around is custom image. :+1:

The keystore contains sensitive secrets and isn't really suitable to being baked into the docker image. It would also mean you would need seperate docker images for each cluster you have. It's much better to store it as a kubernetes secret and mount it into the container.
$ kubectl create secret generic elasticsearch-keystore --from-file=./elasticsearch.keystore

Then mount it via the secretMounts value.
secretMounts:
  - name: elasticsearch-keystore
    secretName: elasticsearch-keystore
    path: /usr/share/elasticsearch/config/elasticsearch.keystore
    subPath: elasticsearch.keystore

I have made a note to get both of these examples added into the readme since I'm sure others will have the same question.

Added an FAQ section in https://github.com/elastic/helm-charts/pull/52

Sounds great and the FAQ is looking good. I was able to get the gcs-repository working just fine (funny that's the one you put in your example). :)
I had one more question, though. For the elasticsearch.keystore, is it somehow tied to a cluster? Can I generate that with any keystore tool (for example, from a desktop) and have it work with any deployment I do, or is there some seed based on the cluster config that will make that not work?
To get my deploy working I just used the elasticsearch-keystore tool in the custom image I created, but I wasn't sure if that was somehow seeded with a keystore encryption key.

Can I generate that with any keystore tool (for example, from a desktop) and have it work with any deployment I do, or is there some seed based on the cluster config that will make that not work?

Yup, it just works! I used the elasticsearch-keystore command from my laptop (macbook running OSX) which works just fine in any other cluster.

Thank you for the assistance. Everything is working great with the strategy that was added to the FAQ.

authors: Crazybus tamarintech

repo: elastic/helm-charts


text:
GatlingTestRunner: add cli to run with custom parameters

Currently we run load testing for Kibana build via FTR and custom config. It solves the basic needs, but does not allow to pass custom arguments to maven command.
We need to have a cli for load testing that allows to specify scenario, path to load testing project, etc.
node scripts/load_testing_runner \
  --relativePath "../kibana-load-testing" \
  --scenario org.kibanaLoadTest.simulation.DemoJourney

I ended up with GATLING_SIMULATIONS =DemoJourney node scripts/functional_tests --config test/load/config.ts

I ended up with GATLING_SIMULATIONS =DemoJourney node scripts/functional_tests --config test/load/config.ts

repo: elastic/kibana-load-testing


text:
Add CI for Python 3.9.0

Closes #1074

CI failed with:
python-build: definition not found: 3.9.0
14:45:16
14:45:16 See all available versions with `pyenv install --list'.
14:45:16
14:45:16 If the version you need is missing, try upgrading pyenv:
14:45:16
14:45:16   cd /var/lib/jenkins/.pyenv/plugins/python-build/../.. && git pull && cd -

@hub-cap do you think it makes sense to have a similar ^^ Makefile target to pull the latest pyenv and reference it here rather than having to rely on rebuilding the CI golden image?

yes, I think we should control that instead of having infra control it, especially since we are the owners of upgrading our own python versions. Shall I do the needful here?
In this case would you like to have me get 3.9 installed in infra's image or use this as the test for doing the work ourselves?

@elasticmachine please test this

@elasticmachine test this please

@elasticmachine test this please

Depends on https://github.com/elastic/rally/pull/1096

@elasticmachine test this please

authors: dliappis hub-cap

repo: elastic/rally


text:
apps: add consolidation of errors in node-local-dns

[!warning]
This is public repository, ensure not to disclose:

[ ] personal data beyond what is necessary for interacting with this pull request
[ ] business confidential information, such as customer names

What kind of PR is this?
Required: Mark one of the following that is applicable:

[ ] kind/feature
[x] kind/improvement
[ ] kind/deprecation
[ ] kind/documentation
[ ] kind/clean-up
[ ] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[ ] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

What does this PR do / why do we need this PR?

Adds consolidation of error logs for node-local-dns to avoid log spam during incidents.

Part of #1691

Additional information to reviewers
Screenshots
Checklist

[x] Proper commit message prefix on all commits

Change checks:

[x] The change is transparent
[ ] The change is disruptive
[x] The change requires no migration steps
[ ] The change requires migration steps

Metrics checks:

[x] The metrics are still exposed and present in Grafana after the change
[ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[x] The logs do not show any errors after the change

Network Policy checks:

[x] Any changed pod is covered by Network Policies
[ ] The change does not cause any dropped packages in the NetworkPolicy Dashboard

Pod Security Policy checks:

[x] Any changed pod is covered by Pod Security Admission
[x] Any changed pod is covered by Gatekeeper Pod Security Policies
[x] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Falco checks:

[x] The change does not cause any alerts to be generated by Falco

Audit checks:

[ ] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Looks good to me but also wondering about what you wrote in your comment regarding the IPs

repo: elastisys/compliantkubernetes-apps


text:
[Feature][Docs] details about Ackee endpoints (~10 min to make it)

🐣 Is your feature request related to a problem? Please describe.
Explicit docs on endpoint and method and what object is sended/ recieved
💡 Describe the solution you'd like
https://docs.aws.amazon.com/iot/latest/apireference/API_DescribeEndpoint.html
or simply like :
method: GET
endpoint : baseUrl/Domains
body:
return: {id: string}[]
and others things if require ...
📋 Additional context
Existing database and api. So I want merge ackee api on my current API but I ask only for you to make a minimal doc on endpoints. I can look to your code (already do) but I'm not sure what really happen.
I think it is really valuable.

Ackee uses GraphQL and therefore has only one endpoint (which is /api). You can find everything about it in the API docs: https://docs.ackee.electerious.com/#/docs/API
Let me know when you have questions about specific queries or mutations.
On 5. Oct 2021, 11:16 +0300, c0ncentus @.***>, wrote:

🐣 Is your feature request related to a problem? Please describe.
Explicit docs on endpoint and method and what object is sended/ recieved
💡 Describe the solution you'd like
https://docs.aws.amazon.com/iot/latest/apireference/API_DescribeEndpoint.html
or simply like :
method: GET
endpoint : baseUrl/Domains
body:
return: {id: string}[]
and others things if require ...
📋 Additional context
Existing database and api. So I want merge ackee api on my current API but I ask only for you to make a minimal doc on endpoints. I can look to your code (already do) but I'm not sure what really happen.
I think it is really valuable.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

repo: electerious/Ackee


text:
Update for 6.3

this plugin its gonna be update to the 6.3??

Yes it will. I'm also planning on doing a release version at the same time.


text:
New app added but ENOENT

Hi, just tried this cool wizard process.
I get this error after i fill the license prompt and hit enter:
? What is the name of the app? ndm
? Short description npm desktop manager
? Website (can be repository URL if app has no website) https://720kb.github.io/
ndm
? Repository (optional) https://github.com/720kb/ndm
? Keywords (optional, comma-delimited) npm,desktop,manager,tool,gui,app
? License (optional) GPL-3.0
(node:2274) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: ENOENT: no such file or directory, open '/Projects/electron-apps/apps/ndm/ndm.yml'

Nothing serious, just wanted to let you know about it.

What version of node are you using?

Not able to reproduce, using the same answers:
? What is the name of the app? ndm
? Short description npm desktop manager
? Website (can be repository URL if app has no website) https://720kb.github.io/
? Repository (optional) https://github.com/720kb/ndm
? Keywords (optional, comma-delimited) npm,desktop,manager,tool,gui,app
? License (optional) GPL-3.0

Yay! Created apps/ndm/ndm.yml
Now you just need to add an icon named ndm-icon.png

Once you're done, run `npm test` to verify. Then open your pull request!

What version of node are you using?

Ouch i am maybe too far, didn't noticed that node is v7.2.0 , could be a problem?

Also, did it actually generate apps/ndm/ndm.yml, even though you got this error?

i have the apps/ndm/ folder but not the apps/ndm/ndm.yml file

Lemme try it on node 7.2

Hmm.. still can't reproduce on node 7.2.1. Opened #11 which might help.
Can you pull down the latest master and give it another try?

👍  thanks it works great!
Yay! Created apps/ndm/ndm.yml
Now you just need to add an icon named ndm-icon.png

Once you're done, run `npm test` to verify. Then open your pull request!

repo: electron/electron-apps


text:
Translation

I would like to request for a Filipino Translation contribution thru github as per utopian.

Hi @vinzruzell. What's your Crowdin username?

Hi...my crowdin user name is vinzruzell.
Thank you.
On Feb 14, 2018 10:42 AM, "Zeke Sikelianos" notifications@github.com
wrote:

Hi @vinzruzell https://github.com/vinzruzell. What's your Crowdin
username?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/electron/electronjs.org/issues/1085#issuecomment-365477963,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhjYgGHW9tyWXu3jbE2Ak8qz8XU9nPkUks5tUkgAgaJpZM4SA_GD
.

Hey I don't see that username among the translators on the Electron project. Have you translated anything yet?

Once you've actually made some translations on the project, please comment again on this issue and I'll change your status to proofreader. Thanks.

Thank you for that
On Feb 19, 2018 5:10 AM, "Zeke Sikelianos" notifications@github.com wrote:

Closed #1085 https://github.com/electron/electronjs.org/issues/1085.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/electron/electronjs.org/issues/1085#event-1479654840,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhjYgJHBsiR6Z7_3VoQGE4avrGVwxIDlks5tWJGogaJpZM4SA_GD
.

authors: vinzruzell zeke


text:
Remove native_mate/compat.h

It's time to remove support for ancient node 0.10

@zcbenz please review

repo: electron/native-mate


text:
Fix duplication of codesign args in loop

Fixes #263

Could not find a usable config.yml, you may have revoked the CircleCI OAuth app.Please sign out of CircleCI and log back in with your VCS before triggering a new pipeline.

CI failure is unrelated to PR

authors: chasestubblefield ckerr

repo: electron/osx-sign


text:
Support dbt utils breaking changes

dbt are about to make a breaking change in dbt-utils (deprecating macros and moving them into dbt-core).
In order to use those macros without making our users upgrading their dbt-core/utils, we wrapped those cross-db-utils to support all versions.

LGTM, just want @oravi to say that he is ok with the license and comment

authors: IDoneShaveIt Maayan-s

repo: elementary-data/dbt-data-reliability


text:
Update prefer css class selector over ids and tags

Hi, some small changes:

Ids: are unique, can be only used once on page, also, it create javascript variables in window, like ('amount-custom' in window)

tags: so much generic, stylize footer by example, we can never have other footers in the same page, it will give conflict

I think the use of IDs is generally for precisely that reason: unique objects.
#amount-custom appears only once, and you have broken much of the javascript by changing it.
Also, the developer ids, while non-descriptive, are useful for scrolling to. Perhaps replacing them with nicer names as well as the additional classes would be better.

Oks...could you close this at moment?

I prefer data attributes for javascript, easy to change style without change scripts.

I too like data attributes, but usually only for data. I use classes like .js-target-amount-custom usually, but much of this was started before me. Semantically, we should never have two footers on the same page though.

authors: lewisgoddard mateuspv

repo: elementary/mvp


text:
🛑 UNER - DDJJ is down

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

HTTP code: 502
Response time: 788 ms

Resolved: UNER - DDJJ is back up in 2ee40ec.

repo: elfoche/monitoreo


text:
🛑 UCU - Koha is down

In 0cf7300, UCU - Koha (http://biblioteca.ucu.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UCU - Koha is back up in fc5d86d after 5 hours, 59 minutes.


text:
torrentleech

Torrentleech has not been working for a long time, can it have something to do whit there new site? new layout and so

I have no account there.

ok, anything i can do to help you check what can be at fault?

An invite or share any login/password so I can enter and fix the search.

email?

denis.kuzmenok@gmail.com

I have an account for torrentleech and will check it out. However you should have in mind this is a private tracker that rigorously enforces a quota limit and also most releases are actually scene releases i.e. multiple rar split files not suitable for direct playback. So indeed not a really good option for kodi&elementum ...

Same problem here, a solution will be much appreciated. Huge thanks!!!

I will pick it up in the next days. Wait for the next version of Burst.

It looks like something is wrong with the CloudHole app and we can't get a valid cloudflare key to bypass cloudflare defense.

Now it's fine with CloudFlare, but then there is a captcha on login form. And that is a problem really.
@mancuniancol do you have any thoughts about passing the captcha?

Strange indeed, I do not get a captcha when trying to login, maybe you need to login at least once successfully from an ip range or something?

First few times I had no captcha, now I do have. We do not use persistent login sessions, so we need to do login every time we try to search something.

@elgatito, the captcha depends from IP address. If it is a VPN connection. It is normal to get that. Too many connections from the same IP

@mancuniancol I know that, but:
We do not use persistent login sessions, so we need to do login every time we try to search something.

Means it will work from time to time, when there is no captcha.

@elgatito other apps have an optional non-intrusive notification like option to specify captcha. They are next to impossible to bypass especially services like recaptcha.

For me I can log in, but no results:
13:37:25.474 T:67656  NOTICE: [script.elementum.burst] [torrentleech] Login successful
13:37:25.475 T:67656  NOTICE: [script.elementum.burst] >      TorrentLeech search URL: https://www.torrentleech.org/torrents/browse/index/query/thor ragnarok 2017/newfilter/2/facets/category%253AMovies
13:37:25.505 T:67544  NOTICE: script.module.metadatautils --> Rate limiter active for themoviedb.org - delaying request with 5 seconds - Configure a personal API key in the settings to get rid of this message and the delay.
13:37:25.588 T:67640  NOTICE: [script.elementum.burst] >>            1337x returned 18 results in 4.3 seconds
13:37:25.656 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    a66dbb: 0 B/0 B | Queued (0.00%)
13:37:25.799 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    285aea: 0 B/0 B | Queued (0.00%)
13:37:25.959 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    360204: 0 B/0 B | Queued (0.00%)
13:37:26.282 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    693013: 0 B/0 B | Queued (0.00%)
13:37:26.371 T:67656  NOTICE: [script.elementum.burst] >>     TorrentLeech returned  0 results in 5.0 seconds

@ilanerukh, both links show in the browser nothing.  Then, it is normal that burst gets no results.

But there are plenty results when you search in TorrenLleech itself for the same movie: https://www.torrentleech.org/torrents/browse/index/query/Thor ragnarok
The query searched in burst doesn't exist, and I think this is the problem. Not logging in to the tracker.

@ilanerukh, the page changed.  Then, the values in the json are not valid.

I see. Is it possible to use the old site which is this:
http://classic.torrentleech.org/
And the results are in the same way:
http://classic.torrentleech.org/torrents/browse/index/query/thor+ragnarok/facets/category%253AMovies
Instead of
https://www.torrentleech.org/torrents/browse/index/categories/8,37,43,14,12,13,41,47,15/query/thor%2Bragnarok

@ilanerukh, the classic seems not to use javascript for the content.  Then, just changing the url in json will work.  I don't have time to do the test.  But, you can try.

I tried, And even though it finds results in the log file, the results are not shown in kodi.
15:14:31.079 T:38292  NOTICE: [script.elementum.burst] >      TorrentLeech search URL: http://classic.torrentleech.org/torrents/browse/index/query/thor ragnarok 2017/newfilter/2/facets/category%253AMovies
15:14:31.336 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    693013: 0 B/0 B | Queued (0.00%)
15:14:31.401 T:44452  NOTICE: script.module.metadatautils --> Rate limiter active for themoviedb.org - delaying request with 5 seconds - Configure a personal API key in the settings to get rid of this message and the delay.
15:14:31.534 T:40152  NOTICE: [script.elementum.burst] >>              YTS returned  4 results in 3.2 seconds
15:14:31.639 T:46536  NOTICE: [script.elementum.burst] >>         MagnetDL returned 39 results in 3.3 seconds, sending 25 best ones
15:14:31.702 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    a66dbb: 0 B/0 B | Queued (0.00%)
15:14:31.749 T:39312  NOTICE: [script.elementum.burst] >>            RARBG returned 25 results in 3.4 seconds
15:14:31.756 T:77600  NOTICE: [script.elementum.burst] >>            Rutor returned 44 results in 3.4 seconds, sending 25 best ones
15:14:31.844 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    285aea: 0 B/0 B | Queued (0.00%)
15:14:31.855 T:52596  NOTICE: [script.elementum.burst] >>          TorLock returned  0 results in 3.5 seconds
15:14:32.005 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    360204: 0 B/0 B | Queued (0.00%)
15:14:32.327 T:62000  NOTICE: [plugin.video.elementum] DEBU  bittorrent   ▶ progressEvent    693013: 0 B/0 B | Queued (0.00%)
15:14:32.595 T:46408  NOTICE: [script.elementum.burst] >>            1337x returned 18 results in 4.2 seconds
15:14:32.635 T:38292  NOTICE: [script.elementum.burst] >>     TorrentLeech returned 58 results in 4.3 seconds, sending 25 best ones

Maybe this is the problem?
15:19:44.029 T:62000  NOTICE: [plugin.video.elementum] WARN  linkssearch  ▶ 1                Resolve failed for |Cookie=PHPSESSID=4e49nat9rbgu9uhja7dn8e8fm6|User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.21 Safari/537.36 : Get : unsupported protocol scheme "" 15:19:44.029 T:62000  NOTICE: [plugin.video.elementum] DEBU  ratelimit    ▶ func1            Resolved yts.am to 104.27.215.28 in 0s 15:19:44.030 T:62000  NOTICE: Previous line repeats 1 times. 15:19:44.030 T:62000  NOTICE: [plugin.video.elementum] WARN  linkssearch  ▶ 1                Resolve failed for /profile/budyzer|Cookie=PHPSESSID=4e49nat9rbgu9uhja7dn8e8fm6|User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.21 Safari/537.36 : Get /profile/budyzer: unsupported protocol scheme "" 15:19:44.031 T:62000  NOTICE: [plugin.video.elementum] WARN  linkssearch  ▶ 1                Resolve failed for /profile/alarquitas|Cookie=PHPSESSID=4e49nat9rbgu9uhja7dn8e8fm6|User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.21 Safari/537.36 : Get /profile/alarquitas: unsupported protocol scheme "" 15:19:44.032 T:62000  NOTICE: [plugin.video.elementum] WARN  linkssearch  ▶ 1                Resolve failed for /profile/alexfiha7797|Cookie=PHPSESSID=4e49nat9rbgu9uhja7dn8e8fm6|User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.21 Safari/537.36 : Get /profile/alexfiha7797: unsupported protocol scheme "" 15:19:44.032 T:62000  NOTICE: [plugin.video.elementum] WARN  linkssearch  ▶ 1                Resolve failed for /profile/kam009|Cookie=PHPSESSID=4e49nat9rbgu9uhja7dn8e8fm6|User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.21 Safari/537.36 : Get /profile/kam009: unsupported protocol scheme "" 15:19:44.033 T:62000  NOTICE: [plugin.video.elementum] WARN  linkssearch  ▶ 1                Resolve failed for /profile/aisha|Cookie=PHPSESSID=4e49nat9rbgu9uhja7dn8e8fm6|User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.21 Safari/537.36 : Get /profile/aisha: unsupported protocol scheme "" 15:19:44.033 T:62000  NOTICE: [plugin.video.elementum] WARN  linkssearch  ▶ 1                Resolve failed for /profile/Flowzn|Cookie=PHPSESSID=4e49nat9rbgu9uhja7dn8e8fm6|User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.21 Safari/537.36 : Get /profile/Flowzn: unsupported protocol scheme "" 15:19:44.033 T:62000  NOTICE: [plugin.video.elementum] WARN  linkssearch  ▶ 1                Resolve failed for /profile/hopoje|Cookie=PHPSESSID=4e49nat9rbgu9uhja7dn8e8fm6|User-Agent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.21 Safari/537.36 : Get /profile/hopoje: unsupported protocol scheme ""

@elgatito @mancuniancol Any possible solution for it?

Will be fixed in the next version.

Please, try v0.0.19

Please, check Burst 0.0.31 with Elementum >= 0.0.67.

authors: Ducco dbarev elgatito hoshsadiq ilanerukh leshets mancuniancol


text:
added pagination

Hey, @eliasdorneles !
Take a look at the pagination. Is it what you are looking for?

whoa, you closed without even giving me a chance to check. are you still working on it?
I didn't follow all the logic, but it looks useful.
I think it would need changing to work for the index page too.

I closed because it did not worked with the index. :-1:
I just made another PR (#2).

authors: eliasdorneles stummjr

repo: eliasdorneles/spidyquotes


text:
is it not possible to leverage difPy to match just a single image to a folder of images?

This was asked 2+ years ago in https://github.com/elisemercury/Duplicate-Image-Finder/issues/6
And it doesn't look like this feature has been added since.. at least if it is then it's not documented.. or maybe I'm just blind.
There are many other libraries that attempt this but I haven't found one that works very well especially when the source image is partially occluded. With the recent awesome performance improvements, I just think it would be cool to add this one feature to allow for matching one-to-many. I'd love to give that a whirl.
Thanks!

Hi @vesper8,
Thanks for your request! This feature will be evaluated for the next difPy release.
Best,
Elise

repo: elisemercury/Duplicate-Image-Finder


text:
Add fetch_change!/2 and fetch_field!/2

#3116

@thojanssens I made some minor fd9b21fcdd1b0367792e78d42dfd21b48d556576. Thank you for the PR!

authors: thojanssens wojtekmach

repo: elixir-ecto/ecto


text:
elixir-ls installer using a not-yet existent function when used with an older elixir version

Environment

Elixir & Erlang versions (elixir --version):
Erlang/OTP 24 [erts-12.3.2.13] [source] [64-bit] [smp:10:10] [ds:10:10:10] [async-threads:1]

Elixir 1.13.4 (compiled with Erlang/OTP 24) - installed with ASDF

Elixir Language Server version:
v0.24.1
Operating system:
Sonoma 14.6.1
Editor or IDE name (e.g. Emacs/VSCode):
nvim
Editor Plugin/LSP Client name and version:
elixirls installed with Mason

Current behavior
It looks like elixir-ls installer is trying to use functions from elixir from the version not installed on my machine. Jumping to definitions doesn't work and the lsp logs are as follows:
[ERROR][2024-12-13 10:55:16] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"Running /Users/dominikstanaszek/.local/share/lvim/mason/packages/elixir-ls/launch.sh\n"
[ERROR][2024-12-13 10:55:16] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"Preferred shell is bash, relaunching\n"
[ERROR][2024-12-13 10:55:16] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"Looking for ASDF install\n"
[ERROR][2024-12-13 10:55:16] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"ASDF install found in /opt/homebrew/opt/asdf/libexec/asdf.sh, sourcing\n"
[ERROR][2024-12-13 10:55:16] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"Installing ElixirLS release v0.24.1\n"
[ERROR][2024-12-13 10:55:16] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"Running in /Users/<<HOME>>/<<PROJECT PATH>>\n"
[ERROR][2024-12-13 10:55:16] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	'Could not find Hex, which is needed to build dependency true\nShall I install Hex? (if running non-interactively, use "mix local.hex --force")\n'
[ERROR][2024-12-13 10:55:18] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"* creating /Users/<<HOME>>/.asdf/installs/elixir/1.13.4-otp-24/.mix/archives/hex-2.1.1\n"
[ERROR][2024-12-13 10:55:18] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"Install complete\n"
[ERROR][2024-12-13 10:55:18] .../vim/lsp/rpc.lua:734	"rpc"	"elixir-ls"	"stderr"	"warning: Mix.Dep.Lock.read/1 is undefined or private. Did you mean:\n\n      * read/0\n\nInvalid call found at 2 locations:\n  /Users/<<HOME>>/.local/share/lvim/mason/packages/elixir-ls/installer.exs:356: ElixirLS.Mix.install/2\n  /Users/<<HOME>>/.local/share/lvim/mason/packages/elixir-ls/installer.exs:357: ElixirLS.Mix.install/2\n\n"

Mix.Dep.Lock.read/1 has been added to elixir after the version I am using, I might be missing something but shouldn't the installer work in a backwards compatible manner? Are there different installer versions and in my case the wrong one has been chosen?
Expected behavior
The installation should be successful

You right, Mix.Dep.Lock.read/1 has been added in 1.14. It's strange that it was not noticed until now. The installer has been used for almost two years. Would you like to raise a PR? Elixir 1.13 is near EoL and support such an old version is not my top priority.

Note the code is only executed if there is something wrong with your mix install dir and lockfile MD5 diverges. https://github.com/elixir-lang/elixir/blob/7df646d960c3cc9a4590861a87245d9c44f7fbc4/lib/mix/lib/mix.ex#L768
Maybe you need to cleanup your mix install dir

authors: dice-dominik lukaszsamson

repo: elixir-lsp/elixir-ls


text:
Add Elixir Version Metadata to Posts

Also, what are your thoughts on updating the elixirschool readme section Posting an Article to nudge authors to specify the versions of Elixir, Phoenix, LiveView, etc. used in their code examples.
Another approach could be to extend the article metadata with an optional :versions field e.g.
%{
  author: "Author Name",
  author_link: "https://github.com/author_github_account",
  tags: ["phoenix", "liveview"],
  versions: [{:phoenix, "~> 1.7.6"}, {:phoenix_live_view, "~> 0.19.0"}]
  date: ~D[YYYY-MM-DD],
  title: "Full Article Title",
  excerpt: """
  Article short preview text
  """
}
---

Originally posted by @codeanpeace in https://github.com/elixirschool/school_house/issues/216#issuecomment-1648718817

@codeanpeace I think that's a valuable suggestion. I think as long as it's optional (though encouraged that would be good metadata to have and display). Maybe we could add a more specific key though to not be confused with lesson or blog version? Something like elixir_and_deps_versions? What do you think?

Yeah, agreed that it should be optional but encouraged.
That's a good point regarding naming confusion. The other potentially confusing thing for authors is that elixir and dependencies are specified separately in a standard mix.exs. For simplicity's sake, combining them as elixir_and_deps_versions or even just elixir_and_deps makes sense but we should definitely highlight that in the readme.
It also occurs to me that this metadata could make it possible to incorporate LiveBook functionality one day, which would be very cool.

authors: codeanpeace kinson


text:
an error in the "create release" step

first

then

sovled. go to Settings>Actions>General>Workflow permissions and choose Read and write permissions

Read and write permissions doesn't seem to fix this anymore.

authors: ShayBox qoqiyu


text:
Make elm-package help identifying forks and dupes

Intro
One of the best things about Elm is the ecosystem. In no small part, this is due to the tooling:

the author is part of the package, which makes it easy to say "oh, I've used another high quality package by abc, so I'll go with that one"
Semver is strictly enforced
packages are encouraged to have descriptive names. something-extra for extensions to existing functionality, -exploration for experimental overhauls
etc.

Problem statement
However, there are some painpoints:

We have 5 packages that have something to do with your keyboard, excluding elm-lang/keyboard. Of these 5, 3 are called keyboard-extra. Note that, after the release of the most recent of those, @eeue56 intervened and helped out in getting the package author to communicate with @ohanhi. Eventually, changes were made to ohanhi/keyboard-extra that made the new package redundant, and it was unreleased.
We have 2 elm-bootstrap packages, and it's been mentioned on Slack that the second one is a fork which came about without any communication with the original maintainer.

Note that even though licensing allows this, and there is no inherent problem with forks; I do feel like the tooling could work harder to prevent splintering and duplication.
How to handle this
I propose three possible improvements.

elm package publish could check if the package name was already in use. This could just be a are you sure? y/n type thing, but pointing it out would at least prevent it from happening by accident.
elm package publish could check if the API of a certain package has significant overlap, and mark it as a fork. When it does, it could ask if any attempt was made to communicate with the original maintainer - if not, point out how it could help the ecosystem more than by just forking and splintering. Either way, having a description of why a package was forked could be helpful.
On package.elm-lang.org, there is no way of identifying forks easily. Adding that, in addition to displaying the reason for the fork, could help people selecting which package they're really after.

Note that the elm-bootstrap fork might just be to enable testing some changes, for personal use or whatever. And that's fine, but if it's not meant for general consumption, elm package could provide some pointers on how to test a package without publishing it (git submodules, etc).

For the last point (forks not being easy to recognize), I made this quick mock up of how I think it could look like:

Hello,
I'm the scrub dev who forked elm-bootstrap and then published it.  To anyone interested, I opened elm-lang/package.elm-lang.org#227 to see if I can get my fork removed from the package manager.
FWIW, I agree wholeheartedly with the solution proposed in this issue.  Whatever message is displayed when elm-package finds an identical package name should be extremely strongly worded so that would-be publishers are made extremely aware that publishing a fork without the original maintainer's blessing is a major insult to that developer's efforts.

I don't think your last half-sentence is consense.

authors: jvoigtlaender nvaldes ohanhi zwilias

repo: elm-lang/elm-package


text:
Building from source don't create bin dir in ElmPlatform on Linux

I have this output while building 0.15.1 gist
and Elm-Platform/0.15/bin does not exist tree
I'v got GHC version 7.10.2 and cabal cabal-install version 1.22.6.0 using version 1.22.4.0 of the Cabal library
Sorry If this is not helpful but I have no idea about Haskell magic :wink:

I think the latest release of cabal made it so instead of bin/ things go into .cabal-sandbox/bin/. Do you have that directory?

See #64.

Thank you! I'll check it out as soon as I get home.

@jvoigtlaender, did cabal change such that what I said is true?
I am having extreme trouble figuring out exactly what is happening on what platform and why, so I need you to be as specific as possible or I won't understand.
Or is the existing build script messed up such that the initial call to cabal sandbox init is actually creating a sandbox that no one uses?

@evancz I wanted to chime in and say that I have the same issue as TeddyDD, but when I tried it again just now it worked.
Not sure if you've made any changes or it was sth. on my end.

@evancz, no, I am not aware that cabal changed in terms of what directories are used. But yes, the existing build script is messed up such that the initial call creates a sandbox then not used by later calls.

#55 should fix that in the public facing version of this, so @TeddyDD, do you mind downloading the latest version of BuildFromSource.hs and trying again? Make sure to destroy everything that's there now and run the fubar.sh script.
Not sure what's up with your case @Enzou, cabal and hackage are mysterious and ever changing. The builds can break and unbreak easily based on what other hackage libraries are doing in patch versions.
#63 is trying out a potentially more reliable route, but we need to figure out how to make it work for different versions of GHC, which it currently does not.

teddy@teddy-Inspiron-5720: Programy » bash fubar.sh                   [16:33:33]
erasing all your user ghc and cabal packages - are you sure (y/n) ? y
erasing directories under ~/.ghc
find: `/home/teddy/.ghc': Nie ma takiego pliku ani katalogu
erasing ~/.cabal/lib
teddy@teddy-Inspiron-5720: Programy » runhaskell BuildFromSource.hs 0.15.1
Cloning into 'elm-compiler'...
remote: Counting objects: 20461, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 20461 (delta 0), reused 0 (delta 0), pack-reused 20457
Receiving objects: 100% (20461/20461), 6.12 MiB | 1.27 MiB/s, done.
Resolving deltas: 100% (11942/11942), done.
Checking connectivity... done.
You are not currently on a branch. Please specify which
branch you want to merge with. See git-pull(1) for details.

    git pull <remote> <branch>

Cloning into 'elm-package'...
remote: Counting objects: 3221, done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 3221 (delta 1), reused 0 (delta 0), pack-reused 3198
Receiving objects: 100% (3221/3221), 604.73 KiB | 715.00 KiB/s, done.
Resolving deltas: 100% (1898/1898), done.
Checking connectivity... done.
You are not currently on a branch. Please specify which
branch you want to merge with. See git-pull(1) for details.

    git pull <remote> <branch>

Cloning into 'elm-make'...
remote: Counting objects: 692, done.
remote: Total 692 (delta 0), reused 0 (delta 0), pack-reused 692
Receiving objects: 100% (692/692), 136.84 KiB | 0 bytes/s, done.
Resolving deltas: 100% (455/455), done.
Checking connectivity... done.
You are not currently on a branch. Please specify which
branch you want to merge with. See git-pull(1) for details.

    git pull <remote> <branch>

Cloning into 'elm-reactor'...
remote: Counting objects: 2340, done.
remote: Total 2340 (delta 0), reused 0 (delta 0), pack-reused 2340
Receiving objects: 100% (2340/2340), 1.61 MiB | 872.00 KiB/s, done.
Resolving deltas: 100% (1375/1375), done.
Checking connectivity... done.
You are not currently on a branch. Please specify which
branch you want to merge with. See git-pull(1) for details.

    git pull <remote> <branch>

Cloning into 'elm-repl'...
remote: Counting objects: 900, done.
remote: Total 900 (delta 0), reused 0 (delta 0), pack-reused 900
Receiving objects: 100% (900/900), 155.92 KiB | 0 bytes/s, done.
Resolving deltas: 100% (558/558), done.
Checking connectivity... done.
You are not currently on a branch. Please specify which
branch you want to merge with. See git-pull(1) for details.

    git pull <remote> <branch>

Writing a default package environment file to
/home/teddy/Programy/Elm-Platform/0.15.1/cabal.sandbox.config
Creating a new sandbox at
/home/teddy/Programy/Elm-Platform/0.15.1/.cabal-sandbox
Warning: The package list for 'hackage.haskell.org' does not exist. Run 'cabal
update' to download it.
Resolving dependencies...
cabal: Could not resolve dependencies:
trying: elm-compiler-0.15.1 (user goal)
next goal: union-find (dependency of elm-compiler-0.15.1)
Dependency tree exhaustively searched.

Note: when using a sandbox, all packages are required to have consistent
dependencies. Try reinstalling/unregistering the offending packages or
recreating the sandbox.
Warning: The package list for 'hackage.haskell.org' does not exist. Run 'cabal
update' to download it.
Resolving dependencies...
cabal: Could not resolve dependencies:
trying: elm-compiler-0.15.1 (user goal)
next goal: union-find (dependency of elm-compiler-0.15.1)
Dependency tree exhaustively searched.

Note: when using a sandbox, all packages are required to have consistent
dependencies. Try reinstalling/unregistering the offending packages or
recreating the sandbox.
Warning: The package list for 'hackage.haskell.org' does not exist. Run 'cabal
update' to download it.
Resolving dependencies...
cabal: Could not resolve dependencies:
trying: elm-reactor-0.3.2 (user goal)
next goal: websockets-snap (dependency of elm-reactor-0.3.2)
Dependency tree exhaustively searched.

Note: when using a sandbox, all packages are required to have consistent
dependencies. Try reinstalling/unregistering the offending packages or
recreating the sandbox.

0.15.1 dir looks the same.

This looks suspicious:

Warning: The package list for 'hackage.haskell.org' does not exist. Run 'cabal
update' to download it.

The BuildFromSource.hs file should do that cabal update call. Without a package list, it's clear that the install will fail.
I'll open a pull request.

Ok cabal update helped. Now I'v got bin dir and alost everything is up and running except elm-reactor. There was some errors while building
Configuring elm-reactor-0.3.2...
Building elm-reactor-0.3.2...
Preprocessing executable 'elm-reactor' for elm-reactor-0.3.2...
[1 of 6] Compiling Paths_elm_reactor ( dist/dist-sandbox-c4f1dabb/build/autogen/Paths_elm_reactor.hs, dist/dist-sandbox-c4f1dabb/build/elm-reactor/elm-reactor-tmp/Paths_elm_reactor.o )
[2 of 6] Compiling Utils            ( backend/Utils.hs, dist/dist-sandbox-c4f1dabb/build/elm-reactor/elm-reactor-tmp/Utils.o )
[3 of 6] Compiling Compile          ( backend/Compile.hs, dist/dist-sandbox-c4f1dabb/build/elm-reactor/elm-reactor-tmp/Compile.o )

backend/Compile.hs:5:1: Warning:
    The import of ‘Control.Applicative’ is redundant
      except perhaps to import instances from ‘Control.Applicative’
    To import instances alone, use: import Control.Applicative()
[4 of 6] Compiling Socket           ( backend/Socket.hs, dist/dist-sandbox-c4f1dabb/build/elm-reactor/elm-reactor-tmp/Socket.o )

backend/Socket.hs:21:64:
    Couldn't match type ‘[Char]’ with ‘FP.FilePath’
    Expected type: FilePath -> IO ()
      Actual type: FP.FilePath -> IO ()
    In the fourth argument of ‘NDevel.treeExtExists’, namely
      ‘(sendHotSwap watchedFile connection)’
    In a stmt of a 'do' block:
      _ <- NDevel.treeExtExists
             notifyManager "." "elm" (sendHotSwap watchedFile connection)
cabal: Error: some packages failed to install:
elm-reactor-0.3.2 failed during the building phase. The exception was:
ExitFailure 1

Ah, I've seen this as well. The reason is that the elm-reactor version corresponding to 0.15.1 doesn't have this commit, but also has no upper bound on the relevant library.
So what you need to do is go into the elm-reactor directory, open the elm-reactor.cabal file, and replace the line fsnotify >= 0.1.0.2 by fsnotify >= 0.1.0.2 && < 0.2. Then try again. Where by "try again" I do not mean the whole BuildFromSource.hs run, but only (from the directory above elm-reactor): cabal install -j --bindir=../bin elm-reactor.
(Leave out the --bindir=../bin part if you have used a BuildFromSource.hs already incorporating my change from #66.)

Thank you for assistance! I'v got Elm 0.15.1 build and running :) Time to mess around with it. Not sure If I should close this issue?

Cool!
Yes, I think just close the issue.

@jvoigtlaender, I was thinking it'd make sense to add a --constrain=fsnotify==0.1.0.3 to the build script because I think this will get lots of people now. I think it actually will be "backwards compatible" in the sense that older versions will either use it or not care. If it makes sense, would you mind doing a PR?

I am running into this issue with elm-lang/elm-reactor@444a57b3ab520ccc9e20499cde84334cb219c446 and elm-lang/elm-package@613c6022cec0ec49687c38f11dde0f76ac9fac9b.  fsnotify 0.2.1 is installed.  The error message is exactly the same, though.  Nothing changes if I attempt to apply @jvoigtlaender's advice by forcing fsnotify to 0.2.0 in the elm-reactor.cabal file and run cabl install.
lap% runhaskell BuildFromSource.hs 0.16
Cloning into 'elm-compiler'...
remote: Counting objects: 22357, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 22357 (delta 15), reused 0 (delta 0), pack-reused 22308
Receiving objects: 100% (22357/22357), 6.35 MiB | 1.66 MiB/s, done.
Resolving deltas: 100% (13347/13347), done.
Checking connectivity... done.
Cloning into 'elm-package'...
remote: Counting objects: 3367, done.
remote: Total 3367 (delta 0), reused 0 (delta 0), pack-reused 3367
Receiving objects: 100% (3367/3367), 618.44 KiB | 858.00 KiB/s, done.
Resolving deltas: 100% (2002/2002), done.
Checking connectivity... done.
Cloning into 'elm-make'...
remote: Counting objects: 955, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 955 (delta 3), reused 0 (delta 0), pack-reused 945
Receiving objects: 100% (955/955), 216.19 KiB | 0 bytes/s, done.
Resolving deltas: 100% (610/610), done.
Checking connectivity... done.
Cloning into 'elm-reactor'...
remote: Counting objects: 2908, done.
remote: Compressing objects: 100% (212/212), done.
remote: Total 2908 (delta 105), reused 0 (delta 0), pack-reused 2695
Receiving objects: 100% (2908/2908), 1.74 MiB | 1.72 MiB/s, done.
Resolving deltas: 100% (1695/1695), done.
Checking connectivity... done.
Cloning into 'elm-repl'...
remote: Counting objects: 920, done.
remote: Total 920 (delta 0), reused 0 (delta 0), pack-reused 920
Receiving objects: 100% (920/920), 159.37 KiB | 0 bytes/s, done.
Resolving deltas: 100% (570/570), done.
Checking connectivity... done.
Downloading the latest package list from hackage.haskell.org
cabal: unrecognised command: sandbox (try --help)
cabal: unrecognised command: sandbox (try --help)
Resolving dependencies...
All the requested packages are already installed:
Use --reinstall if you want to reinstall anyway.
Resolving dependencies...
Configuring elm-make-0.1.2...
Configuring elm-repl-0.4.1...
Building elm-repl-0.4.1...
Building elm-make-0.1.2...
Installed elm-repl-0.4.1
Installed elm-make-0.1.2
Resolving dependencies...
Configuring elm-reactor-0.3.1...
Building elm-reactor-0.3.1...
Failed to install elm-reactor-0.3.1
Last 10 lines of the build log (
/home/coventry/.cabal/logs/elm-reactor-0.3.1.log ):
backend/Socket.hs:21:64:
Couldn't match type `FP.FilePath' with `[Char]'
Expected type: FilePath -> IO ()
Actual type: FP.FilePath -> IO ()
In the return type of a call of `sendHotSwap'
In the fourth argument of `NDevel.treeExtExists', namely
`(sendHotSwap watchedFile connection)'
In a stmt of a 'do' block:
_ <- NDevel.treeExtExists
notifyManager "." "elm" (sendHotSwap watchedFile connection)
cabal: Error: some packages failed to install:
elm-reactor-0.3.1 failed during the building phase. The exception was:
ExitFailure 1

Oh, I thought I would re-open this issue by commenting on it.  I will start a new issue.

authors: Enzou TeddyDD coventry evancz jvoigtlaender

repo: elm-lang/elm-platform


text:
Batch multiple parallel requests into a Task

It would be useful if there was a way to send multiple requests as a single task (and have all of them sent in parallel).
As using Task.map2 to batch multiple tasks together will just run them in sequence.
See https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa/comments/7h2

Yes that would be great because it would help reduce loading times when doing requests that can be parallelized. Having an Http solution for concurrent request would be great for this would be great.
To be a bit more clear @dalen : Should the API only send request concurrently or also synchronize the responses(succeeding when all requests returned) kind of like a Promise.all() would do?
Probably also synchronizing the responses I would say, because just sending them concurrently could also be achieved with Cmd.batch. But the Cmd.batch approach sometimes forces you to compromise your model design if you actually need a combination of the results in your model instead of each of them separately.

Yeah, the responses should probably be synchronized. Otherwise the separate responses would need separate handling and responses.
Maybe some sort of subscription could be setup as an option if you want to subscribe to the progress of the requests.

There is some discussion of this topic here.
The conclusion so far in that thread is that we should get concrete examples of what people want to accomplish with something like Http.parallel2 to learn how errors and progress should be exposed by an API that allows that sort of thing.
My recommendation would be to open an issue on this repo with the title "Example where parallel requests may be ideal" and then fill the body in with the concrete scenario that you ran into in practice. At this phase, I think it's too early to speculate on the particular API that would result from that. Once we get a couple different people sharing examples here in that particular format, I can organize it into one place and see if there is a design that covers everyone nicely.

authors: ChristophP dalen evancz

repo: elm-lang/http


text:
Make copy + paste into REPL easier by giving option to autowrite function name

When defining a function in the REPL, the REPL will auto write the function name for you, this is actually more of an impedance for me than it is useful.
Often I want to test something by copy-pasting functions in, but I can't because I have to write the type annotation then copy the rest so that I don't get a Bad Type Annotation REPL error.
Anyone else wish they had the option to disable this repl feature?

@anandijain Can't you copy the function without the type annotation?
This should work and the type will be inferred anyway.

Yes, thank you, but for large blocks of code ~30-50 lines with multiple function definitions.

Yep. I am just learning Elm, and want to paste blocks of code into the REPL to test them and to try to figure things out. This gets in the way.

authors: anandijain edwardabraham rlefevre

repo: elm/compiler


text:
Added many more MIME types

should fix some file contents being erroneously wrapped in HTML when using reactor #1972
Quick Summary: Reactor served some file contents wrapped in html. This occurred for me when using csv files and made it difficult to use reactor for my application. Others have experienced this problem as well for other file types, see #1972 .
I added many mime types so certain files would no longer be returned as html. I did not yet test my new code because I could not find instructions on how to build elm. I will gladly perform testing given the necessary instructions
SSCCE

In an elm project, put any csv file in assets folder
elm reactor
wget http://localhost:8000/FILE_NAME.csv will return the file contents with lines of html added.

Elm: 0.19.1
Browser: firefox 72.0.1 (64-bit)
Operating System: KDE Neon 5.17 > Ubuntu 18.04

I'm not a contributor to this project or anything, but @Anton-4 , it looks like you can compile elm by running docker build -t elm -f installers/linux/Dockerfile . from the project root. That will create a docker image which contains the compiled version of elm at /usr/local/bin/elm. It seems like a really weird way to build it when you could also just run cabal build, but that's how it's done in the .travis.yml.

Thanks for the tip, I'll make sure to give it a try!


text:
"Exception: arity mismatch" error while variable declaration with assignment

Elvish version: 0.13+ds1-2
OS version: Linux Mint 20.2 Cinnamon
I just typed example from docs in terminal:
var foo = bar

and obtained Exception: arity mismatch.

The var and set builtins were added in the 0.15.0 release. In the 0.13 release you're using they are just regular tokens (e.g., var names) so you have two var names and one value. Hence the arity mismatch.

Try a current release of Elvish from https://elv.sh/get/

Everything works fine. :)

repo: elves/elvish


text:
[#873] fix json output of -compileonly

The errorToJSON() method checks whether the error returned is a *parse.MultiError. However, rather than a pointer to a MultiError, an instance was being passed in.
Updated the the instance methods of MultiError to take pointers as receivers to be in line with what was expected. This further required updating some other references.

Hmm, what about just changing the type switch in errotToJSON?

Hmm, what about just changing the type switch in errotToJSON?

Consistency mostly. Pointer receivers are the norm, instance ones only when necessary. MultiError had a mix of both. Unless there's a reason that I missed, inconsistency tends to foster bugs.
Thinking about it more, the most idiomatic way would be with an interface that both eval.CompilationError and parse.MultiError would implement, but that'd be an even bigger change.
Something like this:
func errorToJSON(err error) []byte {
	var e interface{}
	type hasParseErrors interface {
		ParseErrors() []*parse.Error
	}
	switch err := err.(type) {
	case hasParseErrors:
		var errArr []errorInJSON
		for _, v := range err.ParseErrors() {
			errArr = append(errArr,
				errorInJSON{v.Context.Name, v.Context.Begin, v.Context.End, v.Message})
		}
		e = errArr
	default:
		e = []interface{}{simpleErrorInJSON{err.Error()}}
	}
	jsonError, errMarshal := json.Marshal(e)
	if errMarshal != nil {
		return []byte(`[{"message":"Unable to convert the errors to JSON"}]`)
	}
	return jsonError
}

Ah, this type has methods of both value and pointer receivers. I agree that that is bad and your PR is in the correct direction, which I will merge.
But I am not convinced on the larger point that that pointer receivers are the norm; I don't think there is such consensus in the Go community. Value receivers are useful from time to time.
Regarding how to refactor this further: eval.CompilationError and parse.Error have the same fields, just slightly different implementations of how they print themselves, because they have different types. We can consolidate the difference by introducing a more general Error type with an extra "Type" field. The diag package is a good place for this new Error type.

authors: sblundy xiaq


text:
Invalid COS credentials trigger user cryptic exception

Describe the issue
See next section. The root cause (invalid credentials) repesents a common [user] error scenario.
To Reproduce
Steps to reproduce the behavior:

Create a notebook
Create a pipeline and add the notebook
Create a KFP runtime configuration with invalid COS user credentials (e.g. wrong password)
Export or run pipeline using that runtime configuration

Screenshots or log output
If applicable, add screenshots or log output to help explain your problem.
Log Output

[I 2021-04-14 12:46:25.882 ServerApp] kfp 'untitled':'Untitled' - processing operation dependencies for id: 431db185-d660-4035-8c53-4e2cea22fd88
[I 2021-04-14 12:46:25.884 ServerApp] kfp 'untitled-0414124625':'Untitled' - generated dependency archive: /var/folders/h8/l3qh8v192rv_vvggc6wyphzc0000gn/T/elyra/Untitled-431db185-d660-4035-8c53-4e2cea22fd88.tar.gz (0.002 secs)
[E 2021-04-14 12:46:26.192 ServerApp] Error uploading artifacts to object storage for operation: Untitled
    Traceback (most recent call last):
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/pipeline/processor.py", line 281, in _upload_dependencies_to_object_store
        cos_client = CosClient(config=runtime_configuration)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/util/cos.py", line 41, in __init__
        self.client = self.__initialize_object_store()
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/util/cos.py", line 53, in __initialize_object_store
        if not self.client.bucket_exists(self.bucket):
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/minio/api.py", line 404, in bucket_exists
        self._url_open('HEAD', bucket_name=bucket_name)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/minio/api.py", line 2189, in _url_open
        region = self._get_bucket_region(bucket_name)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/minio/api.py", line 2067, in _get_bucket_region
        region = self._get_bucket_location(bucket_name)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/minio/api.py", line 2109, in _get_bucket_location
        raise ResponseError(response, method, bucket_name).get_exception()
    minio.error.SignatureDoesNotMatch: SignatureDoesNotMatch: message: The request signature we calculated does not match the signature you provided.
[E 2021-04-14 12:46:26.198 ServerApp] Uncaught exception POST /elyra/pipeline/export?1618429585839 (::1)
    HTTPServerRequest(protocol='http', host='localhost:8888', method='POST', uri='/elyra/pipeline/export?1618429585839', version='HTTP/1.1', remote_ip='::1')
    Traceback (most recent call last):
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/tornado/web.py", line 1704, in _execute
        result = await result
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/pipeline/handlers.py", line 54, in post
        pipeline_overwrite
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/pipeline/processor.py", line 89, in export
        None, processor.export, pipeline, pipeline_export_format, pipeline_export_path, overwrite)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/concurrent/futures/thread.py", line 57, in run
        result = self.fn(*self.args, **self.kwargs)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/pipeline/processor_kfp.py", line 291, in export
        export=True)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/pipeline/processor_kfp.py", line 452, in _cc_pipeline
        operation)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/pipeline/processor.py", line 306, in _upload_dependencies_to_object_store
        raise ex from ex
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/pipeline/processor.py", line 281, in _upload_dependencies_to_object_store
        cos_client = CosClient(config=runtime_configuration)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/util/cos.py", line 41, in __init__
        self.client = self.__initialize_object_store()
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/elyra/util/cos.py", line 53, in __initialize_object_store
        if not self.client.bucket_exists(self.bucket):
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/minio/api.py", line 404, in bucket_exists
        self._url_open('HEAD', bucket_name=bucket_name)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/minio/api.py", line 2189, in _url_open
        region = self._get_bucket_region(bucket_name)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/minio/api.py", line 2067, in _get_bucket_region
        region = self._get_bucket_location(bucket_name)
      File "/opt/anaconda3/envs/elyra_dev/lib/python3.7/site-packages/minio/api.py", line 2109, in _get_bucket_location
        raise ResponseError(response, method, bucket_name).get_exception()
    minio.error.SignatureDoesNotMatch: SignatureDoesNotMatch: message: The request signature we calculated does not match the signature you provided.
[E 2021-04-14 12:46:26.204 ServerApp] {
      "Host": "localhost:8888",
      "Connection": "keep-alive",
      "Content-Length": "1624",
      "Sec-Ch-Ua": "\"Google Chrome\";v=\"89\", \"Chromium\";v=\"89\", \";Not A Brand\";v=\"99\"",
      "Authorization": "token 54fdbd55651e6be3454e2cae9bbbcd6732fe6882f28def3d",
      "X-Xsrftoken": "2|3a5f00dd|c99ae0c73961a332e03c47f4c49cdcdd|1618416193",
      "Sec-Ch-Ua-Mobile": "?0",
      "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36",
      "Content-Type": "text/plain;charset=UTF-8",
      "Accept": "*/*",
      "Origin": "http://localhost:8888",
      "Sec-Fetch-Site": "same-origin",
      "Sec-Fetch-Mode": "cors",
      "Sec-Fetch-Dest": "empty",
      "Referer": "http://localhost:8888/lab/tree/untitled.pipeline",
      "Accept-Encoding": "gzip, deflate, br",
      "Accept-Language": "en-US,en;q=0.9,de;q=0.8",
      "Cookie": "_xsrf=2|3a5f00dd|c99ae0c73961a332e03c47f4c49cdcdd|1618416193; username-localhost-8888=\"2|1:0|10:1618429585|23:username-localhost-8888|44:MWYzOGNmNmIxNDYwNDIyNDgwODZiMThlODhlZjA5N2Y=|64be00a6fdf8d488349d9738d931dc40385cda5c581bfa58bec1d747f0e516b1\""
    }
[E 2021-04-14 12:46:26.204 ServerApp] 500 POST /elyra/pipeline/export?1618429585839 (::1) 362.06ms referer=http://localhost:8888/lab/tree/untitled.pipeline

Expected behavior

https://github.com/elyra-ai/elyra/blob/master/elyra/util/cos.py#L61 should be caught in https://github.com/elyra-ai/elyra/blob/master/elyra/pipeline/processor.py#L273-L306
A user friendly message should be displayed/logged, indicating that the credentials are a likely cause of this issue. (Note that a web search for this error yields results that seem to indicate that there are different reasons why this specific error is raised. )

Deployment information
Describe what you've deployed and how:

Elyra version: 2.2.1+
Installation source: from source
Deployment type: local installation

(Note that a web search for this error yields results that seem to indicate that there are different reasons why this specific error is raised. )

Are you suggesting that we treat all ResponseError instances as credential-related or that, after interrogating the ResponseError we treat all SignatureDoesNotMatch (internal) instances as credential-related?  It's tough to determine which specific error you're referring to.  I think the former is more of a generic exception while the latter could probably be classified as credential-related and suspect you're referring to SignatureDoesNotMatch.

and suspect you're referring to SignatureDoesNotMatch.

Yes, it's that one I was eluding to. Looking at the scenarios that can trigger an exception that is bubbled up ...
        self.client = Minio(endpoint=self.endpoint.netloc,
                            access_key=self.access_key,
                            secret_key=self.secret_key,
                            secure=self.secure)

        # Make a bucket with the make_bucket API call.
        try:
            if not self.client.bucket_exists(self.bucket):
                self.client.make_bucket(self.bucket)

the Minio constructor won't surface any issues because it doesn't seem to perform any validation
bucket_exists will surface host/port issues through MaxRetryError
bucket_exists surfaces credential issues through ResponseError/minio.error.SignatureDoesNotMatch
make_bucket surfaces bucket existence/permission issues through means other than SignatureDoesNotMatch

Therefore I believe it should be okay to interpret/surface SignatureDoesNotMatch errors as credential issues unless somebody can identify other scenarios that would cause  bucket_exists and make_bucket to also raise this exception.

authors: kevin-bates ptitzler

repo: elyra-ai/elyra


text:
Update PythonEditor integration with Jupyterlab TOC after release

Placeholder for updating the integration with JupyterLab TOC after the new release + yarn.lock updates

The Elyra JupyterLab 2.x branch has been updated to use latest TOC release that supports JupyterLab 2.x

So I was wrong about this being a versioning thing. The more I look into this the more it seems that it's a side effect of leveraging a function that assumes the tracker is IEditorTracker and not something with the same class def. As such I believe leaving the as unknown as in the code is the best solution for now, so I will be closing this.

authors: ajbozarth lresende


text:
Bug: app.getGlobalRoutes is not a function

If I try to access my documentation route I get the following error: app.getGlobalRoutes is not a function. (In 'app.getGlobalRoutes()', 'app.getGlobalRoutes' is undefined)
Elysia Version: 1.0.25
Swagger Plugin Version: 1.1.5 (1.1.1 doesn't work either).
Code: https://github.com/Global-Tags/API/blob/master/src/index.ts#L43-L73

Same here, bump!

authors: RappyTV liszper

repo: elysiajs/elysia-swagger


text:
does not work in smp for forge build 2796

In my pack World of Dragons, the mod works flawlessly in SSP (single player) but in SMP (multplayer on a dedicated server) the ore will pop around till the smelt cycle and then vanish!

sorry this is bogus. I forgot to install it on my server.

repo: elytra/PopcornSmelting


text:
Supports Quad Polygon Data in ObjLoader class

ObjLoaderクラスで四角形を含むobjファイルにも対応する。

プルリクエスト #31 で対応済み。

repo: emadurandal/GLBoost


text:
Fix 3 small bugs in the simulator

Sim command had -h as an option for host, but that's reserved for --help
Gas limit now defaults to blockchain config's gas limit if no option is provided (Fixes https://github.com/embark-framework/embark/issues/1054)
Fixes embark simulator for Windows

LGTM 👌

authors: PascalPrecht jrainville

repo: embark-framework/embark


text:
Return ROS time values

Fixes: DATA-627
Description of Changes
This switches the python interface to providing timestamps as ROS times, similar to how the actual rospy interface works.
Test Plan
Unit tests.

I'm wondering if we need to support getting time as int or float? Like, why can't we just return embag.RosTime and the client can call to_sec or to_nsec to get long/int or float. This way we won't have to pass around that ros_time_py_type. Does rospy support just getting time/duration as primitive? May be this is for backward compatibility?

@kashish-jain Its mostly just about providing nice functionality for clients so that they don't have to worry about writing the conversions/serializations themselves and dealing with performance hits from deeply nested structures. IMO passing the arg around isn't too big of a deal.
rospy doesn't provide any to_dict functionality, so theres no precedence there.

repo: embarktrucks/embag


text:
embassy-net-driver-channel: large stack size for State

I need a RUST_MIN_STACK of approx. 90000000 (90 MB) to get my test running. The critical part seems to be the initiation of a new embassy_net_driver_channel::State. Could someone please explain to me why I need to define RUST_MIN_STACK to be that large? I would love to know what I'm doing wrong.
trait Sizes {
    const MTU: usize;
    const BUF: usize;
}

pub struct TcpStack {
    pub inner: embassy_net::Stack<
        embassy_net_driver_channel::Device<'static, { <TcpStack as Sizes>::MTU }>,
    >,
}

impl Sizes for TcpStack {
    const MTU: usize = ETHERNET_MTU + ETHERNET_HEADER_LEN; // 1514
    const BUF: usize = TCP_BUF; // 4096
}

impl TcpStack {
    pub fn new(mac_address: [u8; 6]) -> Self {
        let state = singleton!(embassy_net_driver_channel::State::<
            { <TcpStack as Sizes>::MTU },
            { <TcpStack as Sizes>::BUF },
            { <TcpStack as Sizes>::BUF },
        >::new());
        let device = Nic::new(mac_address, state);
        let config = embassy_net::ConfigStrategy::Dhcp;
        let resources: &mut embassy_net::StackResources<1, 2, 8> =
            singleton!(embassy_net::StackResources::new());

        let mut seed = [0; 8];
        rand::thread_rng().fill_bytes(&mut seed);
        let seed = u64::from_le_bytes(seed);

        let stack = embassy_net::Stack::new(device.inner, config, resources, seed);

        Self { inner: stack }
    }
}

#[cfg(test)]
mod test {
    use super::*;

    use anyhow::Result;

    #[test]
    fn test_new() -> Result<()> {
        let stack = TcpStack::new([0xa4, 0x83, 0xe7, 0x48, 0x31, 0x21]);

        Ok(())
    }
}

Nic is also just a wrapper with an inner which is embassy_net_driver_channel::Device

the 2nd and 3rd generic args to State are the count of MTU-sized buffers, not the buffer size. You're allocating 151440962 = 12MB there.
Set them to something small, like 4.

the 2nd and 3rd generic args to State are the count of MTU-sized buffers, not a buffer size in bytes. You're allocating 1514*4096*2 = 12MB there.
Set them to something small, like 4.

Ah great, thank you 🙏

authors: Dirbaio LimpidCrypto

repo: embassy-rs/embassy


text:
stm32: build fixes for troublesome chips

See individual commits.

bors r+


text:
Support RNG operations

Based on a rng feature, support generation of a u32 random number if the LoRa board supports it.
The get_random_number function is added to the lora-phy API.  Access to random number generation is only available through this function, in order to control LoRa board mode at the appropriate level.

This PR provides assistance to PR https://github.com/embassy-rs/lora-phy/pull/9.  The author of the latter PR will be assigned for review of this PR once authorization on this repository is completed.

I do not have a strong opinion on incorporating a RngCore implementation in lora-phy, as long as it uses the API (that is get_random_number).  I do not believe that would be a semver breaking change; rather, an enhancement.
If you believe the functionality in this PR should be merged now and as-is, please indicate that in the approving review.  I will then push a new release 1.1.0 (that is, an enhancement rather than a breaking change) to crates.io.

repo: embassy-rs/lora-phy


text:
fix: add logging for RetrievalEvaluator NaN values for similarity scores

Fixes #1389
Ran through tests but couldn't find a case where it was actually used. It might be a thing we can simply remove.

Checklist

[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.

@orionw or @Muennighoff will merge this in but would love to remove the -1 transformation if possible

I’m not aware of when it would happen, I think it was there when I started using MTEB.  I assume like guessed in #1389 it’s for overflow or something.
Perhaps @Muennighoff may know more.

Yeah I'm also not sure, maybe when embeddings are NaN, but then that's a problem with the model and we probably shouldn't work around that 🤔 We can also remove it and wait until someone reports an issue with it

removing them in #1444

authors: KennethEnevoldsen Muennighoff orionw

repo: embeddings-benchmark/mteb