NoMethodError on Cancel paid Order

When you have a completed order and you pay using the "Cheque" payment method, then mark it as "paid", then cancel it (second button on the top in Admin::Orders#edit) you get the following error messages:
NoMethodError (undefined method `success?' for nil:NilClass):
  /Users/anselm/.rvm/gems/ruby-2.2.1@brandeins/bundler/gems/spree_payone-09eca3459122/app/models/spree/payment_decorator.rb:39:in `handle_response'
  /Users/anselm/.rvm/gems/ruby-2.2.1@brandeins/bundler/gems/spree-acd2b81dc584/core/app/models/spree/payment/processing.rb:73:in `cancel!'
  /Users/anselm/.rvm/gems/ruby-2.2.1@brandeins/bundler/gems/spree-acd2b81dc584/core/app/models/spree/order.rb:646:in `block in after_cancel'
  activerecord (4.2.3) lib/active_record/relation/delegation.rb:46:in `each'
  activerecord (4.2.3) lib/active_record/relation/delegation.rb:46:in `each'
  /Users/anselm/.rvm/gems/ruby-2.2.1@brandeins/bundler/gems/spree-acd2b81dc584/core/app/models/spree/order.rb:646:in `after_cancel'
  state_machines (0.2.2) lib/state_machines/eval_helpers.rb:58:in `evaluate_method'
  state_machines (0.2.2) lib/state_machines/callback.rb:192:in `block in run_methods'
  state_machines (0.2.2) lib/state_machines/callback.rb:191:in `each'
  state_machines (0.2.2) lib/state_machines/callback.rb:191:in `run_methods'
  state_machines (0.2.2) lib/state_machines/callback.rb:159:in `call'
  state_machines (0.2.2) lib/state_machines/transition.rb:394:in `block (2 levels) in after'
  state_machines (0.2.2) lib/state_machines/transition.rb:394:in `each'
  state_machines (0.2.2) lib/state_machines/transition.rb:394:in `block in after'
  state_machines (0.2.2) lib/state_machines/transition.rb:392:in `catch'
  state_machines (0.2.2) lib/state_machines/transition.rb:392:in `after'
  state_machines (0.2.2) lib/state_machines/transition.rb:195:in `run_callbacks'
  state_machines (0.2.2) lib/state_machines/transition_collection.rb:127:in `run_callbacks'
  state_machines (0.2.2) lib/state_machines/transition_collection.rb:63:in `block (2 levels) in perform'
  state_machines (0.2.2) lib/state_machines/transition_collection.rb:63:in `catch'
  state_machines (0.2.2) lib/state_machines/transition_collection.rb:63:in `block in perform'
  state_machines (0.2.2) lib/state_machines/transition_collection.rb:182:in `block in within_transaction'
  state_machines (0.2.2) lib/state_machines/transition.rb:171:in `block in within_transaction'
  state_machines (0.2.2) lib/state_machines/machine.rb:1866:in `within_transaction'
  state_machines (0.2.2) lib/state_machines/transition.rb:170:in `within_transaction'
  state_machines (0.2.2) lib/state_machines/transition_collection.rb:181:in `within_transaction'
  state_machines (0.2.2) lib/state_machines/transition_collection.rb:62:in `perform'
  state_machines (0.2.2) lib/state_machines/transition.rb:163:in `perform'
  state_machines (0.2.2) lib/state_machines/event.rb:155:in `fire'
  state_machines (0.2.2) lib/state_machines/event.rb:219:in `block in add_actions'
  state_machines (0.2.2) lib/state_machines/machine.rb:725:in `call'
  state_machines (0.2.2) lib/state_machines/machine.rb:725:in `block (2 levels) in define_helper'
  state_machines (0.2.2) lib/state_machines/event.rb:224:in `block in add_actions'
  state_machines (0.2.2) lib/state_machines/machine.rb:725:in `call'
  state_machines (0.2.2) lib/state_machines/machine.rb:725:in `block (2 levels) in define_helper'
  /Users/anselm/.rvm/gems/ruby-2.2.1@brandeins/bundler/gems/spree-acd2b81dc584/core/app/models/spree/order.rb:543:in `block in canceled_by'
  activerecord (4.2.3) lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
  activerecord (4.2.3) lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
  activerecord (4.2.3) lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
  activerecord (4.2.3) lib/active_record/transactions.rb:220:in `transaction'
  activerecord (4.2.3) lib/active_record/transactions.rb:277:in `transaction'
  /Users/anselm/.rvm/gems/ruby-2.2.1@brandeins/bundler/gems/spree-acd2b81dc584/core/app/models/spree/order.rb:542:in `canceled_by'
  /Users/anselm/.rvm/gems/ruby-2.2.1@brandeins/bundler/gems/spree-acd2b81dc584/backend/app/controllers/spree/admin/orders_controller.rb:88:in `cancel'
  actionpack (4.2.3) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
  actionpack (4.2.3) lib/abstract_controller/base.rb:198:in `process_action'
  actionpack (4.2.3) lib/action_controller/metal/rendering.rb:10:in `process_action'
  actionpack (4.2.3) lib/abstract_controller/callbacks.rb:20:in `block in process_action'
  activesupport (4.2.3) lib/active_support/callbacks.rb:115:in `call'
  activesupport (4.2.3) lib/active_support/callbacks.rb:115:in `call'
  activesupport (4.2.3) lib/active_support/callbacks.rb:553:in `block (2 levels) in compile'
  activesupport (4.2.3) lib/active_support/callbacks.rb:503:in `call'
  activesupport (4.2.3) lib/active_support/callbacks.rb:503:in `call'
  activesupport (4.2.3) lib/active_support/callbacks.rb:88:in `run_callbacks'
  actionpack (4.2.3) lib/abstract_controller/callbacks.rb:19:in `process_action'
  actionpack (4.2.3) lib/action_controller/metal/rescue.rb:29:in `process_action'
  actionpack (4.2.3) lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
  activesupport (4.2.3) lib/active_support/notifications.rb:164:in `block in instrument'
  activesupport (4.2.3) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
  activesupport (4.2.3) lib/active_support/notifications.rb:164:in `instrument'
  actionpack (4.2.3) lib/action_controller/metal/instrumentation.rb:30:in `process_action'
  actionpack (4.2.3) lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
  activerecord (4.2.3) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
  actionpack (4.2.3) lib/abstract_controller/base.rb:137:in `process'
  actionview (4.2.3) lib/action_view/rendering.rb:30:in `process'
  actionpack (4.2.3) lib/action_controller/metal.rb:196:in `dispatch'
  actionpack (4.2.3) lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
  actionpack (4.2.3) lib/action_controller/metal.rb:237:in `block in action'
  actionpack (4.2.3) lib/action_dispatch/routing/route_set.rb:76:in `call'
  actionpack (4.2.3) lib/action_dispatch/routing/route_set.rb:76:in `dispatch'
  actionpack (4.2.3) lib/action_dispatch/routing/route_set.rb:45:in `serve'
  actionpack (4.2.3) lib/action_dispatch/journey/router.rb:43:in `block in serve'
  actionpack (4.2.3) lib/action_dispatch/journey/router.rb:30:in `each'
  actionpack (4.2.3) lib/action_dispatch/journey/router.rb:30:in `serve'
  actionpack (4.2.3) lib/action_dispatch/routing/route_set.rb:821:in `call'
  railties (4.2.3) lib/rails/engine.rb:518:in `call'
  railties (4.2.3) lib/rails/railtie.rb:194:in `public_send'
  railties (4.2.3) lib/rails/railtie.rb:194:in `method_missing'
  actionpack (4.2.3) lib/action_dispatch/routing/mapper.rb:51:in `serve'
  actionpack (4.2.3) lib/action_dispatch/journey/router.rb:43:in `block in serve'
  actionpack (4.2.3) lib/action_dispatch/journey/router.rb:30:in `each'
  actionpack (4.2.3) lib/action_dispatch/journey/router.rb:30:in `serve'
  actionpack (4.2.3) lib/action_dispatch/routing/route_set.rb:821:in `call'
  dragonfly (1.0.10) lib/dragonfly/middleware.rb:14:in `call'
  warden (1.2.3) lib/warden/manager.rb:35:in `block in call'
  warden (1.2.3) lib/warden/manager.rb:34:in `catch'
  warden (1.2.3) lib/warden/manager.rb:34:in `call'
  rack (1.6.4) lib/rack/etag.rb:24:in `call'
  rack (1.6.4) lib/rack/conditionalget.rb:38:in `call'
  rack (1.6.4) lib/rack/head.rb:13:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/params_parser.rb:27:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/flash.rb:260:in `call'
  rack (1.6.4) lib/rack/session/abstract/id.rb:225:in `context'
  rack (1.6.4) lib/rack/session/abstract/id.rb:220:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/cookies.rb:560:in `call'
  /Users/anselm/.rvm/gems/ruby-2.2.1@brandeins/bundler/gems/alchemy_cms-110e25f2b9e0/lib/alchemy/middleware/rescue_old_cookies.rb:10:in `call'
  activerecord (4.2.3) lib/active_record/query_cache.rb:36:in `call'
  activerecord (4.2.3) lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
  activerecord (4.2.3) lib/active_record/migration.rb:377:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
  activesupport (4.2.3) lib/active_support/callbacks.rb:84:in `run_callbacks'
  actionpack (4.2.3) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/reloader.rb:73:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
  airbrake (4.1.0) lib/airbrake/rails/middleware.rb:13:in `call'
  web-console (2.0.0) lib/action_dispatch/debug_exceptions.rb:18:in `middleware_call'
  web-console (2.0.0) lib/action_dispatch/debug_exceptions.rb:13:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  railties (4.2.3) lib/rails/rack/logger.rb:38:in `call_app'
  railties (4.2.3) lib/rails/rack/logger.rb:20:in `block in call'
  activesupport (4.2.3) lib/active_support/tagged_logging.rb:68:in `block in tagged'
  activesupport (4.2.3) lib/active_support/tagged_logging.rb:26:in `tagged'
  activesupport (4.2.3) lib/active_support/tagged_logging.rb:68:in `tagged'
  railties (4.2.3) lib/rails/rack/logger.rb:20:in `call'
  quiet_assets (1.1.0) lib/quiet_assets.rb:27:in `call_with_quiet_assets'
  request_store (1.1.0) lib/request_store/middleware.rb:8:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/request_id.rb:21:in `call'
  rack (1.6.4) lib/rack/methodoverride.rb:22:in `call'
  rack (1.6.4) lib/rack/runtime.rb:18:in `call'
  activesupport (4.2.3) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
  rack (1.6.4) lib/rack/lock.rb:17:in `call'
  dragonfly (1.0.10) lib/dragonfly/cookie_monster.rb:9:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/static.rb:116:in `call'
  rack (1.6.4) lib/rack/sendfile.rb:113:in `call'
  airbrake (4.1.0) lib/airbrake/user_informer.rb:16:in `_call'
  airbrake (4.1.0) lib/airbrake/user_informer.rb:12:in `call'
  railties (4.2.3) lib/rails/engine.rb:518:in `call'
  railties (4.2.3) lib/rails/application.rb:165:in `call'
  rack (1.6.4) lib/rack/content_length.rb:15:in `call'
  thin (1.5.1) lib/thin/connection.rb:81:in `block in pre_process'
  thin (1.5.1) lib/thin/connection.rb:79:in `catch'
  thin (1.5.1) lib/thin/connection.rb:79:in `pre_process'
  thin (1.5.1) lib/thin/connection.rb:54:in `process'
  thin (1.5.1) lib/thin/connection.rb:39:in `receive_data'
  eventmachine (1.0.5) lib/eventmachine.rb:187:in `run_machine'
  eventmachine (1.0.5) lib/eventmachine.rb:187:in `run'
  thin (1.5.1) lib/thin/backends/base.rb:63:in `start'
  thin (1.5.1) lib/thin/server.rb:159:in `start'
  rack (1.6.4) lib/rack/handler/thin.rb:19:in `run'
  rack (1.6.4) lib/rack/server.rb:286:in `start'
  railties (4.2.3) lib/rails/commands/server.rb:80:in `start'
  railties (4.2.3) lib/rails/commands/commands_tasks.rb:80:in `block in server'
  railties (4.2.3) lib/rails/commands/commands_tasks.rb:75:in `tap'
  railties (4.2.3) lib/rails/commands/commands_tasks.rb:75:in `server'
  railties (4.2.3) lib/rails/commands/commands_tasks.rb:39:in `run_command!'
  railties (4.2.3) lib/rails/commands.rb:17:in `<top (required)>'
  bin/rails:8:in `require'
  bin/rails:8:in `<top (required)>'
  spring (1.3.6) lib/spring/client/rails.rb:28:in `load'
  spring (1.3.6) lib/spring/client/rails.rb:28:in `call'
  spring (1.3.6) lib/spring/client/command.rb:7:in `call'
  spring (1.3.6) lib/spring/client.rb:26:in `run'
  spring (1.3.6) bin/spring:48:in `<top (required)>'
  spring (1.3.6) lib/spring/binstub.rb:11:in `load'
  spring (1.3.6) lib/spring/binstub.rb:11:in `<top (required)>'
  bin/spring:13:in `require'
  bin/spring:13:in `<top (required)>'
  bin/rails:3:in `load'
  bin/rails:3:in `<main>'

This is taking time. Apparently, you can't use PaymentMethods that are not from Spree::Payone with this gem (Cheque is from Spree::Core)


[Soroban Merge] Dapps Challenge

This will migrate the section from the /dapps directory on the soroban-docs site into the current site structure.
Refs: stellar/soroban-docs#740, stellar/soroban-docs#781

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr497.previews.kube001.services.stellar-ops.com

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr497.previews.kube001.services.stellar-ops.com

Would it make sense to link to the Freighter wallet How-To Guide from the Introduction? Since you need to connect your wallet to play the challenges?

Preview is available here:http://developers-pr497.previews.kube001.services.stellar-ops.com

@briwylde08 great idea!! I added the link in this commit.
Does that feel conspicuous enough, or should it be more "in your face" for people to see?

Preview is available here:http://developers-pr497.previews.kube001.services.stellar-ops.com

Yeah I think that works!!

Preview is available here:http://developers-pr497.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr497.previews.kube001.services.stellar-ops.com


Add arm64 support for the docker image

What problem does it solve?
I'd guess im not the only person trying to get this to run on a Raspberry Pi.
How would it work?
Add arm64 docker builds to the docker hub
Any technical considerations?
-

Added in v1.1.0
https://github.com/7eventy7/trackly/releases/tag/v1.1.0


🐛 BUG: Windows Defender reports nebula-cert.exe as Wacatac.B!ml trojan

What version of nebula are you using?
1.7.1
What operating system are you using?
Wintendo
Describe the Bug
Windows Defender detected, quarantined and reported nebula-cert.exe from the 1.7.1 release as Trojan:Win32/Wacatac.H!ml

Logs from affected hosts
n/a
Config files from affected hosts
n/a

Duplicate of https://github.com/slackhq/nebula/issues/902


full jspm support

We should detect when the builder is used in jspm projects and throw / warn to use the jspm builder instance rather for full configuration.

I already abandoned system builder towards jspm Builder. I don't get fancy result logs, but you can perfom bunde injects just fine


IA-663: Set different color for initial district

Added:
When a district is selected while creating a new campaign, its color will be red.
https://user-images.githubusercontent.com/47039931/126795361-e82c396b-2749-49a7-b9de-81f441472856.mov

Added:
When a district is selected while creating a new campaign, its color will be red.
Gravacao.de.Tela.2021-07-23.as.11.13.34.mov

Maybe use the color from the theme instead: theme.palette.primary.main. you can access it by making a useStyles hook

I agree on using a softer color, but we can just hard code it, no need to complicate with the useStyle

I agree on using a softer color, but we can just hard code it, no need to complicate with the useStyle

Currently:

Softer:


waterline auto_increment error

I'm developing a sails.js application that has to do CRUD operations with a Mysql database using waterline ORM .there is an atribute 'id' in my models , which has been set to auto-incremenent , with a beforeCreate function , but every time i try to call'create' function , this error occurs :

{ "error": { "name": "UsageError", "code": "E_INVALID_NEW_RECORD", "details": "Missing value for required attribute id. Expected a number, but instead, got: undefined" } } here is my model :

module.exports = {
primaryKey: 'id',
attributes: {
id: {
type: "number",
required: true,
unique: true,
autoIncrement: true
},
name: {
type: "string",
required: true
},
beforeCreate : function(item, next) {
Counter.native(function(err, collection) {
if (err) console.log(err);
collection.findAndModify(
{ id: "id" },
null,
{ $inc: { seq: 1 } },
{ new:true, upsert:true },
function(err, object){
if (err) console.log(err);
item.id = object.seq;
next();
}
);
});
}

};

and this is my model controller :
module.exports = {
create :function(req,res,next) {
let params = {name:req.param('name') };
model.create(params , function(err , createdData) {
if(err){
return res.badRequest({
error: err
});
}
else
{
return res.json({ added});
}
});
},

Thanks in advanced for your attention .

@joobintir I think your problem is that you have required: true.  You don't want to input data into an auto-increment field, and if it's required:true, it will cause error if there is no data being entered.

@streleck: So, if I use columnName to rename my primary key and then I have a different attribute in my db than in my model and now I have to make hundreds of changes in my code where I use the custom primary key attribute to change them to id - which, to makes things even more fun, will now look completely confusing when I debug and compare objects with database documents...
Whose bright idea was it to remove autoPk, I would really love to know...


WIP : TEST: add osx platform to run tests

/hold

Currently, Travis is not supporting launch docker with osx env.


Can't connect to the server

I use the example docker-compose.yml, and the server appears in the local network tab, if I click the refresh button the server's ping updates, so everything should be okay, but I can not connect to the server, it writes the server doesn't respond.
I tried to set 1 to the SV_LAN environment variable but it didn't help.
Help to find the problem/solution...

Did you find the solution to your problem? I have the same issue.
In the logs of the docker, I can see :
bhop_server  | 2024-09-06T13:06:29.393871819Z Warning: failed to init SDL thread priority manager: SDL not found
bhop_server  | 2024-09-06T13:06:32.471076636Z Could not establish connection to Steam servers.
bhop_server  | 2024-09-06T13:07:23.544072096Z /data/src/common/tcpconnection.cpp (1036) : Assertion Failed: Tried to initiate an outbound connection to <IP_ADDRESS>:27019, bound to local address <IP_ADDRESS>:26900.  An ephemeral local port should be used for outbound TCP conections!  How does this work?

No, I haven't.


submission-via-ctrl-enter-everywhere errors on Releases page

Please ensure:

[X] The bug is caused by Refined GitHub. It doesn't happen if I disable the extension.
[X] The bug happens after clearing extension cache. The "Clear cache" button below can also be found at the bottom of the options page.

Example URLs
https://github.com/refined-github/refined-github/releases
Extension version
Latest main build
Browser(s) used
Firefox
Description
addQuickSubmit@moz-extension://c2ad1c81-15a9-47dc-844b-f4235a6885c1/refined-github.js:14750:57
runFeature@moz-extension://c2ad1c81-15a9-47dc-844b-f4235a6885c1/refined-github.js:8479:22
setupPageLoad@moz-extension://c2ad1c81-15a9-47dc-844b-f4235a6885c1/refined-github.js:8491:11
./features/index.tsx/add/<@moz-extension://c2ad1c81-15a9-47dc-844b-f4235a6885c1/refined-github.js:8555:14
dispatchTurboEvent@moz-extension://c2ad1c81-15a9-47dc-844b-f4235a6885c1/refined-github.js:18215:12

Include in this issue:

[ ] Screenshots/video/gif demonstrating the bug, if it’s visual
[X] Console errors, if any

Related: we should enable the feature on release edit pages

Bug fixed by https://github.com/refined-github/refined-github/pull/5727/files#diff-761e43d505e7006dc33f66bf8b56efc312b1fe809dabe634471c5695ea88df64
Regarding my comment, I remember it not working when editing releases, but the feature always had isEditingRelease and it seems to work now. Will open a new issue if I still see it


Smaller style fixes

two proposed design changes in this PR:

Put video titles above language selection (based on information hierarchy)
Put the lost-looking keywords into a box (inspired a bit by SurrealDB):
landed on two versions for this:

blue box

card

I prefer the blue box, but would like to use the same blue as in the links, but can't figure the class for that out.

Nice! Definitely +1 from me on the (2) - card. I think that the blue is too strong. Card looks great!
Fine with the translation buttons, I'm sort of expecting to come back to this whole homepage header at some point with some redesign, we'll see. For now I was content with mimicking the old site so maintain some feeling of familiarity.
Any reason that the example reports on the homepage are so tiny now?

Also, why the switch to prism? I'm not sure about the purple install 😕
Also the overflow text is cut off and can't be scrolled, so the link is impossible to use. Given that these commands basically never change I'm still fairly inclined to do them manually so that we can have a hyperlink on that code comment...


docs: add ceph-nfs deprecation notice

Add a deprecation notice to the top of all NFS docs.
Signed-off-by: Blaine Gardner<EMAIL_ADDRESS>
Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
[ ] Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.
[ ] Pending release notes updated with breaking and/or notable changes, if necessary.
[ ] Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
[ ] Code generation (make codegen) has been run to update object specifications, if necessary.

Based on: https://github.com/rook/cassandra/pull/31/files


Shift

I was testing the inputs and it might be good to try normalise shift for snapping across all of the visual widgets, I noticed a few didn't have this functionality.
I like the shift-up/down behaviour for text input fields for incrementing and decrementing in larger steps of 10. Although I'm wondering if it might help to adjust the step amounts based on context? E.g. turn and deg units in CSS rotations might benefit from adjust amounts, such as 15deg steps for larger jumps using shift modifier.

Thank you for your detailed feedback..!
I agree with your idea to adjust the step amounts based on context and just updated.

So, I've been wondering which role should shift key be assigned.
Looking at some applications such as AfterEffects and Illustrator, functionalities of shift key can be classified as below:

Change with larger steps (ex. when dragging number field of AE)
Keep ratio (ex. resizing a bounding box)
Quantize values (ex. when rotating rotary knobs on Effect Control Panel of AE)

I would like to give each modifier keys consistent behaviors.
How do you think that shift key behaves like (3) in all case dragging the visual widgets?
I wonder if there's any smart way to realize step amounts for them without conflicting (3) role of shift key.
The ladder UI of Houdini might be a hint, though.
http://www.sidefx.com/docs/houdini/basics/ladder.html


WIP: Add a new overlay command to be able to apply OpenAPI overlays on given API document

Together with the guide written by Phil on OpenAPI overlays, we thought it would be a good idea to release a new bump overlay command in the CLI.
This WIP change is based on @lornajane's work on overlays.
I've published the resulting built package from this branch as a beta version on npmjs registry so you can test a beta version of Bump CLI installable with:
npm install bump-cli@beta

Example usage

Wrong overlay file

> bump overlay ../bump/doc/api/v1/openapi.v3.yml ../bump/doc/api/v1/openapi.v3.yml
 ›   Error: ../bump/doc/api/v1/openapi.v3.yml does not look like an OpenAPI overlay

Correct overlay file

bump overlay ../bump/doc/api/v1/openapi.v3.yml ../bump/doc/api/v1/overlay.yaml > ../bump/doc/api/v1/openapi.v3.overlayed.yml
bump deploy  ../bump/doc/api/v1/openapi.v3.overlayed.yml

Note: the input API document file name is used to detect the target output overlayed document (Json or Yaml)

Can we pop in a Thanks section on the README and put Lorna Mitchel on there?
We've done this for Spectral, Prism, and I recommend it for any tool which has substantial contribution from a single contributor, like this.
https://github.com/stoplightio/spectral#-thanks

@scharrier following your review, I've moved things around to make it clearer (I think). Basically all the “command” related feature is in the new commands/overlay.ts file while all the things around the definition (format, applying overlay...) is in the APIdefinition model.
I think it makes more sense like this. Let me know if it suits you!


Merge base url and prefix properly

Fixes #56
I've added a new 'base_url' configuration. Place the full base URL of your site where the package is hosted, and any URL prefix optionally in prefix.
If base_url is not filled in, will default to the current URL + the prefix

Works great, lgtm!


DOC: add example for scipy.io.loadmat

Add example in loadmat docstring.

I also think this is good but the file name and folder is a bit too specific I think for quick lookup. Could we use something more common like something in the current user directory and with a file name test.mat?

I was trying to write an example that would a) work when doctested and b) the user could run themselves to get the same result.  But you're right, that puts some extra complexity into the example.

Thanks for adding this example! It looks good to me. The scipy.io.loadmat docs will benefit from this PR. But I wonder if there should be a few more complex examples? There are already good docs for flags struct_as_record, squeeze_me, etc. but maybe they would benefit from examples too? Like the example I posted [here on loading mat file into Python] (http://poquitopicante.blogspot.com/2014/05/loading-matlab-mat-file-into-pandas.html). I can send a patch for scipy/io/Matlab/tests/data/teststruct_7.4_GLNX86.mat that follows your example if you think that's helpful? Thanks again!

More examples would be good - thanks - I will try my best to be prompt at review.

OK, I sent a PR to your PR, hope that works.

@mikofski kindly submitted a rewrite to this branch, which I have merged.  @ilayn - can you accept the inconvenience of loading the test files from the test directory?  Are you OK to merge this?

It reads good now in my opinion and Eric is also happy then in it goes. Thanks to all involved!


language/python: order args for virtualenv_install_with_resources

Add without, start_with, and end_with to allow basic control over the order that resources are installed so that the situations where we have to split up virtualenv_install_with_resources is reduced.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

In homebrew-core, we've often have to running separate venv commands whenever there is an ordering problem or there are some extra resources that we don't want in venv.
In this PR, I am looking into expanding DSL to handle some of these cases.
Examples usage can include:

jupyterlab:@@ -519,13 +519,11 @@ class Jupyterlab < Formula
   end

   def install
-    venv = virtualenv_create(libexec, python3)
     ENV["JUPYTER_PATH"] = etc/"jupyter"

     # install packages into virtualenv and link all jupyter extensions
     skipped = %w[hatch-jupyter-builder hatch-nodejs-version jupyterlab-pygments notebook]
-    venv.pip_install resources.reject { |r| skipped.include? r.name }
-    venv.pip_install_and_link buildpath
+    venv = virtualenv_install_with_resources without: skipped
     bin.install_symlink (libexec/"bin").glob("jupyter*")

awscli@@ -133,10 +133,7 @@ class Awscli < Formula
     end

     # The `awscrt` resource requires `setuptools` & `wheel`, so they must be installed first
-    venv = virtualenv_create(libexec, "python3.11", system_site_packages: false)
-    venv.pip_install resources.reject { |r| r.name == "awscrt" }
-    venv.pip_install resource("awscrt")
-    venv.pip_install_and_link buildpath
+    virtualenv_install_with_resources system_site_packages: false, end_with: "awscrt"

I added an exception in case that resource name doesn't exist, but can remove if we want to just ignore these.

EDIT: Probably need to view test diff without whitespace as I ended up indenting existing Language::Python::Virtualenv::Virtualenv (https://github.com/Homebrew/brew/pull/16817/files?diff=unified&w=1)

I'll merge suggestions and then adjust remaining parts after testing out logic.

Need another review as I refactored logic into separate method so want to make sure if this is good. I was trying out other loop logic from my review comment, but Sorbet doesn't seem capable of keeping track of types in that situation.


Override values in config files with environment variables

Information

Type
Version

Question
1.2.0

Description
Does ts-json-properties have the ability to override a value from a file with an environment variable or is it strictly one or the other?  For example, in my aws environment the urls for dependent services could change.  It's a lot easier for my deployment code to set an environment variable than change a config file.

Actually not. But I can implement this new feature :)


Microsoft SQL Server 2019 and other MS apps

a) is this saying Microsoft SQL Server 2019 is not supported?
b) is there a link to new features on Windows Server that are leveraged by these apps?

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

ID: 511301d9-f9cb-bad2-993f-d45c3b17b1b0
Version Independent ID: 3f1d3506-849e-5dde-de07-edfc99b333f8
Content: Windows Server 2019 and Microsoft Server application compatibility
Content Source: WindowsServerDocs/get-started-19/app-compat-19.md
Product: windows-server
Technology: server-general
GitHub Login: @coreyp
Microsoft Alias: coreyp-at-msft

Microsoft SQL Server 2019 is supported on Windows Server 2019, the table has been updated since this issue was raised. For information on whether these server applications support particular features in Windows Server, you'll need to see the product documentation for the particular server application for this information.
#please-close


how do you implement OAuth with receivedRedirectUri

Is there an example of creating a public token using the receivedRedirectUri from plaid?

@tlynch001 I do not have any examples of using the OAuth authentication method, but reading the docs, it looks like it's built on top of the existing Link architecture. Would recommend you switch to Going.Plaid (https://github.com/viceroypenguin/Going.Plaid) since it is being maintained to the latest version of the Plaid API.
For the RedirectUri property, see here as a property of the LinkCreateRequest, to be provided when getting a link token.
For example of how to use this library and the default Link process and token management, please visit this blazor quickstart example: https://github.com/jcoliz/PlaidQuickstartBlazor


Run make gen

Please provide a description of this PR:
Run make gen

@jacob-delgado: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
95b85283597f2e86907eeedf7b8ee4c36caa0d51
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test integ-basic-arm64


[usecase-webapi] Update CSP.feature for usecase webapi

Impacted tests(approved): new 0, update 1, delete 0
Unit test platform: [Android]
Unit test result summary: pass 1, fail 0, block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-4569

Please provide all sub-tests' result.

LGTM


Implementation details of hyper-parameters in CfgSearch and Cfg

I am following your work and running the code on VGD, with pertained features from dataset_setup.md But I failed to get the results mentioned in the paper: my test accuracy was often 2%~5% lower. Could you possibly provide more experimental details about the hyper-parameters such as CfgSearch and Cfg (e.g. ALPHA_START, ALPHA_EVERY, ALPHA_WEIGHT_DECAY, NET_OPTIM_WARMUP, NET_LR_DECAY_R), and other potentially helpful tricks?
Thanks for your preeminent work and help.

Which architecture do you use (the one we provided or searched by yourself)? arch and default hyper-parameters should produce accuracy reported.

Thanks for your replies.
I just re-ran the original code to ensure. Run MMNAS for VGD on RefCOCO+ testA by
python search_vgd.py

python train_vgd.py --RUN='train' --GPU='0, 1' --BS=600 --DATASET='refcoco+' --ARCH_PATH='./arch/train_vgd-search.json' --GENO_EPOCH=99

python train_vgd.py --RUN='test' --GPU='0, 1' --DATASET='refcoco+' --CKPT_PATH='./logs/ckpts/train_vgd-full_epoch13.pkl' --ARCH_PATH='./arch/train_vgd-search.json' --GENO_EPOCH=99 --VERSION="16Nov_refcoco+"

I got the validation accuracy of 69.325% and test accuracy of 75.585%. The paper reports the accuracy to be above 80%. Is there anything wrong with my usage?


Horizontal Compaction feels buggy

RGL with vertical compaction feels more rigid when compared to horizontal compaction. When the compaction is horizontal moving elements in the grid results in some weird positioning of elements which is not expected. Also moving the grid items feels buggy compared to vertical compaction. For my use-case I needed both horizontal and vertical compaction, tried to do it with compactType='horizontal' and verticalCompact=true, but seems that the horizontal compaction is causing issues. Basically if there is some space available for a grid to occupy that space is not being utilized rather it will be pushed to the end. Is anyone having a similar use-case as mine and facing this issue?
Codebox Example : https://codesandbox.io/s/currying-water-xvdtn?file=/src/ShowcaseLayout.js

I am facing the same problem

I am facing the same problem

I'm facing the same problem, can someone help me please


[model] StableLM 2 Zephyr 1.6b

I stumbled upon this two week old discussion here, about the StableLM 2 Zephyr 1.6b model becoming available for web-lmm soon.
https://huggingface.co/stabilityai/stablelm-2-zephyr-1_6b/discussions/9
I'd really love to work with that model, as my testing so far has shown it to work surprisingly well for its size.
Is there any way to use this model already?

I think I just found the files:
https://huggingface.co/OO8/1_6B_dev/tree/main

Got stuck on:
[FATAL] /workspace/mlc-llm/3rdparty/tvm/include/tvm/runtime/packed_func.h:1908: Function tvmjs.array.decode_storage(0: runtime.NDArray, 1: basic_string<char>, 2: basic_string<char>, 3: basic_string<char>) -> void expects 4 arguments, but 3 were provided.
put_char @ web-llm.bundle.mjs:3421

This is likely due to an old version of the web-llm npm (if you are not building from source). If you are building from source, this is likely due to the repo not up to date; try pull the recent changes

It would be fantastic if this model could become part of the default supported models.
The multi-language ability is fantastic. I'm very impressed with it, especially for its size.

Awesome, it seems the model has already become available in the Huggingface repo. The chunks exist:
https://huggingface.co/mlc-ai
However, the .wasm files are missing from binary-mlc-llm-libs. I've created an issue about that.
https://github.com/mlc-ai/binary-mlc-llm-libs/issues/111

Thanks for the request! We should be able to add the prebuilt wasm files in shortly. cc @YiyanZhai

For the record, I think there are more models for which the shards are available, but the wasm files are not (yet).

Music
WizardMath
Gorilla
Gemma 7B
CodeLlama
OpenHermes

Thanks for the list! WizardMath and OpenHermes can reuse the wasm of Mistral (as shown in prebuiltAppConfig in src/config.ts); CodeLlama should be able to reuse that of Llama-2, as long as they share the same quantization (e.g. q4f16_1) and number of params (e.g. 7B or 13B).

Update: StableLM 2 zerphyr 1.6b is now part of the prebuilt app config, since 0.2.39.
For music, this is not intended to be part of the webLLM's prebuilt; runtime is not well-supported for gorilla's function calling yet; Gemma 7B is redundant with https://github.com/mlc-ai/web-llm/issues/357.
Will close this issue for now. Feel free to open new ones!


UI of the website

Is your feature request related to a problem? Please describe.
The UI is a little off vibe I want to change the colour theme to black and purple in to make it attractive.
Describe the solution you'd like
The purple theme will enhance it's look and a bit more transition animation will also help it to look cool.

Something like this
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@Bhumika-00 work on it.. make sure the ui is user friendly

Okay sure ❤❤
On Mon, 14 Oct, 2024, 9:35 am MURUGA PERUMAL, @.***>
wrote:

Assigned #71 https://github.com/TherkuTech/tturl/issues/71 to
@Bhumika-00 https://github.com/Bhumika-00.
—
Reply to this email directly, view it on GitHub
https://github.com/TherkuTech/tturl/issues/71#event-14624185049, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BKOHTVXVUSX7STBTERKZJVDZ3M7IPAVCNFSM6AAAAABP3D4AGGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGYZDIMJYGUYDIOI
.
You are receiving this because you were assigned.Message ID:
@.***>


pytorch implementation

hi, Could you explain why you suggest using Cuda implementation, instead of PyTorch implementation ?https://github.com/fundamentalvision/Deformable-DETR/blob/11169a60c33333af00a4849f1808023eba96a931/models/ops/functions/ms_deform_attn_func.py#L41

It is because the cuda version is much faster and memory efficient than this pytorch version.

@jackroos hi，I am reviewing the implementation of the Cuda version. However, the backward process is hard for me to understand. May you provide any supplementary matirials to explain the process?

It is because the cuda version is much faster and more memory efficient than this pytorch version.

but the cuda version seems not surport to be exported right?i tried to exported,but failed,but got error message:
Could not export Python function call '_MSDeformAttnFunction'. Remove calls to Python functions before export. Did you forget to add @script or @script_method annotation? If this is a nn.ModuleList, add it to constants:
and i don't know how to do with it. @jackroos


Running Falcon7B and Mamba perf tests back-to-back triggers a hang

Summary
Running Falcon7B and Mamba perf tests back-to-back causes a hang on bare metal CI machines. This issue is related to #8606, which I have closed since disabling the persistent kernel cache seems to be a workaround for this problem.
Steps to reproduce
It does not seem possible to replicate this issue on lab machines, but I have been able to get this working on machines that match the CI configuration.

Get a bare-metal machine on the cloud VPN. I have tested this with WH 130.
Build main in release mode. I have tested this with abfc0172dc16c726f695803bc8379ca1c2eeef25.
Run model perf pipeline with the following command: ./tests/scripts/run_tests.sh --tt-arch $ARCH_NAME --pipeline-type llm_javelin_models_performance_bare_metal. This should hang on the Mamba test in a similar way to the pipeline linked above.

Further Investigation
Reproducing this issue requires the Falcon7B tests to run before the Mamba ones. Reordering the Mamba and Falcon7B tests with a fresh build does not seem to also trigger a hang.
It appears that the hang is related to the persistent program cache, since disabling the persistent cache in the Mamba tests can get it to pass - even if Falcon7B ran previously.
The hanging op is ShardedToInterleaved:
                     Op | DEBUG    | Started   C++ ttnn operation: ttnn::to_memory_config
                     Op | DEBUG    | Launching Operation: "ShardedToInterleaved" (device<Tensors>)
                     Op | DEBUG    | Attributes:
                     Op | DEBUG    |    grid_size = (x=8,y=7)
                     Op | DEBUG    |    sharded_op_type = ShardedOpType::ShardedToInterleaved
                     Op | DEBUG    |    output_mem_config = tt::tt_metal::MemoryConfig(memory_layout=TensorMemoryLayout::INTERLEAVED,buffer_type=BufferType::L1,shard_spec=std::nullopt)
                     Op | DEBUG    |    output_dtype = DataType::BFLOAT8_B
                     Op | DEBUG    | Input Tensors:
                     Op | DEBUG    |    0: tt::tt_metal::Tensor(storage=tt::tt_metal::DeviceStorage(memory_config=tt::tt_metal::MemoryConfig(memory_layout=TensorMemoryLayout::WIDTH_SHARDED,buffer_type=BufferType::L1,shard_spec=tt::tt_metal::ShardSpec(grid={[(x=0,y=0) - (x=7,y=4)]},shape={32, 128},orientation=ShardOrientation::ROW_MAJOR,halo=0))),shape=ttnn.Shape([1, 1, 32, 5120]),dtype=DataType::BFLOAT8_B,layout=Layout::TILE)
                     Op | DEBUG    |
                     Op | DEBUG    | Program Hash:<PHONE_NUMBER>3888547997 (HIT)
                     Op | DEBUG    | Kernel info: writer_unary_sharded_blocks_interleaved_start_id/7476807050483506974/

Based on the logs it seems that the cache for this particular op is populated during the Mamba execution, because there are no matching program hashes in the Falcon7B execution
Watcher
The state of the device at the hang obtained through Watcher is this:
Device 0 worker core(x= 0,y= 0) phys(x= 1,y= 1):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 1,y= 0) phys(x= 2,y= 1):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 2,y= 0) phys(x= 3,y= 1):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 3,y= 0) phys(x= 4,y= 1):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 4,y= 0) phys(x= 6,y= 1):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 5,y= 0) phys(x= 7,y= 1):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 6,y= 0) phys(x= 8,y= 1):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 7,y= 0) phys(x= 9,y= 1):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 0,y= 1) phys(x= 1,y= 2):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 1,y= 1) phys(x= 2,y= 2):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 2,y= 1) phys(x= 3,y= 2):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 3,y= 1) phys(x= 4,y= 2):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 4,y= 1) phys(x= 6,y= 2):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 5,y= 1) phys(x= 7,y= 2):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 6,y= 1) phys(x= 8,y= 2):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 7,y= 1) phys(x= 9,y= 2):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 0,y= 2) phys(x= 1,y= 3):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 1,y= 2) phys(x= 2,y= 3):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 2,y= 2) phys(x= 3,y= 3):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 3,y= 2) phys(x= 4,y= 3):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 4,y= 2) phys(x= 6,y= 3):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 5,y= 2) phys(x= 7,y= 3):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 6,y= 2) phys(x= 8,y= 3):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 7,y= 2) phys(x= 9,y= 3):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 0,y= 3) phys(x= 1,y= 5):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 1,y= 3) phys(x= 2,y= 5):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 2,y= 3) phys(x= 3,y= 5):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 3,y= 3) phys(x= 4,y= 5):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 4,y= 3) phys(x= 6,y= 5):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 5,y= 3) phys(x= 7,y= 5):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 6,y= 3) phys(x= 8,y= 5):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 7,y= 3) phys(x= 9,y= 5):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 0,y= 4) phys(x= 1,y= 7):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 1,y= 4) phys(x= 2,y= 7):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 2,y= 4) phys(x= 3,y= 7):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 3,y= 4) phys(x= 4,y= 7):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 4,y= 4) phys(x= 6,y= 7):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 5,y= 4) phys(x= 7,y= 7):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 6,y= 4) phys(x= 8,y= 7):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 7,y= 4) phys(x= 9,y= 7):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 0,y= 5) phys(x= 1,y= 8):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 1,y= 5) phys(x= 2,y= 8):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 2,y= 5) phys(x= 3,y= 8):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 3,y= 5) phys(x= 4,y= 8):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 4,y= 5) phys(x= 6,y= 8):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 5,y= 5) phys(x= 7,y= 8):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 6,y= 5) phys(x= 8,y= 8):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 7,y= 5) phys(x= 9,y= 8):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 0,y= 6) phys(x= 1,y= 9):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 1,y= 6) phys(x= 2,y= 9):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 2,y= 6) phys(x= 3,y= 9):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 3,y= 6) phys(x= 4,y= 9):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 4,y= 6) phys(x= 6,y= 9):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 5,y= 6) phys(x= 7,y= 9):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 6,y= 6) phys(x= 8,y= 9):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 7,y= 6) phys(x= 9,y= 9):    R,   W,   W,   W,   W  rmsg:D1G|BNt smsg:DDDD k_ids:4|3|0
Device 0 worker core(x= 0,y= 7) phys(x= 1,y=10):  NTW, PWW,   W,   W,   W  rmsg:H1G|bNt smsg:GDDD k_ids:0|2|0
Device 0 worker core(x= 1,y= 7) phys(x= 2,y=10):  NTW, PSW,   W,   W,   W  rmsg:H1G|bNt smsg:GDDD k_ids:0|1|0
Device 0 worker core(x= 2,y= 7) phys(x= 3,y=10):   GW,   W,   W,   W,   W  rmsg:H0D|bnt smsg:DDDD k_ids:0|0|0
Device 0 worker core(x= 3,y= 7) phys(x= 4,y=10):   GW,   W,   W,   W,   W  rmsg:H0D|bnt smsg:DDDD k_ids:0|0|0
Device 0 worker core(x= 4,y= 7) phys(x= 6,y=10):   GW,   W,   W,   W,   W  rmsg:H0D|bnt smsg:DDDD k_ids:0|0|0
Device 0 worker core(x= 5,y= 7) phys(x= 7,y=10):   GW,   W,   W,   W,   W  rmsg:H0D|bnt smsg:DDDD k_ids:0|0|0
Device 0 worker core(x= 6,y= 7) phys(x= 8,y=10):   GW,   W,   W,   W,   W  rmsg:H0D|bnt smsg:DDDD k_ids:0|0|0
Device 0 worker core(x= 7,y= 7) phys(x= 9,y=10):   GW,   W,   W,   W,   W  rmsg:H0D|bnt smsg:DDDD k_ids:0|0|0
Device 0 ethnet core(x= 0,y= 4) phys(x= 7,y= 0):   GW,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y= 5) phys(x= 3,y= 0):   GW,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y= 6) phys(x= 6,y= 0):   GW,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y= 7) phys(x= 4,y= 0):   GW,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y= 8) phys(x= 9,y= 6):  RED,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y= 9) phys(x= 1,y= 6):  RED,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y=10) phys(x= 8,y= 6):   GW,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y=11) phys(x= 2,y= 6):   GW,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y=12) phys(x= 7,y= 6):   GW,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y=13) phys(x= 3,y= 6):   GW,   X,   X,   X,   X  k_id:0
Device 0 ethnet core(x= 0,y=14) phys(x= 6,y= 6):   GW,   X,   X,   X,   X  k_id:0
k_id[0]: blank
k_id[1]: tt_metal/impl/dispatch/kernels/cq_prefetch.cpp
k_id[2]: tt_metal/impl/dispatch/kernels/cq_dispatch.cpp
k_id[3]: tt_eager/tt_dnn/kernels/dataflow/reader_unary_interleaved_start_id.cpp
k_id[4]: tt_eager/tt_dnn/kernels/dataflow/writer_unary_interleaved_start_id.cpp
Dump #43 completed at 432.168s

FYI @skhorasganiTT

@davorchap That's what it seems like to me.


Serialization and Deserialization of Attribute CustomExtension on Core2UserBase and Core2GroupBase not working

The ReferenceCode doesn't support SCIM Custom Schema extensions.
Over the method AddCustomAttribute() on Core2GroupBase or Core2UserBase you are able to add custom attributes.
However this attribut will not be serialized or deserialized trought the middleware.

@weyto we are looking into adding support for this.

@cadi3s : No progress from my side. Still a open issue.

@weyto @cadi3s This issue is on our radar, we'll be addressing it.

Any news on this????

Anyone solved this based on the reference code?
I guess this was a start using custom attributes for Groups, which is not finished? https://github.com/AzureAD/SCIMReferenceCode/blob/master/Microsoft.SystemForCrossDomainIdentityManagement/Schemas/ExtensionAttributeWindowsAzureActiveDirectoryGroup.cs

It probably should be at least highlighted the custom attributes aren't functional in this version - it's quite misleading at the moment.

any resolution to this issue?


Fixed grammatical error

'more faster' -> 'faster', the intensifier is redundant

Its a local malaysian slang. You still put a support word even grammatical error, to show a strong convincing there, haha

Oh, that's a learning for me. Haha!


Fixes bug where methodName would not be included in the response event

When the server was not being used in a rpc style, the method name would be undefined on the response event. This fixes that issue and adds a test to ensure that the method name is included when the response event is emitted.

Coverage increased (+0.002%) to 94.479% when pulling e9edf8986aa732effbbbe898cf139658452b524d on levinunnink:master into aee79a8ffa6ac8396d81d5876f4e5ee0a0e241c6 on vpulim:master.


Expand folders in file browser till the first item

If the folder contains the only folder inside it would be nice to expand the nested folder as well till the first file or level with a few folders.

Done


Electricity Purchases hourly buy rates option bug

When the user selects "Use hourly (subhourly) buy rates instead of TOU rates" on the Electricity Purchases page, the Single Owner financial model instead uses the buy rate from the table in the Energy Charges section. This happens at least for the Buy all / sell all configuration.
To Reproduce (In 2010 release and at least 11/2/21 version of LPPA branch)

Open default case of Detailed PV-Battery, PPA Single Owner
Go to Battery Dispatch page. Deselect "charge from system" in Period 1 and select "charge from grid" in Period 1.
Go to Electricity Purchases page
Select "Use Retail Rates" in drop-down
Run default case that we expect to use the 0.06 $/kWh buy rate from the table in the Energy Charges section.
Go to Cash Flow results. Get OPERATING EXPENSES: Electricity purchase ($) = 78,478
Go to Electricity Purchases page
Add 8760 buy rate prices at 0.2 $/kWh and select 'Use subhourly buy rates instead of TOU rates'
Run the modified case. Expect to see higher cost of Electricity purchase due to the higher buy rate in the 8760 data, but instead see the same value as in Step 6.

@cpaulgilman @brtietz @tyneises It looks like the tier_charge variable was not being assigned in the hourly buy rates section which was causing the code to fall back to the TOU rates. Adding the fix changes Electricity purchase to $261,594 for hourly buy rates of $0.2/kWh


CSS only works for /docs

.. but there is:

meta
help
tags
... the future

solution
cascade:
- type: docs


HARP-11531: Sphere horizon computation.

SphereHorizon computes the horizon for sphere projection, which is
a circle. It provides functions to get any point on it or subdivide
an arc into any number of divisions.
Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

@harpgl-bot retest this please

@harpgl-bot retest this please


Safely passing data to d3.html

(cherry picked from commit 136580af002a63572baf61f53e79268010eaa5ba)
@john-bodley @graceguo-supercat @timifasubaa

Codecov Report

Merging #43 into airbnb-master will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           airbnb-master      #43   +/-   ##
==============================================
  Coverage          71.14%   71.14%
==============================================
  Files                188      188
  Lines              14849    14849
  Branches            1085     1085
==============================================
  Hits               10564    10564
  Misses              4282     4282
  Partials               3        3

Continue to review full report at Codecov.

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


Main PDF upload

Upload the main file PDF.

Keep an eye on releases, they're posted there when ready


Integrate frontend code into this project

For the time being, I think I want to keep the actual integration to a minimum - right now, the two code bases only share a readme and the git hooks
As we move forward, we might want to add closer integration - I see a unified deploy process as something to work on soon - but I think we should tackle that separately.
Thoughts?

I'm fine with that

LGTM 👍


OAuth token exchange response body does not contain encounter context and encounter resource cannot be retrieved

This is found in preparation for #1323

@reshmakh  Can you confirm that you launched from an Encounter resource?
If launching from a Patient resource, only the patient claim is set.
If launching from an Encounter resource, both the patient and encounter claims are set.

Confirming this was user error.


test vs. multiple java versions

work in progress...

I put some code that may help to get the version testing in the lambda patch.  The key project is that the skip command for unit tests has to be run before the jvm is started, which is really problematic.

Does the test suite stuff in the lambda patch look useful for your patch?  I can add a 1.6 section as well.

I think the stages in harness should be treated like sets (eg. 1.8 will include all of the stuff of the old versions - or are there incompatible changes, that will prevent 1.8 from executing eg. 1.6 code?)

the travis build matrix now has 72 jobs, which is way too much. I think we should drop support for Python 2.6 (not supported officially by the Python foundation). I guess there are more options to shrink the size of the matrix, but I need to think about it.
Without py26 its still 64 jobs...

Try trimming the with without numpy to just one java version.  Those are separate dimensions.  Also java 1.6 is likely too far from current.

Like Python 2.6, Python 3.3 is also past EOL and no longer supported by the Python Software Foundation. How about dropping that as well?

will do that, thanks @hugovk!
We also need a modern ant version to support java 9, which is not installable from apt. Unfortunately apache deletes micro releases as soon as they get replaced by newer versions from their mirrors, so downloading directly from there requires too much baby sitting. We did this in the past on Appveyor (before using chocolatey) and every month or so CI was failing because the used ant version disappeared from the server.

Is there a wget command that can pull the list of available that we can parse to get the latest.  It would be a pain to set up but if it is the only way to get the ant required that doesn't require babysitting the we should consider it.

I do not think so. But these things only change rarely - so it is not that painful as you put it.

superseded by #304


Metadata exporter

Currently in the FHIR exporter we include patient seed, population seed, and Synthea version, but these are not available in any other data formats. Rather than add them individually to the other formats, this metadata exporter outputs info about the most recent run as a JSON file.
Notes:

I set the new config setting to default to true, because it's a lot better to have it and not need it, than to create a large CSV population and forget the seed you used when you want to recreate it. If people disagree I'm fine disabling it by default though
Each run gets a separate metadata file, just to minimize the chance of weirdness in case people have multiple instances running at the same time.
The filename is {timestamp} _ {population size} _ {state} _ { city? } _ {run ID} to make it more immediately apparent what goes to what, and ensure uniqueness

From the slack channel, 2 earlier suggestions I haven't yet added are gradle version (there doesn't seem to be a trivial way to do it programmatically, so I'll see what out there makes sense) and total run time.
Any suggestions on additional fields we may want to add here?

Note that in updating how the reference date is exported, I discovered a bug in the parsing of the reference date on the command line. It was using YYYYMMDD instead of yyyyMMdd which can produce surprising results: https://ideone.com/88QamU
So that is also fixed here


Typescript for Homepage

My first TypeScript page 🥳
I started with the row for recently followed artists.

 [Detector] Render start page cards with TypeScript


Exception is not logged in Application Insights, targeting net472

I'm currently having some issues where logged exceptions are not showing up in application insights. The application is a windows service using NServiceBus targeting net472 but using new project format, appsettings.json as configuration and Microsoft DI. Setup of AI and logging is done like this:
serviceCollection.Configure<TelemetryConfiguration>(config =>
{
    // using Microsoft.Applicationinsights.WindowsServer.TelemetryChannel 2.10.0
    var channel = new ServerTelemetryChannel();
    config.TelemetryChannel = channel;
    config.TelemetryInitializers.Add(new MyCustomInitializer());
    channel.Initialize(config);
});

serviceCollection.AddLogging(builder =>
{
    builder.AddConfiguration(configuration.GetSection("Logging"));
    builder.AddConsole(o => o.IncludeScopes = true);
    builder.AddApplicationInsights(configuration["ApplicationInsights:InstrumentationKey"]);
});

And NServiceBus is configured like this
// This gets logged to AI
logger.LogCritical(new Exception("Test exception"), "Testing exception logging");

// ... but these never show up in AIs (but are visible in Visual Studio output)
endpointConfiguration.Notifications.Errors.MessageHasBeenSentToDelayedRetries += (s, e) =>
  logger.LogCritical(e.Exception, "MessageHasBeenSentToDelayedRetries");
endpointConfiguration.Notifications.Errors.MessageHasFailedAnImmediateRetryAttempt += (s, e) =>
  logger.LogCritical(e.Exception, "MessageHasFailedAnImmediateRetryAttempt");
endpointConfiguration.Notifications.Errors.MessageSentToErrorQueue += (s, e) =>
  logger.LogCritical(e.Exception, "MessageSentToErrorQueue");

// If i remove the exception in the event handlers above and just log text it will also show up in AI, but not with the exception.

My hunch is that ApplicationInsights somehow treat these exceptions as handled and never sends them. I have read about setting EnableAllExceptions to true, but i'm not sure where i can configure this programatically as i don't have a ApplicationInsights.config -file.

ApplicationInsightsLoggerProvider is whats collector ilogger logs/exceptions. AI SDK doesn't have any notion on treating exceptions as unhandled.
I don't know what you mean by "visible in Visual Studio output" - can you elaborate with screenshots? Are they AI output? If you see if it in Visual Studio, but not in portal, then its ikey issue or sampling elimination.

Upgrading to NServiceBus 7.2.0 seems to solve this issue. No idea why though...

I don't think there is any question about application insights here anymore, closing. Please re-open if there are pending questions from application insgiths.


Add support for visionOS and fix warnings

Closes #47.

Hey there @svenopdehipt - this is a readonly repository. All of our SDKs are auto generated by the SDK Generator package. To contribute, please review the guidelines here and make your contribution within the SDK Generator package.


Unable to write to the Allurereport with [AllureStep]

Describe the bug
I'm using a library project that uses NOKSA.Allure 3.10 that has methods with [AllureStep] and importing this library in to Tests project and when I initiate the test ,nothing is logged in to report
I have Allureconfig.json in the working directory and set the properties set to copy to output folder
I see the error below in event viewer with dump file (attached)
do you have any leads to the error ?
dumpFile.txt
Application: Noksa.Allure.StepInjector.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
at Noksa.Allure.StepInjector.Injection.Injector..ctor(System.Collections.Generic.IEnumerable`1<System.String>)
at Noksa.Allure.StepInjector.Program.Main(System.String[])
Versions
-Net Framework :4.7.2

NUnit: ...3.12
Allure: ...
-Noksa.NUnit.Allure : 3.1.0
-Noksa.Allure.StepInjector :2.0.1

Any help is greatly appreciated.

Hello.
Can you please upload a project, where I can reproduce error?
Thanks

I could figure out the issue. The issue is with using the Latest version of
Newtonsoft.json package 12.0.3 and Mono.Cecil version 0.11.2  with Noksa.Nunit.Allure 3.1.0
I installed Noksa.Nunit.Allure 3.1.0 but later updated to the latest versions of newtonsoft.json and Mono.Cecil version that caused the issue . The warning message is also noted in build log with 532462766 exit code for Noksa.allure.StepInjector.
C# compiler throws this error

@Rupasri33
This is a bug. I will see what has changed in the new version of mono cecil.

Thank you!

Released in new beta


Include option for Feedback and create an OSM Note

Many web sites use OpenLayers, and the map users/viewers could identify errors in the base map (invalid names, changed features). However, there is not an option for the user to report this issue directly into the map producer.
When the base map is OpenStreetMap, it would be a good idea to have the option for "feedback" or "report an error" option, like a link next to contributors text.
Once clicked, a popup could appear to describe the error in the base map. Once clicked on send, the website calls the URL to the OSM API, by using: https://wiki.openstreetmap.org/wiki/API_v0.6#Map_Notes_API
OpenLayers could add some extra information in the comment, like "Created by OpenLayer" (similar to MAPS.ME, organicmaps or onosm.org), and other context stuff to help "note resolving people" better understand the context of the note (like the website name).

Thanks for the suggestion, @angoca. I think this is beyond the scope of the OpenLayers library. But it could make a nice 3rd party library.


Revert changes to Error Summary

Acceptance criteria

[x] Links are red with our regular focus state for links
[x] Border is red
[x] Focus does not focus border
[x] Remove focus text colour from heading when component is in focus

Done when

[ ] Revision is merged

Revert rational

Error summary style changes reverted in PR #519


[BUG]

Describe the bug

What are you trying to do?
use my custom listener.
What did you expect to happen?
add my listener via micro.AddListenOption

		micro.AddListenOption(func(o *server.Options) {
			o.ListenOptions = append(o.ListenOptions,
				func(lo *transport.ListenOptions) { lo.Context = ctx },
			)
		}),

What happens instead?
Nothing!

It will be never get the Listener from Context
bug uri:  https://github.com/go-micro/go-micro/blob/80203030175fee9d982738b10a0cee7e3ad4a6ad/transport/context.go#L15

ad

Still working on that, any chance to give more context?


Create instances directly from component and page prototypes

Removes the need for using jQuery for extending page and component prototypes

Coverage increased (+0.004%) to 91.477% when pulling 69ae4df1e3b49ff7a4277319b23f817944f93f37 on Kaivosukeltaja:create-component into 8eef02fea9c57af7a09ca16e5c276a470f42a103 on Houston-Inc:v1.0.5.


Move security api from plugins to clients

Description
I move the SecurityClient from the plugins directory to the clients directory, accordingly to the @saimedhi comment (https://github.com/opensearch-project/opensearch-py/pull/399#issuecomment-1642789791).

All the security features are considered as part of core features of OS.

How does this impact end-users? Anything I'd have to change in my code when upgrading?

You'll just have to change the import paths if you imported the client directly from plugins (from opensearchpy.plugins import security into from opensearchpy.clients import security).

That's a breaking change :( Is there a way to proxy the old to the new so we don't have to bump the major version?

You'll just have to change the import paths if you imported the client directly from plugins (from opensearchpy.plugins import security into from opensearchpy.clients import security).

That's a breaking change :( Is there a way to proxy the old to the new so we don't have to bump the major version?

@dblock This change is not yet released.

You'll just have to change the import paths if you imported the client directly from plugins (from opensearchpy.plugins import security into from opensearchpy.clients import security).

That's a breaking change :( Is there a way to proxy the old to the new so we don't have to bump the major version?

@dblock This change is not yet released.

Oh! Good.


feat: trap focus order within opened side navigation

MUMUP-3295: "As a person navigating MyUW via keyboard, I would like focus to remain in (cycle through) the open hamburger menu until I dismiss the menu, so that the menu is more usable and so that my navigation is less confusing."
In this PR:

When normal side navigation menu (i.e. not push-content version) is open, keyboard navigation is trapped within the menu
Tabbing past the bottom-most item results in focus resuming at the top-most item, and vice versa

Demo

PR considerations checklist:

[x] Updates CHANGELOG.md to reflect this PR's change.
[x] This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

@ChristianMurphy The reason we can't used the tabindex solution is because we have no control of the tabindex of content include by the ng-transclude on the frame page (e.g. content from apps using the framework). Using tabindex="-1" on the containing element isn't enough, because focus will continue to look all the way down the tree. We'd still have to use Javascript to add tabindex="-1" to every DOM element outside the menu (and remove it from every element when the menu closes), which doesn't seem like a better solution to me :/.

I don't follow
If a section is focused and has tabindex -1 it should hold focus regardless of the surrounding page.
Even if the page semantics somehow breaking the default behavior and extra work arounds are needed.
Its better to use the tabindex semantic rather than creating a copy in JavaScript that now has to be tested and maintained.

Do you have a reference or working example of what you're talking about? I might be misunderstanding you.
 In this case, if the side navigation menu is open, an element within it (which we can specify) receives focus. Setting tabindex="-1" on any of the elements containing the focused element (e.g. the outermost element of the menu), or on the focused element itself, has no effect. Keyboard navigation still proceeds through the DOM as usual.

Do you have another reference or working example of what you're talking about?

https://hackernoon.com/its-a-focus-trap-699a04d66fb5#52df
Re-reading my original comments I was unclear, it's not JavaScript events in general the concern me. It's attaching the event to elements on the edges, instead of attaching the event listener to the parent.
The manual-ness of adding the extra elements and correctly linking them leaves it at risk of being broken the next time the menu is edited.
Its the way around that is to detect anytime that the focus is outside the parent area an pull it back in.
https://github.com/vigetlabs/react-focus-trap/blob/master/src/focal-point.js#L104-L107

If I follow you, I should set tabindex="-1" on the "section" that I want to retain focus.

Right it should be out of the normal focus ordering.


[Deathwatch - Onlywar] Translation

Hi,
How we can add Character Sheet i18n for the Deathwatch and Onlywar caracter sheet? I shall like translate them in french.
Thanks

Wiki page for how to do it:
https://wiki.roll20.net/Character_Sheet_i18n
Example of sheet that uses i18n in the sheet:
https://github.com/Roll20/roll20-character-sheets/tree/master/CWOD-V20

Hello,
I'm working on resolving older issues in Github. Were you able to get the translations done? If you still need help with this issue please let me know.
Thanks,
Cassie

Hey there,
I'm going to go ahead and close this issue out.  Anduh included directions on how to get started with translate. If you have any other questions please let me know.


Fix issue with cmake on windows system outside msbuild environment

Fixing https://github.com/nlohmann/crow/issues/33

Pull Request Test Coverage Report for Build 320

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.617%

Totals

Change from base Build 314:
0.0%

Covered Lines:
44

Relevant Lines:
47

💛  - Coveralls


Need indication or handling of trailing whitespace in expressions

Is your feature request related to a problem? Please describe.
This is relate to the issue here. Specifically if you have an expression that ends in whitespace, the end result will be a concatenation of whatever the expression should be with that whitespace. This can be very hard to troubleshoot if you don't know what to look for.
# template1
- ${1} // LG return an number
- ${1}abc // LG is concatenating the number with the string abc
- ${1}(space character)    // LG is concatenating the number with as space, and turns into string

Describe the solution you'd like
Need some sort of warning, glyph, color, Intellisense or other indication that this is happening.

@boydc2014

#5111

@lei9444 can you investigate whether it is possible to turn on visible whitespace characters in order to highlight trailing whitespace chars that could interfere with LG and expressions?

https://github.com/microsoft/monaco-editor/issues/1932

@lei9444 can you investigate whether it is possible to turn on visible whitespace characters in order to highlight trailing whitespace chars that could interfere with LG and expressions?

Agree, @benbrown that's also what i was talking with Dana. We should give good indicator in Monaco editor for trailing space. I'm re-assigning this to @zhixzhan, who was primarily working on Manaco and LSP integration.
And, thanks @hatpick for the information.
@zhixzhan can you follow up see what's the options here.

@lei9444 can you investigate whether it is possible to turn on visible whitespace characters in order to highlight trailing whitespace chars that could interfere with LG and expressions?

Agree, @benbrown that's also what i was talking with Dana. We should give good indicator in Monaco editor for trailing space. I'm re-assigning this to @zhixzhan, who was primarily working on Manaco and LSP integration.
And, thanks @hatpick for the information.
@zhixzhan can you follow up see what's the options here.

Sure, I will fellow this.


Add the possibility to add tags, tlp, and message in TheHive observables

Description

I added the possibility to add tags, modify tlp level and add messages on TheHive observables.
There is no breaking change.
Checklist

[x] I have reviewed the contributing guidelines.
[x] I have included unit tests for my changes or additions.
[ ] I have successfully run make test-docker with my changes.
[x] I have manually tested all relevant modes of the change in this PR.
[x] I have updated the documentation.
[x] I have updated the changelog.

Questions or Comments

I do not have a docker environment so I ran the test to develop the feature on my test environment

That's weird...


hover event for vue-star-rating

Hey,
I am using vue-star-rating in one of my projects and came across a scenario where I want to do something on the hover action. Currently, there is no event for that specifically.  Can we have a hover event along with the other two?

Hey Jasmin,
Sorry it's taken so long to get back to you. What do you mean by a hover event? The component emits an event on mouse move (current-rating) and on click (rating-selected). Do you mean hover over the entire component? if that's the case you can just wrap it in a div:
<div @mouseover="myFunc">
  <star-rating />
</div>

Hey @craigh411 ,
My concerns were related to the entire component hover. I implemented the same way as you explained above and added some setTimeout() to it so that it didn't capture every mouseover.
Thank you so much for your reply.


Test fixing signing

#1403  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @krzema12 and the rest of your teammates on  Graphite


Site request: hitomi.la

Can you make an API for https://hitomi.la It's another popular doujin site

both hitomi.la and e-hentai.org has a kind of cache to protect images in their galleries, so this is a bit tricky to implement in a data like web-api, I will try to deal with later but don't expect so big..


Update manual task with Run with Arguments

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

https://github.com/wso2-enterprise/choreo/issues/26634

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

PR pointed to DEV https://github.com/wso2/docs-choreo-dev/pull/1357


[stable/traefik] Fix version info

This fixes the version info in Chart.yaml, values.yaml and README.md.
Bump chart version to 1.21.1.

NOTE: the chart version has been bumped to 1.21.1, lined up to be merged after https://github.com/kubernetes/charts/pull/3872.

/assign @krancour

/ok-to-test

/lgtm

Time for 1.5.3 😃
Would you like to make a PR @siwyd? If not, I'm happy to do this myself :–)

@kachkaev I'll just update this one, that would make sense I guess :)

But this PR is already merged - not sure if that’s going to work. IMO it should be a new one, based on the cuttent master.

Ow hah, whoops. Thought this one was still waiting. Got a few of them open, starting to get confused :) Got this one for ya: https://github.com/kubernetes/charts/pull/3923


#245: support the in operator for Circuit and CircuitBuilder

implement contains method

@arcturusannamalai Can you please add some tests for this work? Thanks!

need a bit more time; will do!

done @rturrado

@arcturusannamalai It would be worth checking where in the code it is now convenient to use the in operator.
Also, please make sure you run the requested tests and linters locally before committing. You can check what to run at the Contributing guide.
Thanks!

@rturrado - please check my latest attempt :)

@rturrado - please check my latest attempt :)

I'm sorry @arcturusannamalai, but could you please explain what the latest commit has to do with the purpose of this PR?

@rturrado - please check my latest attempt :)

I'm sorry @arcturusannamalai, but could you please explain what the latest commit has to do with the purpose of this PR?

I added code annotations etc. to pass the criteria in your project post-commit checks. It keeps logic and a new unit-test added for the test intact.

I added code annotations etc. to pass the criteria in your project post-commit checks. It keeps logic and a new unit-test added for the test intact.

Sorry, but that force-pushed the ma-245 branch contains a lot of changes I didn't understand.
Anyway, you keep missing running the static analysis tools.


Support deploying the dashboard to kubernetes and docker compose

We just merged the work to decouple the dashboard from the apphost so it can run as a separate process and as a container image. We should figure out how aspirate can deploy this image to the cluster and wire it up to make the end to end work.
A couple of high-level things:

The dashboard isn't represented in the manifest today so it needs to be handled by aspirate separately
The dashboard talks to resource server to make that list of resources work.

This resource server would need to be deployed as well and it would need to talk to the kubernetes API to get the aspire resources in order to make them show up in the dashboard.
The dashboard works without one and can act solely as an otlp endpoint

Services need to be configured to send telemetry to the dashboard
The dashboard has no access control. It'll probably need to be an internal service only that can be manually port forwarded and launched in the browser (aspirate could have a command to automate this).

To enable pushing to more than one telemetry source, we might also want to consider using the otlp collector and configuring the dashboard as one of the places it pushes to. That would allow fanning out to multiple telemetry sinks (using the dashboard along side grafana etc).
For docker compose, there might be a simpler story for the resource server but I'm not 100% sure what it would look like as it would need to integrate with the local docker daemon.

Awesome thanks David
It's great that you've made it available as a container image too. Massively simplifies things
I'll start drafting something together tonight. Is this for preview 3?

I'll start drafting something together tonight. Is this for preview 3?

Yep! I think the deployment mechanics are more important than the resource server. At least we could tackle that part separately.

We're not re-branding to Aspire APM.

Meanwhile what's the current workflow to use it as a standalore product, any "official" documentation about using it as a tool?

It's currently only shipping as a container image, not a dotnet tool.

Meanwhile what's the current workflow to use it as a standalore product, any "official" documentation about using it as a tool?

It's currently only shipping as a container image, not a dotnet tool.

do you mean I can already use it in my docker compose? how?
I was looking for images in docker hub without luck, was looking for something like mcr.microsoft.com/dotnet/aspire

@prom3theu5 glad you're better now. I'd be happy to meet and whiteboard something (and contribute code).

Can the preview 4 dashboard interoperate with services using Aspire Preview 3?

Yes!

Hey @prom3theu5 I'm back from Australia, so will setup time next week.

Thanks @davidfowl
Hope the flight was ok

thks @davidfowl
I am currently working here, adding a Dashboard container in AppHost, and then adding my application to this container to establish an independent relationship between Dashboard and resource. However, it seems that currently, it is not very useful.

Added in v0.5.3-preview, which is building / releasing now


Add support for different insulin strengths, such as U-200

Added for tracking as discussed on Discord and as Jon already had been thinking about doing this as well:
Working with U-200 I started wondering if it'd be worthwile to implement different insulin strengths. You keep the same settings and you bolus and log the same amounts, but the system will for U-200 reduce it by 50% relative to U-100 and for U-400 it will reduce it by 75% relative to U-100. (Or explained in another way: the ISF and I:C are increased to 200% for U-200 and to 400% with U-400 whilst basal is reduced 50% or 75% respectively). Lastly, it'd have to multiply the amount of units available in the reservoir. (Eg: Omnipod Dash that starts counting down from 50 would show 100 on U-200) So what you see as the user is when you want 1U: you still get 1U. 1U is always still 1U. It's just the insulin output that's reduced in the background. Eg: if we ask 2U on U-200 mode, we tell the pump to inject 1U.)
The reasoning behind it is that this leads to:

a.) Consistency. It is similar to using Humalog/Lyumjev pens with increased potency. With the pens Eli Lily provides, 1U on the dial is still 1U injected - this doesn't change. The mechanism reduces the insulin (in ml) administered, not the user. So with U-200 when you inject 100 units, it injects only 0.5ml instead of the 1.0ml it would've been on U-100. This ensures the user doesn't have to change anything, the only thing that changes for the user is that the pen lasts twice as long.
b.) Prevents confusion when you have to do the maths yourself whilst coming from U-100 and are used to doing bolus calculations in your head or correcting quickly
c.) Keeps nightscout output consistent so for analysis you don't have to multiply it by 2 or 4 for the interpreter (eg: endo) to understand it. Plus some added bonuses if the care team hates U-200/U-400.
d.) Keeps settings cross-compatible with any insulin type and strength, nothing changes; you just have more units available to work with (a 200U Omnipod becomes 400U or 800U)
e.) Makes tuning work better and cross-compatible between different insulin types as it has the same data to work with, only minor tweaks may be necessary after switching to a different concentration.

Possible negative effects I honestly couldn't directly find any, especially as Eli Lily chose the exact same strategy with their pens. (Reduce output, rather than making the user reduce their numbers) The current negatives are you have to maually change profile and manually remember it and the nightscout, AT and AS data get's "tainted" when you switch insulins. If it's as easy as switching in-app from U-100 to U-200 when you switch insulin type: that's easier and probably safer.
There are some caveats, however, such as:

a.) The stored settings on the pump will be different than what the app shows, such as the basal rates. Whilst the app in this setup will show the same basal rates + ISF + I:C as on U-100, we do instruct the pump in the background to deliver 50% less on U-200 and 75% less on U-400. So 1U/hr basal will be 0.5U/hr shown on the pump with U-200 and 0.25U/hr shown with U-400. An in-app warning above/next to the basal rates (and other factors) plus a clear explanation in the docs is a good idea for starters.
b.) The minimum bolus delivery (and minimum basal per hour) is different and is a hardware limitation. Eg: if 0.05 is the minimum, on U-200 that'd be equivalent to 0.1U and on U-400 that'd be equivalent to 0.2U minimum.
c.) People using other software to generate reports from data stored on their pump, such as Glukoo or Tidepool, may see their insulin administration is reduced by 50% or 75% compared to what is shown in-app and in Nightscout. With the current supported pumps, that's likely not an issue (as they cannot be read with such tools to my knowledge); but it may be a problem in the future. It's important to point that out and/or get in touch with the developers of such tools to allow setting insulin strength.

Thank you for your consideration and thanks in advance to everyone providing input/suggestions/feedback on this.

Hi @LiroyvH
Love the idea of supporting U200 insulin from within iAPS. Just to add a point to your issue here and maybe move the discussion forward:
As a person that regularly struggles with pod leaks and has to „guesstimate“ how much insulin was administered, how much to delete from dosing history and possibly how much to give by manual dose, „hiding“ the actual dose would make this troubleshooting harder. Generally speaking, it would just make it harder to troubleshoot dosing in „what happened here when X was dosed or Y happened“ type scenarios.
I like the idea, generally, but I think it comes with big caveats when you are trying to analyze dosing history and I don’t think that you can 1:1 translate how Eli Lilly does its pen dosing mechanism to pump therapy.
How about you can switch or toggle a U200 or U400 switch / option and it automatically adjusts your settings for you (while considering technical limitations such as 0.05u minimum dose)? When you decide to switch back to U100, you just deactivate the switch. That way it doesn’t „hide“ things and the app will still clearly guide you through all dosing, but it stays transparent and you don’t have to go in and fiddle with settings.

Ola @dnzxy :)
Thanks so much for the feedback and thanks for bringing it here. :)
I gave this some thought in the interim and I don't think I really understand how in this situation the problem is different when compared to the existing situation (even with U-100)? The system doses what you put in, so that’s still what you guesstimate on and is exactly the same situation when on U-200 or U-400. 🙂 The unit is the measurement, regardless of U100 or U200 - so deleting the treatments also stays exactly the same. That the pump, as it’s dumb and only understands U-100, says it delivered fewer units (to compensate for different insulin type) doesn’t change the fact how many standardised units were actually truly delivered. 1U is 1U, that the pump thinks it’s 0.5U or 0.25U is irrelevant; that’s because it thinks U-100 no matter what you throw in. iAPS would solve that by showing how many standardised units are truly delivered.
 The ml delivered doesn’t change anything there. If you can follow my train of thought there? 🙂 The situation isn’t any different? History stays the same. Etc.
The only thing different is that maybe the puddle of insulin you see is smaller (though that’s an issue when halving as well hehe). Think of it as an Omnipod carrying 400U rather than 200U whilst 1U is 1U. Rather than having to half all your doses and technically “lie” by delivering “half the amount” you’re used to, you would now still deliver the same units - just with less millilitres of insulin solution being CSII-administered. But whether you’re on U-100 or U-200: the same problem is at play, no? I mean, if you half everything in your settings and your pod starts leaking you have to guesstimate it differently as well if the size of the spot is the indicator.
Long story, haha! But wanted to cover all bases of how I think we should approach it/what the mentality behind it is. :)

I like the idea, generally, but I think it comes with big caveats when you are trying to analyze dosing history

That I don’t think I understand, sorry! Can you please elaborate why would it be a problem when looking at the dosing history? Maybe if you look on a Medtronic pump (hence warning and explanation in app!), but for an Omnipod it shouldn’t matter at all as iAPS will tell you exactly what was dosed?
When you think of it, at least in my opinion: compensating by doing /2 or /4 on all doses is more of a cheat than when using the unit as the standard as how it should be. :) And U-100, 200 or 400: 1 unit is always 1 unit, the amount of ml isn’t in the equation, we just always had to do that because the pumps were too dumb to speak U-200 or U-400 and we had to do the maths ourselves.

How about you can switch or toggle a U200 or U400 switch / option and it automatically adjusts your settings for you (while considering technical limitations such as 0.05u minimum dose)?

Switching the profile settings doesn’t really solve any of the other issues unfortunately :(. Then you still run in to “fake” delivering fewer units (you say you injected 0.5U but in reality it was 1 or 2U), calculations work completely differently, reports in Nightscout change, your profile and basals are “wrongly” adjusted, the algorithm may struggle with your new TDD-data, etc.
Thanks again for the feedback, ideas and input!

1U is 1U, that the pump thinks it’s 0.5U or 0.25U is irrelevant; that’s because it thinks U-100 no matter what you throw in. iAPS would solve that by showing how many standardised units are truly delivered.

I think I misunderstood this part. I thought you wanted to manipulate what is being shown as dosed and show just 50% or 25% of what was actually dosed.

The only thing different is that maybe the puddle of insulin you see is smaller (though that’s an issue when halving as well hehe).

This may actually be an issue in itself because this may make it harder to identify leaky pods / occlusion; but totally different scenario and issue.

Think of it as an Omnipod carrying 400U rather than 200U whilst 1U is 1U. Rather than having to half all your doses and technically “lie” by delivering “half the amount” you’re used to, you would now still deliver the same units - just with less millilitres of insulin solution being CSII-administered. But whether you’re on U-100 or U-200

Yep, totally making sense now. The guesstimating part stays the same. I don’t know by, but I initially thought we were setting out to manipulate what was being shown in iAPS, but your suggestion wouldn’t do this. It’s just that 1U is actually 2U or even 4U strength. I may have been guided down this thought pattern by that last paragraph talking about settings not being truly what’s being dosed. My fault, sorry.

Can you please elaborate why would it be a problem when looking at the dosing history?

Same issue, see above. Thought we were masking what’s being dosed.
Sorry for my initial comment. I seem to have completely misunderstood your suggested feature in a very weird way. So essentially, instead of masking anything in iAPS, the idea is to actually still show the true insulin dose, so units-based history and settings, just half (or quarter) the actual injected dose, e.g., app shows 1U dosed, but it actually just doses 0.5U=U200 or 0.25U=U400. Same for IC or ISF. IC of 1:10 is still 1:10, but the actual dose would be 0.5/0.25U; ISF of 50 still means 1U moved sugars by 50mg/dl, yet it requires only half or quarter of the „fluid“ (as in the clicks by the pod = insulin injected).
Do you know if Jon, Pierre or anyone else has started to work on this yet?

I love this idea. Two things I don't see mentioned above:
Currently when switching between U100 and U200 with iAPS, it's important to either reset the app or build a second iAPS app, because several equations use TDD history which would be very wrong after switching concentrations. Sounds like this wouldn't be an issue with your solution, though.
Also, Bolus Increment would have to be set to 0.1 instead of 0.05 for U200 (.2 for U400, which I didn't even know existed). The bigger problem that needs addressing is basal increments, though, since I currently don't see any settings to alter that minimum.

Love any idea that makes life as a T1D easier.  Per your comment and @MikePlante1's info and help, I set up a U200 iAPS version, which I will be using when I change my pod within the hour.  I absolutely would love to NOT do calculations constantly.

@dnzxy No problem! Re-worded it a little in the hopes its clearer to prevent confusion. :)

Sorry for my initial comment. I seem to have completely misunderstood your suggested feature in a very weird way. So essentially, instead of masking anything in iAPS, the idea is to actually still show the true insulin dose, so units-based history and settings, just half (or quarter) the actual injected dose, e.g., app shows 1U dosed, but it actually just doses 0.5U=U200 or 0.25U=U400. Same for IC or ISF. IC of 1:10 is still 1:10, but the actual dose would be 0.5/0.25U; ISF of 50 still means 1U moved sugars by 50mg/dl, yet it requires only half or quarter of the „fluid“ (as in the clicks by the pod = insulin injected).

Yes and no. In technical terms, that is what it does - but I'd like to ensure the "actual dose" part isn't worded that way. It actually doses an adjusted dose to compensate for the problem with the pump solely speaking U-100. Might sound a bit nitpicky, sorry for that :P, but I hope we can move away from taking what the pump says as "the true/actual dose" and instead consider how many units we truly inject. If we dose "0.5U U-100" whilst the pump is filled with U-200: that is simply 1U actual dose, not 0.5. That the pump displays it wrong/has to be told what to inject "in the wrong way/dose" doesn't alter the fact about the units actually being delivered. The unit is the standard, not what the pump claims the U-100 equivalent is and which we have to compensate for by "reducing" output in the background.
@MikePlante1

Currently when switching between U100 and U200 with iAPS, it's important to either reset the app or build a second iAPS app, because several equations use TDD history which would be very wrong after switching concentrations. Sounds like this wouldn't be an issue with your solution, though.

Correct, this shouldn't be an issue as the algorithm can keep using the exact same units and profile settings. (ISF, CR, basal, etc.)

The bigger problem that needs addressing is basal increments, though, since I currently don't see any settings to alter that minimum.

I think this is guarded by the same minimal delivery? If your hourly basal rate is 0.1 which is the pump minimum then it cannot account for that with U-200, but that'd be a problem when attempting to reduce it manually on the pump as well; you can't go beyond the technical limitations of the pump in any way at any time. So U-200/U-400 simply wouldn't be fit for those people.
At other moments I don't think it's an issue as it should simply reduce the basalrates in the background and send that, background modified, profile to the pump so the pump delivers U-100 equivalents (compensated for by us, iAPS keeps showing the actual units) of whatever insulin strength (U-100/U-200/U-400) it has. If someone uses extremely little basal, it's rather unlikely they'll use U-200 so I don't think we'll quickly find someone who would hit this limitation. But if they do: nothing can be done. 0.x is the technical minimum and even us accounting for it won't make a difference.

The unit is the standard, not what the pump claims the U-100 equivalent is and which we have to compensate for by "reducing" output in the background.

Very much agree, I was just trying to make sense to what the dosing (as in less fluid, less ticks from the pump perspective) would mean with non U100 insulin. I meant it the way you so rightfully described it.
Do you know of any development in this direction? I took a look at the APSManager the other day and some of the instances where enactBolus and enactTempBasal are called, but it seems very odd to just multiply that dose by a specific factor. I‘m also not sure if some changes would need to be made to dependencies (OmniKit?) and if it’s a good thing to be altering that; I‘m not sure it’s necessary though so would be interested if there are some rough outlines of how this would go implementation-wise.

This is implemented in dev branch


feat: add cardBin to js change events

Description

feat: add cardBin to js change events

Testing required outside of automated testing?

[X] Not Applicable

Screenshots (if appropriate):

[X] Not Applicable

Rollback / Rollforward Procedure

[X] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.18.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: