ReservationsController#show (ActiveRecord::RecordNotFound) "Couldn't find Reservation with 'id'=2"

ExceptionCouldn't find Reservation with 'id'=2Last OccurrenceJune 02, 2015 13:29:24 -0400Count1
Stack Trace
[bundle].../gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:320:in `raise_record_not_found_exception!'
[bundle].../gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:429:in `find_one'
[bundle].../gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:413:in `find_with_ids'
[bundle].../gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:68:in `find'
[bundle].../gems/activerecord-4.1.9/lib/active_record/querying.rb:3:in `find'
[bundle].../gems/cancancan-1.10.1/lib/cancan/model_adapters/abstract_adapter.rb:20:in `find'
[bundle].../gems/cancancan-1.10.1/lib/cancan/controller_resource.rb:116:in `find_resource'
[bundle].../gems/cancancan-1.10.1/lib/cancan/controller_resource.rb:68:in `load_resource_instance'
[bundle].../gems/cancancan-1.10.1/lib/cancan/controller_resource.rb:32:in `load_resource'
[bundle].../gems/cancancan-1.10.1/lib/cancan/controller_resource.rb:25:in `load_and_authorize_resource'
[bundle].../gems/cancancan-1.10.1/lib/cancan/controller_resource.rb:10:in `block in add_before_filter'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:440:in `instance_exec'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:440:in `block in make_lambda'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:160:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:160:in `block in halting'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in `block in halting'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in `run_callbacks'
[bundle].../gems/actionpack-4.1.9/lib/abstract_controller/callbacks.rb:19:in `process_action'
[bundle].../gems/actionpack-4.1.9/lib/action_controller/metal/rescue.rb:29:in `process_action'
[bundle].../gems/actionpack-4.1.9/lib/action_controller/metal/instrumentation.rb:31:in `block in process_action'
[bundle].../gems/activesupport-4.1.9/lib/active_support/notifications.rb:159:in `block in instrument'
[bundle].../gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
[bundle].../gems/activesupport-4.1.9/lib/active_support/notifications.rb:159:in `instrument'
[bundle].../gems/actionpack-4.1.9/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
[bundle].../gems/actionpack-4.1.9/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
[bundle].../gems/activerecord-4.1.9/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
[bundle].../gems/actionpack-4.1.9/lib/abstract_controller/base.rb:136:in `process'
[bundle].../gems/actionview-4.1.9/lib/action_view/rendering.rb:30:in `process'
[bundle].../gems/actionpack-4.1.9/lib/action_controller/metal.rb:196:in `dispatch'
[bundle].../gems/actionpack-4.1.9/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
[bundle].../gems/actionpack-4.1.9/lib/action_controller/metal.rb:232:in `block in action'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:82:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:50:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:73:in `block in call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in `each'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:685:in `call'
[bundle].../gems/rack-pjax-0.8.0/lib/rack/pjax.rb:12:in `call'
[bundle].../gems/devise_cas_authenticatable-1.3.7/lib/devise_cas_authenticatable/single_sign_out/rack.rb:14:in `call'
[bundle].../gems/party_foul-1.5.5/lib/party_foul/middleware.rb:8:in `call'
[bundle].../gems/warden-1.2.3/lib/warden/manager.rb:35:in `block in call'
[bundle].../gems/warden-1.2.3/lib/warden/manager.rb:34:in `catch'
[bundle].../gems/warden-1.2.3/lib/warden/manager.rb:34:in `call'
[bundle].../gems/rack-1.5.2/lib/rack/etag.rb:23:in `call'
[bundle].../gems/rack-1.5.2/lib/rack/conditionalget.rb:25:in `call'
[bundle].../gems/rack-1.5.2/lib/rack/head.rb:11:in `call'
[bundle].../gems/remotipart-1.2.1/lib/remotipart/middleware.rb:27:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/flash.rb:254:in `call'
[bundle].../gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context'
[bundle].../gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/cookies.rb:562:in `call'
[bundle].../gems/activerecord-4.1.9/lib/active_record/query_cache.rb:36:in `call'
[bundle].../gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/callbacks.rb:82:in `run_callbacks'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
[bundle].../gems/railties-4.1.9/lib/rails/rack/logger.rb:38:in `call_app'
[bundle].../gems/railties-4.1.9/lib/rails/rack/logger.rb:20:in `block in call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:68:in `block in tagged'
[bundle].../gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:26:in `tagged'
[bundle].../gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:68:in `tagged'
[bundle].../gems/railties-4.1.9/lib/rails/rack/logger.rb:20:in `call'
[bundle].../gems/request_store-1.1.0/lib/request_store/middleware.rb:8:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/request_id.rb:21:in `call'
[bundle].../gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
[bundle].../gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
[bundle].../gems/activesupport-4.1.9/lib/active_support/cache/strategy/local_cache_middleware.rb:26:in `call'
[bundle].../gems/actionpack-4.1.9/lib/action_dispatch/middleware/static.rb:84:in `call'
[bundle].../gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
[bundle].../gems/rack-timeout-0.2.0/lib/rack/timeout.rb:108:in `call'
[bundle].../gems/railties-4.1.9/lib/rails/engine.rb:514:in `call'
[bundle].../gems/railties-4.1.9/lib/rails/application.rb:144:in `call'
[bundle].../gems/railties-4.1.9/lib/rails/railtie.rb:194:in `public_send'
[bundle].../gems/railties-4.1.9/lib/rails/railtie.rb:194:in `method_missing'
/usr/local/rvm/gems/ruby-2.1.2/gems/passenger-5.0.8/lib/phusion_passenger/rack/thread_handler_extension.rb:89:in `process_request'
/usr/local/rvm/gems/ruby-2.1.2/gems/passenger-5.0.8/lib/phusion_passenger/request_handler/thread_handler.rb:149:in `accept_and_process_next_request'
/usr/local/rvm/gems/ruby-2.1.2/gems/passenger-5.0.8/lib/phusion_passenger/request_handler/thread_handler.rb:110:in `main_loop'
/usr/local/rvm/gems/ruby-2.1.2/gems/passenger-5.0.8/lib/phusion_passenger/request_handler.rb:414:in `block (3 levels) in start_threads'
/usr/local/rvm/gems/ruby-2.1.2/gems/passenger-5.0.8/lib/phusion_passenger/utils.rb:111:in `block in create_thread_and_abort_on_exception'
Fingerprint: 26191ed2a75dd4f1dad589868e34afe75c3b3fd9

It works, sweet!


Deployment guide inaccuracies

The UI of the Google Developer Console has been changed significantly enough that the screenshots are no longer accurate and I simply can't figure out how to do some steps.
Specifically, so far I was unable to figure out how to to the step called "Restrict authentication to your domain"
Also, Step 3 of "Create the App Engine service account" was inaccurate since the Consent Screen is now at APIs & Auth -> Credentials -> Credential Screen Tab. Step 5 was also confusing.
The Google Apps Admin console is also being changed and I got a message saying "This feature will be moving to the Google Developers Console by end of Aug 2015. Follow these instructions to get the new permissions you'll need." linking to here: https://cloud.google.com/docs/permissions-overview#h.bgs0oxofvnoo
At this point the UI is different, but still seems similar enough for me to muddle through, but it's not clear if it will let people continue to add apps in a similar way.
The OpenSSL binary link is also broken, it should probably point to https://www.openssl.org/community/binaries.html
It also seemed a bit odd that I was spending time configuring the OAuth2 config up front if it wasn't critical and the only instructions were some comments in config.py.
I'm still working through the whole process, but the rest seems like it's probably not affected by the new UI.

Thanks for the feedback.
Yes, the Google Developer Console UI slightly changed. I have updated the instructions on the Deployment Doc. There are still a few open items, and will have that updated shortly.
Feel free to post to this if you have more questions, or you can post to our support forum too: https://productforums.google.com/forum/#!topicsearchin/apps/category$3Agoogle-password-alert
Thanks

The documentation isn't even close anymore. The domain names you say to watch for are wrong, I cannot even find some of the settings (where are  "Compute > App Engine, select Settings.
Click Edit under Application settings. Under Google authentication, click the drop-down menu and select Google Apps domain. Enter your primary domain name using only lowercase letters. "). I cannot get this deployed at this time because I cannot translate the directions into anything actionable in the developer console.


MAUI project on Android using OpenXR

Summary
Hi,
I am trying to solve unexpected problems when using OpenXR in the MAUI application with Silk.NET NuGet packages on Android.
I prepared a minimalist demo to check the possibility of using Silk.NET for our business, but I couldn't find a working constellation for it.
Steps to reproduce

Create a default MAUI application in the Visual Studio 2022:

To avoid the possibility that we are missing a NuGet package, we will install all of them from Silk.NET:

Set the project to the Unsafe code:

Edit the code to get the OpenXR Extensions:

Run the application:

Click on the button Click me:

This is the first one I would like to ask how to solve this?

I found the solution in installing a NuGet package Evergine.OpenXR:

Run the app with Evergine.OpenXR:

It works.

Run another sample app with all known work-arounds:

It works without exception, but it doesn't load any OpenXR extensions.

Platform:
Mobile - Android, API 34, in emulator, Pixel5+6, (Magic Leap 2 )
AR - Magic Leap 2, Andorid (AOSP) 10.0 - API 29
Desktop - Windows 11
Framework Version: .NET 8, MAUI, Visual Studio 2022
API: OpenXR

Comments
Want some information?
As a solution, it would be enough for me if you create a minimalistic MAUI application in which OpenXR support would work.

Sorry, we’re not going to write your app for you. We also don’t support MAUI at this time, only .NET 8 Android. Also we do not control the Evergine package. Finally, if you want something like this to be developed, please consider taking out a paid sponsorship.


ipcache: Fix lock leak

Commit 40e13ea2a5a9 ("ipcache: Fix race in identity/ipcache release")
unintentionally took the lock on the IPCache and failed to release it if
the loop returned in the middle. This case is a bit unusual given that
allocation fails in this case. Fix it.
Found by inspection. This wasn't yet included in an official release.
Fixes: #20721
Fixes: 40e13ea2a5a9 ("ipcache: Fix race in identity/ipcache release")

This is hit in a case where we run out of allocated addresses, currently there is no coverage for this case. Smoke tests pass, this should be good to merge.


Allow to set up the executable name from the command line.

Description:
This allow to mimic the executable name picked by fyne build command. I think this is another issue with not using fyne directly for building. I will be investigating switching more platform to build with fyne directly as a permanent fix for this serie of problem.
Checklist:

[ ] Tests all pass.

This won't be necessary after merging #159 .


refactor: resolve lintdoc warnings

Summary
I was annoyed by all these warnings of lintdoc.
This PR resolves these warnings.
Any idea how to make them hard errors to avoid regression?
Test Plan
CI should pass.

https://stackoverflow.com/a/73981425


correctly write PublicHeader for client packets with VersionFlag set

For a client, the PublicHeader can contain both a version number as well as a packet number.

This was closed long ago in the wip-client branch, but since it'll probably still take some time until we merge that branch, I'm closing this issue here now manually.


Deploys even if npm errors?

I had a deploy go through, even though npm install failed. I think this might be the culprit:

executing post-deploy npm install ; pm2 startOrRestart ecosystem.json --env production

should it be  npm install && pm2 startOrRestart ecosystem.json --env production ?

You are right
Doc update:
https://github.com/pm2-hive/pm2-hive.github.io/commit/845a5704d419c8e2fa08dabc0b28f6be2befa888
PM2 samples update:
https://github.com/Unitech/pm2/commit/d44ae5a4f93a0191a63b2bdb3d6ff17491d4faf0


feat(notification/telegram): add telegram notification

This PR takes back the telegram notification (#18218) that was reverted by #19088 + adds a new UI feature flag notification-endpoint-telegram that turns on/off telegram notifications (in 04b188a), off by default

[x] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[x] Tests pass
[x] http/swagger.yml updated (if modified Go structs or API)
[x] Documentation updated or issue created (provide link to issue/pr)
[x] Signed CLA (if not already signed)

@sranka what is the status of this? have you looked into why the initial revert was made in order to avoid another? My assumption is that you will need to split this work into separate prs for the frontend and backend work, but i'm not certain

@glinton it was reverted because of deployment problems, a new feature flag that turns off telegram UI is the solution, the name of the flag was suggested by @desa on July, 27th :

"I’d name the feature-flag something like notification-endpoint-telegram
[9:19 PM] next steps would be to re-open the telegram pr with the feature-flag"


Inconsistent architectures for 1.7.2 and 1.7.3 on macOS

I am on macOS with an M-series processor. juliaup add 1.7.3  installs a x64 version, while juliaup add 1.7.2 installs an arm version. This seems inconsistent.
$ juliaup add 1.7.3
Installing Julia 1.7.3+0.x64.apple.darwin14
...

$ juliaup add 1.7.2
Installing Julia 1.7.2+0.aarch64.apple.darwin14
...

Output of versioninfo(), run from latest stable version of Julia:
julia> versioninfo()
Julia Version 1.9.3
Commit bed2cd540a1 (2023-08-24 14:43 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: macOS (arm64-apple-darwin22.4.0)
  CPU: 8 × Apple M2
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-14.0.6 (ORCJIT, apple-m1)
  Threads: 1 on 4 virtual cores

What's the output of file $(which juliaup)?

Ok, I'm out of my depth here. I wonder if the aarch64 version of 1.7.3 is missing for some reason?

It's missing from https://julialang.org/downloads/oldreleases/, at least

So that presumably also means it is not in versions.json? If so, that would explain it. We used to have all this special logic here in Juliaup to decide which versions exist, but since I moved things over to just mirror versions.json, all of that special casing is gone and we just reflect the state of versions.json.

Ok, I checked, and there just doesn't exist a 1.7.3 aarch64 build in versions.json on Mac. I think this is an issue for https://github.com/JuliaLang/VersionsJSONUtil.jl, i.e. if that build exists somewhere and were listed in that version database, it would also show up in Juliaup automatically.


KOGITO-5747 Public API: Shared Modules (Incubation)

https://issues.redhat.com/browse/KOGITO-5747
Blocks:

#1547
#1549
#1550
#1551

Description
These shared modules make available the common component and the application component.
General Expected Usage Example
Every component should provide one or more service implementations. Each service takes an identifier (a Path from a root) and usually a DataContext. The generic form of interaction should follow the pattern:
   LocalId id = appRoot.get(MyComponent.class).get("componentName").subs().get("someSubComponent")
   DataContext result = svc.evaluationMethod(id, dataContext);

for instance, evaluating a DMN may look like this:
   LocalDecisionId decisionId = appRoot.get(DecisionIds.class).get(namespaceString, nameString);
   DataContext result = svc.evaluate(decisionId, dataContext);

When a component admits subcomponents (e.g. tasks in processes, decision services in DMN, queries in rules, etc.), then there should be a way to construct that path with a fluent API:
   LocalDecisionId decisionServiceId = appRoot.get(DecisionIds.class).get(namespaceString, nameString).services().get(serviceString);
   DataContext result = svc.evaluate(decisionServiceId, dataContext);

If the types make sense, then a single evaluate method should be able to "parse" the provided ID, even for different paths; i.e. it is perfectly acceptable, even preferrable:
   DataContext result = svc.evaluate(serviceId, inputDataContext);
   DataContext serviceResult = svc.evaluate(decisionServiceId, inputDataContext);

However, component developers are free to provide their own methods; multiple methods should be returned, especially if they represent different actions; e.g.:
   LocalProcessInstanceId lpid = svc.createProcess(processId, inputDataContext);
   DataContext started = svc.start(lpid);
   DataContext aborted = svc.abort(lpid);

Application and Paths
The application component provides the root of the typed builder API for paths (appRoot);
i.e. paths such as /processes/my.process or /predictions/my.prediction are constructed via appRoot.get(ProcessIds.class).get("my.process") or appRoot.get(PredictionIds.class).get("my.prediction") respectively. The return type of this chain of methods is always an Id or a LocalId.
The <Component>Ids class should implement ComponentRoot.
paths admit subpaths if the Component admits subcomponents; e.g. a DMN admits services, so the path
 /decisions/$id/services/$serviceId

should be allowed. The method chain should reflect the structure of that path:
appRoot.get(DecisionIds.class).get(namespace, name).services().get(serviceId)

A RemoteId is also available to "install" the path on a hostname:port pair. This is not useful at the moment, it will be useful in a distributed setting.
In the future such a path will be also parsable starting from a String (e.g. LocalId.parse(String))
Because of their construction, paths can be always rendered as a string, and can always be parsed from a string into a typed representation (the /prefix and intermediated parts (such as /services specify the subtype). This makes them trivially serializable for sending over the wire and trivially unserializable into their typed representation.
Main API (common)
The common module provides basic interfaces so that each component may specialize one or more LocalId definitions and provide one or more service implementation.
Every component provides a pair of modules:

kogito-api-incubation-<component>: Paths and Identifiers
kogito-api-incubation-<component>-services: Service Interfaces

Paths and Identifiers
The first module contains specializations of LocalId (e.g. DecisionId) and/or subpaths. For instance:

a "decision service ID" should be addressable, and that service Id is a subcomponent of a decision. Then DecisionId should expose the method services() and appRoot.get(DecisionIds.class).get("my.decision").services().get("my.service.id") should be the path constructor; it would create a DecisionServiceId

DataContext

A DataContext is a computational context. It contains all the data that is required by a service to perform its computation.
A DataContext can be always converted into another type (or another DataContext) using the method DataContext#as(Class<T extends DataContext>).

A DataContext can be always converted into another sub-type of DataContext. Converting a DataContext into the same DataContext is a no-op just like (Object) new Object() is a no-op. You are always able to convert a DataContext into an arbitrary sub-type; e.g. a MapDataContext into a POJO that implements DataContext.
class Person implements DataContext, DefaultCastable { String name; }
MapDataContext ctx = MapDataContext.create();
ctx.set("name", "Paul");
Person p = ctx.as(Person.class);
String name = p.name; // "Paul"

MapDataContext provides methods get(), set() and wraps a map. This is the simplest and convenient way to pass data. However, it is suggested to create your own class. In this case your POJO should extends DataContext and DefaultCastable (the latter provides a default implementation of the as() method that is usually good for most cases)
Note: DefaultCastable#as uses Jackson internally, but it's an implementation detail and it may change in the future if we decide so.
Service Interfaces
Service interfaces should follow the generic pattern :
RETURN-TYPE VERB(IDENTIFIER [, optional DATACONTEXT])

e.g.
   LocalId id = appRoot.get(MyComponent.class).get("componentName").subs().get("someSubComponent")
   DataContext result = svc.evaluationMethod(id, dataContext);

Service interfaces do not extend a specific interface; component developers may define their own methods, although a certain degree of consistency is expected.
RETURN-TYPE should be always either an IDentifier or a DataContext. Implementations should usually take the most generic implementation DataContext as a parameter, and should usually return DataContext as a return type. It is allowed (as per Java spec) to return a subtype of DataContext, but this may not be required, as users can always convert into a more specific type.
When a method evaluates the resource pointed by the IDENTIFIER and completes (i.e. stateless evaluation), then RETURN-TYPE should always be DataContext.
When a method starts the evaluation of the resource pointed by the IDENTIFIER but it may not complete, then RETURN-TYPE may be an identifier.  (e.g. processService.create(id) would return a processInstanceId)

Asyncronous evaluation is allowed. In this case RETURN-TYPE should express the fact that evaluation is async. For instance:
   LocalId id = appRoot.get(MyComponent.class).get("componentName").subs().get("someSubComponent")
   CompletableFuture<DataContext> result = asyncSvc.evaluationMethod(id, dataContext);

i.e. a Process engine may provide AsyncProcessService
   CompletableFuture<LocalProcessInstanceId> futureLpid = asyncSvc.createProcess(processId, inputDataContext);
   CompletableFuture<DataContext> futureStarted = futureLpid.andThen(lpid -> asyncSvc.start(lpid));
   ...

Implementation
Currently only for Quarkus. The implementation is being shipped as part of the extension for convenience (it may be refactored to its own extension in the future). Implementation should provide:

injectable version of their component class -- used for wiring in appRoot.get(MyComponent.class)
injectable versions of their services

Currently services delegate their implementation to the internal hidden API that is used for codegen. The internal API should be considered deprecated and in the future codegen should be moved to the new API.
Refer to the related PRs for more details.
Caveats

What about listeners?

Currently listeners are plugged through annotation as we currently do already in Kogito. Since internally the APIs that we use in codegen are being used, those will work automatically.

What about metadata? The API only deals with data, but what about meta-data? e.g. directives that should be passed to the engine, that are not part of the Payload? (e.g. HTTP headers that should be passed to the engine to configure a specific request)
   var result = svc.evaluate(id, payload [ metadata ???] )

This is currently an open question.

A proposal is to allow the DataContext to also include metadata
Another proposal is to have some is that the as method does not just convert but it's a sort of "view"; so ctx.as(MetaDataContext.class) may show the metadata and not the plain data -- I like this but I am not sure how to implement it.

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

The (build) Examples check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

The (build) Optaplanner check has failed. Please check the logs.

The (build) Runtimes check has failed. Please check the logs.

The (build) Runtimes check has failed. Please check the logs.

The (build) Runtimes check has failed. Please check the logs.

The (build) Optaplanner check has failed. Please check the logs.

The (build) Runtimes check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

The (build) Runtimes check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

@tiagodolphine regarding ObjectMapper, I have the same opinion, but I let it go since we have it tracked here: https://issues.redhat.com/browse/KOGITO-5618

@ricardozanini :
@gitgabrio is suggesting the following refactoring:
- interface DataContext implements Castable {
+ interface DataContext {
+    <T extends DataContext> T as(Class<T> type);
}

so remove the implements clause and redeclare the as method explicitly. I am not strongly opinionated about this one. The as() method is there only to have the fluent:
myObject.as(SomeType.class)

as mentioned, in order to make it pluggable we may provide a different API, and static, instead of instance methods. Or even provide a way to use both strategies (e.g. static method + default method on interface -- the main question: shall we make it pluggable? and how? and when?)
e.g. specific services may want to provide their own DataContext implementation with an as method that exposes a specific subset of fields. By using Jackson's ObjectMapper we may be able to define Jackson Modules for each DataContext subtype, but we'll need a loading mechanism to plug them (DI for Quarkus/Spring -- what about "neither" ? ServiceLoaders ?)
in other words: every component should be able to define its own behavior, and that needs some further thinking

The (build) Runtimes check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

asking @ricardozanini @ricardozanini @gitgabrio for approval :)
Also adding @radtriste for approval

The (build) Examples check has failed. Please check the logs.

@evacchi
Please, remove that usage of Path. Beside being an anti-pattern to use something for a different scope is meant to fulfill, it also introduce a clear bug, making this not working on Windows and excluding all windows user from this "incubation" iteration.

I have started writing https://github.com/evacchi/kogito-runtimes/commit/01ba04f89aaa27e273aba38a90e981cdca7b86dc WDYT ? shall I bring this in? (name HierarchicalPath is temporary. Maybe "LocalUri" ?)

added a84426889d with the LocalUri API

The (build) Examples check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

The (build) Optaplanner check has failed. Please check the logs.

The (build) Runtimes check has failed. Please check the logs.


FIXED the infi loop for converting empty array

Hi everybody,
We found a Inifinity Loop in the convert method. We got the following as $data:
FACTFinder\Util\Parameters Object
(
    [parameters:protected] => Array
        (
            [] =>
        )

)

If you call the getInstance for the Parameters and convert the "$data->getArray()" to a Parameter, you get the example above; again and again.
Array
(
    [] =>
)

We found this by using webgrind, because there were over 69000 calls:

I don't know, where the empty parameter key is set, but this request just fix this phenomen.
Greetz

Hey Guys,
Have you already noticed my request?
Greetz

Yes, I noticed,, thank you.
Today I will test it

Hey @abognetti ,
Whats your result of your tests? Can you merge it?
Greetz

Thanks for this pull request.
Could you make these changes in the fork of the development branch and create a new pull request, please?
The stable branch 'master' can not be accepted as target branch of a pull request (details: https://github.com/FACT-Finder/FACT-Finder-PHP-Library/wiki/Guide-for-contributors).


ssmtp: use services.ssmtp not networking.defaultMailServer

Motivation for this change
This PR is part of the networking.* namespace cleanup.
ssmtp used to be configured via networking.defaultMailServer which is sort of misleading since it provides options only for ssmtp. Other dumb mail relays like nullmailer have always been living under services.
The intent of this PR is to align ssmtp's options with those of similar services. Specifically, two renames have been done:

Rename networking.defaultMailHost to services.ssmtp.
Rename directDelivery to enable because this is what it basically does.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

mailcatcher

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @basvandijk

@ckauhaus this has conflicts in rename.nix now. Can you rebase on latest master?

check

@GrahamcOfBorg test mailcatcher


[SPARK-42610][CONNECT][FOLLOWUP] Add some test cases for SQLImplicits.newSequenceEncoder

What changes were proposed in this pull request?

This PR aims to add some test cases for SQLImplicits.newSequenceEncoder that specify the encoder explicitly just like  those deprecated encoders.
Why are the changes needed?

Test the scenario that the new newSequenceEncoder is specified explicitly.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Pass GA.
Was this patch authored or co-authored using generative AI tooling?

No.

Merged to master.

Thank you all. @allisonwang-db @HyukjinKwon


drop the -test project

We are still deploying with the -test project, we should stop doing that. Once we are able to do new tenant deploys without that, I can go clear out the existing ones manually ( so that does not need any automation from the f8tenant side ).

I've a PR for this I'm testing and will submit soon


Apps rand style

This PR standardizes the apps behavior with respect to RNG state files.
Some commands got the -rand flag documented; some sources got code added if it was documented.
Every command that has -rand ow has -writerand.
Internal comments about RAND_load_file and RAND_write_file are now documented, and those limits are enforced in the code.  This made it possible to clean up those functions.
Will be squashed when merged.

Wondering if this couldn't be handled in a manner similar to the OPT_S_.../OPT_V_.../OPT_X_... options; to avoid duplicating code/text everywhere?

They are in alphabetical order which is nominally more useful than numeric (which implies the order of creation :).
The include/openssl/XXXXerr.h files are auto-generated.

So you changed an interface documented as being 1024 bytes to 256 bytes - that behaviour change seems entirely separate to what you are trying to achieve here? This change set is mixing in multiple items which makes it challenging to approve it - even though parts of it at least I would approve if it wasn't for the other items.  Hacking into randfile.c should IMHO be a separate PR.

You want 1024 bytes, I’ll change it back.
You want the randfile.c changes in a separate PR?  Okay.

Changing something without noting you are changing it and why in the middle of a large patch makes for surprises. Most of the apps changes look fine to me - although rather repetitious as already noted by @tmshort - frankly putting it consistently in all apps makes more sense to me - and would be less code.

I pulled the rand file read/write into a separate PR, #3864.
I removed the documentation of how many bytes are written with -writerand.
I did @tmshort's suggestion of using the OPT_x stuff.
I didn't add it to every file (the code would not get shorter), but I am about to add a commit that adds the flags to every command that calls RAND_bytes().

thanks all for the feedback, it made things better.

It looks like save_rand_file in apps/app_rand.c is being set validly but the configuration is freed before the call to app_RAND_write.  This means a rubbish file name results.
Run:

openssl req -config test.cnf -new -out /tmp/x.pem

in test and a file with garbled name gets created.  git status highlights it.  Valgrind produces:
==20743== Syscall param open(filename) points to unaddressable byte(s)
==20743==    at 0x55DABE0: __open_nocancel (syscall-template.S:81)
==20743==    by 0x529FAF5: RAND_write_file (randfile.c:149)
==20743==    by 0x41AF22: app_RAND_write (app_rand.c:65)
==20743==    by 0x43959E: main (openssl.c:243)
==20743==  Address 0x5e7f9a0 is 0 bytes inside a block of size 12 free'd
==20743==    at 0x4C2BDEC: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20743==    by 0x52709B0: CRYPTO_free (mem.c:274)
==20743==    by 0x51CC0CB: value_free_stack_doall (conf_api.c:178)
==20743==    by 0x526D2B6: doall_util_fn (lhash.c:175)
==20743==    by 0x526D301: OPENSSL_LH_doall (lhash.c:183)
==20743==    by 0x51CBBAD: lh_CONF_VALUE_doall (conf.h:32)
==20743==    by 0x51CC018: _CONF_free_data (conf_api.c:156)
==20743==    by 0x51CC3FA: def_destroy_data (conf_def.c:134)
==20743==    by 0x51CC3AA: def_destroy (conf_def.c:123)
==20743==    by 0x51CE05D: NCONF_free (conf_lib.c:199)
==20743==    by 0x4478F2: req_main (req.c:813)
==20743==    by 0x439C77: do_cmd (openssl.c:489)

It looks like req_main is freeing the NCONF data and main is later trying to write the random bits out using a stale pointer.
Test cases impacted by this are test_req, test_ca and test_ssl_old.  I only traced the path in the first.

New issue created #3946 for the use after free


Xargo can not find component rust-src

Following along with the intermezzOs, I installed xargo. After installing Xargo, I ran the following command:
$ xargo build --release --target ./x86_64-unknown-metalomai-gnu.json
error: `rust-src` component not found. Run `rustup component add rust-src`.
$

Following the instructions in the error message, I installed the rust-src component.
$ rustup component add rust-src
info: downloading component 'rust-src'
 26.4 MiB /  26.4 MiB (100 %) 377.6 KiB/s ETA:   0 s
info: installing component 'rust-src'
warning: could not delete temp directory: /home/geemili/.multirust/tmp/zgpxf8_tm0kk8a72_dir
$

Then I tried running xargo again.
$ xargo build --release --target ./x86_64-unknown-metalomai-gnu.json
error: `rust-src` component not found. Run `rustup component add rust-src`.
$ # :(

Xargo finds the current sysroot using [this code][find-sysroot]. In bash, that looks like:
$ rustc --print sysroot
/home/geemili/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu
$

Then it walks the directories to [find a file named "version", in a directory named rust.][find-version]. Translating to bash again:
$ find /home/geemili/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/ -name "version"
/home/geemili/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/test/run-make/version
$

The "version" file is not in the "rust" folder, so the program fails.

I don't know why where version is was changed, but depending on this seems like a hack. Perhaps a better way could be found to find the location of rust-src? Maybe someone from who works on rustup could comment.

version is still there in this nightly version:
rustc 1.14.0-nightly (3f4408347 2016-10-27)

Will check with a more recent nightly.
cc @brson What's a reliable way to find the rust-src component within the sysroot. I was under the impression that the packaging code was explicitly adding that version file and that I could rely on it but perhaps I was wrong. Should I search for the libstd/libcore directory inside the sysroot instead? (There's more than one hit for that search query tough) I recall reading somewhere that I should not assume that rust-src is always going to be in $sysroot/lib/rustlib/src/rust.

Will check with a more recent nightly.

FWIW,
rustc 1.14.0-nightly (5665bdf3e 2016-11-02)

also has the file.

Hmm. I'll try updating my version of rustc.

Updating my version of rustc fixed the issue. Still, I would like to know if there is a better way to get the path to rust-src.

@Geemili I think that you can't get the path to rust-src easily using rustup...
You can check if rust-src is installed using rustup component list | grep rust-src - and your current Rust version/compiler using rustc --print sysroot.
By default, rustup install source files/directories in $(rustc --print sysroot)/lib/rustlib/src/

@japaric: I think that you can close this thread.

Looks like this has re-emerged with rustup 1.0.0 (using xargo master and Rust nightly-x86_64-unknown-linux-gnu 8f02c429a), quite possibly for different reasons.
Note that rustup 1.0.0 migrates ~/.multirust to ~/.rustup and replaces it with a symlink.
Just about to look at a strace to see if something obvious sticks out...

Hmm:
/// The `rust-src` component within `rustc`'s sysroot
pub fn rust_src() -> Result<PathBuf> {
    for entry in WalkDir::new(try!(sysroot())) {
        let entry =
            try!(entry.chain_err(|| "error recursively walking the sysroot"));

        if entry.file_type().is_file() && entry.file_name() == "version" {
            let path = entry.path();

Looks like an assumption changed:
$ find $(rustc --print sysroot) -name version -type f | wc -l
0

Is the equivalent of $(rustc --print sysroot)/lib/rustlib/src/rust too naive for xargo?

This is silly and I've removed the nice error messages, but it works. In src/rustc.rs.
/// The `rust-src` component within `rustc`'s sysroot
pub fn rust_src() -> Result<PathBuf> {
    Ok(try!(sysroot()).join("lib/rustlib/src/rust"))
}

@brson recommends changing the logic to search for the 'Cargo.toml' file that belongs to the std crate. See this convo. If anyone wants to update logic, let me know. Otherwise, I'll look at it sometime during the weekend.

Taking a run at this now.

Is there a workaround? I was hoping to get some work done this weekend, but I get the 'rust-src component not found' with the latest nightly.

Just use the PR above. 😃

Doesn't work for me.
manifest path /home/jonathan/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/src/libstd/Cargo.toml does not exist.

Hmm, double src is interesting, I'll have to fix that. But it shouldn't even get there if you're using rustup. Do you have the rust-src component installed? rustup component add rust-src.

I do.

Oh, that's coming from src/dag.rs. It's expecting rust_src to just be <...>/rust. I wonder why this is even working on my system...

Guess who never cleared his xargo build cache? How embarrassment. One moment, I'll have this fixed in a jiffy. 😄

OK, sorry about that -- give it a whirl now. I suspect the fallback won't work yet, but your default rustup environment should be fine.

I think I've fixed it to :)

@thejpster Your fix seems to have fixed it for me aswell.

@japaric - will there be a release soon? My travis build uses Xargo on crates.io, not my funky patched version.

@thejpster Just released 0.2.3.


Overview of currently downloading streams

After the recent update the overview page where all active downloads are listed is gone. You have to click on a detected stream and then see that it is actually downloading. Maybe the download progress can be added to the detected streams?

I will add an additional page for all the active downloads

Released on v2.1.0 "Pending review on the stores (Chrome/Firefox)"


Updates examples to A-Frame v1.4.1

Also updates dependencies

This works fine for me, but I'd like someone else to check it, before we merge it.

Closed in favor of #6


Connection closed before all data read.

Answers checklist.

[X] I have read the documentation ESP-AT Programming Guide and the issue is not addressed there.
[X] I have used the latest released firmware or have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
2 issues found during development of the application. Device is in manual receive mode.
Issue 1: +IPD returns info, but connection gets closed and read is not possible.
Why don't we wait and let user to first read data before closed is reported? Or let him read after it is closed?
+IPD,0,31
AT+CIPRECVLEN?
+CIPRECVLEN:31,-1,-1,-1,-1

OK
AT+CIPRECVLEN?
+CIPRECVLEN:31,-1,-1,-1,-1

OK
AT+CIPRECVDATA=0,31

ERROR
0,CLOSED
AT+CIPRECVLEN?
+CIPRECVLEN:-1,-1,-1,-1,-1

OK

Issue 2: +IPD and actual read mismatch.
Why there is no missing 29 bytes?
+IPD,0,523
AT+CIPRECVLEN?
+CIPRECVLEN:523,-1,-1,-1,-1

OK
AT+CIPRECVDATA=0,523
+CIPRECVDATA:494,"<IP_ADDRESS>",443,....actual data....

OK
AT+CIPRECVLEN?
+CIPRECVLEN:0,-1,-1,-1,-1

OK

Hello @MaJerle,
If this is the TCP connection, it must be two bugs. If this is the SSL connection, it should be two reasonable cases.
Let me try to clarify this two issues if use SSL connection.
Issue 1: +IPD returns info, but connection gets closed and read is not possible.
could you please check the log port print.
if it prints NO DATA, it means no ssl data. it might receive a ssl alert packet from the server. and AT+CIPRECVLEN? returned 31 bytes, it indicates that tcp data length is 31 bytes, not the ssl data. this tcp data may be that alert packet.
Otherwise, there is no more memory for calloc and output the data.
Issue 2: +IPD and actual read mismatch.
Similar to https://github.com/espressif/esp-at/issues/589, https://github.com/espressif/esp-at/issues/655
In short, for SSL connections, ESP-AT will prioritize returning the data length of the ssl layer. if the ssl layer length is 0, it will return the data length which buffered at the tcp layer (Typically, this means that the ssl layer has not yet received a complete ssl fragment and is waiting to receive new TCP data).

It was for SSL connection, yes.
Thanks for clarification.

no worries


Unable to build on Capacitor 4

I have an ionic 6 project using Capacitor 4.  When compiling the project, I get the error seen below:
C:\project\MainActivity.java:10: error: package com.tchvu3.capvoicerecorder does not exist
import com.tchvu3.capvoicerecorder.VoiceRecorder;

My package.json has this:
"capacitor-voice-recorder": "^4.0.1",
This was working when I was using an older version of Capacitor.  I tried uninstalling and re-installing, but get the same error.  Any help or suggestions would be much appreciated.

After installing the plugin have you synced you android version?
Try running: "npx cap sync android"
and see if it fix your problem. Please let me know if it worked or not so I can close this issue in case of success

Thanks so much for the quick response!  So I actually tried running that command a few times and unfortunately I'm still having the same issue.  Please let me know if I can try anything else, or provide you with more information.  Thanks!

Our of curiosity, where are you importing the library in your Android code? Since capacitor 3 you don't need to manually add the plugin in your main activity

So I'm not manually importing the library anywhere... It's being imported as part of whatever the plugin does during the build from Ionic to Android code.  That said, after looking at the Android code, it appears to be getting imported in the MainActivity.  So I removed the line with the capvoicerecorder import and the build finished successfully.  Perhaps when I upgraded from an old version of Capacitor it didn't remove that import automatically?
My apologies for the trouble, and thank you for following up with the perfect solution; you saved me a ton of time :)


Connection failed when Redmine is behind VPN

I would like to report a bug when we try to report to Redmine, which is behind a VPN.
When we switch Wi-Fi networks (a situation that occurs when we work in the field or simply switch to another network within the building), the plugin breaks the connection with RDM and is unable to reconnect. It seems like it has the existing connection saved in the cache and does not allow creating a new one.
In the Options, there is a message "Connection failed" and the "Issues" tab does not open at all.
After entering the dev tools and selecting "Clear browser cache", then re-entering plugin Settings, editing the Redmine connection link, and saving the configuration, the connection is established correctly.

I'm a little confused because the extensions show "Connection failed", but your screenshot show that the request (/my/accounts.json) was successful (200 OK).
The label of the connection state indicates whether the request (/my/accounts.json) was successful or not.
In version 1.17.0 I added a reqest header to disable the cache for api requests, so that the request should no longer cached by the browser. I cache most of the data internally. When you save the settings, the internal cache will be deleted.
Hint: You do not need to edit the connection link, simply save settings
Is the problem still present?
Is it enough to clear the internal cache (save settings to clear)?
And if you refresh the page or reopen the popup, does that solve the issue?
And if the connection has failed, does the extension make further requests when you switch between settings and issues tab?
Please provide more information so that I can help you.

To make it easier for you to investigate, I'd recorded a video and I've uploaded it to Youtube.
Simulation begins with me being connected to the VPN (of which target redmine is behind). Plugin works fine.
Disconnect from VPN changes connection status to "failed" which is fine - what I couldn't record and what often happens (actually, during recording I have NOT encountered it for the very first time) is that the Issues tab doesn't show up - it's blank.
Then I've reconnected with the VPN (redmine started to be accessible for me) but refreshing, turning off / on the plugin didnt' change the connection status at all. Even though there was a 200, it looked like the connection was cached (look at the timestamp (ignore 2-hours difference between GMT and CET)).
Manual browser cache clearing through devtools resolves the issue.
Video available here:
https://www.youtube.com/watch?v=vEINTiGFelE

I have tested the extension against a redmine instane behind a VPN and I have also tested it under linux. Both worked well for me. It seems to be a very specific problem.
You could try the following 3 scenarios:

Could you try this test version redmine-time-tracking-v1.17.1-test.zip (download). This version tries to reconnect to the Redmien every 3 seconds and I have added the error reason below.

If you reconnect to your VPN and the connection status is "Connection failed", please clear your browser cache and reload the extension page with F5. Please do not make any changes in the settings only reload page or reopen popup. Does it work again afterwards?

Another attempt is to disable the browser cache. Does that work?

Clearing cache helps but it can be partially applied since i have no Network Error but not pretty error message.
Network Error happened only when I turned off NIC

To specify, I'm not sure if your plugin is ready for 403 error - maybe that's the case? Cause the response is there, even without VPN. But the access is blocked.

The problem is that your Redmine instance (or whatever is in front of your Redmine instance) is not actually returning a 403. The response code is 200, but with content that reads 403.
I have added a check that throws an error if the content-type is not application/json. Available in the new version v1.17.0.

I appreciate your efforts but it doesn't fully resolve the issue.
I can confirm it tries to reconnect when swapping tabs and it does work indeed and connects succesfully but only with Disable cache tick in DevTools checked. When unchecked, it fails at Invalid content-type 'text/html'. Expected 'application/json'.
DevTools Network tab says it's 200 OK (from disk cache).
As for now, I have instructed my team to clear cache when switching networks and we will see if it helps. I will come back to you later this week.

Due to the status code 200, the browser has cached this ‘fake error’ response. After reconnecting to your network, the browser returns the cache response with the error. If your service returns a real 403, this should no longer be a problem.
I replied earlier that the browser should no longer caches responses, but that was incorrect. I have now fixed this issue. This should solve the last part of the problem and cover similar problems in the future.
This fix will deployed with the next release.

Nevertheless, after your suggestion, we'd added a proper 403 error from the service and it seems like it works great now.
Thank you for your help!

I'm glad to hear that.
Thank you for reporting this bug and helping me to improve this extention


Fixed undefined method 'public_url' when uploading to s3

resolves #1433

This looks great! Thanks @oronbz ! :100:


@bind_hass decorator is deprecated and will be removed in 2024.9

System Health details
N/A
Checklist

[X] I have added battery_notes: to my configuration.yaml and restarted.
[X] I have read the FAQ's.
[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
https://developers.home-assistant.io/blog/2024/02/27/deprecate-bind-hass-and-hass-components/

As of Home Assistant 2024.3, we deprecate the use of the @bind_hass decorator and thus also the use of hass.components. Using hass.components will issue a warning in the logs. Authors of custom integrations are encouraged to update their code to prevent any issues before Home Assistant 2024.9.
Starting from Home Assistant 2024.9, the @bind_hass decorator and hass.components will be removed and will no longer work.

Reproduction steps
N/A
Debug logs
N/A

Diagnostics dump
N/A

Thanks, saw this myself today and already removed it in the next release I'm working on.


Unable to load plugin. Problem with mob data card.

Description (Required)

I loaded my server to get this error. In game, the dynatech icon is there, but in machines, nothing is there. the categories exist in the guide.
Steps to reproduce the Issue (Required)

no idea
Expected behavior (Required)

plugin to load
Server Log / Error Report

https://pastebin.com/xasLwwEe
Environment (Required)

Minecraft Version: 1.16.5
CS-CoreLib Version: n/a
Slimefun Version: dev 933
Plugin Version: 120

Update to latest :)


GET requests through ActiveResource fail authentication due to Content-Type mismatch

Environment
Rails 4.1.5 (client & server)
ActiveResource 4.0.0 (client)
api-auth 1.2.6 (client & server)

Issue
Server side interprets Content-Type as text/plain when the Content-Type header is missing (as it should be on a GET request). Since the auth signature was calculated with a blank Content-Type on the client and Content-Type of text/plain on the server, the signatures will not match.
Workaround
Force a Content-Type header from the client side with something like:
class ApiModel < ActiveResource::Base
	self.site = "http://api-server/api/v1"
	headers["Content-Type"] = "application/json"
	with_api_auth(access_id, secret_key)
end

In this case, client and server will both use application/json as the content type in computing the signature.
Though this is probably not ideal since Content-Type is not a valid GET header. A better solution might be to check for the presence of the Accept header and skip the Content-Type header in calculating the signature for GET requests.

Thank you @joshlarsen - Scratching my head for hours on this.


Consider using NSProgress instead of progress blocks (requires iOS7)

NSProgress API
I know it's iOS 7+ only, so that might be a dealbreaker, but the API is quite nice. The canceling api would be significantly better than using an NSOperation returned from a method.
An alternate idea for cancelation that doesn't require iOS7+ is to use a BOOL * in the progress block. When the user sets that to YES, the download stops. Exactly like how NSArray enumerateObjectsUsingBlock: works does it

I think this would be nice in 5.0 release. I'll take a look at it. @bpoplauschi @dreampiggy


Timeline for next release?

Tons of good stuff since v0.11.2!
https://github.com/rust-lang/hashbrown/compare/v0.11.2...master
Is there a timeline for the next release?

I just published v0.12.0.


Deploy envoy gateway without load balancer via node port

Hello! Please, help me. My kubernetes cluster don't have loadbalancer. How i can deploy envoy gateway using a node port to send trafic from a remote loadbalancer?

should be possible by configuring the EnvoyProxy resource
https://gateway.envoyproxy.io/v1.0.1/api/extension_types/#kubernetesservicespec

it try it. change default type for services to NodePort in manifest, but, after create gateway class and gateway, services is created with the LoadBalancer type.
Maybe i'm doing something wrong. But, i don't understand.
                          type:                             default: NodePort                             description: |-                               Type determines how the Service is exposed. Defaults to LoadBalancer.                               Valid options are ClusterIP, LoadBalancer and NodePort.                               "LoadBalancer" means a service will be exposed via an external load balancer (if the cloud provider supports it).                               "ClusterIP" means a service will only be accessible inside the cluster, via the cluster IP.                               "NodePort" means a service will be exposed on a static Port on all Nodes of the cluster.                             enum:                             - ClusterIP                             - LoadBalancer                             - NodePort                             type: string
service/envoy-default-test-gateway-40c68872   LoadBalancer   <IP_ADDRESS>     <pending>     80:32519/TCP                    4s

Hi! Can anyone please help me? I really don't understand what I'm doing wrong. And can envoy gateway create services with type nodePort

hey @SerheoReutty suggest going through all the steps outlined in https://gateway.envoyproxy.io/v1.0.1/tasks/operations/customize-envoyproxy/ to better understand how you can modify data plane Envoy Proxy fleet resources in Envoy Gateway

Thank you! i tried create custom option and ref gateway-class for this options. It's work!


fix(RingTheory/TensorProduct): fix instance diamonds

The optional fields to the algebra typeclasses are a trap; if you forget to provide them then you get diamonds.

This looks great: these examples are failing on master! LGTM.

!bench

I think [this] might be a reasonable comparison?

Thanks!
bors d+

bors merge
(The build is passing, and the only changes were a rfl lemma that's not simp, and a heartbeat change; so I don't expect the linter to fail)


implement listener wrapper for use with http app

This is cool, thank you @WeidiDeng !
Does it work? :smiley: What do you use it for / what does your config look like?
I'll take a closer look soon :)

This is cool, thank you @WeidiDeng !
Does it work? 😃 What do you use it for / what does your config look like?
I'll take a closer look soon :)

First adapt this caddyfile
example.com {
        encode gzip
        tls path.crt path.key
        reverse_proxy https://example.com {
        header_up Host {upstream_hostport}
    }
}

Then add this to appropriate path
 "listener_wrappers":
                    [
                        {
                            "wrapper": "layer4",
                            "routes":
                            [
                                {
                                    "match":
                                    [
                                        {
                                            "http":
                                            []
                                        }
                                    ]
                                },
                                {
                                    "match":
                                    [
                                        {
                                            "tls":
                                            {}
                                        }
                                    ],
                                    "handle":
                                    [
                                        {
                                            "handler": "tls"
                                        }
                                    ]
                                }
                            ]
                        }
                    ],
                    "automatic_https":
                    {
                        "disable": true
                    }

This allows caddy to handle https and plain http at once with the same port (no http2 though, only http1.1). listener piping is implicit if handlers are not terminal.
I only tested in dev server though, because a specialized piping is used in my caddy. I think there are some tweaks that can be made with caddy http version, like h2c is not compatible with h2 (one is over plaintext, another is over tls). Also if tls alpn settings only allow h2 or http1.1, golang http server will only server h2 or h1 (because http server checks tls.Conn
negotiated protocol explicitly).

Then add this to appropriate path

@WeidiDeng Which is the appropriate path?
Could you give a full config example that shows the context of where this belongs?

Problem: How to let caddy handle h2?
Grepping around the code and issues I finally realized that "listener_wrappers" is not just a comment like "srv0", but is actually a directive for "http" (NOT "layer4").
So I got things working with http/1.1, just like they were with the layer4 reverse proxy, but I was hoping that h2 would pass through to the caddy handle and get reverse proxied down to http/1.1 as needed automatically, as happens normally.
"minimal config"
In particular, if I remove the alpn policy, the reverse proxy to the python program on localhost:3000 fails with no log in either caddy or that program - the connection just closes:
{
                              "connection_policies": [
                                {
                                  "alpn": ["http/1.1"]  <==== have to put this down there
                                }
                              ]
}

{
  "apps": {
    "http": {
      "servers": {
        "srv0": {
          "listen": [":443"],
          "automatic_https": {
            "disable": true
          },
          "routes": [
            {
              "match": [
                {
                  "host": ["lxc100.duckdns.org"]
                }
              ],
              "handle": [
                {
                  "handler": "subroute",
                  "routes": [
                    {
                      "handle": [
                        {
                          "encodings": {
                            "gzip": {}
                          },
                          "handler": "encode",
                          "prefer": ["gzip"]
                        },
                        {
                          "handler": "reverse_proxy",
                          "headers": {
                            "request": {
                              "set": {
                                "Host": [
                                  "{http.reverse_proxy.upstream.hostport}"
                                ]
                              }
                            }
                          },
                          "transport": {
                            "protocol": "http"
                          },
                          "upstreams": [
                            {
                              "dial": "localhost:3000"
                            }
                          ]
                        }
                      ]
                    }
                  ]
                }
              ],
              "terminal": true
            }
          ],
          "listener_wrappers": [
            {
              "wrapper": "layer4",
              "routes": [
                {
                  "match": [
                    {
                      "tls": {}
                    }
                  ],
                  "handle": [
                    {
                      "handler": "subroute",
                      "routes": [
                        {
                          "match": [
                            {
                              "tls": {
                                "sni": ["lxc100.duckdns.org"]
                              }
                            }
                          ],
                          "handle": [
                            {
                              "handler": "tls",
                              "connection_policies": [
                                {
                                  "alpn": ["http/1.1"]
                                }
                              ]
                            },
                            {
                              "handler": "subroute",
                              "routes": [
                                {
                                  "match": [{ "ssh": {} }],
                                  "handle": [
                                    {
                                      "handler": "proxy",
                                      "upstreams": [
                                        { "dial": ["localhost:22"] }
                                      ]
                                    }
                                  ]
                                },
                                {
                                  "match": [
                                    {
                                      "http": [
                                        {
                                          "host": ["lxc100.duckdns.org"]
                                        }
                                      ]
                                    }
                                  ]
                                }
                              ]
                            }
                          ]
                        }
                      ]
                    }
                  ]
                }
              ]
            }
          ]
        }
      }
    },
    "tls": {
      "certificates": {
        "automate": [
          "localhost",
          "<IP_ADDRESS>",
          "lxc100.duckdns.org",
          "lxc101.duckdns.org"
        ]
      },
      "automation": {
        "policies": [
          {
            "subjects": ["localhost", "<IP_ADDRESS>"],
            "issuers": [
              {
                "module": "internal"
              }
            ]
          },
          {
            "subjects": ["lxc100.duckdns.org", "lxc101.duckdns.org"],
            "issuers": [
              {
                "challenges": {
                  "dns": {
                    "provider": {
                      "api_token": "{env.DUCKDNS_API_TOKEN}",
                      "name": "duckdns"
                    }
                  }
                },
                "module": "acme"
              },
              {
                "challenges": {
                  "dns": {
                    "provider": {
                      "api_token": "{env.DUCKDNS_API_TOKEN}",
                      "name": "duckdns"
                    }
                  }
                },
                "module": "zerossl"
              }
            ]
          }
        ]
      }
    }
  }
}

My Struggle Reading the Config
The thing I struggle with with so much of the caddy config is that it's very difficult to tell what's part of the API and what's a comment or a convention.
For example, "http" is a key, while "srv0" appears to be used merely as a comment. So while "servers" is semantically a set (unsorted array), it's using the syntax of a struct (key-value map):
{
  "http": {
    "servers": {
      "srv0": {}
    }
  }
}

So when I see something like "listener_wrappers" and I can't find it in a code search of the repository, I think it must be an arbitrary comment, not a struct member / identifier.
I don't know how to learn about these things other than trial and error. Is there a resource that shows more context? It seems most of the doc pages I've visited just show literal {} or similar very short snippets with no idea of where it goes or how to use it.

Documentation is done by @mholt. And I'll admit some part of it is very confusing, 😅.
Currently any listener wrapper that doesn't return a *tls.Conn will break h2, there is a pr pending.

Yes, sorry, it's confusing. Server names (keys in the "servers" object) are the only things that are "comments" as far as I can recall. They are primarily useful for logging, as opposed to a positional index. (Also, server order doesn't matter, so an object is more fitting.)
Technically listener_wrapper plugins are not restricted to just the HTTP app. They operate on the listener level, so any module that uses a listener can use listener wrappers. It just so happens that only the http module supports them so far. AFAIK there's no reason we can't add listener_wrapper support to this l4 module.


ShareErrorsFromSession not called when NotFoundHttpException is thrown

Laravel Version: 5.4.0
PHP Version: 5.6.28
Database Driver & Version:

Description:
The ShareErrorsFromSession middleware does not get called when a NotFoundHttpException is thrown.
Thats why I get:
ErrorException
Undefined variable: errors
Steps To Reproduce:
Produce a NotFoundHttpException
Use:
@if($errors->any())

<button type="button" class="close" data-dismiss="alert" aria-label="{{ trans('global.errors_close') }}">×</button>
             {{ trans('global.error_following_errors_occurred') }}

            @foreach($errors->all() as $error)

{{ $error }}

            @endforeach

@endif

in your custom 404.blade.php

Why would you display validation errors in a 404 response screen?


Adds tox and Python 3 compatiblity

I've hit a few Python 3 incompatibilities which I've fixed. I've also added a tox.ini, to run the tests more easily (using just $ tox).

Hi Vincent, thanks for the pull requests and sorry for the long delay :-(
Testing the Tox stuff gave me some trouble and I decided to not merge it in the end. Travis will test against several Python versions anyway and the invocation with make test don't seem too hard.
I cherry-picked 1243ead “Add Python 3 compatibility.“ into master though and will make sure to include it into the next release.


Explorer Long Query

Description
If the inventory tab has a lot of entries, the load time on retrieval is very long without any user feedback.
Context
I went to checkout a wallet's activity and they had a huge inventory, then my screen provide zero feedback that it was fetching something. I only knew because I understand the background process, but unfortunately not everyone has this context. We should provide some user feedback to optimize the process using pagination of results or limit based on some criteria
Acceptance Criteria

[ ] Load times are improved by optimizing the queries/process
[ ] Provide better user feedback of events happening when examining the wallet contents.

Reward
USD $500 in ONE token

this bounty is funded

Is this for explorer v2 or harmony dashboard?

@y04nqt can you provide a URL or an animated gif to get more information / context?  I'm having trouble finding wallet activity with a huge inventory also of the ones I found they provide a loading spinner.  So would love more context.

I went through the entire list, couldn't find much so I resorted to going to Davinchi itself. I was able to replicate a bug, maybe not this particular one in question but similar issue. https://explorer.harmony.one/address/0x1548c6227cbd78e51eb0a679c1f329b9a5a99beb
Click around on the tabs and see after a few clicks things start to lock up. I think it may be reasonable to assume, we have something that gets called and is has a big job to do, then clicking off of it causes disruption to the interface.

I submit my PR👌

is this still open ?


College Football

Can someone please provide the "optimizer = get_optimizer(Site.DRAFTKINGS, Sport. XXXXXX)" for College Football I have tried CFB, NCAAF, NCAA, COLLEGE_FOOTBALL etc and cant find it on my own so maybe someone can give it to me Thx beforehand

currently doesn't exist.
if you add this into draftkings\classic\settings.py
@SitesRegistry.register_settings
class DraftKingsFootballSettings(DraftKingsSettings):
sport = Sport.CFB
min_games = 2
positions = [
LineupPosition('QB', ('QB',)),
LineupPosition('RB', ('RB',)),
LineupPosition('RB', ('RB',)),
LineupPosition('WR', ('WR',)),
LineupPosition('WR', ('WR',)),
LineupPosition('WR', ('WR',)),
LineupPosition('FLEX', ('WR', 'RB',)),
LineupPosition('SFLEX', ('WR', 'RB', 'QB'))
]
and add the FOOTBALLC into pydfs_lineup_optimizer\constants.py
class Sport:
FOOTBALLC = 'CFB'
BASKETBALL = 'BASKETBALL'
FOOTBALL = 'FOOTBALL'
HOCKEY = 'HOCKEY'
that should work. although i have not tested this.


implement puzzlefs extract code too?

I'm not sure if this one is really that useful, but let's see.
It may be useful to have something that does actually extract a puzzlefs image onto a filesystem instead of just being able to mount it. Given that we can do fuse mounts as unprivileged users, people could always just mount the image, but maybe there's some case where it would be useful to extract things too (even if only for debugging).
We could implement this entirely in terms of operations on our fuse::Filesystem trait so we get it "for free" minus the traversal bits.

This is in progress as part of #23

extended attributes are extracted in this PR: https://github.com/anuvu/puzzlefs/pull/38

permissions and ownership are implemented in https://github.com/anuvu/puzzlefs/pull/39

@hallyn can this issue be closed or is there anything else you'd like implemented?

Thanks - let's close it, and open new issues if we find other shortcomings.


Made search boxes generic to integrate extended search

Results are inconsistent with the search terms because I didn't finish implementation of ES query.

[test trying to trigger the yarn test]

@LeshemNoa can you push the latest fixes and conflict resolution so that I could play with this and give me review?

On the visual side, on my screen (13") the search bars wraps which doesn't look as good as on your screen.

yalla merge!!!!!!


refactor: clean up CLI

Summary of Changes

Rename from_json to from_dict
Rename to_json to to_dict
Add methods to create API/UsageCountStore/AnnotationStore from JSON file and convert them to JSON file

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ PYTHON
black
19
2
0
2.55s

✅ PYTHON
mypy
19

0
4.93s

✅ PYTHON
ruff
19
3
0
0.1s

✅ REPOSITORY
git_diff
yes

no
0.04s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by


Unable to find cached IP address for host

Hi,
I am running a simple test to open cnn.com home page, using the corporate proxy as a ChainedProxy. The test runs fine but I see this warning in the logs:
WARN net.lightbody.bmp.filters.HarCaptureFilter - Unable to find cached IP address for host: www.cnn.com. IP address in HAR entry will be blank.
It appears that ResolvedHostnameCacheFilter.getPreviouslyResolvedAddressForHost always returns null when invoked from populateAddressFromCache inside HarCaptureFilter.
Is there something I'm missing in the ChainedProxy configuration?

This makes sense, though I hadn't thought of it till now: Since the chained proxy is actually resolving the address of the remote server, BMP doesn't know what IP address the request is sent to.
You can ignore this WARN message; the IP address should be blank when using a chained proxy. I'll suppress that message for chained proxies.

Yes... it hasn't really caused any issues... just "looks" like something is amiss!
Suppressing the warning works for me.
On the other hand, although I don't have any immediate need for this, would it be possible for the chained proxy to communicate this information to BMP... for the sake of completeness in terms of har capture?

This issue should now be fixed in master. There's no mechanism for an upstream proxy to communicate the IP address of a remote host, so the IP address must be blank.

I appreciate the support... thank you very much!

Hi,
I built the code from master and tested. Looks like this issue is resolved.
However, I see a similar message from net.lightbody.bmp.filters.HttpConnectHarCaptureFilter.
Does that need to be suppressed too?

Yes, you're right, I missed that. I've never been happy with the code duplication between those classes. In any case, this should be fixed in master now!
If this looks good, I'll probably release another minor version, since there have been several dependency updates, including a few security-related ones.

Looks like it's sorted out!
Thanks!
I see another message that wasn't there earlier... Is this related? Should I create a new issue for this?
14:54:15.304 [LittleProxy-0-ProxyToServerWorker-5] INFO org.littleshoot.proxy.impl.ProxyToServerConnection - (HANDSHAKING) [id: 0x88ddded7, L:<IP_ADDRESS>/<IP_ADDRESS>:54076 ! R:<proxy>/<proxy-ip>:<port>]: Connection to upstream server via chained proxy failed
java.nio.channels.ClosedChannelException: null
	at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source)

@madoni - That looks like a separate issue. Can you open a separate issue, and include more of the stack trace and the surrounding BMP logs? Thanks!


Alert when cluster operator is stuck in progress and or failing

Summary
When altering the cluster version, the cluster operator and other operators have a lot of work to do. That work can get blocked for various reasons. This tends not to put the clusters availability at risk. Therefore no alerts due to service unavailabilty are triggered. However ssuch situations should be investigated and resolved.
As a cluster administrator
I want to get notified when the cluster operator remains in state "Progressing" for an extended period
So that I can ensure the cluster can finish up the version change.
Context
This situation is inidated at:

the output of oc adm upgrade --as cluster-admin
info: An upgrade is in progress. Unable to apply 4.5.22: the cluster operator image-registry has not yet successfully rolled out

the OpenShift console at Administration > Cluster Settings > Update Status > View Details.

in monitoring using the Prometheus time series cluster_operator_conditions

Out of Scope

—

Further links

https://kb.vshn.ch/oc4/how-tos/update_maintenance.html

Acceptance criteria

Alert rule(s) that cover the subject
Guidlines/checklist explaining how to investigate thos allerts.

Implementation Ideas
The PQL expression cluster_operator_conditions{condition="Failing"} > 0 could directly be put into an alert rule with a for of 5 minutes. Other conditions might also be usefull. For example  Progressing. When progressing is going into the range of days, it would be worth a look.

This has been solved via a cross cluster monitoring.


Checkbox: Fix error text ids

Fixes #2015
Additional description
This combines aria-describedby id’s. Checkbox with error text were not referencing the error text. Multiple id’s are needed for Toggle variant.

CONTRIBUTOR checklist (do not remove)
Please complete for every pull request

[ ] First-time contributors should sign the Contributor License Agreement.  If you haven't before, wait a few minutes and a bot will comment on this pull request with instructions.
[ ] npm run lint:fix has been run and linting passes.
[ ] Mocha, Jest (Storyshots), and components/component-docs.json CI tests pass (npm test).
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

REVIEWER checklist (do not remove)

[ ] TravisCI tests pass. This includes linting, Mocha, Jest, Storyshots, and components/component-docs.json tests.
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

Required only if there are markup / UX changes

[ ] Add year-first date and commit SHA to last-slds-markup-review in package.json and push.
[ ] Request a review of the deployed Heroku app by the Salesforce UX Accessibility Team.
[ ] Add year-first review date, and commit SHA, last-accessibility-review, to package.json and push.
[ ] While the contributor's branch is checked out, run npm run local-update within locally cloned site repo to confirm the site will function correctly at the next release.

@jcjuett Here is the deployment of this Checkbox error id fix. I’ve tested it with VoiceOver and it works. The Toggle variant needed two ids in aria-describedby.
https://design-system-react-co-pr-2094.herokuapp.com/?selectedKind=SLDSCheckbox&selectedStory=Checkbox Toggle (with error)&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel
If this code is merged before you audit it, please see master branch: http://design-system-react-components.herokuapp.com/?selectedKind=SLDSCheckbox&selectedStory=Checkbox Toggle (with error)&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel


Magic Item Spell Import

Reported problem:

The problem is that spells are imported without the compendium information they came from (pack = ""). So magic items fails to retrieve them.

it would be enough to insert pack = "dnd5e.spells"
but also id & img are empty
and the name of the spell it does not coincide with that of the compendium...

Initial thought:
The spells come in with their item name in as some items have different spell cast DC's etc. It should be adding the pack, id and image stuff - although thinking about it, this might have changed when we switched to importing items spells into the world rather than compendium so players could import their own characters even if they didn't have compendium write access


Access to checkpoints

Hi Wenhao,
Thanks for your great work!
I was trying to download the ViT/L-14-f8 checkpoint, but I encountered the following message: "We're sorry, but<EMAIL_ADDRESS>can't be found in the unisyd-my.sharepoint.com directory. Please try again later, while we try to automatically fix this for you."
Do you have any idea on how to solve this?
Thanks!

Please try downloading again.

Hi @whwu95 ,
I've tried but still did not work. I also tried different accounts and different Internet environments.
Is there access for external users?

It's so strange, I can open this link: https://unisyd-my.sharepoint.com/:u:/r/personal/wenhao_wu_sydney_edu_au/Documents/AAAI23-Text4Vis/k400-vitl-14-f8.pt?csf=1&web=1&e=mdOEns

Maybe it's because you're the owner?
Can you try using different accounts if possible?
Thanks!

Please refer the links in my new README.md. I think it works.

Yayy!
Huge thanks! Now I'm closing the issue.


Filter for Date Select not rendering correctly

Description
The Date Filter widget is not rendering correctly.
Version
1.7.0
Steps to Reproduce
This occurs every time I use the Date filter.
Screenshots

Logs
No response
Platform
desktop
Device
Dell XPS 13
Operating System
Linux
Browser
Firefox
Additional Context
No response
Code of Conduct

[X] I agree to follow Jellyseerr's Code of Conduct

This is already fixed and a duplicate of #415

I'm still getting this issue with 1.8.1

I'm still getting this issue with 1.8.1 with both firefox and chrome.

What is your install method?

I'm still getting this issue with 1.8.1 with both firefox and chrome.

What is your install method?
I checked docker and baremetal and both seems to not have this issue at all

With nixos which does a 'baremetal' installation with yarn: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/servers/jellyseerr/default.nix#L57-L73

With nixos which does a 'baremetal' installation with yarn: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/servers/jellyseerr/default.nix#L57-L73

Ah yes. I thought so. I am also on nixos with nixpkg. And yes this is an issue on it. Unfortunately this seems to be related to how nixpkg builds it. The issue on jellyseerr side is fixed.

With nixos which does a 'baremetal' installation with yarn: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/servers/jellyseerr/default.nix#L57-L73

Ah yes. I thought so. I am also on nixos with nixpkg. And yes this is an issue on it. Unfortunately this seems to be related to how nix derivation builds it. The issue on jellyseerr side is fixed.

Thank you, I ran it using the docker file and confirmed that the issue is with the nixos distribution.


Refactor GridSearch + TFNoiseAwareModel to be fully seeded

Refactored GridSearch to simplify, then ironed out the seeding for both GridSearch and TFNoiseAwareModel, using RandomStates to keep contained within class.  Tested deterministic execution locally

@stephenbach or @jason-fries this is ready to merge in!  Everything should be deterministic end-to-end now.  I already pushed changes to scuba/master that sync it with this branch and am testing / re-running all results overnight to confirm that everything is deterministic in full scuba pipeline

@jason-fries good catch!  Just pushed the fix.
@stephenbach (and @jason-fries if you have an opinion here): In GenerativeModel we set the random seed at construction; in TFNoiseAwareModel currently, the seeds are set (for both the numpy.RandomState instance and the TF graph) when train is called, since currently that's when the graph is constructed.
I could try to change this so that one single graph is constructed at construction... but then this leads to issues if anyone calls train again.  Which is why I prefer it this way.  But any objections?  If we want to test for e.g. variance, we can just start an unseeded instance?

Also @jason-fries @stephenbach FYI somehow I am still not getting deterministic execution of a full scuba pipeline, but will get to bottom of & fix today

@jason-fries Note that I changed the interface so you specify save_dir in the init of GridSearch, and it automatically appends it to save_dir/grid_search.  Happy to change back, this was just to simplify for scuba


daisy and macosx installing failure

Hi!
i cant install daisyui on my mac.
20 verbose Darwin 20.6.0 21 verbose argv<EMAIL_ADDRESS>"/opt/homebrew/opt/node@14/bin/npm" "i" "daisyui" 22 verbose node v14.18.1 23 verbose npm  v6.14.15 24 error Unexpected token , in JSON at position 693246 while parsing near '...0" 24 error         } 24 error     } 24 error }, 24 error "dependencies": { 24 error ...' 25 verbose exit [ 1, true ]

I'm closing this because I could't reproduce the error.
If anyone has a similar problem, feel free to re-open this issue with more info.

same error me too. I too cant able to install daisyui

I don't know. Maybe there's a problem with your Node installation. The error message doesn't specify what's the problem so I would try reinstalling Node JS to see if that fixes the problem.

https://github.com/npm/npm/issues/14268#issuecomment-254044072


GARMIN Varia ertl615

Hello
Can you also integrate the eRTL615 radar?
I tried to select the Varia 515 with the editor but it doesn't work... neither the functions e.g. sunset/sunrise nor the data field with 1 field are displayed... can you help me
Thank you
Roland

Hi,
In order to add support for eRTL615, I need the supported light modes for the light. If you own eRTL615, please clean the "Lights configuration" app setting (leave empty) and report back what numbers do see on the screen and what mode each number represents.
For example:
1 -> High
5 -> Low
7 -> Day Flash
8 -> Nigh Flash

Hi
Thanks for the answer...but where can I see the numbers...when I make a data page with one field I get an empty field...when I make a data page with 2 fields I get the icon and the battery and a question mark...i have a garmin 1040

You need to put the data field to a 1 field layout data screen and clear the "Lights Configuration" app setting.

when I make a data page with one field I get an empty field

Do you see just an empty screen or there is a text in the middle of the screen (e.g. "Error X")?

That's exactly what I did...the configurations field is empty and I have a data page with one field....no errors...the field is absolutely empty

can you help me further?

That is very strange, I am not able to reproduce the empty screen with my lights. If you are willing to help further research what is wrong, you can use a special debugging tool used for cases like this.
Here are the steps:

Download the LightTester widget for Edge 1040: https://github.com/maca88/SmartBikeLights/blob/tester/Source/LightTester/build/edge1040/LightTester.prg
Follow the LightTester steps described here: https://github.com/maca88/SmartBikeLights/tree/tester/Source/LightTester#how-to-use
Post the content of the LightTester.TXT file

When you open the widget, make sure to go through all light modes by using the physical button on the light, so that they will be logged in the file.
I am interested to see what you will see for:

CM (Capable modes)
TY (Light type)
LM (Light mode)
BS (Battery state)

Hi
This is the content of the Lighttester.txt file...I have pushed through all modes:
Net ST=2 MD=0 T=74123
T_L: 1
L0: TY=2 ID=1 LM=0 CM=[0, 4, 5, 6, 7] BS=7
UPD: TY=2 ID=1 LM=7 BS=7 T=81475
UPD: TY=2 ID=1 LM=4 BS=7 T=86479
UPD: TY=2 ID=1 LM=5 BS=7 T=89479
UPD: TY=2 ID=1 LM=6 BS=7 T=93481
UPD: TY=2 ID=1 LM=7 BS=7 T=98483
UPD: TY=2 ID=1 LM=4 BS=7 T=103483
UPD: TY=2 ID=1 LM=0 BS=7 T=106485

Thanks for the taking the time and providing the results! Now it make sense why you see an empty screen. The issue is with "BS=7", battery state 7 is defined as "INVALID" according the ANT specification, that is why Smart Bike Lights is showing an empty screen.
I will release an update to support also battery state 7. In the meantime, can you provide me the light modes names? Based on the above result, the light has the following light modes (LM):
0 -> OFF
4 -> ???
5 -> ???
6 -> ???
7 -> ???
In order to add the light to the configuration, I would need the light mode names for each number (e.g. 6 -> Day Flash). With the LightTester widget open, you can see the current light mode in the "LM" label, which you can use to map the names to numbers

4=Solid-Modus
5=Peloton-Modus
6=Night Flash Modus
7=Day Flash Modus
Thank you very much for your support
br
roland

Thanks for the light modes! I've released version 0.26.6 which should work with eRTL615 and added it to the Lights Configurator

Thank you very much for your help ! everything works perfectly!
The Bike Lights app doesn't work yet...you probably haven't changed that yet!
Best regards
Roland

Now also the Bike Lights Control widget was updated (version 0.15.5) to work with eRTL615.
Thanks again for the help!


Illegal instruction in nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.29.0-nightly (866a71325 2018-07-29)

Cross-posting from rust-lang
https://github.com/rust-lang/rust/issues/52875#issuecomment-409360741
Cargo.toml:x11-dl = "2.18.1"
Illegal instruction with Rust nightly

2018-07-30T20:46:20.443731114+01:00 INFO rust_oids::app - Resuming simulation from snapshot: "/home/nico/.config/rust-oids/saved_state/20180730_193912.json"
error: XDG_RUNTIME_DIR not set in the environment.
Illegal instruction
nico@lenovo-devuan:~/Projects/itadinanta/rust-oids$ gdb target/release/rust-oids
GNU gdb (Debian 7.12-6+b2) <IP_ADDRESS>61007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from target/release/rust-oids...done.
(gdb) run
Starting program: /u01/home/nico/Projects/itadinanta/rust-oids/target/release/rust-oids
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2018-07-30T20:46:43.747665697+01:00 INFO rust_oids::app - Resuming simulation from snapshot: "/home/nico/.config/rust-oids/saved_state/20180730_193912.json"
error: XDG_RUNTIME_DIR not set in the environment.

Program received signal SIGILL, Illegal instruction.
0x0000555555758d1b in x11_dl::xlib_xcb::Xlib_xcb::open::hcf5d0b06fb3c742a ()
(gdb) stack
Undefined command: "stack".  Try "help".
(gdb) help
List of classes of commands:

aliases -- Aliases of other commands
breakpoints -- Making program stop at certain points
data -- Examining data
files -- Specifying and examining files
internals -- Maintenance commands
obscure -- Obscure features
running -- Running the program
stack -- Examining the stack
status -- Status inquiries
support -- Support facilities
tracepoints -- Tracing of program execution without stopping the program
user-defined -- User-defined commands

Type "help" followed by a class name for a list of commands in that class.
Type "help all" for the list of all commands.
Type "help" followed by command name for full documentation.
Type "apropos word" to search for commands related to "word".
Command name abbreviations are allowed if unambiguous.
(gdb) bt
#0  0x0000555555758d1b in x11_dl::xlib_xcb::Xlib_xcb::open::hcf5d0b06fb3c742a ()
#1  0x00005555556f9b20 in winit::platform::platform::x11::xdisplay::XConnection::new::hd8037cc51043bb68 ()
#2  0x00005555556f14bc in std::sync::once::Once::call_once::_$u7b$$u7b$closure$u7d$$u7d$::h3db9c6506b2778f4 ()
#3  0x00005555557f70e1 in std::sync::once::Once::call_inner::h19d8fb8519a6ca98 () at libstd/sync/once.rs:349
#4  0x0000555555702945 in winit::platform::platform::EventsLoop::new::h96a6247628a19d25 ()
#5  0x00005555556fe0b8 in winit::EventsLoop::new::h494bdedfa0de9eda ()
#6  0x000055555565b8c0 in rust_oids::app::main::main_loop::h05b6ab6851b78251 ()
#7  0x00005555555f3645 in rust_oids::app::run::h9bd1da782e5bcfa7 ()
#8  0x00005555556390f6 in rust_oids::main::h93ddf1c0aa5bdd7c ()
#9  0x0000555555625c23 in std::rt::lang_start::_$u7b$$u7b$closure$u7d$$u7d$::h8a490e39f0d9316a ()
#10 0x00005555557e4ff3 in std::rt::lang_start_internal::_$u7b$$u7b$closure$u7d$$u7d$::he46bbe21d122334d () at libstd/rt.rs:59
#11 std::panicking::try::do_call::h8ed5eafe3e94e158 () at libstd/panicking.rs:310
#12 0x000055555580492a in __rust_maybe_catch_panic () at libpanic_unwind/lib.rs:105
#13 0x00005555557e7a16 in std::panicking::try::hb8f13a044e539797 () at libstd/panicking.rs:289
#14 std::panic::catch_unwind::h09594af9f6e0fec4 () at libstd/panic.rs:392
#15 std::rt::lang_start_internal::ha4a5edbf3a495792 () at libstd/rt.rs:58
#16 0x0000555555639c04 in main ()

I believe this won't be fixed in the compiler (as apparently the compiler is doing The Right Thing™:
https://github.com/rust-lang/rust/issues/52898

Yeah I'm hitting this recently as well.  The referenced rust ticket says it's because some unsafe block has some undefined behaviour regarding a zero-value reference, which is illegal.

FYI, Bug still open in x11-dl 2.18.2

While I'm all for strong defined behaviour, I think this one was rushed.
Can you try, er, negotiate at least a "stopgap revert" until a graceful way out is found?

2.18.3 fixes it for me.

I can try using mem::uninitialized instead of mem::zeroed, as someone suggested that it doesn't have the same level of undefined behavior (which makes no sense to me, but whatever)

The undefined behavior is writing a zero to a function pointer, because a function pointer is not allowed to be zero. uninitialized does not write anything to it at all.

hey, we're in an unsafe block, so expect and allow unsafe things to occur.

That's not what an unsafe block means.  If LLVM is told a type is not going to be zero, and code explicitly writes a zero to it, it can assume that code is unreachable, and compile it into an abort to reduce code size.

Bug fixed in 2.18.3. Good work!


Insufficient Spacing Between Buttons on Community Page at Mobile Breakpoints

Insufficient Spacing Between Buttons at Mobile Breakpoints On Community Page
Current Behavior
On the community page of Probot https://probot.github.io/community/ there is insufficient spacing between the buttons when viewed at most mobile breakpoints, creating a very difficult user experience, especially for those with accessibility needs.
Possible Solution
Stack the buttons on top of each other with flex-direction: column and then make sure there is adequate and consistent spacing between all of the buttons with justify-content: space-between. Some adjustments may have to be made for container size, but overall, the spacing between each button should be consistent. Smaller break points would have to be adjusted as well. The buttons currently stack, but there is inadequate spacing between them.
See image for details

hey @one2code tried to fix the issue

as suggested used flex and gap.