Not starting after latest update

Seeing this error:
/usr/local/bin/code-server: line 1: syntax error near unexpected token `newline'
/usr/local/bin/code-server: line 1: `<!DOCTYPE html>'
GNOME_KEYRING_CONTROL=/root/.cache/keyring-OM6X81
SSH_AUTH_SOCK=/root/.cache/keyring-OM6X81/ssh
No init file configured, skipping...

see here: https://github.com/ahmadnassri/docker-vscode-server/issues/27
the latest version v1.4.1 was an automated release that only included some build tooling, you can revert back until the above issue is resolved.


Add validator profitability metrics

[X] epoch credits
[ ] commission
[X] APR or some other rate of return of investment

Validator commission can be taken from vote accounts.


"Can't verify CSRF token authenticity"

I recently tried to log in on sandbox and hit a "422 Unprocessable Entity" error. Here is the backtrace from papertrail. Unfortunately the error does not appear to have been propagated to Sentry. I was eventually able to log in, so at worst it's intermittent. Until we can confirm that this won't be a problem on production, I don't think we should do any deploys.
heroku/router sock=client at=warning code=H27 desc="Client Request Interrupted" method=POST path="/users/sign_in?locale=es" host=sandbox.dariaservices.com request_id=b1d4d799-19a5-4f93-b1c4-317487ab7779 fwd="<IP_ADDRESS>,<IP_ADDRESS>" dyno=web.1 connect=0ms service=292ms status=499 bytes= protocol=https
app/web.1 I, [2023-05-10T21:37:08.883081 #11]  INFO -- : [b1d4d799-19a5-4f93-b1c4-317487ab7779] Redirected to https://sandbox.dariaservices.com/
app/web.1 I, [2023-05-10T21:37:08.883194 #11]  INFO -- : [b1d4d799-19a5-4f93-b1c4-317487ab7779] Completed 302 Found in 271ms (ActiveRecord: 17.1ms | Allocations: 16981)
app/web.1 I, [2023-05-10T21:37:25.404953 #8]  INFO -- : [390fc535-bb9b-456c-9eea-bb429b612b02] Started POST "/users/sign_in" for <IP_ADDRESS> at 2023-05-10 21:37:25 +0000
app/web.1 I, [2023-05-10T21:37:25.411357 #8]  INFO -- : [390fc535-bb9b-456c-9eea-bb429b612b02] Processing by Users::SessionsController#create as HTML
app/web.1 I, [2023-05-10T21:37:25.411408 #8]  INFO -- : [390fc535-bb9b-456c-9eea-bb429b612b02]   Parameters: {"authenticity_token"=>"[FILTERED]", "user"=>{"email"=>"[FILTERED]", "password"=>"[FILTERED]"}, "commit"=>"Sign in with password"}
app/web.1 W, [2023-05-10T21:37:25.478974 #8]  WARN -- : [390fc535-bb9b-456c-9eea-bb429b612b02] Can't verify CSRF token authenticity.
app/web.1 I, [2023-05-10T21:37:25.479456 #8]  INFO -- : [390fc535-bb9b-456c-9eea-bb429b612b02] Completed 422 Unprocessable Entity in 68ms (ActiveRecord: 25.6ms | Allocations: 10882)
app/web.1 F, [2023-05-10T21:37:25.481043 #8] FATAL -- : [390fc535-bb9b-456c-9eea-bb429b612b02]
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] ActionController::InvalidAuthenticityToken (Can't verify CSRF token authenticity.):
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02]
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal/request_forgery_protection.rb:251:in `handle_unverified_request'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal/request_forgery_protection.rb:284:in `handle_unverified_request'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] devise (4.9.2) lib/devise/controllers/helpers.rb:255:in `handle_unverified_request'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal/request_forgery_protection.rb:273:in `verify_authenticity_token'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:400:in `block in make_lambda'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:199:in `block (2 levels) in halting'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/abstract_controller/callbacks.rb:34:in `block (2 levels) in <module:Callbacks>'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:200:in `block in halting'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:595:in `block in invoke_before'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:595:in `each'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:595:in `invoke_before'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:116:in `block in run_callbacks'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-rails (5.9.0) lib/sentry/rails/controller_transaction.rb:28:in `block in sentry_around_action'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry/hub.rb:102:in `with_child_span'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry-ruby.rb:456:in `with_child_span'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-rails (5.9.0) lib/sentry/rails/controller_transaction.rb:14:in `sentry_around_action'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:127:in `block in run_callbacks'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:138:in `run_callbacks'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/abstract_controller/callbacks.rb:233:in `process_action'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal/rescue.rb:22:in `process_action'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal/instrumentation.rb:67:in `block in process_action'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/notifications.rb:206:in `block in instrument'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/notifications.rb:206:in `instrument'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal/instrumentation.rb:66:in `process_action'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal/params_wrapper.rb:259:in `process_action'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activerecord (<IP_ADDRESS>) lib/active_record/railties/controller_runtime.rb:27:in `process_action'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/abstract_controller/base.rb:151:in `process'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionview (<IP_ADDRESS>) lib/action_view/rendering.rb:39:in `process'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal.rb:188:in `dispatch'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_controller/metal.rb:251:in `dispatch'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:32:in `serve'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/mapper.rb:18:in `block in <class:Constraints>'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/mapper.rb:48:in `serve'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:50:in `block in serve'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:32:in `each'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:32:in `serve'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:852:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack-attack (6.6.1) lib/rack/attack.rb:103:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack-attack (6.6.1) lib/rack/attack.rb:127:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] warden (1.2.9) lib/warden/manager.rb:36:in `block in call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] warden (1.2.9) lib/warden/manager.rb:34:in `catch'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] warden (1.2.9) lib/warden/manager.rb:34:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/tempfile_reaper.rb:15:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/etag.rb:27:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/conditional_get.rb:40:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/head.rb:12:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/http/permissions_policy.rb:38:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/http/content_security_policy.rb:36:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/session/abstract/id.rb:266:in `context'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/session/abstract/id.rb:260:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/cookies.rb:704:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:99:in `run_callbacks'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/callbacks.rb:26:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-rails (5.9.0) lib/sentry/rails/rescued_exception_interceptor.rb:12:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/debug_exceptions.rb:28:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry/rack/capture_exceptions.rb:28:in `block (2 levels) in call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry/hub.rb:223:in `with_session_tracking'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry-ruby.rb:385:in `with_session_tracking'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry/rack/capture_exceptions.rb:19:in `block in call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry/hub.rb:59:in `with_scope'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry-ruby.rb:365:in `with_scope'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] sentry-ruby (5.9.0) lib/sentry/rack/capture_exceptions.rb:18:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/show_exceptions.rb:26:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:40:in `call_app'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:25:in `block in call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:99:in `block in tagged'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:37:in `tagged'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:99:in `tagged'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:25:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/remote_ip.rb:93:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] request_store (1.5.1) lib/request_store/middleware.rb:19:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/request_id.rb:26:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/method_override.rb:24:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/runtime.rb:22:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/executor.rb:14:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/static.rb:23:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] rack (<IP_ADDRESS>) lib/rack/sendfile.rb:110:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/ssl.rb:77:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/host_authorization.rb:137:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] railties (<IP_ADDRESS>) lib/rails/engine.rb:530:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] puma (6.2.2) lib/puma/configuration.rb:270:in `call'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] puma (6.2.2) lib/puma/request.rb:98:in `block in handle_request'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] puma (6.2.2) lib/puma/thread_pool.rb:340:in `with_force_shutdown'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] puma (6.2.2) lib/puma/request.rb:97:in `handle_request'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] puma (6.2.2) lib/puma/server.rb:431:in `process_client'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] puma (6.2.2) lib/puma/server.rb:233:in `block in run'
app/web.1 [390fc535-bb9b-456c-9eea-bb429b612b02] puma (6.2.2) lib/puma/thread_pool.rb:147:in `block in spawn_thread'
app/web.1 I, [2023-05-10T21:37:25.482318 #8]  INFO -- : [390fc535-bb9b-456c-9eea-bb429b612b02] Processing by ErrorsController#error_422 as HTML

I loaded this up to take a look and was able to log in with both password and oauth successfully on sandbox. I'll try to recreate this but I can think of a few reasons this would have plausibly happened:

server timing out of sync with reality, causing it to expire
a server restart meant the CSRF provided was no longer recognized
ghosts / other

I think by and large I'm not scared of this (I'd be most inclined to attribute it to the not-ghosts bullets), so I'll plan on doing a deploy tomorrow and seeing if it breaks something or other, and make sure I'm available to rollback if necessary.
PS: Most likely this didn't show up in sentry because it was a 422 and not a 5XX - maybe surprising but expected. If we want to log that we'd probably have to subclass a devise controller, although maybe devise has an '5xx on login failure' setting we can toggle or something.

Unable to repro


array syntax highlighting

First of all, thanks very much for this project; it makes working in Stan much more pleasant.
One thing: brackets array syntax is deprecated in favor of prefacing with the array keyword. As such, it'd be great if, e.g., array[x, y, z] real response; would highlight the array keyword like GitHub does below:
array[x, y, z] real response;

Thanks!

Thank you!


[AUTOPATCHER-CORE] Patched kata-containers to address CVE-2023-22466 -

[AUTOPATCHER-CORE] Patched kata-containers to address CVE-2023-22466
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293596&view=results
AMD64 build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293676&view=results
ARM64 build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293677&view=results

Disputed: this CVE is against "tokio" which is used for Windows servers
https://microsoft.visualstudio.com/OS/_workitems/edit/42938366
Same applies to
https://github.com/microsoft/CBL-Mariner/pull/4634
https://github.com/microsoft/CBL-Mariner/pull/4635
https://github.com/microsoft/CBL-Mariner/pull/4636


Continuous reconcile extension

How to categorize this PR?

/area deployers
/kind enhancement
/priority 3
What this PR does / why we need it:
It adds a continuous reconcile extension to the deployer library which can be used by deployers to implement continuous reconciliation. This is demonstrated as an example in the mock deployer.
Which issue(s) this PR fixes:
Part of #239
Release note:

A deployer library extension which enables continuous reconciliation of deploy items has been implemented. See [here](docs/development/deployer-extensions.md#continuous-reconcile-extension) for the documentation.

/test


[feature request] newer electron

Looks like this needs electron 7 today
https://github.com/mattermost/desktop/blob/83bae0c2b8e3b479988cd3c9507bb47eab0c3422/package.json#L57
Version 11 is the stable release of electron now. I wonder if you folks could bump up the electron version that mattermost builds on.
Thanks!

it is planned to upgrade in a future release. newer versions have some breaking changes that need to be worked on.
Closing the issue for now, but feel free to reopen if you feel it wasn't addressed


combining samples before Circle-Map analysis

Hello,
I am following the Realign tutorial and am hoping to combine 3 samples in my analysis. My question is: at which step should I merge the .sam/.bam files? Right before I use the Circle-Map ReadExtractor command??
Thank you

Hi,
Could you elaborate a bit more on what are the "3 samples"?
Are they technical replicates?
best,
Inigo

Hi Inigo,
They are technical replicates, yes. Sorry for the vagueness.
Thank you

No worries :)
I think that the safest way would be to concatenate the raw aligned BAM files using somenthing like samtools merge
best,
Inigo

Okay, thank you!

You are very welcome.
Happy circle hunting :)


ImportError: cannot import name 'train_test_data_setup'

When I tried to import the train test data setup it through the error, before i have installed all the requirements but I don't know why am I getting thi error

Hello!
Can you provide the example of your script?

When I tried to import the train test data setup it through the error, before i have installed all the requirements but I don't know why am I getting thi error

try 'from fedot.core.data.data_split import train_test_data_setup' , it should resolve your error.

I think this issue is outdated and can be closed.


Upgrade sigstore/cosign dependency to v1.3.1

this should help unblock https://github.com/tektoncd/chains/pull/284 :)

I am more learning from this PR than  anything else, but I the new functions provide a nice abstraction level compare to the previous and the package reorganization (ociremote, mutate) makes complete sense.


UTF-8 character "filtering"

This line tries to filter out bad parameter values.

If you download this repository on Windows, the file will be mangled and show � instead of Õ. As far as I know Android itself doesn't support converting this from unicode notation either.
I think the filtering itself is limited. If you want to retain the user data, consider base64-url-safe encoding. I might want to keep new lines, right?
Is there a reason that only this character (apart from the newlines and carriage returns) is filtered?

("same" as #23)

I removed this filter in the latest build and added a backlog task to migrate over base64 encoding. Thanks for the suggestion!

Super!
On Thu, Apr 23, 2015, 20:33 Alex Austin<EMAIL_ADDRESS>wrote:

Closed #29 https://github.com/BranchMetrics/Branch-Android-SDK/issues/29
.
—
Reply to this email directly or view it on GitHub
https://github.com/BranchMetrics/Branch-Android-SDK/issues/29#event-288595613
.


elstonayx/Personal Project Portfolio

Modified the UGDG and PPP to include my contributions

@elstonayx  can merge? or still ongoing?

still ongoing, will let you know when its ready. @linnnruoo

Also resolves #91


Ensure honorLabels is set to true for prometheus-operator ServiceMonitor

This helps to resolve an issue identified in #1319 and relates to #1721

Fixing jsonnet tests now.

@nabadger thanks for the PR! All of these manifests are auto-generated via jsonnet. You would need to:

add your changes to to the prometheus-operator.libsonnet file
commit your changes git add jsonnet/prometheus-operator/prometheus-operator.libsonnet && git commit --amend --no-edit
run the generation step make generate-in-docker
commit the generated changes

Let me know if you have any questions along the way!

Our CI is failing with the following diff
diff --git a/contrib/kube-prometheus/manifests/0prometheus-operator-serviceMonitor.yaml b/contrib/kube-prometheus/manifests/0prometheus-operator-serviceMonitor.yaml
index bd325ff..10e0059 100644
--- a/contrib/kube-prometheus/manifests/0prometheus-operator-serviceMonitor.yaml
+++ b/contrib/kube-prometheus/manifests/0prometheus-operator-serviceMonitor.yaml
@@ -8,7 +8,6 @@ metadata:
 spec:
   endpoints:
   - port: http
-    honorLabels: true
   selector:
     matchLabels:
       k8s-app: prometheus-operator

The contrib/kube-prometheus/manifests/0prometheus-operator-serviceMonitor.yaml file is also auto-generated, based on the Prometheus Operator jsonnet files in jsonnet/prometheus-operator. But instead of using the current version in your repo, it is pinned to v0.22.2 (See jsonnet lockfile).
@brancz how would you like to proceed here?

make format generate-in-docker seems to work locally for me today - I think you guys fixed a dependency issues with jsonnet-bundler right?

Yes, sorry. There were both issues with jsonnet-bundler and a dependency of kube-prometheus. Both are fixed now.


Update the componentmeta api to support component version interaction

What's it about?

There is currently no association between K8S and its components, and there is no way to limit component versions.
What's the reason why we need it?

I believe this is an important feature for KubeClipper. There're a few use cases:

External version control, convenient component version update iteration.

Please leave your comments below if there's anyone agrees with me. Or just give me a thumb up.
Area Suggestion

/kind feature-request

/assign @qinyer

/milestone v1.2.0


new version 18 error

updated my docker and getting this msg
2023-04-18 12:14:12 [info] : http server started
2023-04-18 12:14:12 [info] : Connected to MQTT
2023-04-18 12:14:19 [error] : Error: State did not change for 3 tries. Last state: NotLoggedIn. Next update at 12:34:12 PM
any idea how to fix it?
my config
xfinity:
username: login
password: pass
interval: 20
http:
post:
url: http://<IP_ADDRESS>:7878/homeassistant
mqtt:
host: <IP_ADDRESS>
port: 1883
username: login
password: password
topic: xfinity
homeassistant:
prefix: "homeassistant"xfinity:

works now


WSS ERR_CONNECTION_CLOSED

i currently have this configuration on my LIghtsail VPS
public function handle() {
    require '/opt/bitnami/apache2/htdocs/gestionaleCore/vendor/autoload.php';

    $loop = ReactLoop::create();
    $pusher = new Pusher;
    // In ascolto del web sever per fare un push ZeroMQ dopo una richiesta AJAX.
    $context = new ReactContex($loop);
    $pull = $context->getSocket(\ZMQ::SOCKET_PULL);
    $pull->bind('tcp://<IP_ADDRESS>:5553');
    $pull->on('message', [$pusher, 'toBroadcast'] );

    $webSock = new ReactServer('<IP_ADDRESS>:33000', $loop);
    $webSock = new SecureServer($webSock, $loop, [
        'local_cert'        => '/opt/bitnami/apache2/conf/server.crt', // path to your cert
        'local_pk'          => '/opt/bitnami/apache2/conf/server.key', // path to your server private key
        'allow_self_signed' => TRUE, // Allow self signed certs (should be false in production)
        'verify_peer' => FALSE
    ]);

   $webServer = new IoServer(
      new HttpServer(
        new WsServer(
          new WampServer(
            $pusher
          )
        )
      ),
      $webSock
    );
    $this->info('Run handle SSL');
    $loop->run();
  }

From my javascript application i use this code
<body>
  <script src="autobahn.min.js"></script>
  <script>
    var conn;
    function onConnect(session) {
      console.log('connect!');
    }
    function onDisconnect(code, reason, detail) {
      console.log('disconnect!', code, reason, detail);
    }
    var configuration = {
      'maxRetries': 60,
      'retryDelay': 4000,
      'skipSubprotocolCheck': true
    }
    conn = new ab.connect('wss://[DOMAINNAME]:33000', onConnect, onDisconnect, configuration);
  </script>
</body>

on my firewall i've opened the port 33000
but every time i test my script i get this error on javascript console
WebSocket connection to 'wss://[DOMAINNAME].it:33000/' failed: Error in connection establishment: net::ERR_CONNECTION_CLOSED
Please i need help.
Best regards

@andreadompe This could be caused by many issues. What troubleshooting have you tried?


Early Film/Bio Sample experiments unbalanced

Bio experiments seem way too expensive (250 funds) for how little science they give. An early film camera is the same cost but is superior in nearly every way:

Early film duration is 5 minutes, bio is 30.
Early film can be used in low flying, bio cannot.
Early film has two slots and is biome-dependant, so with the short experiment duration, you can complete two valuable low-space or flying-high experiments in two different biomes in a single launch, or at least get flying high and low space in the same launch with only one experiment. Bio has a single slot and is biome-independant.

In short, you can easily get 10 science points in a single launch with a single early film experiment, but with bio experiments I think I get like 3 points at max per mission, and I need two parts (500 funds! on a sounding rocket one tenth that cost!) to get both flying high and low space.
I propose:
a) making early film experiments last 10 minutes, as they're a little easy to complete right now (I don't think I've ever needed two launches to finish an experiment).
b) Give bio experiments two slots, so they can complete flying high and low space at the same time.
c) Reduce bio experiment part cost to 50f.

fixed in https://github.com/Standecco/ROKerbalism/tree/experiments-fix


[ABW-1913] Apply divisibility to guaranteed amount

Jira ticket: ABW-1913
Description
After applying a guarantee, we should round the amount according to the divisibility of the resource.
How to test

Make an "estimated" transaction with a resource that has divisibility smaller than 18.
Apply a guarantee
-> The resulting amount should not have more decimals than the divisibility dictates

Screenshot
Coming
PR submission checklist

[x] I have tested account to account transfer flow and have confirmed that it works

This functionality is partly already existing, partly included in https://github.com/radixdlt/babylon-wallet-ios/pull/1010


Cannot Unit Test Angular Factory if $cordovaCalendar is injected n.plugins.calendar undefined

I need to test a service that depends on $cordovaCalendar.  I understand that using Karma to run tests in the browser I cannot actually test a non-existant calendar.  That's OK.  I just want to unit test other methods on my Factory.  In fact, I'm only using the findAllEventsInNamedCalendar method. What I need to do is mock out $cordovaCalendar to send Karma some pre-defined mock events.
I can't get past the angular.mocks.injector instantiating the factory so that I can mock the data. Even though I am NOT testing any method that calls $cordovaCalendar, and even though Karma will not load custom Factory dependencies, it STILL throws an error that n.plugins.calendar is undefined.  Any other dependency of my factory would remain undefined, but for some reason with $cordovaCalendar it all grinds to a halt at that error.
I am finding that I literally have to delete $cordovaCalendar from the list of injected services AND delete or comment out any method that has $cordovaCalendar before Karma will even get past the mock.inject phase.  This is a major pain and prone to introducing errors.
Am I missing something obvious?  How do I get past the instantiation of the factory so that I can stub out $cordovaCalendar.findAllEventsInNamedCalendar()?
Simplified example:

angular.module "test", ['ngCordova']
.factory 'GetEvents', ->
  return {
    readDevice: ->
      events = $cordovaCalendar.findAllEventsInNamedCalendar()
      return events
    manipulateSomeHow: (events) ->
      . . .
  }

describe 'GetEvents factory', ->
  beforeEach ->
    module 'test'
    inject (_GetEvents_) ->
      GetEvents = _GetEvents_
      GetEvents.readDevice = sinon.stub().returns {one:1, two:2}
  it 'exists', ->
    GetEvents.should.exist

FAILED TESTS:
  GetEvents factory
    ✖ "before each" hook
      PhantomJS 1.9.8 (Mac OS X 0.0.0)
    the object {
      "line": 60336
      "message": "'undefined' is not an object (evaluating 'n.plugins.calendar')"
      "name": "TypeError"

Greetings @rlrhett!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


Add Promise to convert jQuery deferred

Need add standard promise functions to convert jQuery deferred.

:+1:


CtrlMarkov?

The feature you'd like
Been reading through the release notes and can't find anything about CtrlMarkov being removed and would love to see it back!
Any alternatives you've considered
I don't know in the current documentation if CtrlMarkov has been replicated by any other feature.
Additional context
None

I miss it

It isn't much code if you wanted to just pull it into your own project.
Here's the original module: https://github.com/Tonejs/Tone.js/blob/389ccf87229df47a1560b37896da8f4c28aea7bb/Tone/control/CtrlMarkov.js
At some point didn't feel like an important part of Tone.js since it does neither scheduling nor synthesis and was more related to generative music more generally. As a maintainer, i've realized that a tightly scoped feature set that works well is the best thing i can do with this library vs trying to jam in the most features.

Why was this removed in the first place?


Using hashed lat/long for BNA's source_id leads to error

Currently the source_id value for BNA's charging stations is filled with the has value over lat/long. This leads to the situation that some charging stations have the same hash value because they have the same lat/long values set (most likely by error) and this in turn leads to the fact that some stations cannot be imported because of a unique key constraint error (source_id has to be unique)
I think we should generate the hash over all attributes of the BNA's charging station to avoid the described situation

Actually the problem is that the rows of the BNA data (and also FR data btw) have changed over time to resemble charge points of charging stations, rather than just a charging station per row.
In effect, we have to do some preprocessing to flatten serveral charge points into a single station.
On the other hand, this is also important for https://github.com/comsysto/eCharm/issues/28, maybe it is better to change our schema to actually handle charge points


fix: net. IP copy, sessions reference

Naming of test files is still ambiguous...

fix: net. IP copy, sessions reference -> fix: make net.IP copy when saving it, use sessions reference to keep extracted data?


Create multi-use invite on issuer creation and invite added to trust registry

@morrieinmaas can you please pick this up. Should be a fairly small change

@lohanspies sure - Will do


[feat] Implement P2WPKH tests/logic

Bitcoin has many different transaction types, one of them being P2WPKH.
In order to support these, we will need to make sure all edge cases and some mainnet P2WPKH transactions can successfully be validated by Shinigami.
Since Shinigami's design is heavily inspired by btcd, I recommend looking through all the witness transaction logic there and replicating it inside Shinigami's engine, where needed. Many witness features are implemented, but notably witness signature calculation is not done in OP_CHECKSIG/OP_CHECKMULTISIG/...
The learnmeabitcoin link can be super helpful in understanding Bitcoin P2WPKH transactions in depth.
Then, using the learnmeabitcoin P2WPKH examples and existing Shinigami transaction tests, create a set of tests to ensure all P2WPKH transactions run properly.
Resources
learnmeabitcoin P2WPKH
Existing P2PK & P2PKH tests in Shinigami
witness sig btcd

I

Hey @b-j-roberts.
Can I take a look at this?

@JoE11-y for sure, please lmk if you have questions! Good luck 🙏

Hey @JoE11-y , any updates on this issue? Many witness features have recently been merged, so I think the main thing we still need here is the P2WPKH tests from learnmeabitcoin.

@b-j-roberts just added it now.


Node to node ports lower than 1025 not authorized is causing issue with ingress controllers with service type load balancer (AWS)

Description
Since we upgrade module from v18 to v19, we got some issue with our ingress controllers. Here is our configuration:

We are deploying an EKS cluster with one managed node group with 4 EC2 instances
We have 1 ingress controllers with a service type Load balancer that is listening on 80 and 443 port
So we have 1 load balancer that registers our 4 EC2 instances
Our ingress controller is deployed as deployment with 2 pods on nodes A and B.

Nodes A and B are InService in our load balancer.
Nodes C and D are OutOfService in our load balancer.
I manually added port 80 and 443 as ingress rule on node security group from self, and all instances are InService.
My questions :

Is there a point to authorize reserved node between nodes of node security group ?
Should users of this module manage this kind of exception by using custom security group rules ?

Versions

Module version [Required]: >= v19.0.4

Terraform version: v1.3.6

Provider version(s): v4.47.0

Reproduction Code [Required]

Steps to reproduce the behavior:
Deploy an EKS cluster with managed node groups with 2 nodes at least.
Deploy an ingress controller in the cluster with Service type Load balancer and 1 pod.
Expected behavior
All nodes join are InService in Load balancer instances.
Actual behavior
Only nodes where are deployed ingress controller pods are InService in Load balancer instances.
Terminal Output Screenshot(s)

Additional context

this is to be expected. It is not known what ports users will run applications on and this access will need to be added by users. You can see more here https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/network_connectivity.md

Hello @bryantbiggs, thank you for your answer.
So, you assume that any user that deploys this module and want to use ingress-controllers will need to add custom rules on node security-group from itself to allow 80 (optionally) and 443 reserved port.
However, in last v19 releases, you added specific rules for Karpenter, ALB Controller, Gatekepper and more recently metrics-server. So, i'm wondering why not for ingress-controllers 🤔

@jbdelpech I might be wrong but for me the issue wasn't that my ingress was listening on port 80, but that the target service was listening on port 80.
kubectl get ing
NAME      CLASS    HOSTS                  ADDRESS                                                               PORTS   AGE
xxx-api   <none>   xxx.example.com   k8s-xxxx-xxxxx-123456-123456.us-east-1.elb.amazonaws.com   80      370d

kubectl get svc
NAME                      TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
xxx-api                   NodePort    <IP_ADDRESS>   <none>        80:32682/TCP   370d

So my assumption is  that @bryantbiggs is saying that users can choose whatever ports they want for their services and if you allow using privileged ones (0 - 1024), it's up to you to add extra ingress rules.
It caught me by surprise too because I think a lot of people will use ports 80 and/or 443 for their services and I don't really see a reason to not use the range 0 - 65536 instead.

I think a lot of people will use ports 80 and/or 443 for their services and I don't really see a reason to not use the range 0 - 65536 instead.

In prior versions, we received a lot of feedback stating that users were frustrated that they had to create their own security groups plus copy over the security group rules of interest in order to have a better security posture. The position that we have taken starting with v18 of the module is to remove all access except for only those rules that are absolutely required for a cluster to come up successfully (this is the cluster and its components, this is not meaning a cluster with a users application). This approach, in my opinion, is the lesser of two evils because users can now start from a strong security perspective and only open up the access they require - it is impossible to start with the access open and try to close that access down (hence the need for users to create their own security groups which causes lifecycle issues, etc.)
That said, in v19 we then added a parameter that is enabled by default that enables common/recommended rules for things that are typically found on a cluster - things like ALB/NGINX controllers, Karpenter, etc. I do not have a great "rule" as to what should or should not be added to this list of recommended rules, but potentially this is something that could accommodate the 80/443 rules listed above

closing since I believe the question has been answered. if not, please feel free to respond below


[REVIEW] Fix issue with duplicates in column renaming

When we have a dataframe df with columns: ['a', 'b'] and run a project statement:
SELECT a AS "I", a as "II" FROM df

there is an AssertionError that occurs here: https://github.com/dask-contrib/dask-sql/blob/11dcf222c317a5327b31a8a4e71eca7c3f61d54e/dask_sql/datacontainer.py#L62
This is the root cause for test_union_mixed failures. This PR attempts to fix this issue by introducing a new rename method so that other parts of the code-base can be switched to call rename_handle_duplicates on case-by-case basis if we start seeing similar issues with other rename calls.

Codecov Report

:exclamation: No coverage uploaded for pull request base (datafusion-sql-planner@11dcf22). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             datafusion-sql-planner     #559   +/-   ##
=========================================================
  Coverage                          ?   58.05%
=========================================================
  Files                             ?       72
  Lines                             ?     3559
  Branches                          ?      714
=========================================================
  Hits                              ?     2066
  Misses                            ?     1363
  Partials                          ?      130

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Included FAQ stub

I added a FAQ.md stub file for more in-depth information for particular problems.
After this has been merged to Leonidas repository, I suggest adding a direct link to FAQ in README.md

Pure awesomeness! Thanks @miohtama!


Grand Rapids Bitcoiners

Thanks for making a suggestion for a new meetup.
Please note: Only suggest bitcoin-only meetups.
Meetups which promote any coin or token other than Bitcoin are not suitable for listing.
Altcoin's are only mentioned in the context of warnings or lessons learnt for bitcoin.
Required:

Name of Meetup:
Location Of Meetup:
At least one of the following:

Meetup Page (or similar):
Telegram Group (or similar):
Website:

Optional

Name of Organiser(s) & Twitter Handle:
Links showing public support: >>>  example
Tweet your commitment

As the organiser of [>>>XXX<<<] Meetup I can confirm that the meetup is bitcoin-only
-The meetup is bitcoin focused.
-'Altcoins' are scams and are not promoted in talks/presentations at our meetups.
#bitcoinonlymeetups @bitcoinonly_

Is there a link or a twitter account?

https://github.com/bitcoin-only/bitcoin-only/issues/591

Twitter: @GRBTCEmail: @.: 6102bitcoin @.>Sent: Thursday, April 28, 2022, 17:30To: bitcoin-only/bitcoin-only @.>Cc: RWSlot @.>; Author @.***>Subject: Re: [bitcoin-only/bitcoin-only] 1. Grand Rapids Bitcoiners (Issue #590)
Is there a link or a twitter account?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


[BUG] Linker Error on Build

Building a Xamarin Forms (currently <IP_ADDRESS>0) project fails when using SkiaSharp 2.80.0.
error MT5209 : Native linking error : framework not found libSkiaSharp
MTOUCH : error MT5202: Native linking failed. Please review the build log.

Steps to reproduce:

In Visual Studio for Mac, create a new Xamarin Forms app using Blank Forms App template.
Upgrade NuGets on all 3 projects, Android, iOS, and Common. (Xamarin Forms -> <IP_ADDRESS>; Xamarin Essentials -> <IP_ADDRESS>)
Add SkiaSharp.Views.Forms (2.80.0) NuGet to the shared project.
Add a reference to SkiaSharp new SKCanvasView(); to MainPage.xaml.cs to prevent the Linker from pruning out SkiaSharp.
Perform Build All.

SkiaLinkerDemo.zip
Expected Behavior
App should build and be able to launch.
Actual Behavior
Build for iOS fails with linker errors.
Basic Information

Version with issue:  2.80.0
Last known good version: 1.68.3
IDE:  Visual Studio for Mac v8.6.5

Visual Studio Community 2019 for Mac
Version 8.6.5 (build 23)
Installation UUID: 06132a91-56f5-4cdb-afc7-6be5f4773937
	GTK+ 2.24.23 (Raleigh theme)
	Xamarin.Mac <IP_ADDRESS> (d16-6 / 088c73638)

	Package version: 610000104

Mono Framework MDK
Runtime:
	Mono <IP_ADDRESS> (2019-12/5d03a6fe116) (64-bit)
	Package version: 610000104

Roslyn (Language Service)
3.6.0-3.20210.9+4eafdcb1bcbd8d3573f2ba6065e56d9b9ce4f8a3

NuGet
Version: <IP_ADDRESS>91

.NET Core SDK
SDK: /usr/local/share/dotnet/sdk/3.1.301/Sdks
SDK Versions:
	3.1.301
	3.1.300
	3.1.202
	3.1.200
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/6.10.0/lib/mono/msbuild/Current/bin/Sdks

.NET Core Runtime
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
	3.1.5
	3.1.4
	3.1.2
	2.1.19
	2.1.18
	2.1.17
	2.1.16

Xamarin.Profiler
Version: <IP_ADDRESS>
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

Updater
Version: 11

Apple Developer Tools
Xcode 11.5 (16139)
Build 11E608c

Xamarin.Mac
Version: <IP_ADDRESS> (Visual Studio Community)
Hash: 29c4ea731
Branch: d16-6
Build date: 2020-05-26 17:03:04-0400

Xamarin.iOS
Version: <IP_ADDRESS> (Visual Studio Community)
Hash: 29c4ea731
Branch: d16-6
Build date: 2020-05-26 17:03:05-0400

Xamarin Designer
Version: <IP_ADDRESS>9
Hash: d4f8bcd13
Branch: remotes/origin/d16-6
Build date: 2020-04-24 02:16:02 UTC

Xamarin.Android
Version: <IP_ADDRESS> (Visual Studio Community)
Commit: xamarin-android/d16-6/3a10de9
Android SDK: **REMOVED**
	Supported Android versions:
		None installed

SDK Tools Version: 26.1.1
SDK Platform Tools Version: 29.0.5
SDK Build Tools Version: 29.0.2

Build Information:
Mono: 165f4b0
Java.Interop: xamarin/java.interop/d16-6@2cab35c
ProGuard: xamarin/proguard/master@905836d
SQLite: xamarin/sqlite/3.31.1@49232bc
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-6@bfb66f3

Microsoft OpenJDK for Mobile
Java SDK: **REMOVED**
1.8.0-25
Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

Android SDK Manager
Version: <IP_ADDRESS>
Hash: 5901879
Branch: remotes/origin/d16-6
Build date: 2020-06-10 22:42:50 UTC

Android Device Manager
Version: <IP_ADDRESS>
Hash: 6e8b80b
Branch: remotes/origin/d16-6
Build date: 2020-06-10 22:43:28 UTC

Build Information
Release ID: 806050023
Git revision: 5289d413b99fddfc20b4ecf3e445ccb822213427
Build date: 2020-06-18 12:08:30-04
Build branch: release-8.6
Xamarin extensions: 5289d413b99fddfc20b4ecf3e445ccb822213427

Operating System
Mac OS X 10.15.5
Darwin 19.5.0 Darwin Kernel Version 19.5.0
    Tue May 26 20:41:44 PDT 2020
    root:xnu-6153.121.2~2/RELEASE_X86_64 x86_64

Looking at the sample, seems that it can't find the native library. It appears that the app is pulling the managed library, but not the framework.
This is probably related to #1296 where the native library is not embedded. This fixes issues with upgrades, but seems to break the case where the skiasharp packages were not also installed into the app project.
I'll have a look at using the buildTransitive folder as well (#1041 and #1057).
But, the easiest and quickest solution is to just install the package into iOS as well.

I had the same problem I fixed it by
Disabling following Build options in the Debug Configuration:

Enable incremental builds
Enable device-specific builds

afterwards it worked.

@mattleibow We're seeing a similar issue in our Xamarin.Mac app. After going from 1.68.3 to 2.80.1 we no longer get libSkiaSharp.dylib in the app bundle. Adding the SkiaSharp package to our app project directly does work as a workaround. Do you want a repro?

Hi folks, I think I know what to do for this issue. I'll update with the next release.
But, installing SkiaSharp into the head projects is a good  workaround for now.

I had the same problem I fixed it by
Disabling following Build options in the Debug Configuration:

Enable incremental builds
Enable device-specific builds

afterwards it worked.

The above is not working for me at all.
"installing SkiaSharp into the head projects is a good workaround for now." solved this.

I had the same problem I fixed it by
Disabling following Build options in the Debug Configuration:

Enable incremental builds
Enable device-specific builds

afterwards it worked.

The above is not working for me at all.
"installing SkiaSharp into the head projects is a good workaround for now." solved this.

Yes this is the recommanded workaround, the problem was that I had installed Skia.Sharp already in the head projects and it still didn't work. So the workaround is in addition to installing Skia.Sharp in the head projects

Yes have installed SkiaSharp.Views.Forms in head projects for ok result.

I forget to mention that I installed SkiaSharp and SkiaSharp.Views.Forms in the head projects.
Maybe it is an issue with Svg.Skia (because this I use for Svg Images in Skia). I didn't do a Full investigation why it didn't work.
Only did trial and error until it worked.

Just for future reference, it might be the issue with incremental builds, so we should be disabling them.


WIP: add option to isolate on fork

Posting this quick experiment to get some feedback:

new option contextIsolationOnFork in Task.Options (in an ugly, but bincompatible way)
its handling in task.start that makes it isolate, but  join overrides whatever you had before - if you ever join

This still preserves fa.start.flatMap(_.join) <-> fa when fa is changing locals, just in a different way. It might prove less surprising for users of TaskLocal, but I don't know the extent of the impact for cats-effect based libraries like fs2 which might use Fibers underneath. At least with Options you can switch things around as you please, and we can see if we should consider changing the default model.

@oleg-py can you please explain why this is needed?
And why does it have to be an option in Task.Options?

@alexandru there are at least two lawful models for TaskLocal behavior in fibers:

we share everything by default unless you explicitly use isolate
we isolate every fiber (it gets its own copy of locals), but switch to its context if/when you join

Currently we only support model 1. For some uses - specifically, those not under your control and/or using tagless final, it's desirable to have both. As a contrived example, I can have a library that simplifies producer-consumer pattern:
object ProCon {
  def forever[F[_]: Concurrent: Parallel, A](produce: F[A], consume: A => F[Unit], bufferSize: Int): F[Unit] =
    for {
      q <- Queue.bounded[F, A](bufferSize)
      pro = (produce >>= q.enqueue1).foreverM[Unit]
      con = (q.dequeue1 >>= consume).foreverM[Unit]
      _ <- pro &> con // [1]
    } yield ()
}

As a user of monix and such library, I might need to put isolate around pro and con on line [1] to have producer and consumer fibers have their own copy, but I cannot do this without modifying the library. Putting isolate on produce and consume has totally different semantics (per each value produced as opposed to one for all values produced). Having it as a task option would allow me to just do:
ProCon.forever(mkInt, printInt, 42).executeWithOptions(_.enableContextIsolationOnFork).attempt

or if it's what my app needs most of the time, I can have this option toggled on by default and switch to shared model when I need to.
Putting it on options since it'll affect the execution of sub-tasks like the other two options we have. In 4.0 we can probably drop the booleans and have a enum of how locals work with  { Disabled, Shared, Isolated } as options. I'm open to other ideas, but I can't think of one.

@oleg-py Are you planning to continue work on this feature? I think I've just run into the underlying issue that this PR fixes, as well as #1146. My expectation was that start would appropriately isolate the context automatically without any user intervention.

@jvican well, given it's been over a year, probably no. I'm watching related developments in cats-effect 3 here though. I'm not sure what's the absolute best model would possibly be, but I'm leaning towards one where creator of local specifies the sharing strategy instead of user.

I've created an issue for it a while ago: https://github.com/monix/monix/issues/1302
Personally, I would like to support auto-isolation on fork, as a default.

but I'm leaning towards one where creator of local specifies the sharing strategy instead of user.

I feel like that at best, we could have it as a Task option, not Local because I don't see a way to have this strategy with Future

I feel like that at best, we could have it as a Task option, not Local because I don't see a way to have this strategy with Future

I am talking about TaskLocal only since we have no control over how operations with Local are forked. I think that creator of TaskLocal knows best what it should be used for and can therefore pick a proper strategy. Having an option on Task means that you, as a user, must know what bits of code uses TaskLocal so you can properly isolate (or not) on the outside.


Migrate from dialog flow v1 to v2 APIs

Dialog flow V1 APIs are going to be shut down on October 23rd 2019. We need to migrate Benten from V1 to V2 APIs of dialog flow.

Dibs 🚀 I'd like to get started on this.

@strangest-quark that will be very helpful thanks!

Functionality implemented and merged #38


[5.5] Added nullable helper to request

This adds a 'nullable' helper to the Request (input concern).
When working with APIs and you're updating a resource sometimes the input is presented as an empty string. In those cases you most likely want to 'remove' or 'reset' something.
However, using intersect would ignore this input and with only your database would become a mess after a while... Therefore a nullable helper to aid you in those if then situations.
Example
$requestedInput = [
    'name' => 'John Doe',
    'optional_description_i_want_to_reset' => '',
];

$attributes = Request::nullable('name', 'optional_description_i_want_to_reset');

// Results in
$result = [
    'name' => 'John Doe',
    'optional_description_i_want_to_reset' => null,
];

You can use Request::all('name', 'optional_description_i_want_to_reset');.

@bonzai Like I've mentioned in the introduction that would result in empty strings not null values.
This is just a shortcut to prevent doing something like this:
$nullableEntityAttributes = array_map(function ($value) {
    return ! empty(trim($value)) ? $value : null;
}, array_only($request->all(), ['description', 'phone_number', 'vat']));

I've updated my comment.

@bonzai I stand corrected, apparently I've missed those during upgrade. (They're not mentioned in the upgrade docs either 🤔)

It was mentioned here:
https://laravel.com/docs/5.4/releases#laravel-5.4  (Request Sanitization Middleware)

D'oh thanks for pointing that one out!


build: update to lnd v0.15.2

This commit updates to the hotfix release for v0.15.2 which fixes an issue in wire parsing that could cause lnd to be unable to parse a bug.

LGTM
running btcd v0.23.2 and lnd v0.15.2-beta on my node right now without issue


Implement the pagination to PollAnswers

Feature description

This issue is for the PollAnswer part's implementation of #448.
In the current version, all the poll answers of the poll are stored in one key. Then, it is always used for checking if user answered the poll by GetPollAnswersByUser.
It should be split to a answer to be associated to only one key related to  postID and user so that it can be checked more efficient and paginated when querying.
Implementation proposal

The key of the PollAnswer can be postId+userAddress+answerID. In this way, we can implement the pagination to PollAnswer. Besides, we can also refractor the GetPollAnswersByUser function to be more efficient.

I double think about the implementation pagination to PollAnswer when writing code.
Currently Desmos has three objects to handle the answer: UserAnswer, UserAnswers and UserAnswerEntry.
UserAnswer is for creating an answer to a poll, It includes a user address and answers array.
UserAnswers is for creating the UserAnswerEntry from UserAnswer.
UserAnswerEntry is for genesis exporting and importing.
To implement pagination to answer. The answer objects can be changed to the following structures:
// UserAnswer contains the data of a user's answer to a poll for storage
message UserAnswer {
  option (gogoproto.equal) = true;
  option (gogoproto.goproto_stringer) = true;

  string post = 1;
  string user = 2;
  string answer = 3;
}

// UserAnswers wraps a list of answers by a user for sending the message
message UserAnswers {
   string user = 1;
   repeated string answers = 2;
}

And the key of a user answer could be postId+userAddress+answerID.
This allows:

Operate a user's poll answers toward the post easily by iterating over PollAnswersPrefix + '<post-id>' + '<user-address>'
Query all the answers towards the post by iterating over PollAnswersPrefix + '<post-id>'
Export and import genesis without UserAnswerEntry

What do you think? @RiccardoM @bragaz

This looks good! 👍 It will help also reduce the complexity around the polls IMO.
Good job @dadamu!

@dadamu I'm having a hard time remembering one thing. Why can't we simply use a single entity named UserAnswer?
// UserAnswer contains the data of a user's answer to a poll
message UserAnswer {
  option (gogoproto.equal) = true;
  option (gogoproto.goproto_stringer) = true;

  string post = 1;
  string user = 2;
  repeated string answers = 3;
}

This way we can simply use MsgAnswerPoll:
message MsgAnswerPoll {
    string post = 1;
  string user = 2;
  repeated string answers = 3;
}

And then we can store the answers as `PollAnswerPrefix + PostID + UserAddress -> UserAnswer.
When we need to export them, we simply export a []UserAnswer and then import them easily. This should be sufficient, or are there any particular cases which make this not sufficient?

@RiccardoM I also thinking about this. By this way, the answer querying would be paginated by user. Then, paginating by user is okay for the case. So, I agree with it.


Add support for Blackrock NSx files with per-sample PTP nanosecond timestamps

Fixes #1332
Blackrock's newest signal acquisition devices use nanosecond timestamps from clocks synchronized with PTP. This allows synchronization between devices that might have slightly different clock rates and not capture exactly 30_000 samples per reference second.
Individual per-sample timestamps are stored in a data header, per sample.
Previously, the presence of a header in the data block would indicate the start of a new segment, and methods would look for the header to start a new memmap. That previous solution, when applied to millions of headers in the PTP-enabled files, led to OS-level problems by creating too many memmaps.
This PR allows the new PTP-enabled NSx files to be loaded.
Note: the time range of data files no longer start at 0! They start at whatever the monotonic clock was when the NSx file was recorded. We can't simply re-zero the timestamps per file because there might be multiple sets of files that were recorded simultaneously (i.e., from different pieces of hardware) but didn't start at the exact same time. We could re-zero with the common minimum across all devices, but the BlackrockRawIO loader doesn't support multi-device ns6 files. For now, it's best to leave it to the user to load the K files manually then find their own common t-zero among those K files.

Hello @cboulay! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file neo/rawio/blackrockrawio.py:

Line 324:1: W293 blank line contains whitespace
Line 326:17: E125 continuation line with same indent as next logical line
Line 381:21: E125 continuation line with same indent as next logical line
Line 458:100: E501 line too long (103 > 99 characters)
Line 966:1: W293 blank line contains whitespace
Line 983:17: E126 continuation line over-indented for hanging indent
Line 987:13: E121 continuation line under-indented for hanging indent
Line 1002:100: E501 line too long (114 > 99 characters)
Line 1004:100: E501 line too long (110 > 99 characters)
Line 1007:100: E501 line too long (111 > 99 characters)
Line 1014:100: E501 line too long (117 > 99 characters)
Line 1057:1: W293 blank line contains whitespace
Line 1067:17: E126 continuation line over-indented for hanging indent
Line 1071:13: E121 continuation line under-indented for hanging indent
Line 1082:100: E501 line too long (125 > 99 characters)

OK this is ready for review. If you want a sample data file then that will have to wait until Friday when I'm in front of the hardware needed to produce the 3.0-ptp variant file spec.

Hi Chadwick.
An enormous thanks for figthing with this new version of blackrock.
I will have a look soon. Lets wait friday to get the the test file that corresponf to this.
Can you try to make a very very short one ?

I found and fixed a bug in my previous implementation thanks to unit tests I just added.
Here's the test file. If you can provide me instructions on how to created a pull request on GIN then I can go ahead and do that, but I'm also totally satisfied having someone else do it if you're already setup for that.
blackrock_3_0_ptp.zip

I push tests files here https://gin.g-node.org/NeuralEnsemble/ephy_testing_data/pulls/121/files

OK I've rebased and fixed the conflicts along the way. Let's hope the tests pass. BTW, I don't mind if you squash the commits when merging... there was some back and forth on quotes that become obsolete when you adopted PEP8.

Actually I went ahead and squashed into 1 commit.
The unit test isn't running because it can't find the file. I guess I'm not providing its path correctly. Can anyone help me out with that part?

I'm pretty lost trying to figure out what's going on the with file loading. I'm happy to yield to someone else.

@cboulay,
We are planning on including this in the next release which will go out in the next few days so if you have the time to either implement my commit fix or give us access we will include otherwise we will plan on this for the next release.

I don't see the option to allow edits from maintainers. I found the GH docs that explains it but the option isn't on this page.

Normally there is a little check box on the right side of the bag just below all the info. When I first looked at your PR you had it turned on but it got switched off at some point. Either way we will see if tests pass now!

Seems like it failed. Could you doublecheck the gin link I gave you and make sure it has all the files necessary for blackrock?

Ah, it's because I made the PR from the lab org. sigh

So I thin there are two paths that need to be fixed. One at the top and one at the bottom. Since I can't push stuff here do you want a PR on your branch with the two file path fixes I think we need and we can test?

That's cool. One last check:
could you try this as the filename? Previously you didn't have the -001 right? so maybe it needs the full file name for the .nev file?
20231027-125608-001

Perfect that worked! thanks for bearing with me! The dirname messed with me! We should really call that filename in the tests for this IO (not your fault, something we've been discussing #1455 recently).

Seems to be working. Thanks for your help!

@samuelgarcia tests are passing here, but you also said you would look over the code. Did you want to read this over first before we merge?

Thanks a lot for this new add Chadwick.
And thanks a lot to wait for me.
this looks good to me.


Adds name and address vcard when creating coauthors. Refactors name a…

…nd address transformation.
closes #127

Following @jcoyne's example.


Browser hang when logging console message

After putting my create-react-app into production using logdna-browser, I received two reports from end users of the browser hanging completely. My suspicion is that it is the same problem as this issue: https://github.com/pinojs/pino/issues/990
On reverting the update that added logdna-browser, the same users reported the hanging problem was gone. I asked one of the users to send their browser console output to see what was there that might have been triggering the problem. I think it's likely to the non-fatal error shown below (from somewhere deep in threejs):

(FWIW, this looks like it contains an instance of https://github.com/mrdoob/three.js/blob/master/src/math/Box3.js)
Additionally, I confirmed that logdna-browser is the only package in my project that uses fast-safe-stringify:
 npm ls fast-safe-stringify
<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
I've not been able to reproduce the browser hang so far, but I suspect outputting an object that contains circular references may trigger it.

Also likely relevant: https://github.com/davidmarkclements/fast-safe-stringify/issues/46

@stephent Thank you for reporting this.  I will read up on the issues that you posted and try to reproduce the issue.

BTW, this is my config for logdna-browser:
import logdna from '@logdna/browser';

logdna.init(process.env.REACT_APP_LOGDNA_INGESTION_KEY,
  {
    console: {
      integrations: ['log', 'info', 'warn', 'error']
    },
    enableStacktrace: false,
    env: process.env.NODE_ENV,
  }).addContext({
    // Context is appended to the metadata of each message sent to LogDNA
    // Add any custom meta data such as:
    version: process.env.REACT_APP_VERSION
  }
);


ArenaConfig  (yaml) doesn't load any configuration on Windows

While running directly: AnimalAI-Olympics\env\AnimalAI.exe correctly displays all random objects,
trying to use python api:
AnimalAI-Olympics\examples>python visualizeArena.py configs/5-SpatialReasoning.yaml
displays an empty arena with blue ball which cannot be controlled.
The same is true with other *.yaml files.
Something wrong is going with yaml loader.
I have installed:
pyyaml                 5.1.1              pypi_0    pypi
yaml                      0.1.7             hc54c509_2
I put two print() in arena_config.py ::
class ArenaConfig(yaml.YAMLObject):
yaml_tag = u'!ArenaConfig'
def __init__(self, yaml_path=None):
    if yaml_path is not None:
        self.arenas = yaml.load(open(yaml_path, 'r'), Loader=yaml.Loader).arenas
        print("AAA 2 "+yaml_path)
    else:
        print("AAA 3")
        self.arenas = {}

Here is the output:
AnimalAI-Olympics\examples>python visualizeArena.py configs/5-SpatialReasoning.yaml
AAA configs/5-SpatialReasoning.yaml
AAA 2 configs/5-SpatialReasoning.yaml
AAA 3

It seems ArenaConfig() is initialized twice and the second time there is no *.yaml parameter?!

I cannot recreate this error on the Windows machine I have access to for testing.
Are you using the animalai (or animalai-train) pip package with python 3.6? Both seem to work fine with a fresh install.
Could you ellaborate on what you mean by:
I have installed:
pyyaml 5.1.1 pypi_0 pypi
yaml 0.1.7 hc54c509_2
The pip package only requires pyYAML 5.1.1 so perhaps this is what is causing the issue.

Due to https://github.com/beyretb/AnimalAI-Olympics/issues/32
I used old install_requires for animalai_train setup, but this is not related to the problem.
I reinstalled everything in a new virtual env without animalai_train and yaml 0.1.7 :
conda list
# packages in environment at Q:\Anaconda\envs\animalai:
#
# Name                    Version                   Build  Channel
animalai                  1.0.3                    pypi_0    pypi
certifi                   2019.6.16                py36_1    conda-forge
cloudpickle               1.2.1                    pypi_0    pypi
future                    0.17.1                   pypi_0    pypi
grpcio                    1.11.1                   pypi_0    pypi
gym                       0.13.1                   pypi_0    pypi
jsonpickle                1.2                      pypi_0    pypi
numpy                     1.14.5                   pypi_0    pypi
pillow                    5.4.1                    pypi_0    pypi
pip                       19.0.3                   py36_0    conda-forge
protobuf                  3.6.1                    pypi_0    pypi
pyglet                    1.3.2                    pypi_0    pypi
python                    3.6.3                         4    conda-forge
pyyaml                    5.1.1                    pypi_0    pypi
scipy                     1.3.0                    pypi_0    pypi
setuptools                41.0.1                   py36_0    conda-forge
six                       1.12.0                   pypi_0    pypi
vc                        14.1                 h0510ff6_4
vs2015_runtime            14.15.26706          h3a45250_4
wheel                     0.33.4                   py36_0    conda-forge
wincertstore              0.2                   py36_1002    conda-forge

I even tried with full path-parameter:
AnimalAI-Olympics\examples>python visualizeArena.py Q:/AI/Contests/NIPS/AnimalAI/AnimalAI-Olympics/examples/configs/1-Food.yaml
but the problem persists.

Hi,
I don't have a windows machine at hand at the moment so I can only try to help you by asking you to conduct a few steps yourself:

running python visualizeArena.py configs/5-SpatialReasoning.yaml do you get any error message or is the environment just stuck?
if you have an error paste it here, if not wait for a few seconds and interrupt the process (ctrl+c) in the terminal and paste the call stack here, this will help identify where the code is stuck
if you have a unity logfile paste its content here too

My guess is not on the yaml loader, but rather on the communicator between the environment and the API. There seems to be issues on windows with the grpcio package...

Hi,
You are right, it shouldn't be yaml loader, since even without *.yaml parameter it behaves in the same way -  empty arena with blue ball which cannot be controlled. Only [c] - change camera view works.

the environment is just stuck without any error messages
here is the log after Ctl+C (I just added one print to be see the yaml parameter) :

Q:\AI\Contests\NIPS\AnimalAI\AnimalAI-Olympics\examples>python visualizeArena.py configs/5-SpatialReasoning.yaml

AAA configs/5-SpatialReasoning.yaml
Traceback (most recent call last):
  File "visualizeArena.py", line 40, in <module>
    env = init_environment(env_path, docker_target_name, no_graphics, worker_id, run_seed)
  File "visualizeArena.py", line 29, in init_environment
    play=True
  File "Q:\Anaconda\envs\animalai\lib\site-packages\animalai\envs\environment.py", line 73, in __init__
    aca_params = self.send_academy_parameters(rl_init_parameters_in)
  File "Q:\Anaconda\envs\animalai\lib\site-packages\animalai\envs\environment.py", line 504, in send_academy_parameters
    return self.communicator.initialize(inputs).rl_initialization_output
  File "Q:\Anaconda\envs\animalai\lib\site-packages\animalai\envs\rpc_communicator.py", line 77, in initialize
    if not self.unity_to_external.parent_conn.poll(90):
  File "Q:\Anaconda\envs\animalai\lib\multiprocessing\connection.py", line 257, in poll
    return self._poll(timeout)
  File "Q:\Anaconda\envs\animalai\lib\multiprocessing\connection.py", line 330, in _poll
    return bool(wait([self], timeout))
  File "Q:\Anaconda\envs\animalai\lib\multiprocessing\connection.py", line 859, in wait
    ready_handles = _exhaustive_wait(waithandle_to_obj.keys(), timeout)
  File "Q:\Anaconda\envs\animalai\lib\multiprocessing\connection.py", line 791, in _exhaustive_wait
    res = _winapi.WaitForMultipleObjects(L, False, timeout)
KeyboardInterrupt

It seems that there is no communication with Unity environment.
I used Unity Machine Learning Agents Toolkit (ML-Agents)  some time ago without any problems, but in order to solve current problem I reinstalled Anaconda and everything is lost. It would have been helpful to compare the envs.

Hi,
The problem is solved!
I had the similar one with ML-Agents. Probably Unity ML messed up with http_proxy settings. The solution may look silly, but it works:
Open  a  new terminal
set http_proxy=
set https_proxy=

That's it. Then running:

python visualizeArena.py configs/5-SpatialReasoning.yaml

we have objects and control.

closing the issue as it is solved


Request ZX TwoQubit Gate

Is your feature request related to a use case or problem? Please describe.
In original, the Fahri et al. proposed classifier is make use of ZX gate, however, the tfq tutorial use the ZZ gate.
At first, I want to custom the ZX Gate but the magic mehod is too complex to override.
For example, pow method, I can not understand how to override. (seems have protocol behind the mul method)
Describe the solution you'd like
Maybe you can offer the ZX gate.
[optional] Describe alternatives/workarounds you've considered
x
[optional] Additional context (e.g. screenshots)
x
What is the urgency from your perspective for this issue? Is it blocking important work?

P2 - we should do it in the next couple of quarters

For example, pow method, I can not understand how to override.

Did you define your ZX gate as an EigenGate?
We have an implementation of this gate in cirq-superstaq that you can take the pow of like ZX ** 0.5.

For example, pow method, I can not understand how to override.

Did you define your ZX gate as an EigenGate?
We have an implementation of this gate in cirq-superstaq that you can take the pow of like ZX ** 0.5. We can add this gate to Cirq's mainline if you'd like to use it.

My fault, I have not to check all documents, many thanks !!

For example, pow method, I can not understand how to override.

Did you define your ZX gate as an EigenGate?
We have an implementation of this gate in cirq-superstaq that you can take the pow of like ZX ** 0.5. We can add this gate to Cirq's mainline if you'd like to use it.

However, I got the following error message while I package the ZX gate into the tfq.layers.PQC,

    from cirq_superstaq import custom_gates

    def create_quantum_model():
        """Create a QNN model circuit and readout operation to go along with it."""
        data_qubits = cirq.GridQubit.rect(4, 4)  # a 4x4 grid.
        readout = cirq.GridQubit(-1, -1)         # a single qubit at [-1,-1]
        circuit = cirq.Circuit()

        # Prepare the readout qubit.
        circuit.append(cirq.X(readout))
        circuit.append(cirq.H(readout))

        builder = CircuitLayerBuilder(
            data_qubits = data_qubits,
            readout=readout)

        # Then add layers (experiment by adding more).
        builder.add_layer(circuit, cirq.XX, "xx1")
        builder.add_layer(circuit, custom_gates.ZX, "zx1")

        # Finally, prepare the readout qubit.
        circuit.append(cirq.H(readout))

        return circuit, cirq.Z(readout)

Unfortunately, the ZX gate seems not competiable into the tfq.layers.PQC layer by using the same serialize protocol ?

The ZX gate is not part of the Serializable gate set in cirq_google. You need to add it like so: https://github.com/quantumlib/Cirq/blob/9349802d924bb5d23753fe0e30e396e0ec84af38/cirq-google/cirq_google/serialization/serializable_gate_set_test.py#L25

Hi @HuangChiEn I would recommend taking a look at: https://www.tensorflow.org/quantum/api_docs/python/tfq/util/get_supported_gates
In order to check if the gate is supported inside of TFQ. Generally speaking TFQ can't support arbitrary gates.
If you wanted to add it, you could add serialization support here (https://github.com/tensorflow/quantum/tree/master/tensorflow_quantum/core/serialize), add adjoint information in C++ (https://github.com/tensorflow/quantum/blob/master/tensorflow_quantum/core/src/adj_util.h) and add parameter shift information in C++ (https://github.com/tensorflow/quantum/blob/master/tensorflow_quantum/core/ops/tfq_ps_decompose_op.cc).
On another note, if you want to realize a ZX like unitary, you could just sandwich a cirq.ZZ ** (whatever) in between two cirq.Hs on the target qubit and you've got basically the same thing.

^^ Is the right answer. I didn't know this issue leaned more TFQ than Cirq. Hopefully this helps you @HuangChiEn.


How Set Direction of Excel Document to RTL

Hi
I need to set set direction of whole excel document into Right to Left (RTL), How do this?

Dear @mpachini
Not supported. I will add it to the enhancement.

Thanks.


.listeners() does not seem to work

SDK Version
1.4.1
What happened?
I'm trying to check if a listener was already started.
I essentially do the following:
const listeners = await ngrokSdk.listeners();
But this returns an array of length 0, despite a listener to ngrok is running in the terminal window next to the process?

Relevant log output
No response

How did you start the agent? Was it through the ngrok-javascript sdk or did you use something like homebrew?


Error determining whether a variable is optional

Not sure if I'm doing this right... but if I try to create a template using isOptional the sourcery script crashes:
2017-01-04 01:21:24.154 Sourcery[48549:19632156] *** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<Sourcery.Variable 0x7ff5cf9340a0> valueForUndefinedKey:]: this class is not key value coding-compliant for the key isOptional.'

...
Generating code.../Users/achan/repos/Noosh/Pods/Sourcery/bin/sourcery: line 6: 48549 Abort trap: 6           "${parent_path}"/Sourcery.app/Contents/MacOS/Sourcery "$@"
Command /bin/sh failed with exit code 134

I'm using Cocoapods to install Sourcery (0.5.0) with a template like this:
{% for type in types.implementing.MyProtocol %}
  {% for variable in type.variables %}
    {{ variable.isOptional }}
  {% endfor %}
{% endfor %}

If I replace {{ variable.isOptional }} with {{ variable.isStatic }}, the script passes and I get a file with a bunch of 0s.

you are doing it right, there is a bug on 0.5.0 because we used POP and that's not working with KVC, I already fixed it on master and will be available in next release, for now you can just do variable.typeName.isOptional

👍 Thanks for the quick reply and great work to everyone involved. Loving the project so far!

@achan should be fixed in the newest 0.5.1 release, let me know ;)

Confirmed 👍


pipe  and integration creation based on YAML file fails ,

What happened?
i have this yaml  and applied , it created pipe and integration but it showing error

kubectl logs pipe/test
error: no kind "Pipe" is registered for version "camel.apache.org/v1" in scheme "pkg/scheme/scheme.go:28"

and also Integration
kubectl get it
NAME                            PHASE   READY   RUNTIME PROVIDER   RUNTIME VERSION   CATALOG VERSION   KIT                        REPLICAS
test                       Error   False   quarkus            3.15.0            3.15.0            kit-ct1up2gro8bs73dchil0   1

kind: Pipe
metadata:
  name: test
  namespace: camel-k
spec:
  sink:
    properties:
      channel: channelname
      destinationName: destinan
      password: '{{pass}}'
      queueManager: test.UAT.BSSB
      serverName: serverip
      serverPort: "1414"
      username: app
    ref:
      apiVersion: camel.apache.org/v1
      kind: Kamelet
      name: jms-ibm-mq-sink
  source:
    properties:
      queueNameOrArn: queue
      region: us-west-2
      accessKey: "dummy"
      secretKey: "dummy/sk45"
    ref:
      apiVersion: camel.apache.org/v1
      kind: Kamelet
      name: aws-sqs-source

Any idea what's missing here?
Another Query how we can pass ServiceAccount to pipe yaml instead of aws accesskey and secretkey
Steps to reproduce
No response
Relevant log output
No response
Camel K version
No response

Hello. It seems the installation did not proceed correctly. I suggest you to clean the previous installation and proceed from scratch following the official Camel K installation guides.

You may also want to check the Camel K troubleshooting guide.

The usage of ServiceAccount has nothing to do with the Kamelet or component configuration. You still need to provide secret, likely in the form of Camel properties which are backed by a Secret config.

Okay. thank you .
now i am getting error on integration , these integration automatically created when  apply pipe yaml .
is there way we can pass  traits to integration from pipe.yaml
 kubectl logs payments-backend-sqs-to-ibmmq-pavan-8454c5755c-rngns exec /opt/java/openjdk/bin/java: exec format erro
from pipe.yaml how we can set
 traits:     affinity:       node-affinity-labels: "kubernetes.io/arch in(amd64)"
when i am applying yaml with above traits setting , i am getting
Error from server (BadRequest): error when creating "pipe.yaml": Pipe in version "v1" cannot be handled as a Pipe: strict decoding error: unknown field "spec.traits"

Yes, the trait configuration in Pipes is different.

Hi Team ,  could you please help me to leverage k8s secrets in pipe.yaml .  here i am trying but its not working. how pipe.yaml will read secrets from k8s .  could you please give me proper yaml
apiVersion: camel.apache.org/v1
kind: pipe
metadata:
name: payments-backend-sqs-to-ibmmq-pavan
namespace: camel-k
spec:
traits:
mount:
configs:
- name: camel-sqs-cred
mountPath: /mnt/secrets
optional: false
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-sqs-source
properties:
queueNameOrArn: "queyename"
region: "us-west-2"
accessKeyId: "{{ env:aws-access-key-id }}"
secretAccessKey: "{{ env:aws-secret-access-key }}"
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: jms-ibm-mq-sink
properties:
channel: "test.TO.BSSB.UAT.CHAN"
destinationName: "test.UAT.BSSB.MT.INPUT"
password: "{testbackend/mq-app-password}}"
queueManager: "test.UAT.BSSB"
serverName: "ip4"
serverPort: "1414"
username: "app"

Hello. All the information is provided in the links in the documentation posted in previous comments, please, go through it.

You must specify traits via annotation
Once you've specified the secret to use, you can use any camel properties normally as {{my.camel.property}}

@squakez : I tried using the access key and secret, but it's not working. Could you please provide a sample pipe.yaml file that uses secrets from Kubernetes secrets? Alternatively, is there a way to use an IAM role through a service account in the pipe.yaml

Hello, there should be enough documentation about this matter as shared in the previous comments. This is how to configure on an Integration: https://camel.apache.org/camel-k/2.5.x/configuration/runtime-config.html#runtime-config-props - the mechanisms for the Pipe is identical.

"I followed the documentation, but it's not picking up the secrets and is giving the error: Caused by: j: java.lang.IllegalArgumentException: useDefaultCredentialsProvider is set to false, useProfileCredentialsProvider is set to false, useSessionCredentials is set to false, AmazonSQSClient or accessKey and secretKey must be specified
In my pipe.yaml, it works when I directly use the AWS accessKey and secretKey, but I cannot commit these keys to GitHub for security reasons. Instead, I want to use a Kubernetes ServiceAccount with IRSA roles in the kind: pipe Kubernetes configuration. How can I achieve this, or how can I reference Kubernetes secrets inside the pipe.yaml file
kid: pipe
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-sqs-source
properties:
queueNameOrArn: "queue-name"
region: "us-west-2"
accessKey: "keyname"
secretKey: "secrets"

Use a secret, you cannot refer a service account.

Okay , apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: sqs-to-ibmmq
namespace: camel-k
labels:
annotations:
trait.camel.apache.org/kubernetes.volumes: |
volumes:
- name: aws-credentials-volume
secret:
secretName: camel-sqs-cred  # Reference the secret where AWS credentials are stored
volumeMounts:
- mountPath: /etc/camel/resources.d/_secrets/camel-sqs-cred  # Mount path for the secret
name: aws-credentials-volume
trait.camel.apache.org/kubernetes.env: |
- name: AWS_ACCESS_KEY_ID
valueFrom:
secretKeyRef:
name: camel-sqs-cred
key: aws-access-key-id  # AWS access key from the secret
- name: AWS_SECRET_ACCESS_KEY
valueFrom:
secretKeyRef:
name: camel-sqs-cred
key: aws-secret-access-key  # AWS secret access key from the secret
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-sqs-source
properties:
queueNameOrArn: "queuename"
region: "us-west-2"
accessKey: "{{ env:AWS_ACCESS_KEY_ID }}"
secretKey: "{{ env:AWS_SECRET_ACCESS_KEY  }}"
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: jms-ibm-mq-sink
properties:
channel: "test.TO.BSSB.UAT.CHAN"
destinationName: "test.UAT.BSSB.MT.INPUT"
password: "{{mq-app-password}}"
queueManager: "reat.UAT.BSSB"
serverName: "IP"
serverPort: "1414"
username: "app" , i tried this yaml also. but
Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create route source: Route(source)[From[aws2-sqs:{{queueNameOrArn}}?accessKey=xxxxxx because of Failed to resolve endpoint: aws2-sqs://queue name?accessKey=xxxxxx&amazonAWSHost=amazonaws.com&autoCreateQueue=false&delay=500&deleteAfterRead=true&greedy=false&maxMessagesPerPoll=1&overrideEndpoint=false&protocol=https&region=us-west-2&secretKey=xxxxxx&sessionToken=xxxxxx&useDefaultCredentialsProvider=false&useProfileCredentialsProvider=false&useSessionCredentials=false due to: The security token included in the request is invalid. (Service: Sqs, Status Code: 403, Request ID: 877ef9f1-9e7d-5bf6-9e7f-a6392799a81d)

Now getting aused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: aws2-sqs://queue-jaeaccessKey=xxxxxx)&amazonAWSHost=amazonaws.com&autoCreateQueue=false&delay=500&deleteAfterRead=true&greedy=false&maxMessagesPerPoll=1&overrideEndpoint=false&protocol=https&region=us-west-2&secretKey=xxxxxx)&sessionToken=xxxxxx&useDefaultCredentialsProvider=false&useProfileCredentialsProvider=false&useSessionCredentials=false due to: Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): 'n89f/dLinHLU1RT5+GtK0ZOBXg7Ov6gUs8MgPGbLap4='.

Can you post the pipe now? It seems you syntax is wrong

`apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: test-backend-sqs-to-ibmmq-pavan
namespace: camel-k
labels:
helm.sh/chart: universal-chart_v2.48.4
app: test-backend
junipersquare.com/initiating_pull_request: pr-1427
junipersquare.com/initiating_repo: test-backend
junipersquare.com/requestor: euanlau
tags.datadoghq.com/env: prpay1427
tags.datadoghq.com/version: pr-1427
annotations:
app: payments-backend1
department: eng
junipersquare.com/initiating_pull_request: pr-1427
junipersquare.com/initiating_repo: test-backend1
junipersquare.com/requestor: euanlau
product: gpx fa
tags.datadoghq.com/env: prpay1427
tags.datadoghq.com/version: pr-1427
team: payments
annotations:
app: payments-backend1
trait.camel.apache.org/kubernetes.volumes: |
volumes:
- name: aws-credentials-volume
secret:
secretName: camel-sqs-cred  # Reference the secret where AWS credentials are stored
volumeMounts:
- mountPath: /etc/camel/resources.d/_secrets/camel-sqs-cred  # Mount path for the secret
name: aws-credentials-volume
trait.camel.apache.org/kubernetes.env: |
- name: AWS_ACCESS_KEY_ID
valueFrom:
secretKeyRef:
name: camel-sqs-cred
key: aws-access-key-id  # AWS access key from the secret
- name: AWS_SECRET_ACCESS_KEY
valueFrom:
secretKeyRef:
name: camel-sqs-cred
key: aws-secret-access-key  # AWS secret access key from the secret
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-sqs-source
properties:
queueNameOrArn: "queuename"
region: "us-west-2"
accessKey: "({{ env:AWS_ACCESS_KEY_ID }})"
secretKey: "({{ env:AWS_SECRET_ACCESS_KEY }})"
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: jms-ibm-mq-sink
properties:
channel: "test.TO.BSSB.UAT.CHAN"
destinationName: "test.UAT.BSSB.MT.INPUT"
password: "{{/mq-app-password}}"
queueManager: "JSQ.UAT.BSSB"
serverName: "ip"
serverPort: "1414"
username: "app"`

This
({{ env:AWS_ACCESS_KEY_ID }})
Should be RAW({{ env:AWS_ACCESS_KEY_ID }})
Same for the secret key. I wrote it above

Still same issue Caused by: software.amazon.awssdk.services.sqs.model.SqsException: Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): 'hMg4ZI09YH7RNqzswja69tK20cHVncx0RApiU0fJLrU='. (Service: Sqs, Status Code: 400, Request ID: b4c352cb-e952-5053-b9e8-0d0317df63a2)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleErrorResponse(CombinedResponseHandler.java:125)

That component, with that authentication mechanism,have been around for many years, so I can only suppose it is something on your side. We cannot help more than this.

@pguptajsq I think you can take as a reference this chat thread: https://camel.zulipchat.com/#narrow/channel/257299-camel-k/topic/Hashicorp.20Token.20in.20modeline/near/480962291
Ideally you should be able to put in your Pipe or Integration specification a Camel property, such as {{my.aws.key}}. Then, you need to provide a secret containing such variable, eg, kubectl create secret generic my-secret --from-literal my.aws.key=123456. Finally you can run your Pipe or Integration mounting the secret via mount.config=secret:my-secret. At runtime, the variable will be using the secret value.

getting kubectl apply -f pipe1.yaml
Error from server (BadRequest): error when creating "pipe1.yaml": Pipe in version "v1" cannot be handled as a Pipe: strict decoding error: unknown field "mounts" getting this

Please, you need to carefully read and understand the solutions we have already proposed. This problem was previously discussed in this thread [1]. The configuration of annotations in Pipes is different than in Integrations.
[1] https://github.com/apache/camel-k/issues/5963#issuecomment-2506528249


Compiler benchmarks panic due to a segmentation fault

Describe the bug
Running the BenchmarkCompiler_compileMemoryCopy benchmarks panic due to a segmentation fault.
To Reproduce
$ go test -run '^$' -bench BenchmarkCompiler_compileMemoryCopy -benchmem -count 10 ./internal/engine/compiler

Expected behavior
The benchmark should run to completion.
Screenshots
unexpected fault address 0x140000f4000
fatal error: fault
[signal SIGBUS: bus error code=0x1 addr=0x140000f4000 pc=0x140000f4000]

goroutine 8 [running]:
runtime.throw({0x102e09f2b?, 0x174?})
	/usr/local/go/src/runtime/panic.go:1047 +0x40 fp=0x140000d3c70 sp=0x140000d3c40 pc=0x102bf3d80
runtime.sigpanic()
	/usr/local/go/src/runtime/signal_unix.go:834 +0x10c fp=0x140000d3cb0 sp=0x140000d3c70 pc=0x102c0a92c
github.com/tetratelabs/wazero/internal/engine/compiler.(*compilerEnv).execBench(0x1400000c090, 0x1400006cc80, {0x140000f4000, 0x174, 0x14000033d78?})
	/Users/achilleroussel/go/src/github.com/tetratelabs/wazero/internal/engine/compiler/compiler_bench_test.go:114 +0x6c fp=0x140000d3d00 sp=0x140000d3cc0 pc=0x102da9acc
github.com/tetratelabs/wazero/internal/engine/compiler.BenchmarkCompiler_compileMemoryCopy.func1(0x1400006cc80)
	/Users/achilleroussel/go/src/github.com/tetratelabs/wazero/internal/engine/compiler/compiler_bench_test.go:53 +0x594 fp=0x140000d3f10 sp=0x140000d3d00 pc=0x102da9224
testing.(*B).runN(0x1400006cc80, 0x1)
	/usr/local/go/src/testing/benchmark.go:193 +0x128 fp=0x140000d3f90 sp=0x140000d3f10 pc=0x102c82478
testing.(*B).run1.func1()
	/usr/local/go/src/testing/benchmark.go:233 +0x50 fp=0x140000d3fd0 sp=0x140000d3f90 pc=0x102c82a90
runtime.goexit()
	/usr/local/go/src/runtime/asm_arm64.s:1172 +0x4 fp=0x140000d3fd0 sp=0x140000d3fd0 pc=0x102c26e34
created by testing.(*B).run1
	/usr/local/go/src/testing/benchmark.go:226 +0x8c

Environment

Go version: 1.20
wazero Version: 4ceef7b24533725f2ef0d406c3baf633d99eca32 (main)
Host architecture: amd64, arm64
Runtime mode: compiler

Additional context
I tested on both linux/amd64 and darwin/arm64, both panicked in the same way.

I think this is because this bench hasn't been run on CI accidentally

looking into this. Essentially, the panic is due to codeSegment not being mmap'd; so this is enough:
func (j *compilerEnv) execBench(b *testing.B, codeSegment []byte) {
	executable := requireExecutable(codeSegment)
	b.StartTimer()

(unless you want to measure the mmap overhead too)
once this is done, there is another panic due to the change to how functionDefintitions are now loaded; looking into that too. Will open a PR.
as for running this in the CI, shall we add this to the Makefile?
bench:
	@go test -run=NONE -benchmem -bench=. ./internal/engine/compiler/...
	@go test -run=NONE -benchmem -bench=. ./internal/integration_test/bench/...
	@go test -benchmem -bench=. ./internal/integration_test/vs/... $(ensureCompilerFastest)

.PHONY: bench.check
bench.check:
	@go build ./internal/engine/compiler/...
	@go build ./internal/integration_test/bench/...
	# ... etc

we run make bench.check, not make bench in CI, I thought because the latter took too long. You can raise a PR to see how long it does, maybe it isn't as long as fuzzing..


Revert null candidate change

This reverts commit 18d65a5651e01a0185259d410b5b798b972edb31.
Fixes #118

Already added that to #123 :)


Update README file to fix inconsistent variable naming

pca is used for PublicClientApplication, and cca (which the other doc) used for ConfidentialClientApplication.

Can you update public to confidential on line 61?

CC @bgavrilMS, can you approve?


cvToValue throws exception for uint with more than 53 bits

Describe the bug
cvToJSON throws expection for uint or int with more than 53 bits. cvToJSON uses cvToValue
What version of Blockstack.js are you using?
transactions 1.3.3
Is the bug present in the Blockstack CLI, Gaia hub, Connect or Blockstack Browser?
no
To Reproduce
  it("should convert uintCV to hex", async () => {
    const value = cvToJSON(uintCV("1000000000000000"));
    expect(JSON.stringify(value)).equal('{"type":"uint","value":10000000000000000}');
  });

Expected behavior
Not clear how to handle this. For small numbers it makes sense to just return the number, for bigger numbers we need BN values.
Console log
 should convert uintCV to hex:
     Error: Number can only safely store up to 53 bits
      at assert (node_modules/bn.js/lib/bn.js:6:21)
      at BN.toNumber (node_modules/bn.js/lib/bn.js:519:7)
      at cvToValue (node_modules/@stacks/transactions/src/clarity/clarityValue.ts:108:24)
      at Object.cvToJSON (node_modules/@stacks/transactions/src/clarity/clarityValue.ts:144:51)
      at Context.<anonymous> (test/unit/pool-tool-utils.spec.ts:60:19)
      at processImmediate (internal/timers.js:461:21)

@friedger what are your thoughts? These could also be encoded a hex string.


chore(configure): fail if specified endpoints are not registered

tests still in the making

Ack

pending https://github.com/SpoonX/aurelia-api/pull/60

@RWOverdijk and that one

Tests are not happy about this PR

Besides the tests, the PR looks good.

as mentioned, pending aurelia-api endpoint property. supposed to fail till then

@doktordirk Let's see :D

@RWOverdijk
tested with api dev build https://travis-ci.org/doktordirk/aurelia-orm


Beautify

[ ] How completed challenges should look
[ ] How uncompleted challenges look
[ ] How errors look
[ ] App icons
[ ] Less website feel
[ ] How buttons look

Some of what exists right now that I'd be happy to change:

Updates:

:ship:


Debug cleanup

Cleanup and standardize debug statements.  Touches lots of files but no algorithm changes, all changes are inside DEBUG defines.  Uses dprint()/dcall()/dprintf() macros to try to eliminate "#ifdef DEBUG" where reasonable, standardizes on "debug" bool (changing "dump" to "debug" in places), and adds a C++11 mutex for all debug statements (replacing the OMP mutex in MkBuilder).  Most extensive changes are in MkBuilder due to consolidation of cut&paste print statements into print routines, changes to other files are all pretty straightforward.  Has been test compiled with (and without) -DDEBUG with icc and clang.  Since there are no algorithmic changes, did not run benchmarks.

@dan131riley How many places still use #ifdef DEBUG, and why would it not be reasonable to remove the ifdef?

On Apr 30, 2016, at 07:54, Kevin McDermott<EMAIL_ADDRESS>wrote:

@dan131riley How many places still use #ifdef DEBUG, and why would it not be reasonable to remove the ifdef?

@kmcdermo,
There's a bunch of places that have some kind of control structure
like an if or loop.  Where we have that kind of control structure,
it isn't enough for the print statements to disappear when DEBUG
isn't defined, we want the whole control structure to disappear (or
be completely certain that the compiler will notice it doesn't do
anything and toss it away).  Where we have cut&paste print statements
(e.g., in MkBuilder and fitttest) I've moved those into functions,
and elide the calls to those functions via dcall(), but it didn't seem
worth it for the things that aren't repeated.  I suppose there's other
ways those control structures could be made to disappear (maybe via
templates and lambdas), but again it didn't really seem worth the
effort just to get rid of the ifdef.
-dan

Hi @dan131riley,
sorry for the late feedback!
I have not looked in detail at the code, but let me make sure one feature I find useful is still possible.
While debugging specific parts of the code, I ofter define DEBUG only in specific files.
Is the new version still compatible with this idea?
By the way, even if the changes are not algorithmic, I would still prefer the benchmarking is run on PR that are more than 1 line change...
Thanks,
Giuseppe

@cerati,
Yes, you can turn on DEBUG only in specific files, the new change is that it has to defined before including Debug.h,
#define DEBUG // must be before include
#include <Debug.h>
However, that does turn the dprint/dcall/dprintf macros on for the entire file.  If you want printouts only for specific routines, you can set the global "bool debug" to false and create a local "bool debug = true;" for the scopes you want printouts enabled.
Supporting benchmarks are now in phiphi:/home/dsr/mictest-mt/2016-05-04-PR43
-dan

@dan131riley,
Maybe it would be good to edit Debug.h to include a comment or two about how to enable DEBUG in specific files and specific routines? Your instructions in this thread are simple enough and can be deduced, but for reference, it would be handy to have a quick summary in the code itself.

@dan131riley thanks for the explanation and for the plots.
I think the PR is good to go, let me know if you plan to add the instructions as requested by @srlantz before merging.

@cerati,
I've added comments, thanks for the suggesting @srlantz
-dan

On May 6, 2016, at 04:08, cerati<EMAIL_ADDRESS>wrote:
@dan131riley thanks for the explanation and for the plots.
I think the PR is good to go, let me know if you plan to add the instructions as requested by @srlantz before merging.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

for the record, benchmarking plots are at
http://uaf-6.t2.ucsd.edu/~cerati/mictest/2016-05-04-PR43/


Update to the latest version of SPIR-V Cross

fixes #1781
Updating to latest version of SPIR-V Cross, which fixes a bug with how access chains are handled in MSL.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Hold on--this also includes my changes to work around Metal allowing stores to storage resources after discard, which include two new options to SPIRV-Cross. I have a change which encompasses your change and also handles these options. I'll be submitting it shortly.

Hold on

Okay.

Closing as superseded by #1783.