Enable remote debugging of functions from local VS Code w/o creating a security problem

Customer (Jason) uses Azure Functions extensively.
He loves to run them locally and debug them, but wants to be able to debug functions deployed to Azure without creating a security problem by opening additional ports, etc.

I do not think it is possible to remote debug without opening up a port - we have to get the debugging information somehow. In addition to your security concerns, remote debugging can also negatively affect performance of your app. For those reasons, I would only recommend you remote debug on test apps instead of production apps.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[framework] make HitTestEntry generic

At least on the web, this is the single most expensive cast in flutter. I wrote a bit about it in https://docs.google.com/document/d/1jkI8GCT4cId3a87PV5E0XQWRd2O5HsNhmchwgDUDv_k/edit

test-exempt: refactor with mostly no semantic change
you will probably want to test this thoroughly in google3 before landing; if it does fail there it'll need a migration guide

I hit all the buttons on frob, not sure what happened though :)

If you click on the details link you can get to the actual test run - it looks like it ran a pretty substantial number of targets to me, although I think it doesn't actually run all possible targets. I kicked off a full run at http://test/OCL:424157500:BASE:424373464:1643219399304:36a92355

I see only two failures which don't look related - or at least do not have any logs that indicate they are.

Unrelated flakes. This should be good to land.

yay, thanks @dnfield


[nnx] Fix variable unflatten

What does this PR do?
Unflatten a Variable usingobject.__new__ instead the constructor to avoid adding / calling hooks.

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

Comparison is base (008c3cc) 56.32% compared to head (0bf48f6) 56.31%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3578      +/-   ##
==========================================
- Coverage   56.32%   56.31%   -0.01%
==========================================
  Files         100      100
  Lines       11951    11954       +3
==========================================
+ Hits         6731     6732       +1
- Misses       5220     5222       +2

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


remove stucked workers, disable confirmation box, formated numbers, d…

remove stuck workers, disable confirmation box, formatted numbers, delta change

Closing due to inactivity


Author is me

How to Check msg author is bot?
ex) if($msg->author == $bot) { return; }
What's for $bot?
$this? Or $discordClient?
I think it's user object.
How to get usr obj from my bot?

$discordClient
And better check would be to use
$msg->author->id == $bot->id

$discordClient
And better check would be to use
$msg->author->id == $bot->id

Oh THX

I guess. Dont know hour your code looks like

I guess. Dont know how your code looks like

Nothing like "id" in Discord\Discord obj

I guess. Dont know how your code looks like

Nothing like "id" in Discord\Discord obj

The Discord\Discord class passes get calls to the Client object which has an id object, so you can call $discord->id on the Discord client. See the properties in the phpdoc: http://teamreflex.github.io/DiscordPHP/reference/classes/Discord-Discord.html#property_id


Not supported....

Hi.
Thank you very much for your software. I set up Noble on my Raspberry PI 2 with new Bluetooth dongles. From time to time I get a "Not supported" state although restarting (on the same device ID) the program results in a "poweredOn" state. I don't really why and where the problem is.
Besides, can I "reset" Noble and try again? If so, how?

@MeMyselfI do you have a set of reproducible steps for this? I've seen this occasionally, but haven't tracked it down.
You can try a sudo hciconfig hci0 down && sudo hciconfig hci0 up to reset the adapter.
I think this is same behaviour as #129.

Thanks for your answer. It helps when starting the program again so I guess I don't need to reset the adapter. The problem isn't related to scanning I start scanning only after a poweredOn which I don't get from time to time.
And sorry, no, I cannot reproduce it - it happens from time to time after starting the program and it works the next time (without any reset or reboot). I will use a workaround with a cron job, though.
BTW, I used two dongles at the same time.

@MeMyselfI how should we proceed with this issue? Without a set of steps to reproduce, it's hard to create a fix.

No problem just close it. If I get more information I will open a new issue. Only thing that may help me is a method to restart noble, like noble.restart.


Corrected replaced unevaluated with additionalProperties

I'm merging immediately as this just fixing a typo in a description.


cannot find mat-core()

I'm using angular-material as part of an angularjs-angular hybrid app. I have a custom these style sheet which up till a few days was working fine, but now I'm getting this error "Cannot find mixin mat-core"
for the line:
@include mat-core();

What version of Material are you using. Also are you using node-sass or sass?

node-sass and<EMAIL_ADDRESS>

In Angular v12 we're switching to the new @use-based module system in Sass which isn't supported by node-sass. If you switch over to sass, it should work without any other changes on your end. It's also worth noting that node-sass is deprecated.

Our changelog for v11 noted that node-sass with Angular Material is officially unsupported:
https://github.com/angular/components/blob/master/CHANGELOG.md#material-19

In Angular v12 we're switching to the new @use-based module system in Sass which isn't supported by node-sass. If you switch over to sass, it should work without any other changes on your end. It's also worth noting that node-sass is deprecated.

thanks a million, that fixed it.


Slideshow with Images and Links to Posts along with Brief Description.

Perhaps it would be even better to have a slideshow that would redirect to a post link given beforehand. What I'm trying to achieve is the following images converted to a slide with clickable links to some other url.
Ideally,
Creation of the following nested YAML front matters:

Title
Url
Description
Img_Path

Hello
I'm not sure I understand
Would you make a PR?


Show also when just hitting a modifier key alone (with no additional character key)

Thank you for the awesome work with KeyCastr! ♥ I love it for demonstration purposes of a screen reader called NVDA.
NVDA has some really quirky special keyboard combos. For example, by hitting Control alone, I stop NVDA while announcing something (through the audio channel). Or by hitting Shift alone, I skip the current announcement and let NVDA announce the next one (if there is one).
Sadly, KeyCastr seems to display only "real" keyboard combos like Ctrl + A or Shift + 1, but not a modifier key alone. Wouldn't it make sense to do that? The logic would be something like: if a modifier's keyUp event is fired, and there has no "real" keyboard combo been pressed since its keyDown, just show the modifier key.

Hey, @jmuheim thanks for opening an issue about this.
Yes, I agree something like this should be supported via a user-facing configuration and/or a new visualizer mode entirely, since there are so many use cases for needing to visualize keystrokes. Indeed, the two currently open PR's have to do with this use case.
I struggle with what to call this as an additive configuration option though... something like "Include all modifiers" Y/N
What do you think?

Thanks for your response, @akitchen. I would call it "Show modifier-only keystrokes", which would include a single Ctrl as well as a combination like Cmd-Shift: as soon as all keyUp events are fired and only modifier keys were pressed, display them!

doesn't work
ctrl
ctrl + mouse drag
I uninstall the app with frustration.

I took the expressed user need here and integrated it into a concrete user experience design proposal.


Bump golangci-lint to 1.20.0

This may fix issues when using golangci-lint with projects
that have moved to go1.13.

Looks great @freeformz - it works as designed now with our 1.13 apps.
Thanks for the quick response!


Ember plupload Problem with Instantiating FileInput

I want to create a drag & drop upload file ember.js app, I'm trying to use ember-plupload, but I can't make the plupload work, I'm using the sample code for template and route, my result is:
Instantiating FileInput...
Trying runtime: html5
Object {accept=[1], name="file", multiple=true, ...}
default mode: browser
selected mode: false
Runtime 'html5' failed to initialize
Trying runtime: html4
Object {accept=[1], name="file", multiple=true, ...}
default mode: browser
selected mode: false
Runtime 'html4' failed to initialize
Trying runtime: flash
Object {accept=[1], name="file", multiple=true, ...}
select_multiple: true (compatible modes: null)
drag_and_drop: true (compatible modes: null)
default mode: client
send_browser_cookies: false (compatible modes: client)
select_file: true (compatible modes: client)
selected mode: false
Runtime 'flash' failed to initialize
Trying runtime: silverlight
Object {accept=[1], name="file", multiple=true, ...}
select_multiple: true (compatible modes: null)
drag_and_drop: true (compatible modes: null)
default mode: browser
send_browser_cookies: false (compatible modes: client)
select_file: true (compatible modes: client)
Silverlight is not installed or minimal version (2.0.31005.0) requirement not met (not likely).
selected mode: false
Runtime 'silverlight' failed to initialize
Instantiating FileDrop...
Trying runtime: html5
Object {accept=[1], required_caps=Object, ...}
default mode: browser
selected mode: false
Runtime 'html5' failed to initialize
Trying runtime: html4
Object {accept=[1], required_caps=Object, ...}
default mode: browser
selected mode: false
Runtime 'html4' failed to initialize
Trying runtime: flash
Object {accept=[1], required_caps=Object, ...}
select_multiple: true (compatible modes: null)
drag_and_drop: true (compatible modes: null)
default mode: client
drag_and_drop: true (compatible modes: null)
send_browser_cookies: false (compatible modes: client)
select_file: true (compatible modes: client)
selected mode: false
Runtime 'flash' failed to initialize
Trying runtime: silverlight
Object {accept=[1], required_caps=Object, ...}
select_multiple: true (compatible modes: null)
drag_and_drop: true (compatible modes: null)
default mode: browser
drag_and_drop: true (compatible modes: null)
send_browser_cookies: false (compatible modes: client)
select_file: true (compatible modes: client)
Silverlight is not installed or minimal version (2.0.31005.0) requirement not met (not likely).
selected mode: false
Runtime 'silverlight' failed to initialize

What can I do in that case?
My version of ember:

> ember-cli: 2.5.0
> node: 6.2.0
> os: win32 x64

Greetings, Rafał

Same problem here. Using the sample code.

+1

Same

Oh man. Lemme look at it. I think the docs may be bad.

Found a bug with a PR that was merged in recently, applying a bug fix. Sorry for that!

See 1.13.16

Thanks @tim-evans !

Thanks Tim !


nuxt SCSS can not use liner gradient on production

So I have a vue file which uses SCSS style (in all my project I am using SCSS) and from some reason when I use the
background-image: linear-gradient(to inline-start, $color-blue--navy 19934%, $color-blue--ocean 20002%)
I get errors only when I run npm build; when I run dev, the app works fine.
The Isueue is at  postcss-minify-gradients -> dist - > index.js

Are you able to create a project that reproduces this issue?
Also, try deleting the lock file and node_modules first and see if it still reproduces.

Closing due to no response.
Though I suppose this is not related to this module at all.


Should we still force keyword arguments in _PowGate initialization?

There's only one unit possible now.

I haven't really decided which way I want to go on that. For the most part users shouldn't be calling those methods anyways, they should be using the more convenient cirq.X**0.5 or cirq.Rx(np.pi/2). So I'm not too worried about making it convenient to call them.

There's only one unit possible now.

Isn't it two? exponent  and global_shift
https://github.com/quantumlib/Cirq/blob/1e6436c136dbe94a62970fa64692d27ed8f919c8/cirq/ops/eigen_gate.py#L65

Anyway, these are the comments on the commit that introduce it
Use just '*' to force keyword arguments (#537)

    Casey pointed this out to me. It's significantly better because:
    - it doesn't require a docstring for the argument
    - it doesn't need an assert line
    - it gives a better error message to the user

I agree.

I think the argument that it doesn't require a docstring is not a positive one.

@vtomole What I mean is that one is no longer allowed to specify the rotation in units of rads or degrees. There is only one choice: specify the exponent.

@kevinsung Thanks for the clarification. In that case i agree.

I like that we continue to force the keyword, because I'm still not happy with the API here. It insulates us from making subtle breaking changes, where the first argument becomes different.

I think that's fine.


npm version detection is pretty lousy

Due to the deprecation of --global-style in npm v9, #242 introduced a version check to avoid triggering the warning.  However, the version check just looks at the first character of the output from npm --version and uses --global-style if it is 7 or 8.
Given npm v6 and older is unsupported, I'm not sure we need to worry about it.  But it could result in a misleading error message if that's indeed the case.  Nevermind that this will break again when npm releases version 70. 😝
I wanted to avoid pulling in all of semver to check the version. Maybe there's something smaller and more robust we could use.

closing given the plugin-like refactor of the package manager code


Build error on MacOS

Hey all!
I've started getting a build error on MacOS since I pulled master. Seems to be related to base64_decode_sextet.
In file included from src/string_object.cpp:3:
/Users/stephen/work/ruby/forks/natalie/include/natalie/string_unpacker.hpp:253:26: error: implicit instantiation of undefined template 'std::array<unsigned char, 3>'
            auto chars = base64_decode_sextet(a, b, c, d);
                         ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/__tuple:219:64: note: template is declared here
template <class _Tp, size_t _Size> struct _LIBCPP_TEMPLATE_VIS array;
                                                               ^
In file included from src/string_object.cpp:3:
/Users/stephen/work/ruby/forks/natalie/include/natalie/string_unpacker.hpp:342:34: error: implicit instantiation of undefined template 'std::array<unsigned char, 3>'
    std::array<unsigned char, 3> base64_decode_sextet(unsigned char a, unsigned char b, unsigned char c, unsigned char d) {
                                 ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/__tuple:219:64: note: template is declared here
template <class _Tp, size_t _Size> struct _LIBCPP_TEMPLATE_VIS array;
                                                               ^
In file included from src/string_object.cpp:3:
/Users/stephen/work/ruby/forks/natalie/include/natalie/string_unpacker.hpp:354:16: error: implicit instantiation of undefined template 'std::array<unsigned char, 3>'
        return { out_a, out_b, out_c };
               ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/__tuple:219:64: note: template is declared here
template <class _Tp, size_t _Size> struct _LIBCPP_TEMPLATE_VIS array;
                                                               ^
3 errors generated.
rake aborted!

Yep I can reproduce, I've just opened a PR with a fix.


Fixed Ukrainian translation for ago line.

Fixed mistake in Ukrainian translation lineago.
use Jenssegers\Date\Date;

Date::setLocale('uk');
Date::now()->subMinutes(30)->diffForHumans(); // "30 хвилин тому" instead of "30 хвилин назад"

Would love to get some additional reviewers on this!

https://github.com/briannesbitt/Carbon/commit/e95eba8fa0537d010ce2f936910f8044f573c88c
@AucT is Ukrainian too and said тому is more used.


Include Only a number of folders inside a solution

vscode currently support only including folders inside a solution.
"files.exclude": {
    "**/.git": true,
    "**/.svn": true,
    "**/.hg": true,
    "**/CVS": true,
    "**/.DS_Store": true

}

However, its very useful to add include option to add only a selected/filtered list of directories to the solution.

I think this is a duplicate of multi root folder work we are currently working on


first draft of race2

Might recode the particles into a separate dim if necessary

Tests also failing, needs investigation.

@anvo2 ping on this. Comments being addressed?

@anvo2 the tests are failing still.
Is this WIP or supposed to be ready for review?


Load data/*.json file from domain name or from the URL

To support routes:
thisproject.com/stemount would load stemount.json
but if you use this project for your own domain, you could load in this order:
json/{{ url_slug }} (support being able to use something.com/url_slug)
json/{{ domain }} (if no URL slug, look at URL domain e.g. something.com.json)
json/me.json (a default in general)

hey can i work on this?

Is anyone currently working on this issue? This is beause it has been open for a while now. If anyone needs help, feel free to ask!
Thank you.

Is anyone currently working on this issue? This is beause it has been open for a while now. If anyone needs help, feel free to ask! Thank you.

Hi, I want to work on this issue. Please let me know, how to understand the problem and go through it.

Did LinkFree ever get this functionality?

I don't think so, if features are going to are added, probably best to add it to the nextjs branch though

I think this depends on the hosting platform? We are currently moving hosting solutions, so I will block it for now


uncomment intallsshkey

Resolves # . (This is applicable only if this pull request relates to a GitHub issue, delete the line otherwise)
Notes:
*
*
*

uncomment ssh of pipeline to install module


[Urgent] Pro Plan , Allow scrolling and grouping of Layouts List

We have a pro plan with you and currently facing that our layouts are out of reach from the screen height, please allow scrolling and grouping of these layouts in the list so we can navigate better.
Thanks

Hi @ibakhsh4salla!
I will look to add scrolling inside the layout list.
In the meantime you can already group them in folders using a / in their name (it's explained in the layout modal).
Let me know if you need more help.
Cheers!


Sync UI

SkyWalking eyes seems having a bug when some other PRs break maven cache, and this CI doesn't need to recompile at the same time.
Wait for @kezhenxu94 to fix on skywalking-eyes.


All MVC4 downloads missing!

General
I can't get a download to the 2014 Web Camps training kit or the .NET 4 MusicStore solution. A boatload of people are not yet on .NET 5/.NET Core, so those downloads should still be available for training.
My main goal is training a team (and brushing up myself) on the proper patters for using dependency injection in a .NET 4 MVC app (also WebAPI). There are some big differences between .NET Core's DI and earlier versions, so I don't really want to train everyone on .NET Core at this time.

Is it this :point_right: https://www.microsoft.com/en-us/download/details.aspx?id=36393

It is indeed, but it results in essentially a 404 from Web Platform Installer. Any other direct download or alternative/ magnet ends in 404 as well.

Ah ... @jongalloway may have the answer. See his comment at the end of this :point_right: https://forums.iis.net/t/1228981.aspx

Curious: @terrimorton ... Is the page at https://www.microsoft.com/en-us/download/details.aspx?id=36393 in your ballpark? If so, can the page provide the content of Jon's note and have its download link disabled?

I ran across that one in my initial Googling. The problem is the 2016 release is based on .NET Core, and that is significantly different from the way .NET 4/4.5 handles DI. I didn't even see a DI section in the 2016, which is my main interest in the .NET 4 Web Camps download.
The articles and hands-on stuff is all still online, it's one of the top results when searching for DI training in MVC. I feel like the downloads should still be available too :(

Does that include the 2015 release?
https://github.com/Microsoft-Web/WebCampTrainingKit/releases/tag/v2015.10.13b

... and I see a bad link in that set of topics to: https://www.microsoft.com/download/29843 that 404s.
Also, the problem with using the link http://aka.ms/webcamps-training-kit is that it goes directly to the 2016 release. Those topics don't say how to reach the general releases page.
I'll take this on and ping Jon on the PR. @stevendc, let me know if that 2015 link get the right kit, and thanks for reporting this problem.

The training I'm after is here, just so you know my hopeful goal:
https://docs.microsoft.com/en-us/aspnet/mvc/overview/older-versions/hands-on-labs/aspnet-mvc-4-dependency-injection
I'm reviewing the download above for 2015 release. It seems like the correct .NET version, but may not contain the specific DI training I was hunting. Either way thanks for the collection of fast responses, I'll continue to monitor this issue so any additional help is appreciated!

@stevendc Yeah ... and I see that bad "29843" link there, too. Does the link down in the comments reach the correct project? https://github.com/Microsoft-Web/HOL-MVC4DependencyInjection/tree/master/Source
... and, yes, if you can let me know if that 2015 downloadable includes that MVC4 DI project, that would be great. Otherwise, np ... I'll download it and look.
ping @jongalloway
TL;DR The Web Camp Training Kit link that replaces the Microsoft Download Center link, http://aka.ms/webcamps-training-kit redirects to https://github.com/Microsoft-Web/WebCampTrainingKit/releases/tag/v2016.02.09, so the reader doesn't immediately see that the 2015 release is still available at https://github.com/Microsoft-Web/WebCampTrainingKit/releases/. Do you have a preference for the docs between ...

Leave the current link; but at the bottom of the topics, link out with the general releases that shows the 2016 and 2015 kits, --OR--
Change the current link to point to the general releases page that shows both kits.

Also note that several topics link to https://www.microsoft.com/download/29843, and they should get the same update depending on which way you want to go. :point_up:

@guardrex Yes, that's the correct solution located at https://github.com/Microsoft-Web/HOL-MVC4DependencyInjection/tree/master/Source
Thanks, from me and on behalf of the 6 devs who will be trained on DI with this exercise!!

Np ... my pleasure. As soon as I hear back from Jon, I'll get those links updated.

I've updated https://aka.ms/webcamps-training-kit to point to the general releases list. Also, I think it makes sense to update notes at the end of the docs to link out to specific releases.

Thanks @jongalloway ... then I'll just get the bad 404 link out at  https://www.microsoft.com/download/29843.
I'll ping you to review the PR. Thanks again! :rocket:

@jongalloway

I think it makes sense to update notes at the end of the docs to link out to specific releases.

There is one thing that concerns me about doing that. We're going to be behind the 🎱 for future releases of the kit. I mean unless you (or someone) remembers to open issues going forward, we'll probably miss adding links for future training kits. Therefore, I think it best if we just update the broken link (https://www.microsoft.com/download/29843) to point to https://aka.ms/webcamps-training-kit.
@Rick-Anderson @scottaddie Thoughts?


Make DialEarly return EarlySession

func DialAddrEarly returns an EarlySession. Why not make DialEarly return an EarlySession too, so that we could use it with the http3 package?

That seems to be a bug.
Would you mind sending us a PR with a fix?


Translate concepts/configuration/pod-overhead.md in Korean

This is a Feature Request

What would you like to be added

Translate concepts/configuration/pod-overhead view in Korean.
Why is this needed
There is no documents with concepts/configuration/pod-overhead in Korean.
Comments

https://kubernetes.io/docs/concepts/configuration/pod-overhead/

/language ko
/assign

/close


feat: 🎸 update to chakra-v2

Description
update the autocomplete component to use chakra ui V2 under the hood
Major
BREAKING CHANGE: 🧨 Now using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Hey @anubra266 ! Super cool lib, i'm relying on it for my usage, would be awsome to update to @chakra-ui v2 and react 18, i made a little PR and update all the depencies

Thanks @Wizyma released v5

you're welcome @anubra266  !
thank you for putting the time and effort to build it at first ! Really helpfull !


sfdx force:source:deploy --manifest  ERROR:  Cannot read property 'getMetadataName' of undefined.

Summary
It seems like if your pacakge.xml has any metadata components listed that do not exist in your force-app, that it fails.
Steps To Reproduce:

sfdx force:source:retrieve -- manifest in VS Code pull source from Org with a Package.xml file
change orgs in VS Code to a new sandbox
sfdx force:source:deploy --manifest  /manifest/package.xml  with the VS code right click

get the error ERROR:  Cannot read property 'getMetadataName' of undefined.
Expected result
unless you have undeployable metadata components in your package.xml, you should be able to use the same package.xml to both source:retrieve and source:deploy
Actual result
If mtetadata defined in your package.xml returns no files, then that folder is not created in force-app. then when you try to deploy you get ERROR:  Cannot read property 'getMetadataName' of undefined.
Additional information
VSCode output window:
Starting SFDX: Deploy Source to Org

sfdx force:source:deploy --manifest /project/manifest/package.xml
WARNING: apiVersion configuration overridden at 43.0
ERROR:  Cannot read property 'getMetadataName' of undefined.
sfdx force:source:deploy --manifest /project/manifest/package.xml ended with exit code 1

VS Code Version:
OSX Version 1.26.1 (1.26.1)
SFDX CLI Version:
sfdx-cli/6.29.0 (darwin-x64) node-v8.11.2
OS and version:
OSX 10.12.6

Interesting thing I found: a typo in your deploy command can produce this error too.
sfdx force:source:deploy -m LightningtComponentBundle:myComponent

Note the extra "T" before "Component". This productes the same error described in the original post. Fixing the metadata name makes the command work.
Just commenting in case someone else has this same issue because of a silly typo. :)


[2.0.4] dmctl: support read master addr from env

What is changed, added, or deleted? (Required)

update dmctl doc to note that master_addr can be read from env var.
Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v3.0 changes)
[x] v2.0 (TiDB DM 2.0 versions)

What is the related PR or file link(s)?

This PR is translated from: https://github.com/pingcap/dm/pull/1726

Do your changes match any of the following descriptions?

[x] Change aliases

/hold

/unhold

@CharLotteiu  @GMHDBJD
DM v2.0.4 has been released and this PR is ready to be merged.

/merge


Add additional formatting options to integer format functions

Currently, the Sunder integer types and std::bigint type support the alternate form and radix portions of the integer format specifiers commonly found in languages such as C, Python, and Rust. Add additional specifier options to bring Sunder closer to what a user would expect coming from another language with similar format specifiers (principal of least surprise).
Use the Python format specification mini language as reference.

With Sunder becoming sufficiently stable, and much of the remaining compiler cleanup work making its way into the 2022.11.01 release, the Sunder project project is unlikely to see major revisions to the language or standard library moving forward. For this reason I am closing this issue as a WONTFIX.


GH-3797 Encode hashcodes in IDs

GitHub issue resolved: #3797
Briefly describe the changes proposed in this PR:
This is a first PoC for embedding of hash codes within IDs.

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

@kenwenzel this PR has been sitting idle for a while. Are you still intending to work on this?

The PoC has shown that the insertion rate drops drastically. Therefore we shouldn't follow this approach.


Cmdable interface has unexported functions

This interface would be perfect for dependency injection or to enable mocking of a client, but it has unexported functions and that makes mocking nearly impossible.
When you create a new struct that implements the interface for mocking, the compiler complains about the unexported functions not having the expected type and the mock not implementing redis.Cmdable.
The compiler error is something like
cannot use client (type *"github.com/my/project/mocks".Cmdable) as type "gopkg.in/redis.v4".Cmdable in argument to NewRedis:

	*"github.com/my/project/mocks".Cmdable does not implement "gopkg.in/redis.v4".Cmdable (missing "gopkg.in/redis.v4".bitOp method)

		have "github.com/my/project/mocks".bitOp(string, string, ...string) *"gopkg.in/redis.v4".IntCmd

		want "gopkg.in/redis.v4".bitOp(string, string, ...string) *"gopkg.in/redis.v4".IntCmd

If I missed anything and there is a better way of mocking Client/Cmdable please let me know.

Fixed in v4.1.9. Thanks for the report!

There are still some unexported functions, I'm opening a pull request now. Thanks for the fast response!


[master] Update OSA SHA

Connects https://github.com/rcbops/rpc-openstack/issues/1950

Closing in favor of https://github.com/rcbops/rpc-openstack/pull/1957


[BUG] Wrong $defs keyword used in JSON schemas

Observed behavior
docs/schema/v0/flags.json and docs/schema/v0/targeting.json use the $defs keyword.
Both JSON schemas use version draft-07 based on the $schema setting.
A quick look at Google shows that the $defs keyword is not part of the draft-07 version. Back then, it was named definitions. E.g., see https://opis.io/json-schema/2.x/definitions.html.
Some json-schema-validators like com.networknt.json-schema-validator write warning logs by default if unknown keywords are encountered. This is exactly what happens in this case with this validator:
c.n.schema.UnknownKeywordFactory         : Unknown keyword $defs - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword

Expected Behavior
Would it be possible to use definitions instead of $defs for as long as the JSON schema version is draft-07?
Affected JSON schemas:

docs/schema/v0/flags.json
docs/schema/v0/targeting.json

Steps to reproduce
No response

Thanks for bringing this up, @dt-rendstrasser. Here's a direct link to the spec that confirms that definitions is still valid in newer versions of the spec but $defs has superseded it.

I will confirm and implement this and if all works as expected I will release a fix. Standby.

Pulling this into the flagd provider for Java: https://github.com/open-feature/java-sdk-contrib/pull/789


Has an error, Manifest Ver 2 is deprecated and support will be removed in 2023

Uhhh Manifest Ver 2 is outdated and support is removed in 2023

Duplicate of #47


colors are gone when you change the colorscheme

spectre works as expected when I start nvim.

But if I ever change my colorscheme (say to switch to a light colorscheme), then the colors are gone:

(and switching back to the previous colorscheme doesn't help either:

)
I am using:
NVIM v0.9.0-dev-805+g9166116c6-dirty
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by<EMAIL_ADDRESS>
Features: +acl +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/opt/homebrew/Cellar/neovim/HEAD-9166116/share/nvim"

Run :checkhealth for more info

on max os sonoma 14.1.2 (23B92)
and with the latest nvim-spectre (commit a18a580)

Hi, I have almost the same setup, and encountaring this bug, did you find any workaround?


pre-commit: integrate with cndp

Install pre-commit for CNDP + its configuration.
Remove old githook.

Sorry for the delay in this, I was away on some summer hols - fixed up the last outstanding issue and it's ready now


Support Visual Studio 2017 and 2019

Description of the Change
Main change:

Detect Visual Studio 2017 and 2019

Related changes:

Stop detecting unsupported versions, which node-gyp refuses to use (Visual Studio 2010 - 2013)
Don't set the --msvs_version node-gyp flag, which sets a specific version of Visual Studio that node-gyp must find, or else it will error out.

Our detection for actually-working Visual Studio installs is substantially worse than node-gyp's. We should let them detect and use whatever usable version of Visual Studio they can find.

Explanation (click to expand):
Builds on apm's existing code to detect installs of Visual Studio, by adding the ability to detect Visual Studio 2017 and 2019.
Those versions of Visual Studio are now fully supported in the version of node-gyp we use (node-gyp@5).
As of node-gyp PR https://github.com/nodejs/node-gyp/pull/1762, node-gyp is much better than us at finding Visual Studio installs and identifying whether on not they can be used. This isn't a simple matter of having Visual Studio or not, but also various components must be installed.
Given that our detection is worse, I have made it so apm no-longer sets the --msvs_version flag. This flag forces node-gyp to use the specified major version of Visual Studio/Build Tools. It can only restrict node-gyp within usable installs. There is no scenario where setting this causes any benefit to us. But if we get it wrong (and our detection is worse, so we very likely would), this can cause node-gyp to refuse to use a valid Visual Studio/Build Tools install and error out.

Alternate Designs
This, but with some of the changes reverted/taken out.

All commits in this PR are designed to be logical choices that are well-backed-up by the explanation and reasoning given.
That said, the commits are in order of how radical the change is, or how controversial I thought the change might be. If any of the commits/changes are objectionable, please let me know, and the rest of the PR still makes sense without that change. This is a few related changes bundled together, but any of the three bullet points is a positive step in the right direction, and works independent of the other two bullet points.

Benefits

Lets apm and node-gyp use Visual Studio 2017 and 2019, even if 2015 or older is also installed
Stops causing errors for our users, such as by rejecting Visual Studio 2017 and 2019 if a buggy 2015 or earlier install is the first one found
Gets out of the way of a critical dependency detection task that node-gyp is doing better than us at
More successful package builds, more happy customers?
Keeps up with the latest Visual Studio major versions we support (via node-gyp).

Possible Drawbacks
None that I am aware of. Before this PR, we have been artificially limiting how good a job node-gyp could do to find Visual Studio, in certain cases. Now, with this PR, we stop doing that.
Reaching for a hypothetical problem: I suppose if Visual Studio 2017 or 2019 are buggy, this exposes our users to that. (In my experience, VS 2017 and 2019 are not buggy.)

Verification Process
Lengthy "Verification Process" section contents (click to expand):
This un-blocks apm from using a correctly-detected, working install of Visual Studio 2019 in (forked) Atom's CI.

Before: https://dev.azure.com/atomcommunity/atomcommunity/_build/results?buildId=176&view=logs&j=97a617bf-bcbd-5dfa-bba2-cfba2747b693&t=1e1369e9-1c56-59b0-830c-f1606a680c8a&l=32
After: https://dev.azure.com/atomcommunity/atomcommunity/_build/results?buildId=177&view=logs&j=97a617bf-bcbd-5dfa-bba2-cfba2747b693&t=1e1369e9-1c56-59b0-830c-f1606a680c8a

Breakdown of the "Before" case: The issue in this case was that apm detected an install of 2015 that turned out to be unusable. The error is: "could not find MSBuild in registry for this version". At the bottom of the error message, a message points out that 2019 would have been a valid version, had we allowed node-gyp to use it:
gyp ERR! find VS valid versions for msvs_version:
gyp ERR! find VS - "2019"
gyp ERR! find VS - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise"

Furthermore, apm --version can now find Visual Studio 2017 and 2019.
Before and after on the same machine, with Visual Studio 2019 Community installed:
Before:
C:\Users\[User]\>apm-dev --version
apm  2.5.0
npm  6.14.5
node 10.20.1 x64
atom 1.50.0-dev-110b05baf
python 2.7.18
git 2.27.0.windows.1
visual studio

After:

C:\Users\[User]>apm-dev --version
apm  2.5.0
npm  6.14.5
node 10.20.1 x64
atom 1.51.0-dev-912dad331
python 2.7.18
git 2.27.0.windows.1
visual studio 2019

Note that Visual Studio 2019 is detected: visual studio 2019 (on the bottom line of output from apm --version).
Here's the before and after on another machine, this time with Visual Studio 2017:
Before
C:\Users\[User]>apm-dev --version
apm  2.5.0
npm  6.14.5
node 10.20.1 x64
atom 1.50.0-dev-9c16e5c67
python 2.7.18
git 2.27.0.windows.1
visual studio

After
C:\Users\[User]>apm-dev --version
apm  2.5.0
npm  6.14.5
node 10.20.1 x64
atom 1.51.0-dev-912dad331
python 2.7.18
git 2.27.0.windows.1
visual studio 2017

Note that Visual Studio 2017 is detected: visual studio 2017 (on the bottom line of output from apm --version).

Applicable Issues

Upstream PR: https://github.com/atom/apm/pull/892
Fixes #893

This and the "Node 12.0.0" PR are copied exactly from the upstream PRs.

As a general Note: when writing draw-backs, if it doesn't have one, it is better to write nothing and don't make an illusion that this PR has a drawback by explaining why it does not! This explanation is usually destructive rather constructive. Move the discussion about the rationale to the description instead.
From my experience, I see that people are too picky about this part of the description. Just move the information to the description and people will feel better!

Yes. I think you are right, sadly. (Or not sadly, if I think about it.)
The instinct to self-review is to show I take contributing changes to upstream seriously, and have considered the ramifications. Then I am so conservative about my changes that there are usually no downsides! So I can't project all this concern and caution when there isn't much reason to feel that way from the code being suggested.
I have to strike a balance, or put "none" and let reviewers see if they feel there is a downside. A middle ground option would be to hold back some of the verbosity here.


pixi add is stuck at the "loading repodata" step

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
pixi.toml is trivial:
[project]
name = "pixi-test"
version = "0.1.0"
description = "Add a short description here"
authors = ["Matthias Riße<EMAIL_ADDRESS>channels = ["conda-forge"]
platforms = ["linux-64"]

[tasks]

[dependencies]

Issue description
This is the output I get:
$ pixi -vvv add python
DEBUG pixi::config: Loading config from /etc/pixi/config.toml
DEBUG pixi::config: Failed to load system config: /etc/pixi/config.toml (error: failed to read config from '/etc/pixi/config.toml')
DEBUG pixi::config: Loading config from /home/icg1/icg149/.config/pixi/config.toml
DEBUG pixi::config: Failed to load global config: /home/icg1/icg149/.config/pixi/config.toml (error: failed to read config from '/home/icg1/icg149/.config/pixi/config.toml')
DEBUG pixi::config: Loading config from /home/icg1/icg149/.config/pixi/config.toml
DEBUG pixi::config: Failed to load global config: /home/icg1/icg149/.config/pixi/config.toml (error: failed to read config from '/home/icg1/icg149/.config/pixi/config.toml')
DEBUG pixi::config: Loading config from /home/icg1/icg149/.pixi/config.toml
DEBUG pixi::config: Failed to load global config: /home/icg1/icg149/.pixi/config.toml (error: failed to read config from '/home/icg1/icg149/.pixi/config.toml')
DEBUG pixi::config: Loading config from /home/icg1/icg149/Playground/pixi-test2/.pixi/config.toml
DEBUG pixi::config: Failed to load local config: /home/icg1/icg149/Playground/pixi-test2/.pixi/config.toml (error: failed to read config from '/home/icg1/icg149/Playground/pixi-test2/.pixi/config.toml')
 INFO pixi::environment: verifying prefix location is unchanged, with prefix file: /home/icg1/icg149/Playground/pixi-test2/.pixi/envs/default/conda-meta/pixi_env_prefix
DEBUG pixi::cli::add: environments affected by the add command: default
 INFO pixi::lock_file::outdated: environment 'default' is out of date because it does not exist in the lock-file.
DEBUG resolve_conda{group=default platform=linux-64}:get_or_create_subdir{channel=Channel { platforms: None, base_url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("conda.anaconda.org")), port: None, path: "/conda-forge/", query: None, fragment: None }, name: Some("conda-forge") } platform=Linux64}:fetch_repo_data{cache_path=/home/icg1/icg149/.cache/rattler/cache/repodata}: rattler_repodata_gateway::fetch: checking availability of 'https://conda.anaconda.org/conda-forge/linux-64/repodata.json.zst'
⠤ updating lock-file   [00:05:34] [────────────────────────────────────────]    0/2
  ⠁ default:linux-64     [00:05:34] loading repodata                                                                                ^C

I've also seen this go on for >30 minutes without any further progress.
This issue affects one machine, while another similar machine (same LDAP user, same home mounted via NFS) does it just fine. Oddly enough, once it ran on the machine where it is working, then it also does on the other, until I clean out the cache (pixi clean cache). Afterwards, it stops working again.
I can wget the file mentioned in the last debug output just fine on both, they have the same checksum.
Expected behavior
pixi add python should just work in a freshly initialized pixi project.

Is there an extreme usage of your CPU or RAM?

Doesn't look out of the ordinary:

(the "artifacts" are from resizing the terminal window...)

Could you test https://fast.prefix.dev/conda-forge instead of conda-forge?

Replacing "conda-forge" in channels with that URL doesn't seem to make a difference, it has been stuck for >5 minutes now.

Does it work if you do a pixi install before the pixi add (should have the same code path but who knows).

pixi install seems to be stuck at the same point.
This is happening for two different user accounts, so I don't think it has anything to do with a broken pixi installation or something. I am sure there is something wrong with this machine, I just don't understand what it could be...

Could you try pixi install --tls-no-verify?

I ran pixi add with --tls-no-verify in the screenshot, which was stuck for >40 minutes. It also doesn't seem to change anything with pixi install.

I'm sorry I missed this, I'm out of ideas, @baszalmstra do you have some more ideas to test to see what could be going on?
Also for reference could you share a pixi info print out?

$ pixi info
      Pixi version: 0.26.1
          Platform: linux-64
  Virtual packages: __unix=0=0
                  : __linux=5.15.0=0
                  : __glibc=2.31=0
                  : __archspec=1=skylake
         Cache dir: /home/icg1/icg149/.cache/rattler/cache
      Auth storage: /home/icg1/icg149/.rattler/credentials.json

Project
------------
              Name: pixi-test
           Version: 0.1.0
     Manifest file: /home/icg1/icg149/Playground/pixi-test/pixi.toml
  Config locations:

Environments
------------
       Environment: default
          Features: default
          Channels: https://fast.prefix.dev/conda-forge
  Dependency count: 0
  Target platforms: linux-64

So, this was rather anticlimactic now... I just rebooted the machine (something that I should probably have done first), and it is working now.
I have no idea what changed, other than the uptime counter, but I doubt that pixi is bothered by >50 days or something. I think I have checked kernel versions before and there wasn't an outstanding update, but I cannot swear by it.
Anyway, it is fixed, so I'll close the issue. Sorry for wasting some time. If the issue ever comes back and I get a handle on how to make it reproducible I'll report back...

Haha that is very anticlimactic. Thanks for getting back to closing the issue.

Followed linux installation and created a new terminal after the install step.
cd /tmp
pixi init howdy
cd howdy
pixi add python

This was stuck at the same loading repodata step.
Instead of rebooting the workstation, logged out completely.  On reconnection, the pixi add python step completed quickly.  FWIW:
(base) prjemian@arf:.../sandbox/hey-there$ pixi info
System
------------
      Pixi version: 0.34.0
          Platform: linux-64
  Virtual packages: __unix=0=0
                  : __linux=5.15.0=0
                  : __glibc=2.35=0
                  : __archspec=1=skylake
         Cache dir: /home/prjemian/.cache/rattler/cache
      Auth storage: /home/prjemian/.rattler/credentials.json
  Config locations: No config files found

Global
------------
           Bin dir: /home/prjemian/.pixi/bin
   Environment dir: /home/prjemian/.pixi/envs
      Manifest dir: /home/prjemian/.pixi/manifests/pixi-global.toml

Project
------------
              Name: hey-there
           Version: 0.1.0
     Manifest file: /tmp/sandbox/hey-there/pixi.toml

Environments
------------
       Environment: default
          Features: default
          Channels: conda-forge
  Dependency count: 0
  Target platforms: linux-64


[5.2] Allow multiple whens and skips on an Event

This PR allows a Scheduling\Event to receive multiple when and skip callbacks, instead of just taking the last one and silently overwriting the previous ones.

Please only send your changes as a PR.

Sorry. Branched off master and opened a new one.


Theia 1.51.0

What it does

update to latest Theia
update branding-util because of changes to how links are opened

How to test
Build and check everything is still working
Review checklist

[x] as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

as a reviewer, I agree to behave in accordance with the review guidelines

mac build is stuck on github workflows, since no executor is available (Waiting for a runner to pick up this job...).
It worked on the Eclipse CI, so I think the mac build should be fine.


Enable a wildcard input for model

Requiring a model input kind of runs contrary to how pytest-operator works, especially for cases where we have multiple pytest files (each of which should run in a separate model).  For example, if we have:
tests
- integration
- - test_something.py
- - test_something_else.py

Those tests will be run in parallel and likely need separate models.  It would be great to be able to dump logs from that style test whenever we have a failure, too.
Perhaps we can do one of:

enable * (or make model optional, with empty meaning *), and have the logdump dump logs for all models
enable patterns (eg: test-charm-*), and dump logs from matching models

It might also be nice to optionally dump all applications, too.  These are not files people look at frequently, so just always having a full log dump doesn't sound that bad and might come in handy (for example, in integration tests which use a few applications)

We should migrate this action to github.com/canonical/charming-actions. In the process, making it dump logs for all resources wouldn't be a terrible idea. Feel free to have a stab at it if you have the time.


remove shuffle from tool command test

Work around https://github.com/flutter/flutter/issues/105924 while I'm investigating fixing the test

Actually, this is the fix forward: https://github.com/flutter/flutter/pull/105927


libsqlite3-sys and all its dependents get recompiled whenever I switch between cargo b and cargo watch -x b

When I build my crate (only whenever I switch between cargo b and cargo watch -x b!), it always recompiles a few deps that didn't change (starting with libsqlite3-sys):
   Compiling libsqlite3-sys v0.9.3
   Compiling diesel v1.3.3
   Compiling migrations_internals v1.3.0
   Compiling r2d2-diesel v1.0.0
   Compiling migrations_macros v1.3.0
   Compiling diesel_migrations v1.3.0

And then it recompiles my workspace's db crate that uses diesel, and all the other crates that depend on the db crate, so somehow libsqlite3-sys gets marked as dirty, but why?
It definitely didn't happen before I upgraded from diesel 0.16 (which used libsqlite3-sys 0.8.1) to diesel 1.3 (last week).
Do you have any idea what could cause this?
Maybe libsqlite3-sys 0.9.3 is reading some environment variables that are different with cargo-watch, and these env vars were not used in libsqlite3-sys 0.8.1?
Btw, it also happens when switching between cargo check and cargo watch -x r (but never when switching between cargo check & cargo b or cargo watch -x r & cargo watch -x b), so the defining characteristic is that this only happens when switching between building/checking with cargo "without cargo-watch" and "with cargo-watch".
So it must have something to do with cargo-watch, but only triggered by the new version of libsqlite3-sys somehow.

Does cargo-watch run cargo with a different value for the PATH env var than the value it has outside of cargo-watch?
If yes, it's triggering this.

/home/.cargo/bin is prepended, apparently. But it's not a cargo-watch thing, nor a watchexec thing. (I.e. nowhere in the code does the PATH get modified, afaics.)
I made a script called cargo-sh with this:
#!/usr/bin/sh

shift
echo "$*"
exec $*

And calling it with cargo sh env yields the same PATH line as when running cargo watch -s env.
Thus, this is a thing that cargo does when calling subcommands.


Unit test: Jest looking for babel configuration

When running the unit tests in a generated app, we have some warning about babel not found (and ignored) with Jest:
[vue-jest]: no .babelrc found, skipping babel compilation

There is maybe an option to explain to Jest that babel is not used.

That's weird, we are using Jest on React and Angular as well without Babel, of course it internally uses whatever it needs but does not make it required at project level. Also its just a normal log I wouldn't bother about it at all

Yes, we do not require it as top level dependency but that's the reason of the warning :)

lets ignore it then, its not worth it
Thanks & Regards,
Deepu
On Fri, Dec 21, 2018 at 1:46 PM Sahbi KTIFA<EMAIL_ADDRESS>wrote:

Yes, we do not require it as top level dependency but that's the reason of
the warning :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jhipster/jhipster-vuejs/issues/152#issuecomment-449379862,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDlF0d8gmxxYje3gtRQLyGsnQB8ZYzKks5u7Ng4gaJpZM4ZchuP
.


Add support for the new native ConPTY API in Windows 10

Information about the API is located here: https://blogs.msdn.microsoft.com/commandline/2018/08/02/windows-command-line-introducing-the-windows-pseudo-console-conpty/

Add bindings for the new API. Ideally we'd add support for this to winpty-rs, but I'm not sure how they deal with insider APIs.
Figure out whether we can use the insider SDK on Appveyor. It may have to be feature-gated if we can't.
Add an implementation of the EventedReadWrite (src/tty/mod.rs) trait for the ConPTY API.
Add config option for PTY backend on Windows and runtime switching based on Windows version.

Migrated to https://github.com/jwilm/alacritty/issues/1661


Add node.async_set_raw_config_parameter_value command

Breaking Change
The return value of async_bulk_set_partial_config_parameters and async_set_config_parameter has changed to include both whether the command was accepted immediately or queued, as well as the result if we have it.
Needed for certification (https://github.com/zwave-js/certification-backlog/issues/21). Dependent on https://github.com/zwave-js/zwave-js-server/pull/1068

@MartinHjelmare any thoughts on this PR? The locks PR is dependent on this one

Can you link to the issue that describes the certification requirement? There's no context right now in the PR description.

done


The semantics of the nuraft::snapshot

Hi,
Is it correct to assume that for each call of read_logical_snp_obj(s, ...) made by NuRaft, the following holds?

The first parameter s contains an information about raft log entry at which latest snapshot was made;
The value of first parameter s  is equal to the one which was passed to latest call of create_snapshot (i.e. s.get_last_log_idx() is equal to index of latest log entry included into latest snapshot);

To be more general, I'm wondering what information is passed as a first parameter to functions:

create_snapshot(snapshot&, ...)
read_logical_snp_obj(snapshot&, ...)
save_logical_snp_obj(snapshot&, ...)
apply_snapshot(snapshot&, ...)

Hi @unixod

s contains the information of the snapshot that the current NuRaft instance (leader) is transmitting to its follower. It can be the latest snapshot, or older than that.
Same as above, it can be older than the latest snapshot. More precisely, it is the snapshot that was the latest one at the moment the leader began the snapshot transmission. More snapshots can be created since then, but s will remain unchanged unless a new snapshot transmission begins.

In short,

create_snapshot: s contains the latest snapshot info, that the state machine has to create.
read_logical_snp_obj: s contains the snapshot that the current leader is transmitting. s will remain the same until the transmission either succeeds or fails. If it fails, read_logcial_snp_obj will be retried with newer s.
save_logical_snp_obj, apply_snapshot: same as read_logical_snp_obj.

Hi @greensky00
Thanks, the answer clarified a lot of things. But I still have several questions about.

Looking at the calculator example I observed that the state machine stores only last 3 snapshots.  How was this number determined? Is it safe to store any number of snapshots, or there is a limit for it? Will everything work correctly, if we store just one snapshot for each node?
Looking at read_logical_snp_obj function. There is an if block there, and I am wondering what are the concrete cases that we can enter that block?
Also why do we return 0 in that block if that is considered to be failure of snapshot reading (I mean why don't we return a negative value)?
Where does NuRaft take that first snapshot argument from? Am I correct that it gets it from calling last_snapshot on the leader node?
Because the reference of the first  snapshot argument is non const in all of the functions above, I suppose that user can modify it. Am I correct and if yes, what are those cases when the first argument can be modified?

Thanks!


Add helper scripts for preparing GCE environment.

Port the helper scripts in https://github.com/solvcon/solvcon-gce to Python.  And bring them into this main repository to simplify GCE management.
I tested the script for several days and it works fine.  But it is still an early version and considered a prototype.  I place it in the contrib directory and hope it's more convenient than the original shell scripts.

It's intentional to leave solvcon-gce scripts intact because the new Python script doesn't handle cluster building.  I simply ported the features that I found myself keep using.
I'll merge this PR.  When we ported all the features to this script we may deprecated the old solvcon-gce.


Fix issue #138

Coverage remained the same at 90.461% when pulling e288c7dd344cefbaf43c62ed1dd8a09a0e978690 on issue_138 into d211d11111ef578fa5ce819cfcee543f97000af3 on master.


AsyncAPI 3.0 support

AsyncAPI 3.0 is almost there (12-06-2023) and we should support it as far as possible
AsyncAPI 3.0 specification: https://www.asyncapi.com/docs/reference/specification/v3.0.0-next-major-spec.16

https://www.asyncapi.com/docs/migration/migrating-to-v3

Btw, we should support 0.2.6 and 0.3.0 both in the same time

Assigned to @KrySeyt


respect runstatedir

Respect runstatedir
configure: re-generate after changing .ac

Error here is not of tests, but that controller.xml contains things like:
  <CLICON_SOCK>${prefix}/var/run/controller/controller.sock</CLICON_SOCK>

This seems to help:
diff --git a/configure.ac b/configure.ac
index a326c1f..af38784 100644
--- a/configure.ac
+++ b/configure.ac
@@ -176,6 +176,8 @@ LIBDIR=`eval echo \`eval echo $libdir\``
 LIBEXECDIR=`eval echo $libexecdir`
 LOCALSTATEDIR=`eval echo $localstatedir`
 RUNSTATEDIR=`eval echo $runstatedir`
+RUNSTATEDIR=`eval echo \`eval echo $runstatedir\``
+

 AC_CONFIG_FILES([Makefile
                 src/Makefile

I am pulling this in locally


Add diagonal and screenRatio methods.

Thank you for the feedback.
I changed screenRatio to a tuple using Float.
diagonal is a Float number as well.
default cases are removed and unidentified case will return -1 or a tuple having -1's.

Awesome, thanks you so much! 🎉

Not at all. Thank YOU for the nice framework!


Documentation upload

This would implement #334. The only action needed would be to add a token in one account with ability to push to the repo and to add it as GH_TOKEN environment variable in Travis. Docs and coverage report will be uploaded automatically. For coverage report you need a coveralls account.
Also, I added tests to compile from Rust 1.3.0 to Rust nightly (1.3.0 is the lowest version compatible with Rust-crypto). Docs will be uploaded to a branch named gh-pages. An example here: https://github.com/FractalGlobal/ntru-rs

Documentation is available in https://docs.rs/rust-crypto/ so I guess that this is no longer needed. Do I close?


date argument to javascript should always be passed in non-localized format.

when I display form translated to czech language, it tries to display date in local datetime format (DD.MM.YYYY HH:mm:ss), but javascript does not parse it to any date, so the datetime field immediatelly blanks. Console shows warning (value provided is not in a recognized RFC2822 or ISO format).
When I manually reformat the date argument to datetimepicker js to YYYY-MM-DD HH:mm:ss format it starts to work.

Which is not easily solvable, because after invalid form validation widget gets last displayed values as localised string and not datetime object. Real solution is probably passing parsing format to moment()

@AxTheB Thanks to a PR, we are now passing in Moment's format... can you take a look at the most recent PR and see if that fixes your issue? Thank you!

Sorry I dont see any pull requests here. And I think the problem is in tempusdominus core, see https://github.com/tempusdominus/bootstrap-4/issues/182

Ah, I see it now: https://github.com/FlipperPA/django-tempus-dominus/pull/4
Its interesting, I will try it as soon as possible.

Yea, it looks like it works well. Thanks a lot.

Thank to @ianastewart - he's the one who fixed it! Take care.


Add ability to input a 'custom' value, in addition the form-specified values

Proposal: add the ability to input a 'custom' value for a key, in addition to the set of predefined values in the form
Example: for a bank's operator key, a number of possible values have been predefined (to minimize errors/typos, and cut down on data entry time), like Barclays Bank, Stanbic Bank, Bank of Africa, and Finance Trust Bank. However, these cover only the ones that occur regularly; mappers can encounter other banks, and would need to be able to enter the actual value for the operator for those. So when a mapper find a Tropical Bank (yes, it does exist :), he'll need to be able to type this name instead of choosing one of the predefined values.

This is currently being tracked as #58


Flow Router ssr needs fast-render?

Hey, when using flow-router-ssr and react, do we need fast-render to inject into html, will ssr work without it? What is the benefit? (populate the mini-mongo collection before the ddp connection established?)

Actually, you don't need to use fast-render.  flow-router-ssr  will do it automatically. That's something required when doing React SSR. (We need to have the same data as on the server, when rendering components on the client)

I mean, when we use flow-router-ssr and react in both folder and view the page source - the components data is already there and the fast-render injected code is below. So the components have the data because of fast-render and this injected code?

Even when disabling javascript, we already get the html with the data, so it is rendered on server and sent with data?
I may sound stupid, but I am trying the flow-router-ssr and react combo and want to understand, why we need fast-render (and injected data in <script type="text/inject-data">) if the components already come with data.
@arunoda maybe you can drop a line or two to make it more clear? I will be very grateful.

Okay. let me add more :)
So with SSR, we have HTML coming from the server. Then there is a set of components rendered on the client, once React is booting on the client.
So, React needs to merge both the components in the HTML and generated on the client side. It use a checksum for that. If that checksums are different, it will clean the components comes with HTML and replace with client generated components.
That's why we need to have the fast-render powered data on the client.
This is due to how to React works. But I hope this can be improved in the React framework level.

@arunoda oh, that definitely made everything clear.
The last question - the checksum of the components includes data and we need the fast-render data in <script type="text/inject-data"> to compare checksums immediately and not wait until the data will come from ddp connection to compare with it. Am I right?

Nope. Checksum is on each react component.
See: view-source:https://kadira.io/

@arunoda yes, I understood the same.
So, basically to get rid of inject-data we could wait for all subs ready, grab the data, only then start React and then compare checksum. But it will be very long so we need fast-render to have the data immediately. And since the data will be the same (as html and injected data both come from the server at the same time), we actually compare, if the components code has changed.

@arunoda Thank you, I think I understood, why we need the fast-render and injected data.
I was a bit scared of all the data, injected to the bottom of html. But is seems, we can't get rid of it. At least for now.


Blob containers do not refresh in VS Code extension

Does this occur consistently? Yes
Repro steps:

Create Storage Account, Container, and Blob
log into VS Code Azure Extension
see the blob under "Storage Accounts->"Blob Containers"->""
Delete the Blob in Azure UI or via command line
Blob Disappears from list in UI
Blob Still appears in the Azure extension in VS Code - even after refresh hitting the loop arrow icon at the top of the sidebar for the extension

I would expect to see the blob disappear - this does not make me confident that i am working with the latest copy - sometimes I just need to view the contents of a file and the UI for the extension  makes it super easy to do so - but i can't trust it :(
Version: 0.14.2
OS: linux
OS Release: 4.19.128-microsoft-standard
Product: Visual Studio Code
Product Version: 1.69.1
Language: en

Thanks for filing this bug, we understand how this is annoying.
Until this is fixed, you can use the Refresh in the right click context menu on the Blob Containers node.


Resource to add: http://reddit.com/r/forhire

URL: http://reddit.com/r/forhire
Message: freelance
This issue was automatically generated from the website.

Added.


Test expiration

I don't think expiration works as intended (or at least as I would expect it).
The response keys are correctly expired, but nothing is ever removed from the idempotency keys set. This has two consequences:

once a response key expires, requests using the same idempotency key will return 409 forever
the idempotency keys set grows without bound

Instead, I would expect expiration to also apply to the idempotency keys set. Once the expiration window has passed, a new request with the same idempotency key should issue a new request.
This commit only introduces the tests without implementing a solution. For MemoryBackend, I'd propose storing the expiry alongside the idempotency key. For RedisBackend, I'd propose something along the lines of https://github.com/redis/redis/issues/135#issuecomment-2361996 using a sorted set to purge expired idempotency keys. But I wanted to run the change by you before taking action on either approach.

Yeah I agree this seems like an implementation we've forgotten to account for. I like the look of the redis suggestion, so feel free to finish the implementation along those lines 👍 Just ping me when you consider this ready and I'll take another look 🙂

Great - I'll throw something up later this week.

I've added a new expire_idempotency_keys abstract method thatimplementations of Backend are responsible for implementing. The middleware calls it on every request.
For the Memory backend, we now store idempotency keys in a dict intead of a set. The value of each key is its expiration time.
We then iterate over all of the items in the dict and remove the ones with an expiration earlier than the current time. This operation isn't very efficient because it iterates over the entire dict, but given that the Memory backend is only meant to be used in local testing, I don't think it's worth optimizing further.
For the RedisBackend, we now store idempotency keys in a sortedset instead of a set. The "score" of each key is its expiration time. This matches the Redis project's official recommendation on how to expire items in a set: https://github.com/redis/redis/issues/135#issuecomment-2361996
We then delete any items from the sorted set with a "score" lower than the current time. The Redis docs describe this a potentially slow operation: https://redis.io/commands/zremrangebyscore/
If we don't want to call this on every request, we could instead add some sort of random fuzzing to only occassionally call it. Or we could abandon using a sorted set entirely and just store the idempotency key as its own key in Redis using the standard Redis expiration functionality. This would mean each request would store potentially three keys (idempotency key, response key, status code key) instead of the current two (response key, status code key).
Users who upgrade to a version of the library that includes this change will see a failure in Redis when it tries to use a sortedset operation on an existing set. At a minimum, this should be called out in a changelog. Additionally, we could change the default idempotency key name from idempotency-key-keys to something else to avoid a collision.

Users who upgrade to a version of the library that includes this change will see a failure in Redis when it tries to use a sortedset operation on an existing set. At a minimum, this should be called out in a changelog. Additionally, we could change the default idempotency key name from idempotency-key-keys to something else to avoid a collision.

Is that because we re-use the same key value for the new data structure? Could we get around the error by changing the key?
I guess upgrading will still effectively drop existing data, which isn't that great. Could this be mitigated if we stored multiple values?


Stats Fix

🐛 fix stats.dart script for latest analyzer
Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
All new code requires tests to ensure against regressions

Description of the Change

Alternate Designs

Why Should This Be In Core?

Benefits

Possible Drawbacks

Verification Process

Applicable Issues

Codecov Report

Merging #3 (ba0e0cc) into main (b38a716) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
- Coverage   99.80%   99.79%   -0.02%
==========================================
  Files          21       21
  Lines         508      482      -26
==========================================
- Hits          507      481      -26
  Misses          1        1

Impacted Files
Coverage Δ

lib/generic/generic.dart
100.00% <0.00%> (ø)

lib/collection/iterable.dart
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


[stable/dokuwiki] Improve getting LoadBalancer address in chart NOTES…

Testing a K8s cluster where LoadBalancer service returns hostname and not ip.
This PR change our current approach in bitnami helm charts where we report IP by doing
-o jsonpath='{.status.loadBalancer.ingress[0].ip}'

The new approach is to use
--template "{{"{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}"}}"

where the . returns value for whatever field is in the map.
Source: https://github.com/helm/charts/issues/84#issuecomment-257754892
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

/lgtm


Add a test that the timer is removed after unmount?

Just a thought 😄. Probably want to test that no dangling intervals or timeouts are left behind after unmount.

good thought. looks like there is a jest.getTimerCount() that I can use for just that purpose.


Canvas image

Good afternoon,
If I place a canvas in a div, and draw to it, can I save all normally, or must I convert first the canvas svg to an image url? If yes, how do I add it to the whole pdf...?
The div will contain the canvas, tables and texts, which I intend to save as PDF.
Thanks in advance.
Kind regards

Hi @cptolemy, the canvases should work with no modification! Let me know if there's any issue - I'm going to close this issue, but please re-open it if there's a problem.

Hello @eKoopmans, I tried converting an html element with a canvas that is being drawn once the page is loaded coming from a dynamic data api source. Now once i run my code to conver this element to PDF it seems it will not render show the  canvas in the pdf. Did miss something? thank you!


multiline javaArgs breaks run.sh script

example build.gradle fragment:
runOsgi {
    [...]
    javaArgs = '''
        -Djersey=true
        -Dosgi.clean=true
    ''''

works for ./gradlew runOsgi but run.sh script looks like this:
[...]
"$JAVA"
                -Djersey=true
                -Dosgi.clean=true
         -jar org.apache.felix.main-5.4.0.jar  "$@"

There should be '' at line ends.

Why don't you do this:
runOsgi {
    [...]
    javaArgs = '''\
        -Djersey=true\
        -Dosgi.clean=true \
    ''''
}

I do :) but every time I edit and copy those properties between different launch environments, I have to run macro to add or strip the ''.

Ok... well, I guess it never makes sense to have new-lines in javaArgs... so we can actually fix that.

Thx .
and BTW great plugin :)


Respect gitlab_email_enabled property

GitLab uses this property but gitlab-ctl reconfigure doesn't recognize this gitlab.rb setting.

@dserodio Thanks!


Tweak sort indicator in table columns?

It’s a little dependent on your browser’s font size (because we didn’t want it to be hidden if the text is truncated with an ellipsis). Maybe it should be align-dependent?

Related: https://github.com/observablehq/inputs/issues/103


add list input and rewrite codegen use python

这个 PR 实现什么功能/修复什么问题:
是否需要 backport 到之前的 release 分支:

2.13

/area util
/cc @swordqiu @yousong

Codecov Report

Merging #3966 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3966      +/-   ##
=========================================
+ Coverage    6.94%   6.94%   +<.01%
=========================================
  Files         505     505
  Lines       85012   85010       -2
=========================================
  Hits         5903    5903
+ Misses      78607   78605       -2
  Partials      502     502

Flag
Coverage Δ

#aFlag
6.94% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/guests.go
0.59% <0%> (ø)
:arrow_up:

pkg/compute/models/hosts.go
0.34% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm

/approve
/lgtm


Integrate pep8 for Python code style checking

https://pypi.python.org/pypi/pep8

I find a useful open source tool created by google, yapf  https://github.com/google/yapf
pip install yapf  will install yapf tool.
This tool provides 4 based style to choose: pep8, google, facebook and chromium.
The style can be find in this link. https://github.com/google/yapf/blob/master/yapf/yapflib/style.py
I make some python code formatting test on currently code on github
Here is a .style.yapf config file created in paddle directory:
[style]
based_on_style = google
indent_width = 4
spaces_before_comment = 4
split_before_logical_operator = true

After run yapf -r -i python/, the python code will be formatted.
But, it brings so much diff and changes our python code format.
Should we format the code right now, or just add a yapf config file?

basically done, closed


Example program issues

I've noticed that when running the samples anywhere but from the root of the repository they throw the error:
ModuleNotFoundError: No module named 'latentblending'

This occurs even after installing the latentblending package successfully, both via pip and setup.py. I'm guessing this is an environment issue, but to make it easier for beginners to deploy I'd recommend putting one of the Python programs in the examples/ directory into the root of the repo.

good point, thanks!


Add alter for start segment > end segment input

Add an alert for when start segment > end segment input.

Resolved with latest commit.


This issue report is returning a broken link to github

Issue Type: Bug
Why is there a dropdown option on this feedback form, the field called "File on," why does it have a non-acceptable choice? If I forget to select something from the dropdown, it's supposed to remind me.  But it's currently got the option "Don't Know" which I can select. However if I select it, I get a message that says "An issue source is required."
That's goofy. Probably take that out and only set it to Nag the user if they forget to select a dropdown item.
VS Code version: Code 1.62.3 (ccbaa2d27e38e5afa3e5c21c1c7bef4657064247, 2021-11-17T08:11:14.551Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

Hi @KirkH420 can you let me know what choice was a non-acceptable choice? Was this some extension? It's possible that the extension needs to update a field to point to their new issue URL.


refactor client

Codecov Report

Merging #55 (5dba71a) into main (6ac128d) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #55   +/-   ##
=======================================
  Coverage   89.09%   89.09%
=======================================
  Files           7        7
  Lines         220      220
=======================================
  Hits          196      196
  Misses         18       18
  Partials        6        6

Impacted Files
Coverage Δ

app/blizz/client.go
80.80% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #55 (5dba71a) into main (6ac128d) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #55   +/-   ##
=======================================
  Coverage   89.09%   89.09%
=======================================
  Files           7        7
  Lines         220      220
=======================================
  Hits          196      196
  Misses         18       18
  Partials        6        6

Impacted Files
Coverage Δ

app/blizz/client.go
80.80% <100.00%> (ø)

Continue to review full report at Codecov.

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


Updates for rustc nightly.

Use visibility pub(crate) in lieu of crate, now that the latter is marked as experimental.
Remove cargo feature "edition," now that it's stable.

I need this change as well. The CI failure seems unrelated to this pr.

CI failure is just some new bugs in rustdoc's code links feature, @MajorBreakfast it might pay to just disable testing that on CI since it's so flaky at the moment.

I'm going to merge this and publish so we can un-break nightly.


Cannot convert Symbol to String when initializing converter

When the asciidoc key is not defined in _config.yml, the base_dir option is set to :docdir, and the serve command is run, the converter fails to initialize.
The problem seems to be that the check for whether the configuration has already been initialized fails when the asciidoc key is not defined in _config.yml.

We could modify the configuration defaults to fix this problem, perhaps.

The alternative is to just make sure the initialization can safely run multiple times.

The defaults are frozen in Jekyll 3.

The only real solution here that I can think of is that we need to check whether the asciidoc key and the asciidoctor key are already configured individually. If either key is not set in the configuration file, the initialization will have to be run again when the watch command kicks off. So we should encourage users to set both keys in the configuration file.

Also, move the registration of the hooks inside the check for the asciidoc key. They are more associated with that than the asciidoctor key, so it is more correct.
The minimum configuration we would ask for optimal behavior is:
asciidoc: {}

and perhaps even:
asciidoc: {}
asciidoctor: {}

However, I think it's pretty safe to assume that most people will have an asciidoctor configuration already. So instead of confuse them, just mention that the minimum is the asciidoc configuration.

We need to report this upstream that Jekyll is not passing through the config object from site, but rather a fresh config object that somehow shares values for existing keys if the value of the keys is a Hash. Why not pass the config object from site?


Allow icons in classic letter

This fixes the bug found in:
https://github.com/moderncv/moderncv/issues/170

Sounds good. I've added it for banking/fancy as well. They look good now.
One thing I noticed is that the symbols used for oldstyle are the marvosym symbols whereas all the other ones use symbols. What this means is that for oldstyle no symbols appear for the socials.

Sounds good. I've added it for banking/fancy as well. They look good now.

Thanks for adding the symbols also for the other styles, @thecaligarmo !
Sorry to bother you again, but would you mind to write a short notice in our CHANGELOG as well? That would be great!
Something like
- include social icons in cover letter for styles classic, fancy and banking (#170)

One thing I noticed is that the symbols used for oldstyle are the marvosym symbols whereas all the other ones use symbols. What this means is that for oldstyle no symbols appear for the socials.

Oh, interesting. Did you use pdflatex?
It comes from here, you are right:
https://github.com/moderncv/moderncv/blob/cdf027a9da1f16038c2df3c02147b3b316741dac/moderncvstyleoldstyle.sty#L48-L57
In my opinion it line 51 should be at least \moderncvicons{symbols}. Maybe line 53 should be changed to that too.
But I think we should cover this in a separate issue.

Yes, I used pdflatex. Yeah, I don't know why that choice was made. If it needs to be changed, you can make another ticket and assign it to me. I can do it fairly fast.
Changelog has been updated as requested.


extract script utilities into single binary

...so that we a) don't have to start containers for invoking fastdp functions, which is costly, and b) reduce image size by having just a single executable for all utilities.
We fall back to invoking the new weaveutil in a container if we cannot find the exe. As a result, weave --local ... now runs both netcheck and docker-tls-args.
Fixes #1613.

btw, for me this reduces time weave launch from 2.8s to 1.7s.


Update Actions version

Proposal
I have found the actions of the older version.
If this issue is accepted, I will research and update it for items other than those listed below.

Checkout's latest is v4
Setup-Python's latest is v5
Cache's latest is v4

https://github.com/databricks/databricks-sql-python/blob/97c815eb03249070bcdec40e8d4c4fa86a53e278/.github/workflows/code-quality-checks.yml#L15-L26
Next Action
If there is no reason why you are using an older version, I would be happy to help you.

Hi @newwingbird! We're using these versions because they work, and GitHub doesn't complain 🤷♂ We usually do upgrade actions when older wersions become unsupported. But if you want to help with upgrade right now - you're welcome 👍


QuantumTrainer.fit(train_dataset) error - examples / quantum_pipeline.ipynb

For either the MC or RP dataset, with training and test data, calling fit(train_dataset, logging_step=12) generates the following error:

ValueError                                Traceback (most recent call last)
~\AppData\Local\Temp\ipykernel_34608\45519830.py in
...
C:\Anaconda3\lib\site-packages\lambeq\training\quantum_trainer.py in fit(self, train_dataset, val_dataset, evaluation_step, logging_step)
197         self.model._training = True
198
--> 199         super().fit(train_dataset, val_dataset, evaluation_step, logging_step)
200
201         self.model._training = False
...
C:\Anaconda3\lib\site-packages\discopy\quantum\tk.py in get_counts(self, backend, *others, **params)
131         if compilation is not None:
132             for circuit in (self, ) + others:
--> 133                 compilation.apply(circuit)
134         handles = backend.process_circuits(
135             (self, ) + others, n_shots=n_shots, seed=seed)
ValueError: Non-unitary matrix passed to two_qubit_canonical

Can you tell us more about your system? OS, python version, version of lambeq, pytket etc.

@dtchang Please include the full trace of the error, as well as the versions of the python packages (lambeq, pytket, discopy) as requested by @Thommy257.

Thanks for looking into this.
Here is the information on the python packages:
lambeq: 0.3.1
discopy: <IP_ADDRESS>
pytket: 1.11.1
Python: 3.9.15
JupyterLab: 3.5.2
Windows 10
Here is the full trace:
ValueError                                Traceback (most recent call last)
~\AppData\Local\Temp\ipykernel_8264\45519830.py in
1 #trainer.fit(train_dataset, val_dataset, logging_step=12)
----> 2 trainer.fit(train_dataset, logging_step=12)
C:\Anaconda3\lib\site-packages\lambeq\training\quantum_trainer.py in fit(self, train_dataset, val_dataset, evaluation_step, logging_step)
197         self.model._training = True
198
--> 199         super().fit(train_dataset, val_dataset, evaluation_step, logging_step)
200
201         self.model._training = False
C:\Anaconda3\lib\site-packages\lambeq\training\trainer.py in fit(self, train_dataset, val_dataset, evaluation_step, logging_step)
373                     step += 1
374                     x, y_label = batch
--> 375                     y_hat, loss = self.training_step(batch)
376                     if (self.evaluate_on_train
377                             and self.evaluate_functions is not None):
C:\Anaconda3\lib\site-packages\lambeq\training\quantum_trainer.py in training_step(self, batch)
161         """
162         self.model._clear_predictions()
--> 163         loss = self.optimizer.backward(batch)
164         y_hat = self.model._train_predictions[-1]
165         self.train_costs.append(loss)
C:\Anaconda3\lib\site-packages\lambeq\training\spsa_optimizer.py in backward(self, batch)
139         xplus = self.project(x + self.ck * delta)
140         self.model.weights = xplus
--> 141         y0 = self.model(diagrams)
142         loss0 = self.loss_fn(y0, targets)
143
C:\Anaconda3\lib\site-packages\lambeq\training\quantum_model.py in call(self, *args, **kwargs)
144
145     def call(self, *args: Any, **kwargs: Any) -> Any:
--> 146         out = self.forward(*args, **kwargs)
147         if self._training:
148             self._log_prediction(out)
C:\Anaconda3\lib\site-packages\lambeq\training\tket_model.py in forward(self, x)
131
132         """
--> 133         return self.get_diagram_output(x)
C:\Anaconda3\lib\site-packages\lambeq\training\tket_model.py in get_diagram_output(self, diagrams)
100
101         lambdified_diagrams = [self._make_lambda(d) for d in diagrams]
--> 102         tensors = Circuit.eval(
103             *[diag_f(*self.weights) for diag_f in lambdified_diagrams],
104             **self.backend_config,
C:\Anaconda3\lib\site-packages\discopy\quantum\circuit.py in eval(self, backend, mixed, contractor, *others, **params)
286             return type(box)(box.dom, box.cod, box.array + 0j)
287         circuits = [circuit.to_tk() for circuit in (self, ) + others]
--> 288         results, counts = [], circuits[0].get_counts(
289             *circuits[1:], backend=backend, **params)
290         for i, circuit in enumerate(circuits):
C:\Anaconda3\lib\site-packages\discopy\quantum\tk.py in get_counts(self, backend, *others, **params)
131         if compilation is not None:
132             for circuit in (self, ) + others:
--> 133                 compilation.apply(circuit)
134         handles = backend.process_circuits(
135             (self, ) + others, n_shots=n_shots, seed=seed)
ValueError: Non-unitary matrix passed to two_qubit_canonical

Thanks for the information. It seems you are using an older notebook from lambeq version 0.2.8, which creates this error when running with lambeq 0.3.0 or higher. The reason is that you are using custom loss functions, which do not work very well with the new initialisation we introduced in lambeq 0.3.0. The easy solution would be to use lambeq's losses, e.g. BinaryCrossEntropyLoss, as we do in the updated notebooks. If you still prefer to use your own losses, you have to add some additional safeguards which prevent situations such as 0-div (check source code of the lambeq's loss functions).

@yousrabou this might be also relevant to your problem.

using :
lambeq : 0.3.1
pytket : 1.14.0
pytket-qiskit : 0.38.0
and the BinaryCrossEntropyLoss function for training RP dataset on GoogleColab envirenement
the following  error is produced  !!
ValueError                                Traceback (most recent call last)
 in <cell line: 1>()
----> 1 trainer.fit(train_dataset, logging_step=12)
7 frames
/usr/local/lib/python3.10/dist-packages/lambeq/training/loss.py in _match_shapes(self, y1, y2)
64                       y2: np.ndarray | jnp.ndarray) -> None:
65         if y1.shape != y2.shape:
---> 66             raise ValueError('Provided arrays must be of equal shape. Got '
67                              f'arrays of shape {y1.shape} and {y2.shape}.')
68
ValueError: Provided arrays must be of equal shape. Got arrays of shape (30,) and (30, 2).

Hi @yousrabou ,
It would help to know the following:

What is the codomain of the diagrams in the dataset (1 qubit  or 0 qubits (scalar)?)
The code snippet where you prepare y_true targets.

I'd recommend taking a look at the documentation for the loss function, which describes the expected param shapes.

I tried the updated notebook for both the MC and RP datasets with only training and test data. No error. So, I'm closing this issue.

This issue is now resolved and will be now closed -- @yousrabou please follow-up your question in #90.


Upcoming 1ES PT change: Release tasks may not be used in build jobs, need to be split into release jobs

Saw this warning in this pipeline run for dnceng-ci

##[warning]1ES PT Warning: Job 'Windows_NT' uses the release tasks ["ServiceFabricUpdateManifests@2"] but is not marked as a release job. Release tasks will soon be disallowed outside of release jobs. See https://aka.ms/1espt/custom-release-job

At a glance I couldn't find a list of tasks that are considered release tasks, so we should see which other pipelines are starting to see similar warnings.

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description

Conversation here: https://teams.microsoft.com/l/message/19:83953de1ddd34bcaa9ebaba54cb8eba4@thread.skype/1729275368719?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=147df318-61de-4f04-8f7b-ecd328c256bb&parentMessageId=1729275368719&teamName=.NET Eng Services&channelName=General&createdTime=1729275368719

Another conversation here: https://teams.microsoft.com/l/message/19:276707cdcf5d431caaa8792b29bd832d@thread.skype/1730827716291?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=147df318-61de-4f04-8f7b-ecd328c256bb&parentMessageId=1730827716291&teamName=.NET Eng Services&channelName=FR Internal&createdTime=1730827716291
Also, re-priortizing this to a 2


More robust resource lookup

ignore NPEs that come randomly from some JDKs
support resource interfaces that are on classpath but not in current annotation round

(replacement for https://github.com/treblereel/gwt-resources/pull/31 )

@zbynek thank you, i ll add few more PR's and release it to sonatype.


Implement ITerminalConnection::ConnectionState and closeOnExit=graceful/always/never

Summary of the Pull Request
This pull request implements the new ITerminalConnection::ConnectionState interface (enum, event) and connects it through TerminalControl to Pane, Tab and App as specified in #2039. It does so to implement closeOnExit = graceful in addition to the other two normal CoE types.
It also:

... exposes the singleton CascadiaSettings through a function that looks it up by using the current Xaml application's AppLogic.

In so doing, we've broken up the weird runaround where App tells TerminalSettings to CloseOnExit and then later another part of App asks TerminalControl to tell it what TerminalSettings said App told it earlier. :crazy_eyes:

... wires up a bunch of connection state points to AzureConnection. This required moving the Azure connection's state machine to use another enum name (oops).
... ships a helper class for managing connection state transitions.
... contains a bunch of template magic.
... contains a TODO (whoops, sorry, if you point it out you'll be removed from the selfhost program)
... introduces WINRT_CALLBACK, a oneshot callback like TYPED_EVENT.
... replaces a bunch of disparate _connecting and _closing members with just one uberstate.

References
Specification is in PR #2039.

PR Checklist

[x] Closes #2563
[x] CLA
[ ] Tests added/passed
[x] Requires documentation to be updated
[x] I've discussed this with core contributors already.

/azp run

/azp run


[3.x] Move to AWS SDK for Java v2

Thanks @belaban - I have setup a 2.x branch and moved main to 3.x now.


apk: use https fastly repositories

what
Switch to the HTTPS alpine apk repositories
why
#249

Fix CI


Event is set to "All Day" when creating an agenda from calendar page using drag and drop

Hi! Thanks for making this calendar plugin! I just wanted to report what I think is a bug.
In the calendar page, if I create an event when dragging, what I think should happen is that the event will be set on the time I dragged over (in this case, 4-7am)

but when the "Modify Schedule" pops in, "All day" is set to Yes.

and the time only appears if I manually set "All day" to "No"

I have the same issue

Agenda3 has a brand new calendar, you can give it a try.

The new calendar is amazing, thank you!


Updated incorrect links from original source

I'm migrating my personal site to Astro and have used this repo as a helpful refence. Figured I'd repay you in a very small way by fixing a few things I noticed. The sitemap one is probably the most important as that likely has real SEO implications. You may also want to do an audit for other stuff from your original source (e.g the PR template for this repo doesn't make sense and web mentions are not super relevant in 2024).
Anyway, thanks for making your code open source 😄

Also, for the robots.txt, I went with the dynamic generation route via pages/robots.txt.ts which makes this bug impossible, described here.


Skript 2.6.2 not work

Hi, the Skript has been updated [2.6.2]. Unfortunately, Skript-packed does not run on the new version. Since there are changes in the loading of addons.

skript-packet-2.1.0-BETA.jar.zip
Hi, I made this hotfix. Does it works ? (Note : YOU HAVE TO USE JAVA 17+ even if you're not using a recent version of Minecraft)

Hi, plugin is working now :)

Official release is available. It's not like this beta file so you should replace it :)


EXR GDK.PixbufLoader

It would be really nice to add EXR native support to many  linux desktop distributions.
So it would be great if the library deliver a GDK.PixbufLoader.
Just to make two examples (for WEBP and svg):
https://github.com/aruiz/webp-pixbuf-loader
https://gitlab.gnome.org/GNOME/librsvg/-/tree/main/gdk-pixbuf-loader

An old unmaintained openexr effort:
https://github.com/afichet/openexr-thumbnailer


Documentation regarding Consistency

Can you please add some documentation about how to maintain consistency in terms of running it from browser?

Can multiple PGLite easily access single storage (IndexedDB)?
Will it corrupt the data? Do we need any external locking mechanism?

Good idea, we should document this better.
For quick context, PGlite is Postgres in "single user mode". There is no support for concurrent connections and you are like to corrupt the database if you open it multiple times at once.
The PGliteWorker helps you to open only a single instance and share it across browser tabs.

Related question - is there any way to check if a target directory is currently in use by a PGlite instance?
It would be awesome if the PGlite constructor threw (or the waitReady promise rejected) with a descriptive error, e.g. "this dataDir is currently in use by another PGlite instance" rather than allow undefined behavior / data corruption. I'm using the Node.js filesystem, but I imagine this applies to the others as well.
I think this validation would be a reasonable side-effect of either the init or  initialSyncFs methods on the Filesystem interface.
https://github.com/electric-sql/pglite/blob/5e390365b6ed5b5c122047a248a4117c50390fa4/packages/pglite/src/pglite.ts#L345-L346

Hey @0xOlias
Yep, we should absolutely do this.
In the browser I think the best way is to implement it with WebLocks, for Node we should open and lock a file in the FS.


Remove deprecated PPA ondrej/php5.

PR for #971

Failure on CentOS 7 was due to:
http://cgit.drupalcode.org/drupal/plain/.eslintignore?h=8.2.2\" file could not be downloaded: failed to open stream: Connection timed out

Running it again.


Editor changes

With the creation of a new article category of "training articles" we have updated the templates.  To avoid unnecessary work for you (this has already been a long process!) we have forked the github repository and made the changes ourselves.
In addition, we added some DOIs to the bibliography to make it more uniform.
Originally, the repository originally contained supporting information.  My understanding is that now you wish to simply refer readers to the GitHub repository. Is this correct?
1-BPIPMDS.pdf
If these changes all look good, then accept the PR (so the changes are part of the permanent record), and we will move forward with publication.
If the attached PDF looks good, we can move forward with this one, you do not need to regenerate it.

Thank you very much for these edits
It is correct that we wish to simply refer readers to the GitHub repository for the supplementary information. For clarity we propose to rename the folder "input" to "supplementary", and write a notice about this in the README.
On our final read-through of your attached PDF, we caught a couple typos in the manuscript - there is always one more.
Do you want us to make these final edits within this PR, or should I accept this PR and then make our final set of changes as usual, and send you a notice when it is done?

Do you want us to make these final edits within this PR, or should I accept this PR and then make our final set of changes as usual, and send you a notice when it is done?

The latter sounds good.  Let me know when you have these changes done; it will be easiest to simply repost your final pdf in releases/ directory as per the usual preparation instructions.  If you can finish them before end of day Norway, that would be appreciated; we are aiming to publicize the finalization of this issue today (US time).

@mrshirts I've implemented our final changes and updated the releases pdf as instructed.


Async delegate call causing random crashes in pie

AsyncTask(ENamedThreads::GameThread, [&, Data]() { 			OnReceivedBytes.Broadcast(Data); })
Is causing random crashes when starting/stopping PIE. I am using unreal engine 4.21, and running pie as dedicated server. I have been unable to track the bug down to a root cause, however it goes away when commenting out these lines. The errors triggering visual studio exceptions in DebugGame Editor mode are inconsistent.

Got any logs from the crashes?