[DOC] Glossary of terms

Describe the issue linked to the documentation
a like the idea of a glossary
https://aeon-toolkit--598.org.readthedocs.build/en/598/glossary.html
but it needs updating
Suggest a potential alternative/fix
Update/edit/remove

Related #361


i18n

Basic internationalization (i18n) framework with a couple of tests.

I18n has since been completely implemented using polyglot.js.


Trying to Helm chart a second time in different namespace fails

This is tied to #297.
I do an initial install of the Helm chart,
$ helm install cass-operator charts/cass-operator-chart
NAME: cass-operator
LAST DEPLOYED: Thu Oct 22 22:14:50 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
johns-mbp:cass-operator jsanda$ helm uninstall cass-operator
release "cass-operator" uninstalled
johns-mbp:cass-operator jsanda$ helm install cass-operator charts/cass-operator-chart
NAME: cass-operator
LAST DEPLOYED: Thu Oct 22 22:16:35 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None

Then I try to install a second release into a different namespace,
$ helm install cass-operator charts/cass-operator-chart --namespace test
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "cass-operator-cr" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "test": current value is "default"

In my local repo I went ahead and removed the files charts/cass-operator-chart/templates/clusterrole.yaml and charts/cass-operator-chart/templates/clusterrolebinding.yaml and tried installing again,
$ helm install cass-operator charts/cass-operator-chart --namespace test
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "cass-operator-webhook" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "test": current value is "default"

After some review and discussion I think support multiple, namespace-scoped installation with the validating webhook will require a bit of work. With that said, it should absolutely be supported though.
I am going to open a separate issue/PR for adding an option to the chart to not install the webhook. It should be configurable and will be provide a temporary work around.

@jimdickinson do you know where the cass-operator-cr ClusterRole is used?

@jimdickinson do you know where the cass-operator-cr ClusterRole is used?

The name for the ClusterRole defined in charts/cass-operator-chart/templates/clusterrole.yaml defaults to the clusterRoleName variable which has a value of cass-operator-cr. This prevents me from installing the chart multiple times without explicitly overriding the clusterRoleName variable.
If we instead have clusterRoleName default to an empty string, we could then use a default value like cass-oeprator-cr-{{ .Release.Name}}. This would make it easier to install multiple releases of the chart.
@jimdickinson thoughts?

The name for the ClusterRole defined in charts/cass-operator-chart/templates/clusterrole.yaml defaults to the clusterRoleName variable which has a value of cass-operator-cr. This prevents me from installing the chart multiple times without explicitly overriding the clusterRoleName variable.
If we instead have clusterRoleName default to an empty string, we could then use a default value like cass-oeprator-cr-{{ .Release.Name}}. This would make it easier to install multiple releases of the chart.
@jimdickinson thoughts?


Field Link doesn't create a fragment (ref) link - but the # does

Describe the bug
(See images) - clicking on a field link (#1 in image) does not create a fragment link, but clicking on the # (#2 in image) does.
#1 output: https://docs.buildresonance.com/demand/api/graphql-admin/reference/objects/demand-hq-notification/#
#2 output: https://docs.buildresonance.com/demand/api/graphql-admin/reference/objects/demand-hq-notification/#code-style-fontweight-normal-demandhqnotificationbsenderreferencekeybcodestring-

This seems like the primary anchor should create a fragment / ref link?

This is a docusaurus plugin we have no control over, maybe updating will help or something, but we ain't fixing.


Docs seem to get truncated when viewing on the iPhone

Not sure if this is the right place to create this issue but Docs seem to get truncated when viewing on the iPhone
iOS version 9.2.1

Can you send in a screenshot?

The "Event:error" line is the last I can see in this page. It doesn't allow me to scroll any further. I've tried on Chrome and Safari on multiple iphones. Same behaviour.

Interesting. Couldn't reproduce with with chrome's window size emulator, but will check it back at work against some devices.

Okay, this is reproduceable on saucelabs. I'll gather some more information and open a ticket on the main repo. Will close it then here. Good call @girishla

Great, ta

will let you close this when appropriate.

They're scrollable to the right and behave exactly like code comments in GitHub and StackOverflow. I think the current behavior is fine.

Nah, he doesn't mean the codeblocks, but that you can't scroll past a certain point.
iOS 9.2, iPhone 6, process.html https://saucelabs.com/beta/tests/e2c86c418a5646bab619e9c4b4e2a6c7/watch
iOS 8.4, iPhone 6, stream.html https://saucelabs.com/beta/tests/fdc9c31581a24841bd8688555374f7f9/watch
iOS 9.2, iPhone 6, stream.html https://saucelabs.com/beta/tests/9e1d5547403b4ffd9f4f01ff9bf4d968/watch

I tested on a real device and I can scroll all the way down - when I reach code blocks I have to stop scrolling and then resume it from a point that is not in the code block which is annoying.
I think this happens because the scrolling gets "stuck" on the code block - we can fix this by listening to the scroll event and handling this case.

Could you be more precise please. Hardware, OS, Page? Because it's very easy to reproduce the faulty behaviour at sauce labs tbh.

Sure - It's faulty, but I can scroll down. This is a real iPhone 6 with iOS 9.2 (haven't upgraded since).

I never had good experience viewing docs on my phone and I gave up... If there is any good third party docs viewer we could probably learn from it.

Closed in favor for nodejs/node#5861 Thanks for reporting!

Thanks for fixing!

+1


Capital letters in Wallet address

Capital letters in Wallet address

Fixed with the latest build.

There is a mix of capital and non-capital letters in wallet address


Delayed job deadlocks in development

Description
When running rake jobs:work in development mode with a newrelic-enabled app, the main thread & the newrelic sampling thread eventually deadlock each other. No more jobs get run, and the process becomes unable to exit on ctrl-c.
Expected Behavior
No deadlocks! They're not usually expected.
Troubleshooting or NR Diag results
Provide any other relevant log data.
Here's the main thread following a deadlock:
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:17:in `enter'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:17:in `block in mon_enter'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/dependencies/interlock.rb:48:in `block in permit_concurrent_loads'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:17:in `mon_enter'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:22:in `block in synchronize'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:597:in `checkin'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:551:in `block (3 levels) in clear_reloadable_connections'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:548:in `each'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:548:in `block (2 levels) in clear_reloadable_connections'
lib/ruby/2.7.0/monitor.rb:202:in `synchronize'
lib/ruby/2.7.0/monitor.rb:202:in `mon_synchronize'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:547:in `block in clear_reloadable_connections'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:749:in `block in with_exclusively_acquired_all_connections'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:824:in `with_new_connections_blocked'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:747:in `with_exclusively_acquired_all_connections'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:546:in `clear_reloadable_connections'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:570:in `clear_reloadable_connections!'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:1093:in `each'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:1093:in `clear_reloadable_connections!'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_handling.rb:351:in `clear_reloadable_connections!'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/railtie.rb:239:in `block (3 levels) in <class:Railtie>'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:427:in `instance_exec'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:427:in `block in make_lambda'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:603:in `catch'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:603:in `block in default_terminator'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:199:in `block in halting'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:512:in `block in invoke_before'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:512:in `each'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:512:in `invoke_before'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:105:in `run_callbacks'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/reloader.rb:120:in `class_unload!'
lib/ruby/gems/2.7.0/gems/railties-6.1.4/lib/rails/application/finisher.rb:244:in `block (2 levels) in <module:Finisher>'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:427:in `instance_exec'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:427:in `block in make_lambda'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:603:in `catch'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:603:in `block in default_terminator'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:199:in `block in halting'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:512:in `block in invoke_before'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:512:in `each'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:512:in `invoke_before'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/callbacks.rb:105:in `run_callbacks'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/execution_wrapper.rb:111:in `run!'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/reloader.rb:114:in `run!'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/reloader.rb:53:in `block (2 levels) in reload!'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/reloader.rb:52:in `tap'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/reloader.rb:52:in `block in reload!'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/execution_wrapper.rb:88:in `wrap'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/reloader.rb:51:in `reload!'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:330:in `reload!'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:187:in `block (2 levels) in start'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:172:in `loop'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:172:in `block in start'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/tagged_logging.rb:99:in `block in tagged'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/tagged_logging.rb:37:in `tagged'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/tagged_logging.rb:99:in `tagged'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:61:in `block in initialize'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:79:in `block in add'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:79:in `block in add'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:66:in `execute'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:40:in `run_callbacks'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:171:in `start'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/tasks.rb:9:in `block (2 levels) in <main>'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `block in execute'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `each'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `execute'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/task.rb:199:in `synchronize'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/task.rb:199:in `invoke_with_call_chain'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/task.rb:188:in `invoke'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:160:in `invoke_task'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:116:in `block (2 levels) in top_level'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:116:in `each'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:116:in `block in top_level'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:125:in `run_with_threads'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:110:in `top_level'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:83:in `block in run'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:186:in `standard_exception_handling'
lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:80:in `run'
bin/rake:6:in `<main>'

and NewRelic's agent thread:
lib/ruby/2.7.0/monitor.rb:108:in `sleep'
lib/ruby/2.7.0/monitor.rb:108:in `wait'
lib/ruby/2.7.0/monitor.rb:108:in `wait_for_cond'
lib/ruby/2.7.0/monitor.rb:108:in `wait'
lib/ruby/2.7.0/monitor.rb:116:in `wait_while'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/share_lock.rb:220:in `wait_for'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/share_lock.rb:190:in `block in yield_shares'
lib/ruby/2.7.0/monitor.rb:202:in `synchronize'
lib/ruby/2.7.0/monitor.rb:202:in `mon_synchronize'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/share_lock.rb:189:in `yield_shares'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:205:in `block in execute'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:696:in `block (2 levels) in log'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:26:in `block (2 levels) in synchronize'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:695:in `block in log'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:687:in `log'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:204:in `execute'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/mysql/database_statements.rb:50:in `execute'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:215:in `execute_and_free'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/mysql/database_statements.rb:55:in `exec_query'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:532:in `select'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:69:in `select_all'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/abstract/query_cache.rb:103:in `select_all'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/mysql/database_statements.rb:12:in `select_all'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/relation/calculations.rb:308:in `block in execute_simple_calculation'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/relation.rb:861:in `skip_query_cache_if_necessary'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/relation/calculations.rb:308:in `execute_simple_calculation'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/relation/calculations.rb:269:in `perform_calculation'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/relation/calculations.rb:144:in `calculate'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/instrumentation/active_record_prepend.rb:85:in `block in calculate'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent.rb:681:in `with_database_metric_name'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/instrumentation/active_record_prepend.rb:84:in `calculate'
lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/relation/calculations.rb:51:in `count'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/samplers/delayed_job_sampler.rb:56:in `count'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/logger_silence.rb:18:in `block in silence'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/logger_thread_safe_level.rb:52:in `log_at'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/logger_silence.rb:18:in `silence'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/logger.rb:64:in `block (3 levels) in broadcast'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/logger_silence.rb:18:in `block in silence'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/logger_thread_safe_level.rb:52:in `log_at'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/logger_silence.rb:18:in `silence'
lib/ruby/gems/2.7.0/gems/activesupport-6.1.4/lib/active_support/logger.rb:62:in `block (2 levels) in broadcast'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/samplers/delayed_job_sampler.rb:45:in `failed_jobs'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/samplers/delayed_job_sampler.rb:65:in `poll'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/sampler_collection.rb:41:in `block in poll_samplers'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/sampler_collection.rb:39:in `delete_if'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/sampler_collection.rb:39:in `poll_samplers'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/sampler_collection.rb:13:in `block in initialize'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/event_listener.rb:40:in `block in notify'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/event_listener.rb:38:in `each'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/event_listener.rb:38:in `notify'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/agent.rb:1143:in `transmit_data'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/agent.rb:619:in `block in create_and_run_event_loop'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/event_loop.rb:148:in `block in dispatch_event'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/event_loop.rb:146:in `each'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/event_loop.rb:146:in `dispatch_event'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/event_loop.rb:111:in `run_once'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/event_loop.rb:99:in `run'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/agent.rb:641:in `create_and_run_event_loop'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/agent.rb:701:in `block (2 levels) in deferred_work!'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent.rb:501:in `disable_all_tracing'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/agent.rb:698:in `block in deferred_work!'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/agent.rb:678:in `catch_errors'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/agent.rb:697:in `deferred_work!'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/agent.rb:724:in `block in start_worker_thread'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-7.1.0/lib/new_relic/agent/threading/agent_thread.rb:14:in `block in create'

Steps to Reproduce
I found this helpful for narrowing down the problem:
NewRelic::Agent::Samplers::DelayedJobSampler.prepend(
  Module.new {
    def count(query)
      puts "#{Time.now} Fetching count #{query}"
      t = nil
      Rails.logger.silence do
        t = super
      end
      puts "#{Time.now} Count: #{t}"
      t
    rescue Exception => e
      puts e.inspect
      raise
    end
  }
)

NewRelic::Agent::EventLoop.prepend(
  Module.new {
    def fire_every(interval, event)
      interval = interval / 10
      puts "Firing event #{event} every #{interval} seconds."
      super(interval, event)
    end
  }
)

which logs before and after the DJ sampling occurs, and makes the sampling more frequent so you don't have to wait hours for it to occur. When the deadlock occurs you'll see something like
2021-07-01 11:55:30 +0100 Fetching count failed_at is not NULL
2021-07-01 11:55:30 +0100 Count: 4
2021-07-01 11:55:30 +0100 Fetching count locked_by is not NULL

in the log, followed by no other output.
Your Environment
Newrelic agent 7.1.0
Ruby 2.7.3
Rails 6.1.4
macOS 11.4
Additional context
I wonder if the DJ sampling needs wrapping in Rails.application.executor, but not totally sure.

hello @jdelStrother
Thanks for letting us know about this issue.
Following your instructions and using the code provided, I was able to replicate some weird behavior, so this does appear to be something we'll want to take a closer look at.
When I was running it, it would output
Firing event report_data every 6 seconds.
Firing event report_event_data every 6 seconds.
Firing event reset_log_once_keys every 6.0 seconds.
2021-07-02 12:49:27 -0700 Fetching count failed_at is not NULL
2021-07-02 12:49:27 -0700 Count: 0
2021-07-02 12:49:27 -0700 Fetching count locked_by is not NULL
2021-07-02 12:49:27 -0700 Count: 0
2021-07-02 12:49:33 -0700 Fetching count failed_at is not NULL

and then be deadlocked and unable to ctrl-c out of it.
This appears to be a long standing issue, as I also tried with some older agent versions and saw the same behavior. This was surprising to me since we haven't received any other reports of this issue.
I'll put this in our next bug smash, so that when we get started on the bug smash we'll take a closer look at solving this issue. Thanks for letting us know!

Hi @jdelStrother, @tannalynn  and I took a look at this today.
We're still narrowing down the cause of the issue, however, we noticed in our playground environment that the deadlock went away when updating our configuration to disable the DelayedJob sampler:
# newrelic.yml

  disable_delayed_job_sampler: true

This is a potential temporary workaround until we identify the root cause. Thanks for your patience!

Hi @jdelStrother, we may have a fix for the deadlock issue on this branch. Feel free to update your Gemfile with the following if you'd like to see if it helps:
gem 'newrelic_rpm', :git => 'https://github.com/newrelic/newrelic-ruby-agent.git',  :branch => 'bugfix/delayed-job-deadlocks'

There are references in the latest stacktrace to some files directly within RAILS_ROOT [...] Another new element I see is sentry-ruby-core

I've disabled some of the RAILS_ROOT code, and removed Sentry, but was still able to reproduce the deadlock:

main thread
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:17:in `enter'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:17:in `block in mon_enter'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies/interlock.rb:48:in `block in permit_concurrent_loads'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:17:in `mon_enter'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:22:in `block in synchronize'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:597:in `checkin'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:551:in `block (3 levels) in clear_reloadable_connections'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:548:in `each'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:548:in `block (2 levels) in clear_reloadable_connections'
lib/ruby/2.7.0/monitor.rb:202:in `synchronize'
lib/ruby/2.7.0/monitor.rb:202:in `mon_synchronize'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:547:in `block in clear_reloadable_connections'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:749:in `block in with_exclusively_acquired_all_connections'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:824:in `with_new_connections_blocked'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:747:in `with_exclusively_acquired_all_connections'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:546:in `clear_reloadable_connections'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:570:in `clear_reloadable_connections!'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:1093:in `each'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:1093:in `clear_reloadable_connections!'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_handling.rb:351:in `clear_reloadable_connections!'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/railtie.rb:239:in `block (3 levels) in <class:Railtie>'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:427:in `instance_exec'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:427:in `block in make_lambda'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:603:in `catch'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:603:in `block in default_terminator'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:199:in `block in halting'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:512:in `block in invoke_before'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:512:in `each'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:512:in `invoke_before'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:105:in `run_callbacks'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:120:in `class_unload!'
lib/ruby/gems/2.7.0/gems/railties-<IP_ADDRESS>/lib/rails/application/finisher.rb:244:in `block (2 levels) in <module:Finisher>'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:427:in `instance_exec'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:427:in `block in make_lambda'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:603:in `catch'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:603:in `block in default_terminator'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:199:in `block in halting'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:512:in `block in invoke_before'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:512:in `each'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:512:in `invoke_before'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:105:in `run_callbacks'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:111:in `run!'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:114:in `run!'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:53:in `block (2 levels) in reload!'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:52:in `tap'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:52:in `block in reload!'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:88:in `wrap'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:51:in `reload!'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:330:in `reload!'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:187:in `block (2 levels) in start'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:172:in `loop'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:172:in `block in start'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:61:in `block in initialize'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:79:in `block in add'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:66:in `execute'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/lifecycle.rb:40:in `run_callbacks'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/worker.rb:171:in `start'
lib/ruby/gems/2.7.0/gems/delayed_job-4.1.9/lib/delayed/tasks.rb:9:in `block (2 levels) in <main>'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `block in execute'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `each'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `execute'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `synchronize'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `invoke_with_call_chain'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/task.rb:188:in `invoke'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:160:in `invoke_task'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `block (2 levels) in top_level'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `each'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `block in top_level'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:125:in `run_with_threads'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:110:in `top_level'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:83:in `block in run'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:186:in `standard_exception_handling'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:80:in `run'
lib/ruby/gems/2.7.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
bin/rake:21:in `load'
bin/rake:21:in `<main>'

agent thread
lib/ruby/2.7.0/monitor.rb:108:in `sleep'
lib/ruby/2.7.0/monitor.rb:108:in `wait'
lib/ruby/2.7.0/monitor.rb:108:in `wait_for_cond'
lib/ruby/2.7.0/monitor.rb:108:in `wait'
lib/ruby/2.7.0/monitor.rb:116:in `wait_while'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/share_lock.rb:220:in `wait_for'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/share_lock.rb:190:in `block in yield_shares'
lib/ruby/2.7.0/monitor.rb:202:in `synchronize'
lib/ruby/2.7.0/monitor.rb:202:in `mon_synchronize'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/share_lock.rb:189:in `yield_shares'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:205:in `block in execute'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:696:in `block (2 levels) in log'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:26:in `block (2 levels) in synchronize'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:695:in `block in log'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:687:in `log'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:204:in `execute'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/mysql/database_statements.rb:50:in `execute'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:215:in `execute_and_free'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/mysql/database_statements.rb:55:in `exec_query'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/database_statements.rb:532:in `select'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/database_statements.rb:69:in `select_all'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/query_cache.rb:103:in `select_all'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/mysql/database_statements.rb:12:in `select_all'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/calculations.rb:308:in `block in execute_simple_calculation'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation.rb:861:in `skip_query_cache_if_necessary'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/calculations.rb:308:in `execute_simple_calculation'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/calculations.rb:269:in `perform_calculation'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/calculations.rb:144:in `calculate'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/instrumentation/active_record_prepend.rb:85:in `block in calculate'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent.rb:682:in `with_database_metric_name'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/instrumentation/active_record_prepend.rb:84:in `calculate'
lib/ruby/gems/2.7.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/calculations.rb:51:in `count'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/samplers/delayed_job_sampler.rb:56:in `count'
RAILS_ROOT/lib/delayed_job_hacks.rb:16:in `block in count'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/logger_silence.rb:18:in `block in silence'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/logger_thread_safe_level.rb:52:in `log_at'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/logger_silence.rb:18:in `silence'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/logger.rb:64:in `block (3 levels) in broadcast'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/logger_silence.rb:18:in `block in silence'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/logger_thread_safe_level.rb:52:in `log_at'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/logger_silence.rb:18:in `silence'
lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/logger.rb:62:in `block (2 levels) in broadcast'
RAILS_ROOT/lib/delayed_job_hacks.rb:15:in `count'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/samplers/delayed_job_sampler.rb:45:in `failed_jobs'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/samplers/delayed_job_sampler.rb:65:in `poll'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/sampler_collection.rb:41:in `block in poll_samplers'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/sampler_collection.rb:39:in `delete_if'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/sampler_collection.rb:39:in `poll_samplers'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/sampler_collection.rb:13:in `block in initialize'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/event_listener.rb:40:in `block in notify'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/event_listener.rb:38:in `each'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/event_listener.rb:38:in `notify'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/agent.rb:1143:in `transmit_data'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/agent.rb:619:in `block in create_and_run_event_loop'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/event_loop.rb:148:in `block in dispatch_event'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/event_loop.rb:146:in `each'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/event_loop.rb:146:in `dispatch_event'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/event_loop.rb:111:in `run_once'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/event_loop.rb:99:in `run'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/agent.rb:641:in `create_and_run_event_loop'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/agent.rb:701:in `block (2 levels) in deferred_work!'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent.rb:502:in `disable_all_tracing'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/agent.rb:698:in `block in deferred_work!'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/agent.rb:678:in `catch_errors'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/agent.rb:697:in `deferred_work!'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/agent.rb:724:in `block in start_worker_thread'
lib/ruby/gems/2.7.0/gems/newrelic_rpm-8.0.0/lib/new_relic/agent/threading/agent_thread.rb:14:in `block in create'

delayed_job_hacks.rb just contains the hacks to try & speed up the deadlock:
NewRelic::Agent::Samplers::DelayedJobSampler.prepend(
  Module.new {
    def count(query)
      puts "#{Time.now} Fetching count #{query.inspect}..."
      t = nil
      Rails.logger.silence do
        t = super
      end
      puts "#{Time.now} Count: #{t}"
      t
    rescue Exception => e # rubocop:disable Lint/RescueException
      puts e.inspect
      raise
    end
  }
)

NewRelic::Agent::EventLoop.prepend(
  Module.new {
    def fire_every(interval, event)
      puts "Firing event #{event} every #{interval / 10} seconds."
      super(interval / 10, event)
    end
  }
)

you mention this is occurring in development mode. Does that refer to your development environment/local machine or something else? Do issues come up in other environments?

I only see it for RAILS_ENV=development, presumably because ActiveSupport::Dependencies.interlock is only active when config.cache_class=true.
I created a bare-bones app to try & reduce the problem further: https://github.com/jdelStrother/newrelic-dj-deadlocks
The license key in newrelic.yml needs replacing with a real key[^1], then running rake jobs:work should hopefully eventually hit the deadlock.
The deadlock takes significantly longer to reproduce with the bugfix/delayed-job-deadlocks branch compared to 8.0.0, but I still hit it occasionally. In the test app (which speeds up sampling 100x) it took maybe half an hour to reach.
[^1]: is there a test key that can be used to sample locally but not necessarily report to NewRelic?

Hello @jdelStrother,  thank you for helping by provide a bare-bones app and log information for this issue.  We truly appreciate it. We tried to resolve this issue for 8.1.0, but unfortunately, we were not able to do so.  We will return to this issue when we can pick it up again.  If it's becoming pressing, I encourage you to file an issue with New Relic Support.  Thank you for your patience.

Closing this issue for now since it only happens in development and a fix to reduce the amount of time until a deadlock has been shipped. Please re-open if this comes up in a non-development environment.

Hi - we’re in the midst of setting up New Relic on our environment and one of our applications in production appears to have a very similar issue as described above in this ticket on agent 8.8.0. We are running DelayedJob via rake jobs:work in a Docker container and will experience a deadlock generally within a few minutes (!) so long as New Relic is active.
Interestingly, we are also not seeing any of the successful jobs actually get submitted to the New Relic dashboard for the app. As seen above, there’s very little in logs, but our rb_backtrace() for the main thread looks very similar to what’s been reported already.

@hedgeye-fslezak Thanks for letting us know that you're encountering a similar issue to this one.
For this particular issue, the deadlock was only seen in development environments, but was not seen in production due to differences in settings between prod/dev environments. Right now, I'm not sure if it's the same issue as this or just one that looks similar. One way this issue was able to be prevented was to disable the delayed job samplers (which caused the problem) by adding the following to the newrelic.yml:
# newrelic.yml

  disable_delayed_job_sampler: true

If this is the same issue, setting that config should prevent the deadlock from occurring.
One thing that's interesting, is that I don't believe we saw the same behavior you describe about the successful jobs not appearing on the UI. Are you using infinite tracing? In 8.9.0 we released a bugfix for infinite tracing that would prevent data from being sent to the new relic servers. If you aren't using infinite tracing, that bugfix wouldn't be relevant to the situation though.
One thing to note is that data related to a transaction will not be sent until the transaction is complete. I have seen jobs in the past structured in such a way that it was just one transaction running indefinitely, which caused the agent to be unable to send the transaction data to the new relic servers. I'm not sure if that is relevant to your particular situation since it isn't common, but I wanted to bring it up because I have seen that before from someone using delayed job.
Enabling debug level logging for the agent and reviewing the logs may be able to provide additional information about what is going on behind the scenes in the agent.
# newrelic.yml

  log_level: debug

One of the first things I'd check in the agent logs would be to look for any errors or warnings, and then lines related to communicating to the new relic server to see if there are any issues in the response from the collector, these tend to look like this
DEBUG : Sending TransactionEvent data to New Relic Service
DEBUG : Sampled 4 / 4 (100.0 %) requests this cycle, 59 / 59 (100.0 %) since startup
DEBUG : Sending 4 items to analytic_event_data
DEBUG : Sending request to <collector url> with POST
DEBUG : Received response, status: 202, encoding: ''

Hopefully some of this helps, please let me know if you have any questions.

Hi! Thank you for the response, and the information about that config flag. We will be testing that more this week, rather than our current heavy-handed solution of just disabling the agent entirely on our worker nodes.
On our environment (staging), we did manage to get some information out of the debug log, most notably that the deadlock appears to happen on the 60_second_harvest event:
[2022-09-19 16:30:24 -0400 b91b1743c2ff (135)] DEBUG : EventLoop: Dispatching event '5_second_harvest' with 4 callback(s).
[2022-09-19 16:30:24 -0400 b91b1743c2ff (135)] DEBUG : Sending TransactionEvent data to New Relic Service
[2022-09-19 16:30:24 -0400 b91b1743c2ff (135)] DEBUG : Sampled 0 / 0 (NaN %) requests this cycle, 0 / 0 (NaN %) since startup
[2022-09-19 16:30:24 -0400 b91b1743c2ff (135)] DEBUG : Sending CustomEvent data to New Relic Service
[2022-09-19 16:30:24 -0400 b91b1743c2ff (135)] DEBUG : Sending ErrorEvent data to New Relic Service
[2022-09-19 16:30:24 -0400 b91b1743c2ff (135)] DEBUG : Sending LogEvent data to New Relic Service
[2022-09-19 16:30:24 -0400 b91b1743c2ff (135)] DEBUG : Sending 7 items to log_event_data
[2022-09-19 16:30:24 -0400 b91b1743c2ff (135)] DEBUG : Sending request to <redacted> with POST
[2022-09-19 16:30:25 -0400 b91b1743c2ff (135)] DEBUG : Received response, status: 202, encoding: ''

[2022-09-19 16:30:29 -0400 b91b1743c2ff (135)] DEBUG : EventLoop: Dispatching event '60_second_harvest' with 1 callback(s).
[2022-09-19 16:30:29 -0400 b91b1743c2ff (135)] DEBUG : Sending data to New Relic Service

We did have a couple earlier runs of 60_second_harvest succeed in this case, which seemed to actually report what we expected:
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : EventLoop: Dispatching event '60_second_harvest' with 1 callback(s).
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending data to New Relic Service
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending 51 items to metric_data
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending request to [redacted]  with POST
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Received response, status: 202, encoding: ''
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending 7 items to log_event_data
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending request to [redacted]  with POST
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Received response, status: 202, encoding: ''
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending request to [redacted] with POST
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Received response, status: 200, encoding: ''
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Received get_agent_commands = []
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : No thread profiles with data found to send.
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : EventLoop: Dispatching event 'reset_log_once_keys' with 1 callback(s).
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : EventLoop: Dispatching event '5_second_harvest' with 4 callback(s).
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending TransactionEvent data to New Relic Service
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sampled 0 / 0 (NaN %) requests this cycle, 0 / 0 (NaN %) since startup
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending CustomEvent data to New Relic Service
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending ErrorEvent data to New Relic Service
[2022-09-19 16:29:29 -0400 b91b1743c2ff (135)] DEBUG : Sending LogEvent data to New Relic Service

I'm still not exactly sure why jobs didn't report earlier as they are working on a separate test; I suspect it was just bad luck and the deadlock happened during submission (?). Hopefully the above can be of some value to the New Relic team as well. Thanks for your support!

@hedgeye-fslezak - Thanks for sharing your debug logs!  We'll keep an eye out for your update on your test with the config flag toggle. 😄

Hiya, update on our end. We managed to find our problem - it was indeed related to a stray config.cache_class = true caused by us running Spring in production (oops). Removing spring and ensuring cache_classes was disabled cleared the problem up and stopped the deadlocks, so that's at least a workable solution.
Thank you all for your support!

Fantastic! Thanks for the update! I'm glad you found a solution. 🎉
I'm going to close this ticket now, but please feel free to comment on this issue or create a new one if the problem returns.


KeyError: 'queryResult'

After running your django example:
self.intent = request['queryResult']['intent']['displayName']
KeyError: 'queryResult'

I have the same issue! Was hoping to use this library but does not seem to work?!

I debugged a bit. This is due to the incoming request body not being parsed ok.
For me request was a `` so I removed the typechecking:
def webhook(request) -> Dict:

Next you need to parse the request yourself:
import json
request_ = json.loads(request.body)

Next error I ran into is that the response of dialogflow-fulfillment is not correctly formatted. So I guess this library is not really correct!? The outputContexts that was automagically put in the response wasn't correctly formatted according to Dialogflow.


feat(restartStuckPod):Restart stuck pods

@AntiTyping to help @vimystic test this one

Wip :  to rework  this to accomodate other time strings.

Update :
So far the only sentries that get stuck are nibiru , stargaze , saga. (They are all pre sdk50).
Speculation still appears to be true.

Update : Same as last week.
Once nibiru , stargaze and saga are upgraded to sdk50 we can expect (with some confidence) this issue to go away.

No change in status .

Abandoning this .
We can revisit if val running chains that  remain on pre 50 sdk, insist on this fix.


getting different results with tutorial

Trying out the get started tutorial:
After executing clf.fit(X_train, y_train) I get
BinaryRelevance(classifier=SVC(), require_dense=[False, True])
instead of
BinaryRelevance(classifier=SVC(C=1.0, cache_size=200, class_weight=None, coef0=0.0,   decision_function_shape='ovr', degree=3, gamma='auto', kernel='rbf',   max_iter=-1, probability=False, random_state=None, shrinking=True,   tol=0.001, verbose=False),         require_dense=[False, True])
and
clf.classifiers_
gives
[SVC(), SVC(), SVC(), SVC(), SVC(), SVC()]
and my prediction matrix has only 27 stored elements instead of 246.
Any idea what could be the reason?

Part of my problem is solved here.
But still the prediction matrix contains only 27 stored elements and the hamming loss doesn't match the one posted in the tutorial. Could it be the emotions dataset changed?


Generate _BuildInfo.xml file after asserting version numbers

One of the artifacts created by UppercuT was the _BuildInfo.xml file, which contains all of the asserted version numbers, used as part of the build.
This is useful information to have, and we should look to generate a similar file during the execution of the Chocolatey.Cake.Recipe build, which can then be uploaded as an artifact into the CI system being used.

An example of the contents of this file is as follows:
<?xml version="1.0" ?>
<buildInfo>
  <projectName>chocolatey</projectName>
  <companyName>Chocolatey Software, Inc.</companyName>
  <versionMajor>0</versionMajor>
  <versionMinor>12</versionMinor>
  <versionPatch>1</versionPatch>
  <buildNumber>0</buildNumber>
  <revision>0.12.1</revision>
  <revisionhash>0.12.1</revisionhash>
  <version><IP_ADDRESS></version>
  <versionProduct>0.12.1-0.12.1</versionProduct>
  <repositoryPath>https://github.com/chocolatey/choco</repositoryPath>
  <microsoftNetFramework>net-4.0</microsoftNetFramework>
  <msbuildConfiguration>ReleaseOfficial</msbuildConfiguration>
  <msbuildPlatform>Any CPU</msbuildPlatform>
  <builtWith>UppercuT v. <IP_ADDRESS></builtWith>
</buildInfo>

This is made up from:
      <![CDATA[<?xml version="1.0" ?>
<buildInfo>
  <projectName>${project.name}</projectName>
  <companyName>${string::replace(string::replace(company.name,'&','&'),'&','&')}</companyName>
  <versionMajor>${version.major}</versionMajor>
  <versionMinor>${version.minor}</versionMinor>
  <versionPatch>${version.patch}</versionPatch>
  <buildNumber>${version.build}</buildNumber>
  <revision>${version.revision}</revision>
  <revisionhash>${version.hash}</revisionhash>
  <version>${assembly.version.full}</version>
  <versionProduct>${version.product}</versionProduct>
  <repositoryPath>${repository.path}</repositoryPath>
  <microsoftNetFramework>${microsoft.framework}</microsoftNetFramework>
  <msbuildConfiguration>${msbuild.configuration}</msbuildConfiguration>
  <msbuildPlatform>${msbuild.platform}</msbuildPlatform>
  <builtWith>UppercuT v. ${version.uppercut}</builtWith>
</buildInfo>]]>


docs: update README

Simplify primary README.md and include links to 3.0 documentation.
Remove extraneous NATS README.md.
fixes #212

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/go-mod-messaging/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

Codecov Report

Merging #235 (eb809bb) into main (ac0d35d) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #235   +/-   ##
=======================================
  Coverage   71.14%   71.14%
=======================================
  Files          24       24
  Lines        1043     1043
=======================================
  Hits          742      742
  Misses        269      269
  Partials       32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Please release the training code!

I am working on a course project (potential thesis topic) that involves training your model. That would be very helpful if you could advance the date for publishing the training code. Thank you in advance.

Thanks for your attention. Start updating this week.


Can't connect to coind to get live updates from the p2p network.

I am struggling with this for a couple of hours now:
Can't connect to coind to get live updates from the p2p network. (Tried connecting to bitcoind at <IP_ADDRESS>:5837 and failed.)
in the log I see { '0': 'connecting to <IP_ADDRESS>:5837' } after a while { '0': 'disconnected from peer <IP_ADDRESS>:5837' }.
I can telnet <IP_ADDRESS> 5837 and <IP_ADDRESS> 5837
telnet <IP_ADDRESS> 5837
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.
Escape character is '^]'.
I double checked the magic again, and it is d9e6e7e5 exactly like in the source code https://github.com/Leocoin-project/LEOcoin/blob/master/src/main.cpp#L3023
The Protocol version is 70000 same as in the code
"version" : "v<IP_ADDRESS>-L32a928e-leo-enhanced",
"protocolversion" : 70000,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 605091,
"moneysupply" : 65289528.44299800,
"connections" : 9,
"proxy" : "",
"ip" : "<IP_ADDRESS>",
"difficulty" : 0.18828001,
"testnet" : false,
"keypoololdest" :<PHONE_NUMBER>,
"keypoolsize" : 102,
"paytxfee" : 0.00001000,
"errors" : "."
but I can't get it to work !!! any suggestion ? did I miss anything ?

Fixed, somehow I mixed the magic numbers for the mainnet with the testnet.
Otherwise for people having any trouble connecting to p2p, go through the steps that I've listed and double check your config.

lol at best i connect to the p2p for a day or two.. at worst it takes restarting over and over every 30 seconds, and sometiems takes 20-50 tries to get it to connect and stay (for a few hours/days)
i see this issue all over github..

Hello, yes I thought it worked as well, but after few hours the p2p was dead again, I found out that the problem is with the coin daemon (sonething with magix number) and it is not with Insight.


[Request - Product] podman

Full and short name of product

long, full name : redhat-podman
short name : podman

Does this product have LTS versions? What are the intervals between each LTS version?
I dont'know (yet)
What is the website for the product and for its version information?

:octocat: containers/podman
https://podman.io/
:tickets: https://github.com/containers/podman.io/issues
Getting Started with Podman
Podman blog
Podman on RedHat site

Additional context

https://github.com/containers/podman/blob/main/RELEASE_PROCESS.md

The branches could take some effort to sort out, though.
  origin/v3.0
  origin/v3.0.1-rhel
  origin/v3.1
  origin/v3.2
  origin/v3.2.3-rhel
  origin/v3.3
  origin/v3.3.1-rhel
  origin/v3.4
  origin/v3.4.2-rhel
  origin/v4.0
  origin/v4.0-rhel
  origin/v4.1
  origin/v4.1.1-rhel
  origin/v4.2
  origin/v4.2.0-rhel
  origin/v4.3
  origin/v4.3.1-rhel
  origin/v4.4
  origin/v4.4.1-crio
  origin/v4.4.1-rhel
  origin/v4.5
  origin/v4.6
  origin/v4.6.1-rhel
  origin/v4.7
  origin/v4.8
  origin/v4.9
  origin/v4.9-rhel
  origin/v4.9.1-rhel
  origin/v4.9.3-rhel
  origin/v5.0
  origin/v5.1
  origin/v5.2
  origin/v99.99.99-rhel_ci_test_do_not_merge

But otherwise it could probably reuse docker/moby ?
auto:
  methods:
  -   git: https://github.com/moby/moby.git
      regex: ^v(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(-ce)?$

auto:
  methods:
  -   git: https://github.com/containers/podman.git
      regex: ^v(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(-rhel)?$

Note: only the client (podman-remote) is included in the actual github releases.
The packaging of the server (podman) is handled by the Linux distributions...
https://podman.io/docs/installation#linux-distributions
For Podman Machine v5 and beyond, there is a custom Podman Machine OS.
It builds the image for the podman machine VM, and features a newer version.
e.g. --image docker://quay.io/podman/machine-os:5.2

@adriens you should call this "podman-engine", instead of "redhat-podman"
Both to avoid confusion with the Podman Desktop software, and because it is an Open Source project driven by an organization called "containers" (even if it is sponsored by Red Hat, it's not a product). It also rhymes with "docker-engine".
The URLto the issues is wrong, you got the one for the website by accident...

Without more input from the project, it is hard to do a timeline (since it is unclear how long a release is supported for).

The ubuntu/debian and other distro packages will be out of scope for the podman page, those are tracked indirectly via the distro pages themselves.

The fedora/rhel are "special", since that is where the podman developers are determining which versions are still supported or not

Might want to create a separate page for Podman Desktop, even if it is only the GUI (and not the Podman Machine)
https://podman-desktop.io/


Add eNFT.md

Grant Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the Terms and Conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
[x] The initial PR contains only one commit (squash if needed before submitting your PR).
[x] The grant will only be announced once the first milestone has been accepted.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Many thanks for the application @gusiri. We will look into it as soon as possible. Do you intend to deliver milestones 5-6 even though they are self-funded? If not and they represent future plans, I'd suggest moving them to that section to avoid confusion.

@alxs Yes that's what we intend to do. We would like to contribute to Polkadot ecosystem and its expansion with real-world integration and use cases.

@alxs Yes, we will deliver them as grant milestones as well even though they are self-funded.

Thank you so much for your kind review and feedback! Here are the answers to your questions/comments.
Q. In general, I recommend finishing M1 before you apply for the grant, since you don’t want any money for it anyway and this way it will be easier to convince the committee.
Actually, we have been already working on M1 as you recommended :) We will share the deliveries of M1 this week. Let us get back to you with the delivers soon.
Q. To be honest, I also still find the combination of an erc20 token and no visible github activity quite concerning. Is there any code/recent development you could share? The Splytcore Polkadot Substrate repo is basically only a fork of the node template plus your grant application as far as I can see it.
We fully understand your concern and we also would like to show that we are serious with Polkadot and this grant. As you recommend, we have been working on M1 to show that we are serious in this grant application and our future plan with polkadot. We also plan to work on M2 after we complete M1 regardless of this grant process so that we can show the committee that we are serious.
So far, 1) we did set up local rococo testnet for parachain development (M1-D3), 2) we are learning and developing our very first pallet, which is a part of M2 (eNFT Asset), 3) we are working on M1-D1 (Polkadot NFT Projects Survey, 4) we are working M1-D2 (eNFT Ref Architecture).
In terms of the Polkadot repository, as we mentioned above, we have been mainly working on milestone 1 so that did not have meaningful development-related commits yet. However, we already started working on M2-eNFT pallet for Asset and will commit those codes soon. We will wrap up M1-D1 and M1-D2 this week. Also, we will actively push our commits to the repository after wrapping up M1, because M2 is mostly about developing eNFT pallets.
We were also invited to NFT Strategy on Kusama element group and we will communicate with other projects for the survey and future collaboration.
Also, since public repositories do not show many activities, we attached a brief screenshot of our private repositories. There are also some other developments going on without repositories setup and we will also share them once they are ready.

Q. I’m also not fully sure why you need to develop your own standard for the polkadot ecosystem. Could you explain this a little bit more detailed? Why are you not able to use existing ethereum standards for this?
First of all, we needed to develop a E-commerce specific NFT standards rather than the existing ethereum standards. During the time we were developing our E-commerce NFT standard on top of ethereum and trying to deploy use case applications, we suffered real-world problems (ex: gas and scalability) and that stopped us moving forward. We are eager to deliver real-world applications to the e-commerce industry and we thought Polkadot is best fit for our
Q. Furthermore, if you want to focus on creating a standard, you probably should integrate the PSP process in your application:
Thank you so much for your advice, we looked at the PSP process and will study more about PSP. As we work on M2 and collaborate with other NFT projects (for detailed design specifications), we will consider PSP too.

@gusiri I'm closing this due to inactivity. Feel free to leave a comment if you'd like us to review your application again and we'll reopen it!

@alxs Hi alxs! Sorry for the delay. Can you re-open this pull request? We have worked on milestone #1 so far and now we would like to submit the deliverables. Also, can you please let us know how to submit those deliverables? It is okay that we add the github URLs of deliverables into the application? Thank you!

Alex is currently OOO. I will reopen the PR. Usually you should use the Grant Milestone Delivery repo, but since this isn’t a “normal” milestone delivery, you can also just include it in your application.

@gusiri the link you added to the application is broken, and https://github.com/splytcore/Splyt_Polkadot/tree/main/deliverables doesn't contain any deliverables.

@alxs Sorry for that. I will ping you right after fixing them and uploading the deliverables.

@gusiri are you still interested in this? The application was reopened a month ago now so you could add the deliverables.

@alxs Yes, Aleixo! We are very interested in this and we keep working on stuffs.
My Apologies for the late reply. We fixed the broken URL and also uploaded Milestone 1 - Deliverable 1, 2 and 3.

Deliverable 1. Survey on Polkadot NFT Projects
Deliverable 2. eNFT Reference Architecture
Deliverable 3. Dev Environment Setup

We are happy for feedbacks and we will update each deliverable based on the feedback.
For Deliverable 1 and 2, we will update them continuously while we are working on the next milestones.

@gusiri could you remove milestone 1 from the roadmap so it's clear that it won't be delivered as part of the grant? Feel free to include the survey and other deliverables in the background information or project details. I also suggest you remove milestone 6 as we're very unlikely to accept a milestone of such long duration.

@alxs Thank you so much for your kind feedback.
We removed milestone 1 and 6 as you recommended, and updated other related stuffs (e.g., milestone overview) accordingly :) .

Thanks. Could you also sign the CLA again?

@alxs Thank you so much :) Just signed the CLA again.


Add to campaign styles UI enhancements

Relates to issue https://github.com/silverstripe/silverstripe-framework/issues/6058

I just remember this isn't rebased, so I will do that shortly.

After rebasing I've noticed the file area add to campaign area need updating too. I possibly need to create an asset-admin branch.

Current coverage is 70.23% (diff: 100%)

Merging #6118 into master will not change coverage

@@             master      #6118   diff @@
==========================================
  Files           416        416
  Lines         35711      35711
  Methods        4688       4688
  Messages          0          0
  Branches          0          0
==========================================
  Hits          25083      25083
  Misses        10628      10628
  Partials          0          0

Powered by Codecov. Last update a08a854...050ba28

Requires AssetAdmin branch for add to campaign within the files area. https://github.com/silverstripe/silverstripe-asset-admin/pull/282

I've removed the specific styles for campaign admin so everything else should be generic to any modal.

It looks like you force-pushed over the fix I added to the linting issue.

I've re-pushed the fix and retested it. Everything is good to merge on green.

Behat tests run perfectly fine locally.


Update of documentation for HiOrg-Server delegated PAC4J authn (forward port)

Update of documentation for #3501 on head/master branch.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add FernFlower for Mixin Debugging

Tranformed classes will be decompiled and copied to ./run/.mixin.out/java.
This is the newest version I could find (from September 2020).

Care if i ask in where did you configure FF to save to ./run/.mixin.out/java?

I didn't configure it like that, SpongeMixins does it automatically.

Gotcha, seems good to me honestly.


My requests are called twices

I'm using laravel 5.1, I have a problem with my cURL request, the API is called twice.
I tried to execute the same code on a single .php file without laravel and everything is ok.
I see on the web that may come from the mod_rewrite rules because of parameters but I don't know how check that.
My function look like this :
$url = 'http://api.com/api.asmx/deepSearchCreate';
$ch = curl_init($url);

curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, 'apikey=API_KEY&search='.strip_tags(trim($article->contenu)).'&source=&searchid=');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);

$response = curl_exec($ch);
curl_close($ch);

$xml = simplexml_load_string($response, 'SimpleXMLElement', LIBXML_NOCDATA);
$json = json_encode($xml);
$array = json_decode($json, TRUE);

$id = $array['collection']['@attributes']['id'];

Httacces :
<IfModule mod_headers.c>
    <FilesMatch "\.(eot|font.css|otf|ttc|ttf|woff)$">
        Header set Access-Control-Allow-Origin "*"
    </FilesMatch>
</IfModule>

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews
    </IfModule>

    RewriteEngine On

    # Deny access to framework directories
    RewriteRule ^(app/|bootstrap/|config/|database/|resources/|storage/tests|vendor/) - [R=404,L,NC]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)/$ /$1 [L,R=301]

    # And dot files/folders (for example .env)
    RedirectMatch 404 /\..*$

    # Handle Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

I'm sorry, but I don't see what this has to do with Laravel

I tried to execute the same code on a single .php file without laravel and everything is ok.

Please ask on the forums. To be a bit blunt, I'm afraid this is an error in your code.


Refactor waitUntilTasks from CustomEvent::sendRpc.

Using waitUntilTasks in sendRpc is a footgun as you might depend on a request to the rpc server that will happen complete after the request has been responded to and the client closes the connection causing a waitUntilTasks is not empty error.
This PR and the internal PR fix any remaining usages of waitUntilTasks and finally refactors waitUntilTasks out of the code.
This PR is targeted at https://github.com/cloudflare/workerd/pull/2863 to make reviewing them easier. I will either merge train them or merge one and rebase depending on review process.

Be sure to run the internal CI on these changes. The public tests don't exercise this very much.

Be sure to run the internal CI on these changes. The public tests don't exercise this very much.

Yes, of course, there’s a matching internal PR 😁


Cluster animation slowing down the browser. It also takes much time.

OS: Windows 10
Browser: Firefox

Cluster animation becomes useless now. It takes too much time to load and animate. It also slows the browser down. Switching between the tabs sometimes does not work.
It will be very good if you improve it.

@jeremyphilemon @JunaidBabu @sudevschiz Kindly check it. It is indeed getting very slow.

Thanks for reporting!
Please file issues about the cluster at https://github.com/someshkar/covid19india-cluster


Follow a user/artist/playlist is not implemented

It would be nice to be able to follow users/artists/playlists.
https://developer.spotify.com/web-api/console/put-playlist-followers/
Is there a work around that will allow me to do this while continuing to use the spotify-web-api-java?

Hey @coreygarvey! While this isn't added to this library, you could absolutely make the request yourself since it's basically a HTTP request to Spotify's Web API using an access token of your choice. Read more about the request that this Java client is making here.

I'll implement this in v2. Stay tuned!

I'll close this. Please follow #102 for updates.

Version 2.0.0-RC1 was just released.


[Feature] support google gemma

Motivation
as titled
Related resources
huggingface: https://huggingface.co/google/gemma-7b-it
tech report: https://storage.googleapis.com/deepmind-media/gemma/gemma-report.pdf
blog: https://blog.google/technology/developers/gemma-open-models/
vllm pr: https://github.com/vllm-project/vllm/pull/2964
Additional context
No response

Gemma in PyTorch: https://github.com/google/gemma_pytorch


Good Article - Some Issues

Good article in general.   However, your use of the terms "Password" protection in the decision trees to refer to the Leaked Credential report is horrible - most people use the term for the use of a password (as opposed to anonymous access).
Also, in my opinion the decision trees places the "password protection / leaked credentials" feature very early (and therefore pivotally) in the decision tree , when it feels like a frankly "nice to have" feature for most enterprises who would consider the password policies, advanced authentication requirements, and DR features FAR more important a decision (and therefore should probably be earlier in the process)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 74a7839e-3be4-a6b8-10ac-addc1285d0a6
Version Independent ID: 11a6d260-6e5e-0434-5503-198285446c2a
Content: Choose the right authentication method for your Azure AD hybrid identity solution
Content Source: articles/security/azure-ad-choose-authn.md
Service: active-directory
GitHub Login: @martincoetzer
Microsoft Alias: martincoetzer

@PeteB-UK Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@Peter-UK. This is great feedback, we are looking at updating the questions. The first question is indeed very important and determine if a customer should choose Password Hash Sync, hence the reason why we ask "Do you want to do cloud authentication....?". Cloud authentication comes in 2 flavors and only PHS offers password protection. An alternative first question would be "Do you want to cloud authentication without on-premises password verification and policy enforcement?" It is a bit long and sounds bad. We will discuss this internally a bit more to get better wording.
#please-close


Issue running nvm use command

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
When I run nvm dev it says it doesnt exist!
.bru file to reproduce the bug
No response
Screenshots/Live demo link
It says something like nvm is not recognized by cmd

Hey @RikhiSingh,
Could you please confirm whether you're able to set up Bruno locally?
The instructions in the contributing.md file should be clear for setting up Bruno. If you're encountering the issue with nvm dev saying it doesn't exist, it might be worth double-checking your nvm installation.
If you're still having trouble, would you mind sharing a screenshot or a quick video?

Yeah I got some help from youtube, apparently my system was missing nvm, so it could be installed using nvm install or from its official repo on GitHub.
I also added the same in contributing!


Error when 'npm run production'

Help, pleace... Whole day headache :(

Laravel Mix Version:
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>(git://github.com/wffranco/vue-strap.git#02b471c8b99a509ff4f9e6064495133288c781fe)

Node Version: v6.10.3

NPM Version:v3.10.10

OS: MACOs Siera

Description: Error when 'npm run production'
> npm ERR! Darwin 16.5.0
> npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "production"
> npm ERR! node v6.10.3
> npm ERR! npm  v3.10.10
> npm ERR! code ELIFECYCLE
> npm ERR! @ production: `cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
> npm ERR! Exit status 2
> npm ERR!
> npm ERR! Failed at the @ production script 'cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
> npm ERR! Make sure you have the latest version of node.js and npm installed.
> npm ERR! If you do, this is most likely a problem with the  package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
> npm ERR! You can get information on how to open an issue for this project with:
> npm ERR!     npm bugs
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR!     npm owner ls
> npm ERR! There is likely additional logging output above.
>
> npm ERR! Please include the following file with any support request:
> npm ERR!     /Users/valentin/Desktop/www/jobs/npm-debug.log

===========
npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'production' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'preproduction', 'production', 'postproduction' ]
5 info lifecycle @~preproduction: @
6 silly lifecycle @~preproduction: no script for preproduction, continuing
7 info lifecycle @~production: @
8 verbose lifecycle @~production: unsafe-perm in lifecycle true
9 verbose lifecycle @~production: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/valentin/Desktop/www/jobs/node_modules/.bin:/Applications/MAMP/bin/php/php7.0.15/bin:vendor/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/valentin/.composer/vendor/bin:/Users/valentin/bin:/Users/valentin/.composer/vendor/bin
10 verbose lifecycle @~production: CWD: /Users/valentin/Desktop/www/jobs
11 silly lifecycle @~production: Args: [ '-c',
11 silly lifecycle   'cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js' ]
12 silly lifecycle @~production: Returned: code: 2  signal: null
13 info lifecycle @~production: Failed to exec production script
14 verbose stack Error: @ production: `cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
14 verbose stack Exit status 2
14 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:886:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid @
16 verbose cwd /Users/valentin/Desktop/www/jobs
17 error Darwin 16.5.0
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "production"
19 error node v6.10.3
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error @ production: `cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
22 error Exit status 2
23 error Failed at the @ production script 'cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the  package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Update your cross-env and see if it works?

Nope :(

same here just installed

@lotestudio
I fixed it by adding this to a newly created file .babelrc
{"presets": [ ["env", { "targets": { "uglify": false } }] ]}

Do you use Yarn or npm shrinkwrap by any chance?
It may be that some locked dependencies haven't updated properly.
I had ELIFECYCLE error after upgrading to 0.12, Then if I recall correctly I performed the following sequence of actions:
yarn remove laravel-mix
yarn add laravel-mix
yarn remove cross-env
yarn add cross-env

Weirdly, the issue was gone after purging the old cross-env.

@adiachenko I use npm, but will try the sequence.
@msonowal same with with watch and production.

Hm...I've found that laravel notification  in upper right corner produce warning: 'undefined/app.someversioncontrolnumber.js'.
Here is my webpack.mix.js:

const {mix} = require('laravel-mix');

mix.setPublicPath('public_html/');

mix.js('resources/assets/js/app.js', '/js')
    .sass('resources/assets/sass/app.scss', '/css')
    .sass('resources/assets/sass/pdf.scss', '/css');

mix.browserSync('jobs');

if (mix.config.inProduction) {
    mix.version();
}

The vue-strap library caused the problem. There is some files that babel can't compile for some reason. I've complied them manually with babel online compiler and everything work now. Still don't understand the problem entirety. The errors in command line is not so clear, but notification panel from laravel mix show me the exact error. Is there some explanation why mix can't compile these files?

putang ina niyong lahat mga bobo kayo

Hi @lotestudio .  Did you find any answer to your question "Is there some explanation why mix can't compile these files?" ?  Because I ran into the very same problem (for another vue npm package but basically the same problem).  I'm pretty sure that if I change the file by hand to make it readable in JS it'll work but I'd prefer not to touch to npm dependencies in my project and I can't figure out how to solve this O_O

@msonowal after spending hours and hours and hours with this issue, your solution fixed everything like a charm! Thanks a lot!


Feat: Implement API for Tracking Orphaned Tasks

Date: 15/11/2024
Developer Name: Vignesh B S

Issue Ticket Number
Closes Real-Dev-Squad/website-dashboard#888
Description
Implemented changes in tasks api for Tracking Orphaned Tasks

tasks?orphaned=true - Retrieves tasks assigned to users who have departed the Discord server.

Added test cases for the above api.
Documentation Updated?

[ ] Yes
[x] No

Under Feature Flag

[x] Yes
[ ] No

Database Changes

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Screenshots

Screenshot 1

Test Coverage

Screenshot 1

Additional Notes
PRD
Design Doc
Have moved the updateTaskStatusToDone function to models as it was directly interacts with the database and performing operations such as updating task documents. This was also causing circular dependency issues.

Splitting this PR into smaller parts for easier review. This PR will serve as the main split: https://github.com/Real-Dev-Squad/website-backend/pull/2267. Closing this PR as part of the process.


Tasks are displayed twice

When I display the tasks, they are displayed twice. Once with the date when they were created and once with the date when they are due. Is there a way to turn this off or is it intentional? I would like the tasks to be displayed only with their due date.

Is time sorting working for you??

No, that doesn't work either. I have sorted once in ascending order and once in descending order, both with the same result.


tag 0.2.2 release

The 0.2.2 release tag is missing on GitHub
please add the tag for the commit that was used for the latest pypi/conda release @marscher

I think you got confused by the difference between tags and releases. The latter is a (pretty useless) Github feature, which is mainly used to attach binaries to a tag. As we deploy this lib to pypi and conda-forge, it didn't seem to be relevant.

ohh sorry that was my mistake, somehow I didn't even look for the tag and only the releases.
I had one local pip install that was showing as 0.2.1+something but I'm not sure why.
Thanks for clearing that up :)


[Stdlib][Frontend][CMake] Remove SWIFT_DARWIN_ENABLE_STABLE_ABI_BIT option, make it permanently on.

@swift-ci please test

@compnerd @gottesmm @slavapestov

LGTM modulo the couple of questions.  Glad to see that you got around to that bit of review comments :-)

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - d7aaad32a28a9aeee5f2bcc9b6b69fcb5b9def10

Build failed
Swift Test OS X Platform
Git Sha - d7aaad32a28a9aeee5f2bcc9b6b69fcb5b9def10

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


Fixed a regression introduced in #5929

Coverage remained the same at 82.688% when pulling c339da7d224b2e6adfc55282f0ffc79f167338dd on bugfix/get-dist-path into b40e7ae6be1714380bf8eb5b4dc2828da2a40811 on release/3.4.x.

Coverage remained the same at 82.688% when pulling bff8e2bb84b47cfda158e0a8ce888ccdfbdd0380 on bugfix/get-dist-path into 0d25012fce3743130a4c94418c523faa568f2a76 on release/3.4.x.


Support React 17

Getting an error when trying to install:
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^16.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/react-tooltip-lite
npm ERR!   react-tooltip-lite@"*" from the root project

Here's a PR for this. Anyone minds sharing their thoughts on it?
https://github.com/bsidelinger912/react-tooltip-lite/pull/113


Revert "Add "select all" and "unselect all" to dropdown selects"

Reverts RedashCommunity/redash#39, as it clearly needs more work due to causing our CI to fail.

Reverts #39, as it clearly needs more work due to causing our CI to fail.

ok, i tested it. Just code style not pass.

Cool.  Yeah, if we get the code style testing to pass then we should be good. :smile:

I will fix it.

Thanks.  My head space is mostly in backend Go programming at the moment, so I'm not much use for Typescript + React changes for now. :smile:


Embed in existing Express app?

Would this be possible by replicating some of the server.js, iframe.html.js, & build?

This is a dev time tool. So having a it's own express seems fine to me.
What's the reason behind this decision?

@arunoda Our projects have DX baked into it.  npm start gives you both the public interface as well as an internal component playground + docs + private tools + dashboard, etc. (If authenticated. Otherwise, you only see the public portal).
We were evaluating using this project instead of our internal playground, which means having it available under http://localhost:3000/components.
(We dropped Cosmos as well, because a separate tool/process means it doesn't get used).

@ericclemmons Our idea with storybook is to develop without using the full app. Just the components once.
AFAIK: It works pretty well.
We are also building storybooks.io which allows to keep, comment and discuss storybooks for every commit in your app.

Seems like you need to find a way to display your storybook right inside your app. If that's the case, there's a much easy way. Follow this:

Use our static builder to build a static version of storybook.
Then use your express app to serve it in /components route.
You can create an automatic script to build the storybook for everytime you are deploying your app.

I think we have slightly different goals, so no fault of this project.
Thanks for the prompt responses. Beautiful project so far!

Ahh, I'm sorry to hear this :( I'm working on upgrading our company's custom component development workflow, too. I was hoping that, while I was at it, I could swap out our custom component preview tooling for the React Sandbox UI.
Unfortunately, while the core UI is in its own reusable module, I'd seemingly have to rewrite a bunch of the React and addon support myself. I was hoping that layer of React Sandbox would be decoupled from the server workflow, too, so I could embed it in our prod site and get shareability and extensibility for free. Ah, well; looks like we're better off sticking with our custom thing.
Anyway! I know my requirements are unusual, and I'm glad y'all are focusing your efforts on the primary use case. Thanks for making a cool thing! :)

@matchu because I have the same issue like you, you can try to deploy storybook on the same machine as your app, then serve in nginx under specific path storybook and in the storybook create symlink to the folder containing your components. The same with sass (if you use). Then it should work :) I will let you know if it works, because I plan to do the same.


A brief history of the metrics store - Towards Data Science Blog

URL: https://towardsdatascience.com/a-brief-history-of-the-metrics-store-28208ec8f6f1
Review (1-2 sentences): We haven't learned about feature store yet. But it won't stop us to read about Metric stores :)

Published in Digest #16.


Integrate WikiFile api to WikiFix

Improve WikiFix by using the WikiFile api to update the wiki pages

Commit https://github.com/tholzheim/wikirender/commit/48ddda310ac2e90fce316592d437635de9d1f381 integrates WikiFile into the export functionality

Commit https://github.com/tholzheim/wikirender/commit/42ca3d2f3f2641fad47b5d5604b77421ac189094 integrates WikiFile into the export functionality.

WikiFix still contains some topic specific methods
see https://github.com/tholzheim/wikirender/blob/e2ee791a1b6e8c55b131582400aaef6bd5f7b727/wikifile/wikiFix.py#L22
should be moved to openresearch since a general use case for these methods is not given

Migrate the lod to csv and vice versa part to pyLoDStorage

see https://github.com/WolfgangFahl/pyLoDStorage/issues/29 for csv to LoD conversion


not work in react 18 version any other pack suggestion

Upgraded package and sent and merge request I hope it will get merged soon.


🐛 [Bug] Incorrect Documentation page

This page has several issues with the provided examples:
https://pytorch.org/TensorRT/user_guide/saving_models.html

In the examples, an optional parameter is passed before a non-optional parameter which is invalid python. This issue also appears here: https://github.com/pytorch/TensorRT/blob/7f14221ca532d8c42daa43b74fe600ebb27e1537/docsrc/user_guide/saving_models.rst#L20
The a) example does not work because the default from torch_tensorrt.compile is to use an output_format of ExportedProgram.
This line is no longer valid: trt_exp_program = torch_tensorrt.dynamo.export(trt_gm, images)
torch.jit.trace should not be used when specifying the correct output format. The corrected code should be as follows:
`
model = MyModel().eval().cuda()
inputs = [torch.randn((1, 3, 224, 224)).cuda()]
trt_gm = torch_tensorrt.compile(model, ir="dynamo", inputs=inputs, output_format="torchscript") # Output is a torch.fx.GraphModule
torch.jit.save(trt_gm, "trt_model.ts")

Later, you can load it and run inference
model = torch.jit.load("trt_model.ts").cuda()
model(*inputs)
`

@Skier23 thank you for your code example!
How to load trt_model.ts on triton inference server? With platform: "pytorch_libtorch" in config.pbtxt config file, it expects model file to be in .pt format in model_repository. Is there a way to save tensorrt compiled file in .pt format?


Is it works faster then JavaScript?

I didn’t see any benchmarks, would it work faster then usual JavaScript in V8?

The short answer is no, currently WebAssembly doesn't allow dynamic code generation, which is needed for the traditional multi-tier compiler architectures like V8, on top of that QuickJS only offers an interpreter, which will be generally slower than a baseline and/or optimizing compiler. See https://github.com/bytecodealliance/javy/issues/480 for more details.

Is it possible to use v8 or other jit compiler instead of Quick JS?

It's definitely possible to use another JavaScript engine, but relying on any of the JIT compilers used on those engines is not trivial; it's important to consider that since WebAssembly doesn't allow for dynamic code generation at runtime none of these JIT compilers will work out of the box in the same way that they work on non-Wasm environments. If you're curious about the details, I recommend reading: https://wingolog.org/archives/2022/08/18/just-in-time-code-generation-within-webassembly.
I'll go ahead and close this issue since the main question was already addressed, but feel free to continue the discussion.

Thanks for a quick response and good article, I just find out there is a library based on SpiderMonkey https://github.com/bytecodealliance/componentize-js, but it looks like it also want be very fast