Array property type?

When I add a property with an Array data type my callback returns err 'property value [[37.7, 23.9]] is of type class java.util.ArrayList is not supported (Error 500)'. Same result if it's inline or bound, ie
client.execute( 'g.addV( "name", name, "place", [37.7,23.9] )', {name:'Home'},..
client.execute( 'g.addV( "name", name, "place", place)', {name:'Home',place:[37.7,23.9]},..
Wondering if there is another syntax for arrays or am I missing some config or ?

There is no ArrayList type : http://s3.thinkaurelius.com/docs/titan/1.0.0/schema.html#_property_key_data_type
Maybe you should take a better look at http://s3.thinkaurelius.com/docs/titan/1.0.0/schema.html#property-cardinality

Ah got it, thx for the clarification.


Adding docker build for Alpine Linux

In my project I'm using Alpine docker java image.
Alpine is using libc instead of glibc, which gives these errors:

[22:07:23 WARN]: Failed to load native library:sqlite-3.15.1-fb339d95-503e-4709-89aa-514bc537aa5c-libsqlitejdbc.so. osinfo: Linux/x86_64
[22:07:23 WARN]: java.lang.UnsatisfiedLinkError: /tmp/sqlite-3.15.1-fb339d95-503e-4709-89aa-514bc537aa5c-libsqlitejdbc.so: Error relocating /tmp/sqlite-3.15.1-fb339d95-503e-4709-89aa-514bc537aa5c-libsqlitejdbc.so: __isnan: symbol not found
[22:07:23 WARN]: java.lang.UnsatisfiedLinkError: org.sqlite.core.NativeDB._open_utf8([BI)V
[22:07:23 WARN]: 	at org.sqlite.core.NativeDB._open_utf8(Native Method)
[22:07:23 WARN]: 	at org.sqlite.core.NativeDB._open(NativeDB.java:71)
[22:07:23 WARN]: 	at org.sqlite.core.DB.open(DB.java:174)
[22:07:23 WARN]: 	at org.sqlite.core.CoreConnection.open(CoreConnection.java:220)
[22:07:23 WARN]: 	at org.sqlite.core.CoreConnection.(CoreConnection.java:76)
[22:07:23 WARN]: 	at org.sqlite.jdbc3.JDBC3Connection.(JDBC3Connection.java:24)
[22:07:23 WARN]: 	at org.sqlite.jdbc4.JDBC4Connection.(JDBC4Connection.java:24)
[22:07:23 WARN]: 	at org.sqlite.SQLiteConnection.(SQLiteConnection.java:45)
[22:07:23 WARN]: 	at org.sqlite.JDBC.createConnection(JDBC.java:114)
[22:07:23 WARN]: 	at org.sqlite.JDBC.connect(JDBC.java:88)

In my use case I replaced the native in my jar with the one I compiled using the alpine docker image which fixed my error.

Thanks for the information. I didn't know Alpine is only using libc.
The reason I'm using CentOS5 is to build sqlite-jdbc by using an older version of glibc to support various versions of Linux, since binaries built with glibc is backward compatible.
It seems using https://github.com/sgerrand/alpine-pkg-glibc is another approach to run glibc-based sqlite-jdbc.
For now merging this PR has no harm to the current build. I'll merge this. Thanks.


fix: bug 2196 prevent multi-close on same session

:tada: This PR is included in version 0.322.7 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Uploading a folder got errors

When I upload a folder of smallish files (lots of screen shots) some of the files error.

2015-04-02 12:48:36 -0400 (18925) GenericFilesController::create rescued Ldp::HttpError
STATUS: 409 Could not remove triple containing predicate http://fedora.info/definitions/v4/repository#primaryType to node /prod/n5/83/xx/16/n583xx16c
Could not remove triple containing predicate http://fedora.info/definitions/v4/repository#created to node /prod/n5/83/xx/16/n583xx16c
Could not remove triple containing predicate http://fedora.info/definitions/v4/repository#lastModified to node /prod/n5/83/xx/16/n583xx16c
Could not remove triple containing predicate http://fedora.info/definitions/v4/repository#mixinTypes to node /prod/n5/83/xx/16/n583xx16c
Could not remove triple containing predicate http://fedora.info/definitions/v4/repository#mixinTypes to node /prod/n5/83/xx/16/n583xx16c
Could not remove triple containing predicate http://fedora.info/definitions/v4/repository#lastModifiedBy to node /prod/n5/83/xx/16/n583xx16c
Could not remove triple containing predicate http://fedora.info/definitions/v4/repository#uuid to node /prod/n5/83/xx/16/n583xx16c
Could not remove triple containing predicat...
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/ldp-0.2.3/lib/ldp/client/methods.rb:107:in block in check_for_errors' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/ldp-0.2.3/lib/ldp/client/methods.rb:105:in tap'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/ldp-0.2.3/lib/ldp/client/methods.rb:105:in check_for_errors' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/ldp-0.2.3/lib/ldp/client/methods.rb:88:in put'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/caching_connection.rb:24:in put' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/ldp-0.2.3/lib/ldp/resource.rb:72:in create'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/ldp-0.2.3/lib/ldp/resource/rdf_source.rb:19:in create' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/persistence.rb:151:in create_record'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/indexing.rb:40:in create_record' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/callbacks.rb:237:in block (2 levels) in create_record'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:113:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:113:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in block in halting' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:215:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:215:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in run_callbacks' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/callbacks.rb:237:in block in create_record'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:113:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:113:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:215:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:215:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:215:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in run_callbacks' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/callbacks.rb:236:in create_record'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/persistence.rb:144:in create_or_update' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/persistence.rb:27:in save'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/validations.rb:50:in save' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/persistence.rb:112:in create'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/sufia-models-6.0.0/app/models/batch.rb:28:in safe_create' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/sufia-models-6.0.0/app/models/batch.rb:16:in rescue in find_or_create'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/sufia-models-6.0.0/app/models/batch.rb:13:in find_or_create' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/sufia-6.0.0/app/controllers/concerns/sufia/files_controller_behavior.rb:215:in process_file'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/sufia-6.0.0/app/controllers/concerns/sufia/files_controller_behavior.rb:88:in create_from_upload' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/sufia-6.0.0/app/controllers/concerns/sufia/files_controller_behavior.rb:73:in create'
/opt/heracles/deploy/scholarsphere/releases/20150401151428/app/controllers/concerns/sufia/files_controller/browse_everything.rb:10:in create' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/sufia-6.0.0/app/controllers/concerns/sufia/files_controller/local_ingest_behavior.rb:9:in create'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal/implicit_render.rb:4:in send_action' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/abstract_controller/base.rb:189:in process_action'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal/rendering.rb:10:in process_action' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/abstract_controller/callbacks.rb:20:in block in process_action'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:113:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:113:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:282:in block (2 levels) in halting_and_conditional' /opt/heracles/deploy/scholarsphere/releases/20150401151428/app/controllers/generic_files_controller.rb:21:in notify_users_of_permission_changes'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:424:in block in make_lambda' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:281:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:281:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in block in halting_and_conditional' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in block in halting' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in block in halting' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in block in halting' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in block in halting' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in block in halting' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in block in halting' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in run_callbacks' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/abstract_controller/callbacks.rb:19:in process_action'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal/rescue.rb:29:in process_action' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal/instrumentation.rb:31:in block in process_action'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/notifications.rb:159:in block in instrument' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in instrument'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/notifications.rb:159:in instrument' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal/instrumentation.rb:30:in process_action'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal/params_wrapper.rb:250:in process_action' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activerecord-4.1.9/lib/active_record/railties/controller_runtime.rb:18:in process_action'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/abstract_controller/base.rb:136:in process' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionview-4.1.9/lib/action_view/rendering.rb:30:in process'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal.rb:196:in dispatch' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal/rack_delegation.rb:13:in dispatch'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_controller/metal.rb:232:in block in action' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:82:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:82:in dispatch' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:50:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:73:in block in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in each'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:685:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/engine.rb:514:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/railtie.rb:194:in public_send'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/railtie.rb:194:in method_missing' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:73:in block in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in each' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:685:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/rack/agent_hooks.rb:30:in traced_call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/rack/browser_monitoring.rb:23:in traced_call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/warden-1.2.3/lib/warden/manager.rb:35:in block in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/warden-1.2.3/lib/warden/manager.rb:34:in catch'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/warden-1.2.3/lib/warden/manager.rb:34:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/etag.rb:23:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:35:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/head.rb:11:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/params_parser.rb:27:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/flash.rb:254:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in context' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/cookies.rb:562:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activerecord-4.1.9/lib/active_record/query_cache.rb:36:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/active-fedora-9.0.6/lib/active_fedora/ldp_cache.rb:26:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/callbacks.rb:29:in block in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:82:in run_callbacks' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/callbacks.rb:27:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/remote_ip.rb:76:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/debug_exceptions.rb:17:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:38:in call_app'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:20:in block in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:68:in block in tagged'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:26:in tagged' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:68:in tagged'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:20:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/request_id.rb:21:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/cache/strategy/local_cache_middleware.rb:26:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/ssl.rb:24:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/engine.rb:514:in call' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/application.rb:144:in call'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/railtie.rb:194:in public_send' /opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/railties-4.1.9/lib/rails/railtie.rb:194:in method_missing'
/opt/heracles/deploy/scholarsphere/shared/bundle/ruby/2.1.0/gems/newrelic_rpm-<IP_ADDRESS>4/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in call' /opt/heracles/deploy/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/passenger-enterprise-server-5.0.4/lib/phusion_passenger/rack/thread_handler_extension.rb:69:in process_request'
/opt/heracles/deploy/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/passenger-enterprise-server-5.0.4/lib/phusion_passenger/request_handler/thread_handler.rb:140:in accept_and_process_next_request' /opt/heracles/deploy/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/passenger-enterprise-server-5.0.4/lib/phusion_passenger/request_handler/thread_handler.rb:95:in main_loop'
/opt/heracles/deploy/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/passenger-enterprise-server-5.0.4/lib/phusion_passenger/request_handler.rb:438:in block (3 levels) in start_threads' /opt/heracles/deploy/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/passenger-enterprise-server-5.0.4/lib/phusion_passenger/utils.rb:95:in block in create_thread_and_abort_on_exception'

If I had to hazard a guess the batch is getting created in multiple threads threads, and only one is succeeding.

This is repeatable in that each time some files fail

Wonder if this is related to: https://github.com/projecthydra/sufia/pull/961#issuecomment-79175090

Looking into this I can easily replicate the issue when I upload a Folder with many small files (many small files very likely makes the race condition more likely to happen).
The log shows several errors.

The first three errors are the "expected" ones. We tried to create a resource but another thread already created it. I believe this is what gets reported as ActiveFedora::IllegalOperation and that the code handles properly. The last error Ldp::HttpError is what is not handled and what caused the problem to the bubbled all the way up to the user.
At this point I don't know it is safe to ignore this Ldp::HttpError HTTP 409 by just adding an extra rescue clause to the code. Some how that does not seem right. It might be OK but I am not sure yet.

You can consistently reproduce with
batch_id = ActiveFedora::Noid::Service.new.mint
2.times do |i|
  fork { expect { Batch.find_or_create(batch_id) }.to_not raise_error }
end

@pgwillia thanks for the test case, this is nice!
It's interesting that this raises a different exception with a status of HTTP 500
<Ldp::HttpError: STATUS: 500 javax.jcr.ItemExistsException: A node definition that allows same name siblings could not be found for the node "{}6t" in workspace "default" (RSpec::Expectations::ExpectationNotMetError)
	at org.modeshape.jcr.JcrSession$JcrPreSave.processAfterLocking(JcrSession.java:2422)
	at org.modeshape.jcr.cache.document.WritableSessionCache.runPreSaveAfterLocking(WritableSessionCache.java:541)
	at org.modeshape.jcr.cache.document.WritableSessionCache.save(WritableSessionCache.java:614)
	at org.modeshape.jcr.JcrSession.save(JcrSession.java:1166)
	at org.fcrepo.http.api.FedoraLdp.createOrReplaceObjectRdf(FedoraLdp.java:301)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java...> with backtrace:

@hectorcorrea my mistake.  I thought I was getting the 409 error, but you're right this is new.

@hectorcorrea this consistantly gives me the 409 error.  I'm guessing sleep time may vary.
batch_id = ActiveFedora::Noid::Service.new.mint
        2.times do |i|
          fork { expect { Batch.find_or_create(batch_id) }.to_not raise_error }
          sleep 0.04
        end

Should we consider reverting https://github.com/projecthydra/sufia/commit/d852947ba50876177a96e3f2b86d0b6714b28269 ?

+1


Feature request: Payment integration

Is your feature request related to a problem? Please describe:
Most of the time when using bolt.new, I am working on a product that I would eventually like to monetize. There is currently no easy way to implement payments or premium features using bolt.new
Describe the solution you'd like:
Similar to the Supabase integration; Create a workflow for attaching Stripe, or any payment processor.
Describe alternatives you've considered:
I've considered and struggled with integrating payments after the fact, using another LLM.

big +1 for this request

agree. +1


Build consistent set of Solr/ES integration test corpora

Ref: #811
Currently, the Solr integration test script works only on Core18. The ES integration test script works on Robust04 and MS MARCO passage. Let's bring these into alignment - make both Solr/ES work on {Core18, Robust04, and MS MARCO passage}.

Originally planned to be part of v0.7.0 release, punting.

Closed by #1030


Add foreign key constraint on shipments.move_id [delivers #160992717]

Description
shipments.move_id wasn't setup to be a foreign key of move.id. This PR fixes that.
There should be no Shipment records on staging or production (HHG is disabled,) so this should be a safe and easy change.
Before adding the foreign key constraint, we attempt to drop any rows that don't adhere to the constraint. This is what this query does:
DELETE FROM
  shipments
WHERE NOT EXISTS
  (SELECT id FROM moves WHERE id = shipments.move_id);

This, however, will fail if the shipments that try to get deleted have ShipmentOffers, or other records that reference shipments:
    TABLE "shipment_offers" CONSTRAINT "awarded_shipments_shipment_id_fkey" FOREIGN KEY (shipment_id) REFERENCES shipments(id)
    TABLE "move_documents" CONSTRAINT "move_documents_shipment_id_fkey" FOREIGN KEY (shipment_id) REFERENCES shipments(id) ON DELETE RESTRICT
    TABLE "service_agents" CONSTRAINT "service_agents_shipment_id_fkey" FOREIGN KEY (shipment_id) REFERENCES shipments(id)
    TABLE "shipment_accessorials" CONSTRAINT "shipment_accessorials_shipment_id_fkey" FOREIGN KEY (shipment_id) REFERENCES shipments(id) ON DELETE RESTRICT

I am optimistically choosing not to write a complex SQL query to deal with all of these cases, given that:

we think the data shouldn't be corrupt
there shouldn't be any data on staging or production yet
writing the query that catches every case would be really complex, because it needs to remove every record in a chain of foreign keys.

If you think that's too optimistic, let me know why and I can expand the query.

@reggieriser The Circle build will fail and should notify us if the migration fails on staging or prod.

Can/should we audit the other relations in the database to make sure we have FKs in the appropriate places?  If we happen to have other cases of missing FKs, that's a problem that we should probably solve sooner rather than later.


How to deploy a JBoss EAP application on ARO

Deploy a Java application with Red Hat JBoss Enterprise Application Platform (JBoss EAP) on an Azure Red Hat OpenShift 4 cluster

@yersan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@yersan - Thanks for your pull request. A member of the content team will review it.

@sakthi-vetrivel - Could you review this new article? If it's approved, the PR review team can help move it to the private repo. Thanks!

@yersan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hello, @sakthi-vetrivel I have received no feedback yet about this PR, is there anything blocking this I can do on my side to continue moving it on? thanks

@leebeasley-v Can you take a look at this with the ARO PMs and if it looks good sign off on it?

#reassign @leebeasley-v

Closing this PR, since it was handled differently.


Add the default hosting services to IWebHost as directly accessible properties. IHostingEnvironment, ApplicationStopping, etc.

@davidfowl

@glennc FYI.

What's concerning about this change is the fact that our default services might grow over time.

We can either leave it as it is and expose extension method (ZOMG we need extension properties)
We can add a few properties that we think are core to the usage of IWebHost, like IHostingEnvironment and ApplicationStopping and leave the rest as services.
We can do nothing and require even the most basic properties to be resolved via the service provider.

I'm leaning towards 2.

@davidfowl Do we want this?  1 or 2?

Nope


gRPC stream stats

Title: Collect gRPC bidi stream stats
Description:
For long-running gRPC calls (bidi), stats and access logs are insufficient. It would be useful to have an option to count the number of messages in the streams in both directions, which can help in monitoring long lasting streams (e.g. xDS server). gRPC parameter messages appear to be length prefixed in DATA frames, so this should be possible without full unmarshalling.

Relevant discussion here

+1

Since there has been no movement on this issue for 9 months, perhaps a more incremental approach would work, instead of waiting for an over all design.
This istio-proxy PR by kuat, implements grpc message counts in a filter. I think it will be beneficial to have it in envoy.
@PiotrSikora @htuch

@qiwzhang

Yes, my project will like to have bidirectional message count in our telemetry report.  If it is implemented in Envoy, it will benefit my project.

@mandarjog certainly beneficial, but how will the output from this work in Envoy? Will it appear as an access log or something?

I'm open to suggestions about where to store the message counts and how to output them in base Envoy.

I don't have strong opinions, but it seems that since each individual message is the streamed equivalent of a request/response, that this should follow the access log pattern. Would like to hear from others.

access log can emit from and to message counts when an h2 request ends.

Like to add two points

since even reading DATA frame may incur cpu, so it is better to have a config in http_connection_manager to enable it. default is disabled.
add request_grpc_message_count and response_grpc_message_counts in stream_info.

or
write a small special http filter for doing this.  anybody wants this data, can just add this filter.
the two counters can be written to filterState in stream_info.

Is waiting for the request to end fine for the stream to end sufficient here? I guess there are two issues:

Providing gRPC level chunking of messages/requests.
Providing insight into the behavior of long lived streams.
For (2), if a stream lives for 24h, do we want to see what was going on during this period?

@htuch Regarding 2): gRPC client library tends to recommend short-lived requests since it load-balances on re-connect. That does not cover non-gRPClib clients, such as envoy.

@htuch stream connection time histograms at the very least would be extremely helpful. Those followed by messages I/O counts (and sizes if possible). We are implementing all of this in a Go middleware at the moment but having unified Envoy metrics would be ideal.


How to backup the scheduling?

Did not find where the schedulings in the database.

I could be wrong, I believe they removed the scheduling table and basically triggers and schedules became interchangeable.

+1 on what @jh3155 mentioned.
Table schedule keeps empty. Table Triggers includes all schedule info


add problem matcher for fmt and lint

setup-node uses github's problemMatcher to automatically add error message to TSC errors; it'd be great to have the same functionality, along with matchers for fmt and lint errors.

I've made this matcher for output of deno check but I have no idea how to enable it and test if it works:
{
  "problemMatcher": [
    {
      "owner": "deno-check",
      "pattern": [
        {
          "regexp": "(TS\\d+) \\[(ERROR)\\]: (.*)",
          "code": 1,
          "severity": 2,
          "message": 3
        },
        {
          "regexp": ".*"
        },
        {
          "regexp": ".*"
        },
        {
          "regexp": "at file://(.+):(\\d+):(\\d+)$",
          "file": 1,
          "line": 2,
          "column": 3
        }
      ]
    }
  ]
}


Actions failing while releasing binary

I've been trying to release my compiler and actions failing while searching variable INPUT_TARGET
The yaml file: https://github.com/osmon-lang/havo/blob/main/.github/workflows/release.yml
Run taiki-e/setup-cross-toolchain-action@v1
Run bash --noprofile --norc "${GITHUB_ACTION_PATH:?}/main.sh"
  bash --noprofile --norc "${GITHUB_ACTION_PATH:?}/main.sh"
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    INPUT_TARGET:
    INPUT_RUNNER:
/home/runner/work/_actions/taiki-e/setup-cross-toolchain-action/v1/main.sh: line 40: INPUT_TARGET: parameter null or not set
Error: Process completed with exit code 1.

You have to pass target: ${{ matrix.target }} to setup-cross-toolchain-action.
https://github.com/osmon-lang/havo/blob/371239b4110733ddd772e5d509344aff52f4531a/.github/workflows/release.yml#L39

thank you very much, worked!


Fix issue where build errors if checkout.js or checkout.scss don't exist

Recently added a shopifyPlus configuration item. If false, these files won't be looked at for the build. If true, these files are required. At the moment I'll consider this good.


error

[dbt -50000] unable to check for available memory

@zahramohebat27 when are you seeing this error?


Fix typo in lstm_ops.cc

Fix typo in line 441. Change "wci_tensor->dims()" to "wcf_tensor->dims()".
Fixes https://github.com/tensorflow/tensorflow/issues/60114.

已收到，我会尽快回复你！
                     ——刘劲字


Add token for loading card

Right now you can't load private cards w/o background authentication since token is not exposed.

I think this is already supported no? https://github.com/nateraw/modelcards/blob/main/modelcards/cards.py#L85 had a tokenparam

Ah yea this was closed by #51. Forgot to link this issue there.


Enhancement: Add configuration for Dependabot

This PR

[x] adds the configuration for Dependabot from next to master

Follows #2078.
💁♂ I think the configuration needs to be on the default branch.

Thank you, @pimjansen!


Runtime genesis ledger not being used

I created a daemon.json with 300K accounts, and used runtime_genesis_ledger to write a genesis ledger specified by --genesis-dir. I verified that directory was populated with a couple of tar.gz files.
I then ran the daemon as a seed using --genesis-ledger-dir, the directory containing those tar.gz files.
Running client status, the status shows only 18 accounts. Exporting the staged ledger also contains 18 accounts.
I had earlier run the daemon specifying the same daemon.json as a --config-file, and saw the 300k accounts in the client status and when exporting the staged ledger.
The executables were built from compatible using testnet_postake_medium_curves.

The config file is here: https://stecksoft.2038.io/daemon-300k.json
(That's a server where I drop files, the file will be deleted eventually.)

Passing the original config file to the daemon solves the problem.


website down

www.videosegmentation.com is down

Yeah we had to take down the site as users were using it way more than we could support.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Fábio Ferreira<EMAIL_ADDRESS>Sent: Monday, October 29, 2018 4:55:39 PM
To: videosegmentation/video_segment
Cc: Subscribed
Subject: [videosegmentation/video_segment] website down (#22)
www.videosegmentation.comhttp://www.videosegmentation.com is down
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/videosegmentation/video_segment/issues/22, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA9SmYvq_EeLfq7qARbWInAAbyfp6XClks5up5V7gaJpZM4YA6y8.

ah I see, thanks for the reply. Maybe you could manage the workload with a queue while maintaining the same amount of resources.


[Bug]: Search functionality not working correctly on react.dev in Safari on iOS real device (iPhone 12 Pro)

Summary
The current behavior
Search functionality does not work correctly on iOS real device (iPhone 12 Pro).
https://github.com/reactjs/react.dev/assets/57572988/f50ff514-d84b-4e8c-b067-628eedd2d762
Since search functionality is currently working as expected on macOS, both in Chrome and Safari, the issue might be in implementation of Algolia InstantSearch iOS:
https://github.com/reactjs/react.dev/assets/57572988/44ddea01-cd10-4323-bcdb-aec1788da64d
An issue has been opened in the react repo as well
The expected behavior
Search functionality is working as expected on macOS, both in Chrome and Safari. Should work similarly on iOS real device:
macOs Chrome
https://github.com/reactjs/react.dev/assets/57572988/41c9cd76-3ac8-4820-9917-52141d68c8ed
macOS Safari
https://github.com/reactjs/react.dev/assets/57572988/4daf9a68-2671-446c-a9c3-8a39bfefc8e5
Page
https://react.dev
Details
Steps To Reproduce

Open react.dev in Safari on iPhone (real device)
Tap search icon: note that search function is working as intended
Scroll down to "Write components with code and markup" section
Tap search icon: note that action doesn't open search
Scroll down again and tap the search icon several times:  note that action doesn't open search
Repeat step 5: note that eventually screen freezes

The iOS real device that this behavior was recorded on is using the current iOS version:

Duplicate of #6693

@MeetYourCreator you opened this issue twice on this repo.

HI @pwbriggs. Sorry about that. I didn't know which one of the duplicates for the issue you preferred that I close. Please let me know and I'll close that duplicate out. Thanks


Add eventbridge replay

Added the needed endpoints for the replay functionality. The state is quite often faked, because the real replay had to be done asynchron, which I didn't want to implement. I also implemented the possibility to send events to a Log Group target.

Codecov Report

Merging #3735 (dff4b3d) into master (6da8dc0) will increase coverage by 0.00%.
The diff coverage is 95.85%.

@@           Coverage Diff            @@
##           master    #3735    +/-   ##
========================================
  Coverage   94.78%   94.79%
========================================
  Files         437      437
  Lines       47905    48071   +166
========================================
+ Hits        45408    45569   +161
- Misses       2497     2502     +5

Flag
Coverage Δ

servertests
56.02% <20.20%> (-0.12%)
:arrow_down:

unittests
94.65% <95.85%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

moto/events/models.py
93.30% <95.18%> (+0.48%)
:arrow_up:

moto/events/exceptions.py
100.00% <100.00%> (ø)

moto/events/responses.py
88.98% <100.00%> (+1.18%)
:arrow_up:

moto/iam/models.py
95.27% <0.00%> (+0.14%)
:arrow_up:

Continue to review full report at Codecov.

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

This is now part of moto >= 2.0.1.dev295


sql injection vulnerability with content provider

I made my TV app searchable but Google told me that the app has an SQL Injection vulnerability and directed me to this guide to fix it (https://support.google.com/faqs/answer/7668308).
I have tried to select "exported = false" but my app no longer appears in the TV search with this solution. Same result using "android:protectionLevel="signature"".
I have tried this solution:
In Manifest I have setted
<provider             android:name=".xx.xxx.contentProvider.Provider"             android:authorities="${packageName}"             android:exported="true">             <path-permission                 android:pathPrefix="/search"                 android:readPermission="android.permission.GLOBAL_SEARCH" />
And in Provider I have setted:
 static {         sVideosContainingQueryBuilder = new SQLiteQueryBuilder();         sVideosContainingQueryBuilder.setStrict(true);         sVideosContainingQueryBuilder.setProjectionMap(sColumnMap);
With this solution I have tested the app with drozer but, if the app is builded in debug mode, drozer show me:
Injection in Projection:   No vulnerabilities found. Injection in Selection:   No vulnerabilities found.
but when the app is builded in realese i have:
`Injection in Projection:
content://android.media.tv/program/
content://android.media.tv/preview_program/
content://android.media.tv/program
content://android.media.tv/preview_program
content://android.media.tv/recorded_program
content://android.media.tv/recorded_program/
content://android.media.tv/channel
content://android.media.tv/watch_next_program
content://android.media.tv/channel/
content://android.media.tv/watch_next_program/
Injection in Selection:
No vulnerabilities found.`
Do you have any suggestions?
Thanks

I have also tried to scan my app with drozer using the command "run scanner.provider.finduris -a com.org.testapp"
This is the result:

dz> run scanner.provider.finduris -a xx.xxx.myapp
Scanning xx.xxx.myapp...
Unable to Query  content://com.facebook.orca.provider.MessengerPlatformProvider/versions
Unable to Query  content://xx.xxx.myapp.firebaseinitprovider/
Unable to Query  content:// Uri/
Unable to Query  content://xx.xxx.playxxx
Unable to Query  content:// Uri
Unable to Query  content://com.google.android.gms.chimera
Unable to Query  content:// or file:// uri
Able to Query    content://android.media.tv/channel
Unable to Query  content://com.facebook.app.FacebookContentProvider/
Able to Query    content://android.media.tv/channel/
Unable to Query  content://xx.xxx.myapp.FacebookInitProvider
Able to Query    content://android.media.tv/preview_program/
Able to Query    content://android.media.tv/program
Unable to Query  content:// or file:// uri/
Unable to Query  content://com.google.android.gms.chimera/
Able to Query    content://android.media.tv/recorded_program/
Unable to Query  content://com.facebook.katana.provider.AttributionIdProvider/
Unable to Query  content://xx.xxx.myapp.firebaseinitprovider
Unable to Query  content://xx.xxx.myapp.MarketingInitProvider
Able to Query    content://android.media.tv/watch_next_program/
Unable to Query  content://xx.xxx.playxxx/
Unable to Query  content://xx.xxx.myapp.crashlyticsinitprovider/
Able to Query    content://android.media.tv/program/
Unable to Query  content://com.facebook.app.FacebookContentProvider
Able to Query    content://android.media.tv/preview_program
Able to Query    content://android.media.tv/recorded_program
Unable to Query  content://com.facebook.wakizashi.provider.AttributionIdProvider/
Unable to Query  content://xx.xxx.myapp.FacebookInitProvider/
Unable to Query  content://com.facebook.katana.provider.AttributionIdProvider
Unable to Query  content://com.facebook.wakizashi.provider.AttributionIdProvider
Unable to Query  content://com.facebook.orca.provider.MessengerPlatformProvider/versions/
Unable to Query  content://xx.xxx.myapp.MarketingInitProvider/
Able to Query    content://android.media.tv/watch_next_program
Unable to Query  content://xx.xxx.myapp.crashlyticsinitprovider

Accessible content URIs:
content://android.media.tv/program/
content://android.media.tv/preview_program/
content://android.media.tv/program
content://android.media.tv/preview_program
content://android.media.tv/recorded_program
content://android.media.tv/recorded_program/
content://android.media.tv/channel
content://android.media.tv/watch_next_program
content://android.media.tv/channel/
content://android.media.tv/watch_next_program/


Examine what CSS modules are used by a service

Bash command to query a services CSS file looking for the modules used from GOV.UK Frontend:
curl -s [URL] | grep -Eo '\.[a-z]+[a-z0-9_-]*' | grep "govuk" | grep -Ev "__|--" | sort | uniq | sed s/.// > output.txt

Leaving here for posterity.


Typescript implementation of jsonapi-server

I've found your project and have begun to play a little with it.
We are certainly going to use it on our projects.
however, we are using Typescript and we are wondering if you are willing to make a typescript version of it or just the needed typings for a good integration.
Thanks in advance for your responses (and sorry if my english isn't accurate)

We don't have any plans to re-implement jsonapi-server in TypeScript and it would not make sense to maintain both a JavaScript and a TypeScript version.
Maintaining the typings for ease of integration with TypeScript sounds like a good idea, and you're welcome to contribute a PR with those which would certainly consider for merging.


#3 Automated deploy to docker hub

Actually, for puppeteer-service we do docker releases in reversed way - and let docker hub do the build by itself:
https://docs.docker.com/docker-hub/builds/
Personally I think it's better 😅

Actually, for puppeteer-service we do docker releases in reversed way - and let docker hub do the build by itself:
https://docs.docker.com/docker-hub/builds/
Personally I think it's better  and it keeps repository a bit more clean

Right, I didn't know it was possible. I removed the file responsible for pushing images. Either way I don't have permissions to set it up on dockerhub side so I will just leave the task for someone else.
Current code creates releases on GitHub and tags proper commits. Is it possible to build images from tagged commits?

Right, I didn't know it was possible. I removed the file responsible for pushing images. Either way I don't have permissions to set it up on dockerhub side so I will just leave the task for someone else.
Current code creates releases on GitHub and tags proper commits. Is it possible to build images from tagged commits?

Yep, it's how it works on puppeteer.
I will setup it when everything is merged :)


With "sort" command, "-s" returns off-by-one shortened list

With the search or list command, -s returns the expected number of envelopes.
With the sort command, the returned set of envelopes is one fewer than requested by -s

I confirm the bug. The pagination is not handled well for the sort command. Thank you!

Himalaya is slowly migrating away from GitHub. The new bug tracker is now on sourcehut. I move your issue here [#30]. You can subscribe to the thread by sending an email at<EMAIL_ADDRESS>(and unsubscribe to it by sending an email at ~soywod/himalaya/30/unsubscribe@todo.sr.ht).


Manage policies UI is broken

Trying to add/remove a policy is broken for all entities.

=>

It seems that the edit variable doesn't get populated in the second call.
Server logs:
http://pastebin.com/ihvYyAPR

@himdel @martinpovolny ^

@alongoldboim can you verify https://github.com/ManageIQ/manageiq/pull/11105 fixes the issue please?

@himdel it doesn't.

@alongoldboim  I'm almost sure it does :) (you do have to restart the server and load the screen before that though)
But if not, can you tell me how to reproduce please? There are no step by step instructions and no mention of the url here..

@himdel I edited my post 10 sec after :), it worked.

Aah, did not notice that, thanks! :) OK, even better then :)


Contact role settings do not display correctly. bug #2257.

Critical Changes
Changes
Issues Closed
Fixes #2257

@jjbennett This trivial change fixes all of the uses in NPSP Settings of our multiselect picklist component, that were not using RecordType Id's, and not specifying the new attribute strValuesOverride.  I cannot figure out why the use of BLANKVALUE(strValuesOverride...) wasn't working as expected, but changing the logic to use IF() solve the issue.
In addition, since those callers who are providing strValuesOverride are not passing stgLabelNone if they have no data, I've made the markup also do this in the component if strValuesOverride isn't provided, and strValues is empty.  This is now consistent for all use cases, and approved by Mary.


Error: No code found during the build -- for a project using C.

I’m not quire sure why the action is unable to find any code or binaries to analyze.
Here's the run: https://github.com/smallstep/pkcs11-proxy/actions/runs/3212053239/jobs/5250635125. I'm using my own command to cmake and make the binary (as well as the .so files). I've SSH-ed into the build to validate that the binary and .so files are present inside the current tree structure. Not sure what else CodeQL might be expecting. Any guidance would be appreciated. Thanks!

Thanks for your question. It seems you're running cmake and make as root (using sudo). This means CodeQL will not be able to pick up on the underlying compiler invocations, as they are executed by a different user.
Looking at your workflow, I expect it should be sufficient to replace:
    - name: Build
      run: |
        sudo apt-get update
        sudo apt-get install -y bash curl git-core build-essential pkg-config cmake libssl-dev libseccomp-dev
        sudo cmake .
        sudo make
        sudo make install
        mkdir bin
        sudo cp /usr/local/lib/libpkcs11-proxy.so.0.1 ./bin/
        sudo cp /usr/local/lib/libpkcs11-proxy.so.0 ./bin/
        sudo cp /usr/local/lib/libpkcs11-proxy.so ./bin/
        sudo cp /usr/local/bin/pkcs11-daemon ./bin/
        sudo chown -R runner:docker ./bin
    - name: Setup tmate session
      uses: mxschmitt/action-tmate@v3

by:
    - name: Build
      run: |
        sudo apt-get update
        sudo apt-get install -y bash curl git-core build-essential pkg-config cmake libssl-dev libseccomp-dev
        cmake .
        make

Yep, that was it. Thanks a ton for the help!


Pool creation bug

Describe the bug
Exact details unknown, seems to be something to do with using WETH as a token on Arbitrum. See this discord message: https://discord.com/channels/638460494168064021/638460494168064025/1048363607777345536
To Reproduce
Steps to reproduce the behavior:
TBD
Expected behavior
A clear and concise description of what you expected to happen.

@alter-eggo what was the result of investigating this?

@garethfuller none, I couldn't reproduce it


Update README.vi-VN.md

Hi, because of the new vi-VN translation from Crowdin after new tag 0.11.0 I haven't published yet, I force-pushed main branch. Please fork and pull request again.


Get pre-processed file

On the command line, clang -E test.cpp will show you the preprocessed output.
> # 1 "prog.c"
> # 1 "<built-in>" 1
> # 1 "<built-in>" 3
> # 157 "<built-in>" 3
> # 1 "<command line>" 1
> # 1 "<built-in>" 2
> # 1 "prog.c" 2
> int main (void)
> {
> int a;
> }

Is there a way to get pre-processed with ClangSharp?

Not currently, but it wouldn't be hard to configure by extending the CursorWriter class in the P/Invoke Binding Generator.

Thanks.


Multiple progress bars

Fixes #208.

(this white rectangle is my terminal cursor).

Oh, that's dope! One tiny suggestion: Can we just show a progress bar w/o ios or android if we are running in a single platform mode?

@grabbou
I made it more generic to handle future platforms.
Also, I'd suggest to keep platform label is there is only one build happening, as it can be a sanity-check in case You selected platform You did not want to (so You get feedback immediately).

Thanks!

Also, I'd suggest to keep platform label is there is only one build happening, as it can be a sanity-check in case You selected platform You did not want to (so You get feedback immediately).

Well, we already provide quite explicit interface informing about the platform (and eventually want to default to all in the future)

Fair enough. Going to do those changes next week, as few workarounds will be necessary.

Let's get this merged soon to avoid more merge conflicts :)

Let's merge this, and create an issue to hide platform name if in single-build mode


Release 2024-01-10

:tada: This PR is included in version 1.25.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


different user promts optimization

Unber Linux,User A runs eg: php bin/start start => ok
Switch to user B and enter the command php bin/start status, and it will dispaly:
Workerman[bin/start] status
Workerman[bin/start] not run

In Fact, the program is running, but user B sends a signal and user A cannot receieve it,user B needs to use sudo to respond normally.
When sudo is not use, Suggest to optimize the output
For example:
Workerman[bin/start] is running
Workerman[bin/start] but does not have permission, You need to use the `sudo` command

Different user can not visit the same process, and you should not use different user to do that.

Linux has strict access control. You can't use different users to access the same process.


Update hello-neon README.md to call out release build

This is mainly to clarify https://github.com/googlesamples/android-ndk/issues/474 to use release ( signed APK ) when comparing performance numbers.

Only readme file change, merging it in.


Error while finetuning stable diffusion on Pokemon dataset in google colab

System Info
I am trying to finetune stable diffusion model as provided in the below tutorial on google colabl
https://huggingface.co/docs/diffusers/v0.9.0/en/training/text2image

However while running !accelerate launch train_text_to_image.py in google colab I am encountering below error
2023-05-22 10:11:35.176343: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
[10:11:36] WARNING  The following values were not passed to

I have tried installing latest version of TensorRT and still face the same error

I am attaching accelerate env below.
- `Accelerate` version: 0.19.0
- Platform: Linux-5.15.107+-x86_64-with-glibc2.31
- Python version: 3.10.11
- Numpy version: 1.22.4
- PyTorch version (GPU?): 2.0.1+cu118 (True)
- System RAM: 12.68 GB
- GPU type: Tesla T4
- `Accelerate` default config:
	Not found

Can someone help me with how to finetune the above script on Pokemon dataset on google colab environment

Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction

Follow the steps given in : https://huggingface.co/docs/diffusers/training/text2image

Expected behavior
We should be able to finetune model

You should safely be able to ignore this. Colab comes pre-installed with TF but we do not use it at all

@muellerzr  I was trying to fine tune the model but it was not happening , can you please provide some sample code on how to fine tune it in colab's environment .
Thanks

@sayedathar11 can you please post the full trace?

Hi @muellerzr wanted to ask any updates on this ?


Maintenance window

Can we please implement a maintenance window, like patch Tuesday or something? My hotspot has restarted 3-4 times in the last three days because of updates, causing all kinds of problems.
Thanks

No, that isn't realistic this early in the Helium days. We need to be able to iterate quickly and both implement our own fixes and the upstream Helium fixes quickly. Restarts should really not cause any issues however.

https://discord.gg/PZ6BrqF6


Fix: helpers reference implementation block was not matching the code

So it made me lose some time today, hope this will prevent others from doing the same.

Commit 8bb40bc was intended.


Flutter 1.20 compatibility

After running flutter upgrade, my build breaks because fluttter_form_builder 3.12.3 depends on flutter_chips_input 1.8.3 which is not compatible for Flutter 1.20.
What is the prescribed solution?  Will there be an official 1.9.0 release?

Just released a few minutes ago.

And there it is!  Thank you!


fix return of replacement items

fixes #4

Looks good. Will merge in a few days unless there are objections.


[AMI/GCP/Azure] - Align images name

Today we have different naming convention for our images
In AMI:
For building AMI via Jenkins in master branch we have:  scylla_2022-05-01T14-26-06Z-build-312-x86_64
For building AMI locally we are getting: scylla_2022-05-01T12-44-47Z-build-2022-05-01T12-44-46-
Both image name doesn't make any sense, instead we need to check the tags to get more information
In GCP:
For building GCP via Jenkins in master branch we have: scylla-5-1-dev-0-20220429-7f1e368e92ce-1-build-312
In Azure:
For building Azure image via Jenkins in master branch: ScyllaDB-5.1.dev-0.20220427.f6ce7891a590-1-build-144
For building images for debug (same branch): debug-image-ScyllaDB-4.7.dev-0.20211119.f3d5b2b2b0-1-build-189
Let's align all images name

Suggested convention <product>_<version>_<dev/debug>_<arch>, ex.

scylla_5.1-dev.x86
scylla_2022.1-dev.aarch64
scylla_5.1-debug.x86 (we can use the debug-image- prefix for hydra backward compatibility)

All other information (date, build, commit, etc.) will be added as tags

scylla_2022.1-dev.aarch64

shouldn't it be scylla_enterprise_2022.1-dev.aarch64?

scylla_2022.1-dev.aarch64

shouldn't it be scylla_enterprise_2022.1-dev.aarch64?

yes


Creates the Speedometer Widget UI and Funtionality

Summary
This PR creates the Speedometer gauge with it's functionalities as the first widget necessary to completely address the second step of #1  . This widget is expected to be able to subscribe to a specific topic and select a field from that topic to show on the gauge UI. The following features are added to this widget:

Show the value of the specified topic field as a speedometer.
Modify the minimum and maximum value of the gauge
Modify the units of the speedometer

Run the widget
In order to test out this widget,  follow this next steps:

Compile the package and source the workspace:

cd <workspace-with-the-package>
clear && colcon build --packages-select rqt_gauges_2
source install/setup.bash

Here you can choose to run it on RQT or as a Standalone node:
RQT

Run the RQT plugin UI:

rqt

Go to the following path on the menu tab: Plugins -> Visualization -> Speedometer

Standalone Plugin

Run the standalone node:

ros2 run rqt_gauges_2 rqt_gauges_2

Test it out
In order to test out, you can do the following:

Play by changing the minimum limit, maximum limit and units of the gauge with the boxes at the bottom of the widget.
Subscribe to topics and watch the gauge move:

Create a publisher other terminals and run:

ros2 topic pub /test_topic_2 geometry_msgs/msg/Twist "linear:
  x: 70.0
  y: 0.0
  z: 0.0
angular:
  x: 0.0
  y: 0.0
  z: 0.0"

Create another publisher on other terminal and run:

ros2 topic pub /test_topic std_msgs/msg/Int16 "data: 10"

Go to the plugin and start filling the text box on top of it until you reach the specific field you want for a specific topic (there is a topic autocompleter in order to avoid any name issues):

After selecting the topic and completing the required field, hit the Subscribe button to the right.
Take a look at the gauge move and play around  :grin:

PS
So sorry for the long PR :sob:

Discovery of topics

I opened the speedometer.
Then, I published some test data in some topics.
I can't select that topic in the speedometer plugin. It is like the discovery of topics happens only up to when the speedometer was opened. This isn't convenient.

Setting min and max value
It is weird to see the highest value not matching the max value that the user has entered:

@francocipollone

Discovery of topics

I opened the speedometer.
Then, I published some test data in some topics.
I can't select that topic in the speedometer plugin. It is like the discovery of topics happens only up to when the speedometer was opened. This isn't convenient.

I was aware of this behavior, I have a couple of options I wanted to discuss on how to solve this:

Create a refresh button on the widget that basically discovers all the topics at that moment.
The object that I'm using to show the topics is a QLineEdit, we could use their signals to trigger the update function of the widget and that way we can have a discovery state "on demand". However, from the signals that object have, there isn't a clear choice since the signals that could be useful would impose a restriction to the user such as "Write/delete something in order to update the topics". I also think this isn't convenient.

Let me know what you think about this issue.

Setting min and max value
It is weird to see the highest value not matching the max value that the user has entered:

This actually seems weird to me, I tried exactly that and did't get any problems. Did you clicked Enter after writing down the number? I think I can modify it to better use the value change signal from the object, the question is just to appease my curiosity.

The object that I'm using to show the topics is a QLineEdit, we could use their signals to trigger the update function of the widget and that way we can have a discovery state "on demand". However, from the signals that object have, there isn't a clear choice since the signals that could be useful would impose a restriction to the user such as "Write/delete something in order to update the topics". I also think this isn't convenient.

I think that using a signal like FocusIn makes sense, in way that it only updates the list when you are working on that field. It sounds like the best option as we want it to be updated and we don't want to have a timer for that. (Maybe plotter gives us a hint.)

Edit: I just recalled this happens due to the segmentation of the whole circle into a semicircle. Due to the calculations made to readjust the circle and the amount of scale markers, the final value is not exactly at the end of the semicircle, unless the maximum number is a multiple of 90. I can take a look at this and see how to solve it. However, this doesn't mean that the big number in the middle of the widget won't be able to get to the specified maximum value.

Makes sense. It is ok then. I will fill up a ticket later on just to make it a know issue. There is no necessity on tackling this, it is just an enhacement.

Let me know when it is ready for another pass. (In case you are missing some cycles to work on this, let me know and I will try to continue)


False negatives on PYI rules

Ruff reports no errors on the following codes snippet with the command ruff --select=PYI, whereas flake8-pyi reports quite a few ;)
import mypy_extensions
import typing
import typing_extensions

from typing import TypedDict, TypeVarTuple, Union
from typing_extensions import TypeAlias

DoublyNestedAlias: TypeAlias = Union[type[str], type[float] | type[bytes]]

class _UnusedTypedDict3(mypy_extensions.TypedDict):
    baz: dict[str, str]

_UnusedTypedDict4 = TypedDict("_UnusedTypedDict4", {"-": int, "def": str})
_UnusedTypedDict5 = typing_extensions.TypedDict("_UnusedTypedDict5", {"foo": bytes, "bar": str})
_P = typing_extensions.ParamSpec("_P")
_Ts = TypeVarTuple("_Ts")

type lowercase_alias = str | int
type _LooksLikeATypeVarT = str | int
type _Unused = str | int

def badfunc1(*args: typing.NoReturn) -> None: ...
def badfunc2(**kwargs: typing_extensions.NoReturn) -> None: ...

If I run flake8 --extend-ignore=Y023,Y031,Y037 on the same file (with the latest version of the flake8-pyi installed), it reports the following violations:
sample.pyi:8:49: Y055 Multiple "type[Foo]" members in a union. Combine them into one, e.g. "type[float | bytes]".
sample.pyi:10:1: Y049 TypedDict "_UnusedTypedDict3" is not used
sample.pyi:13:1: Y049 TypedDict "_UnusedTypedDict4" is not used
sample.pyi:14:1: Y049 TypedDict "_UnusedTypedDict5" is not used
sample.pyi:15:1: Y018 ParamSpec "_P" is not used
sample.pyi:16:1: Y018 TypeVarTuple "_Ts" is not used
sample.pyi:18:1: Y042 Type aliases should use the CamelCase naming convention
sample.pyi:19:1: Y043 Bad name for a type alias (the "T" suffix implies a TypeVar)
sample.pyi:19:1: Y047 Type alias "_LooksLikeATypeVarT" is not used
sample.pyi:20:1: Y047 Type alias "_Unused" is not used
sample.pyi:22:15: Y050 Use "typing_extensions.Never" instead of "NoReturn" for argument annotations
sample.pyi:23:16: Y050 Use "typing_extensions.Never" instead of "NoReturn" for argument annotations

(Some of these are due to recent changes we've made in flake8-pyi -- e.g. the violations on lines 18-20 are because we recently extended our type alias rules to cover type aliases created using PEP-695 type statements.)

Thank you!

All but one of these are now ticked off 🥳
I'm closing this now, since the last one is sort-of in a category by itself, and I'm not sure we'd want to fix it. The obvious way to teach ruff to recognize mypy_extensions.TypedDict would be to have ruff recognize mypy_extensions as a "typing module" in the same way as typing or typing_extensions. But unlike typing and typing_extensions, mypy_extensions is, well, mypy-specific -- other type checkers accord it no special treatment. mypy_extensions.TypedDict specifically is also deprecated in favour of typing(_extensions).TypedDict (though there's yet to be a release that includes the DeprecationWarning


docs: update chrome web store link

close #348

@hakadao don't forget to update the link in description

@hakadao don't forget to update the link in description

thank your for your reminder


String data becomes binary after "convert_dictionary_to_ros_message"

In python3

Where M = std_msgs.msg, MC = rospy_message_converter.message_converter

This is the correct behavior. ROS message fields of type "string" correspond to the Python3 type "bytes", see here:
http://wiki.ros.org/msg#Fields
One peculiarity is that you can put anything into a message field when you create it, e.g.:
ms1 = std_msgs.msg.String("Hello")
ms2 = std_msgs.msg.String(3)
ms3 = std_msgs.msg.String(b"Hello")

All of this will work, but when you try to serialize ms1 or ms2 (such as when you try to publish it), an exception will be thrown, because a ROS string field cannot hold a python str or int. Publishing ms3 will succeed.


A11y_AzureDataStudioSQLMigration_MigratetoAzureSQL_MigrationAssessment_Keyboard:Typing in search form field and pressing enter key closes the migration assessment screen and no search results are displayed.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags: #A11yMAS;#A11yTCS;#A11ySev2;#SH_AZUREDATASTUDIOSQLMigration_June2021;#SQL Azure Data Studio;#Win10;#FTP;#DesktopApp;#WCAG4.2.2;#AINotInScope;#Keyboard
Environment Details:
Application Name: SQL Azure Data Studio
Windows Version: Win10
Repro Steps:

Launch the application-Azure Data Studio-Insiders and install extension Azure SQL Migration.
Connect to any sql server.
Tab till Azure SQL migration Tab and press enter.
Tab till Migrate to azure sql and press enter.
Add azure account and tab till next button and press enter.
Select SQL server on azure virtual machine radio button and tab till view/select button and press enter.
Tab till Search form field.

Actual:
Typing in search form field and pressing enter key closes the migration assessment screen and no search results are displayed.
Expected:
When pressing enter key the results should be displayed or if there are no matching results a status message should be displayed as no results found.
User Impact:
Keyboard only users will not be able to search anything in the screen.

![15855_A11y_Issue fixed](https://user-images.githubusercontent.com/100270074/218442195-ba1f244a-7b17-499c-8907-408cafaea578.jpg)
Verified this issue in the below environment.
App name: Azure data Studio Insider.
Version: 1.42.0-insider (user setup)
Commit: 99a924dbcdce7bbaa0ab78b19f84e83035e54651
Date: 2023-02-08T06:58:10.882Z
VS Code: 1.67.0
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22623
GitHub Tags:#Closed;


Remove blanket "supported" language.

Signed-off-by: Peter Salvatore<EMAIL_ADDRESS>

@psftw Thanks for the quick response Peter. LGTM
ping @docker/docs-owners

LGTM. Thanks!

ping @moxiegirl (if you were waiting for this to publish)

thanks @thaJeztah  I was!


fix for index out of range

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # index out of range in oneDNN verbose log tutorial
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[X ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Sample Migration (Moving sample from old repository after completing checklist established)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[X ] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode

Checklist for Moving samples:
Links and Details can be found in the samples WG Teams Files.

[ ] Review sample design with domain reviewers https://github.com/oneapi-src/oneAPI-samples/wiki/Reviewers-and-Domain-Experts
[ ] Implement coding guidelines and ensure code quality.
[ ] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[ ] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com
[ ] Adhere to readme template
[ ] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[ ] Enforce format via clang-format config file
[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth or Joe Oster. (GitHub User: JoeOster)
[ ] Tested using Dev Cloud when applicable
[ ] Implement fixes for ONSAM Jiras
[ ] If you have new dependencies/binaries, inform Samples Project Manager Swapna R Dontharaju (@srdontha) or @JoeOster

error handling for the outliner of the oneDNN log file.

addressed the runtime issues.
all notebooks are passed in the PV machine.


Add TLS configuration to tasklist ingress

For whatever reason, tasklist does not allow you to configure TLS on the ingress like the rest of the camunda components.  These changes address the issue by simply following the same pattern as all of the other camunda ingress templates.

@conadrisca it looks great now :clap:
Just one thing to merge, please rebase your branch against the repo's latest main branch (as you see your changes are mixed with other changes).

I just did the rebase to include this change in the new version I'm about to release.


testing: run: do not crash when the pull request data cannot be fetched

This breaks the rehearsals from openshift/release.

/lgtm

/hold

/hold cancel

/lgtm

/lgtm

With a nit that I've been taught to report errors and warnings on stderr.

With a nit that I've been taught to report errors and warnings on stderr.

one day we'll have a cleaner way than Bash to write the entrypoints of the test, and that will include proper logging :)
thanks for having a look @jmencak :)
/approve


[SPARK-21093][R] Terminate R's worker processes in the parent of R's daemon to prevent a leak

What changes were proposed in this pull request?
This is a retry for #18320. This PR was reverted due to unexpected test failures with -10 error code.
I was unable to reproduce in MacOS, CentOS and Ubuntu but only in Jenkins. So, the tests proceeded to verify this and revert the past try here - https://github.com/apache/spark/pull/18456
This new approach was tested in https://github.com/apache/spark/pull/18463.
Test results:

With the part of suspicious change in the past try (https://github.com/apache/spark/pull/18463/commits/466325d3fd353668583f3bde38ae490d9db0b189)
Tests ran 4 times and 2 times passed and 2 time failed.

Without the part of suspicious change in the past try (https://github.com/apache/spark/pull/18463/commits/466325d3fd353668583f3bde38ae490d9db0b189)
Tests ran 5 times and they all passed.

With this new approach (https://github.com/apache/spark/pull/18463/commits/0a7589c09f53dfc2094497d8d3e59d6407569417)
Tests ran 5 times and they all passed.

It looks the cause is as below (see https://github.com/apache/spark/pull/18463/commits/466325d3fd353668583f3bde38ae490d9db0b189):
+ exitCode <- 1
...
+   data <- parallel:::readChild(child)
+   if (is.raw(data)) {
+     if (unserialize(data) == exitCode) {
      ...
+     }
+   }

...

- parallel:::mcexit(0L)
+ parallel:::mcexit(0L, send = exitCode)

Two possibilities I think

parallel:::mcexit(.. , send = exitCode)
https://stat.ethz.ch/R-manual/R-devel/library/parallel/html/mcfork.html

It sends send to the master (unless NULL) and then shuts down the child process.

However, it looks possible that the parent attemps to terminate the child right after getting our custom exit code. So, the child gets terminated between "send" and "shuts down", failing to exit properly.

A bug between parallel:::mcexit(..., send = ...) and parallel:::readChild.

PR proposal:
To resolve this, I simply decided to avoid both possibilities with this new approach here (https://github.com/apache/spark/pull/18465/commits/9ff89a7859cb9f427fc774f33c3521c7d962b723). To support this idea, I explained with some quotation of the documentation as below:
https://stat.ethz.ch/R-manual/R-devel/library/parallel/html/mcfork.html

readChild and readChildren return a raw vector with a "pid" attribute if data were available, an integer vector of length one with the process ID if a child terminated or NULL if the child no longer exists (no children at all for readChildren).

readChild returns "an integer vector of length one with the process ID if a child terminated" so we can check if it is integer and the same selected "process ID". I believe this makes sure that the children are exited.
In case that children happen to send any data manually to parent (which is why we introduced the suspicious part of the change (https://github.com/apache/spark/pull/18463/commits/466325d3fd353668583f3bde38ae490d9db0b189)), this should be raw bytes and will be discarded (and then will try to read the next and check if it is integer in the next loop).
How was this patch tested?
Manual tests and Jenkins tests.

cc @felixchung and @shivaram, I ran some simple tests on Mac OS (described one in https://github.com/apache/spark/pull/18320). Likewise, I would like to be sure before going through the checklist - https://github.com/apache/spark/pull/18320#issuecomment-310594551. Could you take a look please?

Test build #78896 has started for PR 18465 at commit 9ff89a7.

To cut this short, the new approach is roughly
From
exitCode <- 1
...
   data <- parallel:::readChild(child)
   if (is.raw(data)) {
     if (unserialize(data) == exitCode) {
     ...
     }
   }

...

parallel:::mcexit(0L, send = exitCode)

to
  pid <- parallel:::readChild(child)
  if (is.integer(pid)) {
    if (child == pid) {
      ...
    }
  }

...

parallel:::mcexit(0L)

For race condition concern, I tested this as below:
vi tmp.R

copied and pasted:
kill <- function(children) {
  lapply(children, function(child) {
    pid <- parallel:::readChild(child)
    if (is.integer(pid)) {
      if (child == pid) {
        print(paste("child PID:", child, "and read PID:", pid))
        tools::pskill(child, tools::SIGUSR1)
      } else {
        print(paste("child PID:", child, "and read PID:", pid, "not killing"))
      }
    } else {
      print(paste("child PID:", child, "and sent data:", unserialize(pid)))
    }
  })
}

for(i in 0:10000) {
  p <- parallel:::mcfork()
  if (inherits(p, "masterProcess")) {
    # Send no data
    parallel:::mcexit(0L)
  } else {
    p <- parallel:::mcfork()
    if (inherits(p, "masterProcess")) {
      # Send custom data
      parallel:::sendMaster("arbitrary")
      parallel:::sendMaster(123)
      parallel:::mcexit(0L)
    }
  }

  c <- parallel:::selectChildren(timeout = 0)
  if (is.integer(c)) {
    invisible(kill(c))
  }
}

and ran:
Rscript tmp.R

Also tested with this:
kill <- function(children) {
  lapply(children, function(child) {
    pid <- parallel:::readChild(child)
    if (is.integer(pid)) {
      if (child == pid) {
        print(paste("child PID:", child, "and read PID:", pid))
        tools::pskill(child, tools::SIGUSR1)
      } else {
        print(paste("child PID:", child, "and read PID:", pid, "not killing"))
      }
    } else {
      print(paste("child PID:", child, "and sent data:", unserialize(pid)))
    }
  })
}

for(i in 0:100) {
  for(i in 0:50) {
    p <- parallel:::mcfork()
    if (inherits(p, "masterProcess")) {
      # Send no data
      parallel:::mcexit(0L)
    } else {
      p <- parallel:::mcfork()
      if (inherits(p, "masterProcess")) {
        # Send custom data
        parallel:::sendMaster("arbitrary")
        parallel:::sendMaster(123)
        parallel:::mcexit(0L)
      }
    }
  }

  for(i in 0:50) {
    c <- parallel:::selectChildren(timeout = 0)
    if (is.integer(c)) {
      invisible(kill(c))
    }
  }
}

Test build #78896 has finished for PR 18465 at commit 9ff89a7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78896/
Test PASSed.

retest this please

Test build #78899 has started for PR 18465 at commit 9ff89a7.

retest this please

Test build #78900 has started for PR 18465 at commit 9ff89a7.

If these tests all pass, 8 times with Jenkins pass. I believe this solves the flakiness if so.

Test build #78899 has finished for PR 18465 at commit 9ff89a7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78899/
Test PASSed.

Test build #78900 has finished for PR 18465 at commit 9ff89a7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78900/
Test PASSed.

Thanks @HyukjinKwon - I will try to look at this later tonight

hmm, this is a fairly small but crucial change.
One point we were discussing, earlier, we are saying that we don't know if the child is going away, or merely slow starting, so we explicitly send and look for a exit code. I guess this condition is covered in the new change.
According to the doc
readChild and readChildren return a raw vector with a "pid" attribute if data were available, integer vector of length one with the process ID if a child terminated

So I guess it is safer to act only if we get an integer (which, according to above, the child terminated), but to clarify

isn't being "terminated" enough? that we have to pskill it again?
the original issue with leaking was thought to be related to child process getting stuck and not terminated properly? would that manifest again under this new behavior? in other words, would it get into a state where integer is never returned to the master?

isn't being "terminated" enough? that we have to pskill it again?

Indeed, this is the point. I really tested so many times but exit does not terminate (I think I might have to change the term used in the comments in my PR, maybe to 'kill').
This can be tested as below:
vi tmp.R

for(i in 0:50) {
  p <- parallel:::mcfork()
  if (inherits(p, "masterProcess")) {
    # Send no data
    parallel:::mcexit(0L)
  }
}

Sys.sleep(10)

Rscript tmp.R

and, ps -fe | grep /exec/R shows the children processes.

the original issue with leaking was thought to be related to child process getting stuck and not terminated properly?

I think yes, it is. It looked they are killed but somehow pipes (file descriptors) were left open. This hit the ulimit of open files and then it went an error like Resource temporarily unavailable fork. This looked because the children were killed by itself before or while calling exit() and left incomplete.

would that manifest again under this new behavior? in other words, would it get into a state where integer is never returned to the master?

In the original behaviour, I think the problem is exitis not being properly called or terminated during exit. The new change here I think it makes sure the children call exit properly.
I think this test makes sure what I said:
read.pids <- function(children) {
  lapply(children, function(child) {
    print(parallel:::readChild(child))
  })
}

kill <- function(children) {
  lapply(children, function(child) {
    tools::pskill(child, tools::SIGUSR1)
  })
}

p <- parallel:::mcfork()
if (inherits(p, "masterProcess")) {
  parallel:::mcexit(0L)
}

Sys.sleep(3)

print("Children exited - new behaviour here")
children <- parallel:::selectChildren(timeout = 0)
if (is.integer(children)) {
  read.pids(children)
  kill(children)
}

p <- parallel:::mcfork()
if (inherits(p, "masterProcess")) {
  tools::pskill(Sys.getpid(), tools::SIGUSR1)
  parallel:::mcexit(0L)
}

Sys.sleep(3)

print("Children killed itself - old behaviour here")
children <- parallel:::selectChildren(timeout = 0)
if (is.integer(children)) {
  read.pids(children)
}

p <- parallel:::mcfork()
if (inherits(p, "masterProcess")) {
  Sys.sleep(10000)
}

Sys.sleep(3)

print("Children killed by parent without exiting")
children <- parallel:::selectChildren(timeout = 0)
if (is.integer(children)) {
  kill(children)
  # wait for kill
  Sys.sleep(1)
  read.pids(children)
}

In my local, this prints the pid when mcexit is called properly.
[1] "Children exited - new behaviour here"
[1] 12992
[[1]]
[1] FALSE

[1] "Children killed itself - old behaviour here"
[1] "Children killed by parent without exiting"

And here we kill it.

btw, even when the earlier commit is revert seems like there's still a high number of test failure with
fails due to an unknown error code, -9. - do you know how that might be related?

@felixcheung are these failures happening from the gapply tests ? Also do we have a way to map the error code to an error reason ?

FWIW, I don't know but I guess it happens randomly in the middle of any tests. My wild guess is it is related with triggering many tests (or maybe rebasing a lot to trigger the build). I saw it broke all other builds with -9 in all other PRs when it happens once. Resently I mapped the unknown codes directly to be printed as above because I don't know the reason.

I see, quite possibly it is bubbled up more because of that change.

Just to be clear, -9 error has occured consistently without paricularly increasing or decreasing given my observations. I don't believe R change is partocularly related with it.

Just FYI, -9 error has occurred consistently without particularly increasing or decreasing given my observations. I think code changes are not particularly related with it.

thinking more about this, how would it handle the case when the forked process is in a bad state?
say, if we put stop() in the gapply UDF. Or something more serious say some sort of native error (Rcpp?). Would that state be reflected there in the returned terminated process id list? Can pskill still be effective in those cases?

Sounds good to.check. I will be back after investigating. BTW, I guess the original state does not handle that case too.

@felixcheung, it looks the codes below:
for(i in 0:10000) {
  p <- parallel:::mcfork()
  if (inherits(p, "masterProcess")) {
    stop("unexpected failure")
  }

  children <- suppressWarnings(parallel:::selectChildren(timeout = 0))
  if (is.integer(children)) {
    lapply(children, function(child) {
      print(parallel:::readChild(child))
      tools::pskill(child, tools::SIGUSR1)
    })
  }
}

works fine. Sounds parallel:::selectChildren sometimes prints warnings such as "Bad file descriptor" and looks few pipes are left open but it still does not at least die.
I also resembled the original way -
for(i in 0:10000) {
  p <- parallel:::mcfork()
  if (inherits(p, "masterProcess")) {
    tools::pskill(child, tools::SIGUSR1)
    stop("unexpected failure")
  }

  children <- parallel:::selectChildren(timeout = 0)
  if (is.integer(children)) {
    lapply(children, function(child) {
      print(parallel:::readChild(child))
    })
  }
}

In my local, this gets easily dead.

Also, just checked via manually calling stop() as end-to-end tests  after building it.
df <- createDataFrame(list(list(1L, 1, "1", 0.1)), c("a", "b", "c", "d"))
collect(gapply(df, "a", function(key, x) { stop() }, schema(df)))
... 30 times
collect(gapply(df, "a", function(key, x) { x }, schema(df)))

The daemon does not die and the pipes were not left open at all in this case.

@felixcheung and @shivaram, do you guys see it sounds okay to go through the checklist I used before for the current state? (of course, not asking a sing-off but just a rough judgement)

hey, thanks! I think it's reasonable.
I do want to check out what happens with a native error/exception (ie. here a std:: exception not inside a try/catch block in c++) as per this https://github.com/apache/spark/pull/18465#issuecomment-312936691 but that would be a stretch goal.

Yea, I get your point and thanks for details. Will go thought the list first and then maybe give a shot for that

Mac OS

[ ] jobs with many stages - https://github.com/apache/spark/pull/18320#issuecomment-310312766
[ ] jobs with long stages - https://github.com/apache/spark/pull/18320#issuecomment-310312766
[ ] NULL when we expect it - https://github.com/apache/spark/pull/18320#issuecomment-309940653
[ ] sleep before connection - https://github.com/apache/spark/pull/18320#discussion_r122687051
[ ] full tests
[ ] dapply/gapply described in the PR

CentOS

[ ] jobs with many stages - https://github.com/apache/spark/pull/18320#issuecomment-310312766
[ ] jobs with long stages - https://github.com/apache/spark/pull/18320#issuecomment-310312766
[ ] NULL when we expect it - https://github.com/apache/spark/pull/18320#issuecomment-309940653
[ ] sleep before connection - https://github.com/apache/spark/pull/18320#discussion_r122687051
[ ] full tests
[ ] dapply/gapply described in the PR

+https://github.com/apache/spark/pull/18465#issuecomment-313306125

(simply rebased)

Test build #79308 has started for PR 18465 at commit c08ccd5.

Test build #79308 has finished for PR 18465 at commit c08ccd5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79308/
Test PASSed.

Merged build finished. Test PASSed.

I referred this - http://adv-r.had.co.nz/Rcpp.html and your link.
I did as below:
R test alone
vi tmp.R

copy and paste the codes in Before and After and then ran
Rscript tmp.R

Before
library(Rcpp)
cppFunction('double takeLog(double val) {
    try {
        if (val <= 0.0) {         	// log() not defined here
            throw std::range_error("Inadmissible value");
        }
        return log(val);
    } catch(std::exception &ex) {
	forward_exception_to_r(ex);
    } catch(...) {
	::Rf_error("c++ exception (unknown reason)");
    }
    return NA_REAL;             // not reached
}')

for(i in 0:10000) {
  p <- parallel:::mcfork()
  if (inherits(p, "masterProcess")) {
    takeLog(-1.0)
    print("unreachable")
    tools::pskill(child, tools::SIGUSR1)
  }
}

print("end")
Sys.sleep(10L)

After
library(Rcpp)
cppFunction('double takeLog(double val) {
    try {
        if (val <= 0.0) {         	// log() not defined here
            throw std::range_error("Inadmissible value");
        }
        return log(val);
    } catch(std::exception &ex) {
	forward_exception_to_r(ex);
    } catch(...) {
	::Rf_error("c++ exception (unknown reason)");
    }
    return NA_REAL;             // not reached
}')

for(i in 0:10000) {
  p <- parallel:::mcfork()
  if (inherits(p, "masterProcess")) {
    takeLog(-1.0)
    print("unreachable")
  }

  children <- suppressWarnings(parallel:::selectChildren(timeout = 0))
  if (is.integer(children)) {
    lapply(children, function(child) {
      print(parallel:::readChild(child))
      tools::pskill(child, tools::SIGUSR1)
    })
  }
}

print("end")
Sys.sleep(10L)

The symptoms are similar with https://github.com/apache/spark/pull/18465#issuecomment-313049544
End to end
I could not do this as I did above with cppFunction due to such errors below:
Error in as.character(node[[1]]) :
  cannot coerce type 'builtin' to vector of type 'character'

So, I did as below:
vi takeLog.cpp

copy and paste
#include <Rcpp.h>

using namespace Rcpp;

// [[Rcpp::export]]
double takeLog(double val) {
    try {
        if (val <= 0.0) {         	// log() not defined here
            throw std::range_error("Inadmissible value");
        }
        return log(val);
    } catch(std::exception &ex) {
	forward_exception_to_r(ex);
    } catch(...) {
	::Rf_error("c++ exception (unknown reason)");
    }
    return NA_REAL;             // not reached
}

And then ran below with SparkR:
func <- function(key, x) {
  library(Rcpp)
  path <- "/.../spark/takeLog.cpp"
  sourceCpp(path)
  takeLog(-1.0)
}

df <- createDataFrame(list(list(1L, 1, "1", 0.1)), c("a", "b", "c", "d"))
collect(gapply(df, "a", func, schema(df)))
... 30 times
collect(gapply(df, "a", function(key, x) { x }, schema(df)))

The symptoms are also similar with https://github.com/apache/spark/pull/18465#issuecomment-313055990 for both before/after.

I tested above both on MacOS and CentOS. Basically, they are same but it is, as expected, worse on CentOS causing a crash in the master.

Doh! Not inside try/catch. Sure.

I rushed to read the comment. I also try to get rid of that try/catch in c++ as below:
R test alone
vi tmp.R

copy and paste the codes in Before and After and then ran
Rscript tmp.R

Before
library(Rcpp)
cppFunction('double takeLog(double val) {
    throw std::range_error("Inadmissible value");
    return NA_REAL;             // not reached
}')

for(i in 0:10000) {
  p <- parallel:::mcfork()
  if (inherits(p, "masterProcess")) {
    takeLog(-1.0)
    print("unreachable")
    tools::pskill(child, tools::SIGUSR1)
  }
}

print("end")
Sys.sleep(10L)

After
library(Rcpp)
cppFunction('double takeLog(double val) {
    throw std::range_error("Inadmissible value");
    return NA_REAL;             // not reached
}')

for(i in 0:10000) {
  p <- parallel:::mcfork()
  if (inherits(p, "masterProcess")) {
    takeLog(-1.0)
    print("unreachable")
  }

  children <- suppressWarnings(parallel:::selectChildren(timeout = 0))
  if (is.integer(children)) {
    lapply(children, function(child) {
      print(parallel:::readChild(child))
      tools::pskill(child, tools::SIGUSR1)
    })
  }
}

print("end")
Sys.sleep(10L)

The symptoms are similar with https://github.com/apache/spark/pull/18465#issuecomment-313049544
End to end
vi takeLog.cpp

copy and paste
#include <Rcpp.h>

using namespace Rcpp;

// [[Rcpp::export]]
double takeLog(double val) {
    throw std::range_error("Inadmissible value");
    return NA_REAL;             // not reached
}

With SparkR:
func <- function(key, x) {
  library(Rcpp)
  path <- "/Users/hyukjinkwon/Desktop/workspace/repos/forked/spark/takeLog.cpp"
  sourceCpp(path)
  takeLog(-1.0)
}

df <- createDataFrame(list(list(1L, 1, "1", 0.1)), c("a", "b", "c", "d"))
collect(gapply(df, "a", func, schema(df)))
# ... 30 times
collect(gapply(df, "a", function(key, x) { x }, schema(df)))

The comments here are a bit messy. I think https://github.com/apache/spark/pull/18465#issuecomment-313559240 summarises all results with some links.

ah cool, this https://github.com/apache/spark/pull/18465#issuecomment-313671617 was what I meant and want to see if it recovers (or dies) properly.
have you seen enough test passes running in jenkins?

Yes, I believe these were all worth being tested.
I have veen 9 times with the current change and I believe it is enough.

merged to master.
let's keep an eye on this, ok? thanks!

Sure, thanks @felixcheung. I will let you know if I see something odds!