text:
Use of python UDF with external third-party dependencies is not supported in Flink SQL-query.

Description
In case of Flink python UDF having python third-party dependencies, if used in Flink sql query job is getting failed with “ModuleNotFoundError: No module named xxxxxxx”
To Reproduce
Step1: Mention the third-party dependencies in requirements.txt
e.g
jsonpath-ng==1.5.3
Step2: Write python udf and save with function name i.e json_update_jpath.py
e.g
from jsonpath_ng import parse
import json
from pyflink.table import DataTypes
from pyflink.table.udf import udf

@udf(result_type=DataTypes.STRING())
def json_update_jpath(json_event, obj, jpath):
    json_data = json.loads(json_event)
    jpath_expr = parse(jpath)
    jpath_expr.update(json_data, obj)
    json_out_string = json.dumps(json_data)
    return json_out_string

Step3: Mention these python udf configuration
{
	"PYTHON_FILES": "gs://*****/python-udf/master/json_update_jpath.py",
	"PYTHON_REQUIREMENTS": "gs://*****/python-udf/master/requirements.txt",
	"PYTHON_ARCHIVES": "gs://*****/python-udf/master/data.zip#data",
	"PYTHON_FN_EXECUTION_ARROW_BATCH_SIZE": "10000",
	"PYTHON_FN_EXECUTION_BUNDLE_SIZE": "100000",
	"PYTHON_FN_EXECUTION_BUNDLE_TIME": "1000"
}

Step4: Run Dagger job and use the UDF in Flink SQL query
SELECT
  json_update_jpath(
    '{"k1":"v1","k2":"v2","k3":"v3"}',
    'replaced_value',
    '$.k2'
  ) as json_updated_event
FROM
  `data_streams_0`

After following these steps below exceptions occur in Job-manager.
Cannot instantiate user-defined function 'json_update_jpath'
ModuleNotFoundError: No module named 'jsonpath_ng'.
Detailed error
org.apache.flink.table.api.ValidationException: SQL validation failed. Cannot instantiate user-defined function 'json_update_jpath'.
	at org.apache.flink.table.planner.calcite.FlinkPlannerImpl.org$apache$flink$table$planner$calcite$FlinkPlannerImpl$$validate(FlinkPlannerImpl.scala:164)
	at org.apache.flink.table.planner.calcite.FlinkPlannerImpl.validate(FlinkPlannerImpl.scala:107)
	at org.apache.flink.table.planner.operations.SqlToOperationConverter.convert(SqlToOperationConverter.java:215)
	at org.apache.flink.table.planner.delegation.ParserImpl.parse(ParserImpl.java:101)
	at org.apache.flink.table.api.internal.TableEnvironmentImpl.sqlQuery(TableEnvironmentImpl.java:716)
	at io.odpf.dagger.core.StreamManager.registerOutputStream(StreamManager.java:185)
	at io.odpf.dagger.core.KafkaProtoSQLProcessor.main(KafkaProtoSQLProcessor.java:33)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:355)
	at org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:222)
	at org.apache.flink.client.ClientUtils.executeProgram(ClientUtils.java:114)
	at org.apache.flink.client.deployment.application.DetachedApplicationRunner.tryExecuteJobs(DetachedApplicationRunner.java:84)
	at org.apache.flink.client.deployment.application.DetachedApplicationRunner.run(DetachedApplicationRunner.java:70)
	at org.apache.flink.runtime.webmonitor.handlers.JarRunHandler.lambda$handleRequest$0(JarRunHandler.java:104)
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604)
	at java.lang.Thread.run(Thread.java:750)
Caused by: org.apache.flink.table.api.ValidationException: Cannot instantiate user-defined function 'json_update_jpath'.
	at org.apache.flink.table.functions.UserDefinedFunctionHelper.instantiateFunction(UserDefinedFunctionHelper.java:219)
	at org.apache.flink.table.catalog.FunctionCatalog.getFunctionDefinition(FunctionCatalog.java:659)
	at org.apache.flink.table.catalog.FunctionCatalog.resolvePreciseFunctionReference(FunctionCatalog.java:562)
	at org.apache.flink.table.catalog.FunctionCatalog.lambda$resolveAmbiguousFunctionReference$3(FunctionCatalog.java:624)
	at java.util.Optional.orElseGet(Optional.java:267)
	at org.apache.flink.table.catalog.FunctionCatalog.resolveAmbiguousFunctionReference(FunctionCatalog.java:624)
	at org.apache.flink.table.catalog.FunctionCatalog.lookupFunction(FunctionCatalog.java:362)
	at org.apache.flink.table.planner.catalog.FunctionCatalogOperatorTable.lookupOperatorOverloads(FunctionCatalogOperatorTable.java:97)
	at org.apache.calcite.sql.util.ChainedSqlOperatorTable.lookupOperatorOverloads(ChainedSqlOperatorTable.java:67)
	at org.apache.calcite.sql.validate.SqlValidatorImpl.performUnconditionalRewrites(SqlValidatorImpl.java:1183)
	at org.apache.calcite.sql.validate.SqlValidatorImpl.performUnconditionalRewrites(SqlValidatorImpl.java:1169)
	at org.apache.calcite.sql.validate.SqlValidatorImpl.performUnconditionalRewrites(SqlValidatorImpl.java:1200)
	at org.apache.calcite.sql.validate.SqlValidatorImpl.performUnconditionalRewrites(SqlValidatorImpl.java:1169)
	at org.apache.calcite.sql.validate.SqlValidatorImpl.validateScopedExpression(SqlValidatorImpl.java:945)
	at org.apache.calcite.sql.validate.SqlValidatorImpl.validate(SqlValidatorImpl.java:704)
	at org.apache.flink.table.planner.calcite.FlinkPlannerImpl.org$apache$flink$table$planner$calcite$FlinkPlannerImpl$$validate(FlinkPlannerImpl.scala:159)
	... 18 more
Caused by: java.lang.IllegalStateException: Instantiating python function 'python_udfs.json_update_jpath.json_update_jpath' failed.
	at org.apache.flink.table.functions.python.utils.PythonFunctionUtils.getPythonFunction(PythonFunctionUtils.java:48)
	at org.apache.flink.table.functions.UserDefinedFunctionHelper.instantiateFunction(UserDefinedFunctionHelper.java:206)
	... 33 more
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.GeneratedMethodAccessor125.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.flink.table.functions.python.utils.PythonFunctionUtils.getPythonFunction(PythonFunctionUtils.java:45)
	... 34 more
Caused by: org.apache.flink.api.python.shaded.py4j.Py4JException: An exception was raised by the Python Proxy. Return Message: Traceback (most recent call last):
  File "/opt/flink/opt/python/py4j-0.10.8.1-src.zip/py4j/java_gateway.py", line 2410, in _call_proxy
    return_value = getattr(self.pool[obj_id], method)(*params)
  File "/opt/flink/opt/python/pyflink.zip/pyflink/java_gateway.py", line 169, in getPythonFunction
    udf_wrapper = getattr(importlib.import_module(moduleName), objectName)
  File "/usr/local/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmp/pyflink/207a6c73-f7ec-4d01-b2ba-ef3a82c18034/26bad213-4e33-4d22-9900-731ffba2fdb1/python_udfs/python_udfs/json_update_jpath.py", line 1, in <module>
    from jsonpath_ng import parse
ModuleNotFoundError: No module named 'jsonpath_ng'

	at org.apache.flink.api.python.shaded.py4j.Protocol.getReturnValue(Protocol.java:476)
	at org.apache.flink.api.python.shaded.py4j.reflection.PythonProxyHandler.invoke(PythonProxyHandler.java:108)
	at com.sun.proxy.$Proxy260.getPythonFunction(Unknown Source)
	at org.apache.flink.client.python.PythonFunctionFactoryImpl.getPythonFunction(PythonFunctionFactoryImpl.java:47)
	at org.apache.flink.client.python.PythonFunctionFactory.getPythonFunction(PythonFunctionFactory.java:131)
	... 38 more
2022-10-19 12:31:27,580 WARN  org.apache.flink.client.deployment.application.DetachedApplicationRunner - Could not execute application:
org.apache.flink.client.program.ProgramInvocationException: org.apache.flink.table.api.ValidationException: SQL validation failed. Cannot instantiate user-defined function 'json_update_jpath'.
	at io.odpf.dagger.core.KafkaProtoSQLProcessor.main(KafkaProtoSQLProcessor.java:37) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_322]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_322]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_322]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_322]
	at org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:355) ~[flink-dist_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:222) ~[flink-dist_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.client.ClientUtils.executeProgram(ClientUtils.java:114) ~[flink-dist_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.client.deployment.application.DetachedApplicationRunner.tryExecuteJobs(DetachedApplicationRunner.java:84) ~[flink-dist_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.client.deployment.application.DetachedApplicationRunner.run(DetachedApplicationRunner.java:70) ~[flink-dist_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.runtime.webmonitor.handlers.JarRunHandler.lambda$handleRequest$0(JarRunHandler.java:104) ~[flink-dist_2.12-1.14.3.jar:1.14.3]
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604) [?:1.8.0_322]
	at java.lang.Thread.run(Thread.java:750) [?:1.8.0_322]
Caused by: org.apache.flink.table.api.ValidationException: SQL validation failed. Cannot instantiate user-defined function 'json_update_jpath'.
	at org.apache.flink.table.planner.calcite.FlinkPlannerImpl.org$apache$flink$table$planner$calcite$FlinkPlannerImpl$$validate(FlinkPlannerImpl.scala:164) ~[flink-table_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.table.planner.calcite.FlinkPlannerImpl.validate(FlinkPlannerImpl.scala:107) ~[flink-table_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.table.planner.operations.SqlToOperationConverter.convert(SqlToOperationConverter.java:215) ~[flink-table_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.table.planner.delegation.ParserImpl.parse(ParserImpl.java:101) ~[flink-table_2.12-1.14.3.jar:1.14.3]
	at org.apache.flink.table.api.internal.TableEnvironmentImpl.sqlQuery(TableEnvironmentImpl.java:716) ~[flink-table_2.12-1.14.3.jar:1.14.3]
	at io.odpf.dagger.core.StreamManager.registerOutputStream(StreamManager.java:185) ~[?:?]
	at io.odpf.dagger.core.KafkaProtoSQLProcessor.main(KafkaProtoSQLProcessor.java:33) ~[?:?]
	... 12 more

Expected behavior
The expected output of the sql query suppose to be {"k1":"v1","k2":"replaced_value","k3":"v3"}
Analysis
We have gone through the logs of task-manager and job-manager during the application startup. The python third-party dependencies as mentioned in requirements.txt file are properly installed in task-manager container, however not in jobmanager. If you manually install the third-party dependency in job-manager container and restart the job, the job is properly started with the udf function properly resulting in the data.
We are working on such use-case where python udf having third-party dependencies are needed. Please connect with us for more details.

We found a fix for this issue. The python UDF using third-party dependencies should be packaged with  pip (version >= 7.1.0) and setuptools (version >= 37.0.0) as mentioned in docs.

repo: odpf/dagger


text:
Replace InfluxQL queries with Flux queries in Grafana dashboard

InfluxQL queries are incompatible with InfluxDB 2.0 and later.. Thus, the queries for metrics in the Firehose Grafana dashboard must switch to Flux queries supported by InfluxDB 2.0+

Hey @sumitaich1998, I would like to pick this up. I would be needing your guidance for this(kinda new to this project as well as flux)

Hey @sumitaich1998, I would like to pick this up. I would be needing your guidance for this(kinda new to this project as well as flux)

cool, i will help u with any doubts

@iharshit009 you'll need to set up Grafana locally . Go through this guide on how to set up Grafana and InfluxDB with Firehose.

source: gharchive/issue

repo: odpf/firehose

license_type: permissive

license_source: github-api


text:
fix: spec reading where asset is optional

Change logs:

[x] add capability to read job without assets folder

Pull Request Test Coverage Report for Build 3262485380

4 of 6 (66.67%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 80.502%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client/local/specio/job_spec_io.go
4
6
66.67%

Files with Coverage Reduction
New Missed Lines
%

ext/notify/pagerduty/pagerdutynotifier.go
2
93.75%

Totals

Change from base Build 3218867138:
-0.03%

Covered Lines:
7989

Relevant Lines:
9924

💛  - Coveralls

source: gharchive/pull-request

authors: coveralls deryrahman

repo: odpf/optimus


text:
CTS fails with java metaspace error (UBI-8 container image)

When testing Release 2.3, in k8s or compose (or indeed plain docker) the graph CTS will fail with:
Fri Oct 02 14:07:58 GMT 2020 CTS_Server Information CONFORMANCE-SUITE-0012 The Open Metadata Conformance Test Case repository-type-definition-event-396 is initializing; see https://egeria.odpi.org/open-metadata-conformance-suite/docs/repository-workbench/test-cases/repository-type-definition-event-test-case.md for documentation
Fri Oct 02 14:07:58 GMT 2020 CTS_Server Information CONFORMANCE-SUITE-0014 The Open Metadata Conformance Test Case repository-type-definition-event-396 has completed with 10 successful assertions, 0 unsuccessful assertions, 0 unexpected exceptions and 7 discovered properties.  The message on completion was: Type definition event successfully processed
Fri Oct 02 14:07:58 GMT 2020 CTS_Server Information CONFORMANCE-SUITE-0012 The Open Metadata Conformance Test Case repository-typedef-AttachedNoteLog-event-396 is initializing; see https://egeria.odpi.org/open-metadata-conformance-suite/docs/repository-workbench/test-cases/repository-typedef-test-case.md for documentation
Terminating due to java.lang.OutOfMemoryError: Metaspace

I didn't observe this with other usage of egeria or the inmem repository.
This does not occur when run locally.
The reason appears to be that the Redhat UBI-8 image (which we switched to for this release) sets the metaspace space explicitly - see https://access.redhat.com/solutions/2038983
the article specifies a whole lot of things that could be checked - in case of leaks, but notes that by default metaspace is not artificially limited by the jvm. And that apps with many classes may get an issue when restricted
One of the recommended actions, and the one I intend to take, is to remove the artificial metaspace limit.
JVM utilization could be looked into in more depth, but at this point it seems hard to justify expending the resource
cc: @grahamwallis

The simple docs for the UBI-8 image for openjdk11 make NO mention of this setting
docker run registry.access.redhat.com/ubi8/openjdk-11 cat /help.md

The working value appears to be
-XX:MaxMetaspaceSize=unlimited

The image offers

JAVA_OPTS
JAVA_OPTS_APPEND

Since it's not documented what is set in the former, it would seem adding to the latter makes sense - will have to see if it can OVERRIDE the presumably coded specific, smaller setting

Before:
jonesn:egeria/ (issue3740) $ kubectl logs lab-odpi-egeria-lab-dev-568cfff9dc-jlbxb | head                             [16:33:16]
 1 Dockerfile +                                                                                X
/usr/local/s2i/run: line 15: /opt/jboss/container/maven/default//scl-enable-maven: No such file or directory
Starting the Java application using /opt/jboss/container/java/run/run-java.sh ...
INFO exec  java -XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MaxMetaspaceSize=100m -XX:+ExitOnOutOfMemoryError -cp "." -jar /deployments/server/server-chassis-spring-2.3.jar
 ODPi Egeria
    ____   __  ___ ___    ______   _____                                 ____   _         _     ___
   / __ \ /  |/  //   |  / ____/  / ___/ ___   ____ _   __ ___   ____   / _  \ / / __    / /  / _ /__   ____ _  _
  / / / // /|_/ // /| | / / __    \__ \ / _ \ / __/| | / // _ \ / __/  / /_/ // //   |  / _\ / /_ /  | /  _// || |
 / /_/ // /  / // ___ |/ /_/ /   ___/ //  __// /   | |/ //  __// /    /  __ // // /  \ / /_ /  _// / // /  / / / /
 \____//_/  /_//_/  |_|\____/   /____/ \___//_/    |___/ \___//_/    /_/    /_/ \__/\//___//_/   \__//_/  /_/ /_/

After (local build)
jonesn:egeria/ (issue3740) $ docker run docker.io/library/image                                                       [16:45:41]
/usr/local/s2i/run: line 15: /opt/jboss/container/maven/default//scl-enable-maven: No such file or directory
Starting the Java application using /opt/jboss/container/java/run/run-java.sh ...
INFO exec  java -XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MaxMetaspaceSize=100m -XX:+ExitOnOutOfMemoryError -XX:MaxMetaspaceSize=1g -cp "." -jar /deployments/server/server-chassis-spring-2.3.jar
 ODPi Egeria
    ____   __  ___ ___    ______   _____                                 ____   _         _     ___
   / __ \ /  |/  //   |  / ____/  / ___/ ___   ____ _   __ ___   ____   / _  \ / / __    / /  / _ /__   ____ _  _
  / / / // /|_/ // /| | / / __    \__ \ / _ \ / __/| | / // _ \ / __/  / /_/ // //   |  / _\ / /_ /  | /  _// || |
 / /_/ // /  / // ___ |/ /_/ /   ___/ //  __// /   | |/ //  __// /    /  __ // // /  \ / /_ /  _// / // /  / / / /
 \____//_/  /_//_/  |_|\____/   /____/ \___//_/    |___/ \___//_/    /_/    /_/ \__/\//___//_/   \__//_/  /_/ /_/

 :: Powered by Spring Boot (v2.3.3.RELEASE) ::

^C%

Unfortunately I could not easily set the value to limited without changing many other settings that the redhat image sets up and was keen to make the minimum change. 0,-1 or 'unlimited' are invalid.
Recommendations online tend to either go with unset, or to a high value for a production guard.
Redhat defaults to 100m. Many sites suggest several 100m, but could be more for complex app. Ours is so I am setting
to 1g. Note this is a safety limit only.

repo: odpi/egeria


text:
#7309 add support for building lightweight chassis

Signed-off-by: Nigel Jones nigel.l.jones+git@gmail.com

Description
Adds support to build a lightweight chassis for gradle builds.
Build by adding -PadminChassisOnly, for example
./gradlew -PadminChassisOnly build -x test -x javadoc

to build egeria with a cut-down admin chassis, and skipping test & javadoc.

Related Issue(s)
Fixes #7309

Testing

Built with & without flag, and checked content of artifacts ie when set:
% jar -tf server-chassis-spring-3.15-SNAPSHOT.jar | grep spring | grep 3.15
BOOT-INF/lib/admin-services-spring-3.15-SNAPSHOT.jar
BOOT-INF/lib/platform-services-spring-3.15-SNAPSHOT.jar
BOOT-INF/lib/spring-rest-client-connector-3.15-SNAPSHOT.jar

Release Notes & Documentation
Should be added to dojo documentation when happy (@mandy-chessell please indicate if you plan to do this)

Additional notes
This change replicates what we have with maven (though there we typically set via mvn with -D instead of -P - the implementation for gradle is more aligned with the normal way of setting gradle properties
In maven there is a conditional build for the connector configuration factory. I've implemented this. However the gradle build doesn't currently build an uber jar for this project, so the change makes no difference..... this condition could be removed. It's only relevant when building an uber jar since the dependencies are runtime only.
For the server chassis

gaf wasn't in the gradle build at all. I presume it should be, so added
4 other dependencies looked as if they should have been excluded, but weren't. I have done so for gradle.

Please review. I can consolidate these changes with another commit
NOTE: I have not actually RUN a cut down platform.

This is good.  I was surprised by the following libraries but realized they are the client-side libraries pulled in by the governance server services and so it is correct that they are there ...
asset-lineage-api-3.15-SNAPSHOT.jar
asset-lineage-client-3.15-SNAPSHOT.jar
asset-lineage-topic-connectors-3.15-SNAPSHOT.jar
data-engine-api-3.15-SNAPSHOT.jar
data-engine-client-3.15-SNAPSHOT.jar
data-engine-topic-connectors-3.15-SNAPSHOT.jar
governance-engine-api-3.15-SNAPSHOT.jar
governance-engine-client-3.15-SNAPSHOT.jar
governance-engine-topic-connectors-3.15-SNAPSHOT.jar

This is good. I was surprised by the following libraries but realized they are the client-side libraries pulled in by the governance server services and so it is correct that they are there ...

Thanks for confirming. I will merge.
We do have options in future to strip more out, but we may also need to bundle some groupings to make it easier to assemble. That can be for another issue if we ever want to.


text:
🛑 urbamonde.org is down

In 09c020f, urbamonde.org (https://www.urbamonde.org) was down:

HTTP code: 429
Response time: 593 ms

Resolved: urbamonde.org is back up in a21578a.

repo: odqo/upptime

license: MIT


text:
Create a oeg-resource

Include a TM mapping that links all the resources used by this website to a central resource (oeg-resource entity)

oopen in the correct repo

this will work after the creation of the central website

repo: oeg-upm/morph-website


text:
refactor: replace ethers with ethereum-cryptography

Description
Refactors the functions so that they all use ethereum-cryptography instead of ethers (several already did).
Also makes use of the latest version to do AES encryption, meaning that we can also remove crypto-js dependency from this repo.
Still working on tests but seems to be working pretty good so far.
Fixes # (issue)
The ethers package is absolutely huge and we don't use 98% of it. In mobile there is no tree shaking, meaning that including ethers causes our bundle size to increase massively and it hits the performance.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
The objective was to test for equivalence with the original functions which were exported from eth-crypto. I didn't want to install that here so I have forked the repo and installed the necessary stuff here https://github.com/JamieLivi/eth-crypto-tests.
Have tested pretty extensively and everything seems to work nice - results viewable here https://jamielivi.github.io/eth-crypto-tests/results/index.html

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (6d3e39e) to head (68055f2).

Additional details and impacted files
@@            Coverage Diff            @@
##           develop       #44   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           13         9    -4
  Lines          151       134   -17
  Branches        17        15    -2
=========================================
- Hits           151       134   -17

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles

Out of curiosity, is it possible to add ethers as a dev-dependency? Then you could add tests which create ciphertexts via ethers and decrypt via this JS implementation and vice versa. Those would probably be good tests to guarantee that we still have interoperability.

Out of curiosity, is it possible to add ethers as a dev-dependency? Then you could add tests which create ciphertexts via ethers and decrypt via this JS implementation and vice versa. Those would probably be good tests to guarantee that we still have interoperability.

I have just done it separately here https://github.com/JamieLivi/eth-crypto-tests so we don't clog up this repo.
If you guys wanted to release an rc version of this, I could import the functions straight from eth-crypto-js, but the functions are 100% the same on this branch as that testing repo.

repo: oesukam/eth-crypto-js


text:
Add CI builds for current Compiler

Add CI builds for all current GCC and Clang version, capable of C++17.
:question: MSVC too (related #3)? — too much pain to setup / maintain.

Getting a windows build is horrible (tested on Travis CI). Maybe another try on Github Actions later.

Other CI system, same annoyance with Windows … :man_facepalming:

Windows is still a nightmare – since it blocks progress it's ignored for now.

repo: offa/influxdb-cxx


text:
UPNP-IGD - Replace javax.xml.soap generation/parsing with manual text parsing

Open questions:

Should use US-ASCII/UTF-8 for all parsing? regardless of what XML header states?
Should use regex to parse information out of response? or maybe just basic text search? (android supports, but javame8 doesn't)

Done and tested, but not integrated.
To integrate, need to revamp NIO communication portal.

Done and tested, but not integrated.
To integrate, need to revamp NIO communication portal.

repo: offbynull/portmapper


text:
Multi-Step Q-Learning Implementation

Hello authors,
Thank you for sharing your interesting work. I have reviewed the paper and examined the repository, but I have not been able to locate the implementation of the multi-step DQN trick.
Could you please help me point out the location of the multi-step Q-Learning integration? Your assistance in this matter would be greatly appreciated.
Regards.

Hi taindp98,
Apologies for the very delayed response—I missed your comment earlier.
Thank you so much for your interest in our work!
To address your question, the implementation of multi-step Q-Learning can be found in lines 1568–1573 within the UTE class, located in the directory /grid_atari/atari.py. Specifically, we repeat the same action for the specified skip times. Here's the relevant code snippet:
for curr_skip in range(skip + 1):  # repeat the selected action for "skip" times
    ns, r, d, info_ = self._env.step(a)
    self.total_steps += 1
    es += 1
    skip_states.append(s)  # keep track of all observed skips
    skip_rewards.append(r)

I hope this clarifies your query! Please don't hesitate to reach out if you have further questions.


text:
Improve compatibility with other frameworks and future OMF.

Use init.fish instead of *.load to require files on load.

LGTM :+1:

authors: bobthecow derekstavis

license: mit

license_source: bigquery


text:
Deep Linking doesn't work seamlessly

Describe the bug
When clicking on/scanning the QR codes to open a wallet not all fields are opened
To Reproduce
Steps to reproduce the behavior:

Go to donate
Enter a value to generate the QR code
Click on the QR Code
Check the prefilled values in the wallet in sending page ... value is missing

Expected behavior
Open Mobile Wallet and/or Phoenix wallet with all prefilled values

Desktop Wallet works now

I close this, as this seems to be an issue with the Android wallet, rather than with dAppo

repo: ohager/burst-dappository


text:
Failure installing blurr, when dealing with the tranformers library

I am having some trouble just installing both the transformers library from huggingface and blurr library. If I install first
!pip install transformers==3.5
!pip install fastai

The option to set transformers == 3.5, is because this seems to be related to the problem I find later, but it does not solver the problem. Then, after checking that everything is ok, for example using
import fastai
import transformers
print('fastai version :', fastai.__version__)
print('transformers version :', transformers.__version__)

I try to
!pip install git+git://github.com/ohmeow/blurr.git@master

or even simpler
pip install ohmeow-blurr

The result from this is that I get
...
  Attempting uninstall: transformers
    Found existing installation: transformers 3.5.0
    Uninstalling transformers-3.5.0:
      Successfully uninstalled transformers-3.5.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
allennlp 1.2.2 requires transformers<3.6,>=3.4, but you have transformers 4.1.1 which is incompatible.
Successfully installed nlp-0.4.0 ohmeow-blurr-0.0.20 onnxruntime-1.6.0 rouge-score-0.0.4 seqeval-1.2.2 tokenizers-0.9.4 transformers-4.1.1 xxhash-2.0.0

I am running everything on a Kaggle notebook. Is there anything I am doing wrong, or is this even supposed to be a problem?
Thanks a lot!

Hey Pablo!
Looks like the issue may have something to do with allennlp (that's not a dependency in blurr) ... allennlp 1.2.2 requires transformers<3.6,>=3.4, but you have transformers 4.1.1 which is incompatible.
Have you tried updating it?
I'm working on a new release for blurr before end of year, and I'm mostly trying to keep things up-to-date with the latest transformers library, and so I'm not sure if the latest bits will work with transformers v.3.5.  You can try with your current setup and see ... lmk either way.

Thanks a lot @ohmeow ! You're totally right that this is probably not an issue of blurr, but of the transformers and allen-nlp libraries. I posted it here because if I did not install blurr, but only fastai and transformers this error would not appear. I found https://github.com/allenai/allennlp/commit/84a36a06e28894fe3fbf582186fd71a3eb25cd6f but if I only installed fastai and blurr I would not get the error, even if that implicitly installs transformers (because I can query the version).
So in conclusion I am not sure why that was happening but it seems there is a way to avoid the error.

authors: PabloAMC ohmeow

repo: ohmeow/blurr


text:
Mutect Dockerfile

Create, test and build Dockerfile for Mutect

quay.io/ohsu-comp-bio/mutect


text:
Support for non-Amazon S3 services

New features:

support multiple S3 implementations (ceph, minio, etc)
support for S3 URIs of the form s3://<endpoint>/<bucket>/<key>
standardized cloud storage backends and e2e tests

Fixes issues:

closes #257
closes #332
closes #338
closes #352

Known issues:

All non amazon S3 backends are hardcoded to use the V2 signing method.

Example config:
Worker:
  Storage:
    S3:
      - Endpoint: "localhost:8080"
         Key: "access_key"
         Secret: "secret_access_key"

TODO:

[ ] add new tests to travis build

closes #352

A few minor issues, but otherwise tons of great work here.
Also, this: https://github.com/rabix/bunny/issues/382#issuecomment-347526813

authors: adamstruck buchanae

repo: ohsu-comp-bio/funnel


text:
🛑 Ekşi Sözlük is down

In 20f7f08, Ekşi Sözlük (https://eksisozluk.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ekşi Sözlük is back up in 0551c95.

Resolved: Ekşi Sözlük is back up in 0551c95.

repo: okankocyigit/upptime


text:
Add spider for Fortaleza/CE

In this PR we add the spider to collect data from Fortaleza/CE gazette

@rennerocha
Thanks for all the tips. The code got much better now.

@rennerocha
Fixed all comments.
Thanks.

repo: okfn-brasil/diario-oficial


text:
Add line terminator heuristic

Most of time people expect to parse a CSV regardless line terminator. This PR adds a method to guess the line terminator of the stream if no line terminator is provided. However if a line terminator is provided by configuration it will use it.
Before parsing the file it unify all the line endings to \n. To be performant it only reads the first 4096 characters of the stream.

@topicus awesome - it would be really nice to also guess the separator if you are up for it ;-)
Also assume you are happy contributing under the MIT license (I'll merge now but please reply to confirm).

authors: rgrp topicus


text:
Fix heading on job page

Looks like we're using Resumator so this heading doesn't make sense:

Our other open positions:

I've just made it "Our open positions:". @nealbastek Please feel free to reopen if you'd like to change it further.

authors: nigelbabu tryggvib

repo: okfn/foundation


text:
[Idea] Migrate to ReactiveDict

Session is entirely based on ReactiveDict now: https://github.com/meteor/meteor/blob/devel/packages/session/session.js
Since: https://github.com/meteor/meteor/commit/624035fab8fb27b1d4f5d884518d92dd3d52e5e0
So rather then adding all the functionality to Session, it could be added to ReactiveDict.
This has the advantage of being able to isolate a namespace/ReactiveDict.
Any thoughts?
Cheers!

Might be a nice idea. Havent done much with ReactiveDict, but i will take a look at it

@RobertLowe So do you mean you would you want to add it to all ReactiveDicts? Or do you mean that rather than having it available on Session you would have a separate persistent ReactiveDict available?

@pauldowman no, not really but it depends on how it's implemented. I think injecting the functionality into ReactiveDict would be a poor choice over creating a new object. Something like:
MyPackageSettings = PersistentReactiveDict('MyNameSpace') where PersistentReactiveDict extends ReactiveDict would be useful.
Then the persistent session package would be one line:
Session = new PersistentReactiveDict('session');

using the let's say persistent-reactive-dict package. Like Session is with ReactiveDict: https://github.com/meteor/meteor/blob/devel/packages/session/session.js
OT: Another difficulty of Session +/- persistent-session is as an author you have to detect if it's used rather then just being able to trust your own namespace.

@RobertLowe I like this suggestion.

@RobertLowe Sorry for the super slow reply. This is a great idea, and we're definitely seeing how this is super useful, especially for writing packages.
But we'd like to see a couple things first:

Please fork the project from our repo, rather than creating a new one. This will help maintain code fixes between the repos, and will let us push fixes to you when we get them

Please leave the code in Javascript. Personal opinions about Coffeescript aside, we want to keep the module in Javascript to minimise the barriers for contributions. Everyone who knows Coffeescript also knows Javascript, but not necessarily vice versa.

Hey @rgould, no worries! (How have you been by the way?)

Please fork the project from our repo, rather than creating a new one. This will help maintain code fixes between the repos, and will let us push fixes to you when we get them

I did this on purpose, it's kind of a different thing. I'm happy maintaining it as is. The reason I referenced it was to flag you guys about it's creation.

Please leave the code in Javascript. Personal opinions about Coffeescript aside, we want to keep the module in Javascript to minimise the barriers for contributions. Everyone who knows Coffeescript also knows Javascript, but not necessarily vice versa.

I disagree, which alone is probably a good reason for it being a fork. Yay, open source! I'm an opinionated developer and I enjoy working with CoffeeScript, I'm not optimizing for contribution barriers, I'm optimizing for developer happiness, productivity and for my own utility. Which is why persistent-reactive-dict is written in CS.
Cheers!

@RobertLowe I'm well! Hope the same with you!
Yeah, I just figured if we used the same code base that it would make it easy to share bug fixes and patches quickly. But it's not a big deal at all, and it's a pretty small project anyway.

authors: RobertLowe jhuenges pauldowman rgould

repo: okgrow/meteor-persistent-session


text:
Breaking API changes with Node-MPV 2

Hey there,
I'm the author of Node-MPV. Thanks a lot for using it 🙂
I've been working on a Version 2 of the library for quite a while now and I think I will publish it to NPM within the next days or weeks.
Version 2 brings quite some changes to the table as it makes heavy use of promises to check if all the messages it sends to MPV over the socket are actually working or not.
You can find Version 2 here along with a Migration Guide and the Changelog.
I'm just filing this issue to inform you, that you either want to lock the Node-MPV version in your package.json or if you are willing to take the time, migrate your app to version 2, as soon as it is released.
I try to provide bugfixes for Version 1 in the future but I will probably not add new features. I think version 2 is a lot more robust and overall better so you might at least want to take a look 🙂
Cheers

Thank you very much for your help. I'll try to rewrite my Player to match the new version 2 api in a few days.

Cool 🙂 Just keep in mind that as long as I haven't merged the branch into master and published it on NPM yet, everything is still subject to change.
I don't think I'll change anything big but just keep in mind I might :)

Yeah, thank you :)

repo: okonek/tidal-cli-client


text:
Consider adding serialization/deserialization logic for Splines

Possible approaches:

Using boost::serialization.
Using custom JSON format.
Using completely custom format.

Won't do.

repo: okruz/BSplinebasis

license: Unlicense


text:
UserProfile custom attributes in lower camel case

Hi,
Using Version 2.5.0
when querying users I get the first 200 results with the custom UserProfile attributes named as expected (matching with what the API returns).
Going to the next page of 200 results suddenly the custom attributes are lower camel case.
Could you please have a look?

Hi @Flo451,
Thanks for reporting this. Can you please share the minimal piece of code to reproduce this issue?
A Fiddler log is also desirable to help investigate the issue.
Thanks!

After further testing it appears the lower camel case attribute is a duplicate. So in my case the custom attribute named JobFamily suddenly also has a duplicate named jobFamily.
import asyncio
from okta.client import Client as OktaClient

config = {

}
okta_client = OktaClient(config)

async def main():
    query_parameters = {'filter': 'status eq "ACTIVE"'}
    users, resp, err = await okta_client.list_users(query_parameters)
    allusers=[]
    while True:
        allusers+=users
        if resp.has_next():
            users, err = await resp.next()
        else:
            break
    # users = [user for user in allusers if hasattr(user.profile, "JobFamily")]
    for count, user in enumerate(allusers):
        print(count, end=' ')
        if hasattr(user.profile, "JobFamily"):
            print('check',end='| ')
        else:
            print('nope',end='| ')
        if hasattr(user.profile, "jobFamily"):
            print('check', end=' ')
        else:
            print('nope',end='| ')
        print()
        # print(count, hasattr(user.profile, "JobFamily"), hasattr(user.profile, "jobFamily"))

if __name__=='__main__':
    loop = asyncio.get_event_loop()
    loop.run_until_complete(main())

From row 200 we get a duplicated lower camel case attribute.
grep 200 -C10 output
190 check| nope|
191 check| nope|
192 check| nope|
193 check| nope|
194 check| nope|
195 check| nope|
196 check| nope|
197 check| nope|
198 check| nope|
199 check| nope|
200 check| check
201 nope| nope|
202 nope| nope|
203 check| check
204 check| check
205 check| check
206 check| check
207 check| check
208 check| check
209 check| check
210 check| check

@Flo451 Thank you for that information.  Have you confirmed with raw api calls that you are not getting jobFamily in your responses?

Yes, the custom attribute is JobFamily. The duplication also happens for other custom attributes. The duplicated values are not available in the raw api call results.

Resolved in 2.9.0

authors: Flo451 bretterer laura-rodriguez

repo: okta/okta-sdk-python


text:
The input paramter name in readme should be namespace instead of name

Since i use this action in my project, i got a warning
Warning: Unexpected input(s) 'name', valid inputs are ['entryPoint', 'args', 'namespace']

So i reviewed the code found in the action define file:
https://github.com/okteto/namespace/blob/1cb27522f16a4db1497f109dcbbab19af4756b6d/action.yml#L3-L7
but in the readme file is:
    - name: "Create devlopment environments namespace"
      uses: okteto/namespace@master
      with:
        name: devenvs-cindylopez

It's different. Although it does not affect anything, the program still works, but I think it is better to unify
I mentioned a pull request by the way: https://github.com/okteto/namespace/pull/2

fixed by #2

authors: dunmengjun rberrelleza

repo: okteto/namespace


text:
Api revises

Changes related https://github.com/okulbilisim/ojs/issues/1378 issue

closed with https://github.com/okulbilisim/ojs/commit/0dcb6d5039a6a33d38cc0235c82dff60d3fc54ed

repo: okulbilisim/ojs


text:
[Bug]: Sessions never auto load when passing path to nvim from commandline after recent updates

Your minimal.lua config

  local opts = {
    autostart = true, -- Automatically start the plugin on load?
    save_dir = vim.fn.expand(vim.fn.stdpath("data") .. "/sessions/"), -- directory where session files are saved
    silent = true, -- silent nvim message when sourcing session file
    -- use_git_branch = false, -- create session files based on the branch of a git enabled repository
    -- default_branch = "main", -- the branch to load if a session file is not found for the current branch
    autosave = true, -- automatically save session files when exiting Neovim
    -- should_autosave = function()
    --   return is_only_neotree_and_empty_buffer()
    -- end, -- function to determine if a session should be autosaved
    -- should_save = function()
    --   return true
    -- end,
    autoload = true,
    -- on_autoload_no_session = nil, -- function to run when `autoload = true` but there is no session to load
    on_autoload_no_session = function()
      vim.notify("No existing session to load.")
    end,
    follow_cwd = true, -- change session file name to match current working directory if it changes
    -- allowed_dirs = nil, -- table of dirs that the plugin will auto-save and auto-load from
    -- ignored_dirs = nil,
    -- ignored_branches = nil, -- table of branch patterns that are ignored for auto-saving and auto-loading
    telescope = {
      mappings = { -- table of mappings for the Telescope extension
        copy_session = "<C-c>",
        change_branch = "<C-b>",
        delete_session = "<C-d>",
      },
      icons = { -- icons displayed in the picker, set to nil to disable entirely
        branch = icons.common.git .. "",
        dir = icons.common.folder_open .. "",
        selected = icons.common.trace .. "",
      },
    },
  }

...

modules["olimorris/persisted.nvim"] = {
  --lazy = true,
  --event = "VeryLazy",
  lazy = false,
  priority = 1000,
  config = editor_config.persisted_nvim,
}

Error messages
No errors
Describe the bug
When opening nvim with no arguments it autoloads fine. When passing a directory e.g. nvim . it does not autoload.
I've made no changes to my setup in a while and the session never autoloads. Manually invoking works fine still.
Final checks

[X] I have made sure this issue exists in the latest version of the plugin
[X] I have tested with the minimal.lua config file above and still get the issue
[X] I have used SessionSave to save the session before restarting Neovim and using SessionLoad
[X] I have made sure this is not a duplicate issue

As per #145 this is intended. I outline in the README how you can implement your own functionality for this

authors: Ajaymamtora olimorris


text:
feat: add config option autosave_when_session_exists

As discussed #95.

Thanks for this.
Quick glance and looks good. I added a global variable a couple of days ago vim.g.persisted_exists...could that be utilised in the should_autosave callback? Or, could we pass the current session to the callback?
I think that would accomplish your ask, take up less lines of code and always bring more possibilities to the callback.

It's also possible, but this requires changing session_exists() or vim.g.persisted_exists.
Specifically, put the session called by write() in save() into session_exists() instead of just determining whether the session file in the current working directory exists.
vim.g.persisted_exists also needs to be changed based on conditions, such as the working directory changing when follow=true.
I personally think that this global variable can be completely replaced by session_exists().
To do this, user need to put the session_exists() API into the should_autosave function.

authors: MasouShizuka olimorris


text:
New label picker for editing events doesn't load labels

Editing an event doesn't load the labels

Resolved before I even noticed this issue in 8c76c7d95ff4a4e1134e357bb8f1557e77f86061

authors: audreywl newsch

repo: olinlibrary/abe-web-frontend


text:
Can this be integrated within Django

First of all, I've been looking all over for something like this in Python, lucky to find Nebulo.
Kudos.
I mostly work in the Django space, and would like to expose some tables and views using something like Nebulo, is there an easy way to pass the django.connection which holds the DB connection into this and it starts to work automatically.
Let me know.

Thanks, that's really nice to hear!
There is no public api or documentation for usage as a library yet, so any integrations you try to make will be unstable for a while. If you just want to try it out, you could do something like
from nebulo.server.flask import create_app
from graphql.type import GraphQLSchema

# connection is your connection string from django config
app = create_app(connection="connection string", schema='public', echo_queries=False)

schema: GraphQLSchema = app.config["graphql_schema"]
engine = app.config['engine']
session = app.config["database"].session

From there you can execute queries against that schema using standard python-graphql ecosystem using nebulo's database engine and session (sqlalchemy).
Hope that helps
Leaving this open for other django related discusssion

authors: olirice ranjanprj

repo: olirice/nebulo


text:
Can't connect to Elastic

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[ ] elastic.v2 (for Elasticsearch 1.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ x ] elastic.v5 (for Elasticsearch 5.x)
Please describe the expected behavior
Client connects and works as intended
Please describe the actual behavior
Client errors and returns no Elasticsearch node available
Any steps to reproduce the behavior?

Run sebp/elk:latest docker container
Have a config with elastic pool list ( in my case it's ["http://192.168.99.100:9200"] in json file )
Try to connect with code below

	log.Println(config.ElasticPool)
	elasticClient, err = elastic.NewClient(elastic.SetURL(config.ElasticPool[0]))
	if err != nil {
		log.Fatalln("Error creating elastic client: ", err.Error())
	}

I've tried numerous times to curl root of that address (http://192.168.99.100:9200) and I always get
$ curl http://192.168.99.100:9200
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   327  100   327    0     0  20437      0 --:--:-- --:--:-- --:--:-- 20437
{
  "name" : "HkRAP0f",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "qD5LuTUaQqG-GS9qTvdTOg",
  "version" : {
    "number" : "5.0.1",
    "build_hash" : "080bb47",
    "build_date" : "2016-11-11T22:08:49.812Z",
    "build_snapshot" : false,
    "lucene_version" : "6.2.1"
  },
  "tagline" : "You Know, for Search"
}

Me too...
elastic.v5

The wiki has a whole page dedicated to solving connection problems. If you still can't solve it, feel free to come back and I'll reopen the issue.

authors: CodeJuan olivere zet4

repo: olivere/elastic


text:
Accessory reachability

Can we have reachability feature implemented like in this homebridge mqtt plugin?
https://github.com/cflurin/homebridge-mqtt/issues/9

We could if it’s cool :)
What is it really about?

It's about triggering "No Response" message manually and not only just when bridge is unavailable. Let's say, I have some sensor or switch. Node-RED is subscribed to MQTT topics to get updates (current temperature or switch status). I have trigger node which sends device availability status (true) and if it is not getting new data within 1 minute, it will send false as availability status which leads to "No response" message in Home.app on iOS. Here's a screenshot from Home.app from that thread:
https://camo.githubusercontent.com/338d49fd9fe12fa29509adfccfc90926e64c8c0a/68747470733a2f2f6c68332e676f6f676c6575736572636f6e74656e742e636f6d2f634e3441414c764d537265654c4b616343386a6a6649315f5535515162686e5f465f54594e6137596b304a354d72585f30667137345f5435502d30544a69754d4e4c634944354956364a5662526e4f4c3532386b2d5652387a38414536537a505054654966315a457047354e7a2d7a503146516631706e4c666d39774e6b393048667365477a4f70645a4d4e6d5a5566326f795752366e4c756c635a6241626849566352677851595936483278536a6270573635726d434565752d6d66573254593959615870736e4e376a386c4456615377386e414539626a70654d6d47744143446d5631364b447748794f6f5a764432454f6c6c776a2d6c6b5a49546f4a4d49744e634f7a547742644638707537417073594b485336614c544b2d797770786145694f636e5646674b396b4f4f345f68495f647a715a4b77514178696f6f4c6a784d757168377a2d5832435336386a5f686a482d486c615a7745363747594868446254613261476c58684a747275302d55547062664258703252584e753358393869303873306d3374456450714854727843776f6634793170664437564c4470505f45736165394f4a374e6d534f4d70515a5f6c44656363745f7345647a79754a706364306d4b416363663435665466554c715f7a3858676465376b76665f6c337a4445727677766350336879374e2d654248797874316578535f7178384d365430574f414256626f6273653158716a49384e72745f635f47504639356b716f524e68487562592d4b73416e386f7a6a7167664f594f4e3131736c4675746b44694a79706c30663451766d475430375f773157635566585745456c346c6f446459316230706676644c6d57647670554f413d773630382d68313037382d6e6f

This was deprecated a few iOS releases ago and no longer supported.  Only way to trigger ‘no response’ programmatically is to return an error object to a get characteristics request.  This is the pattern from homebridge plugins, but with this code base I’m not sure how to cause the same message.

On Mar 3, 2019, at 1:26 PM, Daniil Molchanov notifications@github.com wrote:
It's about triggering "No Response" message manually and not only just when bridge is unavailable. Let's say, I have some sensor or switch. Node-RED is subscribed to MQTT topics to get updates (current temperature or switch status). I have trigger node which sends device availability status (true) and if it is not getting new data within 1 minute, it will send false as availability status which leads to "No response" message in Home.app on iOS. Here's a screenshot from Home.app from that thread:
https://camo.githubusercontent.com/338d49fd9fe12fa29509adfccfc90926e64c8c0a/68747470733a2f2f6c68332e676f6f676c6575736572636f6e74656e742e636f6d2f634e3441414c764d537265654c4b616343386a6a6649315f5535515162686e5f465f54594e6137596b304a354d72585f30667137345f5435502d30544a69754d4e4c634944354956364a5662526e4f4c3532386b2d5652387a38414536537a505054654966315a457047354e7a2d7a503146516631706e4c666d39774e6b393048667365477a4f70645a4d4e6d5a5566326f795752366e4c756c635a6241626849566352677851595936483278536a6270573635726d434565752d6d66573254593959615870736e4e376a386c4456615377386e414539626a70654d6d47744143446d5631364b447748794f6f5a764432454f6c6c776a2d6c6b5a49546f4a4d49744e634f7a547742644638707537417073594b485336614c544b2d797770786145694f636e5646674b396b4f4f345f68495f647a715a4b77514178696f6f4c6a784d757168377a2d5832435336386a5f686a482d486c615a7745363747594868446254613261476c58684a747275302d55547062664258703252584e753358393869303873306d3374456450714854727843776f6634793170664437564c4470505f45736165394f4a374e6d534f4d70515a5f6c44656363745f7345647a79754a706364306d4b416363663435665466554c715f7a3858676465376b76665f6c337a4445727677766350336879374e2d654248797874316578535f7178384d365430574f414256626f6273653158716a49384e72745f635f47504639356b716f524e68487562592d4b73416e386f7a6a7167664f594f4e3131736c4675746b44694a79706c30663451766d475430375f773157635566585745456c346c6f446459316230706676644c6d57647670554f413d773630382d68313037382d6e6f
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Maybe this will help? https://github.com/KhaosT/HAP-NodeJS/pull/556

Ps that was my pull request
I’m out on a vacation right now, but when I back am thinking of looking at this further.
I did look at how this node manages set characteristic events, and it is tied in at the accessory level and doesn’t follow the typical homebridge pattern.  But you could call the updateValue function at the characteristic level to set ‘not responding’. But it will need some thought, as this codebase is very elegant in its integration with hap-nodejs.

On Mar 5, 2019, at 4:25 AM, Daniil Molchanov notifications@github.com wrote:
Maybe this will help? KhaosT/HAP-NodeJS#556
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Figured out how to trigger this event from code and submitted PR

This sounds like a cool idea - how do I use it?!
For example I have an MQTT switch that is "not responding" - what do I send into homekit?
Reading the PR it seems like {"On":"NO_RESPONSE"} would work?

Exactly. You send "NO_RESPONSE" as a value for any valid characteristic and when you reopen Home.app or push the accessory icon and hold it for a while (it will open in fullscreen) its status will change to "not responding". As soon as any other valid value will be sent to Homekit, "not responding" status will go away.
For example, I use Trigger node which emits a message when there were no updates through MQTT within 1 minute.

#51 got merged to dev branch.
@radionoise  as you are the author I assume it fits your needs.
@crxporter could you test it yourself and provide me some info here?

I’m not actually running a dev version anywhere right now - I’ll load it up at work tomorrow and try it!

I went ahead and installed the dev branch on one of my pi's at home and tested this - with mixed results.
Using switches - it works when sending {"On":"NO_RESPONSE"}
Using dimmers (light bulb service) - it works when sending {"On":"NO_RESPONSE"} but not {"Brightness":"NO_RESPONSE"}

Which characteristics will this work with?

Using occupancy detector - it works when sending {"OccupancyDetected":"NO_RESPONSE"}
Additionally I can only get the "NO_RESPONSE" to appear when reopening the home app, not when long-pressing the item in homekit as stated above. When keeping the Home app open and sending NO_RESPONSE causes my switch or dimmer to show "Off" and still be controllable in Home.
The "recovery" from "no response" status back to a functioning item is pretty good, I can get it back by long-pressing, swiping to another room then back, or closing and reopening the app.
Conclusion - this looks like it works with SOME characteristics (I tested with "on" for both switch and dimmer services also tested with "OccupancyDetected" for occupancy sensor) and it will show an error when opening the Home app (tested on iphone and computer). It doesn't update while inside of the app (have to quit and reopen) and it doesn't "automatically" update back to good status - (have to long press or change screens).
I like it!
I'll use this to sort through my startup statuses, they always return "NULL" between boot of my pi and the first poll event (up to 10 minutes). During boot I will be able to see whether any item has been polled yet. This looks like it will work really well for long-lasting errors like boot-up or offline devices as @radionoise described as MQTT offline for over 1 minute.

It seems that NO_RESPONSE value will take effect only with required characteristics but not optional ones.

You're right about controlling device after NO_RESPONSE was set and Home.app was not restarted. Perhaps we should keep some state in the service that NO_RESPONSE was triggered. I did some research.
Right now here is the problem after triggering NO_RESPONSE and not reopening Home.app:

Turning switch OF does not fire "characteristic-change" event.
Turning switch ON fires two events simultaneously (one for previous OFF and one for ON).
We can preserve NO_RESPONSE state and send it to Homekit again if it was not recovered properly, but we see the result after we open Home.app when Light was ON.

I'll try to investigate further.

If you have some time, review the Characteristic.js file in hap-nodejs.  It caches state as well, so maintaining a local copy of state could be redundant.
Sent from my iPad

On Mar 6, 2019, at 1:57 AM, Daniil Molchanov notifications@github.com wrote:
You're right about controlling device after NO_RESPONSE was set and Home.app was not restarted. Perhaps we should keep some state in the service that NO_RESPONSE was triggered. I did some research.
Right now here is the problem after triggering NO_RESPONSE and not reopening Home.app:
Turning switch OF does not fire "characteristic-change" event.
Turning switch ON fires two events simultaneously (one for previous OFF and one for ON).
We can preserve NO_RESPONSE state and send it to Homekit again if it was not recovered properly, but we see the result after we open Home.app when Light was ON.
I'll try to investigate further.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

It seems that NO_RESPONSE value will take effect only with required characteristics but not optional ones.
After thinking about it more that was my guess as well.

Like I said - I like this idea. Once it's "figured out" it'll be pretty cool. It seems like you're headed in the right direction.

I'm glad to say, that NO_RESPONSE feature was improved in this PR: https://github.com/oliverrahner/node-red-contrib-homekit-bridged/pull/58.

I am closing this Issue.
Improvement merged into dev. Made by @radionoise and confirmed by @crxporter - thanks guys!
If you have a problem then first head to [this section in README](url
https://github.com/oliverrahner/node-red-contrib-homekit-bridged/tree/dev#no-response).
If it didn't help then feel free to open new Issue.

authors: NorthernMan54 Shaquu crxporter radionoise


text:
support findFirstOrThrow

Hi,
Im using findFirstOrThrow many in my app and I wonder what is the effort to support it as well.
From my understanding its just adding this action to middlewareByModel function in:
https://github.com/olivierwilkinson/prisma-soft-delete-middleware/blob/main/src/lib/createSoftDeleteMiddleware.ts#L68
Thank you

Hi there,
just wanted to let you know that I'm looking into this, I also thought it would be as simple as adding the findFirst middleware handler under the findFirstOrThrow field of middlewareByModel but it's failing some tests I added.
I'll have some time to work on it this weekend, if not sooner 👍

Thanks man, I appreciate it!

All fixed, this should be available in v1.2.0! 😄
Thanks again for raising this and please let me know if you have any other problems 👍

authors: olivierwilkinson tomhoffen


text:
CUDA error: out of memory when use gemma model

What is the issue?
system_message = {
        'role': 'system',
        'content': 'XXXX'
    }
    user_message = {
        'role': 'user',
        'content': 'XXXX'
    }
    messages.append(system_message)
    messages.append(user_message)
    stream = ollama.chat(
        model = model_name,
        messages = messages,
        stream=True
    )

when i use gemma do this work,it will be CUDA error: out of memory.the log is here.
ggml_init_cublas: GGML_CUDA_FORCE_MMQ:   no
ggml_init_cublas: CUDA_USE_TENSOR_CORES: yes
ggml_init_cublas: found 1 CUDA devices:
  Device 0: NVIDIA GeForce RTX 3070 Laptop GPU, compute capability 8.6, VMM: yes
llama_model_loader: loaded meta data with 24 key-value pairs and 254 tensors from D:\Ollama\models\blobs\sha256-456402914e838a953e0cf80caa6adbe75383d9e63584a964f504a7bbb8f7aad9 (version GGUF V3 (latest))
llama_model_loader: Dumping metadata keys/values. Note: KV overrides do not apply in this output.
llama_model_loader: - kv   0:                       general.architecture str              = gemma
llama_model_loader: - kv   1:                               general.name str              = gemma-7b-it
llama_model_loader: - kv   2:                       gemma.context_length u32              = 8192
llama_model_loader: - kv   3:                     gemma.embedding_length u32              = 3072
llama_model_loader: - kv   4:                          gemma.block_count u32              = 28
llama_model_loader: - kv   5:                  gemma.feed_forward_length u32              = 24576
llama_model_loader: - kv   6:                 gemma.attention.head_count u32              = 16
llama_model_loader: - kv   7:              gemma.attention.head_count_kv u32              = 16
llama_model_loader: - kv   8:     gemma.attention.layer_norm_rms_epsilon f32              = 0.000001
llama_model_loader: - kv   9:                 gemma.attention.key_length u32              = 256
llama_model_loader: - kv  10:               gemma.attention.value_length u32              = 256
llama_model_loader: - kv  11:                       tokenizer.ggml.model str              = llama
llama_model_loader: - kv  12:                      tokenizer.ggml.tokens arr[str,256000]  = ["<pad>", "<eos>", "<bos>", "<unk>", ...
llama_model_loader: - kv  13:                      tokenizer.ggml.scores arr[f32,256000]  = [0.000000, 0.000000, 0.000000, 0.0000...
llama_model_loader: - kv  14:                  tokenizer.ggml.token_type arr[i32,256000]  = [3, 3, 3, 2, 1, 1, 1, 1, 1, 1, 1, 1, ...
llama_model_loader: - kv  15:                tokenizer.ggml.bos_token_id u32              = 2
llama_model_loader: - kv  16:                tokenizer.ggml.eos_token_id u32              = 1
llama_model_loader: - kv  17:            tokenizer.ggml.unknown_token_id u32              = 3
llama_model_loader: - kv  18:            tokenizer.ggml.padding_token_id u32              = 0
llama_model_loader: - kv  19:               tokenizer.ggml.add_bos_token bool             = true
llama_model_loader: - kv  20:               tokenizer.ggml.add_eos_token bool             = false
llama_model_loader: - kv  21:                    tokenizer.chat_template str              = {% if messages[0]['role'] == 'system'...
llama_model_loader: - kv  22:               general.quantization_version u32              = 2
llama_model_loader: - kv  23:                          general.file_type u32              = 2
llama_model_loader: - type  f32:   57 tensors
llama_model_loader: - type q4_0:  196 tensors
llama_model_loader: - type q8_0:    1 tensors
llm_load_vocab: mismatch in special tokens definition ( 416/256000 vs 260/256000 ).
llm_load_print_meta: format           = GGUF V3 (latest)
llm_load_print_meta: arch             = gemma
llm_load_print_meta: vocab type       = SPM
llm_load_print_meta: n_vocab          = 256000
llm_load_print_meta: n_merges         = 0
llm_load_print_meta: n_ctx_train      = 8192
llm_load_print_meta: n_embd           = 3072
llm_load_print_meta: n_head           = 16
llm_load_print_meta: n_head_kv        = 16
llm_load_print_meta: n_layer          = 28
llm_load_print_meta: n_rot            = 192
llm_load_print_meta: n_embd_head_k    = 256
llm_load_print_meta: n_embd_head_v    = 256
llm_load_print_meta: n_gqa            = 1
llm_load_print_meta: n_embd_k_gqa     = 4096
llm_load_print_meta: n_embd_v_gqa     = 4096
llm_load_print_meta: f_norm_eps       = 0.0e+00
llm_load_print_meta: f_norm_rms_eps   = 1.0e-06
llm_load_print_meta: f_clamp_kqv      = 0.0e+00
llm_load_print_meta: f_max_alibi_bias = 0.0e+00
llm_load_print_meta: n_ff             = 24576
llm_load_print_meta: n_expert         = 0
llm_load_print_meta: n_expert_used    = 0
llm_load_print_meta: pooling type     = 0
llm_load_print_meta: rope type        = 2
llm_load_print_meta: rope scaling     = linear
llm_load_print_meta: freq_base_train  = 10000.0
llm_load_print_meta: freq_scale_train = 1
llm_load_print_meta: n_yarn_orig_ctx  = 8192
llm_load_print_meta: rope_finetuned   = unknown
llm_load_print_meta: model type       = 7B
llm_load_print_meta: model ftype      = Q4_0
llm_load_print_meta: model params     = 8.54 B
llm_load_print_meta: model size       = 4.84 GiB (4.87 BPW)
llm_load_print_meta: general.name     = gemma-7b-it
llm_load_print_meta: BOS token        = 2 '<bos>'
llm_load_print_meta: EOS token        = 1 '<eos>'
llm_load_print_meta: UNK token        = 3 '<unk>'
llm_load_print_meta: PAD token        = 0 '<pad>'
llm_load_print_meta: LF token         = 227 '<0x0A>'
llm_load_tensors: ggml ctx size =    0.19 MiB
llm_load_tensors: offloading 28 repeating layers to GPU
llm_load_tensors: offloading non-repeating layers to GPU
llm_load_tensors: offloaded 29/29 layers to GPU
llm_load_tensors:        CPU buffer size =   796.88 MiB
llm_load_tensors:      CUDA0 buffer size =  4955.54 MiB
...........................................................................
llama_new_context_with_model: n_ctx      = 2048
llama_new_context_with_model: freq_base  = 10000.0
llama_new_context_with_model: freq_scale = 1
llama_kv_cache_init:      CUDA0 KV buffer size =   896.00 MiB
llama_new_context_with_model: KV self size  =  896.00 MiB, K (f16):  448.00 MiB, V (f16):  448.00 MiB
llama_new_context_with_model:  CUDA_Host input buffer size   =    11.02 MiB
llama_new_context_with_model:      CUDA0 compute buffer size =   506.00 MiB
llama_new_context_with_model:  CUDA_Host compute buffer size =     6.00 MiB
llama_new_context_with_model: graph splits (measure): 2
{"function":"initialize","level":"INFO","line":440,"msg":"initializing slots","n_slots":1,"tid":"20160","timestamp":1710811450}
{"function":"initialize","level":"INFO","line":452,"msg":"new slot","n_ctx_slot":2048,"slot_id":0,"tid":"20160","timestamp":1710811450}
time=2024-03-19T09:24:10.303+08:00 level=INFO source=dyn_ext_server.go:162 msg="Starting llama main loop"
{"function":"update_slots","level":"INFO","line":1590,"msg":"all slots are idle and system prompt is empty, clear the KV cache","tid":"29364","timestamp":1710811450}
{"function":"launch_slot_with_data","level":"INFO","line":833,"msg":"slot is processing task","slot_id":0,"task_id":0,"tid":"29364","timestamp":1710811450}
{"function":"update_slots","ga_i":0,"level":"INFO","line":1828,"msg":"slot progression","n_past":0,"n_past_se":0,"n_prompt_tokens_processed":63,"slot_id":0,"task_id":0,"tid":"29364","timestamp":1710811450}
{"function":"update_slots","level":"INFO","line":1852,"msg":"kv cache rm [p0, end)","p0":0,"slot_id":0,"task_id":0,"tid":"29364","timestamp":1710811450}
CUDA error: out of memory
  current device: 0, in function ggml_cuda_pool_malloc_vmm at C:\Users\jeff\git\ollama\llm\llama.cpp\ggml-cuda.cu:8658
  cuMemSetAccess(g_cuda_pool_addr[device] + g_cuda_pool_size[device], reserve_size, &access, 1)
GGML_ASSERT: C:\Users\jeff\git\ollama\llm\llama.cpp\ggml-cuda.cu:256: !"CUDA error"

windows 11 and RTX 3070 Laptop GPU.Does anyone know if it’s a model error or another reason?
What did you expect to see?
user_message = {
        'role': 'user',
        'content': 'XXXX'
    }
    messages.append(system_message)
    stream = ollama.chat(
        model = model_name,
        messages = messages,
        stream=True
    )

if i use just like this it's ok.however other model(dolphin-mistral:latest,qwen:7b) doesn't have this problem.
Steps to reproduce
No response
Are there any recent changes that introduced the issue?
No response
OS
Windows
Architecture
x86
Platform
No response
Ollama version
0.1.29
GPU
Nvidia
GPU info
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 527.99       Driver Version: 527.99       CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name            TCC/WDDM | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ... WDDM  | 00000000:01:00.0  On |                  N/A |
| N/A   45C    P0    32W / 115W |    701MiB /  8192MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      5916    C+G   ...y\ShellExperienceHost.exe    N/A      |
|    0   N/A  N/A      7564    C+G   C:\Windows\explorer.exe         N/A      |
|    0   N/A  N/A      8684    C+G   ...n1h2txyewy\SearchHost.exe    N/A      |
|    0   N/A  N/A      8708    C+G   ...artMenuExperienceHost.exe    N/A      |
|    0   N/A  N/A      9864    C+G   ...8bbwe\Notepad\Notepad.exe    N/A      |
|    0   N/A  N/A     10100    C+G   ...2txyewy\TextInputHost.exe    N/A      |
|    0   N/A  N/A     11228    C+G   ...cw5n1h2txyewy\LockApp.exe    N/A      |
|    0   N/A  N/A     16052    C+G   ...cal\Obsidian\Obsidian.exe    N/A      |
|    0   N/A  N/A     19716    C+G   ...2gh52qy24etm\Nahimic3.exe    N/A      |
|    0   N/A  N/A     21696    C+G   ...l-0.15.0\WeaselServer.exe    N/A      |
|    0   N/A  N/A     22360    C+G   ...8bbwe\WindowsTerminal.exe    N/A      |
|    0   N/A  N/A     22876    C+G   ...lPanel\SystemSettings.exe    N/A      |
|    0   N/A  N/A     23712    C+G   ...d\runtime\WeChatAppEx.exe    N/A      |
|    0   N/A  N/A     26532    C+G   E:\VSCode\Code.exe              N/A      |
|    0   N/A  N/A     28660    C+G   ...me\Application\chrome.exe    N/A      |
|    0   N/A  N/A     30704    C+G   ...ge\Application\msedge.exe    N/A      |
+-----------------------------------------------------------------------------+

CPU
Intel
Other software
No response

Hello,
I tested Gemma:7b on my machine(not laptop) on CPU only, it works. I can tell you Gemma:7b does not take too much resource on computer.
Thanks,

Hello,
I tested Gemma:7b on my machine(not laptop) on CPU only, it works. I can tell you Gemma:7b does not take too much resource on computer.
Thanks,

I have also tested it, and it runs normally in most cases. The problem only occurs when I run it according to the prompt format I mentioned above. I'm not sure if it's a format issue. Thank you!

Hi there, this should be improved as of 0.1.32 - please let me know if that's not the case!

Hi there, this should be improved as of 0.1.32 - please let me know if that's not the case!您好，这应该从 0.1.32 开始改进 - 如果不是这种情况，请告诉我！

Thank you, I have tested it on version 0.1.32 and everything works fine.

authors: OPDEV001 jmorganca ycyy

repo: ollama/ollama


text:
option to change the model loading device (CPU/GPU)

it would be great if we can mention the device the model to be loaded (CPU/GPU).

With GPUs, you can select the device by setting CUDA_VISIBLE_DEVICES.  If you want to load a model on CPU and avoid GPU, set num_gpu to zero (https://github.com/ollama/ollama/issues/6950#issuecomment-2373663650).  If you want all models to avoid GPU, set OLLAMA_LLM_LIBRARY=cpu.

authors: ansilmbabl rick-github


text:
🛑 MediaNet is down

In 924ed00, MediaNet (https://medianet-pa.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MediaNet is back up in 6ad43fe.

repo: olmloa/upptime


text:
Update default csv url

testing deploy etc...

can this go in, @will-moore?

(other than that some of the thumbnails aren't loading...)

authors: joshmoore will-moore


text:
🛑 UoD SLS OMERO (image 3925540 - render_image) is down

In 62b6a3a, UoD SLS OMERO (image 3925540 - render_image) (https://omero.lifesci.dundee.ac.uk/webgateway/render_image/3925540/3/5/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UoD SLS OMERO (image 3925540 - render_image) is back up in cead36f.

repo: ome/upptime


text:
🛑 UoD SLS OMERO (public) is down

In f1bbd02, UoD SLS OMERO (public) (https://omero.lifesci.dundee.ac.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UoD SLS OMERO (public) is back up in 059ed04 after 11 minutes.


text:
🛑 OME documentation is down

In f55ce38, OME documentation (https://docs.openmicroscopy.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OME documentation is back up in c466115.


text:
Fix Crash Loading Normals without NormalIndex

Fix #354

test me

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/621/consoleText

test me

test me

test me

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/622/consoleText

Build Passed :ok_hand:
You can safely merge 'fix-indexedFaceSet-normal' into 'develop'.

:+1:

authors: DavidMansolino cyberbotics-jenkins

repo: omichel/webots


text:
Advance filtering for transaction break with some query

Describe the bug
I'm trying to use advance filter but it breaks and return 500 with this curl
curl 'http://localhost:4000/api/admin/transaction.all' \
  -H 'Accept: application/vnd.omisego.v1+json' \
  -H 'Referer: http://localhost:9000/admin/wallets/futh731508527610/transactions' \
  -H 'Authorization: OMGAdmin dXNyXzAxZGQyZXlycDNqazFhNTUzdjI2bnBtOGMxOmpMLWpGOHdlb2Q1d2hlX2hOTVcxNl9SUWJUVzE1b2M2S18tSzFULWFkeWc=' \
  -H 'Content-Type: application/json;charset=UTF-8' \
  --data-binary '{
    "per_page":10,
    "sort_by":"created_at",
    "sort_dir":"desc",
    "match_any":[
      {
        "field":"from_wallet",
        "comparator":"contains",
        "value":"futh731508527610"
      },{
        "field":"to_wallet",
        "comparator":"contains",
        "value":"futh731508527610"
      }
    ]
  }'

# FunctionClauseError at POST /api/admin/transaction.all

Exception:

    ** (FunctionClauseError) no function clause matching in EWallet.Web.MatchAnyQuery.do_filter/5

    The following arguments were given to EWallet.Web.MatchAnyQuery.do_filter/5:

        # 1
        false

        # 2
        :to_wallet

        # 3
        [:address, :name, :identifier, :enabled, :inserted_at, :created_at]

        # 4
        "contains"

        # 5
        "futh731508527610"

    Attempted function clauses (showing 3 out of 3):

        def do_filter(dynamic, field, -:uuid-, comparator, value)
        def do_filter(dynamic, field, -nil-, comparator, -nil = value-)
        def do_filter(dynamic, field, -nil-, comparator, value)

        (ewallet) lib/ewallet/web/filters/match_any_query.ex:23: EWallet.Web.MatchAnyQuery.do_filter/5
        (ewallet) lib/ewallet/web/filters/match_parser.ex:183: anonymous fn/4 in EWallet.Web.MatchParser.filter/5
        (elixir) lib/enum.ex:3317: Enumerable.List.reduce/3
        (elixir) lib/enum.ex:1990: Enum.reduce_while/3
        (ewallet) lib/ewallet/web/filters/match_parser.ex:177: EWallet.Web.MatchParser.filter/5
        (ewallet) lib/ewallet/web/filters/match_parser.ex:35: EWallet.Web.MatchParser.build_query/6
        (ewallet) lib/ewallet/web/orchestrator.ex:61: EWallet.Web.Orchestrator.build_query/3
        (ewallet) lib/ewallet/web/orchestrator.ex:37: EWallet.Web.Orchestrator.query/4
        (admin_api) lib/admin_api/v1/controllers/transaction_controller.ex:173: AdminAPI.V1.TransactionController.query_records_and_respond/3
        (admin_api) lib/admin_api/v1/controllers/transaction_controller.ex:15: AdminAPI.V1.TransactionController.action/2
        (admin_api) lib/admin_api/v1/controllers/transaction_controller.ex:15: AdminAPI.V1.TransactionController.phoenix_controller_pipeline/2
        (admin_api) lib/admin_api/endpoint.ex:15: AdminAPI.Endpoint.instrument/4
        (phoenix) lib/phoenix/router.ex:278: Phoenix.Router.__call__/1
        (phoenix) lib/phoenix/router/route.ex:147: Phoenix.Router.Route.forward/4
        (phoenix) lib/phoenix/router.ex:278: Phoenix.Router.__call__/1
        (admin_api) lib/admin_api/endpoint.ex:15: AdminAPI.Endpoint.plug_builder_call/2
        (admin_api) lib/admin_api/endpoint.ex:17: AdminAPI.Endpoint."call (overridable 2)"/2
        (admin_api) lib/plug/debugger.ex:122: AdminAPI.Endpoint."call (overridable 3)"/2
        (admin_api) lib/admin_api/endpoint.ex:15: AdminAPI.Endpoint."call (overridable 4)"/2
        (admin_api) lib/admin_api/endpoint.ex:15: AdminAPI.Endpoint.call/2

## Connection details

### Params

    %{"match_any" => [%{"comparator" => "contains", "field" => "from_wallet", "value" => "futh731508527610"}, %{"comparator" => "contains", "field" => "to_wallet", "value" => "futh731508527610"}], "per_page" => 10, "sort_by" => "created_at", "sort_dir" => "desc"}

### Request info

  * URI: http://localhost:4000/api/admin/transaction.all
  * Query string:

### Headers

  * accept: application/vnd.omisego.v1+json
  * accept-encoding: gzip, deflate, br
  * accept-language: en-US,en;q=0.9
  * authorization: OMGAdmin dXNyXzAxZGQyZXlycDNqazFhNTUzdjI2bnBtOGMxOmpMLWpGOHdlb2Q1d2hlX2hOTVcxNl9SUWJUVzE1b2M2S18tSzFULWFkeWc=
  * connection: keep-alive
  * content-length: 218
  * content-type: application/json;charset=UTF-8
  * host: localhost:4000
  * origin: http://localhost:9000
  * referer: http://localhost:9000/admin/wallets/futh731508527610/transactions
  * user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.80 Safari/537.36

### Session

    nil

@jarindr Can you try with "field":"from_wallet.address" and "field":"from_wallet.address"?
It'll probably solve your issue and this internal server error will be fixed separately.

authors: jarindr unnawut

repo: omisego/ewallet


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/42823

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/42828

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44126

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/79966

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/85600

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86897

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88077

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/91290

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/97050

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98480

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/101021

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103800

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/109005

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110517

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111483

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112980

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113258

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116112

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117262

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120735

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/121203


text:
Scraping Apple device specs is broken In version 3.1.3

Before update to 3.1.3 with -s command i was able to generate all needed splashes now new version even with -s false skips following :
apple-splash-0-0.png
apple-splash-320-568.png
apple-splash-375-667.png
apple-splash-375-812.png
apple-splash-414-736.png
apple-splash-414-896.png
apple-splash-768-1024.png
apple-splash-810-1080.png
apple-splash-834-1112.png
apple-splash-834-1194.png
apple-splash-1024-1366.png
apple-splash-1242-2208.png

Execute cli command 'npx pwa-asset-generator ./logo.svg ./img/icons -p "5%" -b "linear-gradient(147deg, #FFE53B 0%, #FF2525 74%)" --type png --quality 100 --path-override "/img/icons"'
1.1  Execute cli command 'npx pwa-asset-generator ./logo.svg ./img/icons -p "5%" -b "linear-gradient(147deg, #FFE53B 0%, #FF2525 74%)" --type png --quality 100 --path-override "/img/icons" -s false '

OS: [macOS ]
npm version [ 6.14.7]
cli version [3.1.3]

Small Debug tip:
Returned back to v 3.1.1 Running commands :
npx pwa-asset-generator ./logo.svg ./img/icons -p "5%" -b "linear-gradient(147deg, #FFE53B 0%, #FF2525 74%)" --type png --quality 100 --path-override "/img/icons"
Generates:
apple-icon-120
apple-icon-167
apple-icon-152
apple-icon-180
apple-splash-0-0
apple-splash-320-568
apple-splash-375-667
apple-splash-375-812
apple-splash-414-736
apple-splash-414-896
apple-splash-768-1024
apple-splash-810-1080
apple-splash-834-1112
apple-splash-834-1194
apple-splash-1024-1366
manifest-icon-192
manifest-icon-512
npx pwa-asset-generator ./logo.svg ./img/icons -p "5%" -b "linear-gradient(147deg, #FFE53B 0%, #FF2525 74%)" --type png --quality 100 --path-override "/img/icons" -s false
**The rest of splashes

Hi @maklai-0x001, you were never supposed to get those images as an output. It was due to a recent change in the source page, which broke the functionality of the lib: https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/adaptivity-and-layout/
You can tell it by the image name: apple-splash-0-0, this doesn't make any sense.
v3.1.2 fixes that issue by properly scraping the table. After the scraping, this is the source of dimensions for the latest Apple human interface guidelines:
[
  {
    "device": "12.9\" iPad Pro",
    "portrait": {
      "width": 2048,
      "height": 2732
    },
    "landscape": {
      "width": 2732,
      "height": 2048
    },
    "scaleFactor": 2
  },
  {
    "device": "11\" iPad Pro",
    "portrait": {
      "width": 1668,
      "height": 2388
    },
    "landscape": {
      "width": 2388,
      "height": 1668
    },
    "scaleFactor": 2
  },
  {
    "device": "10.5\" iPad Pro",
    "portrait": {
      "width": 1668,
      "height": 2388
    },
    "landscape": {
      "width": 2388,
      "height": 1668
    },
    "scaleFactor": 2
  },
  {
    "device": "9.7\" iPad Pro",
    "portrait": {
      "width": 1536,
      "height": 2048
    },
    "landscape": {
      "width": 2048,
      "height": 1536
    },
    "scaleFactor": 2
  },
  {
    "device": "7.9\" iPad mini",
    "portrait": {
      "width": 1536,
      "height": 2048
    },
    "landscape": {
      "width": 2048,
      "height": 1536
    },
    "scaleFactor": 2
  },
  {
    "device": "10.5\" iPad Air",
    "portrait": {
      "width": 1668,
      "height": 2224
    },
    "landscape": {
      "width": 2224,
      "height": 1668
    },
    "scaleFactor": 2
  },
  {
    "device": "9.7\" iPad Air",
    "portrait": {
      "width": 1536,
      "height": 2048
    },
    "landscape": {
      "width": 2048,
      "height": 1536
    },
    "scaleFactor": 2
  },
  {
    "device": "10.2\" iPad",
    "portrait": {
      "width": 1620,
      "height": 2160
    },
    "landscape": {
      "width": 2160,
      "height": 1620
    },
    "scaleFactor": 2
  },
  {
    "device": "9.7\" iPad",
    "portrait": {
      "width": 1536,
      "height": 2048
    },
    "landscape": {
      "width": 2048,
      "height": 1536
    },
    "scaleFactor": 2
  },
  {
    "device": "iPhone 11 Pro Max",
    "portrait": {
      "width": 1242,
      "height": 2688
    },
    "landscape": {
      "width": 2688,
      "height": 1242
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone 11 Pro",
    "portrait": {
      "width": 1125,
      "height": 2436
    },
    "landscape": {
      "width": 2436,
      "height": 1125
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone 11",
    "portrait": {
      "width": 828,
      "height": 1792
    },
    "landscape": {
      "width": 1792,
      "height": 828
    },
    "scaleFactor": 2
  },
  {
    "device": "iPhone XS Max",
    "portrait": {
      "width": 1242,
      "height": 2688
    },
    "landscape": {
      "width": 2688,
      "height": 1242
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone XS",
    "portrait": {
      "width": 1125,
      "height": 2436
    },
    "landscape": {
      "width": 2436,
      "height": 1125
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone XR",
    "portrait": {
      "width": 828,
      "height": 1792
    },
    "landscape": {
      "width": 1792,
      "height": 828
    },
    "scaleFactor": 2
  },
  {
    "device": "iPhone X",
    "portrait": {
      "width": 1125,
      "height": 2436
    },
    "landscape": {
      "width": 2436,
      "height": 1125
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone 8 Plus",
    "portrait": {
      "width": 1080,
      "height": 1920
    },
    "landscape": {
      "width": 1920,
      "height": 1080
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone 8",
    "portrait": {
      "width": 750,
      "height": 1334
    },
    "landscape": {
      "width": 1334,
      "height": 750
    },
    "scaleFactor": 2
  },
  {
    "device": "iPhone 7 Plus",
    "portrait": {
      "width": 1080,
      "height": 1920
    },
    "landscape": {
      "width": 1920,
      "height": 1080
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone 7",
    "portrait": {
      "width": 750,
      "height": 1334
    },
    "landscape": {
      "width": 1334,
      "height": 750
    },
    "scaleFactor": 2
  },
  {
    "device": "iPhone 6s Plus",
    "portrait": {
      "width": 1080,
      "height": 1920
    },
    "landscape": {
      "width": 1920,
      "height": 1080
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone 6s",
    "portrait": {
      "width": 750,
      "height": 1334
    },
    "landscape": {
      "width": 1334,
      "height": 750
    },
    "scaleFactor": 2
  },
  {
    "device": "iPhone 6 Plus",
    "portrait": {
      "width": 1080,
      "height": 1920
    },
    "landscape": {
      "width": 1920,
      "height": 1080
    },
    "scaleFactor": 3
  },
  {
    "device": "iPhone 6",
    "portrait": {
      "width": 750,
      "height": 1334
    },
    "landscape": {
      "width": 1334,
      "height": 750
    },
    "scaleFactor": 2
  },
  {
    "device": "4.7\" iPhone SE",
    "portrait": {
      "width": 750,
      "height": 1334
    },
    "landscape": {
      "width": 1334,
      "height": 750
    },
    "scaleFactor": 2
  },
  {
    "device": "4\" iPhone SE",
    "portrait": {
      "width": 640,
      "height": 1136
    },
    "landscape": {
      "width": 1136,
      "height": 640
    },
    "scaleFactor": 2
  }
]

Please use the latest version and it should be good on all listed devices.

repo: onderceylan/pwa-asset-generator


text:
[API/Settings] Remote control to edit a profile

Inside a studio where hosts may move at different places, is there any possibility to easily change the shot associated to a mic source without having to edit a profile?
It may be interesting to control this kind of assignations, so it can be controlled by remote devices like Companion or custom Raspberry Pi devices.

Hello ! 👋
In the next release, some controls will be added through OSC :

power on/off
set/edit a profile config
change profile

On the other hand changing the shots associated with a mic is not planned for now, sorry 😢

repo: one-click-studio/gabin


text:
Fix relocate empty clusters

Fix the problem due to the fact that empty clusters were not removed from previous clusters. Add new array to store in which cluster is the point.

/intelci: run

/intelci: run

/intelci: run

/intelci: restart

repo: oneapi-src/oneDAL


text:
Finish Django Tutorial for a simple page example

Make it work:
https://docs.djangoproject.com/en/2.2/intro/tutorial01/

It is now working. Thanks DjangoGirls


text:
Talos v1.9.0

Describe the bug or feature request
Several things need to be changed when upgrading to Talos 1.9.0

Remove i915.force_probe=7d55 kernel arg
Update system extensions with new schematic id (not needed, extensions migrated fine)
Cilium with netkit (apply this change before upgrade to reduce amount of reboots)
Revamp rook wipe task to use talosctl wipe disk ... ? (currently not possible)

Code of Conduct

[x] I agree to follow this project's Code of Conduct

Closing issue and will change to netkit in the future.

license: WTFPL


text:
Switch Argo to PNS

See workflow executors documentation for comparison and configuration.

Addressed in https://github.com/onepanelio/manifests/pull/19

repo: onepanelio/core


text:
Point to new version 3.6

Added a new minor version 3.6.0
Point all urls to this new version in the library

I’m not sure we can just bump the api version like this in a client SDK, especially in a minor point release! Why isn’t this configurable?

@orf We enforce clients to use the latest API version, that’s why we don’t allow to be configurable.

authors: orf serbioboeronfido

repo: onfido/onfido-python