text:
"ThinkingSphinx::SphinxError - unknown local index 'index_name' in search request" while indexing

Sphinx 3.3.1
thinking-sphinx 5.5.1
Ruby 3.2.2
Rails 7.0.8
Not sure if this is a sphinx thing or just a "that's just how it works" thing...
I have a cron job that periodically updates some data and then runs rake ts:index. Sometimes when this runs, the searches on my site receive a ThinkingSphinx::SphinxError exception: unknown local index 'index_name' in search request. This seems to only last a second or two and then everything's back to normal.
Here's the log of my reindexing script:
Starting at Sat Dec 16 03:00:01 PM UTC 2023
Reindexing at Sat Dec 16 03:00:43 PM UTC 2023
(in /www/greasyfork/releases/20231214004847)
Generating configuration to /www/greasyfork/shared/config/production.sphinx.conf
Sphinx 3.3.1 (commit b72d67b)
Copyright (c) 2001-2020, Andrew Aksyonoff
Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file '/www/greasyfork/shared/config/production.sphinx.conf'...
indexing index 'script_core'...
collected 63851 docs, 34.8 MB
sorted 6.6 Mhits, 100.0% done
total 63851 docs, 34.77 Mb
total 7.0 sec, 4.933 Mb/sec, 9058 docs/sec
indexing index 'script_delta'...
collected 1 docs, 0.0 MB
sorted 0.0 Mhits, 100.0% done
total 1 docs, 2.0 Kb
total 0.0 sec, 460.0 Kb/sec, 225 docs/sec
skipping non-plain index 'script'...
rotating indices: successfully sent SIGHUP to searchd (pid=2226406).
Done at Sat Dec 16 03:00:52 PM UTC 2023

searchd.log from this time:
[Sat Dec 16 15:00:48.951 2023] [2226410] rotating index 'script_core': started
[Sat Dec 16 15:00:48.956 2023] [2226410] rotating index 'script_core': success

Stack trace of a search request:
Mysql2::Error: unknown local index 'script_core' in search request (Mysql2::Error)
  from mysql2 (0.5.5) lib/mysql2/client.rb:151:in `_query'
  from mysql2 (0.5.5) lib/mysql2/client.rb:151:in `block in query'
  from mysql2 (0.5.5) lib/mysql2/client.rb:150:in `handle_interrupt'
  from mysql2 (0.5.5) lib/mysql2/client.rb:150:in `query'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection/mri.rb:22:in `results_for'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection/client.rb:65:in `perform'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection/client.rb:51:in `check_and_perform'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection/client.rb:36:in `query_all'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/search/batch_inquirer.rb:19:in `block in results'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection.rb:42:in `block in take'
  from innertube (1.1.0) lib/innertube.rb:138:in `take'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection.rb:40:in `take'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/search/batch_inquirer.rb:18:in `results'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/inquirer.rb:11:in `block in call'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/logger.rb:5:in `log'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/inquirer.rb:10:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/geographer.rb:13:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/sphinxql.rb:16:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/valid_options.rb:9:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/stale_id_filter.rb:12:in `call'
  from middleware (0.1.0) lib/middleware/runner.rb:31:in `call'
  from middleware (0.1.0) lib/middleware/builder.rb:102:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/search.rb:95:in `populate'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/active_record/base.rb:68:in `merge_search'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/active_record/base.rb:33:in `search'
  from app/controllers/concerns/script_listings.rb:309:in `load_scripts_for_index'
  from app/controllers/concerns/script_listings.rb:32:in `block (3 levels) in index'
  from app/controllers/concerns/page_cache.rb:17:in `block in cache_page'
  from activesupport (7.0.8) lib/active_support/cache.rb:809:in `block in save_block_result_to_cache'
  from activesupport (7.0.8) lib/active_support/cache.rb:783:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from activesupport (7.0.8) lib/active_support/cache.rb:783:in `instrument'
  from activesupport (7.0.8) lib/active_support/cache.rb:808:in `save_block_result_to_cache'
  from activesupport (7.0.8) lib/active_support/cache.rb:338:in `fetch'
  from app/controllers/concerns/page_cache.rb:15:in `cache_page'
  from app/controllers/concerns/script_listings.rb:28:in `block (2 levels) in index'
  from actionpack (7.0.8) lib/action_controller/metal/mime_responds.rb:214:in `respond_to'
  from app/controllers/concerns/script_listings.rb:25:in `index'
  from actionpack (7.0.8) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
  from actionpack (7.0.8) lib/abstract_controller/base.rb:215:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/rendering.rb:165:in `process_action'
  from actionpack (7.0.8) lib/abstract_controller/callbacks.rb:234:in `block in process_action'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:118:in `block in run_callbacks'
  from actiontext (7.0.8) lib/action_text/rendering.rb:20:in `with_renderer'
  from actiontext (7.0.8) lib/action_text/engine.rb:69:in `block (4 levels) in <class:Engine>'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `instance_exec'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `block in run_callbacks'
  from sentry-rails (5.13.0) lib/sentry/rails/controller_transaction.rb:28:in `block in sentry_around_action'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:102:in `with_child_span'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:476:in `with_child_span'
  from sentry-rails (5.13.0) lib/sentry/rails/controller_transaction.rb:14:in `sentry_around_action'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `block in run_callbacks'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:138:in `run_callbacks'
  from actionpack (7.0.8) lib/abstract_controller/callbacks.rb:233:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/rescue.rb:23:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/instrumentation.rb:67:in `block in process_action'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from actionpack (7.0.8) lib/action_controller/metal/instrumentation.rb:66:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/params_wrapper.rb:259:in `process_action'
  from activerecord (7.0.8) lib/active_record/railties/controller_runtime.rb:27:in `process_action'
  from actionpack (7.0.8) lib/abstract_controller/base.rb:151:in `process'
  from actionview (7.0.8) lib/action_view/rendering.rb:39:in `process'
  from actionpack (7.0.8) lib/action_controller/metal.rb:188:in `dispatch'
  from actionpack (7.0.8) lib/action_controller/metal.rb:251:in `dispatch'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:32:in `serve'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:50:in `block in serve'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:32:in `each'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:32:in `serve'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:852:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/builder.rb:44:in `call'
  from rack-attack (6.6.1) lib/rack/attack.rb:127:in `call'
  from warden (1.2.9) lib/warden/manager.rb:36:in `block in call'
  from warden (1.2.9) lib/warden/manager.rb:34:in `catch'
  from warden (1.2.9) lib/warden/manager.rb:34:in `call'
  from rack (2.2.8) lib/rack/tempfile_reaper.rb:15:in `call'
  from rack (2.2.8) lib/rack/etag.rb:27:in `call'
  from rack (2.2.8) lib/rack/conditional_get.rb:27:in `call'
  from rack (2.2.8) lib/rack/head.rb:12:in `call'
  from actionpack (7.0.8) lib/action_dispatch/http/permissions_policy.rb:38:in `call'
  from actionpack (7.0.8) lib/action_dispatch/http/content_security_policy.rb:36:in `call'
  from rack (2.2.8) lib/rack/session/abstract/id.rb:266:in `context'
  from rack (2.2.8) lib/rack/session/abstract/id.rb:260:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/cookies.rb:704:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:99:in `run_callbacks'
  from actionpack (7.0.8) lib/action_dispatch/middleware/callbacks.rb:26:in `call'
  from sentry-rails (5.13.0) lib/sentry/rails/rescued_exception_interceptor.rb:12:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/debug_exceptions.rb:28:in `call'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:28:in `block (2 levels) in call'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:251:in `with_session_tracking'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:387:in `with_session_tracking'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:19:in `block in call'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:59:in `with_scope'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:367:in `with_scope'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:18:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/show_exceptions.rb:29:in `call'
  from railties (7.0.8) lib/rails/rack/logger.rb:40:in `call_app'
  from railties (7.0.8) lib/rails/rack/logger.rb:25:in `block in call'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:99:in `block in tagged'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:37:in `tagged'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:99:in `tagged'
  from railties (7.0.8) lib/rails/rack/logger.rb:25:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/remote_ip.rb:93:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/request_id.rb:26:in `call'
  from rack (2.2.8) lib/rack/method_override.rb:24:in `call'
  from rack (2.2.8) lib/rack/runtime.rb:22:in `call'
  from activesupport (7.0.8) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/executor.rb:14:in `call'
  from rack (2.2.8) lib/rack/sendfile.rb:110:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/host_authorization.rb:138:in `call'
  from railties (7.0.8) lib/rails/engine.rb:530:in `call'
  from puma (6.3.1) lib/puma/configuration.rb:270:in `call'
  from puma (6.3.1) lib/puma/request.rb:100:in `block in handle_request'
  from puma (6.3.1) lib/puma/thread_pool.rb:344:in `with_force_shutdown'
  from puma (6.3.1) lib/puma/request.rb:99:in `handle_request'
  from puma (6.3.1) lib/puma/server.rb:443:in `process_client'
  from puma (6.3.1) lib/puma/server.rb:245:in `block in run'
  from puma (6.3.1) lib/puma/thread_pool.rb:151:in `block in spawn_thread'

ThinkingSphinx::QueryExecutionError: unknown local index 'script_core' in search request - SELECT *, weight() myweight, LENGTH(site_application_id) AS site_count FROM `script_core`, `script_delta` WHERE `sensitive` = 1 AND `script_type` = 1 AND `locale` = 187 AND `site_application_id` = 39369 AND `available_as_js` = 1 AND `sphinx_deleted` = 0 ORDER BY `myweight` DESC, `daily_installs` DESC, `id` LIMIT 0, 50 OPTION cutoff=0, field_weights=(combined_text=10, author=5), ranker=expr('top(user_weight)'); SHOW META (ThinkingSphinx::QueryExecutionError)
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection/client.rb:70:in `rescue in perform'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection/client.rb:66:in `perform'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection/client.rb:51:in `check_and_perform'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection/client.rb:36:in `query_all'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/search/batch_inquirer.rb:19:in `block in results'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection.rb:42:in `block in take'
  from innertube (1.1.0) lib/innertube.rb:138:in `take'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection.rb:40:in `take'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/search/batch_inquirer.rb:18:in `results'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/inquirer.rb:11:in `block in call'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/logger.rb:5:in `log'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/inquirer.rb:10:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/geographer.rb:13:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/sphinxql.rb:16:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/valid_options.rb:9:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/stale_id_filter.rb:12:in `call'
  from middleware (0.1.0) lib/middleware/runner.rb:31:in `call'
  from middleware (0.1.0) lib/middleware/builder.rb:102:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/search.rb:95:in `populate'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/active_record/base.rb:68:in `merge_search'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/active_record/base.rb:33:in `search'
  from app/controllers/concerns/script_listings.rb:309:in `load_scripts_for_index'
  from app/controllers/concerns/script_listings.rb:32:in `block (3 levels) in index'
  from app/controllers/concerns/page_cache.rb:17:in `block in cache_page'
  from activesupport (7.0.8) lib/active_support/cache.rb:809:in `block in save_block_result_to_cache'
  from activesupport (7.0.8) lib/active_support/cache.rb:783:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from activesupport (7.0.8) lib/active_support/cache.rb:783:in `instrument'
  from activesupport (7.0.8) lib/active_support/cache.rb:808:in `save_block_result_to_cache'
  from activesupport (7.0.8) lib/active_support/cache.rb:338:in `fetch'
  from app/controllers/concerns/page_cache.rb:15:in `cache_page'
  from app/controllers/concerns/script_listings.rb:28:in `block (2 levels) in index'
  from actionpack (7.0.8) lib/action_controller/metal/mime_responds.rb:214:in `respond_to'
  from app/controllers/concerns/script_listings.rb:25:in `index'
  from actionpack (7.0.8) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
  from actionpack (7.0.8) lib/abstract_controller/base.rb:215:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/rendering.rb:165:in `process_action'
  from actionpack (7.0.8) lib/abstract_controller/callbacks.rb:234:in `block in process_action'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:118:in `block in run_callbacks'
  from actiontext (7.0.8) lib/action_text/rendering.rb:20:in `with_renderer'
  from actiontext (7.0.8) lib/action_text/engine.rb:69:in `block (4 levels) in <class:Engine>'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `instance_exec'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `block in run_callbacks'
  from sentry-rails (5.13.0) lib/sentry/rails/controller_transaction.rb:28:in `block in sentry_around_action'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:102:in `with_child_span'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:476:in `with_child_span'
  from sentry-rails (5.13.0) lib/sentry/rails/controller_transaction.rb:14:in `sentry_around_action'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `block in run_callbacks'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:138:in `run_callbacks'
  from actionpack (7.0.8) lib/abstract_controller/callbacks.rb:233:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/rescue.rb:23:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/instrumentation.rb:67:in `block in process_action'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from actionpack (7.0.8) lib/action_controller/metal/instrumentation.rb:66:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/params_wrapper.rb:259:in `process_action'
  from activerecord (7.0.8) lib/active_record/railties/controller_runtime.rb:27:in `process_action'
  from actionpack (7.0.8) lib/abstract_controller/base.rb:151:in `process'
  from actionview (7.0.8) lib/action_view/rendering.rb:39:in `process'
  from actionpack (7.0.8) lib/action_controller/metal.rb:188:in `dispatch'
  from actionpack (7.0.8) lib/action_controller/metal.rb:251:in `dispatch'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:32:in `serve'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:50:in `block in serve'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:32:in `each'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:32:in `serve'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:852:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/builder.rb:44:in `call'
  from rack-attack (6.6.1) lib/rack/attack.rb:127:in `call'
  from warden (1.2.9) lib/warden/manager.rb:36:in `block in call'
  from warden (1.2.9) lib/warden/manager.rb:34:in `catch'
  from warden (1.2.9) lib/warden/manager.rb:34:in `call'
  from rack (2.2.8) lib/rack/tempfile_reaper.rb:15:in `call'
  from rack (2.2.8) lib/rack/etag.rb:27:in `call'
  from rack (2.2.8) lib/rack/conditional_get.rb:27:in `call'
  from rack (2.2.8) lib/rack/head.rb:12:in `call'
  from actionpack (7.0.8) lib/action_dispatch/http/permissions_policy.rb:38:in `call'
  from actionpack (7.0.8) lib/action_dispatch/http/content_security_policy.rb:36:in `call'
  from rack (2.2.8) lib/rack/session/abstract/id.rb:266:in `context'
  from rack (2.2.8) lib/rack/session/abstract/id.rb:260:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/cookies.rb:704:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:99:in `run_callbacks'
  from actionpack (7.0.8) lib/action_dispatch/middleware/callbacks.rb:26:in `call'
  from sentry-rails (5.13.0) lib/sentry/rails/rescued_exception_interceptor.rb:12:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/debug_exceptions.rb:28:in `call'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:28:in `block (2 levels) in call'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:251:in `with_session_tracking'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:387:in `with_session_tracking'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:19:in `block in call'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:59:in `with_scope'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:367:in `with_scope'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:18:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/show_exceptions.rb:29:in `call'
  from railties (7.0.8) lib/rails/rack/logger.rb:40:in `call_app'
  from railties (7.0.8) lib/rails/rack/logger.rb:25:in `block in call'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:99:in `block in tagged'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:37:in `tagged'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:99:in `tagged'
  from railties (7.0.8) lib/rails/rack/logger.rb:25:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/remote_ip.rb:93:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/request_id.rb:26:in `call'
  from rack (2.2.8) lib/rack/method_override.rb:24:in `call'
  from rack (2.2.8) lib/rack/runtime.rb:22:in `call'
  from activesupport (7.0.8) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/executor.rb:14:in `call'
  from rack (2.2.8) lib/rack/sendfile.rb:110:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/host_authorization.rb:138:in `call'
  from railties (7.0.8) lib/rails/engine.rb:530:in `call'
  from puma (6.3.1) lib/puma/configuration.rb:270:in `call'
  from puma (6.3.1) lib/puma/request.rb:100:in `block in handle_request'
  from puma (6.3.1) lib/puma/thread_pool.rb:344:in `with_force_shutdown'
  from puma (6.3.1) lib/puma/request.rb:99:in `handle_request'
  from puma (6.3.1) lib/puma/server.rb:443:in `process_client'
  from puma (6.3.1) lib/puma/server.rb:245:in `block in run'
  from puma (6.3.1) lib/puma/thread_pool.rb:151:in `block in spawn_thread'

Innertube::Pool::BadResource: Innertube::Pool::BadResource (Innertube::Pool::BadResource)
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection.rb:46:in `rescue in block in take'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection.rb:41:in `block in take'
  from innertube (1.1.0) lib/innertube.rb:138:in `take'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/connection.rb:40:in `take'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/search/batch_inquirer.rb:18:in `results'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/inquirer.rb:11:in `block in call'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/logger.rb:5:in `log'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/inquirer.rb:10:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/geographer.rb:13:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/sphinxql.rb:16:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/valid_options.rb:9:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/middlewares/stale_id_filter.rb:12:in `call'
  from middleware (0.1.0) lib/middleware/runner.rb:31:in `call'
  from middleware (0.1.0) lib/middleware/builder.rb:102:in `call'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/search.rb:95:in `populate'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/active_record/base.rb:68:in `merge_search'
  from thinking-sphinx (5.5.1) lib/thinking_sphinx/active_record/base.rb:33:in `search'
  from app/controllers/concerns/script_listings.rb:309:in `load_scripts_for_index'
  from app/controllers/concerns/script_listings.rb:32:in `block (3 levels) in index'
  from app/controllers/concerns/page_cache.rb:17:in `block in cache_page'
  from activesupport (7.0.8) lib/active_support/cache.rb:809:in `block in save_block_result_to_cache'
  from activesupport (7.0.8) lib/active_support/cache.rb:783:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from activesupport (7.0.8) lib/active_support/cache.rb:783:in `instrument'
  from activesupport (7.0.8) lib/active_support/cache.rb:808:in `save_block_result_to_cache'
  from activesupport (7.0.8) lib/active_support/cache.rb:338:in `fetch'
  from app/controllers/concerns/page_cache.rb:15:in `cache_page'
  from app/controllers/concerns/script_listings.rb:28:in `block (2 levels) in index'
  from actionpack (7.0.8) lib/action_controller/metal/mime_responds.rb:214:in `respond_to'
  from app/controllers/concerns/script_listings.rb:25:in `index'
  from actionpack (7.0.8) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
  from actionpack (7.0.8) lib/abstract_controller/base.rb:215:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/rendering.rb:165:in `process_action'
  from actionpack (7.0.8) lib/abstract_controller/callbacks.rb:234:in `block in process_action'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:118:in `block in run_callbacks'
  from actiontext (7.0.8) lib/action_text/rendering.rb:20:in `with_renderer'
  from actiontext (7.0.8) lib/action_text/engine.rb:69:in `block (4 levels) in <class:Engine>'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `instance_exec'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `block in run_callbacks'
  from sentry-rails (5.13.0) lib/sentry/rails/controller_transaction.rb:28:in `block in sentry_around_action'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:102:in `with_child_span'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:476:in `with_child_span'
  from sentry-rails (5.13.0) lib/sentry/rails/controller_transaction.rb:14:in `sentry_around_action'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:127:in `block in run_callbacks'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:138:in `run_callbacks'
  from actionpack (7.0.8) lib/abstract_controller/callbacks.rb:233:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/rescue.rb:23:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/instrumentation.rb:67:in `block in process_action'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `block in instrument'
  from activesupport (7.0.8) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
  from activesupport (7.0.8) lib/active_support/notifications.rb:206:in `instrument'
  from actionpack (7.0.8) lib/action_controller/metal/instrumentation.rb:66:in `process_action'
  from actionpack (7.0.8) lib/action_controller/metal/params_wrapper.rb:259:in `process_action'
  from activerecord (7.0.8) lib/active_record/railties/controller_runtime.rb:27:in `process_action'
  from actionpack (7.0.8) lib/abstract_controller/base.rb:151:in `process'
  from actionview (7.0.8) lib/action_view/rendering.rb:39:in `process'
  from actionpack (7.0.8) lib/action_controller/metal.rb:188:in `dispatch'
  from actionpack (7.0.8) lib/action_controller/metal.rb:251:in `dispatch'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:32:in `serve'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:50:in `block in serve'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:32:in `each'
  from actionpack (7.0.8) lib/action_dispatch/journey/router.rb:32:in `serve'
  from actionpack (7.0.8) lib/action_dispatch/routing/route_set.rb:852:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:202:in `call!'
  from omniauth (2.1.1) lib/omniauth/strategy.rb:169:in `call'
  from omniauth (2.1.1) lib/omniauth/builder.rb:44:in `call'
  from rack-attack (6.6.1) lib/rack/attack.rb:127:in `call'
  from warden (1.2.9) lib/warden/manager.rb:36:in `block in call'
  from warden (1.2.9) lib/warden/manager.rb:34:in `catch'
  from warden (1.2.9) lib/warden/manager.rb:34:in `call'
  from rack (2.2.8) lib/rack/tempfile_reaper.rb:15:in `call'
  from rack (2.2.8) lib/rack/etag.rb:27:in `call'
  from rack (2.2.8) lib/rack/conditional_get.rb:27:in `call'
  from rack (2.2.8) lib/rack/head.rb:12:in `call'
  from actionpack (7.0.8) lib/action_dispatch/http/permissions_policy.rb:38:in `call'
  from actionpack (7.0.8) lib/action_dispatch/http/content_security_policy.rb:36:in `call'
  from rack (2.2.8) lib/rack/session/abstract/id.rb:266:in `context'
  from rack (2.2.8) lib/rack/session/abstract/id.rb:260:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/cookies.rb:704:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
  from activesupport (7.0.8) lib/active_support/callbacks.rb:99:in `run_callbacks'
  from actionpack (7.0.8) lib/action_dispatch/middleware/callbacks.rb:26:in `call'
  from sentry-rails (5.13.0) lib/sentry/rails/rescued_exception_interceptor.rb:12:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/debug_exceptions.rb:28:in `call'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:28:in `block (2 levels) in call'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:251:in `with_session_tracking'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:387:in `with_session_tracking'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:19:in `block in call'
  from sentry-ruby (5.13.0) lib/sentry/hub.rb:59:in `with_scope'
  from sentry-ruby (5.13.0) lib/sentry-ruby.rb:367:in `with_scope'
  from sentry-ruby (5.13.0) lib/sentry/rack/capture_exceptions.rb:18:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/show_exceptions.rb:29:in `call'
  from railties (7.0.8) lib/rails/rack/logger.rb:40:in `call_app'
  from railties (7.0.8) lib/rails/rack/logger.rb:25:in `block in call'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:99:in `block in tagged'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:37:in `tagged'
  from activesupport (7.0.8) lib/active_support/tagged_logging.rb:99:in `tagged'
  from railties (7.0.8) lib/rails/rack/logger.rb:25:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/remote_ip.rb:93:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/request_id.rb:26:in `call'
  from rack (2.2.8) lib/rack/method_override.rb:24:in `call'
  from rack (2.2.8) lib/rack/runtime.rb:22:in `call'
  from activesupport (7.0.8) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/executor.rb:14:in `call'
  from rack (2.2.8) lib/rack/sendfile.rb:110:in `call'
  from actionpack (7.0.8) lib/action_dispatch/middleware/host_authorization.rb:138:in `call'
  from railties (7.0.8) lib/rails/engine.rb:530:in `call'
  from puma (6.3.1) lib/puma/configuration.rb:270:in `call'
  from puma (6.3.1) lib/puma/request.rb:100:in `block in handle_request'
  from puma (6.3.1) lib/puma/thread_pool.rb:344:in `with_force_shutdown'
  from puma (6.3.1) lib/puma/request.rb:99:in `handle_request'
  from puma (6.3.1) lib/puma/server.rb:443:in `process_client'
  from puma (6.3.1) lib/puma/server.rb:245:in `block in run'
  from puma (6.3.1) lib/puma/thread_pool.rb:151:in `block in spawn_thread'

I would expect/hope that reindexing does not cause errors on things using the index.

Hi Jason - I think frustratingly, this might be an issue with Sphinx itself. To be honest, I'm a little surprised - the whole point of rotating indexes should be how Sphinx steps around this (only switching from the old to the new when the new is ready - ideally with no gaps! And yet…)
I have checked locally, and I'm quite sure that when this error crops up Thinking Sphinx removes the current connection to Sphinx from the pool, and then retries again (up to three times) using fresh connections to Sphinx.
If you wanted to try something yourself, I would suggest adding some retry logic around your search calls - and perhaps, try adding ThinkingSphinx::Connection.pool.clear before retrying. This should ensure Thinking Sphinx doesn't hold onto any existing connections.

authors: JasonBarnabe pat

repo: pat/thinking-sphinx


text:
Add trending searches method

Have you already thought about adding a "trending searches" method, like in the Python library you've linked? https://github.com/GeneralMills/pytrends#trending-searches

That could be added! Looks like it would take a bit of configuration changing since it requires POST vs GET, but definitely doable

Hi there ...
I need the trending search methods and would love to use your framework to implement these apis for the missing search(es). Do you mind if I add/participate on your project, this would be the ideal place for the method(s)?
Please let me know.  In the meanwhile I'll research what is necessary.
Regards,
Patrick JP
Colibry Consulting

@Colibry-Source That would be great. Would you be able to make PRs in?

Hi, sorry I don't understand what you mean  by 'PRs'?

Yup, pull requests

@Colibry-Source It looks like the python trending searches uses this URL with a POST method:
TRENDING_SEARCHES_URL = 'https://trends.google.com/trends/hottrends/hotItems'
Right now in utilities.js it's hard coded to always perform a GET so we would need to update this object to also take a method

There is also real time searches:
https://trends.google.com/trends/api/realtimetrends?hl=en-US&tz=300&cat=all&fi=0&fs=0&geo=US&ri=300&rs=20&sort=0

Thanks for bringing this to my attention. I'll add it to the api also.
PJP
Sent from BlueMail
On Dec 2, 2018, 13:34, at 13:34, Patrick Trasborg notifications@github.com wrote:

There is also real time searches:
https://trends.google.com/trends/api/realtimetrends?hl=en-US&tz=300&cat=all&fi=0&fs=0&geo=US&ri=300&rs=20&sort=0
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/pat310/google-trends-api/issues/99#issuecomment-443531056

Hi Patrick,
Just a quick update. I was able to implement both in a way that seems to
compliment the existing work. However, the returned data set for both
queries are very verbose. I'll provide some more info in the documentation
on how to use it. The real-time query search in particular will give around
8 results in detail, but will provide a list of 300 articles IDS that
represent trending information. I have no found a way to use theses
articles IDS to pull back more information if the 8 provided are not
enough. Unfortunately, I don't have the time to research this further at
the moment as I am behind in my own project that uses this information.  I
see somehow the official googletrends page is translating these to another
ID and them doing a 'post' call to retrieve more information with a whole
bunch of information sent that I have no idea how is gotten but I can
confirm that the info passed isn't present in the result set that was
provided by the initial google trend call. So there is a lookup "process"
that is happening that I haven't been able to identify. Perhaps Ill look at
the python version of these libraries (that seem to be broken also) to see
what was done in the past.
The next steps, once i have some down time would be to update the tests,
document and research more behavior about the needed parameters and then
you can approve and merge it back into the project.
I'll update my own repository with the preliminary code and you can give it
a look over.
Regards,
PJP
On Mon, Dec 3, 2018 at 4:12 PM Colibry Consulting <
colibryconsulting@gmail.com> wrote:

Yes, this is exactly what I'm using to implement. It fits nicely with the
framework you've created and as such I will avoid the extra work of
implementing post logic. I did not find a reference to the POST method you
talked about. I wanted to do some research to see if there was a difference
in results. I'll be moving ahead with the GET solution in the meanwhile.
On Sun, Dec 2, 2018 at 1:29 PM Patrick Trasborg notifications@github.com
wrote:

@Colibry-Source https://github.com/Colibry-Source I think we should
look into the daily trends
https://trends.google.com/trends/trendingsearches/daily?geo=US
endpoint, it would probably be easier to implement and might cover what
we're looking for.
It goes something like this:
https://trends.google.com/trends/api/dailytrends?hl=en-US&tz=300&geo=US&ns=15
Let me know what you think.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pat310/google-trends-api/issues/99#issuecomment-443530659,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApknalTaNj9lzxMyow2pICmdXsNPGgwBks5u1Bv1gaJpZM4Syjg7
.

The proposed source changes can be found here:
https://github.com/Colibry-Source/new-google-trends-api
You'd need to run the build process script via npm , and then use the outputted library to test the newer apis.
No documentation for it yet but here is my entry code that you can run with:
googleTrends.realTimeTrends({
geo: 'US',
category: 'all',
}, function(err, results) {
if (err) console.log('oh no error!', err);
else console.log(results);
});
googleTrends.dailyTrends({
trendDate: new Date('2018-12-15'),
geo: 'US',
}, function(err, results) {
if (err) {
console.log('oh no error!', err)
}else{
console.log(results);
}
});

Tests updates to come later but feel free to add feedback.

There is also real time searches: https://trends.google.com/trends/api/realtimetrends?hl=en-US&tz=300&cat=all&fi=0&fs=0&geo=US&ri=300&rs=20&sort=0

Thank you very much! I am just looking for this link!

source: gharchive/issue

authors: Colibry-Source HyperionZhou pat310 tobihagemann

license: mit

license_type: permissive

license_source: bigquery


text:
New feature: Jsonify

Hi again!
As I stated early this week (https://github.com/pathable/supermodel/pull/66), I want to share with you some modifications to Supermodel library which I miss on working in my day to day.
This time I bring you Jsonify options which will be very useful when serializing models to persist or use in templates.
PD: This branch includes some corrections and test fixing I made for newer versions of Backbone.js. I made a pull request formerly. (https://github.com/pathable/supermodel/pull/65)
Jsonify
We sometimes need that relationships defined among models are also parsed when running "toJSON" function. Thus, I have brought to you the possibility to configure which relationships you want to be serialized. Further, you are also enabled to configure which attributes or associations to include or exclude in the "toJSON" method output.
Global configuration
You may set up a default behaviour to the "toJSON" function.
defaultInJson
Boolean. Set to true to serialize all associations by default when jsonify.
cidInJson
Boolean. A value of true includes cid attribute in json output.
Example
_.extend(Supermodel.configure, {
  defaultInJson: true, // A true value serializes all associations when jsonify
  cidInJson: false // whether or not include cid in object response
});

Local configuration
You may have the neccesity to configure serialization specifically. To do so, you are enable to do it by function parameter, model and association level. If a local configuration does not include some association, the default value defined in the global configuration will be used.
Configuration by parameter
"toJSON" function has been altered to accept options to control output and relationship serialization. This configuration method could be very useful to distingish serialization for persisting or templating processes.
The options that are able to be passed to model.toJSON([options]) are described below:
includeInJson
String or String[]. Returns the object which represents the model but only picks the provided attribute/s and relation/s.
excludeInJson
String or String[]. Returns the object which represents the model but omits the provided attribute/s and association/s.
assocInJson
Object representing:
{associationName : configuration}
Configuration may accept a boolean, a string or an array referencing a model's attribute/s or association/s, or an object.

Boolean. Set to true to serialize the related model/s and the full set of attributes and associations. In case of false, the relationship is not be serialized.
String. Represents a single attribute or association. Serializes the related model/s and returns an object which includes such attribute or association.
String[]. Represents a set of attributes and associations. Serializes the related model/s and returns an object which includes such set of attributes or associations.
Object. Serializes the related model/s and represents options to include or exclude attributes and associations.

includeInJson. String or String[].  Returns an object which includes the provided attribute/s and association/s.
excludeInJson. String or String[]. Returns an object which omits the provided attribute/s and association/s.

Example
// User has one Settings
var user = User.create({
  id: 1,
  name: "Peter"
});
var settings = Settings.create({
  id: 1,
  notifications: true
});

user.settings(settings);

user.toJSON({
  excludeInJson: "id",
  assocInJson: {
    settings: true
  }
}); // outputs {name: "Peter", settings_id: 1, settings: {notifications: true}}

Configuration by model
When you are defining models, you may set up the serialize configuration as well.
Example
var User = Supermodel.Model.extend({
  assocInJson: {
    settings: false // Set configuration at model level
  }
});
var Settings = Supermodel.Model.extend();

User.has().one('settings', {
  model: Settings,
  inverse: 'user'
});

var settings = Settings.create({id: 1});

var user = User.create({
  id: 1,
  name: "Peter",
  settings_id: 1
});

user.toJSON(); // outputs {id: 1, name: "Peter", settings_id: 1}

Configuration by association
You may set up the serialize configuration when you are defining associations.
Example
User.has().one('settings', {
  model: Settings,
  inverse: 'user',
  assocInJson: true // Set configuration at association level
});

user.toJSON(); // outputs {id: 1, name: "Peter", settings_id: 1, settings: {id: 1}}

Thank you! Sorry for the delay, will be reviewing this shortly.

I have just checked that this feature is an extended version of  (https://github.com/pathable/supermodel/pull/61) recently pull request accepted.

source: gharchive/pull-request

authors: Gywem flippyhead

repo: pathable/supermodel


text:
Getting missing id_token error when refreshing tokens

Hello,
I am getting this error from the library when I try to refresh the tokens:
Required option not passed: "id_token"
I logged apple's response to see how it looks and that parameter is actually not returned:
[
  'access_token' => 'THE_TOKEN',
  'token_type' => 'Bearer',
  'expires_in' => 3600,
]

Does this id_token parameter need to be required by the AppleAccessToken class?
My call to refresh the token looks like this:
const AUTH_CODE_GRANT = 'authorization_code';
$token = $appleSignIn->getAccessToken(
    self::AUTH_CODE_GRANT,
    ['code' => $signInData->getCode()]
);

// the next object will be persisted:
$refreshToken = new RefreshToken($token->getRefreshToken(), $token->getExpires());

// After I get the persisted token I refresh it like this
const REFRESH_TOKEN_GRANT = 'refresh_token';
$appleSignIn->getAccessToken(self::REFRESH_TOKEN_GRANT, [
    'refresh_token' => $refreshToken->getToken(),
]);
// When doing the previous call I get the id_token option error.

Yes @mcustiel thank you.
You're right. I added a test case for it and created a new version.

authors: mcustiel patrickbussmann

license: MIT

license_source: github-api


text:
Initial scroll in ChartScrollState not handled properly

Describe the bug
It looks like InitialScroll setting is handled incorrectly.
Module

[ ] compose
[ ] views
[ ] compose-m2
[ ] compose-m3
[x] core (select if none of the above apply)

To reproduce
create lineChart, use ChartScrollSpec with initialScroll = InitialScroll.End
Expected behavior
Chart is scrolled to the end.
Android versions
Not version specific bug
Comment
I believe there is something wrong with com.patrykandpatrick.vico.compose.chart.scroll.ChartScrollState#handleInitialScroll. Property initialScrollHandled is not reset when maxValue is updated. Initially maxValue is 0 (handleIntialScroll is performed), and when maxValue is updated to something non-zero then update of value is skipped.
There is a chance that I'm doing something wrong on my side (as this part is not well documented and I'm beginner regarding JetPack Compose).

Hello! I’ve followed the steps listed under “To reproduce,” but no unexpected behavior can be observed. Would you be able to provide a minimal reproducible example?

This is quick and dirty example. I just found that the issue is caused by values coming from mutable state from ViewModel, so it is most likely some kind of misunderstanding of JetPack Compose on my side.
See fragment
// this causes the issue
val values by viewModel.measurements

// this works
// val values = sampleValues

in this example
import androidx.compose.animation.core.spring
import androidx.compose.foundation.layout.Column
import androidx.compose.foundation.layout.height
import androidx.compose.material3.MaterialTheme
import androidx.compose.runtime.Composable
import androidx.compose.runtime.MutableState
import androidx.compose.runtime.getValue
import androidx.compose.runtime.mutableStateOf
import androidx.compose.ui.Modifier
import androidx.compose.ui.tooling.preview.Preview
import androidx.compose.ui.unit.dp
import androidx.lifecycle.ViewModel
import androidx.lifecycle.viewModelScope
import androidx.lifecycle.viewmodel.compose.viewModel
import com.patrykandpatrick.vico.compose.axis.horizontal.bottomAxis
import com.patrykandpatrick.vico.compose.axis.vertical.startAxis
import com.patrykandpatrick.vico.compose.chart.Chart
import com.patrykandpatrick.vico.compose.chart.line.lineChart
import com.patrykandpatrick.vico.compose.chart.scroll.rememberChartScrollSpec
import com.patrykandpatrick.vico.compose.chart.scroll.rememberChartScrollState
import com.patrykandpatrick.vico.core.chart.values.AxisValuesOverrider
import com.patrykandpatrick.vico.core.entry.ChartEntryModel
import com.patrykandpatrick.vico.core.entry.FloatEntry
import com.patrykandpatrick.vico.core.entry.entryModelOf
import com.patrykandpatrick.vico.core.scroll.AutoScrollCondition
import com.patrykandpatrick.vico.core.scroll.InitialScroll
import kotlinx.coroutines.delay
import kotlinx.coroutines.launch

class FixedStepXModelDecorator(
    private val constantStepX: Float,
    decoratedModel: ChartEntryModel,
) :
    ChartEntryModel by decoratedModel {
    override val xStep: Float
        get() = constantStepX
}

private val sampleValues = (0..100).map {
    FloatEntry(it.toFloat(), kotlin.math.sin(it.toDouble()).toFloat() * 100)
}

class ChartTestViewModel : ViewModel() {
    val measurements: MutableState<List<FloatEntry>> = mutableStateOf(emptyList())
    init {
        viewModelScope.launch {
            delay(1000L)
            measurements.value = sampleValues
        }
    }
}

@Preview
@Composable
fun ChartTest(viewModel: ChartTestViewModel = viewModel()) {

    // this causes the issue
    val values by viewModel.measurements

    // this works
    // val values = sampleValues

    val chartEntryModel: ChartEntryModel = FixedStepXModelDecorator(5f, entryModelOf(
        values
    ))

    val chartScrollSpec = rememberChartScrollSpec(
        isScrollEnabled = true,
        initialScroll = InitialScroll.End,
        autoScrollCondition = AutoScrollCondition.OnModelSizeIncreased,
        autoScrollAnimationSpec = spring()
    )

    val chartScrollState = rememberChartScrollState()

    Column {
        val lineColor = MaterialTheme.colorScheme.primary
        Chart(
            chart = lineChart(
                axisValuesOverrider = AxisValuesOverrider.fixed(
                    minY = 0f, maxY = 100f
                ),
            ),
            model = chartEntryModel,
            startAxis = startAxis(
                maxLabelCount = 5,
                valueFormatter = { value, _ ->
                    "${value.toInt()}%"
                }
            ),
            bottomAxis = bottomAxis(
                valueFormatter = { value, _ ->
                    value.toString()
                }
            ),
            modifier = Modifier.height(200.dp),
            chartScrollSpec = chartScrollSpec,
            chartScrollState = chartScrollState,
            isZoomEnabled = true,
        )
    }
}

Thank you! The chart is empty at first. On the chart’s creation, ChartScrollState#value is correctly assigned the value of ChartScrollState#maxValue, which is zero. When, after one second, the chart is populated, it’s no longer in its initial state—the requested initial scroll value has already been applied. If you’d like ChartScrollState#value to be assigned the value of ChartScrollState#maxValue whenever the width of the chart content increases, you can use automatic scrolling. You’ve correctly passed AutoScrollCondition.OnModelSizeIncreased to rememberChartScrollSpec, but your custom ChartEntryModel-related solutions are incompatible with automatic scrolling. Specifically, FixedStepXModelDecorator doesn’t override ChartEntryModel#id so that the identifier changes along with the data, and the Chart composable never receives the previous ChartEntryModel. ChartEntryModelProducer and the Chart variant that accepts a ChartEntryModelProducer handle these matters out of the box, but for your custom approach, you’ll have to add support for automatic scrolling yourself.

Thank you very much for your response. FixedStepXModelDecorator is kind of hack as I didn't know how to specify step size correctly. What is suggested approach?

authors: patrickmichalik thubalek

repo: patrykandpatrick/vico


text:
Integrated Game Chat

So a few updates .. first edition of the integrated game chat. Includes a playback buffer of 10 lines (can be changed) when people log in. Still need some spam/work filtering for completeness but it does seem to work in all the browsers I tested. Added it through an addition websocket which is applied to an actor through the main application. Probably should be on its own but I'm just happy it works at this point.
Made a few other minor changes. Some of these JS files probably should be hosted from the CDN .. no point in serving them yourself.
Oh .. and edit the chat.js to modify the port if needed .. that could be important :)

Updated the PR and cleaned a few things

Thanks again! Sorry I was very busy working on #85  today. But I will look at this PR next for sure1  😸

Updated for all the new lounge PR to ensure no conflicts.

Probably will look at this PR this weekend since the Lounge is hopefully fixed
And it's long weekend here :)

repo: patsonluk/airline


text:
fix(tools): dev server icon and colours

What I did

change dev server header colour to black
use correct url for dev server header icon

@zeroedin please do

unexpected test failures.  taking a look.

authors: bennypowers zeroedin

repo: patternfly/patternfly-elements


text:
Implement Forms demo for a11y testing

A demo page is needed that provides different examples of form elements, which can be tested for accessibility issues.
As part of this issue:

create the forms demo page, based on the forms demo outline identified as part of #679

Closing this since #919 should hopefully cover all the variations.

repo: patternfly/patternfly-next


text:
fix(wizard): update disabled step, remove right align option

fixes https://github.com/patternfly/patternfly-next/issues/1616

Deploy preview for pf-next ready!
Built with commit f94eae950d057b7832b78d2a4abbeaa65af40280
https://deploy-preview-1661--pf-next.netlify.com

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: mcoker patternfly-build


text:
Aider not having the correct map of my repo, have to re-add files every session

Added aider to my small repo. When trying to reference files it only has access to a limited number. There should be a way to make it save the file structure and see all of them.

turns out Aider just wont work with files that are in .gitignore. Which seems like something that should be addressed.

repo: paul-gauthier/aider


text:
Changes not applied to file

Hi, when I use aider, response is printed to the terminal but not applied to the file like described and shown in the screencasts. I don't have GPT-4 access yes, though, so am running with the -3 flag.
Thanks for doing this, eager to use it :) .

Thanks for trying aider!
You are probably correct that the issue is caused by using gpt-3.5-turbo. It doesn't following instructions well, and often fails to  format code in a way that aider expects.
Is it outputting "edit blocks" that look like the example in the prompts?
https://github.com/paul-gauthier/aider/blob/82cc64eb6f4bd1006bf55b94890a76c5db1576b8/aider/prompts.py#L18-L28
If not, then aider won't be able to parse out the edit and apply to the file.

No, it's just outputting the entire file, with its changes. It would be nice if there was a command like /replace or /overwrite that would simply replace the file with that output. Because the answer is good, even though it's gpt-3.5-turbo.

Yes, it would be nice for aider to support some basic functionality with gpt-3.5-turbo. That model is quite limited in what it can do though. With only 4k context window and the need to read and write the entire code that is being modified... you can only work on small pieces of code with it.
I'll definitely think some more about this and try and find a good approach to adding support for 3.5.
Thanks again for the feedback.

I'm going to close this for now. Feel free to reopen or make a new issue if you have problems or questions about gpt-3.5-turbo support.

authors: paul-gauthier tiktuk


text:
Nightscout / sponsorship

Howdy, great work!  FWIW, I notice a lot of defensive warnings that I don't think are needed:

Right to repair protects patient rights use third party software without violating terms of service.  In certain states it is illegal for manufacturers to claim this, and it is being enforced on a federal basis by the FTC.
The risk is low - this is may be considered Class I, low-risk, as it is read-only data.  In any case T1Pal is registered with FDA as secondary display remote monitor and would be happy to add this carelink viewer as another registered device.

I'm very interested in promoting Nightscout connectivity, how would you feel about additional synchronizing to or from Nightscout?

@bewest I don't understand some of your comments. The defensive warnings were copied, I am not a lawyer. If you have specific changes, I would be happy to accept. I would he thrilled if you add this to FDA remote monitor registry.
As for sync with NightScout I have no idea what that entails I have never used NightScout personally. This code is very tailored to Medtronic 770G and 780G to allow a deeper understanding of the algorithm and information that pump makes available some of which is very hard or impossible to get from existing reports.
I personally don't promote this app; I share it freely with a few users and they share it organically.  My next priority (which I am having 0 success with) is to read the CareLink DEVICE SETTINGS SNAPSHOT report to allow the program to automatically import that information which is not available from pump (today its manual entered) and additionally reformat it to be a step-by-step personalized report to program a replacement pump. It will merge the data from device setting with format of "How to program a new pump". This MAY cause liability to me and if so, I may just use this new report for myself as I get 4-6 new pumps a year due to travel schedule and am constantly missing a setting.

Very reasonable.  Feel free to get in touch with me, bewest@medicaldatanetworks.com.  There is an additional project to connect to the BLE device directly, it sounds like you might be an ideal contributor; it could lead to restoring/configuring settings on the pump.  Finally, I'm not yet a dotnet dev, but I'm very impressed with MAUI and f#, and it would be great to ask you some questions about feasibility of open source and cross platform mobile apps in this space.

@bewest replied via email


text:
🛑 Paulynomial (index) (www-redirect) is down

In 0b5bfe2, Paulynomial (index) (www-redirect) (https://www.paulynomial.com) was down:

HTTP code: 503
Response time: 373 ms

Resolved: Paulynomial (index) (www-redirect) is back up in 0e781dc.

repo: paulkiernan/paulynomial-uptime


text:
Hash to point should conform to updated spec

The hash to curve draft standard does not support try-and-increment. The specific hashToG2 standard for blockchains is based on Wahby-Boneh.

@JustinDrake not sure I understand. What do you think we should change in hashToG2?

To be standards-compliant with various blockchain projects hashToG2 would need to be changed to the Wahby-Boneh hash function (chosen because it can relatively easily be made constant-time).

@JustinDrake could you please share some implementation which contain the standard?
If it will be kwantam/bls12-381_hash could you please describe which function creates an G2 from hash (sequence of bytes)?

implementations in Sage and Python (including test vectors): https://github.com/cfrg/draft-irtf-cfrg-hash-to-curve/tree/master/poc
Rust implementation: Ping @kirk-baird

Further resources:

academic paper: https://eprint.iacr.org/2019/403
IETF draft: https://tools.ietf.org/html/draft-irtf-cfrg-hash-to-curve-04

Hi, I thought I'd expand on this as it can be quite complicated.
The process of converting a message / bytes to a G2 point can be broken into three parts.

Hash to Base: Converting message to a Number in the Finite Field
See https://github.com/cfrg/draft-irtf-cfrg-hash-to-curve hash_to_base for details
Map to Curve: Convert a Field Point to G2 Point
This is often done by a SWU mapping however that is not directly applicable to BLS12-381 so an additional step is used where the SWU mapping is to a new 3-Isogenous curve then mapped to BLS12-381.
Read section 4 for details on this https://eprint.iacr.org/2019/403.
Clear Cofactor: Ensure that the final G2 point is in the correct sub group.
A fast method is shown here  https://eprint.iacr.org/2017/419 in section 4.1

All three parts have been implemented by https://github.com/kwantam/bls_sigs_ref in the Sage Implementation.
I've also just finished writing an implementation here https://github.com/sigp/incubator-milagro-crypto-rust/tree/bls-standard/src though it has minimal testing and it needs some tidying up but feel free to ask if you're lost :)

Alright, the pull request is up...except the test vectors now don't match previous ones.
New hashToG2 must produce identical outputs for the same inputs, correct?

Yep, if you're asking if it is deterministic i.e. input A will always generate G2 point B.

GLAD to finish this. Hash to curve now conforms to v7 of the draft!

authors: JSMonk JustinDrake kirk-baird paulmillr


text:
Figtext for many GTIs in sci_plots (minor issue)

When the event file has a lot of GTIs, the display command
plt.figtext(str(gtitable['START'][:]))
of the astropy.Table automatically truncates the number of rows in the table, but there are still too many, and the list of GTIs overlaps with the title and goes out of the page.
That's a minor issue, but I can't find a way to truncate the display even more. There doesn't seem to be any way to tell 'print' or 'str()' to shorten the output of the astropy.Table
Any ideas?

Maybe the code could count the number of lines in the str representation and then set the font size accordingly, so that the whole table fits?

I did something like this:

if there are more than 7 GTIs, the table shows only the first and last 3, replacing the middle ones by '...', and in the duration column, it shows the sum of the omitted GTIs.
changed the font to courier to have fixed-width characters.

authors: paulray sguillot

repo: paulray/NICERsoft


text:
Move from SPIFFS to LittleFS

SPIFFS has been deprecated and is no longer actively supported.
LittleFS is currently being actively supported.  It also offers support for real directories and is many times faster than SPIFFS (not that its particularly important in this situation.
Move eris to LittleFS and implement new commands to support directories.

I'm not so sure on this one now.  ESP8266 says SPIFFS is deprecated, ESP32 doesn't mention LittleFS.

Wait and see. I think it's more important to add SD Card support, which isn't difficult I would think but I don't have a 1.4 board yet. (The reason there's no directories incidentally is SPIFFS doesn't support them)

Agreed...SD card support is more important.  I was going to ask you what hardware you had been testing on.  I currently have V1.4 of TTGO VGA32, and have also ordered Fabrizio's V4 Development board.  I'm also making up my own prototype board based on the schematic published by Fabrizio.

I have ordered some 1.4 SD cards but it'll be 2-3 weeks before they arrive. I'll have an optional build because there are three of these boards out there - they all have ps2 and vga, then they added the sound socket, then they added the SDcard connector. So it's worth keeping SPIFFS as an option.

From my research, the pins used for TTGO SD card are different from Fabrizio's Development board.  So it would be necessary to be able to change the pin designations fairly easily.
As for SD vs SPIFFS, is it possible to support both?  That way you could copy files from one to the other.
I believe the change from SPIFFS to LittleFS would be a replacement, but again, I didn't find evidence that SPIFFS is deprecated for ESP32.
I'm not sure how these file system changes we are discussing affect the other platforms supported by eris.

authors: OzHawk paulscottrobson

repo: paulscottrobson/eris


text:
Wont load images when I scroll down the view

wont load the images that are not visible at first time, I mean the images when I scroll down.

check your ion-content attribute as list

guys any solution to this, been scratching my head for days now.
Help Out
Kindest Regards

Could you get any solution for this? thanks!

my solution is adding the lazy-load atribute to your ion-scroll tag hope this helps any one

For everyone else experiencing this issue. Simply add lazy-scroll as an attribute on your ion-content directive.

authors: Zieheavy fzaffarana isumakun jokerjkeeper padrian spencerspear

repo: paveisistemas/ionic-image-lazy-load


text:
Add support for numba-compiled callable metrics

Expected behaviour
pynndescent supports passing callable metrics compiled with numba, so I would expect openTSNE to be able to support this
Actual behaviour
When I pass a numba-compiled callable metric, openTSNE throws a ValueError
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-44-b188b4c74e96> in <module>()
----> 1 embedding_train = tsne.fit(X_train)

/home/jake/.local/lib/python3.6/site-packages/openTSNE/tsne.py in fit(self, X)
   1040
   1041         """
-> 1042         embedding = self.prepare_initial(X)
   1043
   1044         try:

/home/jake/.local/lib/python3.6/site-packages/openTSNE/tsne.py in prepare_initial(self, X)
   1118             metric_params=self.metric_params,
   1119             n_jobs=self.n_jobs,
-> 1120             random_state=self.random_state,
   1121         )
   1122

/home/jake/.local/lib/python3.6/site-packages/openTSNE/affinity.py in __init__(self, data, perplexity, method, metric, metric_params, symmetrize, n_jobs, random_state)
    124         k_neighbors = min(self.n_samples - 1, int(3 * self.perplexity))
    125         self.knn_index, self.__neighbors, self.__distances = build_knn_index(
--> 126             data, method, k_neighbors, metric, metric_params, n_jobs, random_state
    127         )
    128

/home/jake/.local/lib/python3.6/site-packages/openTSNE/affinity.py in build_knn_index(data, method, k, metric, metric_params, n_jobs, random_state)
    274             metric_params=metric_params,
    275             n_jobs=n_jobs,
--> 276             random_state=random_state,
    277         )
    278

/home/jake/.local/lib/python3.6/site-packages/openTSNE/nearest_neighbors.py in __init__(self, metric, metric_params, n_jobs, random_state)
     11     def __init__(self, metric, metric_params=None, n_jobs=1, random_state=None):
     12         self.index = None
---> 13         self.metric = self.check_metric(metric)
     14         self.metric_params = metric_params
     15         self.n_jobs = n_jobs

/home/jake/.local/lib/python3.6/site-packages/openTSNE/nearest_neighbors.py in check_metric(self, *args, **kwargs)
    184             )
    185
--> 186         return super().check_metric(*args, **kwargs)
    187
    188     def build(self, data, k):

/home/jake/.local/lib/python3.6/site-packages/openTSNE/nearest_neighbors.py in check_metric(self, metric)
     58         if metric not in self.VALID_METRICS:
     59             raise ValueError(
---> 60                 f"`{self.__class__.__name__}` does not support the `{metric}` "
     61                 f"metric. Please choose one of the supported metrics: "
     62                 f"{', '.join(self.VALID_METRICS)}."

ValueError: `NNDescent` does not support the `CPUDispatcher(<function kld at 0x7f7fe2311158>)` metric. Please choose one of the supported metrics: euclidean, l2, manhattan, taxicab, l1, chebyshev, linfinity, linfty, linf, minkowski, seuclidean, standardised_euclidean, wminkowski, weighted_minkowski, mahalanobis, canberra, cosine, correlation, haversine, braycurtis, hamming, jaccard, dice, matching, kulsinski, rogerstanimoto, russellrao, sokalsneath, sokalmichener, yule.

Steps to reproduce the behavior
Here is a minimal working example:

import numpy as np
from openTSNE import TSNE
from openTSNE.callbacks import ErrorLogger
from numba import njit

@njit(fastmath=True)
def kld(p, q):
    result = 0.0
    for i in range(p.shape[0]):
        logp = np.log(p[i]) if p[i] > 0 else 0
        logq = np.log(q[i]) if q[i] > 0 else 0
        result += p[i] * (logq - logp)
    return -result / np.log(2.)

tsne = TSNE(
    perplexity=30,
    metric=kld,
    callbacks=ErrorLogger(),
    n_jobs=1
)

x_train = np.random.beta(0.5, 0.5, size=(500,10))
embedding_train = tsne.fit(x_train)

Almost all the problems I've encountered while maintaining openTSNE have been pynndescent related. As such, I would be very hesitant to add anything that ties openTSNE even closer to pynndescent.
However, it should be fairly simple to achieve what you want. I've made it so that the neighbors parameter can be an instance of openTSNE.nearest_neighbors.KNNIndex, so you can just copy over the NNDescent class and remove the check that disallows custom metrics. You can probably just change check_metric to return True and I'd guess that would do it.

Sorry, I wasn't clear. I'm not suggesting you tie openTSNE closer to pynndescent. Passing a callable metric is a standard feature for many packages. scikit-learn also allows it for many of their algorithms, including their implementation of TSNE. Adding a check if metric is callable is fairly straightforward. If you're short of time/motivation then I can make a PR once I have time to look through the code. You're of course free to reject it, but I think this is a reasonable feature to have for a t-SNE implementation and would be potentially useful to quite a few people.
I'm trying to apply openTSNE to use these methods for analyzing animal behavior:
https://royalsocietypublishing.org/doi/10.1098/rsif.2014.0672
as an example analysis for my recently developed package:
https://github.com/jgraving/behavelet
Applying t-SNE to these data requires using KL-divergence as a distance metric between normalized time-frequency vectors. If accomplishing that requires that users subclass and modify your code to get it working then I will likely just find something else, as I'd like it to be straightforward for people to use.
Again, I appreciate the work you've done on this. I'm not trying to be pushy. Just wanted to let you know that openTSNE would be more widely useful if it had this feature.

Hmm, I'm all for custom distance metrics, but the "numba-compiled callable" threw me off a little bit. I'm not very familiar with numba so is it possible to call numba compiled from regular old python code? What I'm getting at is that opentsne supports both exact neighbor search via scikit-learn and approximate neighbor search via pynndescent, and I'd like to keep some consistency between the two. My concern was that if the function is numba-compiled, that it wouldn't be possible to use that callable in the scikit-learn BallTree.
Putting all numba-related things aside, adding custom distance metrics was definitely on my to-do list, but I've been and will likely be short on time for a while, so if you're willing to open a PR, I'd be more than happy to take a look. The changes should be fairly minimal anyhow.

Ah, I see. Sorry I assumed you were familiar with numba as it's one of the main dependencies for pynndescent. numba is a library that JIT-compiles pure python/numpy functions to make them faster. A numba compiled function works just like any other python function in practice. scikit-learn's BallTree accepts user-defined functions, which includes numba compiled functions. Here is an example:
from sklearn.neighbors import BallTree
from numba import njit
import numpy as np

@njit(fastmath=True)
def l1(x, y):
    return np.sum(np.abs(x - y))

tree = BallTree(np.random.normal(size=(1000,10)), metric=l1)
distances, indices = tree.query(np.random.normal(size=(100,10)), k=5)

The only issue I can see is if the function isn't numba compiled and it's passed to pynndescent then pynndescent will throw an uninformative error message from numba. Whether or how to deal with this might require some thought, or maybe just make clear in the docstring and leave this for pynndescent to deal with. I assume if the user is savvy enough to pass a custom metric then they'd expect error messages are a possibility.
I'll take a look at the code and submit a PR with the changes.

The only issue I can see is if the function isn't numba compiled and it's passed to pynndescent then pynndescent will throw an uninformative error message from numba.

I would hope that numba has some kind of way to check if a function is compiled. Then if it isn't, we could do that within the pynndescent wrapper to avoid potential errors. A decorator is just a function, after all. It should be fairly straightforward to check if a function is an instance of the Dispatcher type and then if it isn't, to just call numba.njit(f) otherwise.

Fixed via #94.

authors: jgraving pavlin-policar

repo: pavlin-policar/openTSNE


text:
Android auto and carplay support

Does this lib support carplay and android auto yet?

Currently supported carplay see example for setup, it is in beta mode. Android auto is not planned.

repo: pawan-pk/react-native-mapbox-navigation


text:
There are no changes in the module that are on github

There is no UTF-8 in the connected module:

@r35p3ct update to latest version 0.2.0


text:
libfiledialogs Git Submodule (Optional Dear ImGui File Dialogs Dependency)

what my thought on this was, it won't actually go inside your repository
as a git submodule it will be optional
they will have to specify git clone --recurse-submodules
without --recurse-submodules it can use dlgmodule or tiny file dialogs or whatever you prefer as the fallback
the executable will look in its working directory for the dll and if it exists override the dialogs with the imgui ones
if the dll isn't found on the filesystem, don't attempt to call functions from nonexistent dll
and then use the fallback you already have in your repos
it won't require much code added to your codebase
what do you think?
having it as a submodule will allow you to maintain your ide how you like
and i can maintain my dialogs with my own write access without directly affecting you upon breakages for example
people can use yours if mine breaks or vise versa
the most compelling reason for this to be added is less maintenance needed for building on mac
mac is currently broken with dlgmod
and will likely break after i fix it, just a matter of yearly os updates
as for the imgui dialogs it relies on code that apple rarely changes
in my experience
even then i can reimport a newer version of imgui if stuff breaks and let the imgui devs fix things for me
ok so ill make a pull request
but before that ill write a pseudo code real quick to give you a better idea
string get_open_filename(filter, fname) {
  if (file_exists(libfiledialogs_dll_file)) {
    return call_dll(libfiledialogs_dll_file, "get_open_filename", filter, fname);
  }
  // existing code from dlgmodule here
}

basically that for each dialog function
2-3 lines each
of course, not counting the helper function for call_dll
that's just a helper function wrapping dlopen(), dlsym(), and dlclose()  on unix-likes  and LoadLibraryW() for win32
dlopen(), dlsym() dlclose() docs - https://man7.org/linux/man-pages/man3/dlopen.3.html
LoadLibraryW() docs - https://learn.microsoft.com/en-us/windows/win32/api/libloaderapi/nf-libloaderapi-loadlibraryw
the dialogs are fully customizeable
you can set the localization, button text, title bar text, set them to borderless, parent window, always on top (when there is no parent), fullscreen, fixed, sizeable, change theme
just to name a few of the features already in
the library doesn't just do file dialogs and also message boxes and i will also add input box, login box, color picker and other stuff in the future

libfiledialogs library repos: https://github.com/time-killer-games/libfiledialogs
Preview:

Motivation:
primarily to have consistent looking dialogs for every platform while also ensuring macos support goes stale less often as imgui devs will handle most of the required maintenance for us, because in my experience of working with macOS's native dialogs they need to have code maintained nearly every year because os upgrades keep on breaking dlgmodule's code. This also opens the door to unofficially supporting DragonFly BSD, NetBSD, OpenBSD, and SunOS variants which are currently not supported by the version of dlgmodule used in the GPE IDE repos.
Additional Notes:

You don't need all of those fonts files in my repos. It depends how many languages you want to support, ultimately.
Ubuntu/Debian needs dependencies installed with: sudo apt-get install -y libsdl2-dev libgtk-3-dev libglib2.0-dev if the dll is to be used at all, we can use the fallback if calling the dll fails for whatever reason, as if the file doesn't exist
libgtk-3-dev and libglib2.0-dev are needed for loading system-defined icons from the default icon theme. libsdl2-dev is needed for the dialog window itself.
FreeBSD/DragonFlyBSD needs dependencies installed with: su -l root -c "pkg install sdl2 gtk3 glib" if the dll is to be used at all, we can use the fallback if calling the dll fails for whatever reason, as if the file doesn't exist
The dialogs support localization if you want to make translations of this app. All elements can be translated with the environment variables found in this header, using environment_set_variable(name, value) within C++:
https://github.com/time-killer-games/libfiledialogs/blob/main/filedialogs/ImFileDialogMacros.h

Adding to Fall 2024 due to backlog priority.

authors: nhurde time-killer-games

repo: pawbyte/Game-Pencil-Engine-Editor


text:
Remove the rules keyword

The rules keyword in section 6.1 and 6.2 the rules keyword is defined. However in case there is only rule included or excluded from the test the rules keyword would imply there is more than one
rule mentioned in the list.
I would be feasible to use rule and rules keyword depending on the number of rules in the list, but that would be hassle for test writers. Instead leave out the rules keyword entirely from section 6.1 and 6.2.

Migrated from BitBucket.

repo: pawwkm/spot


text:
🛑 Pay4Me App Website is down

In 57b5fd1, Pay4Me App Website (https://pay4me.app) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pay4Me App Website is back up in 3da9384 after 23 minutes.


text:
Adding editableProps

Description
Allowing the ability to send down props to SlateJS' Editable component through editableProps

[*] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[*] New feature (non-breaking change which adds functionality)

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Existing test suite passes locally with my changes
[*] I have made corresponding changes to the documentation

Hey @Ontopic — thank you for the PR! It looks great. The only thing I think we might want to be sensitive to is that if we allow overriding of currently used props, like onKeyDown and onBlur, there could be some funny business happening.
So, we probably can define some type of system, so that if someone wants to override onBlur, for example, they would be provided with both the event itself, and our current onBlur handler as a second argument—which would allow them to leverage our existing functionality but add on top of it as well.
Slate does a similar thing with their plugin architecture in concept. In practice, it's different, but in reality it's the same. For example, if someone wanted to override our onBlur but still leverage our function:
Within src/admin/components/forms/field-types/RichText/RichText.tsx:
<Editable
  onBlur={(event) => {
    // Run theirs if they defined it
    if (typeof admin.editableProps.onBlur === 'function') {
      admin.editableProps.onBlur(event, ourExistingOnBlur);
    } else {
      ourExistingOnBlur();
    }
  }}
/>

Alternatively, we could force our default handlers to run in all cases. Such as:
<Editable
  onBlur={(event) => {
    // Run theirs if they defined it
    if (typeof admin.editableProps.onBlur === 'function') {
      admin.editableProps.onBlur(event);
    }

    // Still run ours
    ourExistingOnBlur(event);
  }}
/>

What do you think?

Check, that will indeed cause some confusion in the future 😅  I might even add an onBeforeX and onAfterX kind of structure. I've encountered now situations where I would like the original callbacks from Slate and Payload to be fired before I fire my own. F.e. after pressing enter I'd like the styling to reset after the cursor has moved to the new line, not before.
Will look into the Slate types and update the code!

Hey @Ontopic — if you want to revisit this one, we're happy to re-open but otherwise we'll get back to this in the future with a more robust and solidified approach.
Thanks and hope all is well!

I don’t understand how to finish and sign! Please help!
Get Outlook for iOShttps://aka.ms/o0ukef

From: James Mikrut @.>
Sent: Wednesday, July 6, 2022 10:32:50 AM
To: payloadcms/payload @.>
Cc: clueless360 @.>; Comment @.>
Subject: Re: [payloadcms/payload] Adding editableProps (#128)
Closed #128https://github.com/payloadcms/payload/pull/128.
—
Reply to this email directly, view it on GitHubhttps://github.com/payloadcms/payload/pull/128#event-6943887172, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASDNFTNM3VMR7VVGEBH6YZDVSWRKFANCNFSM42IDFUWQ.
You are receiving this because you commented.Message ID: @.***>

authors: Ontopic clueless360 jmikrut

repo: payloadcms/payload


text:
feat(render): add render prop

What: This also moves all examples and tests to use render prop and adds one test to verify the children prop still works

Why: Closes #258
I'm trying to bring some cohesion to the render prop idea.

How: the source code change was as simple as this.props.render ||. Most of the changes are updating the stories, tests, and docs to use the render prop instead.

Checklist:

[x] Documentation
[x] Tests
[x] Ready to be merged
[ ] Added myself to contributors table N/A

NOTE: The children prop still works fine. I don't know whether I'll ever drop support for it. Can't think of a reason why I would...

Codecov Report

Merging #261 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #261   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines         299    299
  Branches       71     72    +1
=====================================
  Hits          299    299

Impacted Files
Coverage Δ

src/downshift.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks for the review @petetnt! You've been added to the contributors table :tada:

authors: codecov-io kentcdodds

repo: paypal/downshift


text:
Incorrect starting skill points when making new character

When making a new character, starting skill points are 0-INT instead of 5-INT

Starting Skill, Trade and Language points come from background. You need to add one to your character sheet. You can open background compendium from character sheet

authors: OmarMAbbasi pazindorb


text:
IndexError: index 0 is out of bounds for axis 0 with size 0

Running this code under Python 3.8 produced the following traceback. Note that it seems that max_n=10**7 is related to this bug, because it didn't happen before I used that.
Traceback (most recent call last):
  File "heapz.py", line 115, in <module>
    best, others = big_o.big_o(heapify, data_generator_heapify, max_n=10**6)
  File "C:\Program Files\Python38\lib\site-packages\big_o\big_o.py", line 157, in big_o
    return infer_big_o_class(ns, time, classes, verbose=verbose)
  File "C:\Program Files\Python38\lib\site-packages\big_o\big_o.py", line 97, in infer_big_o_class
    residuals = inst.fit(ns, time)
  File "C:\Program Files\Python38\lib\site-packages\big_o\complexities.py", line 38, in fit
    return residuals[0]
IndexError: index 0 is out of bounds for axis 0 with size 0

I did some debugging and testing. Like you mentioned this happens at larger  max_n, as in the error message it also happens with max_n=10**7. I tried remove different classes and I think the error seems to occur specifically for the Cubic class, for others not. If you follow the error precisely, you see that  coeff, residuals, rank, s = np.linalg.lstsq(x, y, rcond=-1)  (here) we get an empty numpy vector for the residual for the Cubic case when max_n is large, the reason being that the rank of x is too small (see the relevant numpy docs) and thus numpy gives one an empty array. I think you should be able to compute the residual doing something like np.linalg.norm(y - x @ coeff) which would still work in this case, however, doing that give different residual from numpy.
Why this specifically happens for the Cubic case, I cannot tell you. I tried this also for another case that I made up and again for large max_n specifically the Cubic case has this problem.

authors: cool-RR lucasalavapena


text:
Update keycloak-core to 26.0.4

About this PR
📦 Updates org.keycloak:keycloak-core from 26.0.1 to 26.0.4
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (26.0.1).
You might want to review and update them manually.
src/main/scala/akkahttp/oidc/OIDCKeycloak.scala

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.keycloak", artifactId = "keycloak-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.keycloak", artifactId = "keycloak-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #1001.


text:
Extra quotes in PSLiteral.repr

The .six fork adds extra quotes to PSLiteral.__repr__:
ipdb> from pdfminer.psparser import PSLiteral
ipdb> PSLiteral("Name")
/'Name'

... where regular pdfminer would just print /Name.
This seems to be because of this line, which switched from using '/%s' to  '/%r'.
Should be a one-character fix, unless there's some reason using %r is important?
(Seems like a minor issue, I know, but pdfquery uses __repr__ for serializing PDFs, so this becomes a blocker for py3 support.)
Thanks!

as mentionned in PSLiteral doc "Note: Do not create an instance of PSLiteral directly. Always use PSLiteralTable.intern()" This seems to take care of the problem you mention. Please reopen with a test case if not

authors: goulu jcushman


text:
⚠ Hartman Foundation has degraded performance

In 721965b, Hartman Foundation (https://gordonhartman.com/) experienced degraded performance:

HTTP code: 200
Response time: 2577 ms

Resolved: Hartman Foundation performance has improved in 7617ba3.

Resolved: Hartman Foundation performance has improved in 7617ba3.

repo: pearanalytics/uptime


text:
🛑 alamofireworks is down

In 87466d8, alamofireworks (https://www.alamofireworks.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: alamofireworks is back up in 47478e9.


text:
🛑 Office Furniture Liquidations is down

In a77431d, Office Furniture Liquidations (https://www.officefurnituresa.com) was down:

HTTP code: 503
Response time: 515 ms

Resolved: Office Furniture Liquidations is back up in c911912.


text:
Handle bad reference to OSD + add test for module import

This change addresses #14 by defining the entire GeoTIFFTileSource class within the enableGeoTIFFTileSource function. Importing the class directly will no longer be supported, but will be available through OpenSeadragon.GeoTIFFTileSource after intialization.
I've also added a test using vitest (very similar API to Jest) to check for the import working as expected + the tile source being accessible in the OSD namespace. This brought in a few extra packages (canvas, jsdom, openseadragon) to test initializing the plugin + OSD in a browser environment.

@abiswas97 Thanks for putting this together.
@mdushkoff Would you be able to test this to make sure it fixes the issues you've been seeing?

I just tried this out and so far it is looking like it works from my limited testing (basic loading).  Thanks again for your efforts!

Ok, I'll go ahead and merge this and create a new release. Hopefully now it works right!

authors: abiswas97 mdushkoff pearcetm

repo: pearcetm/GeoTIFFTileSource


text:
Print notification when LXRHash file is being calculated

Right now the console is just blank for 10+ minutes with no output while the hash file is being generated. We can either turn LXRHash's verbose option on, or at least print out console output letting people know when it starts and when it ends

Agree, this is a bit obnoxious.

this has been implemented

Can probably be refined later

authors: Cahl-Dee Emyrk WhoSoup

repo: pegnet/pegnet


text:
Publish version 0.0.5 on the Maven central repository?

I am trying to use the version 0.0.5, which is supposed to be the latest version of the event bus framework, but it seems that it is not published on the Maven central repository.
http://stackoverflow.com/questions/28786579/how-to-use-the-latest-version-of-vaadin4spring-eventbus-framework-with-maven?noredirect=1#comment45862929_28786579
I have cloned the whole vaadin4spring repository and run a mvn clean install and installed the whole components of the framework successfully.
Anyway, will you publish the version 0.0.5 of the framework on the central repository?

No, it's not published yet since not all the tasks that are planned for that release have been completed yet. See #170 .

authors: Tonix-Tuft peholmst


text:
No way to send a request without the 'language' header

Just spent a while wondering why my API server was rejecting my requests, and it turns out it's because there's an unexpected header, 'language' being sent with the request.
This bit of code makes it impossible to not send the header:
if (!headers.containsKey('language')) {
      headers['language'] = Intl.defaultLocale ?? 'en_US';
    }

Of course I can set my server's CORS policy to accept this header, but that requires that I modify the CORS package I'm using for my backend, so It's kind of a pain. Moreover though, this could be breaking for people sending requests to APIs/services that they don't have control over.
(Also, I might be wrong but isn't the name of this header 'accept-language'?)

You are correct, it should have been accept-language.  Thanks for pointing that out.  :)
I fixed the name, and updated so you can unset any default header by setting it to empty.  Just update to:
rest_client: ^2.1.1

authors: alexobviously jpeiffer


text:
[prometheus-artifactory-exporter] feat: support reading an external secret

What this PR does / why we need it:
This adds support for ingesting a secret provided outside of the Helm release for authentication with Artifactory. For example, using an ExternalSecret to grab the credentials from Vault, and allowing the exporter to read from the generated secret owned by the external-secrets controller.
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [prometheus-artifactory-exporter])

@peimanja I noticed that you had setup existingSecret but the chart's Deployment did not provide an option for specifying such a secret.

@peimanja I noticed that you had setup existingSecret but the chart's Deployment did not provide an option for specifying such a secret.
I know it's a bit misleading but setting that to anything but false will be the name of the existing secret. See here

authors: alec-drw peimanja

repo: peimanja/helm-charts


text:
Can't use training tools

I built the tesseract for visual studio 2017 x64 bit and it is running fine. But when i train the data unicharset_extractor is not a command error comes. How to use the training tools?

You have to build the training tools yourselft. Please have a look at: https://github.com/tesseract-ocr/tesseract/wiki/Training-Tesseract

That is for Linux only. Is there a way to build for windows X64

That is only for linux not for windows x64..
And i am able to decode only phototest.tif no other image. This error is coming up

authors: Shweta-singh peirick


text:
🛑 Beyond.pl is down

In a2aeb73, Beyond.pl (http://www.beyond.pl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beyond.pl is back up in 71b3ee9 after 11 minutes.

repo: pejotes/upptime


text:
🛑 Dinas Perhubungan is down

In 3d0c312, Dinas Perhubungan (https://dishub.bekasikota.go.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dinas Perhubungan is back up in 4c79293.

repo: pemkotbekasi/website-status


text:
More structured query planner

Reader's guide to this PR:
The aim is to have a more structured and maintainable approach to generating bytecode from the query AST so that different parts of the query processing pipeline have clearer responsibilities, so that developing new functionality is easier. E.g.:

If you want to implement join reordering -> you do it in Optimizer
If you want to implement GROUP BY -> you change QueryPlanNode::Aggregate to include it, parse it in Planner and handle the code generation for it in Emitter

The pipeline is:
SQL text -> Parser -> Planner -> Optimizer -> Emitter
and this pipeline generates:
SQL text -> AST -> Logical Plan -> Optimized Logical Plan -> SQLite Bytecode

Module structure:
node.rs: defines the QueryPlanNode enum. A QueryPlanNode is a tree of other QueryPlanNodes, e.g. a QueryPlanNode::Join has left and right children, etc.
planner.rs: Parses an ast::Select into a SelectPlan which is mainly a wrapper for a QueryPlanNode
optimizer.rs: Makes a new SelectPlan from an input SelectPlan - does predicate pushdown, constant elimination and turns Scan nodes into SeekRowId nodes where applicable
emitter.rs: Generates bytecode instructions from an input SelectPlan.

Adds feature EXPLAIN QUERY PLAN <stmt> which shows the logical query plan instead of the bytecode plan

Other changes:

Almost everything from select.rs removed; things like translate_aggregation() moved to expr.rs
where_clause.rs removed, some things from it like translate_condition_expr() moved to expr.rs
i.e.: there is nothing new in expr.rs, stuff just moved there

Concerns:

Perf impact: there's a lot more indirection than before (QueryPlanNodes are very "traditional" trees where they refer to other nodes via Boxes etc)
emitter.rs structure with .start() .emit() and .end() is TBH still a bit of a hack and I'm not entirely sure yet how to make it more consistent without having to special case the behavior of certain nodes like Order. The upside is that the bytecode generation of SELECT statements is now fully controlled by that module (plus its utility dependencies like expr.rs) so it's also more straightforward to change

Rewrote emitter.rs to be more flexible, mainly via adding a step: usize property to the Operator struct variants with which they can track their own execution state

repo: penberg/limbo


text:
[BACKLOG-38674] Integration Tests are outdated and some do not compile.

While, under BACKLOG-37696, the Rest step was moved to the Rest plugin, this code was "left behind".
I've moved it into the plugin tree.
Note that it is still needed to update the integration tests code to the new implementation!
@bcostahitachivantara @renato-s @andreramos89

:white_check_mark: Build finished in 50m 47s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine,plugins/rest/core

:ok_hand: All tests passed!
Tests run: 4101, Failures: 0, Skipped: 13    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 50m 38s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
engine,plugins/pur/core,plugins/rest/core

:ok_hand: All tests passed!
Tests run: 4101, Failures: 0, Skipped: 13    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 50m 45s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
engine,plugins/pur/core,plugins/rest/core

:ok_hand: All tests passed!
Tests run: 4092, Failures: 0, Skipped: 13    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 51m 32s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
engine,plugins/pur/core,plugins/rest/core

:ok_hand: All tests passed!
Tests run: 4092, Failures: 0, Skipped: 13    Test Results

:information_source:  This is an automatic message

authors: buildguy smmribeiro

repo: pentaho/pentaho-kettle