src ip is <IP_ADDRESS> when sending out packets to remote endpoints

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I'm trying to redirect traffic to an external endpoint.
Traffic ingress is with metallb v0.13.4 , bgp/frr enabled
Cilium v1.12.0 deployed with helm chart using these parameters:
    --namespace=kube-system \
    --set kubeProxyReplacement=strict \
    --set k8sServiceHost=<IP_ADDRESS> \
    --set k8sServicePort=6443 \
    --set l7Proxy=false

I have this Service and Endpoint:
kind: Service
apiVersion: v1
metadata:
  name: external-svc
spec:
  type: LoadBalancer
  #externalTrafficPolicy: Local
  externalTrafficPolicy: Cluster
  loadBalancerIP: X.Y.35.167
  ports:
    - name: http
      protocol: TCP
      port: 80
      targetPort: 80
    - name: https
      protocol: TCP
      port: 443
      targetPort: 443
---
kind: Endpoints
apiVersion: v1
metadata:
  name: external-svc
subsets:
  - addresses:
        - ip: X.Y.67.204
    ports:
      - port: 80
        name: http
      - port: 443
        name: https

In FRR vtysh, all nodes show :
nodeX# show ip bgp
<snip>
   Network          Next Hop            Metric LocPrf Weight Path
*> A.B.35.167/32 <IP_ADDRESS>                  0         32768 i

Ingress traffic is OK and arrives at the correct node(s). The problem is that cilium is sending back out the traffic with source ip <IP_ADDRESS>, whereas I believe it should be the Node's IP instead.
From tcpdump on the eth0 interface :
IN:
11:15:08.980597 IP A.B.C.D.52676 > X.Y.35.167.http: Flags [S], seq 337435015, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 7], length 0

OUT:
11:15:08.980630 IP <IP_ADDRESS>.52676 > X.Y.67.204.http: Flags [S], seq 337435015, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 7], length 0

@joestringer suggested to file this bug report.
Thanks
Cilium Version
v1.12.0
Kernel Version
5.15.0-46-generic #49-Ubuntu
Kubernetes Version
v1.24.4
Sysdump
Can provide sysdump information on demand privately.
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

Would it be possible to get a sysdump for this if you didn't solve it since then (I'm pchaigno on Cilium Slack)?


Set up code coverage workflow with CodeCov

This adds the code-coverage.yaml file for GH Actions. The test coverage report should be uploaded to CodeCov following this change.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


PP 179 update and release zksync js

What
Update references on the zksync js to continue with the rsk port.

Removed unused networks for rsk (rinkeby, ropsten)
Update references for rsk links on localhost, mainnet and testnet

Why
Continue with the port to rsk network
References
https://rsklabs.atlassian.net/browse/PP-179
https://www.npmjs.com/package/rif-aggregation

There is a release here https://www.npmjs.com/package/rif-aggregation

Also added a release in github releases here. We could compare which one should work
https://github.com/rsksmart/ri-aggregation/releases/tag/v0.11.8

@jurajpiar old files updated. Please check again


Updated packages to use the nnbd version of the intl package.

Description
Update of all the package to use the nnbd version of the intl package.
Removed a dependency in the stocks app on intl_translation that is no longer needed.

@darrenaustin are you going to keep working on this PR?

@darrenaustin are you going to keep working on this PR?

Yeah, I just got stuck pulling the chain of deps with the community gallery test. They need to update their intl dep, which in turn means another package they depend on flutter_localized_locales needs to be updated as well. Still working this through with them, but if this is hold you up or something let me know.

Looks like someone already updated the packages to the nnbd intl package so this is no longer needed.


Is it by design that parsing halts upon the first non-flag argument?

Given the following code:
var options = []optparse.Option{
	{"connection", 'c', optparse.KindRequired},
	{"migrations", 'm', optparse.KindRequired},
}

	results, rest, err := optparse.Parse(options, os.Args)

	fmt.Println("RESULTS")
	fmt.Println(results)
	fmt.Println("REST")
	fmt.Println(rest)

Is this output expected?
$ app --connection="foo" status
RESULTS
[{{connection 99 1} foo}]
REST
[status]

$ app status --connection="foo"
RESULTS
[]
REST
[status --connection=foo]

I'm looking for an alternative to the built-in flags package which halts parsing upon encountering the first non-flag argument. Is it by design that this package also halts? Or have I misconfigured things?
I suppose, in other words, that I would expect the same output in both code examples.

From @skeeto's blog:

GNU-style programs usually allow options and non-options to be mixed, though I don’t consider this to be essential.
...
An advantage of requiring that non-options follow options is that the first non-option demarcates the two groups, so -- is less often needed.


remove duplicate state in NewOp func

What this PR does:
Remove duplicate state in NewOp func
Which issue(s) this PR fixes:
Fixes #203
Checklist

[ ] Tests updated
[ ] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jeffsunxu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


fix links

https://analyze.polyverse.com

Thank you Wesinator! I'm sorry it took me a while to look at this. Github notifications are going to spam for some reason.


OSC-Platform-006: Deployment of pre-trained models

As a data scientist, i can deploy pre-trained models to be used in my pipeline (e.g. e.g. BERT, RoBERTa, DistilBERT)
As a first use-case, focus on deploying existing Allianz NLP model.

Yes, this works now. You can close the ticket.


chore: import repository https://github.com/kardasa/golang-http.git

this commit will trigger a pipeline to generate the CI/CD configuration which will create a second commit on this Pull Request before it auto merges

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign kardasa

/approve

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: kardasa
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign

/approve


4555 rtrans actions

Added release and deploy actions.
Updates for running and building Rtrans in OpenShift.

Hi @tschia/ @daveb-hni  , application code changes are ready to review. Please have a look.


compiler linking error during module installation within termux-app on android

Node Version: v8.9.0
Platform: Linux localhost 3.18.31-perf-gd9dd13b #1 SMP PREEMPT Wed Jul 5 18:59:18 CST 2017 aarch64 Android | executed within termux-app on android
Compiler:  clang version 5.0.0 (tags/RELEASE_500/final) / Target: aarch64--linux-android / Thread model: posix
Module: ijavascript which uses zeromq.js for communication

During the installation of the ijavascript module the zeroqm.js module wants to be compiled and produces an error during the linking step:
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _ZN3zmq13monitor_errorE' which may bind externally can not be used when making a shared object; recompile with -fPIC
The zeromq.js module must be linked against the preinstalled libzmq and requests the -fPIC compiler flag for c and c++ code.
 Skipping download of prebuilt binaries.
Requested to use external libzmq. Skipping libzmq build
gyp info it worked if it ends with ok
gyp verb cli [ '/data/data/com.termux/files/usr/bin/node',
gyp verb cli   '/data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild' ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| android | arm64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` succeeded python2 /data/data/com.termux/files/usr/bin/python2
gyp verb check python version `/data/data/com.termux/files/usr/bin/python2 -c "import platform; print(platform.python_version());"` returned: "2.7.14\n"
gyp verb get node dir no --target version specified, falling back to host node version: 8.9.1
gyp verb command install [ '8.9.1' ]
gyp verb install input version string "8.9.1"
gyp verb install installing version: 8.9.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 8.9.1
gyp verb build dir attempting to create "build" dir: /data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/build
gyp verb build dir "build" dir needed to be created? /data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/build
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: /data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/build/config.gypi
gyp verb config.gypi checking for gypi file: /data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/config.gypi
gyp verb common.gypi checking for gypi file: /data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/common.gypi
gyp verb gyp gyp format was not specified; forcing "make"
gyp info spawn /data/data/com.termux/files/usr/bin/python2
gyp info spawn args [ '/data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/data/data/com.termux/files/home/.node-gyp/8.9.1/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/data/data/com.termux/files/home/.node-gyp/8.9.1',
gyp info spawn args   '-Dnode_gyp_dir=/data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/data/data/com.termux/files/home/.node-gyp/8.9.1/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture arm64
gyp verb node dev dir /data/data/com.termux/files/home/.node-gyp/8.9.1
gyp verb `which` succeeded for `make` /data/data/com.termux/files/usr/bin/make
gyp info spawn make
gyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/build'
  g++ '-DNODE_GYP_MODULE_NAME=zmq' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION' '-D_GLIBCXX_USE_C99_MATH' -I/data/data/com.termux/files/home/.node-gyp/8.9.1/include/node -I/data/data/com.termux/files/home/.node-gyp/8.9.1/src -I/data/data/com.termux/files/home/.node-gyp/8.9.1/deps/uv/include -I/data/data/com.termux/files/home/.node-gyp/8.9.1/deps/v8/include -I../../nan  -Wall -Wextra -Wno-unused-parameter -O3 -fno-omit-frame-pointer -fPIE -fno-rtti -std=gnu++0x -MMD -MF ./Release/.deps/Release/obj.target/zmq/binding.o.d.raw   -c -o Release/obj.target/zmq/binding.o ../binding.cc
  g++ -shared -rdynamic -fPIE -pie  -Wl,-soname=zmq.node -o Release/obj.target/zmq.node -Wl,--start-group Release/obj.target/zmq/binding.o -Wl,--end-group -lzmq -llog
clang-5.0: warning: argument unused during compilation: '-pie' [-Wunused-command-line-argument]
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq7Context3NewERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq7Context5CloseERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq7Context6SetOptERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq7Context6GetOptERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3zmq7ContextE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3Nan10ObjectWrapE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3zmq7ContextE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3Nan10ObjectWrapE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket3NewERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket8GetStateEN2v85LocalINS1_6StringEEERKN3Nan20PropertyCallbackInfoINS1_5ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket10GetPendingEN2v85LocalINS1_6StringEEERKN3Nan20PropertyCallbackInfoINS1_5ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket10SetPendingEN2v85LocalINS1_6StringEEENS2_INS1_5ValueEEERKN3Nan20PropertyCallbackInfoIvEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket4BindERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket8BindSyncERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket6UnbindERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket10UnbindSyncERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket7ConnectERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket10GetSockOptERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket10SetSockOptERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket17AttachToEventLoopERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket19DetachFromEventLoopERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket4RecvERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket5ReadvERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket4SendERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket5SendvERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket5CloseERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket10DisconnectERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket7MonitorERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket9UnmonitorERKN3Nan20FunctionCallbackInfoIN2v85ValueEEE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq14monitor_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq13monitor_errorE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq20read_callback_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq20send_callback_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket12UV_BindAsyncEP9uv_work_s' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket17UV_BindAsyncAfterEP9uv_work_s' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket14UV_UnbindAsyncEP9uv_work_s' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket19UV_UnbindAsyncAfterEP9uv_work_s' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint32E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint32E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq14monitors_countE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket18UV_MonitorCallbackEP10uv_timer_si' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3zmq6SocketE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3Nan10ObjectWrapE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq20read_callback_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq20send_callback_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq14monitor_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq13monitor_errorE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket18UV_MonitorCallbackEP10uv_timer_si' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3zmq6SocketE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket15UV_PollCallbackEP9uv_poll_sii' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3Nan10ObjectWrapE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3Nan10ObjectWrap12WeakCallbackERKN2v816WeakCallbackInfoIS0_EE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq6Socket15IncomingMessage12FreeCallbackEPcPv' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3Nan10ObjectWrap12WeakCallbackERKN2v816WeakCallbackInfoIS0_EE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3Nan10ObjectWrapE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3Nan10ObjectWrapE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq8opts_intE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZNSt6__ndk13setIiNS_4lessIiEENS_9allocatorIiEEED2Ev' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint32E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq10opts_int64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_uint64E' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq11opts_binaryE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq20send_callback_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq20read_callback_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq14monitor_symbolE' which may bind externally can not be used when making a shared object; recompile with -fPIC
/data/data/com.termux/files/usr/bin/ld: Release/obj.target/zmq/binding.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZN3zmq13monitor_errorE' which may bind externally can not be used when making a shared object; recompile with -fPIC
  rm -rf "Release/zmq.node" && cp -af "Release/obj.target/zmq.node" "Release/zmq.node"
make: Leaving directory '/data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/build'
gyp info ok
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
npm verb lifecycle<EMAIL_ADDRESS>PATH: /data/data/com.termux/files/usr/lib/node_modules/npm/bin/node-gyp-bin:/data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq/node_modules/.bin:/data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/.bin:/data/data/com.termux/files/usr/lib/node_modules/.bin:/data/data/com.termux/files/usr/bin:/data/data/com.termux/files/usr/bin/applets
npm verb lifecycle<EMAIL_ADDRESS>CWD: /data/data/com.termux/files/usr/lib/node_modules/ijavascript/node_modules/zeromq
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm verb unlock done using /data/data/com.termux/files/home/.npm/_locks/staging-a3e96e1db80e25cf.lock for /data/data/com.termux/files/usr/lib/node_modules/.staging
+<EMAIL_ADDRESS>added 58 packages in 20.039s
npm verb exit [ 0, true ]
npm info ok

This seems like an issue with how zeromq.js does linking rather than a bug/problem in node-gyp -- I would recommend opening up an issue on their issue tracker with your logs and seeing if they can help further


THE BEST COMPANY TO RECOVER FUNDS AFTER SCAM DANIEL MEULI WEB RECOVERY

Entering the realm of crypto investment, I was hopeful but unaware of the risks ahead. Like many, I saw an opportunity for financial growth and invested 101,000 CAD with a binary options platform. Initially, things seemed promising, but when I tried to withdraw my funds weeks later, I hit a wall. Withdrawal requests were denied, and my attempts to contact customer support went unanswered. It became clear I had fallen victim to a scam. The situation worsened when I received an email demanding more money to facilitate my withdrawal—a blatant attempt to extort further funds from me. Feeling devastated and betrayed, I realized I needed help. Months later, I discovered Daniel Meuli Web Recovery through positive testimonials online. With little hope left, I decided to give them a chance. Reluctantly, I shared my experience with Daniel Meuli Web Recovery, providing details of the scam and the individuals involved. Their response was professional and reassuring, which gave me a glimmer of hope amidst my skepticism. Miraculously, within just 48 hours, Daniel Meuli Web Recovery managed to recover every cent of my stolen investment. It was an overwhelming moment of relief and joy, bringing closure to a painful chapter. This taught me invaluable lessons about the importance of caution and due diligence in the crypto world. It underscored the risks associated with quick gains and highlighted the need for thorough research before trusting any platform. My journey, though fraught with challenges, ultimately ended with a triumph thanks to the expertise and dedication of Daniel Meuli Web Recovery.I share my story not only as a cautionary tale but also as a testament to the resilience and possibility of recovery in the face of adversity. T E L E G R A M @  D A N I E L M E U L I   OR  E M A I L  hire us @ daniel meuli recovery wizard. online For anyone navigating similar challenges or contemplating crypto investments, remember to stay vigilant and seek assistance from trusted professionals if you find yourself in trouble. With perseverance and the right support, even the darkest of situations can be overcome.

Sylvester G. Bryant, a reputable expert in fund recovery, can be reached for assistance at<EMAIL_ADDRESS>or on Instagram under the handle Yt7crackersz. Clients who have fallen victim to scams can rely on his unwavering reliability and trustworthiness when it comes to the retrieval of their stolen funds. With a proven track record of successfully recovering scammed funds, Sylvester G. Bryant stands out as a competent professional in the realm of financial restitution. His dedication and expertise make him a top choice for those seeking swift and effective resolution to such unfortunate situations.

In recent times, technology has proven to be more sophisticated and just like any other currency that can be stolen or lost, crypto and other digital assets has proven to be more difficult to recover but not impossible, and just like searching for any other monetary currency, you need a trustworthy and honest agency or personnel who can track and recover the value lost or stolen, in my case I hired easyreclaimer@gmailcom,they followed the blockchain and was able to recover over 247k of my stolen funds within a couple of weeks. The fees for the services I received was fair and communication was excellent


502 Bad Gateway on recorder.js

Describe the bug
502 Bad Gateway on /recorder.js even though other paths work
To Reproduce
Steps to reproduce the behavior:

Deploy Smartlook relay via docker image: smartlook/relay-proxy:latest
Observe inconsistent respones:

502: https://smartlook-next.fons.app/recorder.js
200: https://smartlook-next.fons.app/manager/status

Expected behavior
A 200 response for all routes
Additional context
Smartlook support directed me here suggesting that my nginx config is somehow incorrect.  However, I am deploying the Smartlook Docker container with no changes so I don't expect that to be the issue.

I verified that the latest commit (https://github.com/smartlook/smartlook-relay-proxy/commit/bd2b6b0e56d3ca52ce0375dae0c90cbd724bfcc4) fixes this issue.  Can we get an updated version of the official container with the change?

Hi @troyschneringer,
thank you for opening this issue. I've released v6.1.0, which includes the fix.
I'm closing this now, feel free to reopen if you encounter any other issues.


Change the uuid for the testpmd pod

Description
Changed the uuid for the testpmd pod to be different from the uuid for the benchmark. We don't really need it there and it prevents the benchmark from ever finishing as the testpmd pod acts as a server pod and will never stop, unlike the client trex pod.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@befbd51). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #674   +/-   ##
=========================================
  Coverage          ?   53.48%
=========================================
  Files             ?        8
  Lines             ?      316
  Branches          ?        0
=========================================
  Hits              ?      169
  Misses            ?      147
  Partials          ?        0

Flag
Coverage Δ

gha
53.48% <0.00%> (?)

python-3.9
53.48% <0.00%> (?)

unit
53.48% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update befbd51...a707d4b. Read the comment docs.


Remove unneeded unwinds

Description of changes:
There are unreachable loops in the code snippet compiled from generator resume. For example, in the goto program compiled from the benchmark moved_locals.rs:
     8: ASSERT false // KANI_CHECK_ID_moved_locals.c1d95029::moved_locals_3
        // 716 file /Users/qinhh/Repos/kani/qinheping/tests/kani/Generator/rustc-generator-tests/moved-locals.rs line 71 column 5 function overlap_x_and_y::{closure#0}
        ASSERT 0 ≠ 0 // [KANI_CHECK_ID_moved_locals.c1d95029::moved_locals_3] generator resumed after completion
        // 717 file /Users/qinhh/Repos/kani/qinheping/tests/kani/Generator/rustc-generator-tests/moved-locals.rs line 71 column 5 function overlap_x_and_y::{closure#0}
        ASSUME 0 ≠ 0
        // 718 file /Users/qinhh/Repos/kani/qinheping/tests/kani/Generator/rustc-generator-tests/moved-locals.rs line 71 column 5 function overlap_x_and_y::{closure#0}
        GOTO 8

The jump-back instruction GOTO 8 is unreachable as it is after ASSUME 0 ≠ 0.
However, such unreachable loops can actually be correctly handle by CBMC. So we can remove the unwinding numbers from the benchmarks modified in this PR.
Resolved issues:
Resolves #ISSUE-NUMBER
Related RFC:

Optional #ISSUE-NUMBER.
Call-outs:

Testing:

How is this change tested?

Is this a refactor change?

Checklist

[ ] Each commit message has a non-empty body, explaining why the change was made
[ ] Methods or procedures are documented
[ ] Regression or unit tests are included, or existing tests cover the modified code
[ ] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

I'm curious why you decided to remove the unwind in these tests. Did you try other tests as well? I'm assuming we have a lot of unwind annotations that are not quite needed anymore.

I tried the synthesizer on all benchmarks with unwinding numbers and investigated what kind of loops are in the benchmarks. Some of those benchmarks are actually unbounded even though we specify unwinding number for them. So, to better track which benchmarks should be the target of the synthesizer, I decided to remove unwinding numbers from those unbounded benchmarks (assuming the input become unbounded).
Yes, there are more unbounded benchmarks in which we can remove the unwinding numbers. This PR now only covers loops caused by generators. Let me also add other kind of loops into this PR.


Add support for non square images

Steps to reproduce:
Mojo git:(bouncers-line) ✗ yo rn-toolbox:assets --icon src/images/mojo-cat.png
? Name of your react-native project Mojo
Please use a square image
➜  Mojo git:(bouncers-line) ✗

Hello, we just revamped the generator 😁
For up to date icon and splashscreen generation please use @bam.tech/react-native-make
The new version handles non-square images thanks to the switch to sharp for image processing. So it should solve your issue 😉


Rock vapour calculation

Currently, AGNI only supports volatile outgassing, but at higher temperatures we should expect significant amounts of rock vapour to be produced. Integrating these into the radiative transfer would be complex, but they could quite easily be incorporated into calculations of MMW and bulk density.
We can calculate vapour partial (surface) pressures at a given temperature and fO2 using codes such as Vaporock and Lavatmos. These codes are somewhat annoying to setup, since they depend on ThermoEngine, but I have been successful in doing this on my Mac laptop.
We would have to think carefully about how to include these gases alongside the currently supported volatiles.

Agree, we had similar issues in Björn Koops' BSc thesis earlier this year when trying out Vaporock. At the meeting on Wednesday, we should discuss whether pre-computed look-up tables may provide an entry.
Why do you think that integrating them into the radiative transfer would be complex? If we have the opacities for the major gases, SOCRATES should be able to compute k-tables?

Pre-computing this is a nice idea, particularly if we are assuming BSE composition since that would only leave 2 variables (Tsurf, fO2) for the table's axes.
I think it might be complex because SOCRATES doesn't currently support any refractory species. It uses hardcoded gas IDs defined in gas_list_pcf.f90, so we would need to manually add all of the required gases to this list. This is easy to do, but it would mean diverging from the Met Office SOCRATES distribution somewhat.

The currently supported refractory species are: TiO, VO, Na, K, FeH, CrH, Li, Rb, Cs

Mh, yeah, these are clearly not sufficient. But yes, perhaps assuming BSE and condensing the axes would make sense. I wonder if the axes should be (Tsurf, Psurf, fO2), but that's a thing to discuss on Wednesday with Yamila's group further.

Notes from meeting with Yamila's group:

Lavatmos can calculate rock vapour partial pressures - can probably use a look up table to do this easily.
Installing lavatmos might be a pain - depends on ThermoEngine.
We can probably integrate this into CALLIOPE directly.
Include Lavatmos in the main CALLIOPE solver loop where we calculate elemental mass inventories from partial pressure guesses. Only possible if we allow the fO2 to evolve at the same time
fO2 will need to be made into a dependent variable, which is good anyway
Need to think about which opacities to prioritise
Would be good to get Lavatmos integrated into a framework like PROTEUS


Weird value of standard deviation of the O&M costs for Solar PV

Hi,
I have encountered a weird value for the solar O&M costs.
In the FTT-P-24x71_2022_S0 and FTT-P-24x71_2023_S0, in the BCET sheet,
The value of the standard deviation of the Solar PV O&M cost is higher than the O&M costs themselves, which should imply frequent negative O&M costs for solar ?

Anyway, if you have any explanation or tips to fix that, I am all ears.
Cheers

That's probably due to determining the standard deviation on the basis of gobal data. Country-specific data is often too limited to determine regional SDs.
We should probably express SDs in percentages to the average anyway as I think that the width of the deviation moves with the average (e.g. if prices increase than it makes sense to increase the uncertainty).

I agree about expressing SD as a percentage. This can still be sector or even technology specific. If we make it technology-specific, we would compute the sample standard deviation by country, divide it by the mean of that country, and average these out. We can automate this in excel, so that we don't have to do this every update.


Copying text in Word and losing formatting

Love the app. If I'm working with two word documents open, and want to skim through one document and copy all the bits which I want to have on the clipboard for easy re-ordering, I lose the formatting of the text by switching between what to paste.
So if I copy two bits of text from the same word document, and both have words in bold or italicised, this will be lost if I switch between the two bits in the maccy menu. Is this intended?

It's not quite intended, but it's the way it is. There was a request to allow pasting without formatting so anything pasted from Maccy will lose formatting. I don't know how to support both with and without formatting at the same time as they are contradicting.

Could this feature be toggle-able? Just a friendly suggestion.
On Mon, Feb 3, 2020 at 6:08 PM Alex Rodionov<EMAIL_ADDRESS>wrote:

It's not quite intended, but it's the way it is. There was a request to
allow pasting without formatting so anything pasted from Maccy will lose
formatting. I don't know how to support both with and without formatting at
the same time as they are contradicting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/p0deje/Maccy/issues/75?email_source=notifications&email_token=ABU3FF4LMADFGTYSKVOVAILRBBMPRA5CNFSM4KPG3BTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKU2D4I#issuecomment-581542385,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABU3FF54L2UKUJZIXL52IHLRBBMPRANCNFSM4KPG3BTA
.

The way I did in the past is cmd shift V pastes without format

The way I did in the past is cmd shift V pastes without format

Can this be done in the current version?

The way I did in the past is cmd shift V pastes without format

Can this be done in the current version?

don't think this app ever supported.
but is something, MS Office, chrome, and even some web editors supported for many years

The way I did in the past is cmd shift V pastes without format

Can this be done in the current version?

don't think this app ever supported.
but is something, MS Office, chrome, and even some web editors supported for many years

Would be good to have this re-integrated into maccy then. Would like to paste with formatting preserved.

The way I did in the past is cmd shift V pastes without format
We cannot do this in Maccy, can we?

Hi.  I think that Maccy should keep/save the formatting.
Then, to paste without....you do the normal Maccy select action Shift+Cmd+C -> select what you want -> and then use the standard MacOS shortcut to past without formatting.

Option+Shift+Command+V to paste text without any formatting

While there are other alternatives this seems the most straightforward/easiest to implement.

Hm, then you cannot use keyboard shortcuts to select for example item number 5 on the list. Don't you think that makes the whole UX inconsistent?

I think I'm missing something from your question.
I'm using Maccy with the defaults so when I hit enter on an entry or cmd-5 then that text is copied to the clipboard(it doesn't paste).  Only then do I hit Ctr-V to paste.  If RICH text was copied to the clipboard.....then I'd have the option to use the MacOS shortcut Opt+Shift+CMD+V to paste with no formatting.
I get that my suggestion wouldn't work at all if you have Automatically Paste by Default turned on.   (actually, I might go and turn that option on now that I know about it 👍 ..... I went back and scanned through the documentation to answer your question.
Looking at your proposed Action/Behavior table.... both of the 1st two actions start with an "enter".  Should the second one be "shift+enter". ?  (for removes formatting and copies item )

Ok, I think what needs to change now is to have Maccy preserve formatting. I think it should work once the work on #84 is completed. After that, if we get requests to remove formatting we can get back to adding SHIFT behavior to remove it.

Implemented via 6a2b6aa

This is exact use cases I am looking for @simpalsimon. Thanks @p0deje for creating and open source such great software
Regarding UI/UX for this issue, can we learn from Pasta, another clipboard manager, which looks like this:

By having a floating windows that can be pin on the screen, we can simply see the copied text visually and click into each snippet to paste it. This was almost a clone of the UX of Office Clipboard which Microsoft does not support on MacOS but do on Windows.
In theory, I might just simply use Pasta. But Pasta are very buggy with MS Office, I frequently meet issue similar to #353 while using it, thus making it unusable. I tried to contact Pasta developer for help, but they seems can't fix the problem. Fortunately, I don't encounter those issue with Maccy.
How's your take on this @p0deje. Do you think adding this new UX for Maccy possible? If yes, are you willing to implement it ?
I also willing to make a fork and do the UI by myself, but I don't had any experience in Swift and in building MacOS application yet. I'm sure I can pick it up, but I will need a lot of help from you, starting with a feasibility assessment.

@lamhoangtung I don't think there is a way to preserver NSMenu (which is how the popup is implemented) to remain open when selecting item. If there is one, you can try implementing a simple "anchor" button to keep the menu open. The rest should probably just work. I'm however against introducing any new UI in addition to what we currently have (e.g. custom achored window with history list).


Ref loading will ignore ref feeds if previous streams did not contain a map

The following line was added to ReferenceData:180
            if (refDataStoreHolder.isLookupNeeded(pipelineReference, mapName)) {

to make it ignore ref feeds that are known not to contain the map being looked up against.  This is fine if the maps included in a feed never changed but they can do.  It needs to change to apply this logic further down and to cache the contained maps at the refStreamDefinition level.  This means we will always have to load a ref stream on first use to establish what maps it holds.
Also RefDataStoreHolder needs to change to use a caffeine cache to hold this information so that it can age off and be clearable.

This was fixed in #3136


feat(scan): support std::string_(view)

[ ] support complex case
[ ] add unit test to reader::empty
[ ] update docs

Codecov Report
Patch coverage: 95.00% and project coverage change: -0.05% :warning:

Comparison is base (3049abd) 99.19% compared to head (069ff9d) 99.15%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #45      +/-   ##
==========================================
- Coverage   99.19%   99.15%   -0.05%
==========================================
  Files          54       54
  Lines        5322     5416      +94
==========================================
+ Hits         5279     5370      +91
- Misses         43       46       +3

Files Changed
Coverage Δ

include/emio/reader.hpp
100.00% <ø> (ø)

include/emio/detail/scan/scanner.hpp
95.45% <87.17%> (-2.47%)
:arrow_down:

include/emio/detail/format/formatter.hpp
98.27% <100.00%> (ø)

include/emio/formatter.hpp
100.00% <100.00%> (ø)

include/emio/scanner.hpp
100.00% <100.00%> (ø)

test/unit_test/test_scan.cpp
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

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


Add information for contributers

Added basic files to help out contribuiters
Added checkstyle, pmd and findbugs to the project
Added the Google Java Style as the project Java style
After playing with some code styles I've choose Google's style. There are good documentation and tools.
The provided checkstyle is enforcing the Google Java Style but our source is far from meeting that.
I've updated app/src/main/java/chat/rocket/android/fragment/ChatRoomFragment.java to meet the new style (works as an example).
I'm not enforcing the rules just yet, since we have to change all of the code base.

@laggedHero Thank you for your pull request!
I agree with enforcing the Google Java Style for better quality of our codes.
Actually I'm now replacing full of the source codes of Rocket.Chat.Android in develop2 branch, and develop branch will be unused in future.
Could you provide the pull request based on develop2 branch with enforcing the Google JavaStyle?

@YusukeIwaki I'll pick up the extra files (the markdown files with extra information) and add to develop2.


Get android example to build on OS X

Cc @lberki.

Looks like this got merged, thanks @kchodorow!


Do we need to sign up for Miro and/or Mural?

Exploring the Welo space (which I seem to be able to fully explore without having to do any setup; just follow the link from the main page) I see there are some tools on the lower central toolbar: Google Drive, miro and Mural. With miro it appears that one can create a board without signing up. Will we need thought to create a miro account in order to work with others in the OSC? And the same with Mural; do we need to create an account?

You don't need to use the links on bottom - we can use those to share a Miro board for everyone. Instead, if you look at room called Information, you see it has a little folder image with resources attached to it - there is a link to the conference  Miro board. We build our agenda on it, and it is open for anyone. I tweaked Miro rights a bit so that you can join the as guests but it does not allocate you licenses. So no need to create accounts.

@maaretp thank you, I found it!


Fix urls

@ldko @somexpert
Replaced slug with str in url for views.detail. I have checked all django upgrades and found that here I have used <slug> when I am supposed to use <str>

As @ldko mentioned, since all name_ids are only letters and digits meaning regexes [^/]+ or .*,  using either slug or str would be same in effect. So I'm closing this PR.


Clarification on 5/13 Rollback AMI version

Can someone please confirm what is the latest AMI version to use?
getting these results for us-east-1, us-east-2 and us-west2.  Just want to make sure which ami date to specify.
aws ssm get-parameter --name /aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id
{
"Parameter": {
"Name": "/aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id",
"Type": "String",
"Value": "ami-0fb604efcd6aaf3d5",
"Version": 29,
"LastModifiedDate": "2022-05-19T14:31:36.154000-05:00",
"ARN": "arn:aws:ssm:us-east-1::parameter/aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id",
"DataType": "text"
}
}
aws ssm get-parameter --name /aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id
{
"Parameter": {
"Name": "/aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id",
"Type": "String",
"Value": "ami-09dd25549dd970de5",
"Version": 29,
"LastModifiedDate": "2022-05-19T14:26:19.487000-05:00",
"ARN": "arn:aws:ssm:us-east-2::parameter/aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id",
"DataType": "text"
}
}
aws ssm get-parameter --name /aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id
{
"Parameter": {
"Name": "/aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id",
"Type": "String",
"Value": "ami-07b7ea65cbbc3dc71",
"Version": 29,
"LastModifiedDate": "2022-05-19T14:26:31.343000-05:00",
"ARN": "arn:aws:ssm:us-west-2::parameter/aws/service/eks/optimized-ami/1.21/amazon-linux-2/recommended/image_id",
"DataType": "text"
}
}

The v20220513 release inadvertently changed the format of the release_version found in our SSM parameters. This was the result of changes in our release process. The v20220513 AMI is available in all regions and is safe to use. However, it will not be the default AMI used when creating nodegroups, and (as you noted) the values of our SSM parameters have been rolled back as part of our recovery process. To maximize backward compatibility, the v20220429 release remains our recommended AMI.
We have corrected the issue in our release process, and will release an AMI that supersedes v20220513 in the next few days.

I'm going to leave this issue open for the time being, in case there are any other questions we can answer. Sorry about the confusion!

The recalled release has been superseded by v20220523, which contains all the fixes slated for the recalled release.


More granular traces on gitbase SquashedTable

Related to https://github.com/src-d/go-mysql-server/issues/466
SquashedTable should provide more insights in each chainable iterator.

I've been playing for a while with this and I don't think it's feasible to trace squashed table. New iterators used in squashed table are created per repo and they're iterated in a chained way, so there's no real way to add tracing without flooding the traces with a bajillion spans.


Provide a way to enable source level statistics for tables registered in the CLI

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
#1347 enabled collection of statistics by default on the ListingOptions constructor, though the tables created with CREATE EXTERNAL TABLE can't still use this feature since they are created manually.
https://github.com/apache/arrow-datafusion/blob/e54110fb592e03704da5f6ebd832b8fe1c51123b/datafusion/core/src/execution/context.rs#L486-L488
Describe the solution you'd like
We already have a per file extension listing option implementation for the read_ dataframe APIs (e.g. CsvReadOptions, ParquetReadOptions) and they have sane defaults (like collect_stats is false for CSV and true for Parquet). I wonder whether we can just use them here and obtain the ListingOptions directly from them.
Describe alternatives you've considered
Leaving as is, or enabling them globally (instead of refactoring that part to use ReadOptions) by just setting the flag to true.

I wonder if it ever can be enabled by default for parquet datasets.
The downside for parquet is that when using remote object storage, collecting of statistics takes quite a bit of IO, slowing down simple queries.
I guess at some point we have to switch testing with Delta Lake or Apache Iceberg I guess :)


OTT Player error 504 invalid key on Euronews PT stream

I'm getting this 504 error whenever I try to use the Portuguese Euronews, it's not that relevant for me, but my family sometimes likes to watch it. Is this fixable or just a temporary thing? I followed the docs and restored the backup.

Thanks for the heads up mate.


Fix intermittent assert_{patched,redirected} failures

Uses the assert_{patch,redirect} (with ed) variants to benefit from the default timeout of 100. I guess there's no getting around timeouts/sleep 🤠

Pull Request Test Coverage Report for Build 4663d4be398b757122864cb3e6e299bcc6184ba0-PR-1125

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.427%

Totals

Change from base Build 11695393f7ed7cb37f81a6d14cfcce05eba27c77:
0.0%

Covered Lines:
1199

Relevant Lines:
1805

💛  - Coveralls


Feature request: add a dry run mode

Does it make sense to add a dry run mode to the oc command?
It goes like:
input:
oc --dry-run

output:
commit message:
feat(someFeature): some message

git command:

git commit -m "feat(someFeature): some message"

it's possible in the new version, you can pass any arguments to oc <...arguments> that you can pass to git commit <...arguments>


capabilities: revert change from boolean to string

It was committed accidentially. And actually this is a bug in phoenix. oc10 renders booleans in ocs json responses properly, not as strings.

LGTM. Needs to be followed up with a proper fix for this, that is the OCS api JSON and XML encoding diferr.
https://cloud.owncloud.com/ocs/v1.php/cloud/capabilities?format=json
...
"user": {
"send_mail": true
},
"resharing": true,
"group_sharing": true,
"auto_accept_share": true,
"share_with_group_members_only": true,
"share_with_membership_groups_only": true,
"can_share": true,
...

https://cloud.owncloud.com/ocs/v1.php/cloud/capabilities?format=xml
...
<user>
<send_mail>1</send_mail>
</user>
<resharing>1</resharing>
<group_sharing>1</group_sharing>
<auto_accept_share>1</auto_accept_share>
<share_with_group_members_only>1</share_with_group_members_only>
<share_with_membership_groups_only>1</share_with_membership_groups_only>
<can_share>1</can_share>
...


Fix "incompatible" types

Currently, the following test fails to compile with a error: incompatible types: 'i32' and 'f32'
    zigthesis.falsify(struct {
        pub fn pred(args: struct { i32, f32 }) bool {
            const x = args[0];
            const y = args[1];

            return x + y == y + x;
        }
    }.pred, "Int and Float Test");

This is not ideal, and the code needs to be restructured to accommodate different but compatible types.

@ellipsis-dev


[Question]: Keep getting "Error: Npm failed with return code: 217" while installing Angular CLI when building using our self hosted build agent. The only solution I've found is to remote in and delete the _work directory for the agent. Any suggestions?

Describe your question

We have two separate agents on the same server. Sometimes this happens to only one of the agents, sometimes it's both. Regardless, the only solution is to delete the _work directory for the agent having issues.
I've tried enabling the "Clean Build Directories" option in the build pipeline and it doesn't seem to make a difference because the issue is with the _work/_tool directory at the agent level.
Should I add a build task that runs 'rm -rf _work'? Thats what I've been having to do every time this happens. Is there any built in automated way of doing this?
Or I more than anything... any suggestions as to why this is failing in the first place? It succeeds for a few weeks then this will happen and I have to manually delete the work folder.
Versions
2.213.2
Ubuntu
Environment type (Please select at least one enviroment where you face this issue)

[x] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Operation system
Ubuntu
Version controll system
Git
Azure DevOps Server Version (if applicable)
No response

Hi @edgariscoding ,
Thank you for reporting this issue, most likely it happened because that npmjs is not concurrency-safe (or the previous attempt was unsuccessful)
This issue appears from time to time in npm cli repo, and not seem to be resolved, have you tried to add the extra step "npm cache clean --force" before npm install, or tried to invoke npm install --force?

I will try adding nom cache clean --force thank you


Add dates

Hi @jupblb! Thanks for this tool!
Is it planned to add dates sync in any format?

My pleasure! :D I'm sorry that you had to wait 3 weeks for a response, my daughter was born a day after this issue was created.
I did not consider supporting dates (or links for that matter) because I don't have a good idea how to compose it with the Markdown document structure. There are three different dates associated with each Task according to the documentation: updated, due and completed. So it's not right to have just one of these written next to a Task title. Therefore, we would need to somehow embed it in Task's note but this feels a bit messy as it requires creating a less obvious convention. The best thing that comes to my mind is having some metadata table.
I'm not convinced at this moment that this is a feature worth supporting but would like to leave this issue open. If there is a good idea on how this should work I'm open to having it implemented.

@jupblb Congratulations for your daughter birth bouquetrelaxed

Thanks :)

Maybe you can add support just for due date since it's the only one visible in Tasks app and the most important one from my point of view?
Maybe this format on the next line after the title:
date:: 230319

This seems a bit too arbitrary for me. Let's say tomorrow I get a request to add support for completed date because someone wants to see when exactly a certain task was done (so that they don't repeat themselfes on standup or something). Whatever a solution to such a problem would be, it needs to be different than having the value simply next to a title, after the due date. This is a reason why I believe we must have a more generic approach towards presenting dates that may also include even more metadata fields.


added threshold option to multichainBalance

For multichain, users can add a quorumThreshold to modify the quorum of the total balance returned from the contract calls e.g. total * 0.05

Looks good. I'm just not sure about the term quorumThreshold. Something like quorumModifier feels better to me.

@mktcode updated to quorumModifier

Will merge once you approve @mktcode


Hide Fork button if disabled

Private repos could have forks disabled (which is quite useful as forks of private repos are or used to be public by default). If there are no forks and creating new forks is disabled for the repo, the Fork button serves no purpose. We can hide it.
Here's a screenshot and DOM tree of a disabled fork button with 0 forks:

    <svg class="octicon octicon-repo-forked v-align-text-bottom" viewBox="0 0 10 16" version="1.1" width="10" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M8 1a1.993 1.993 0 0 0-1 3.72V6L5 8 3 6V4.72A1.993 1.993 0 0 0 2 1a1.993 1.993 0 0 0-1 3.72V6.5l3 3v1.78A1.993 1.993 0 0 0 5 15a1.993 1.993 0 0 0 1-3.72V9.5l3-3V4.72A1.993 1.993 0 0 0 8 1zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zm3 10c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zm3-10c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"></path></svg>
    Fork

    0

This would also leave more space for other extensions adding this there like Sourcegraph or even some things from Refined GitHub which are on the line of the repository name.

Related UX arguments: https://ux.stackexchange.com/questions/120848/should-i-have-a-disabled-button-or-no-button-at-all-if-the-user-doesnt-have-su/120853
It may look like noise, but if I didn't see some of the disabled buttons GitHub shows (e.g. the Edit button in commit files) I wouldn't know why that's disabled and I'd scratch my head.


Javascript error on all WebVR.info/samples on desktop

When using Chrome 52 or Firefox 46 with the webvr.info/samples on a machine without a VR device attached, the following errors are produced in console:
Chrome:
webvr-polyfill.js:5421 Uncaught (in promise) TypeError: Cannot read property 'fieldOfView' of null(…)
Firefox:
TypeError: parameters is null webvr-polyfill.js:5421:5
(Windows 10, on desktop and laptop)  Samples work fine on Chrome and Firefox Mobile browsers

Yep, I'm seeing it too. /cc @toji

Fixed in latest update to #149


Possibility to deploy tensorflow-java to AppEngine

I was trying to run ML Inference with tensorflow-java deployed to AppEngine, but quickly failed with this error:
ERROR: (gcloud.app.deploy) Cannot upload file
 [/root/repo/target/appengine-staging/WEB-INF/lib/tensorflow-core-api-0.3.3-linux-x86_64.jar],
 which has size [62305961] (greater than maximum allowed size of [33554432]).

Which means that AppEngine forbids to deploy any single file that's bigger than 32Mb. And the jar for linux-x86_64 is ~62Mb right now. It is confirmed there: https://cloud.google.com/appengine/quotas#Code
Just checking if someone has any advice/workaround in mind?
Like, is it possible to maybe do a custom-build (I only need to run Inference of SavedModelBundle, nothing else) of tensorflow-java for Linux, to fit in under 32Mb? Or, split the jar into multiple sub-32Mb files?
Not looking for AppEngine advice (as this repo is not a right place for it), but for something that can be done with this library itself. 🙏

Try making a fat jar and running it through proguard (for the shrinker).  I don't know what rules you would need, it's probably going to be trial and error.  If/once you get a working set we should document it here, and there might be a way to distribute them in the jars.

If your models can be exported to TF Lite, you might want to consider using that: https://github.com/bytedeco/javacpp-presets/tree/master/tensorflow-lite That's less than 3 MB per platform.

Oh that's a cool idea! I'll explore that! 👍

Our uncompressed TensorFlow library alone is 375M, which is slightly bigger than the one used for Python (312M), I think the difference is because we also export the C++ client API is ours. Still, I have no clue how we can distribute a library that big in a smaller jar...

I only need to run Inference of SavedModelBundle, nothing else

Even if you only do inference, you need all the TensorFlow ops and kernels to be present in your library in case your graph is using one of them. I haven't checked but I suspect that most of the bytes of this library are taken by the ops (over 1K).

Another option to consider is XLA AOT.  I'm not entirely sure how you would use that from Java but you should be able to export the function and work from there.


Get the count data and RNA velocity after batch correction

Hi,
After running latent_adata = ltv.output_results(model, adata), I could only get an adata of 20 dimensions, which equals to the latent_dim that I set in initializing the model. I'm wondering if there's any method to reconstruct the count data and RNA velocity after batch correction.
Thank you very much!

Problem solved.


WorkContext null

I'm using the multitenancy module and am trying to see if it is possible to have shape alternates defined by tenant so that a customization doesn't have to affect all tenants.
My thought was to implement my own IShapeTemplateHarvester in order to add an additional path such as "Views/TenantName".
My problem is that WorkContext is null at the time the ShapeTemplateHarvester is run.
Is there another way I could get the tenant name for the current request?
        public IEnumerable<string> SubPaths()
        {
            var workContext = _workContextAccessor.GetContext();
            //var workContext = Services.WorkContext;
            List<string> paths = new List<string>() { "Views", "Views/Items", "Views/Parts", "Views/Fields", "Views/Elements" };
            if(workContext != null)
            {
                var settings = workContext.Resolve<Orchard.Environment.Configuration.ShellSettings>();
                var tenant = settings.Name;
                paths.Add("Views/" + tenant);
            }
            return paths;
        }

This code is not run by a specific tenant. What you can do instead if defined alternates with the tenant name. Look at the Widget Url Atlernates feature which does something similar.


Move downloads to S3

CSV, JSON, HTML, etc.

[x] Modify the downloads-generating cron job to copy files to S3 at the completion of the script.
[x] Create a downloads page.

Looks like it's this easy:
aws s3 sync . s3://downloads.richmondsunlight.com --grants read=uri=http://acs.amazonaws.com/groups/global/AllUsers --storage-class REDUCED_REDUNDANCY

That can't go in the script, for reasons of authentication, so I created a separate cron job for it.

Done.


Leaky ReLU as part of tf.nn

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Ν/Α
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.3.0
Python version: 2.7
Bazel version (if compiling from source): bazel release 0.5.4
CUDA/cuDNN version: 8.0
GPU model and memory: GeForce 940MX, 4Gb
Exact command to reproduce: N/A

Describe the problem
A leaky relu function could be part of the standard tensorflow package, under tf.nn. or some other non-contrib module. It could be something like
tf.maximum(x, alpha * x)

Custom leaky relus, which is what people do now, may be largely non-efficient. See for example the discussion in https://stackoverflow.com/q/45307072/5615276 .

Efficiency issue could potentially be fixed by enabling XLA to fuse this pattern into a single op. That's better for maintainability than adding yet another native op (743 in the latest count)
/cc @hawkinsp in case he knows if that's close to being reality

I think it's worth adding a leaky_relu to tf.contrib.nn for now. Using tf.maximum is fine.

I think this was added after r1.3, it's the max(alpha * features, features) variant.
https://www.tensorflow.org/versions/master/api_docs/python/tf/nn/leaky_relu
https://github.com/tensorflow/tensorflow/commit/7a8c63da365106048dc96affddb39e2fdc33da89#diff-7e066e8d1b9eff5c683b33517b35ae13

@rryan Indeed, it is a very recent commit. Thanks!


Assayapps inline file link creation is limited

My custom assay plugin creates file links for selected text columns, based on code of the meta_ms assay plugin. Due to https://github.com/bihealth/sodar-server/commit/d82da0da78343eec378b2d76ef66d02173132f39 and specifically https://github.com/bihealth/sodar-server/blob/f3e37287b058c4fd6c9db50c46de43de35e3b2d0/samplesheets/rendering.py#L81-L82 this approach only works for columns named "Report file".
This special case treatment is not mentioned in the documentation, not expected, and fails silently.
How to Reproduce
Use code like this in assay plugins to create inline file links:
if (
    header['obj_cls'] == 'Process'
    and (
        header['value'].lower() == 'antibody panel'
        or header['value'].lower() == 'barcode key'
        or header['value'].lower() == 'report file'
        )
    and row[i]['value']
):
    row[i]['link'] = (
        base_url + '/' + MISC_FILES_COLL + '/' + row[i]['value']
    )

Links are only created in Report file columns.
Expected Behavior
Links are created in all matched text columns.

This is not a bug and doesn't quite work as you say.
The SPECIAL_FILE_LINK_HEADERS list contains special cases (well, currently one special case) which are not counted as data file headers, as they are not specified as such in AltamISA / ISA model. We are not causing anything to "only" work with a certain column header, we are extending the functionality to an additional type via an ugly hack. IIRC it was done urgently for some demo.
As long as the column type is in DATA_FILE_HEADERS, no hack is needed.
Also see:
elif (
    name.lower() == 'name' and header['item_type'] == 'DATA'
) or name.lower() in SPECIAL_FILE_LINK_HEADERS:  # HACK for issue #817
    header['col_type'] = 'LINK_FILE'

Ok, I had a hard time understanding why my draft plugin did not work as expected and this is what I understood. Thanks for the clarification.
Let's definitely discuss this, as the files I want to link are technically not data files, but part of the metadata.

Resolved in d1afebfb738544edc0a908fbd36c70506df8252f.


Too many tests broken or deactivated on Windows

@miroi  I am considering dropping automated testing on Appveyor because many of the corresponding tests are broken or deactivated. Nobody seems to have time or means to work on it. I don't see the value of such tests. What do you think?

As long as autocmake is beeing used with MS Windows, let us keep the tests.
Currently https://ci.appveyor.com/project/bast/autocmake tests are not even starting due to missing git...

But what is the value of keeping them?

The value of (Windows working) tests is that they serve as working examples, which can be adapted for users purposes.

Then they should not be tests but move to the documentation, right?

And I don't think they serve as working examples because they are not working.

Just to be clear I am not suggesting that we should stop supporting Windows. Python is cross-platform and CMake is cross-platform so Autocmake is cross-platform. I am just suggesting that we should stop the testing since it does not serve us anything. Many tests are deactivated and many active tests are broken. I don't see any value in that. I really appreciate your work on Windows integration and we should not stop this. I just think that we should test only on Linux and Mac for the moment. This is because I have no way to develop and test on Windows myself and you are busy too. We should focus our efforts. We should continue supporting Windows via issues. If there are problems, then we will know via issues.

Miro, I think I will get rid of the automated Windows tests but if you like you can maintain a fork which focuses on Windows tests. However, I want to keep supporting Windows via issues. I believe with this we will be able to move faster while keeping portability.

Go ahead - I created own branch for supporting Windows, https://github.com/miroi/autocmake/tree/windows_supp .


Invalid frame header?

chrome report WebSocket connection to 'ws://<IP_ADDRESS>:8080/' failed: Invalid frame header?
please help me.

@hoangweb  please look http://wenda.workerman.net/?/question/1335

@hoangweb  can you show full code ?

Closing this due to a lack of feedback.
Please come back with more details if this problem persists and we can reopen this.


Csrftoken

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

It's not obvious how this error gets triggered. Does it need to be plugged into the form validation?

It's not obvious how this error gets triggered. Does it need to be plugged into the form validation?

It's not obvious how this error gets triggered. Does it need to be plugged into the form validation?

csurf handles the validation for each request, and we handle the error in the csrftoken class
app.use((error, req, res, next) => {       if (error.code === 'EBADCSRFTOKEN') {         logger.error(${error.stack || error});         return res.redirect(CSRF_TOKEN_ERROR_URL);       }       next();     });

It's not obvious how this error gets triggered. Does it need to be plugged into the form validation?

csurf handles the validation for each request, and we handle the error in the csrftoken class
app.use((error, req, res, next) => {       if (error.code === 'EBADCSRFTOKEN') {         logger.error(${error.stack || error});         return res.redirect(CSRF_TOKEN_ERROR_URL);       }       next();     });