[Bug]: shopify theme dev suddenly stopped working

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
I run shopify theme dev --store store-slug and a local development server is created for me to make changes on my machine.
Actual behavior
Error is thrown: Cannot read properties of undefined (reading 'toString'). When I run the command with the --verbose flag, this is the last message before the error is thrown:
2023-03-24T22:55:52.557Z: Sending Identity Introspection request to URL: undefined
I'm assuming there should be a url in place of undefined.
Verbose output
2023-03-24T22:55:52.511Z: Running command theme dev
  shopify:theme:dev init version<EMAIL_ADDRESS>argv: [ '--store', 'store-slug, '--verbose' ] +0ms
2023-03-24T22:55:52.552Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]

2023-03-24T22:55:52.552Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store store-slug.myshopify.com:
[]

2023-03-24T22:55:52.554Z: Getting session store...
2023-03-24T22:55:52.556Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access"
]
For applications:
{
  "adminApi": {
    "scopes": [],
    "storeFqdn": "oakandeden.myshopify.com"
  }
}

2023-03-24T22:55:52.557Z: Sending Identity Introspection request to URL: undefined
╭─ error ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Cannot read properties of undefined (reading 'toString')                                                                                │
│                                                                                │
│  To investigate the issue, examine this stack trace:                                                                                │
│    at shopifyFetch (../../../../usr/local/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-k  │
│    it/src/public/node/http.ts:69)                                                                                │
│      outputDebug(outputContent`Sending ${options.method ?? 'GET'} request to URL ${url.toString()}                                       │
│    at (usr/local/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/private/node/sess  │
│    ion/identity-token-validation.js:16)                                                                                │
│    at async withIntrospectionURL (../../../../usr/local/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/  │
│    @shopify/cli-kit/src/private/node/session/identity-token-validation.ts:49)                                                            │
│      let result: Result<T, AbortError> = await fn(introspectionURL)                                                                      │
│    at async validateSession (../../../../usr/local/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shop  │
│    ify/cli-kit/src/private/node/session/validate.ts:37)                                                                                │
│      const identityIsValid = await validateIdentityToken(session.identity.accessToken)                                                   │
│    at async ensureAuthenticated (../../../../usr/local/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/@  │
│    shopify/cli-kit/src/private/node/session.ts:113)                                                                                │
│      const validationResult = await validateSession(scopes, applications, fqdnSession)                                                   │
│    at async ensureAuthenticatedAdmin (../../../../usr/local/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modu  │
│    les/@shopify/cli-kit/src/public/node/session.ts:82)                                                                                │
│      const tokens = await ensureAuthenticated({adminApi: {scopes, storeFqdn: store}}, process.env, forceRefresh)                         │
│    at run (../../../../usr/local/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/src/cli/commands/theme/dev.ts:103)    │
│      const adminSession = await ensureAuthenticatedThemes(store, flags.password, [], true)                                               │
│                                                                                │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

2023-03-24T22:55:52.629Z: Unable to log analytics event - no information on executed command
2023-03-24T22:55:52.648Z: Failed to report usage analytics: Couldn't find a a package.json traversing directories from /Users/briancook/repos/oak_and_eden
2023-03-24T22:55:52.648Z: Completed command theme dev
2023-03-24T22:55:52.659Z: There was an error adding metadata to the Bugsnag report; Ignoring and carrying on Error: Couldn't find a a package.json traversing directories from /Users/briancook/repos/oak_and_eden

Reproduction steps

Upgrade to latest Shopify CLI version (3.44.1)
Run shopify auth logout
Run shopify theme dev --store store-slug

Operating System
Mac OS Ventura 13.2.1
Shopify CLI version (check your project's package.json if you're not sure)
3.44.1
Shell
zsh
Node version (run node -v if you're not sure)
v15.14.0
What language and version are you using in your application?
No response

Your instincts are correct! We have a caching mechanism that is apparently failing. Can you tell me more about how you first hit this issue? Maybe related to an upgrade? Or did it just suddenly stop working?

@amcaplan Suddenly stopped working. I had upgraded last Thursday and was able to do most my day's work Friday, but it stopped working some time mid-afternoon PST Friday.

Have any of you checked the value of that identity-introspection-url-accounts.shopify.com value before deleting it? It would be useful for us to fix the issue.

@gonzaloriestra Unfortunately, I don't recall exactly what it was before I deleted it, but it was a ten digit number of some kind. Maybe an ID or a timestamp?

It will be fixed in the next release (next week). As a workaround, you can remove the config.json in this folder:

macOS: ~/Library/Preferences/shopify-cli-kit-nodejs
Windows: %APPDATA%\shopify-cli-kit-nodejs\Config (for example, C:\Users\USERNAME\AppData\Roaming\shopify-cli-kit-nodejs\Config)
Linux: ~/.config/shopify-cli-kit-nodejs or $XDG_CONFIG_HOME/shopify-cli-kit-nodejs

Hello, I have almost the same problem but even with deleting the file on C:\Users%USERNAME%\AppData\Roaming\shopify-cli-kit-nodejs\Config
After delete the file config.json and login on browser sometimes the output says "✔ Logged in." but nothing happends or I have this error :
╭─ error ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Cannot read properties of undefined (reading 'toString')                                                                          │
│                                                                                │
│  To investigate the issue, examine this stack trace:                                                                               │
│    at create (../../AppData/Roaming/npm/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/src/public/node/themes/theme-ma  │
│    nager.ts:48)                                                                                │
│      this.setTheme(theme.id.toString())                                                                                │
│    at processTicksAndRejections (node:internal/process/task_queues:95)                                                             │
│    at findOrCreate (../../AppData/Roaming/npm/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/src/public/node/themes/th  │
│    eme-manager.ts:19)                                                                                │
│      theme = await this.create()                                                                                │
│    at run (../../AppData/Roaming/npm/node_modules/@shopify/theme/src/cli/commands/theme/dev.ts:127)                                │
│      const theme = await new DevelopmentThemeManager(adminSession).findOrCreate()                                                  │
│    at async runCLI (../../AppData/Roaming/npm/node_modules/@shopify/cli/node_modules/@shopify/cli-kit/src/public/node/cli.ts:88)   │
│      await run(undefined, options.moduleURL)                                                                                │
│    at async runShopifyCLI (../../AppData/Roaming/npm/node_modules/@shopify/cli/src/index.ts:42)                                    │
│      await runCLI({                                                                                │
│                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
TypeError: Cannot read properties of undefined (reading 'toString')
Someone found a fix?

i have a similar error. I want to start a dev server to create a theme. After running shopify theme dev --store {store-name} i am logged in but cant access any further information eg. viewing theme and the urls. Thats the error
To run this command, log in to Shopify.
👉 Press any key to open the login page on your browser
✔ Logged in.
╭─ error ──────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  Cannot read properties of undefined (reading 'toString')                    │
│                                                                              │
│  To investigate the issue, examine this stack trace:                         │
│    at create (opt/homebrew/Cellar/shopify-cli/3.59.1/libexec/lib/node_modul  │
│    es/@shopify/cli/dist/index.js:195941)                                     │
│    at processTicksAndRejections (node:internal/process/task_queues:95)       │
│    at findOrCreate (opt/homebrew/Cellar/shopify-cli/3.59.1/libexec/lib/node  │
│    _modules/@shopify/cli/dist/index.js:195914)                               │
│    at run (opt/homebrew/Cellar/shopify-cli/3.59.1/libexec/lib/node_modules/  │
│    @shopify/cli/dist/index.js:204557)                                        │
│    at _run (opt/homebrew/Cellar/shopify-cli/3.59.1/libexec/lib/node_modules  │
│    /@shopify/cli/dist/chunk-3MMF34G4.js:212317)                              │
│    at runCommand (opt/homebrew/Cellar/shopify-cli/3.59.1/libexec/lib/node_m  │
│    odules/@shopify/cli/dist/chunk-3MMF34G4.js:210764)                        │
│    at run (opt/homebrew/Cellar/shopify-cli/3.59.1/libexec/lib/node_modules/  │
│    @shopify/cli/dist/chunk-3MMF34G4.js:212426)                               │
│    at async runCLI (opt/homebrew/Cellar/shopify-cli/3.59.1/libexec/lib/node  │
│    _modules/@shopify/cli/dist/index.js:194855)                               │
│    at async runShopifyCLI (opt/homebrew/Cellar/shopify-cli/3.59.1/libexec/l  │
│    ib/node_modules/@shopify/cli/dist/index.js:207961)                        │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯
TypeError: Cannot read properties of undefined (reading 'toString')

I tried logging out and deleting the cachign file but nothings changed. Please help !

@annacaosi that looks like a different issue, would you mind creating a new one? And include the output with --verbose, please.

@annacaosi I had this issue and found that store name was spelled wrond. Double check you are using the correct store name. It should match the one in the admin URL - https://admin.shopify.com/store/store-name/...


Authenticated screens

Sorry in advanced @luwol03, this will be the last BIG PR >.<
FirstLogin Screen

AddVocab Screen

Top Nav

SideNav

This is not a problem. Now the linting errors are finally gone and we can develop properly. The screens look great.
Tomorrow I'll fix the axios stuff.

Thanks for fixing and redesigning the screens. They look amazing.


cant reactivate Answer Machine

Version: homebridge-fritz-platform v5.0.18
FritzBox 7490
FritzOS: 07.21
It is possible to deactivate the Answer Machine but it is not possible to reactivate Answer Machine.

Should be fixed with v5.0.19


Validation Report

This is now out-of-date: please see "Validation Report (revised)" below
Validation Report

Update IndexService to get missing field data from Solr
Model, controller, routes, and basic views for ValidationReport
Rake task to index sample invalid aggregation into Solr

DO NOT MERGE!  This branch is not fully working.

Ok -- new approach to integrating Krikri and Blacklight.  Instead of using Blacklight's catalog, which exists outside the krikri namespace, we are using catalog as a superclass for records and validation_reports, both of which exists inside the krikri namespace.
Benefits:

It's easier for records and validation_reports to talk to each other and everything else within the krikri namespace.
records and validation_reports maintain template inheritance from Blacklight, so they can use all of the same views and partials that catalog can access.
We don't have to copy any extra files forward into the host application (ie. we don't have to create files outside the krikri namespace to modify Blacklight behavior)
All of our routes get to stay within the krikri namespace.

Automated tests are failing for me locally b/c they cannot connect with Redis:

  1) Krikri::SoftwareAgent#enqueue enqueues a job
     Failure/Error: Resque.remove_queue(queue_name)
     Redis::CannotConnectError:
       Error connecting to Redis on <IP_ADDRESS>:6379 (ECONNREFUSED)
     # ./spec/models/software_agent_spec.rb:23:in `block (3 levels) in <top (required)>'

  2) Krikri::SoftwareAgent#enqueue creates a new activity when it enqueues a job
     Failure/Error: Resque.remove_queue(queue_name)
     Redis::CannotConnectError:
       Error connecting to Redis on <IP_ADDRESS>:6379 (ECONNREFUSED)
     # ./spec/models/software_agent_spec.rb:23:in `block (3 levels) in <top (required)>'

  3) Krikri::Harvesters::OAIHarvester with connection #enqueue saves harvest options correctly when creating an activity
     Failure/Error: Resque.remove_queue('harvest')  # Not strictly necessary. Future?
     Redis::CannotConnectError:
       Error connecting to Redis on <IP_ADDRESS>:6379 (ECONNREFUSED)
     # ./spec/models/harvesters/oai_harvester_spec.rb:216:in `block (4 levels) in <top (required)>'```

To test in a browser window, follow the instructions in README to start the dummy application and index an invalid aggregation into Solr.
Go to /krikri/records (or click "QA" in the search bar).  This will show you all the records in the search index.  From there, you can click "View Reports" to access Validation Reports.

@AudreyAltman: are you running 'rake ci' inside the Vagrant VM that's defined in ./provisioning?  That sets up Redis for you.

Alternately, you can use Homebrew to install Redis, and start it manually:
brew install redis
redis-server &

By the way, a local working copy of this branch (rebased onto develop) passes all tests. I get a minor RSpec deprecation notice:
Using `stub` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated.
Use the new `:expect` syntax or explicitly enable `:should` instead. Called from
/Users/mark/Documents/Code/dpla/KriKri/spec/lib/krikri/validation_report_list_spec.rb:15:in `block (3
levels) in <top (required)>'.

On /krikri/reports, I'm getting the following error:
Started GET "/krikri/reports" for <IP_ADDRESS> at 2015-01-16 17:15:12 -0500
Processing by Krikri::ReportsController#index as HTML
Solr query: {:qt=>"search", :rows=>0, "facet.field"=>["dataProvider_name", "isShownAt_id", "preview_id", "sourceResource_rights", "sourceResource_title", "sourceResource_type_id"], "facet.mincount"=>10000000, "facet.missing"=>true}
Solr fetch (7.6ms)
  Rendered /Users/mark/Documents/Code/dpla/KriKri/app/views/krikri/reports/_validation_report_list.html.erb (0.2ms)
  Rendered /Users/mark/Documents/Code/dpla/KriKri/app/views/krikri/reports/index.html.erb within layouts/blacklight (2.2ms)
Completed 500 Internal Server Error in 77ms

ActionView::Template::Error (undefined method `opensearch_catalog_url' for #<#<Class:0x007ff3969706d0>:0x007ff39770e260>):
    14:     <![endif]-->
    15:
    16:     <title><%= render_page_title %></title>
    17:     <%= opensearch_description_tag application_name, opensearch_catalog_url(:format => 'xml') %>
    18:     <%= favicon_link_tag 'favicon.ico' %>
    19:     <%= stylesheet_link_tag "application", media: "all" %>
    20:     <%= javascript_include_tag "application" %>
  blacklight (5.8.2) app/views/layouts/blacklight.html.erb:17:in `___sers_mark__rbenv_versions_______lib_ruby_gems_______gems_blacklight_______app_views_layouts_blacklight_html_erb__3734651986433074894_70342053151640'
  actionview (4.1.8) lib/action_view/template.rb:145:in `block in render'
  activesupport (4.1.8) lib/active_support/notifications.rb:161:in `instrument'
  actionview (4.1.8) lib/action_view/template.rb:339:in `instrument'
  actionview (4.1.8) lib/action_view/template.rb:143:in `render'
  actionview (4.1.8) lib/action_view/renderer/template_renderer.rb:67:in `render_with_layout'
  actionview (4.1.8) lib/action_view/renderer/template_renderer.rb:53:in `render_template'
  actionview (4.1.8) lib/action_view/renderer/template_renderer.rb:17:in `render'
  actionview (4.1.8) lib/action_view/renderer/renderer.rb:42:in `render_template'
  actionview (4.1.8) lib/action_view/renderer/renderer.rb:23:in `render'
  actionview (4.1.8) lib/action_view/rendering.rb:99:in `_render_template'
  actionpack (4.1.8) lib/action_controller/metal/streaming.rb:217:in `_render_template'
  actionview (4.1.8) lib/action_view/rendering.rb:82:in `render_to_body'
  actionpack (4.1.8) lib/action_controller/metal/rendering.rb:32:in `render_to_body'
  actionpack (4.1.8) lib/action_controller/metal/renderers.rb:32:in `render_to_body'
  actionpack (4.1.8) lib/abstract_controller/rendering.rb:25:in `render'
  actionpack (4.1.8) lib/action_controller/metal/rendering.rb:16:in `render'
  actionpack (4.1.8) lib/action_controller/metal/instrumentation.rb:41:in `block (2 levels) in render'
  activesupport (4.1.8) lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
  /Users/mark/.rbenv/versions/2.1.3/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
  activesupport (4.1.8) lib/active_support/core_ext/benchmark.rb:12:in `ms'
  actionpack (4.1.8) lib/action_controller/metal/instrumentation.rb:41:in `block in render'
  actionpack (4.1.8) lib/action_controller/metal/instrumentation.rb:84:in `cleanup_view_runtime'
  activerecord (4.1.8) lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
  actionpack (4.1.8) lib/action_controller/metal/instrumentation.rb:40:in `render'
  actionpack (4.1.8) lib/action_controller/metal/implicit_render.rb:10:in `default_render'
  actionpack (4.1.8) lib/action_controller/metal/implicit_render.rb:5:in `send_action'
  actionpack (4.1.8) lib/abstract_controller/base.rb:189:in `process_action'
  actionpack (4.1.8) lib/action_controller/metal/rendering.rb:10:in `process_action'
  actionpack (4.1.8) lib/abstract_controller/callbacks.rb:20:in `block in process_action'
  activesupport (4.1.8) lib/active_support/callbacks.rb:113:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:113:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:229:in `block in halting'
  activesupport (4.1.8) lib/active_support/callbacks.rb:229:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:229:in `block in halting'
  activesupport (4.1.8) lib/active_support/callbacks.rb:229:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:229:in `block in halting'
  activesupport (4.1.8) lib/active_support/callbacks.rb:166:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:166:in `block in halting'
  activesupport (4.1.8) lib/active_support/callbacks.rb:166:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:166:in `block in halting'
  activesupport (4.1.8) lib/active_support/callbacks.rb:166:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:166:in `block in halting'
  activesupport (4.1.8) lib/active_support/callbacks.rb:166:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:166:in `block in halting'
  activesupport (4.1.8) lib/active_support/callbacks.rb:86:in `call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:86:in `run_callbacks'
  actionpack (4.1.8) lib/abstract_controller/callbacks.rb:19:in `process_action'
  actionpack (4.1.8) lib/action_controller/metal/rescue.rb:29:in `process_action'
  actionpack (4.1.8) lib/action_controller/metal/instrumentation.rb:31:in `block in process_action'
  activesupport (4.1.8) lib/active_support/notifications.rb:159:in `block in instrument'
  activesupport (4.1.8) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
  activesupport (4.1.8) lib/active_support/notifications.rb:159:in `instrument'
  actionpack (4.1.8) lib/action_controller/metal/instrumentation.rb:30:in `process_action'
  actionpack (4.1.8) lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
  activerecord (4.1.8) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
  actionpack (4.1.8) lib/abstract_controller/base.rb:136:in `process'
  actionview (4.1.8) lib/action_view/rendering.rb:30:in `process'
  actionpack (4.1.8) lib/action_controller/metal.rb:196:in `dispatch'
  actionpack (4.1.8) lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
  actionpack (4.1.8) lib/action_controller/metal.rb:232:in `block in action'
  actionpack (4.1.8) lib/action_dispatch/routing/route_set.rb:82:in `call'
  actionpack (4.1.8) lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
  actionpack (4.1.8) lib/action_dispatch/routing/route_set.rb:50:in `call'
  actionpack (4.1.8) lib/action_dispatch/journey/router.rb:73:in `block in call'
  actionpack (4.1.8) lib/action_dispatch/journey/router.rb:59:in `each'
  actionpack (4.1.8) lib/action_dispatch/journey/router.rb:59:in `call'
  actionpack (4.1.8) lib/action_dispatch/routing/route_set.rb:678:in `call'
  railties (4.1.8) lib/rails/engine.rb:514:in `call'
  railties (4.1.8) lib/rails/railtie.rb:194:in `public_send'
  railties (4.1.8) lib/rails/railtie.rb:194:in `method_missing'
  actionpack (4.1.8) lib/action_dispatch/journey/router.rb:73:in `block in call'
  actionpack (4.1.8) lib/action_dispatch/journey/router.rb:59:in `each'
  actionpack (4.1.8) lib/action_dispatch/journey/router.rb:59:in `call'
  actionpack (4.1.8) lib/action_dispatch/routing/route_set.rb:678:in `call'
  warden (1.2.3) lib/warden/manager.rb:35:in `block in call'
  warden (1.2.3) lib/warden/manager.rb:34:in `catch'
  warden (1.2.3) lib/warden/manager.rb:34:in `call'
  rack (1.5.2) lib/rack/etag.rb:23:in `call'
  rack (1.5.2) lib/rack/conditionalget.rb:25:in `call'
  rack (1.5.2) lib/rack/head.rb:11:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/params_parser.rb:27:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/flash.rb:254:in `call'
  rack (1.5.2) lib/rack/session/abstract/id.rb:225:in `context'
  rack (1.5.2) lib/rack/session/abstract/id.rb:220:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/cookies.rb:560:in `call'
  activerecord (4.1.8) lib/active_record/query_cache.rb:36:in `call'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
  activerecord (4.1.8) lib/active_record/migration.rb:380:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:82:in `run_callbacks'
  actionpack (4.1.8) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/reloader.rb:73:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  railties (4.1.8) lib/rails/rack/logger.rb:38:in `call_app'
  railties (4.1.8) lib/rails/rack/logger.rb:20:in `block in call'
  activesupport (4.1.8) lib/active_support/tagged_logging.rb:68:in `block in tagged'
  activesupport (4.1.8) lib/active_support/tagged_logging.rb:26:in `tagged'
  activesupport (4.1.8) lib/active_support/tagged_logging.rb:68:in `tagged'
  railties (4.1.8) lib/rails/rack/logger.rb:20:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/request_id.rb:21:in `call'
  rack (1.5.2) lib/rack/methodoverride.rb:21:in `call'
  rack (1.5.2) lib/rack/runtime.rb:17:in `call'
  activesupport (4.1.8) lib/active_support/cache/strategy/local_cache_middleware.rb:26:in `call'
  rack (1.5.2) lib/rack/lock.rb:17:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/static.rb:84:in `call'
  rack (1.5.2) lib/rack/sendfile.rb:112:in `call'
  railties (4.1.8) lib/rails/engine.rb:514:in `call'
  railties (4.1.8) lib/rails/application.rb:144:in `call'
  rack (1.5.2) lib/rack/lock.rb:17:in `call'
  rack (1.5.2) lib/rack/content_length.rb:14:in `call'
  rack (1.5.2) lib/rack/handler/webrick.rb:60:in `service'
  /Users/mark/.rbenv/versions/2.1.3/lib/ruby/2.1.0/webrick/httpserver.rb:138:in `service'
  /Users/mark/.rbenv/versions/2.1.3/lib/ruby/2.1.0/webrick/httpserver.rb:94:in `run'
  /Users/mark/.rbenv/versions/2.1.3/lib/ruby/2.1.0/webrick/server.rb:295:in `block in start_thread'

  Rendered /Users/mark/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/templates/rescues/_trace.html.erb (1.1ms)
  Rendered /Users/mark/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/templates/rescues/_request_and_response.html.erb (0.9ms)
  Rendered /Users/mark/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/templates/rescues/template_error.html.erb within rescues/layout (11.1ms)

I'm still in favor of starting up Redis on rake ci if it isn't already running.  Everything else in the development environment starts up automatically when you checkout the repo and run the task. (This is obviously unrelated to the PR).

I think this is looking great, apart from the issue I ran into. The renaming of ReportsController isn't a blocker but I think it will make the purpose of the controller a little clearer.

I'm :+1:, once this is has been rebased on develop and squashed (although @AudreyAltman says there's more to come on this branch, perhaps).

:sunglasses: cool.  This looks good to me.  I think the few minor comments are what remains.
Awaiting forthcoming rebase and functional changes, but will watch closely so we can get this merged as soon as it's ready.

Will someone review this latest commit, "change validation reports layout"?  This commit includes the final changes that Gretchen asked for.

I had to make one final commit b/c Gretchen and I realized that we needed another field in validation reports.

Awesome. I think this is ready to :squash: if Gretchen is happy with it.

:penguin: :tada: :penguin: :confetti_ball: :penguin:


Screenshots

Hi, I just downloaded the newest open XR toolkit app 1.3.0 and now I can't take screenshots through my HP reverb G2 VR headset.   Everything was fine before, and I have even tried going back to version 1.2. 4 but  the screenshots facility no longer works although everything else seems OK. I don't really know if it's the new version 1.3.0 or the fact that I recently downloaded the new update 12 for Microsoft Flight Simulator? Can you provide any help for me? Cheers for now!

Did you make sure screenshot is enabled from the desktop app? And that it's set to the keys you expect.

Yes. I tried different key set ups. I tried checking and unchecky the box.
I tried different photo format types. And I tried going back to 1.2.4. All
to no avail.
Appreciate your help thank you for now
Larry
On Sun, Mar 26, 2023, 16:22 Matthieu Bucchianeri @.***>
wrote:

Did you make sure screenshot is enabled from the desktop app? And that
it's set to the keys you expect.
—
Reply to this email directly, view it on GitHub
https://github.com/mbucchia/OpenXR-Toolkit/issues/470#issuecomment-1483999394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2LVDBUBP7SR4L6YLCFD5MLW57HCHANCNFSM6AAAAAAWH6UN4Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

Good news, the screenshot facility in the open XR toolkit started
mysteriously working again this morning. It could be the two nvidia files
that were automatically downloaded last night that has made this happen. I
don't know, but I'm just happy that it's working again. Before I go I would
just like to say that the toolkit has been a great adjunct to my Microsoft
flight simulator. I think it works a lot better with the tool kit running.
Cheers for now, Larry
On Sun, 26 Mar 2023 at 16:22, Matthieu Bucchianeri @.***>
wrote:

Did you make sure screenshot is enabled from the desktop app? And that
it's set to the keys you expect.
—
Reply to this email directly, view it on GitHub
https://github.com/mbucchia/OpenXR-Toolkit/issues/470#issuecomment-1483999394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2LVDBUBP7SR4L6YLCFD5MLW57HCHANCNFSM6AAAAAAWH6UN4Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

Resolved via DM.


Develco Heat Alarm HESZB-120

Adding Develco Heat Alarm HESZB120 which also has a temperature sensor.
I also added a Develco IasZone to the init.py file since this is used across many Develco devices which will be useful for PR's to come.

Codecov Report

Merging #1022 (aec60a1) into dev (8c61c6d) will decrease coverage by 0.66%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev    #1022      +/-   ##
==========================================
- Coverage   82.55%   81.88%   -0.67%
==========================================
  Files         189      191       +2
  Lines        4798     5002     +204
==========================================
+ Hits         3961     4096     +135
- Misses        837      906      +69

Impacted Files
Coverage Δ

zhaquirks/develco/__init__.py
100.00% <100.00%> (ø)

zhaquirks/tuya/valve.py
86.52% <0.00%> (-9.01%)
:arrow_down:

zhaquirks/philips/__init__.py
50.56% <0.00%> (-5.00%)
:arrow_down:

zhaquirks/tuya/ts0601.py
100.00% <0.00%> (ø)

zhaquirks/tuya/__init__.py
72.74% <0.00%> (ø)

zhaquirks/legrand/dimmer.py
100.00% <0.00%> (ø)

zhaquirks/tuya/ts0601_dimmer.py
100.00% <0.00%> (ø)

zhaquirks/tuya/air/ts0601_air_quality.py
100.00% <0.00%> (ø)

zhaquirks/philips/ltd011.py

zhaquirks/philips/zhadimmablelight.py

... and 17 more

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

34 of 34 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 81.887%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
4096

Relevant Lines:
5002

💛  - Coveralls

New commit done with changes recommended. I have kept the "ZoneStatus" class in there, because according to Develco spec sheet, it expects a t.uint16_t where as the Zigpy library is expecting a t.bitmap16.

Can you share the spec sheet too please?

Can you share the spec sheet too please?

Sure, it is located here.

Lmao they say it is an uint16, but then tell you what each bit do, essentially telling you -- yeah, it is a bitmap.
Kudos to them for providing the device specs, makes our life easier, but still don't understand why it wasn't the standard implementation for the commands ?
uint16 and bitmap are the same, you could use it interchangeably

Oh, my bad!
Should I get rid of the ZoneStatus also then?

Yeah, I'd leave only server commands only. Everything else looks to be backward compatible

OK done that!

Yes tested and working perfectly


Use JENKINS_SECRET and JENKINS_NAME env vars if present

Fix #3

@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@reviewbybees done


Made Client better

Added README.md
Added comments to all files
Switched synchronous requests to AJAX
Got rid of unnecessary verbose jQuery (not the AJAX, just the DOM part)

Don't worry about the 70 different commits, just focus on the fact that only 4 files have been changed.

https://github.com/Gigabyte-Giant/KA-Contest-Judging-System/commit/b25f2e5aa79c87dc4fc20570163c9ef001a2706f


Video Compressor Not Working at ALL

String file = null;
                           try {
                                file = SiliCompressor.with(getContext()).compressVideo(list.get(i).getOriginalPath(), Environment.getExternalStorageDirectory() + "/"+ URLUtil.guessFileName(String.valueOf(list.get(i).getOriginalPath()), null, null));
                            } catch (URISyntaxException e) {
                                e.printStackTrace();
                            }`

That's my code and when glide trying to get the picture is not working, but its working when I don't compress the video

Hi @icangku
How do you say that video compression is not working because you not able to get an image  from the compressed file using Glide?
I have seen in your code, are you passing the file absolutePath as parameter to the compression method?

yes, because its asking for path not file right?

can you help me?

why don't u make it same as compress image just using file? i really need ur help

try {
                                String file = SiliCompressor.with(getContext()).compressVideo(list.get(i).getOriginalPath(), Environment.getExternalStorageDirectory().getAbsolutePath()+"/DCIM/Camera/"+list.get(i).getOrientationName());
                                videos.add(videos.size(), file);
                            } catch (URISyntaxException e) {
                                e.printStackTrace();
                            }

that's my latest code, still not working glide tells me that file not found

btw, i'm using the code in my fragment, is it influencing something

I've tried also the example, that's why i commented here https://stackoverflow.com/questions/45785439/video-compression-using-silicompressor-in-android-not-working
but its still not working

Use asyncTask


feat(CI): update run coveralls

Close #4

Changes Unknown when pulling 828d7b5c3f54ba5c760d59889ba902014c6e9dd6 on feat/CI/update-coveralls into ** on master**.


Results differing between paper and repository?

Hey,
your beat tracking plot in here
shows different results than the one in the paper - is there a mistake somehow?

Hi,
Good observation! It looks like the Max F-Measure and F-Measure labels have been erroneously switched in the repo. Thanks for catching this, a fix will be made in the coming days.

Note this has been fixed for the next release in the commit here:
https://github.com/urinieto/harmonixset/commit/4425d3181a849fd64483ea11ae965f7e94153e24


fix unreadable characters bug

After a period of use, such modification can indeed fix the problem of garbled characters.

Thanks 👍


Create a dashboard

Some sort of an overview page, which gives a summary of everything the user has stored somehow (i.e. bus favourites)

won't do...


LLVM 15.0 support

A variety of changes to get a clean build and passing tests when using LLVM 15.0.

I've noticed problems when using LLVM 15 but building with earlier clang, so the cmake scripts now print a warning in that case, so if users encounter trouble they have a hint about what to do to fix it.

For our CI tests on Mac, force the MacOS-11 test to use llvm 14, and the MacOS-12 test to use llvm 15.

IMPORTANT TO-DO / CAVEATS:

When doing JIT at optlevel 12 or 13, I had to disable a number of passes that don't seem to exist anymore in LLVM 15. This is enough to get it working, and to be honest, I don't know if anybody uses these opt levels.  But we need to revisit this, because I don't know if there these are cases where the names of the passes merely changed or that new passes take their place (in which case we should add the new passes, not stop after merely disabling the deprecated ones). For that matter, optlevel modes 11, 12, 13 are supposed to match what clang does for -O1, -O2, -O3, and that changes from one release to the next, so we should probably revisit this list and make sure it's matching clang's current choices (which I assume are crafted and periodically revised by clang's authors).

LLVM 15 switches to "opaque pointers". It still supports typed pointers...  for now. But as you can see in the diffs, I had to disable a variety of deprecation warnings and take some other actions to put LLVM 15 in the old "opaque ptr" mode to match our use of LLVM <= 14. But this is only temporary, because the typed pointer mode is expected to be removed entirely in LLVM 16. So at some point in the next few months, we are going to need to support opaque pointers in our use of LLVM. (Also note: for a while, we're going to have a bunch of ugly #if guards or other logic to support both opaque pointers for users with llvm >= 16 and also typed pointers for users with llvm <= 14, until such time as our LLVM minimum is at least 15, which I expect is not a reasonable assumption for at least a couple years.)

Closes #1587
Signed-off-by: Larry Gritz<EMAIL_ADDRESS>

I want to get this merged ASAP because a few days ago, Homebrew upgraded their default llvm to 15, so a large swath of Mac users now can't build OSL (without figuring out the arcane way to install and use a non-default llvm 14 or earlier version). I expect to do the merge tomorrow unless somebody raises a serious objection to the contents of this PR.
But as I noted, although this patch works as-is, there are a few things we need to return to. One is the issue of updating the set of passes we use for optlevel 12 and 13, which I hope @AlexMWells or @steenax86 might tackle, because it is they who wrote that section (which isn't exactly a perfect replica of the clang logic as I oversimplified above, but includes some curation and fine tuning of the passes based on their specific knowledge).
Another caveat worth mentioning is that I've tested this only on Mac, because my own use of Homebrew to manage an llvm install forced the issue upon me. I made a good effort today to build llvm 15 on Linux at work, but haven't been able to get it built, it may be that our compilers or some other component of our build environment are too old to do it properly. It might take some time to dig into. Anyway, this is a long-winded way of saying that additional problems crop up with llvm 15 on Windows or Linux specifically, since I haven't personally tested them yet and they aren't part of the CI, and we'll address those when and if they do. (I will separately look into how we get an llvm15 into our Linux CI; it obviously already is there for Mac.)


Disable linting on code climate

We haven't configured it yet, so it's complaining. We don't actually use
eslint yet, so its initial inclusion was more aspirational that useful.

👍


Wrong README for todo-csharp-cosmos-sql (not Mongo!)

https://github.com/Azure-Samples/todo-csharp-cosmos-sql. We reference MongoDB but this should be SQL?

See arch diagram and also https://github.com/Azure-Samples/todo-csharp-cosmos-sql/blob/main/infra/main.bicep

@jongio @vhvb1989 do you know if this todo-csharp-cosmos-sql does provision Cosmos DB(MongoDB API) similar to todo-java-mongo and todo-nodejs-mongo?

@rajeshkamal5050 , yes, it uses cosmos-sql-db (see: https://github.com/Azure-Samples/todo-csharp-cosmos-sql/blob/main/infra/app/db.bicep#L26)
The template name is good. The readme needs to be updated


Set DPS max current from MODEL specified in makefile

Set the CONFIG_DPS_MAX_CURRENT #define based on the MODEL chosen. You can however override this if you so wish.
This was based on the following https://github.com/kanflo/opendps/issues/45#issuecomment-435242383
I haven't tested if this compiles/works as I don't have my toolchain with me...

When running the following command:
make -C opendps MODEL=DPS5015 WIFI=0
I get the following error:
func_cv.c:94:12: error: 'CONFIG_DPS_MAX_CURRENT' undeclared here (not in a function)
     .max = CONFIG_DPS_MAX_CURRENT,

I don't have a toolchain here but I'm going to guess that dps-model.h needs to be included in func_cv.c and func_cc.c. I'll make a pull request for it

Darn. I tried building but somehow this did not show up until I did make clean. Sorry 'bout that.

Thanks @Xenoamor


Possible to define an index on a non-existent column

Invalid SQL is generated without an error.

Probably better to push this to https://github.com/propelorm/Propel2

Thanks, submitted it: https://github.com/propelorm/Propel2/issues/906


a pure es module import would be fantastic

I frequently like to use dat.gui in small experiments on my local machine. I'd love to not need to have a package manager to install/build/configure dat.gui for these fast experiments.
Here is how I'd like to use dat.gui:
<script type="module">
    import dat from<EMAIL_ADDRESS>
    const obj = { x: 40, y: 100 }

    const gui = new dat.GUI()
    gui.add(obj, 'x')
    gui.add(obj, 'y')
</script>

Right now this snippet won't work because the source code doesn't include the file extension when it imports modules (.js)
This would be really amazing for prototyping, just being able to wire up this usage of dat.gui without all the ceremony of needing node, npm, bundling tools, bundling config, etc.

I guess the files need to be renamed to extension ".mjs", so they're compatible to both Node.js and browser environments.

My understanding of .mjs is that it's a workaround that was used in/proposed node, before they added es modules support.
We could potentially use .mjs but at this point it might be better to stick with .js. .mjs isn't technically a known MIME type.

You'll need to import the final build ES6 module, not the source files, to use the module in a browser. Try:
<EMAIL_ADDRESS>

Thanks for the link!
I'm curious why the es6 build doesn't use let, const, or other es6 nice-ities? This seems to be transpiled down to an older javascript dialect (es5?)

The purpose of the build is to provide an ES module — it's not meant to be any different otherwise than the CommonJS module version.

The purpose of the build is to provide an ES module

yeah I get that, I guess what I mean is, es module support was one of the last things to go into es 6, so if the output target of build/dat.gui.module.js is es module based, why not leverage other capabilities that are also in es6?

not the source files,

A pity though. B/c by adding the extension ".js" to something like import Color from './color/Color';:
import Color from './color/Color.js';
Throughout the source https://github.com/dataarts/dat.gui/blob/master/src/dat/index.js
It would allow us to use import directly on "dat.gui"'s source like this:
import dat from 'https://unpkg.com/dat.gui/src/dat/index.js'

by adding the extension ".js" ... it would allow us to use import directly on "dat.gui"'s source

It isn't quite that simple: the build process also includes the .scss files used to style dat.gui. The build outputs are meant for distribution on npm and on CDNs, but the source code is not. See:
https://github.com/dataarts/dat.gui/blob/071edeb334c246ac5eb406010c773dfbb8f6dcce/src/dat/gui/GUI.js#L28

es module support was one of the last things to go into es 6, so if the output target of build/dat.gui.module.js is es module based...

If you're importing scripts from a CDN, sure. But users may be using ES imports in ES5 code, and relying on something like Rollup to strip the imports without fully transpiling the code. Bundlers like Rollup handle import/export by default, but require additional plugins to fully transpile other parts of ES6 or ES7.
I'm not saying this is the "right" way to do this — that's subjective. But today this project's CommonJS and ES module builds are both compiled to ES5, which is the default behavior of rollup-plugin-babel, and I'd prefer not to drop that backward-compatibility without a compelling reason.

I'd prefer not to drop that backward-compatibility without a compelling reason.

Yeah I'm not asking anyone to drop backwards compatibility. :) I'm just asking if we could provide a "pure" es modules based thing alongside all of our existing stuff, which would enable me to drop node/npm/packag.json/build tools/legacy module formats, etc.
with the advent of good browser support + deno, now seems like a prime time to start re-evaluating the way we've been doing things for the last decade of javascript.

The build published under the module entry (i.e<EMAIL_ADDRESS>is an ES module, written in pure JavaScript, compatible with all modern browsers. You don't need any build tools to use it. The fact that it doesn't contain let/const or ES6 Classes doesn't really seem like it should be holding your project back, correct?
I've shipped modern ES6+ in other libraries, and I have no problem with that practice, but I think this project's use of ES5 is reasonable and sufficient. This is, after all, a library dating back to 2004.
I'd prefer not to add another build output unless there is a clear way to make it useful, e.g. a modern entry in package.json. That doesn't exist today, but perhaps will in the future: https://twitter.com/_developit/status/1263174528974364675.

The fact that it doesn't contain let/const or ES6 Classes doesn't really seem
like it should be holding your project back, correct?

Well, I didn't open this issue because I'm held back. :) I have dozens of projects that have been using an npm based build chain. And I'm certainly able to use dat.gui in all kinds of existing projects. (dat.gui is a great tool by the way!)
On the other hand, just because things work doesn't mean they are optimal, and won't stop me from continuously evaluating how I can improve tools and libraries I rely on. :)

Ok — regarding the original question of the issue, we do provide a "pure ES module import" as explained above. Publishing a build (whether it uses ES imports or CommonJS) that uses other new ES6 features, rather than ES5, I see as a separate question. For the time being I am not willing to make that change.

regarding the original question of the issue, we do provide a "pure ES module import" as explained above

sounds reasonable, thanks for your time!


Collection display

On pages that show all the inscriptions in a collection, the blurb at the top of the page that describes the collection should have an "open/close" button or [more...]/[less...] link so that it doesn't take up so much room on the page.

close button, too


embedded resource with alt tag is broken in ckeditor

Steps to Reproduce
Compare:

the markdown in the django admin

{{< resource 692ac2c1-ffd1-23f0-7e6f-1bba6fa9ea14 "Photo of Professor Gilbert Strang in front of a chalkboard. " >}}

{{< resource 692ac2c1-ffd1-23f0-7e6f-1bba6fa9ea14 >}}

with the page loaded in ocw-studio-rc:

Expected Behavior

Both these embedded resources should look the same (more or less) in ocw-studio.
If you edit the page, and save it, both embedded resources should be preserved, without escaping.

Actual Behavior

The embedded resource shortcode with the alt text parameter is loaded in ckeditor as raw text
If you edit and save the page, the < is escaped.

Looking at this some more, I think this is degenerate short code. The string parameter doesn't seem to have any affect at all.

This was a mistake from the rootrelative url fixer. It it including the title as a second positional parameter to the shortcode. Looks like title should only have been included for videos and it should have been a named parameter.


Error hover text too small not very readable

Insiders:

Stable:

Also noticed for insiders where it says 'error' and 'any', should me monospace since it's direct reference to code?. Then again it does say it after..

It is because of using normal font. It was only for short time and now I am using the editor font again.


[Bug] chart state after updateSpec is incorrect

Version
@visactor/vchart :  "1.12.2"
Link to Minimal Reproduction
null
Steps to Reproduce
state_spec.txt
Current Behavior
https://github.com/user-attachments/assets/a329b345-00ce-4d4a-9664-22cc8c38e09d
Expected Behavior
updateSpec后，没有选中状态，所有图元都高亮
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

可以在更新前调用 clearAllStates() 解决这个问题


Homepage of MX version of site is missing homepage

BUG
Current Behavior
When going to https://www.dosomething.org/mx as a non-admin user, the homepage tiles do not load and instead a 404 message is displayed
Desired Behavior
The homepage tiles should display the featured campaigns instead of the 404 message.
Steps to Replicate
Go to https://www.dosomething.org/mx
Why This Matters
The homepage experience is broken, making it confusing for site visitors. Additionally, users are unable to signup for homepage featured campaigns unless they locate them elsewhere.
Countries Affected (optional)
Mexico
Relevant Screenshots + Links
Using Torguard (Mexico City) as an anonymous user:

Same happens when going to https://www.dosomething.org/mx without Torguard (as an anonymous user).
This is the view when logged in as an admin in the US, going directly to https://www.dosomething.org/mx (same, as expected, if using Torguard):

One of the campaigns on the homepage (first tile) is: https://www.dosomething.org/mx/voluntario/beneficia-con-lo-que-ya-no-necesitas?source=node/1141. I can access this campaign as an anonymous user without issue.

I noticed on https://www.dosomething.org/mx/node/1141/edit/es-mx that the translation is unpublished. This box is ticked off for: https://www.dosomething.org/br/node/1141/edit/pt-br

I checked the box for "This translation is published" - this appears to have fixed the issue with the homepage tiles.
https://www.dosomething.org/mx/node/1141 is now accessible to anon users.

@ngjo : Would you mind letting our partners in Mexico know that the homepage should be working now? There's no revision history turned on, but I suspect that somehow this box was unchecked on the last edit before this issue.

Oooooh quick and smart sleuthing @mirie ! I know one thing we've seen on the US scholarship page is that when someone edits the page, it sometimes mysteriously un-publishes itself.
I've checked the site on Torguard too and it looks good, so going to close the issue and let our partners know. Thank you!!!


Devel

Keep track of the bodies as Frames

Thanks for this PR. Unification of names with "frames" is good. Should we start to document body listing as deprecated?
What is the interest of remembering the type of frames (body vs oppoint vs joint)? Is there any explicit demand for this feature? If so, it would be nice to document this demand somewhere to keep track of it.

Coverage decreased (-0.7%) to 82.506% when pulling ff1046028268cba5355a6c75107d30dc27315e84 on fvalenza:devel into 4743d3a5faa5fb5ef13f46775e8c8789d3523852 on stack-of-tasks:devel.

This is related to #179.

I would go a little bit deeper by adding the type Joint inside FrameType and registering all the joints inside. The idea is to have everything directly accessible from the vector frames in Model, simplifying the API.

This is an interesting proposition. I am afraid that it may simplify the API a little bit too much (loosing efficiency in runtime). I think we should try to imagine how this "frames" could be used by a third-party.

The adding of Joint in the frame list is just a redundant information to help the end-user to easily retrieve the objects (SENSOR, BODY, JOINT, ...) created during parsing procedure.
The efficiency can be near the same if in the method getFrameJacobian we make the distinction between Joint frame and the other frame types.

Having a unified way of getting joints regardless of their type (Fixed or not) is a feature that will simplify the work of porting HPP to Pinocchio.

Coverage increased (+0.09%) to 83.277% when pulling cd056d01544ad9fa09937a0aa36ad9bb98e83cc0 on fvalenza:devel into 4743d3a5faa5fb5ef13f46775e8c8789d3523852 on stack-of-tasks:devel.

Coverage increased (+0.09%) to 83.277% when pulling cd056d01544ad9fa09937a0aa36ad9bb98e83cc0 on fvalenza:devel into 4743d3a5faa5fb5ef13f46775e8c8789d3523852 on stack-of-tasks:devel.

:+1:


Added crosscompile toolchain file for aarch64.

Try running.
$ sudo apt install gcc-aarch64-linux-gnu
$ cmake .. -DCMAKE_TOOLCHAIN_FILE=../aarch64.toolchain
$ make

Artifacts can tested on a Pi or qemu+Docker.


add support for cloud based syncing (e.g. Google Drive) via rclone

Nice work!
Does this move files off of the drive or mirror them?

it's set to move... easy to change the behavior by editting the file archive-clips.sh and changing the rclone command from move to  sync or copy
rclone move "$file_name" "$drive:$path" >> "$LOG_FILE" 2>&1 || echo ""
i noticed the original version was just moving the files over so i did the same thing.
everything seems to be working okay using test data - i'll get a real run on my drive home from work tonight.

Please test this process if you haven't, already; I'm not sure you how got past line 227 in setup-teslausb .

@cimryan - sorry about that. i'll do a fresh install with a new sdcard and confirm that everything is working.

okay - i started with a fresh sd card and confirmed the install works. i ran into two issues that didn't come up during testing from a clean install.

rclone is complaining about HOME not being set so it can't find the directory. i can get around this one by passing in the config file from when calling the script.

it looks like rclone updates it's token from time to time but as you know the file system is read-only.

suggestions on how to deal with item 2?

Do we get to control where the token gets written? We could add another partition after the backingfiles partition and leave that one read/write.

yes - we can specify the config location upon creation of the config.
i like the idea of having a read/write partition. we can store other configs in there too. also things like fake-hwclock (which will fix the time sync issue) needs a writeable directory. thoughts on size -- 5MB should be more than enough?

The instructions currently require a MicroSD card which is at least 8GB in size; I think we can reserve up to 100MB, without issue.

Are you okay with accepting this PR first? It's is marked as experimental anyway... I can then submit another one with the changes to support the new partition hopefully over the weekend.

I've merged into the branch u/rtanaka/rclone_archive . I'm not inclined to merge to master with known bugs, but if there's a compelling reason to do so I could be convinced.


Considerable difference between contracted and non-contracted routes

I have two routes in Norway, same coordinates and "car.classifications" profile. The first is calculated with a router database with a contracted profile and the second is calculated with a router database without a contracted profile.
Both routes should be identical but they are not, and the route with the contracted profile has some strange choices. The non-contracted route is similar to what Google maps shows, but the contracted route is very different.
I'm using Itinero 1.5. I've also tried the latest pre-release with the same result.
Start position: 68 51 40.86N 18 20 54.30E
End position: 69 23 28.09N 20 16 02.13E
Non-contracted route (correct route):

Contracted route (incorrect route):

I want to have a contracted route that looks like the non-contracted image. Both routes should also be identical regardless of contracted and non-contracted profiles.
Any help would be much appreciated!

Possible duplicate of #267?

To be able to use this routing library, routing with contracted profiles must generate the correct route.
Is anyone looking into this issue for a possible fix?

this requires the newest develop instance of Reminisce
See also
https://github.com/itinero/routing/pull/302

I've tried with the latest develop instance of Reminiscence with the same result. I've also tried with the latest develop instance of OsmSharp, Itinero.IO.Osm and Itinero as well, but still the same result.
I've attached two routerdb databases which can be used to reproduce the issue.
Using the "car.classifications" profile, the routerdb "norway-extract.osm.routerdb" and "norway-extract-contracted.osm.routerdb" with the following coordinates will reproduce the issue:
Start latitude: 68.86135
Start longitude: 18.3484173
Stop latitude: 69.3911362
Stop longitude: 20.2672577
RouterDB.zip

Can you try on https://github.com/itinero/routing/pull/302 and by linking Reminiscence with it locally?
Let me know if you still have issues and I will take a look

I've tried your branch in #302 and linked develop of Reminiscence, but the result is the same. If you try the router databases attached above you can easily reproduce the issue.

When contracting the profile after loading the OSM data without restrictions and using the AugmentedWeightHandler, the route is correctly calculated.
So it seems that contracted profiles with restrictions is the problem here.

Is there any progress on this issue?

I d k, @xivk  hasn't been around here for some time, he was active in OsmSharp where he my PR was take and the version was increased https://github.com/OsmSharp/core/pull/101.
Is there anyway I can be of assistance?

P.s.
I think you can also fix this in WeightMatrixAlgorithm:
There's definitely improvement as the Weight class offers more than I am using here.
//295
//Todo hope this is correct but tis seems the GetAugmentedWeightHandler is not really used afaik
            //Allocations may be heavy here
            if (_router.Db.HasContractedFor(_profile.Profile))
            {
                var weightsResult = _router.TryCalculateWeight(_profile, _router.GetAugmentedWeightHandler(_profile), locations);
                var v = weightsResult.Value;
                _weights = new float[v.Length][];
                for (int i = 0, e = v.Length; i < e; ++i)
                {
                    int j = v[i].Length;
                    _weights[i] = new float[j];
                    for (; j >= 0; --j)
                    {
                        _weights[i][j] = v[i][j].Value;
                    }
                }
            }
            else
            {
                var weightsResult = _router.TryCalculateWeight(_profile, _weightHandler, locations, locations,
               nonNullInvalids, nonNullInvalids, _settings);
                _weights = weightsResult.Value;
            }

Hey, sorry all, very busy with my day job. I still follow here but fixing this (and first figuring out what the root cause is) will take me a few days (at least) and I still haven't found the spare time.

I'm not sure how to use the "TryCalculateWeight" code above.
I generate a contracted database once and save it, and load it later using deserialization for performance reasons.
Most of the issues occur when contracting the profile after loading the OSM data with restrictions (I guess this is what you call "turn based routing"), but there are a few issues that occur without restrictions as well as shown bellow.
So there are issues as the ones bellow as well as the ones at the top of this issue related to contracted databases.

I don't think there is a workaround for all of these issues as I have tried for a while now without any luck.

Is there any progress on this issue?

Is there any feedback or progress for a solution for this issue?


Building azure-storage-blobs on Linux

Query/Question
I like to verify if I am following proper steps to build and install azure-storage-blobs_12.1.0. I previously did build azure-storage-blobs_12.0.1 and was able to link sample code just fine. Please let me know if I am missing steps or if they are wrong. Also, I am building my project with c++17 and azure SDK cmake sources are set to 14. Should I expect any issues/incompatibilities? Should I build everything with c++17 or c++14?
Why is this not a Bug or a feature Request?
Not applicable
Setup (please complete the following information if applicable):

OS: Ubuntu 20.04
IDE : vim/cmake 3.16.3
gcc/g++: g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
All depended libraries were installed apt install

Information Checklist
Kindly make sure that you have added all the following information above and check off the required fields otherwise we will treat the issuer as an incomplete report

[x] Query Added
[x] Setup information Added

Following steps were taken to build this project. Please section comment at the very bottom.
$ cd ~/github
$ git clone https://github.com/Azure/azure-sdk-for-cpp.git
$ cd azure-sdk-for-cpp
$ git checkout azure-storage-blobs_12.1.0
$ mkdir build; cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..

This produces the following output
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- The CXX compiler identification is GNU 9.3.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Found CURL: /usr/lib/x86_64-linux-gnu/libcurl.so (found suitable version "7.68.0", minimum required is "7.44")
Libcurl version 7.68.0
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "1.1.1f")
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/core/azure-core/src/private/package_version.hpp
-- VERSION_MAJOR 1
-- VERSION_MINOR 3
-- VERSION_PATCH 0
-- VERSION_PRERELEASE beta.1
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/identity/azure-identity/src/private/package_version.hpp
-- VERSION_MAJOR 1
-- VERSION_MINOR 2
-- VERSION_PATCH 0
-- VERSION_PRERELEASE beta.1
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/keyvault/azure-security-keyvault-keys/src/private/package_version.hpp
-- VERSION_MAJOR 4
-- VERSION_MINOR 1
-- VERSION_PATCH 0
-- VERSION_PRERELEASE beta.1
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/keyvault/azure-security-keyvault-secrets/src/private/package_version.hpp
-- VERSION_MAJOR 1
-- VERSION_MINOR 0
-- VERSION_PATCH 0
-- VERSION_PRERELEASE beta.1
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.10")
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/storage/azure-storage-common/src/private/package_version.hpp
-- VERSION_MAJOR 12
-- VERSION_MINOR 1
-- VERSION_PATCH 0
-- VERSION_PRERELEASE
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/storage/azure-storage-blobs/src/private/package_version.hpp
-- VERSION_MAJOR 12
-- VERSION_MINOR 1
-- VERSION_PATCH 0
-- VERSION_PRERELEASE
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/storage/azure-storage-files-datalake/src/private/package_version.hpp
-- VERSION_MAJOR 12
-- VERSION_MINOR 1
-- VERSION_PATCH 0
-- VERSION_PRERELEASE
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/storage/azure-storage-files-shares/src/private/package_version.hpp
-- VERSION_MAJOR 12
-- VERSION_MINOR 1
-- VERSION_PATCH 0
-- VERSION_PRERELEASE
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/storage/azure-storage-queues/src/private/package_version.hpp
-- VERSION_MAJOR 12
-- VERSION_MINOR 1
-- VERSION_PATCH 0
-- VERSION_PRERELEASE beta.1
-- AZ_LIBRARY_VERSION
By default, if no option is selected, on POSIX, libcurl transport adapter is used.
-- Retrieving version from /home/mrs/github/azure-sdk-for-cpp/sdk/template/azure-template/src/private//package_version.hpp
-- VERSION_MAJOR 1
-- VERSION_MINOR 0
-- VERSION_PATCH 0
-- VERSION_PRERELEASE
-- AZ_LIBRARY_VERSION
-- Configuring done
-- Generating done
-- Build files have been written to: /home/mrs/github/azure-sdk-for-cpp/build

Here is output from ```ccmake ..``
 BUILD_CODE_COVERAGE              OFF
 BUILD_DOCUMENTATION              OFF
 BUILD_PERFORMANCE_TESTS          OFF
 BUILD_STORAGE_SAMPLES            OFF
 BUILD_TESTING                    OFF
 BUILD_TRANSPORT_CURL             OFF
 BUILD_TRANSPORT_CUSTOM           OFF
 BUILD_TRANSPORT_WINHTTP          OFF
 CMAKE_BUILD_TYPE                 Release
 CMAKE_INSTALL_PREFIX             /usr/local
 CURL_DIR                         CURL_DIR-NOTFOUND
 MSVC_USE_STATIC_CRT              OFF
 RUN_LONG_UNIT_TESTS              OFF
 WARNINGS_AS_ERRORS               ON

Next is building
$ make -j 4
...
...
[100%] Building CXX object sdk/storage/azure-storage-files-datalake/CMakeFiles/azure-storage-files-datalake.dir/src/datalake_utilities.cpp.o
[100%] Linking CXX static library libazure-storage-files-datalake.a
[100%] Built target azure-storage-files-datalake

Next, I create deb package with ```checkinstall`` for backup
$ sudo checkinstall

This package will be built according to these values:

0 -  Maintainer: [ buildMaster ]
1 -  Summary: [ Azure c++ sdk ]
2 -  Name:    [ azure-storage-blobs ]
3 -  Version: [ 12.1.0 ]
4 -  Release: [ 1 ]
5 -  License: [ MIT ]
6 -  Group:   [ checkinstall ]
7 -  Architecture: [ amd64 ]
8 -  Source location: [ build ]
9 -  Alternate source location: [  ]
10 - Requires: [  libxml2  ]
11 - Recommends: [  ]
12 - Suggests: [  ]
13 - Provides: [ build ]
14 - Conflicts: [  ]
15 - Replaces: [  ]

Enter a number to change any of them or press ENTER to continue:

Next, elect all checkinstall defaults. Deb package created.
  By the way azure-sdk was built with default c++14 where my test application was build using c++17 and linked o the above build library.
Am I missing any steps above? Or should be done differently?
One issue I have is with integrating it with my application the cmake-way. Below are relevant cmake parts added to my test application CMakeLists.txt file
set(PROJ_NAME     "azure-storage-blobs-test")
project(${PROJ_NAME} VERSION "1.0.0" LANGUAGES CXX)

include(CheckIncludeFileCXX)

set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)
set(CMAKE_C_FLAGS     "${CMAKE_C_FLAGS} -Wall -pedantic -Wextra -Wunused-parameter -Wformat-security -Wunreachable-code -fdata-sections -ffunction-sections -Wcast-align")
set(CMAKE_CXX_FLAGS   "${CMAKE_CXX_FLAGS} -Wall -pedantic -Wextra -Wunused-parameter -Wformat-security -Wunreachable-code -fdata-sections -ffunction-sections -Wcast-align")

set(CMAKE_C_FLAGS_DEBUG   "-g -O0" CACHE INTERNAL "C debug compiler flags")
set(CMAKE_CXX_FLAGS_DEBUG "-g -O0" CACHE INTERNAL "C++ debug compiler flags")

set(CMAKE_C_FLAGS_RELEASE   "-Os -flto" CACHE INTERNAL "C release compiler flags")
set(CMAKE_CXX_FLAGS_RELEASE "-Os -flto" CACHE INTERNAL "C++ release compiler flags")

find_path(LIBUUID_INCLUDE_DIR uuid.h PATH_SUFFIXES uuid)
find_library(LIBUUID_LIBRARY libuuid.a)

find_package(azure-storage-blobs-cpp CONFIG REQUIRED)

if (azure-storage-blobs-cpp_FOUND)
    include_directories(${azure-storage-blobs-cpp_INCLUDE_DIRS})
    set(azure-storage-blobs-cpp_LIBRARY Azure::azure-storage-blobs)
else(azure-storage-blobs-cpp_FOUND)
    message(STATUS "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!")
    message(STATUS "You need to install git clone --depth 1 -b azure-storage-blobs_12.1.0 https://github.com/Azure/azure-sdk-for-cpp.git")
    message(STATUS "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!")
    message(FATAL_ERROR " You need to install azure-sdk-for-cpp library")
endif(azure-storage-blobs-cpp_FOUND)

file(GLOB app_SRCS src/*.cpp include/*.h)

list_files( "${app_SRCS}" )

add_executable(${PROJECT_NAME} ${app_SRCS})

target_link_libraries(${PROJECT_NAME}
                        ${LIBUUID_LIBRARY}
                        ${azure-storage-blobs-cpp_LIBRARY})

So my issue is that I have to add
set(azure-storage-blobs-cpp_LIBRARY Azure::azure-storage-blobs)

vs cmake detecting it. Am I missing something?

CMake related question.

I will check that and report.
Also not sure if I should open a separate ticket but I realized I hade to build azure sdk with -fPIC flax in order to link it to my main project with uses my own shared libs which were build with -fPIC. Else I had linking error linking my shared lib to azure sdk build static lib.
Would it be worth adding cmake option for PIC flag?

Also not sure if I should open a separate ticket but I realized I hade to build azure sdk with -fPIC flax in order to link it to my main project with uses my own shared libs which were build with -fPIC. Else I had linking error linking my shared lib to azure sdk build static lib.
Would it be worth adding cmake option for PIC flag?

CMake flag -DBUILD_SHARED_LIBS=ON will build share libraries of azure-sdk. Will that work for you?

That should work. But if anyone wants to produce his own shared lib linked yo azure static lib then PIC option should be added? I think...

@mrspirytus , I don't think we have the cmake configuration to create azure-storage-blobs-cpp_LIBRARY after find_package. Or, at least, that's not something we are testing/validating at the moment.
Usually, we expect customers to link the azure SDK libraries by doing:
target_link_libraries(${PROJECT_NAME} Azure::azure-storage-blobs)
So, after calling find_package and finding the package, you can use Azure::azure-storage-blobs directly instead of a CMake variable.

I was suggesting such option so just in case in future library name will change this would be transparent. All my cmake projects and all I did put in wild do append _INCLUDE and _LIBRARY to what ever was used in find_package.
Cheers

in case in future library name will change this would be transparent

Once the library is GA version, we promise to never introduce breaking changes.  Changing the lib name would break customers, so we will never change the name of introduce any breaking change within a major version.  So, for storage library version 12.x.x, there will be always backwards compatibility.
If a breaking change can't be avoided, it would require version 13.x.x to be released. But the SDK is designed to prevent this, and to only have minor versions released.


feat: Update Job Listing Feature

This PR implements an API endpoint to update job post details, allowing users to modify existing job listings in case of omissions or errors.
Changes

Added a new PATCH endpoint at api/v1/jobs/:id
Implemented authentication and authorization checks
Added input validation for request body
Updated JobsService with new update method
Added error handling for non-existent jobs
Implemented unit tests for the new functionality

Technical Details

Endpoint: PATCH api/v1/jobs/:id

Authentication: Bearer token required in Authorization header

Request body:
 {
  "title": "Software Engineer",
  "description": "Responsible for developing and maintaining web applications.",
  "location": "New York, NY",
  "deadline": "2024-12-31T23:59:59Z",
  "salary_range": "30k_to_50k",
  "job_type": "full-time",
  "job_mode": "remote",
  "company_name": "Tech Corp"
}

Note: All fields are optional for updates. Only provided fields will be updated.

Successful response (200 OK):
 {
  "message": "Job details updated successfully",
  "status_code": 200,
  "data": {
    "title": "Software Engineer",
    "description": "Responsible for developing and maintaining web applications.",
    "location": "New York, NY",
    "deadline": "2024-12-31T23:59:59Z",
    "salary_range": "30k_to_50k",
    "job_type": "full-time",
    "job_mode": "remote",
    "company_name": "Tech Corp",
    "is_deleted": false
  }
}

Error response (400 Bad Request):
{
  "status_code": 400,
  "message": ["validation error message"],
  "error": "Bad Request"
}

Testing

Added unit tests for JobsService update method
Tested successful update scenario
Tested error handling for non-existent jobs

Checklist

[x] Implemented PATCH endpoint at api/v1/jobs/:id
[x] Added authentication and authorization checks
[x] Implemented input validation
[x] Updated JobsService with update method
[x] Added error handling for non-existent jobs
[x] Implemented unit tests
[x] Ensured compliance with security standards

Related Issues
Closes #158

Please update the title, all small letters


[telemetry] CLI correlation with MSGraph/Azure calls

Now that we control HTTP calls to MSGraph/Azure, we should set the required headers to allow HTTP requests to be traced to individual azd commands.

Spec on ARM request headers: https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#client-request-headers
We should set x-ms-correlation-id with our traceId


vault-tasks: init at 0.4.0

vault-tasks is a TUI Markdown task manager. It will parse any Markdown file or vault and display the tasks it contains.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 354744 run on x86_64-linux 1

1 package built:

vault-tasks

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/2094


feat: use CLUSTER SHARDS

closes #350

Codecov Report
Patch coverage: 73.41% and project coverage change: -0.16% :warning:

Comparison is base (5128a75) 97.63% compared to head (3e46ff9) 97.47%.
Report is 1 commits behind head on main.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #361      +/-   ##
==========================================
- Coverage   97.63%   97.47%   -0.16%
==========================================
  Files          76       76
  Lines       30550    30714     +164
==========================================
+ Hits        29826    29937     +111
- Misses        610      646      +36
- Partials      114      131      +17

Files Changed
Coverage Δ

internal/cmds/cmds.go
100.00% <ø> (ø)

rueidiscompat/command.go
78.18% <54.11%> (-1.38%)
:arrow_down:

cluster.go
97.86% <91.25%> (-0.71%)
:arrow_down:

mux.go
100.00% <100.00%> (ø)

pipe.go
99.70% <100.00%> (-0.30%)
:arrow_down:

rueidiscompat/adapter.go
95.15% <100.00%> (+<0.01%)
:arrow_up:

... and 2 files with indirect coverage changes

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

These two cases should also be covered in tests.

Hi @Exca-DK,
It looks good now. Thank you very much for your contribution!


Support Typescript@5 moduleResolution bundle

Discussed in https://github.com/webpack/webpack/discussions/16682

Originally posted by tal-rofe January 29, 2023
TypeScript@5 now can configure moduleResolution to bundle
When configuring it, Webpack emits an error as it does not know it,
Is it going to be supported?
When I did:
		"moduleResolution": "bundler",

I got this error:

ERROR in ./tsconfig.base.json:6:23
TS6046: Argument for '--moduleResolution' option must be: 'node', 'classic', 'node16', 'nodenext'.
    4 |                 "target": "ES2017",
    5 |                 "module": "ESNext",
  > 6 |                 "moduleResolution": "bundler",
      |                                     ^^^^^^^^^
    7 |                 "noEmit": true,
    8 |                 "baseUrl": "./",
    9 |                 "allowJs": false,

webpack 5.76.2 compiled with 1 error in 536 ms
 ELIFECYCLE  Command failed with exit code 1.

Sorry, it is not a webpack plugin, please read carefully

TS6046: Argument for '--moduleResolution' option must be: 'node', 'classic', 'node16', 'nodenext'.

It means you still have old typescript version that doesn't support bundler, please read typescript documentation and check since which version it will work and update to this version, we can't fix it here, sorry again


Upgrade NPM and Dependancies of UI portals

Problem
The product UI portals are built on Node.js 16.x and the latest LTS version is 20.x (22.x will enter LTS in Oct 2024). Many of the dependancies in the portals are also deprecated or using older versions. This issue will track the effort upgrade dependancies and the node version.
Solution
Upgrade :

[ ] Node version
[ ] dependancies

Affected Component
APIM
Version
4.4.0
Implementation
No response
Related Issues
https://github.com/wso2/api-manager/issues/2191
Suggested Labels
No response

Changing @babel/plugin-proposal-foo packages to @babel/plugin-transform-foo
[1] https://github.com/babel/babel/issues/15786#issuecomment-1789047316

Updated the dependencies related to babel and smoke tested. No issues found so far.

Update (14-06-2024)
Admin Portal
Reduced the vulnerable dependancies in admin portal
from : 99 vulnerabilities (2 low, 50 moderate, 43 high, 4 critical)
to : 20 vulnerabilities (1 low, 3 moderate, 16 high)
pending :

migrate webpack-dev-server from v3 to v5

migrate eslint and related packages [1]
  npm init @eslint/config@latest
  npx @eslint/migrate-config .eslintrc.js

Further clear vulnerable packages and deprecated warnings

Upgrade possible remaining libraries to latest version

[1] https://eslint.org/blog/2024/05/eslint-configuration-migrator/#main

Upgraded Eslint and web pack. The remaining vulnerabilities are yet to be patched.
99 vulnerabilities (2 low, 50 moderate, 43 high, 4 critical) => 5 vulnerabilities (3 moderate, 2 high)

Note on running :npm run build:prod
The following error cannot be fixed since it's not fix in a the latest version of a dependent library url-js [1]
(node:19163) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

[1] https://github.com/garycourt/uri-js/pull/95

Devportal update
48 vulnerabilities (3 low, 15 moderate, 23 high, 7 critical) => 18 vulnerabilities (12 moderate, 5 high, 1 critical)
Lodash critical vulnerability in graphql-to-postman is yet to be fixed [1]
@stoplight/elements is not yet react 18 supported. this is a breaking change and the warnings cannot be resolved at the moment
[1] https://github.com/postmanlabs/graphql-to-postman/pull/22
[2] https://github.com/stoplightio/elements/issues/2365

Update
Fixed the dev portal swagger UI style rendering issue and related dependancies.
48 vulnerabilities (3 low, 15 moderate, 23 high, 7 critical) => 9 vulnerabilities (3 moderate, 5 high, 1 critical)

Admin portal latest log
npm i
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
npm warn deprecated<EMAIL_ADDRESS>Please switch to @apidevtools/json-schema-ref-parser

added 1514 packages, and audited 1515 packages in 3m

236 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Publisher portal update
25 vulnerabilities (2 low, 8 moderate, 14 high, 1 critical) => found 0 vulnerabilities
The @stoplight/elements being react 18 incompatible is not fixable.

Cannot migrate to ESLint 9 yet since several dependent libraries are not supported yet for the newly introduced flat config and other breaking API changes [1]
https://github.com/airbnb/javascript/issues/2961#issue-2229282975

Remaining test cases to verify / fix :

devportal/002-subscriptions/01-subscribe-unsubscribe-to-app-from-app.s
devportal/002-subscriptions/03-change-subscription-tier-on-an-application.spec.js
devportal/004-api-product/00-api-product-invoke-with-keys.spec..skipjs
e2e/developerFundamentalScenarios/01-create-api-from-scratch-and-publish.spec.skip.js
publisher/000-general/00-deploy-sample-api.spec.js
publisher/000-general/03-create-and-publish-graphql-api-with-all-information.spec.js
publisher/001-api-create/02-create-api-with-swagger-file-super-tenant.spec.js
publisher/001-api-create/03-create-api-with-swagger-url-super-tenant.spec.js
publisher/002-api-resources/00-api-resource-create.spec.js
publisher/002-api-resources/02-add-assign-global-scopes-for-api.spec.js
publisher/005-design-config/02-set-publisher-access-control-and-visibility-by-roles.spec.js
publisher/008-business-info/00-business-info.spec.js
publisher/011-lifecycle/02-deploy-as-prototype.spec.skip.js
publisher/012-documents/00-add-edit-inline-document.spec.js
publisher/012-documents/02-view-generated-document-not-rest.spec.js
publisher/013-api-product/01-create-product-and-update-underline-api.spec.js
publisher/013-api-product/02-create-a-new-revision-for-the-api-product-and-deploy.spec.js
publisher/013-api-product/04-lifecycle-support-for-api-products.spec.js
publisher/019-read-only-user/00-verify-that-read-only-user-cannot-create-update-api.spec.js
publisher/021-api-linter-feature/00-lint-when-creating-api-with-swagger-url.spec.js
publisher/021-api-linter-feature/02-lint-when-creating-api-with-swagger-v2-url.spec.js
publisher/021-api-linter-feature/06-lint-when-importing-api-with-swagger-url.spec.js
publisher/021-api-linter-feature/08-lint-when-importing-api-with-swagger-v2-url.spec.js

All the test cases are passing except for the ones identified as intermittent / BE errors.

Remaining sub tasks to resolve

[ ] Bump url.js version to fix punycode waring in npm run build:prod
[ ] Migrate form field validations from deprecated @hapi/joi to joi and fix breaking changes
[ ] Migrate ESLint from v7 to v9 when related plugins are eslint 9 supported
[ ] Bump swagger2-postman2-converter when released
[ ] Bump graphql-to-postman when released


Gatekeeper/App Signing

Hello!
I was just wondering if there is any sort of timeline/ETA on when LightTable will be signed for Gatekeeper on Mac OS X? We have a CS teacher in district that would like to use LightTable, but we need to have Gatekeeper enabled on staff laptops. Unfortunately Ctrl+Click > Open does not work for him either since it prompts for the local admin password each time (and we do not give that out to users).
Thanks!

I don't think somebody is working on this but @kenny-evitt and @cldwalker are the experts on that topic. They probably can give you a complete answer.

@mberardinelli Thanks for the reminder. I'll look into this.


Global issue to summarize all the changes made to improve electrical models

Hello all,
Here is the global issue that summarizes all the changes that will be gathered in PR #464:
- Rework of Input objects to:

better handle the control specificities for PMSM and SCIM: https://github.com/Eomys/pyleecan/issues/465
improve the generation of time/angle axes, rotor position over time and initial rotor position: https://github.com/Eomys/pyleecan/issues/418 / #295 / #433
setup several types of PWM strategies: https://github.com/Eomys/pyleecan/issues/410

- Rework of dq transform to:

include homopolar axis and add function to directly handle current object as DataTime: https://github.com/Eomys/pyleecan/issues/413
better handle current rotating direction and stator mmf rotating direction function of rotor direction: #468

- Rework of electrical models to:

improve calculation efficiency using interpolation on Look-Up Table to get operating point (e.g. calculate current given voltage and slip for SCIM): #466
calculate MTPA for PMSM: #467
calculate PWM currents: https://github.com/Eomys/pyleecan/issues/372

Don't hesitate to discuss here about these changes and/or in the respective issues, all the issues and the PR #464 will remain open for a while for this purpose.
Best regards,
Emile

Issue solved with PR #464


[Introduction] Short intro to Galaxy slides

I often find myself wanting a shorter and simpler introductory slide deck for the audiences I teach, so I've added such a slide deck to the "Short intro to Galaxy" tutorial (I hope that's ok @AnnaSyme!)
TODO:

[x] Add speaker notes suitable for video conversion

Great idea!

@hexylena could you check the speaker notes for suitability for video conversion?


Debugged photo carousel.

Debugged the carousel on the home page. It should now work with Angel's updated photo upload.


su password doesn't work on local deployment

Tried to use the password to log in as root, the password "password" worked on the webvm.io but does not work on my machine - Authentication failure. All other commands worked fine and console does not produce any error.

The most likely cause i that the root password is not actually set in your local setup. How is the local image built?

Followed the instructions under 'Local Deployment' section. Cloned the repo into my desktop, edited the variables and ext2 image as per the instructions and used nginx to start the server. Empty password also does not work. Any idea on which point or where do I need to set the root password?

The debian_mini image does not have the passwords configured. You can change the uid/gid on the JavaScript side to run the shell with root privileges. You can also follow build a new version of the debian_mini image by following the instructions here: https://github.com/leaningtech/webvm?tab=readme-ov-file#fork-deploy-customize
To make the image downloadable don't forget to select the "Upload GitHub release" workflow option.


AutoAdamRound bug due to quant_block_list

please refer https://github.com/intel/auto-round/pull/275


Is it ok to not specify default for styling options?

Hi, sorry if this is obvious.
I have some styling options that I want to use only as an override for the original color specified in the main CSS. When I am using defaults (which is the same one as the main CSS) I have to use this so that it doesn't output the CSS : 'exclude'  => [ '#000000' ]
Then, when I'm using the same code for another site, if the color change in the main CSS I have to also go and change all my defaults to fit.
I tried removing the default option from the color option and it seems to work fine for this since it only output if something is specified and it override the original styling.
Is it ok to do it? I just want to be sure because in the documentation it says we should always have some defaults but I wasn't sure if it is for every options or just options that would be use in the templates.
Thanks!

instead of omitting the default argument, use 'default' => ''
Empty arguments don't get a CSS output :wink:


Remove CSS filter in examples

Was used to set the opacity for IE <= 8

Nice. Please merge when green.

Thanks for the review


NREL Resstock and Comstock retrieval

Checklist

[X] I am using the current master branch
[X] I am running on an up-to-date pypsa-usa environment. Update via conda env update -f envs/environment.yaml

The Issue
For sector coupling studies, we use NREL comstock and resstock demand data. NREL recently did an update of this data and changed the format from *.csv to *.parquet. This causes the retrieval rules to break.
Steps To Reproduce
No response
Expected Behavior
No response
Error Message
No response
Anything else?
No response

I dont think this is an actual issue haha. It downloads fine as a csv!


Pan Gesture causing crashing

The following informations are requested in a bug report
Accidentally panning up on calendar causing crash.

Stack trace. see below

Integration method. pods

Full steps to reproduce.
Add calendar with constraints to bottom of 0, and equal width to container, with 0 for leading space to container.  Then add the pan gesture as shown in the demo code for Interface builder example.  Then swipe up on the calendar...it doesn't happen every time, but I've gotten it to swipe up and then crash pretty consistently.

Xcode 8.1
2.7.3
CALayer position contains NaN: [207 nan]
["0   CoreFoundation                      0x000000018bce11d0  + 148", "1   libobjc.A.dylib                     0x000000018a71855c objc_exception_throw + 56", "2   CoreFoundation                      0x000000018bce1100  + 0", "3   QuartzCore                          0x000000018f03919c  + 152", "4   QuartzCore                          0x000000018f039310  + 40", "5   QuartzCore                          0x000000018f0398a8  + 448", "6   UIKit                               0x0000000191b90174  + 784", "7   UIKit                               0x0000000191bb4440  + 116", "8   UIKit                               0x0000000191c45c14  + 472", "9   FSCalendar                          0x0000000100f4bf28 -[UIView(FSCalendarExtensions) setFs_top:] + 196", "10  FSCalendar                          0x0000000100f5de88 -[FSCalendarTransitionCoordinator performPathAnimationWithProgress:] + 928", "11  FSCalendar                          0x0000000100f5684c -[FSCalendarTransitionCoordinator scopeTransitionDidUpdate:] + 1172", "12  FSCalendar                          0x0000000100f5553c -[FSCalendarTransitionCoordinator handleScopeGesture:] + 164", "13  FSCalendar                          0x0000000100f2ea44 -[FSCalendar handleScopeGesture:] + 112", "14  UIKit                               0x000000019215ef80  + 64", "15  UIKit                               0x0000000192162688  + 124", "16  UIKit                               0x0000000191d2973c  + 260", "17  UIKit                               0x0000000191bc80f0  + 764", "18  UIKit                               0x0000000192152680  + 1100", "19  UIKit                               0x00000001921521e0  + 408", "20  UIKit                               0x000000019215149c  + 268", "21  UIKit                               0x0000000191bc630c  + 2960", "22  UIKit                               0x0000000191b96da0  + 340", "23  UIKit                               0x000000019238075c  + 2736", "24  UIKit                               0x000000019237a130  + 784", "25  CoreFoundation                      0x000000018bc8eb5c  + 24", "26  CoreFoundation                      0x000000018bc8e4a4  + 524", "27  CoreFoundation                      0x000000018bc8c0a4  + 804", "28  CoreFoundation                      0x000000018bbba2b8 CFRunLoopRunSpecific + 444", "29  GraphicsServices                    0x000000018d66e198 GSEventRunModal + 180", "30  UIKit                               0x0000000191c017fc  + 684", "31  UIKit                               0x0000000191bfc534 UIApplicationMain + 208", "32  grow                                0x000000010019f80c main + 140", "33  libdyld.dylib                       0x000000018ab9d5b8  + 4"]

Does this happen in the demo project? Which one? Or a link to another demo project.
Yes, demo for Interface builder

Same as #621
Fixed.