add a new env variable to define the SCHEME

I am not sure how this affects Heroku, there is a default to HTTP which should prevent any breakages due to the KODI_SCHEME env variable not being set.
Would the only Heroku change be the setting of the env var by adding it to the config:set command i.e.
heroku config:set KODI_SCHEME='https' KODI_ADDRESS='your_ip_or_dynamic_address' KODI_PORT='kodi_port' KODI_USERNAME='kodi_username' KODI_PASSWORD='kodi_password' --app app-name-and-number.
If that is the case I will change the readme to include it.

Stupid question.. but where do I even enable HTTPS in Kodi?  http://kodi.wiki/view/JSON-RPC_API#HTTP doesn't list it as an option, nor do I see it in Kodi's configuration.

You don't :)
But if you are not running the skill locally then the KODI_ADDRESS var would need to be your dyndns address and that can be HTTPS e.g. https://dyndns.domainname.com:33133
Then you port forward or use a reverse proxy to direct traffic to your Kodi local ip using HTTP.

Ah I gotcha.
Looks fine to me then.

Squashed commits
Also updated readme to include the KODI_SCHEME var in the Heroku command and added information about what should go into the vars.

It'd be relevant to this PR if you want to add the variable for specifying the path too (KODI_JSONRPC_PATH?  Or something like that maybe).

I could, but as this PR is (hopefully) ready to merge it would be good to tick it off and I can clean up  a bit.

Well, it isn't necessary, but this PR won't work if the user can't proxy on the default path for whatever reason (e.g., has another configured already).
Also, you should probably add something to the documentation describing that this is for a proxy.  It wasn't initially clear to me and I'm going to guess other users are just going to assume that Kodi supports HTTPS now and ask about it on the forums.

Added env vars for KODI_SCHEME and KODI_SUBPATH and included some comments in the .env files.
Tested with AWS only, defaults are in place to not upset any installs that don't use the extra vars.

Looks OK at a glance.  I'll make sure there's no issue with the defaults when I get home today.

Sorry, I'm not ignoring this -- just have been coming home so late I don't have the energy to get to it.  Should be over with soon though.

All merged.  Removed some trailing whitespace and shuffled a bit around, but it's the same functionally.


[Feature Request] Array of dicts of tensors structure

Storing them in "columnar format" can be more compact in some circumstances (e.g. they are copy-on-write safe in multiprocessing context as they are stored as a very small number of tensors not depending on "dataset" size): https://gist.github.com/vadimkantorov/86c3a46bf25bed3ad45d043ae86fff57

Thanks for this @vadimkantorov
How do you see this interacting with TensorDict?
Should Arrays of dicts be a possible data type stored by tensordict? Do you have a typical use case in mind?

I don't know much about TensorDcit project. I just wanted to share a usecase I had for dicts of tensors: represent a dataset in a way that avoids copy-on-write problems: https://github.com/pytorch/pytorch/issues/13246
I represented this array of dicts of tensors as columnar dict of tensors, each key is a tensor that concats all per-items tensors related to a given key.
One way it could integrate with TensorDict: provide a constructor/util function and a "indexing/getitem" method/util that would do slicing of all keys in TensorDict and return a new, "per-item" TensorDict. These may be just recipes from docs or util functions + tests that no copy-on-write is indeed happening.

Also, similar usecase may be for collecting some partial results from validation loop. Usually, one would store them in a list of dicts of tensors and then analyze it somehow. If such a structure is implemented in some extendable way (as proposed here: https://github.com/pytorch/pytorch/issues/64359), it could be useful

That is something we have I think.
Here's an example:
>>> tensordict1 = TensorDict({"a": torch.zeros(1, 1)}, [1])
>>> tensordict2 = TensorDict({"a": torch.ones(1, 1)}, [1])
>>> tensordict = torch.stack([tensordict1, tensordict2], 0)
>>>
>>> tensordict
LazyStackedTensorDict(
    fields={
        a: Tensor(torch.Size([2, 1, 1]), dtype=torch.float32)},
    batch_size=torch.Size([2, 1]),
    device=None,
    is_shared=False)
>>>
>>> tensordict[0] is tensordict1
True
>>> tensordict["a"]
tensor([[[0.]],

        [[1.]]])

The LazyStackedTensorDict does not currently support appending but we might consider that.


[config] no param naming validation

I have noticed that one could make a typo in the config file and DeepSpeed silently ignores it. e.g. I did:
    "gradient_clipp1ng": 1

and got no errors.
Not sure if it should validate the value as well, as float is expected, but I guess int is fine as it's just converted to float.
This lack of validation could lead to user errors which could be hard to notice.
Nothing urgent, but at some point it'd be good to tell the user if they added a config entry which is invalid.
Thank you.

@stas00 Apologies for the radio silence and for stalling your progress.
Your point is well made regarding silent errors from typos in the config file. In the past, users have actually exploited this lack of validation as a way to convenient disable features without deleting the entries. So perhaps a reasonable solution would be to introduce yet another config option to validate the config entries and issue a warning for each unrecognized entry. What do you think?

@stas00 Apologies for the radio silence and for stalling your progress.
Your point is well made regarding silent errors from typos in the config file. In the past, users have actually exploited this lack of validation as a way to convenient disable features without deleting the entries. So perhaps a reasonable solution would be to introduce yet another config option to validate the config entries and issue a warning for each unrecognized entry. What do you think?

Oh, no problem, I'm sure you guys need some breaks too!
Your suggestion to make the validation optional would work great, @tjruwase. This is a very low priority feature request.
Since you mentioned that the lack of validation is exploited to make users' life easier,  I'm also thinking that json isn't a user-friendly format for configuration, because it has a ton of problems, e.g.:

don't put comma here, but must put it here,
can't use comments,
can't use python 5_000_000_000 numbers - who can read<PHONE_NUMBER>
json, IMHO, is more of a program-intermediary format, rather than designed for human manipulation.

It'd have been much better to use some other, more user-friendly format, IMHO. But it has been a while since I had to deal with config files so I'm not sure what's the standard these days.

Oh, no problem, I'm sure you guys need some breaks too!
Your suggestion to make the validation optional would work great, @tjruwase. This is a very low priority feature request.
Since you mentioned that the lack of validation is exploited to make users' life easier,  I'm also thinking that json isn't a user-friendly format for configuration, because it has a ton of problems, e.g.:

don't put comma here, but must put it here,
can't use comments,
can't use python 5_000_000_000 numbers - who can read<PHONE_NUMBER>
json, IMHO, is more of a program-intermediary format, rather than designed for human manipulation.

It'd have been much better to use some other, more user-friendly format, IMHO. But it has been a while since I had to deal with config files so I'm not sure what's the standard these days.

Completely agree with the pain of json, so we are very open to any suggestions.

Completely agree with the pain of json, so we are very open to any suggestions.

Thanks @stas00, JSON validation I think is on our radar and definitely something we should add in the short term. Also agree JSON isn't the most user-friendly of formats. We'll have to look into alternatives. I have heard good things about hjson. It allows commas/comments but I don't think supports numbers in the way you describe unfortunately. YAML might also be a reasonable option but also comes with difficulties haha

Thanks @stas00, JSON validation I think is on our radar and definitely something we should add in the short term. Also agree JSON isn't the most user-friendly of formats. We'll have to look into alternatives. I have heard good things about hjson. It allows commas/comments but I don't think supports numbers in the way you describe unfortunately. YAML might also be a reasonable option but also comes with difficulties haha

I was going to suggest YAML, but I thought that something better must have been invented since then. YAML is from around 2001 if I remember correct.
I have never used https://hjson.github.io/, but it does look like the most straightforward solution as it was created to overcome limitations of json for human use. May be that's all is needed.
I don't know how your user/developer community works, perhaps throwing the net wider would give practical feedback from users who may have used hjson already and can tell how good it is in practice.

I was going to suggest YAML, but I thought that something better must have been invented since then. YAML is from around 2001 if I remember correct.
I have never used https://hjson.github.io/, but it does look like the most straightforward solution as it was created to overcome limitations of json for human use. May be that's all is needed.
I don't know how your user/developer community works, perhaps throwing the net wider would give practical feedback from users who may have used hjson already and can tell how good it is in practice.


Can't import Bestiary 2 - Kelpie

Can't import statblock:
Kelpie      CR 4
XP 1,200
Male kelpie (Pathfinder RPG Bestiary 2 172)
NE Medium fey (aquatic, shapechanger)
Init +7; Senses low-light vision; Perception +13
Defense
AC 17, touch 13, flat-footed 14 (+3 Dex, +4 natural)
hp 38 (7d6+14)
Fort +4, Ref +8, Will +6
Resist fire 10
Offense
Speed 40 ft., swim 40 ft.
Melee 2 slams +6 (1d6+2 plus grab)
Statistics
Str 15, Dex 16, Con 15, Int 8, Wis 12, Cha 17
Base Atk +3; CMB +5 (+9 grapple); CMD 18
Feats Alertness, Deceitful, Improved Initiative, Weapon Finesse
Skills Acrobatics +3 (+7 to jump), Bluff +15, Disguise +15, Perception +13, Sense Motive +13, Stealth +13, Swim +10
Languages Aquan, Common, Sylvan; telepathy (1 mile, previously touched creatures only)
SQ amphibious, captivating lure, change shape (hippocampus or horse; beast shape I), change shape (Small or Medium humanoid; alter self)
Ecology
Environment any water
Organization solitary or shoal (2-5)
Treasure standard
Special Abilities
Amphibious (Ex) You can survive indefinitely on land.
Captivating Lure (1/day, DC 16) (Su) Once per day, a kelpie can use a powerful mental attack to lure in a single creature within 60 feet. The target must make a DC 16 Will saving throw or become captivated by the kelpie, thinking it is a desirable woman in mortal danger or (if in hippoc
Change Shape (hippocampus or horse; beast shape I) (Su) You can change your form.
Change Shape (Small or Medium humanoid; alter self) (Su) You can change your form.
Energy Resistance, Fire (10) You have the specified Energy Resistance against Fire attacks.
Grab: Slam (Medium) (Ex) You can start a grapple as a free action if you hit with the designated weapon.
Low-Light Vision See twice as far as a human in dim light, distinguishing color and detail.
Swim (40 feet) You have a Swim speed.
Telepathy (1 mile, previously touched creatures only) (Su) Communicate telepathically if the target has a language.

I used Hero Lab to produce this statblock.  For greater accuracy, you might want to use one of the online resources.  Hero Lab can truncate some of the text.  All the other statblocks from Bestiary 2 imported -- a total of more than 96% imported.

Used your latest module that was available as of this morning.

Identified Issue: Parenthesis in languages, e.g. Languages Aquan, Common, Sylvan; telepathy (1 mile, previously touched creatures only)


Update k8s deployment manifest

Motivation and Context
The previous version runs a loop constantly causing the pod to consume CPU resource it doesn't need.
What has changed

Update deployment manifest

How to test?
Run through an unaddressed batch, before and after check the CPU usage drops when the pod is not running anything
Links
https://trello.com/c/vr0EdmaM/868-bug-qid-batch-runner-constantly-uses-cpu-at-rest

 BUG: qid-batch-runner constantly uses CPU at rest


Multiscreen > Notification on the screen where the application is located

Currently if I have the app on the left screen, notifications are displayed on the right screen. Would be better if notifications are on the same screen as the application or make an option

I dont think that this is possible to do. The operating system handles the notifications. We just create it on the OS notifications center.


uranium isnt registered as an ore on a fresh profile.

I recall uranium being added automatically to the ore registry and the sieve registry, is this not the case anymore? or am I just misremembering?

I had added the colour as 4e5b43 ;
it seems close ish enough to Immersive engineering's
but then I messed up the fluidblock transform registry and the sieve registry and disabled it again because I didnt feel like troubleshooting my jsons I just wanted to plug and play (though that's just delaying the inevitable because I will have to add stuff because I want to add ways of getting astral sorcery to my skyblock)
if you take the time to add it to the defaults I would be very thankful!

the chunk drops for uranium should probably be rarer or as rare as the gem drops I reckon


rabbit: 1.0.0 -> 1.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for rabbit is: A tool for identifying bot accounts based on their recent GitHub event history
meta.homepage for rabbit is: https://github.com/natarajan-chidambaram/RABBIT
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.1 in filename of file in /nix/store/w2qmv1mp89mnrnrq8jiczy3g3lssdrps-rabbit-1.0.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
rabbit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w2qmv1mp89mnrnrq8jiczy3g3lssdrps-rabbit-1.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rabbit https://github.com/r-ryantm/nixpkgs/archive/df0b73e74e3df4f5e68e2ff6d19aaad90b81b7f8.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/df0b73e74e3df4f5e68e2ff6d19aaad90b81b7f8#rabbit

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w2qmv1mp89mnrnrq8jiczy3g3lssdrps-rabbit-1.0.1
ls -la /nix/store/w2qmv1mp89mnrnrq8jiczy3g3lssdrps-rabbit-1.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

rabbit
rabbit.dist

Maintainer pings
cc @drupol for testing.

@ofborg build rabbit

@ofborf eval rabbit


Total energy of panels drop when inverters goes offline

Describe the bug
After the microinverters goes offline (no more power from the sun?), the integration report that the "total energy" for the inverter is what it was set to at the beginning of the day.  I assume that there is some kind of "hack" to add the total energy of the previous days to the currently generating data and that the inverter going offline make the calculation fail...
To Reproduce
Steps to reproduce the behavior:

Configure the DC total energy port for each individual panel
Wait for the inverter of this panel to go offline
observe the drop in energy produced (exactly the generation of the current day)

Expected behavior
No drop to a previous lower value
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I just installed the integration, so I may not be using it right.  Although I would still not expect a sensor to drop back to a value as old as the previous day...  I know this is the data sent by the DTU, so it's not that reliable either as there is probably no data for the day if the inverter is down...

Thanks, I will have a look at it.

In the mean time, I've used the Daily energy sensor and it's working pretty well.  So it's just the "total" one that isn't what I would have expected.

In the mean time, I'm still using the individual panels value as it's more reliable.  But using the DTU sum would be nice... I'm also wondering if it's the DTU and will have a look later tonight if times allow.

I just installed this addon (and the inverter, for that matter) yesterday. As expected (?) the inverter went offline over night, however, the "Total energy" entity does not reset for me:

I just installed this addon (and the inverter, for that matter) yesterday. As expected (?) the inverter went offline over night, however, the "Total energy" entity does not reset for me:

This is exactly the expected behaviour. Thanks.

@sc-ampersand-p you may want to look at "total_daily_energy".

Also only resets once per day, as expected, in spite of the DTU briefly going offline occasionally.

You're lucky, this is what I have ;

Is your DTU blocked from the Internet? Just curious about potential differences.

Is your DTU blocked from the Internet? Just curious about potential differences.

Nope, alway reporting to S-Miles.

Same here. Might it be down to the solar panels being used? Or is that not a reasonable line of inquiry?

The panels used are Thornova, but it doesn't matter, it's really the way the reporting is done into either the DTU, hoymile-wifi or this module.

I suspect it's the DTU

@elafontaine what really bugs me is that it starts from 0. Because this means that the DTU reports this state.
You can cross check that by manually calling the hoymiles-wifi lib.
Maybe there is some setting in the DTU?

@stheid yes, that sounds like a good approach and should actually be rather streight forward to implement.
I'm still hesitant to do so, since it might automatically "hide" other bugs in the DTU.
@elafontaine What happens if you directly connect to the DTU via the hoymiles app once the inverter goes offline? Do you also see a similar drop in the app?

Also @elafontaine in the initial bug you were talking about the total energy dropping to 0. Do you still see this issue or is only the daily energy affected?


Read remote state file from specified working dir

This changes shouldConfigureRemoteState in remote_state.go to always pass the WorkingDir option to ParseTerraformStateFileFromLocation in terraform_state_file.go. If --terragrunt-working-dir is specified the path to state files in that working dir should always take precedence over DEFAULT_PATH_TO_LOCAL_STATE_FILE and DEFAULT_PATH_TO_REMOTE_STATE_FILE.
Fixes #95.

I was concerned about the case of the workingDir not existing, but that's handled gracefully downstream by ParseTerraformStateFile in any case.
@brikis98 042ae90 reverts this back to the original structure if/else-if/else structure.

Just created a new release here: https://github.com/gruntwork-io/terragrunt/releases/tag/v0.9.2. If the build passes, the binaries should show up in a few minutes.


Allow the climbing_slope to be a zero

In case of a diversion, there is no need to a climbing phase, so the climbing_slope should not be a None but it can be a zero

I have Updated the branch, now it should pass the tests


Rename constant to match platform idioms

Goal
Replaces VERSION with Version to be better aligned with Go naming conventions.

Correct - those are v1. Both v1 and v2 live in the same codebase 😕 - for the final release PR I've at least put in a test to avoid accidental changes to v1.

Correct - those are v1. Both v1 and v2 live in the same codebase 😕 - for the final release PR I've at least put in a test to avoid accidental changes to v1.


feature request: identical file names with path addition

Hey, I like your extension! And the issue is more like a feature request.
If I open files with a same file name, then it looks like that:

Nova itself handles it like that in the tabs and add part of the path to the name, like that:

Maybe that would be possible for your extension, too.
Nevertheless... great extension! Missed this feature in Nova, but thanks to you.

Thanks for your comment.
I don't know if nova will let me do that but I will try it.
Best regards and stay tuned ;-)

I would second this enhancement if possible. It would help determine which files belong to which path, otherwise it's a random game of click-the-file.

Hi.
I try to implement this feature. Now you can see las directory name before file name:

You can update it from nova extension panel.
Thanks to all! and Merry Christmas.


DDN64: image()

https://bugzilla.mozilla.org/show_bug.cgi?id=703217 - Implement image() from CSS Image Values and Replaced Content Module Level 4

[ ] - add disambiguation to https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/Image

[ ] - add image() and conic-gradient() to https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Images

[ ] - determine if url() and element() should be added to https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Images

[ ] - update https://developer.mozilla.org/en-US/docs/Web/CSS/image
[] - add image as an option

[X] - create image() page

[-] - Example - interactive

[-] - example Codepen

[X] - syntax

[ ] - a11y concerns

[ ]  - printing

[ ] - BCD

add link to values page

[X] - Explain  media fragments to clip out a portion of an image

[X] - Example: use a solid color as an image

[X] - fallback to a solid-color image, when the image at the specified url can’t be downloaded or decoded

[X] - automatically respect the image orientation specified in the image’s metadata

[] - https://developer.mozilla.org/en-US/docs/Web/CSS/element - make sure this is added everywhere
Acceptance criteria:

[ ] all above tasks are complete
[ ] ticket changed to DDC

I created the codepen examples, but they are staying hidden as no browser yet supports image(), so it will just look broken. When there is browser support, we can make the output visible.


Comment out dev dependencies on deploy

Right now due the naive dependency resolver in Swift PM all related repos for all dependencies are cloned. This kinda sucks, it means things like SwiftFormat and SwiftLint are cloned when you just want to have a copy of Danger Swift or Komondor.
I propose the deployment process comments out any of the dependencies we declare as a dev dependeny before making the tag, and then undoing it after.

This is in


move part of porch/pkg/oci to pkg/oci

Split it from https://github.com/GoogleContainerTools/kpt/pull/3450 in case it's useful.

LGTM


Fitness-App using React js

Describe the project you want to add with tech stack

I am contributing in this by making a Fitness app using React js .
Expected behavior

The data comes from the api for all the gym exercise . This website will be helpful for the gym content . This is a fully functional dynamic website.
Screenshots (optional)

Additional context (optional )

Please assign me this issue so that I can resolve it under GSSOC-23


VST3 regularly blacklisted by Ardour 6.7

Running sfizz-git r3699.ce2170c8-1. Often when creating a MIDI track in Ardour 6.7 I will only see the LV2 version (which crashes Ardour when opening the SFZ file). Clearing Ardour's plugin blacklist works but it is only a matter of time before it disappears again.

If I read the Ardour code correctly, the blacklisting is a result of a failure to scan the plugin, or something to do with Ardour's cache file.
I don't know much else, but a log might be helpful perhaps.


cyclenext/swapnext are unpredictable

I notice that if one is to use swapnext - the clients still preserve their order in the "stack".
This leads to cyclenext become unpredictable since the client order in the screed does not reflect to the order in the "stack":
------------- -----------
|            |     2     |
|      1     |------------
|            |     3     |
------------- -----------

------------- -----------
|            |     2     |
|      3     |------------
|            |     1     |
------------- -----------

Any idea on how to make this a little more predictable?
(since there is a dwindle layout and master layout to consider)
I prefer always using those instead of movefocus and movewindow.

jesus christ y'all have some real gaps in like, reading
bind = SUPER, X, layoutmsg, cycleprev


bolt storage api

Looks good!

We need more than a master branch on this repo so my tagging makes sense, lol.
Well, what can you tell us about this PR @tammybutow ?

I may be missing the obvious, but does one use the code in this PR? :confused:

wrong branch, will create a new one ~ the code is created duing the Women Who Go NYC hackathon that uses boltdb is here: https://github.com/womenwhogonyc/samples/blob/master/chat/app/chatroom/storage.go

How is the storage.go code consumed by the sample app?
PS - nice hackathon, do you guys have a website or any presentations? I could add the link to our Articles page if it mentions Revel :)


[RSDK-9281]   Add native type return to Flutter SDK DiscoverComponents

RSDK-9281
Add native type return to Flutter SDK DiscoverComponents
Tested locally

LGTM. my only q/comment is who will be reading these results? looking at the photo you included for local testing, the results are a bit difficult for a user to interpret (it is hard to tell if the nested discovery objects are related to the top-level component?). however, if this is primarily for internal use, than I can understand priorities might be different

Really good point. This is a point of discussion with AV and mobile right now. I think this is a good initial step though https://viaminc.slack.com/archives/C07GTSXSVEC/p1731708356210009?thread_ts=1731688631.621549&cid=C07GTSXSVEC

LGTM. my only q/comment is who will be reading these results? looking at the photo you included for local testing, the results are a bit difficult for a user to interpret (it is hard to tell if the nested discovery objects are related to the top-level component?). however, if this is primarily for internal use, than I can understand priorities might be different

Really good point. This is a point of discussion with AV and mobile right now. I think this is a good initial step though https://viaminc.slack.com/archives/C07GTSXSVEC/p1731708356210009?thread_ts=1731688631.621549&cid=C07GTSXSVEC

I do still agree with this point, on the frontend right now I'm playing around with getting this to something useable and it's tricky. The json string for the cameras in the results looks like this:
{
  "fields": {
    "cameras": {
      "Kind": {
        "ListValue": {
          "values": [
            {
              "Kind": {
                "StructValue": {
                  "fields": {
                    "rtsp_urls": {
                      "Kind": {
                        "ListValue": {}
                      }
                    },
                    "manufacturer": {
                      "Kind": {
                        "StringValue": "ONVIF_ICAMERA"
                      }
                    },
                    "model": {
                      "Kind": {
                        "StringValue": "F26C_IR_c3"
                      }
                    },
                    "serial_number": {
                      "Kind": {
                        "StringValue": "EF00000005087E34"
                      }
                    }
                  }
                }
              }
            },
            {
              "Kind": {
                "StructValue": {
                  "fields": {
                    "manufacturer": {
                      "Kind": {
                        "StringValue": "Amcrest"
                      }
                    },
                    "model": {
                      "Kind": {
                        "StringValue": "IP5M-T1179EW-AI-V3"
                      }
                    },
                    "serial_number": {
                      "Kind": {
                        "StringValue": "AMC1083EC3C8118218"
                      }
                    },
                    "rtsp_urls": {
                      "Kind": {
                        "ListValue": {
                          "values": [
                            {
                              "Kind": {
                                "StringValue": "rtsp://admin:admin@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif"
                              }
                            },
                            {
                              "Kind": {
                                "StringValue": "rtsp://admin:admin@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif"
                              }
                            }
                          ]
                        }
                      }
                    }
                  }
                }
              }
            },
            {
              "Kind": {
                "StructValue": {
                  "fields": {
                    "serial_number": {
                      "Kind": {
                        "StringValue": "EF0000000509A87D"
                      }
                    },
                    "rtsp_urls": {
                      "Kind": {
                        "ListValue": {}
                      }
                    },
                    "manufacturer": {
                      "Kind": {
                        "StringValue": "A_ONVIF_CAMERA"
                      }
                    },
                    "model": {
                      "Kind": {
                        "StringValue": "YMA42P_IR_N_AF"
                      }
                    }
                  }
                }
              }
            }
          ]
        }
      }
    }
  }
}

After calling toMap() all those extra keys like "Kind", "StringValue", "ListValue" make it tough to decode.

Q: why use native type? is it because the results are even more difficult to read as raw proto?

Q: why use native type? is it because the results are even more difficult to read as raw proto?

If there was a proto for the results / a result maybe not? 🤔

Clarification: you mean if results wasn't a list of generic pb structs?

Exactly, sorry if my wording off I haven't really worked w/ proto buffers / grpc

Q: why use native type? is it because the results are even more difficult to read as raw proto?

If there was a proto for the results / a result maybe not? 🤔

Clarification: you mean if results wasn't a list of generic pb structs?

Exactly, sorry if my wording is off I haven't really worked w/ proto buffers / grpc

Though to provide more context, in the current app we're working on, when working with a robotConfig it's a bit easier to work with when converted to a map (and it's a pb struct)

The question that is currently blocking this PR is: can we make this even better for mobile?
And it looks like the answer is no unless we change the proto

if results wasn't a list of generic pb structs?

OK with me merging this? @kevin49999 @jckras @njooma

Let's not merge yet unless it's blocking something. There should be a way to fix the nested struct keys

Please see new util handler to unwrap nested "Kind" and "fields" wrappers
See the new output here

Further conversations were had and we are not going forward with a unwrapper https://viaminc.slack.com/archives/C07GTSXSVEC/p1732050452559639?thread_ts=1731688631.621549&cid=C07GTSXSVEC


post_send and post_recv will result in PageFault the first time an address is called on

Due to ODP, post_send and post_recv will result in PageFault the first time an address is called on. This page fault will result in a huge overhead. We can avoid the overhead of post_recv by posting dummy sends to warm up the recv_mrs on the other side. However, post_send may not be easily solved.
As post_send sends messages constructed by user application, user app will allocate new space for their replys and requests. We can reuse the buffers for re-sending the same requests from a buffer. However, this might not be easily done for user app's server side.

Closes the issue since the throughput issue has been solved many months ago.


Correcting grammar for subca ValidationError message for clarity

See issue #656 for explanation. I got stuck on this error message a bit before digging into the code deeper here.

Coverage remained the same at 67.745% when pulling 5463548b1c831bd924c3570f5f09e89048e500fb on neilschelly:punctuation-fix-issue#656 into d67b6c61206d3ccde2af7ebcab2d642d9a340c59 on Netflix:master.

lgtm


Add feature to crop image

Croping functionality for Media manager. Thanks to @shingo0620
Fixed keypress functionality when modal is open.
Only Russian and English translations for buttons for now

Thanks 👍


For each task there should be a task id generated.

It will be really great if each task has a task id generated. It will be really helpful while write creating git commits and pull requests.

Every task already has a unique ID generated.

Can you please share more details as I am not able to understand your difficulty

Yes, I saw the .tkb file that contains Id for each and every task. Instead of having a task if like task-8FtK0Q73PZNBQC5m35hRh it will be really helpful if we can have a task if like 92234. based on the workspace we created. This feature will help us writing commit messages like
T92235: Added files for project abc and after merging the pull request we can easily check the documentation based on the task id.


Update index.markdown

PR 개요 :information_source:
리뷰 요청 사항 :mag_right:

[ ] .
[ ] .

Wiki 링크 :memo:

Wiki:

Screenshot :camera:

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


Super Quick Example fails to run on Node v14

Description
Super quick example fails to run
Expected Result

Actual Result
import { createMachine, interpret } from 'xstate';
^^^^^^^^^
SyntaxError: The requested module 'xstate' does not provide an export named 'interpret'
at ModuleJob._instantiate (internal/modules/esm/module_job.js:92:21)
at async ModuleJob.run (internal/modules/esm/module_job.js:107:20)
at async Loader.import (internal/modules/esm/loader.js:179:24)
steve@Steves-MBP src % node -v
v14.0.0

cc. @Andarist Is this an ESM issue?

I am able to get it going for now with:
import fsm from 'xstate';
const lightMachine = fsm.createMachine(config);

//also as service
const lightService = fsm.interpret(lightMachine);

Duplicate of https://github.com/davidkpiano/xstate/issues/963

@Andarist Is this an ESM issue?

Yes. We currently don't provide enough information for node (through package.json) for it to be able to load our ESM files. The issue is not so simple as it might look like though, comes with some caveats and at this point in time changing it for v4 would be a breaking change for every ESM consumer in node as they would have to change all import statements for XState. The support for modules in node is also still considered as experimental so I don't really think that we should jump into fixing this straight away (especially that - as mentioned - this only looks trivial, we also don't know yet how bundlers will handle conditional exports which are expected to be handled by them)

Closing as duplicate


Changing path visibilty is slow when a lot of paths change state

On AC maps there is a noticeable delay (0.5s) when the visibility state of all neuron paths is changed. This appears to be due to a few things:

A single neuron path can consist of more than one line-string features and the visibility state of each feature has to be changed.
Path state is maintained both in a MapLibre layer and the DeckGL layer even though only one of these layers is visible. This is so the correct path state is used when layers are switched.
MapLibre doesn't have a way of disabling rendering while several features change state to then be redrawn together.
This may also be true of DeckGL, although we do have better low level control of its rendering.

As an example of 1. above, enabling the bolser_12 nerve centreline (on human male), which has the single bolew-unbranched-12 neuron path associated with it, results in 14 features changing state -- 1 feature is the centreline, 13 are the path:
0 {id: 1167, source: 'vector-tiles', sourceLayer: 'whole-human_pathways', children: Array(0)}
1 {id: 7042, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
2 {id: 7043, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
3 {id: 7044, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
4 {id: 7045, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
5 {id: 7046, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
6 {id: 7047, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
7 {id: 7048, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
8 {id: 7049, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
9 {id: 7050, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
10 {id: 7051, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
11 {id: 7052, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
12 {id: 7053, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
13 {id: 7054, source: 'vector-tiles', sourceLayer: 'neural-routes_pathways', children: Array(0)}
14 features changed enabled state...

For the future, maplibre/maplibre-gl-js#4199 should provide a way to control feature visibility (and other styling) without using Map.setFeatureState() and likely be more efficient.


[HOLD] Fix snapshot.get Response

as titled.

need to discuss the handling of outdated test artefacts.


Update manage-alerts-windows-defender-advanced-threat-protection.md

The user has suggested adding the attributes of the rule that are supported while the creation of the new rules in the same document. I have added the required information.
Problem Details: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/2974

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

Joyce please have a look to see what I have done for this PR. Will this
process work?
On Thu, Mar 21, 2019 at 3:36 PM Joyce Y<EMAIL_ADDRESS>wrote:

@JohanFreelancer9 https://github.com/JohanFreelancer9 - kindly do the
copy editor review for this PR. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windows-itpro-docs/pull/3008#issuecomment-475231085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AuUZlT7RdtvdXvre97Cd3Z8mjei_Bu-uks5vY4rvgaJpZM4cBGoH
.

@joinimran - please check again on the copy/edit that I did and merge the new commit if you can. Thank you.

@mjcaparas - can you please assist to check, approve and merge the content for this PR based on issue #2974?
Thank you.


Language stats not available without JavaScript

Description
The language stats inside a repository are not available if JavaScript is disabled.
Clicking the colored bars doesn't bring up the language names and shares, since it relies on a JavaScript function.
Screenshots

Gitea Version
1.17
Can you reproduce the bug on the Gitea demo site?
Yes
Operating System
No response
Browser Version
all

This was always intended to require js. You are welcome to provide a PR that would make this work without JS.
if you disable JS many things in Gitea will not work.


update requirement.txt

This PR updates the python requirement in plugins/anomaly-detection/requirements.txt and also updates the unit test as the version changes in requirement.txt.

/theia-test-e2e


Remove ODH/RHOAI conditional in upgrade test; getNotebookImage is perfectly sufficient

There is extra override for notebook image of not on ODH. This should not be there, because the image selection above already considers ODH/RHOAI.
As a consequence, we use the huge pytorch image on RHOAI, which makes upgrade test run long and be unstable.

CI run passed, merging.


3.0 release notes

Issue: #1046
What I did

Release note proposed structure
Rough draft of release notes

Inspired by:

https://github.com/facebook/react/releases
https://atom.io/releases

What I need

Other notable changes
Discussion on release structure
Suggestion for how to get a formatted list of PRs since last tagged release? => this will get added to the CHANGELOG as well as the release tag

How to test
Browse the formatted release notes HERE

Suggestion for how to get a formatted list of PRs since last tagged release?

I use Lerna's conventional commits feature, it works very nicely.

Suggestion for how to get a formatted list of PRs since last tagged release?

or maybe like this?
https://github.com/storybooks/storybook/pulls?page=1&q=is%3Apr+is%3Aclosed+merged%3A2017-01-15..2017-05-18&utf8=✓

@aaronmcadam conventional-commits works great. but it also requires that we get everybody to adopt that style including PRs from community members.
Somebody also suggested https://github.com/zeit/release, where the person making the release can manually classify each commit. But I guess it does not know about monorepos.
At any rate, it seems like best practices seems to be logging at the commit level. Does this mean we should get smarter about squashing commits and other more serious git usage?
cc @ndelangen @tmeasday @UsulPro

Can we link PR's merged to issues and list those in the CHANGELOG?

I think systems that are based on "hygenic" commits are going to be hard to enforce on a community project unless we want to do a lot of PR rebasing, which sounds like a pain.
I would suggest we follow the process we do for Meteor and Apollo, which is to have a vNEXT section of the changelog, ask people to make PRs against a dev branch and include changes to the changelog in their PR (alongside doc changes too if possible).
So a contributor would add a line to the vNEXT section of the changelog. Then the release process is to merge dev to master, re-label vNEXT as vX.Y.Z, and publish.
If we don't want to use dev we could do a different strategy with the same idea.

@ndelangen @tmeasday I did a quick experiment of trying to pull out merged PR's that specifically referenced commits in the first line of their body. The rationale being that enforcing hygienic commits is probably too much work, but maybe we can do a better job with PRs. Also Github makes it easy for us to edit PR titles to make them more descriptive.
Here is the output of that experiment:
#1043 Update README after repo-restructure (#1042)
#1038 Deprecate builtin addons (#1017)
#1025 Deprecate built-in addons (#1017)
#1024 Updated issue triage guidelines (#733)
#1021 Add addonlinks repo (#1016)
#996 refactor: change NPM organisation from kadira to storybook (#773)
#989 Add typescript definition to addon-notes (#953)
#961 #959 add a max-height and center element with alignItems: center (#959)

Let me know if you think this ideas merit. If so I can pursue it further. If not, I'm tempted to go with @tmeasday 's suggestion of a manually-curated changelog, but enforced in PRs.

referenced commits

Do you mean "referenced issues"?
I can get behind the idea of updating the PR title instead of changing a changelog file. If it's reliable it's a great middle ground.

@tmeasday Sorry, yes referenced issue. I updated my comment.
OK, that's encouraging. I'll take a more complete pass at this today and we can at least give it a shot. If it turns out to be a pain, we can revert to a manual method later. Thanks!

This is the format generated by https://github.com/ahmdigital/github-publish-release:
- Updated issue triage guidelines #1024 (by @shilman)
- Updated dead getstorybook.io links to storybooks.js.org #988 (by @zjeraar)
- Update README after repo-restructure #1043 (by @shilman)
- Update links in PRs section of CONTRIBUTING.md #992 (by @UsulPro)
- Update jest to the latest version 🚀 #998 (by @greenkeeper[bot])
- Switch back to non-fork of react-inspector #1026 (by @ndelangen)
- Remove text transform uppercase for knob labels #991 (by @cnandreu)
- refactor: change NPM organisation from kadira to storybook #996 (by @aaronmcadam)
- MOVE & RENAME and storyshots && CHANGE “React Storybook” > “Storybook” #1044 (by @ndelangen)
- Fixing link #974 (by @she-dev)
- Fixes for types for knobs `number` #1001 (by @marcfallows)
- Fix typo in README #977 (by @rixth)
- Fix linting in addon-info #980 (by @UsulPro)
- First pass at update the contribution instructions #982 (by @tmeasday)
- Do not ignore story.js in prepublish #973 (by @subpopular)
- Deprecate builtin addons #1038 (by @shilman)
- Deprecate built-in addons #1025 (by @shilman)
- Dependency updates #1008 (by @ndelangen)
- CHANGE folder structure && CHANGE package-names #1031 (by @ndelangen)
- addon-info: make the info overlay be fixed  #914 (by @Kiwka)
- Add typescript definition to addon-notes #989 (by @fabien0102)
- Add propTablesExclude option #924 (by @elisherer)
- Add addonlinks repo #1021 (by @ndelangen)

Here's the latest, joining PRs and issues per @ndelangen 's suggestion.

### CLOSED issues with PRs

- #404 Images gets extra height when displayed in storybook #974
- #733 Issue triage guidelines #1024
- #773 Change npm organisation from kadira to storybook #996
- #959 [BUG] Style: Title of Panels #961
- #1016 Restore storybook-addon-links #1021
- #1017 Deprecate addon-links and addon-actions as "built-in addons" #1038,#1025
- #1042 Update README #1043

### OPEN issues with PRs

- #953 Typescript compatibility #989

### PRs without issues

- #1044 MOVE & RENAME and storyshots && CHANGE “React Storybook” > “Storybook”
- #1026 Switch back to non-fork of react-inspector
- #1008 Dependency updates
- #1001 Fixes for types for knobs `number`
- #998 Update jest to the latest version 🚀
- #997 Update eslint-plugin-jest to the latest version 🚀
- #992 Update links in PRs section of CONTRIBUTING.md
- #991 Remove text transform uppercase for knob labels
- #988 Updated dead getstorybook.io links to storybooks.js.org
- #982 First pass at update the contribution instructions
- #980 Fix linting in addon-info
- #977 Fix typo in README
- #975 support the react 16 alpha for react-native lib
- #973 Do not ignore story.js in prepublish
- #972 FIX for test-cra was breaking the build
- #969 Update lerna to the latest version 🚀
- #967 Fix error when component has object as props
- #965 FIX webpack overriding && CLEANUP && ADD example
- #956 CHANGE to use react-split-view 0.1.63 over the fork
- #955 Add splitpane repo
- #929 add description field from __docgenInfo for prop table for info plugin

I think we're on the right track.
If we could do things like extract labels from issues and do something with that in the CHANGELOG, that could be very useful? For example to categorise per addon / app?

I've always asked (or automated asking) contributors to add CHANGELOG entries from a user's perspective. Trying to automate it from PRs and commits has never worked for me as their audience is different (targeted at devs)

I think making PR titles more "user focused" is ok even if commits remain
developer focused?
On Sat, 20 May 2017 at 12:03 am, Orta<EMAIL_ADDRESS>wrote:

I've always asked (or automated asking http://danger.systems)
contributors to add CHANGELOG entries
https://github.com/danger/danger-js/blob/master/changelog.md from a
user's perspective. Trying to automate it from PRs and commits has never
worked for me as their audience is different (targeted at devs)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/storybooks/storybook/pull/1047#issuecomment-302711257,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIFygRipsvWH-Njfm2J67cmxIiK_TbUks5r7aETgaJpZM4NeEj8
.

Nice @orta , love the concept of Danger CI. That's really cool.
I'm going to propose that we run with manual release summaries and edited PR titles:

For major releases like 3.0.0, the manual summary might take some work and link to blog posts etc., and there is a large backlog of noisy PRs that are all grouped and collapsed.
For minor releases, the release may only consist of a list of the merged PRs. It's up to the person doing the release how they want to edit the CHANGELOG.

The rationale is that policing things at the commit level is too much overhead, but moving forward we should be able to enforce sensibly-named PRs that are user-centric.
It's an experiment, and we can fall back to the tried-and-true method of manually editing the CHANGELOG after a few releases if it doesn't prove out.

Best practices for CHANGELOGS for anybody who's interested: http://keepachangelog.com/en/0.3.0/

@ndelangen latest version with the more granular grouping:

Bug Fixes

#53 Left menu goes blank when switching items #991
#1016 Restore storybook-addon-links #1021
#1042 Update README #1043
#1052 [3.0.0alpha] build-storybook no longer supports relative paths #1058

Other

#733 Issue triage guidelines #1024

Maintenance

#759 Deprecation warnings & discontinued addon support for React 16 #1008
#773 Change npm organisation from kadira to storybook #996

Open Issues

#953 Typescript compatibility #989

Addons

#1017 Deprecate addon-links and addon-actions as "built-in addons" #1038,#1025

PRs without issues

#1074 Update link to Storyshots addon
#1065 Activating Open Collective
#1064 Removed > typo in Info prop table header
#1063 chore(jest): update to v20's default configuration file
#1062 Upgraded webpack PostCSS plugin definition
#1049 fix(codemod): update for new package names
#1044 MOVE & RENAME and storyshots && CHANGE “React Storybook” > “Storybook”
#1030 Added component description from __docgenInfo, Added the ability to get the PropType from __docgenInfo for prop table, Fixed an issue with PropVal rendering an object
#1026 Switch back to non-fork of react-inspector
#1001 Fixes for types for knobs number
#998 Update jest to the latest version 🚀
#992 Update links in PRs section of CONTRIBUTING.md
#988 Updated dead getstorybook.io links to storybooks.js.org
#982 First pass at update the contribution instructions
#980 Fix linting in addon-info
#977 Fix typo in README
#974 Fixing link
#973 Do not ignore story.js in prepublish

@ndelangen i moved the CHANGELOG to the root. let me know if you think i should make a copy instead.


CH02: Use FunctionTransformer instead of self-defined CombinedAttributesAdder

Closes #349
To avoid unrelated diff, I modified the notebook directly, made a copy of the new notebook and ran that copy to ensure that we get same results.
I removed CombinedAttributesAdder because I guess it's not user-friendly.

hi
why should we use a user defined class or FunctionTransformer class? is'nt it possible to use the function @qinhanmin2014 defined in a pipline?


Strictly typed functions and unicode to wstring conversions

C++ functions bound to lua expect strict types and arguments count, otherwise cause luaL_error, example:

bad argument #-1 to 'typeSafeFunc' (string expected, got number)
expected parameters count: 3

Lua should be compiled as C++ otherwise it will long jump instead of throwing an exception, which may cause memory leaks and undefined behavior
Lua unicode strings are converted to wstrings when C++ function expects wstring. This might be desired when code is written for Win32
C++ functions can throw lua_nil excpetion and Lua code will get nil return value, like this:

int cpp_func_returning_int()
{
...
   if (!some_condition)
      throw lua_nil;

   return value;
}

Added new unit test
Added specialization for raw Lua C functions with int(lua_State*) signature

Note, the code is raw and tested only with MSVC
Not sure if these features are really needed in master branch of luacppinterface. There could be 2 different registrations of functions, like:
Lua.CreateFunction<int(int)>(func);
Lua.CreateStrictFunction<int(int)>(strict_func);

Hey, thanks for the pull request. Travis does not seem so happy about it though...

Hi, I've fixed type being used as a value issue. Windows build now fails with linkage errors caused by name mangling issue, MSVC project settings should be updated, i'll do that later this week. GCC build seems to fail because UNREFERENCED_PARAMETR macro is not defined, it's a macro that is defined in Windows headers, well it's fixable.

Apparently the build still isn't fixed. looks like pip --use-mirrors is dying

if you try pull the main repo and push to yours you should get --use-mirrors fix in this pull request

well, looks like a different error now.

Yup, looking into it. Just out of curiosity, can I submit a change directly to Travis from my local machine, without committing a change into the repository?
The thing is that I tested this with MSVC, but GCC and Clang throw different errors, I can test it locally with Cygwin + GCC though, just need to install it.

Commit to travis? Not that I know of. I know what you mean though

Yeah, in the company where I'm working we call it "virtual build".  Looks like the last issue is: luaerror.h: error: extra qualification . Gonna fix it tomorrow.

This set of changes is getting quite large. Can you please move it into a branch on your repository so I can pull the topic branch and we can work on it together? I have win32, linux and mac machines here so I can test everything locally and maintain the non-win32 stuff easier

Sure, the changes are in my fork: https://github.com/ziab/luacppinterface
I'll also fix the issues you pointed above.
Closing the pull request.


Cannot sort containers by "health"

When attempting to sort containers by "health" it doesn't work.

ping @eoghanino

Fixed in 28dfcbb


PassManager and compiler test framework updates

adds the discussed phase and occurence features to the PassManager
refactors the test framework into a monadic style one that is actually reasonable to use compared to the old one.

Merged manually


Restructuring spring 2022

Restructuring to de-clutter, and clarify which parts are relevant to which groups of people.
These changes have been Marketing and Sales Manager approved.

This is an overhaul, so if one wants to check it out, mkdocs serve is almost a necessity.

Formal approval by @erenman? :smile:

Closes #319


Collect the dependency info and process them outside of the libIndexStore callback

This is because processing populates the database and C++ exceptions can be thrown; libIndexStore builds with -fno-exceptions so we cannot be throwing C++ exceptions from inside its frames.
rdar://60611975

@swift-ci Please test


Recommendations

hey!!  i recommend addin a feature that replaces pronouns so you can replace she/her with they/them or he/him ect etc! it would be very helpful!

Hmmmmmm... not sure I'm completely on-board with this suggestion, although I see what you're getting at. I'm just thinking about reading like an article or something, and every person on the page is getting misgendered because the extension is changing all the pronouns opposed to just pronouns that are referring to you


Added support for Key Rotation.

Fixes #22993.
Added tests and code snippets. Also updated documentation for Key Vault Keys clients and code snippets.
Will add quickstart samples in a future PR.

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here


Add vectorization to the par_vec (aka par_unseq) implementations of the parallel algorithms

The par_vec (aka par_unseq) policy allows interleaving of element access functions, e.g. it is safe to the iterations of the algorithm.
Explicit engagement of compiler vectorizers through pragmas is probably the best way to ensure this occurs (e.g. #pragma simd, #pragma omp simd).
I will probably take a look into doing this myself while preparing my CppCon talk on parallel algorithms.

@brycelelbach @hkaiser Could you please add a project description here https://github.com/STEllAR-GROUP/hpx/wiki/GSoC-2017-Project-Ideas

I am interested in working on this project. I have seen that in the previous PRs we have added openMP pragmas for vectorization and parallelisation of a loop. Can someone guide me on how I can start out with working on this issue?

I am interested in working on this project. I have seen that in the previous PRs we have added openMP pragmas for vectorization and parallelisation of a loop. Can someone guide me on how I can start out with working on this issue?

Yes, we have implemented this for the first batch of algorithms. There are still algorithms left that have not been touched, though. Also, we would need a thorough performance analysis of the existing implementation, combined with improvements, if needed.

par_unseq implementation for algorithms

[x]  adjacent_difference
[ ]  inner_product  does it support any execution policy, could not find doc. Do we Implement using transform reduce?
[x]  adjacent_find
[x]  all_of any_of none_of

[ ]  copy copy_if copy_n
[ ]  move
[ ]  count count_if
[ ]  equal mismatch
[ ]  exclusive_scan inclusive_scan
[ ]  reduce transform
[ ]  fill fill_n
[ ]  find find_end find_first_of find_if find_if_not
[x]  for_each for_each_n
[ ]  generate generate_n
[ ]  is_heap is_heap_until
[ ]  is_partitioned is_sorted is_sorted_until
[ ]  lexicographical_compare
[ ]  max_element min_element minmax_element
[ ]  make_heap
[ ]  partial_sort
[ ]  partial_sort_copy nth_element
[ ]  sort
[ ]  stable_sort
[ ]  partition
[ ]  partition_copy
[ ]  stable_partition
[ ]  remove remove_if
[ ]  remove_copy remove_copy_if
[ ]  replace replace_copy replace_copy_if replace_if
[ ]  reverse reverse_copy
[ ]  rotate rotate_copy
[ ]  search search_n
[ ]  set_difference set_intersection set_symmetric_difference set_union includes
[ ]  inplace_merge
[ ]  merge
[ ]  swap_ranges
[ ]  uninitialized_copy uninitialized_copy_n
[ ]  uninitialized_fill uninitialized_fill_n
[ ]  uninitialized_default_construct uninitialized_default_construct_n
[ ]  uninitialized_value_construct uninitialized_value_construct_n
[ ]  uninitialized_move uninitialized_move_n
[ ]  destroy destroy_n
[ ]  unique
[ ]  unique_copy
[ ]  transform_reduce
[ ]  transform_exclusive_scan transform_inclusive_scan
[ ]  shift_left shift_right
[ ]  starts_with ends_with

Hello @hkaiser , I am interest in this topic on gsoc24 ,I have a qeustion.
Is this restricted to only use the #pragma omp simd to vectorize or using something like __m128d, __m256d, some SIMD instructions are unreadable.

Hello @hkaiser , I am interest in this topic on gsoc24 ,I have a qeustion. Is this restricted to only use the #pragma omp simd to vectorize or using something like __m128d, __m256d, some SIMD instructions are unreadable.

Everything is possible, I guess - as long as it is portable across architectures (beyond x86), at least in the long run.


How to dynamic add computed property

Vue.js version
1.0.23
Reproduction Link
https://vuejs.org/examples/firebase.html
Steps to reproduce
What is Expected?
From the code, the computed property 'validation' will cacl when all data properties changed. If we add 'validation_name', 'validation_email' as computed property can solve the problem.
Now the problem is, how can I dynamic add 'computed property' without hard code the 'validation_name' property? I tryed vm.$set method, but it only create a data propery.
What is actually happening?

Please make sure to read the Issue Reporting Guidelines before opening new issues. The issue list only accepts bug reports and feature requests. Questions should be posted to the Gitter chat room,  forum or StackOverflow. Thanks.


Add support for sbt 2

See

https://github.com/sbt/sbt/issues/7698
sbt 2.x plugin migration wiki page with list of progress
https://github.com/playframework/playframework/pull/12897

We can't really do much at this point but to wait for other plugins to be released first that twirl depends on:

[ ] ch.epfl.scala:sbt-bloop_sbt2.0.0-M2_3
[ ] com.eed3si9n:sbt-buildinfo_sbt2.0.0-M2_3
[ ] com.github.sbt:sbt-maven-plugin_sbt2.0.0-M2_3
[ ] com.typesafe:sbt-mima-plugin_sbt2.0.0-M2_3
[ ] org.scala-js:sbt-scalajs_sbt2.0.0-M2_3
[ ] org.portable-scala:sbt-scalajs-crossproject_sbt2.0.0-M2_3
[ ] com.lightbend.sbt:sbt-java-formatter_sbt2.0.0-M2_3
[ ] de.heikoseeberger:sbt-header_sbt2.0.0-M2_3
[ ] com.github.sbt:sbt-ci-release_sbt2.0.0-M2_3
[ ] org.scalameta:sbt-scalafmt_sbt2.0.0-M2_3

Hmm.. seems I was to fast. We can of course already cross publish the twirl plugin with Scala 3/sbt 2, even if running sbt 1 with missing sbt 2 plugins:
https://www.scala-sbt.org/2.x/docs/en/changes/migrating-from-sbt-1.x.html#cross-building-sbt-plugin-with-sbt-1x
Makes total sense.

See #840


Activity Data: Determine if popups on activity points

currently no popup. Clicks open associated entrance detail panel

We changed this to show the activity name in a pop up. Possibly will refine further.

Closing for now


Search tabs work only in current tab not in other obsidian windows

Search tabs work only in current tab not in other obsidian windows. Version 0.5.2

Thanks for reporting this issue. I'm aware of it and are working on a fix in Issue #24, but it's proving to be a bit challenging. Just moment, please.

@sql99
I have resolved this issue in version v0.6.0 (#27)

Thank you! Work Great!


stress test

New Expended Stress Test for ble_hal
Description
This expends the capabilities of ble_hal stress test
Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

/bot run checks


How to push new data into the graph on the client side?

Hello.
Could anyone help me to understand how to push ohlcv data into the empty chart right from browser?
There is no way from me to get data from vue server, so I want somehow to create a json in browser to push data for processing into the chart
Thank you
P.S. I want to compile tradingvue lib into pure js and use it in browser when page loads

@jokaorgua You can using datacube update real time data. View code example here https://github.com/tvjsx/trading-vue-js/blob/master/test/tests/DataHelper.vue

Thanks for the tip. Im already using tue DataCube in server vue.
I’m more interested in solution for already compiled js code. Something like chart.dc.update but from js on the page


Allow for user-defined comparison metrics

Description
Right now a generated result for a model is compared to a reference result up user-defined precision. This is quite restrictive.
Goal
Instead, users should be able to select from

some predefined metrics like max-norm; euclidean distance of result vectors, i.e. $\ell^2$; $L^2$-norm
user-defined result metrics passed as a function handle

This requires the reference result and the actual result to have data on the union of their respective timestamps.


tapdb: add minimalistic test framework for testing DB migrations

This is an attempt at solving https://github.com/lightninglabs/taproot-assets/issues/694.
There are many ways to solve this, and this is IMO the most easy to implement one.
So this is mainly a proposal to get the discussion started. If we feel like we need something more involved, we can discuss based on this example code.
I mainly had this PR in mind when coming up with the design for this: https://github.com/lightninglabs/taproot-assets/pull/684
There we need to have a way to insert existing data into the DB before applying the latest migration.
Here are the pros/cons of the current approach:
Pros:

Simple to implement, understand, use and maintain
Should allow us to fully test data manipulation migrations
No need to carry along multiple versions of Golang model code
No impact on production code or run time

Cons:

Not very easy to test schema manipulation migrations, since Golang model is always the very latest version
If we need to test changes to the actual schema, we need to do it with raw SQL queries
Need to manually create test data SQL code

Super cool!

e.g if we already have 10 migrations in the DB and a new PR is trying to add n.11, are we gonna test that migration against all possible states a tapd could be upgrading from?

The idea is that we have a way to test migrations that do data manipulations. Those are quite hard to test with just a unit test that looks at the state after all migrations have been applied. One of those PRs is https://github.com/lightninglabs/taproot-assets/pull/684 (which was taken as the inspiring PR to influence some of the design in this PR).


Fix SQL parsing for MVT provider

Make ID field optional
Fix geometry sniffing for MVT queries
Fix handling MVT provider SQL when using (SELECT ...) as alias queries

@johngian it looks like this PR is failing the test suite: https://github.com/go-spatial/tegola/pull/744/checks?check_run_id=2015097575. I can help look into this if that would be helpful.

Pull Request Test Coverage Report for Build cbedc67ec-PR-744

35 of 42 (83.33%)  changed or added relevant lines in 3 files are covered.
7 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.02%) to 45.673%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

provider/postgis/postgis.go
13
16
81.25%

provider/postgis/util.go
16
20
80.0%

Files with Coverage Reduction
New Missed Lines
%

server/viewer.go
3
61.54%

server/server.go
4
83.33%

Totals

Change from base Build 8e40cafbb:
0.02%

Covered Lines:
5409

Relevant Lines:
11843

💛  - Coveralls


salud IsHealthy using wrong radius

Context
v2.1.0 (and earlier)
Summary
Several of my sepolia testnet nodes are not participating in the storage compensation rounds.  All of these nodes have storage radius 4 while the remainder of the swarm has increased to radius 5.   Radius 4 is CORRECT for these lesser-populated neighborhoods.
The nodes are logging:
"time"="2024-05-29 07:22:14.260110" "level"="info" "logger"="node/storageincentives" "msg"="skipping round because node is unhealhy" "round"=39473

and
"time"="2024-05-29 07:56:05.200700" "level"="warning" "logger"="node/salud" "msg"="node is unhealthy due to storage radius discrepency" "self_radius"=4 "network_radius"=5

Expected behavior
If a node has the same radius as its neighborhood peers, then it must be healthy, regardless of what the radius is in other neighborhoods.
Actual behavior
Because other neighborhoods in the swarm have increased to radius 5, the lesser-populated neighborhoods are not participating in the storage compensation.
Steps to reproduce
Just fire up a node in one of the lesser-populated, radius 4 sepolia testnet neighborhoods.  Specifically (at this point in time):
0x480, 0xb80, 0xc80, 0xd00, 0xdef, 0xe80
Possible solution
Use a neighborhood radius calculation for health rather than the overall swarm which may be different.
Here's the /status/peers output of one of the affected nodes.
4635-status-peers.txt

Here is the /status output for each of the radius 4 nodes/neighborhoods:
  "peer": "480...",
  "proximity": 0,
  "beeMode": "full",
  "reserveSize": 4193860,
  "reserveSizeWithinRadius": 3426466,
  "pullsyncRate": 0,
  "storageRadius": 4,
  "connectedPeers": 41,
  "neighborhoodSize": 0,
  "batchCommitment":<PHONE_NUMBER>,
  "isReachable": true

  "peer": "b80...",
  "proximity": 0,
  "beeMode": "full",
  "reserveSize": 4193515,
  "reserveSizeWithinRadius": 3430038,
  "pullsyncRate": 0,
  "storageRadius": 4,
  "connectedPeers": 41,
  "neighborhoodSize": 0,
  "batchCommitment":<PHONE_NUMBER>,
  "isReachable": true

  "peer": "c80...",
  "proximity": 0,
  "beeMode": "full",
  "reserveSize": 4176960,
  "reserveSizeWithinRadius": 3810215,
  "pullsyncRate": 0,
  "storageRadius": 4,
  "connectedPeers": 41,
  "neighborhoodSize": 0,
  "batchCommitment":<PHONE_NUMBER>,
  "isReachable": true

  "peer": "d00...",
  "proximity": 0,
  "beeMode": "full",
  "reserveSize": 4093335,
  "reserveSizeWithinRadius": 4043948,
  "pullsyncRate": 0,
  "storageRadius": 4,
  "connectedPeers": 41,
  "neighborhoodSize": 2,
  "batchCommitment":<PHONE_NUMBER>,
  "isReachable": true

  "peer": "def...
  "proximity": 0,
  "beeMode": "full",
  "reserveSize": 4159288,
  "reserveSizeWithinRadius": 4043952,
  "pullsyncRate": 0,
  "storageRadius": 4,
  "connectedPeers": 37,
  "neighborhoodSize": 2,
  "batchCommitment":<PHONE_NUMBER>,
  "isReachable": true

  "peer": "e80...",
  "proximity": 0,
  "beeMode": "full",
  "reserveSize": 4181723,
  "reserveSizeWithinRadius": 3733244,
  "pullsyncRate": 0,
  "storageRadius": 4,
  "connectedPeers": 41,
  "neighborhoodSize": 0,
  "batchCommitment":<PHONE_NUMBER>,
  "isReachable": true

If you compare those reserveSizeWithinRadius to the radius 5 nodes in the attached /status/peers file, you'll notice that the radius 4 have almost full reserves while the radius 5 nodes are only about 1/2 full; consistent with a recent increase of radius that didn't land uniformly across the swarm.
If this can happen in testnet and sustain for several days (as it has, until I noticed), then it can certainly happen in mainnet and be missed across the 1,024, 2,048, or even 4,096 neighborhoods.

Made an improvement regarding this issue in PR-4721 that we think could help solve this issue.
Using neighbourhood radius for calculation of node radius in that neighbourhood is not reliable. Like described in the PR, comparing node radius to neighbourhood radius could lead to issues and also to attacks from bad intended actors in that neighbourhood.
Also regarding peers radius comparison, that comparison is the way it is to have an acceptable tolerance for those peers.


Nexus fix: Ownable Validator module implementation + tests

PR-Codex overview
The focus of this PR is to replace the toHolder utility with toSigner across multiple files and update related function parameters.
Detailed summary

Replaced toHolder with toSigner utility function
Updated function parameters in various modules to use signer instead of holder
Added a new dependency @rhinestone/module-sdk to the package.json file

The following files were skipped due to too many changes: src/sdk/modules/index.ts, src/sdk/clients/decorators/erc7579/supportsExecutionMode.ts, src/test/executables.js, src/sdk/modules/validators/K1ValidatorModule.ts, src/test/callDatas.js.map, src/sdk/clients/createNexusClient.ts, src/sdk/clients/decorators/erc7579/index.ts, scripts/fetch:deployment.ts, src/sdk/account/utils/toHolder.ts, src/test/__contracts/mockAddresses.ts, src/sdk/modules/base/BaseModule.ts, src/sdk/modules/base/BaseValidationModule.ts, src/sdk/clients/createNexusClient.test.ts, src/sdk/clients/decorators/erc7579/erc7579.decorators.test.ts, src/sdk/clients/decorators/erc7579/getPreviousModule.ts, src/sdk/modules/utils/Types.ts, src/sdk/modules/validators/k1Validator.test.ts, src/test/testUtils.ts, src/sdk/account/toNexusAccount.ts, src/sdk/modules/validators/ownableValidator.test.ts, src/sdk/modules/executors/OwnableExecutor.ts, src/test/testUtils.js.map, src/sdk/modules/validators/OwnableValidator.ts, src/test/testUtils.js, src/test/callDatas.js

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

conflicts need to be resolved.

conflicts to be resolved

ok new conflicts here

I've not given this more that a moments thought, but something like...

to
modules >
smartSessions >
abi
constants
installation
index
usage
decorators
ownables >
abi
constants
installation
index
usage
decorators

checks are failing.

I've not given this more that a moments thought, but something like...

`to`
modules >
  smartSessions >
    abi
    constants
    installation
    index
    usage
    decorators
  ownables >
    abi
    constants
    installation
    index
    usage
    decorators

folder for each module is ok. most of them will be validators though for which we precisely need these classes because of default and active validator concept.

getActiveValidationModule

We don't need this, instead we will be migrating to use rhinestone's sdk for module.


tooltip

how can i show node info via tootip on hover on node

Hi @MohandesaliRahnema,
Thank you for your question.
v-network-graph does not have the ability to display Tooltips. However, it is possible to realize Tooltip by using the features of events and coordinate translation.
I have created a new example. Please see below:
https://dash14.github.io/v-network-graph/examples/event.html#tooltip
Please note that the latest version (v0.3.8) is required to use the coordinate translation feature.

I'll close this issue for now.
If you have any other questions, please open a new issue.

thank you a lot
it is very useful future
On Sat, Nov 27, 2021 at 3:53 PM dash14 @.***> wrote:

I'll close this issue for now.
If you have any other questions, please open a new issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dash14/v-network-graph/issues/19#issuecomment-980564667,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAUS5VVGGHL3ANUUTXBCWTUODEUZANCNFSM5INSUPFQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Why is the DUT output video cropped

Why is the DUT output video cropped,Is it because of the model?How should this problem be solved?

你可以在dutstabilizer.py的生成视频的函数里面，输出未裁剪的视频帧，但是这个模型推理会产生黑框，我建议还是对视频进行裁剪。黑边的补偿，我看到作者分享一篇边界外推方法，但是目前还未上传项目代码，我觉得，你可以尝试用生成对抗网络来对边界进行预测生成。

Why is the DUT output video cropped,Is it because of the model?How should this problem be solved?

You can output uncropped video frames in dutstabilizer.py's function to generate video, but this model will generate black boxes, so I recommend cropping the video. Black edge compensation, I saw the author share a boundary extrapolation method, but has not uploaded the project code, I think, you can try to use generative adversarial network to predict the boundary generation.

Thank you very much for your reply！ I have one more question to ask. I set up the code environment according to the readme.file, but when I ran it, I got an error: RuntimeError: cuDNN error: CUDNN_STATUS_EXECUTION_FAILED。What is the reason for this problem?

Thank you very much for your reply！ I have one more question to ask. I set up the code environment according to the readme.file, but when I ran it, I got an error: RuntimeError: cuDNN error: CUDNN_STATUS_EXECUTION_FAILED。What is the reason for this problem?

I guess it may be caused by the mismatch between your cuda and pytorch. Are you running code on Ubuntu? I haven't tried this before? Because I was configured and successfully run under the Windows 10 environment. Can you show me your condo list ，so that I can the diffrence between your configuration and mine?

Thank you for reminding me! Now I also debug code in the windows environment. After investigation, I found that it was caused by insufficient video memory，Maybe I need to change the size of batchsize. Do you know how to modify the batchsize in dut?In addition, I wonder if it is convenient for you to leave your email address so that I can consult you more conveniently.

Thank you for reminding me! Now I also debug code in the windows environment. After investigation, I found that it was caused by insufficient video memory，Maybe I need to change the size of batchsize. Do you know how to modify the batchsize in dut?In addition, I wonder if it is convenient for you to leave your email address so that I can consult you more conveniently.

hello,my email is<EMAIL_ADDRESS>

Thank you for reminding me! Now I also debug code in the windows environment. After investigation, I found that it was caused by insufficient video memory，Maybe I need to change the size of batchsize. Do you know how to modify the batchsize in dut?In addition, I wonder if it is convenient for you to leave your email address so that I can consult you more conveniently.

you can reduce your length of input video，out of memory can be slolved.The batch size can adjusted in config.but I remember it is 1.

Thank you for reminding me! Now I also debug code in the windows environment. After investigation, I found that it was caused by insufficient video memory，Maybe I need to change the size of batchsize. Do you know how to modify the batchsize in dut?In addition, I wonder if it is convenient for you to leave your email address so that I can consult you more conveniently.

you can reduce your length of input video，out of memory can be slolved.The batch size can adjusted in config.but I remember it is 1.

Do you have any code for evaluation metrics?


Speedup dev build.

This PR speeds up developer build (one with pinot-fastdev profile enabled) by skipping compression and e.g. npm validation.
Following build command on my desktop :
mvn -DskipTests=true --also-make   --projects pinot-distribution package -P'pinot-fastdev,bin-dist' -T1C
takes:
in master branch - 3 minutes
in this branch - 2 minutes.
It looks possible to shave another 30 seconds by disabling compression in shade plugin but that'd require changing plugin code.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (badd7b0).
Report is 1176 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (badd7b0). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (badd7b0)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14210       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Wrong warning while the output path is outside the extension folder.

Hi.
I have a project structure like this:
c:\code\⬛⬛⬛\vscode-extension  # root of the workspace/reporoot
c:\code\⬛⬛⬛\vscode-extension\src\extension # root of the vscode extension
c:\code\⬛⬛⬛\vscode-extension\artifacts\extension # output of webpack

my configs:
c:\code\⬛⬛⬛\vscode-extension\src\extension\tsconfig.json:
{
// ...
  "outDir": "../../artifacts/obj/extension/tsc/",
}

c:\code\⬛⬛⬛\vscode-extension\src\extension\package.json:
{
// ...
"main": "../../artifacts/extension/extension.js",
}

And I've got warning like this:
[c:\code\⬛⬛⬛\vscode-extension\src\extension\]: Expected `main` (c:\code\⬛⬛⬛\vscode-extension\artifacts\extension\extension.js) to be included inside extension's folder (c:\code\⬛⬛⬛\vscode-extension\src\extension\). This might make the extension non-portable.

As you can see the main is not included inside extension's folder.
The problem is here:
https://github.com/microsoft/vscode/blob/e2458c2d70552806aa834c87019cb2a70735a183/src/vs/workbench/services/extensions/node/extensionPoints.ts#L407-L409

@vchirikov In a vscode extension, the package.json must be situated at the root of the extension. That is why resources referenced from package.json must be in the same folder as package.json. Please see https://code.visualstudio.com/api/get-started/extension-anatomy#extension-file-structure

@vchirikov In a vscode extension, the package.json must be situated at the root of the extension. That is why resources referenced from package.json must be in the same folder as package.json. Please see https://code.visualstudio.com/api/get-started/extension-anatomy#extension-file-structure

@alexdima
I made repro for this issue. This is not a question and package.json is placed at the root of the extension. I've made a repro for you, please check it.
https://github.com/vchirikov/vscode-bug-repro

@alexdima
I made repro for this issue. This is not a question and package.json is placed at the root of the extension. I've made a repro for you, please check it.
https://github.com/vchirikov/vscode-bug-repro

@vchirikov What you desire is not possible. package.json must be at the root of the extension. It is not allowed to point to files outside of the extension folder. I have pointed you to documentation which clearly explains this. There are also yo generators that we maintain that you can use to scaffold a valid vscode extension.

@vchirikov What you desire is not possible. package.json must be at the root of the extension. It is not allowed to point to files outside of the extension folder. I have pointed you to documentation which clearly explains this. There are also yo generators that we maintain that you can use to scaffold a valid vscode extension.

package.json must be at the root of the extension

It is. I only changed the output path to the upper directory.

I have pointed you to documentation which clearly explains this

Let's check the docs:

main: The extension entry point.

no, it is not "clearly explains" that main should points ONLY in a subfolder of the extension's source root (where package.json is placed and where --extensionDevelopmentPath points).
moreover, everything works fine, only this annoying warning appears.

package.json must be at the root of the extension

It is. I only changed the output path to the upper directory.

I have pointed you to documentation which clearly explains this

Let's check the docs:

main: The extension entry point.

no, it is not "clearly explains" that main should points ONLY in a subfolder of the extension's source root (where package.json is placed and where --extensionDevelopmentPath points).
moreover, everything works fine, only this annoying warning appears.

@vchirikov That warning is there to help you when you try to package the extension and presumably publish it to the marketplace. As part of packaging for the marketplace, only the extension folder is packaged and any other files on your hard disk will not be packaged. Such a package (which references missing files) will not work correctly. So the warning is there to let you know that although this works, this is not a good idea because the extension will not be portable.

@vchirikov That warning is there to help you when you try to package the extension and presumably publish it to the marketplace. As part of packaging for the marketplace, only the extension folder is packaged and any other files on your hard disk will not be packaged. Such a package (which references missing files) will not work correctly. So the warning is there to let you know that although this works, this is not a good idea because the extension will not be portable.

Yep, vsce doesn't work when the artifacts output folder is higher than package.json.

Yep, vsce doesn't work when the artifacts output folder is higher than package.json.


Support PHP 7.1

Before thinking about other stuff here, we should have PHP 7.1 "support".
(because we have that already in the other repos, and this is supposed to be a template)

Absolutely


Please Update Vuejs to 2.1.3

Please Update this gem to Vuejs library version 2.1.3.

can you send a pull request with the update?


Switch to hyper-rustls

By using hyper-rustls we reduce the amount of native dependencies the developers and final users of the application will have to have on their system. However hyper-rustls uses some architecture specific ASM, so we can't use it on some systems, so we fall back to hyper-tls there.
Resolves #10

Why is there no CI here?!


Added optional NavigationTransitionInfo parameter to NavigationService.GoBack()

#1085

And should we do Forward() before we wrap this up?

the built in Frame.GoForward() does not take NavigationTransitionInfo as an argument though


Add support for CWE field in vulnerability proto message

Currently we only create a note for a given CVE where the note name is the CVE. There are cases when a particular CVE can have one or more CWEs eg: CVE-2021-39139  has CWE CWE-502 & CWE-434 and one CWE can be for multiple CVEs.
Ref: CVE-2021-39139
The latter case can be covered by creating each Note entry for each CVE & having a field within the detail of the note kind which identifies the CWE associated for that CVE.
Since there is a correlation between CVE & CWE creating a different note for each CWE might not be the solution as previously recommended. I would like to propose adding a new field in the vulnerability proto message here for repeated CWE which can then eventually be trickled down to Note/Occurrence.
Please let me know your thoughts & if any alternate approach than the one suggested above.
Thanks for taking a look.

@aysylu @nms2140 Any thoughts?

I think this is a good idea. Would you like to create a PR?

Thanks. Yes I will raise a PR with the above fix.

@hkadakia sounds good re adding a new field. Should the field be on a Detail or top-level Vulnerability? If different CWEs apply depending on the OS distro, then per-Detail is the best place to do this.

AFAIK, CWEs are not OS distro dependent and are related to high level CVE/vulnerability. I think adding the field at top-level vulnerability message should be acceptable.

Afaik, CWEs are not OS distro dependent and are related to high level CVE/vulnerability. I think adding the field at top-level vulnerability message should be acceptable.

@hkadakia Got it. Could we please confirm this with comparison of Debian vs Ubuntu reports of CWEs for a given CVE? I left a comment on the PR, but happy to move the discussion here, up to you.

Issue resolved as part of #527


esModuleInterop causes is not a constructor function type

TypeScript Version:  2.7.1 and 2.8.0-dev.20180211

Search Terms:
is not a constructor function type
is not a constructor function type esModuleInterop
is not a constructor function type module Interop
Code
I am using https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/hapi for typing hapi 17
It works fine until I enable the new esModuleInterop then suddenly I get this error

node_modules/@types/hapi/definitions/server/server.d.ts:45:29 - error TS2507: Type '{ default: Podium; registerEvent(events: Events[]): void; registerEvent(events: Events): void; re...' is not a constructor function type.

45 export class Server extends Podium {

Expected behavior:
I believe the definition file should either be valid or not regardless of if esModuleInterop is enabled or not
Actual behavior:
If the type definition is invalid code and then should error either way. If it is valid code then it should not error either way.
Also if I //@ts-ignore the error the code compiles and runs fine

[Since Podium is a CommonJS module that is declared with an export =, you need to import it with import Podium = require("podium") or import Podium from "podium"

I guess I misunderstood the request; you're saying we should not issue these errors within declaration files since it's sort of out of the user's control.

Thanks I will also try to issue a PR to fix the declaration file. I was just super confused since it isn’t an error when module interop is off

It looks like this has been addressed. If not, please open a new issue with a self-contained repro so we can reassess. Thanks!


Next step for XVG integration?

Please see https://twitter.com/vergecurrency/status/1060240916483465216 regarding XVG integration - it seems the XVG development team has been waiting several months for a response, thanks.
Would you please see if there is anything that can be done to push this forward?  I really don't have a use for the Ledger Nano S if it doesn't support XVG.
Thank you.

Did someone response?

No, no one from Ledger as of yet has responded to this Github issue.  XVG core team has been waiting for months!


Started wire entity memory sync class

Will also require stringstream class

WireLib.MemoryTracker = {
    __index = {
        wrote = function(self, addr)
            -- See if a block already exists
            for i, v in ipairs(self.blocks) do
                if addr >= v.offset and addr < v.offset+v.size then
                    return
                elseif addr == v.offset-1 then
                    -- Leading edge
                    v.offset = v.offset - 1
                    if i>1 then -- Attempt merge
                        local prevblock = self.blocks[i-1]
                        if prevblock.offset+prevblock.size == v.offset then
                            prevblock.size = prevblock.size + v.size
                            table.remove(self.blocks, i)
                        end
                    end
                    return
                elseif addr == v.offset+v.size then
                    -- Trailing edge
                    v.size = v.size + 1
                    if i<#self.blocks then -- Attempt merge
                        local nextblock = self.blocks[i+1]
                        if v.offset+v.size == nextblock.offset then
                            v.size = v.size + nextblock.size
                            table.remove(self.blocks, i+1)
                        end
                    end
                    return
                end
            end
            local block = {offset = addr, size = 1}
            for i, v in ipairs(self.blocks) do
                if addr<v.offset then
                    table.insert(self.blocks, i, block)
                    return
                end
            end
            self.blocks[#self.blocks + 1] = block
        end,
        serialize = function(self, ss, memory, sizeleft)
            local nblocks = #self.blocks -- Needed because array is being cleared
            for i, v in ipairs(self.blocks) do
                local size = math.min(v.size, math.floor((sizeleft - 8)/8))
                if size > 0 then
                    ss:writeInt32(v.offset)
                    ss:writeInt32(size)
                    for i=v.offset, v.offset+size-1 do
                        ss:writeDouble(memory[i])
                    end
                    sizeleft = sizeleft - 8 - size*8
                    self.blocks[i] = nil
                else
                    -- Shift unfinished blocks to beginning
                    for j=i, nblocks do
                        self.blocks[j-i+1] = self.blocks[j]
                        self.blocks[j] = nil
                    end
                    return false
                end
            end
            return true
        end
    },
    deserializeAndApply = function(ss, memory)
        for i=1, ss:readUInt32() do
            local offset, size = ss:readUInt32(), ss:readUInt32()
            for j=offset, offset+size-1 do
                memory[j] = ss:readDouble()
            end
        end
    end,
    __call = function(meta)
        return setmetatable({
            blocks = {}
        }, meta)
    end
}
setmetatable(WireLib.MemoryTracker, WireLib.MemoryTracker)

Is this meant to be a replacement for NetworkVars?

Is this meant to be a replacement for NetworkVars?

No, it's for entities that sync their 'memory' variable to client

The only problem I foresee with my current approach is that it doesn't preserve write order or writing over a memory address multiple times, which I imagine may cause bugs in some entities. Maybe need to remove those optimizations.

Or maybe make a WireLib.MemoryTrackerPreserveOrder version.

Not really happy with this. I think I should've done a queue per entity instead of globbing all the entity data together. Also I don't have the energy to do the memory playback management for each entity that syncs its memory.


Acceptor errors are ignored

Hi there,
I wrote a custom acceptor that enforces client hostname checking during mTLS. I noticed in serve that errors from the acceptor are ignored, leading the the socket being closed with out reporting an error back to the client. It would be helpful to report these errors back to the client before closing the connection.
serve in server.rs
 tokio::spawn(async move {
     if let Ok((stream, send_service)) = acceptor.accept(addr_stream, service).await
     // ^^^^ maybe match on the result and write the error down the socket before closing the connection.
.....

In the case of an error, there is no way to access the socket to write to.
You should be able to write the error to the socket before returning an error from acceptor.


Introducing WIL activities for Push Notifications

The third and last part of the WIL activities into WNP trilogy.
This PR replaces Push Notifications telemetry events with activities. It also cleans throttling logic on NotificationTelemetryHelper and adds exception handling on all Start events.


Login/Restore not working

Something changed during the login/restore handshake. The following error appears:
Restoring failed: error decoding login connResp: json: cannot unmarshal array into Go value of type map[string]interface {}
The following json is received:
["cmd", {"type": "update"}]
Code fails in line 393 of session.go. Note that JSON does not contain entry "status", which is expected.

Me too

I got the same issue here: "error decoding login connResp: json: cannot unmarshal array into Go value of type map[string]interface {}".

try new version for whatsApp:  SetClientVersion(2, 2121, 6)

This happens because of outdated wa web version given to whatsapp. Change the version to newer one like @Stasich said and you can connect again.

Worked for me, thx guys :)

It worked here too! All of our clients got broken today.

When I changed to new version we received new error: qr code scan timed out.

Solved!

Is there a programmatic way of automatically figuring out the next version numbers?

How can I change the version?


Kbridwel patch 7

Hi Aiden,
I think you’re right. Too many late hours.
On Tue, Feb 8, 2022 at 10:34 AM Aidan Pine @.***> wrote:

Hi @kbridwel https://github.com/kbridwel - this PR (along with #5
https://github.com/roedoejet/AnyLanguage-Wordle/pull/5) looks
accidental, so I'll close them. Let me know if I'm missing something though.
—
Reply to this email directly, view it on GitHub
https://github.com/roedoejet/AnyLanguage-Wordle/pull/4#issuecomment-1032819292,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFUMNXWS6IHWTDOG3E6PELTU2FAZTANCNFSM5NZQTAGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Nahwitsakʉ mʉmʉ namakamuki!
"Listen with the ear of your heart." --Rule of Benedict
"There is always more misery among the lower classes than there is humanity
in the higher."

Victor Hugo

No worries @kbridwel ! :)


set dictionary circuit components

Codecov Report
Attention: Patch coverage is 0% with 12 lines in your changes are missing coverage. Please review.

Project coverage is 34.27%. Comparing base (cab62c5) to head (d429311).
Report is 3 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #4330       +/-   ##
===========================================
- Coverage   81.53%   34.27%   -47.27%
===========================================
  Files         107      107
  Lines       52271    52279        +8
===========================================
- Hits        42620    17918    -24702
- Misses       9651    34361    +24710


🐛 withConverter does not handle throwing converters well

Bug report
When using the default json serializer as a factory constructor on a class like in the example here: Typing collections with Firestore
Use withConverter fromFirebase with this factory constructor, a thrown exception is ignored and we never get a value back.
==> Loading Forever
Steps to reproduce
Steps to reproduce the behavior:

Throw inside the withConverter fromFirebase function
listening to the resulting future of reading from db will never complete

Expected behavior
withConverter should at least log, that there was something wrong, so that during development this can be tracked.
A possible fallback if exception was thrown, should be possible OR rethrow the error.

We had a custom error handler in the project which did not work...
The with converter function behaves correctly. Sorry for the inconvenience.